>>>>> "vincent" == Vincent Meyer <[EMAIL PROTECTED]> writes:

vincent> Hi,
vincent> Since a couple of kernel updates ago, this machine hasn't been too solid.  
vincent> I've experienced solid lock-ups, where only powering off will allow me to 
vincent> restart the machine.

vincent> Tonight it happened again, and I tried to do an <alt> <sys req> S
vincent> to sync the disk (and preserver my file system!) and got the following.  I
vincent> think I may have had this before, but with X running at the time the machine 
vincent> freezes, couldn't see it.  Tonight I was in the console when it happened, so 
vincent> I was able to see the messages.

vincent> SysRq: Emergency Sync
vincent> Syncing device 03:05 .. scheduling interupt
vincent> kernel BUG at sched.c:712!
vincent> invalid operand
vincent> CPU 0
vincent> EIP 0010:[<c0113260>] Tainted: P
vincent> EFLAGS 00010286
vincent> Process cc1 (pid 20108 stackpage ccc0a000)
vincent> <0> kernel panic Aiee, killing interupt handler!
vincent> in interupt handler - not syncing

vincent> (sorry, snipped out the registers some of the detail.  If it will help let me 
vincent> know and I'll write it all down.)


Try -7mdk, 2.4.13-ac8 has a patch that caused inestabilities, now it
should work right.

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

Reply via email to