On Mon, Nov 10, 2008 at 03:31:42PM +0100, Pascal A. Dupuis wrote: > On Sun, Nov 09, 2008 at 02:55:32PM +0100, Aurelien Jarno wrote: > > > > If your system is totally frozen, I have doubt it's a qemu bug. Looks > > like more a hardware or kernel problem. > > > > You should send you system logs over the network, so that you can see > > what happens when the computer crash. > > > > Hello Aurelien, > > the trouble is that I suspected various causes, and eliminated them all: > - the /var/log/messages and syslog are empty for the minutes preceeding the > crash, only occasional '-- MARK --' lines
Looking at that is not really relevant if your system totally freeze. You may miss some messages that have not been written to the disk. > - it's not linked to thermal overrun, as I kept the CPU clock frequency low > enough to not overheat the laptop > - last, I performed the same simulation under bochs: it is much slower, > but I didn't get a single lookup. Setup: block device and network emulation > are exactly the same than under qemu > > OTOH, I didn't experience lookups recently (in the last 3 month) in any > other circumstances. > > So maybe qemu is triggering some hardware or kernel bug, how to debug ? > You have to send your system logs to a second machine, it is the only way to have a possible log of the crash. Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
