From: Alexander Z. <Ale...@fm...> - 2000-09-14 14:28:05
|
On 13 Sep, David Paschal wrote: > >> But now, how to track this error. Before chrashing there are a lot of >> messages displayed on the screen (virtual consule 1), but these are not >> in the log file after rebooting, and scrolling up the screen doesn't >> work any more, when the kernel crashed. Redirecting to file also does >> not work. Any idea? > Redirecting to a file wouldn't work because the messages are sent directly > to the console by the kernel, rather than through standard output or > standard error of any particular process. I added line numbers to the printk statements in ieee12844pp.c the last lines before the crash are (transcribed): 439: get_nibble(e00ba5c0): nibble=0x5 Aiee, killing interupt handle 444: e00ba5c0: event=11. Kernel panic: Attemped to kill the idle task! 448: e00ba5c0: event=6. In swapper task - not syncing 433: e00ba5c0: event=9. Does this help? > Is there any way you can run an SMP kernel but somehow force your computer > to only activate one CPU, either by a BIOS setup option, dip switch/jumper, > or physically removing one CPU (but be careful!)? If you can duplicate > this problem with an SMP kernel on a uniprocessor system then I might be > able to scrounge up an extra PC and set it up to work on this problem if > nobody else can. There is no way to deactivate the CPU without unscrewing the machine. I'll try that as soon as it is possible. -- Ale...@fm... / You look like a million http://www.fmi.uni-passau.de/~zimmerma/ dollars. All green and for PGP public key finger / wrinkled. zim...@yo... / |