shutdown does not work under suse 9.1

hello NG, i have a problem with a suse 9.1 system. from time to time, i'm not able to shutdown it properly. Yesterday, i did a "shutdown -h now". As far as i remember, the console output was "switching to runlevel 0" and "sending all processes the TERM signal". The "sending all processes the KILL signal" did not come (as far as i remember). Here is an excerpt from my syslog (hopefilly not too long): ----------------------------------------------------------------------------------------- Sep 4 17:52:25 pc51332 init: Switching to runlevel: 0 Sep 4 17:52:26 pc51332 kernel: Unable to handle kernel paging request at virtual address fa0129a0 Sep 4 17:52:26 pc51332 kernel: printing eip: Sep 4 17:52:26 pc51332 kernel: c028d0e5 Sep 4 17:52:26 pc51332 kernel: *pde = 32833067 Sep 4 17:52:26 pc51332 kernel: Oops: 0002 #1 Sep 4 17:52:26 pc51332 kernel: SMP Sep 4 17:52:26 pc51332 kernel: CPU: 0 Sep 4 17:52:26 pc51332 kernel: EIP: 0060:jpegdecode+3301-4240 Not tainted tainted Sep 4 17:52:26 pc51332 kernel: EFLAGS: 00010206 (2.6.4-52-smp) Sep 4 17:52:26 pc51332 kernel: EIP is at jpegdecode+0xce5-0x1090 Sep 4 17:52:26 pc51332 kernel: eax: 0000320c ebx: 0000003c ecx: 00003200 edx: 00000065 Sep 4 17:52:26 pc51332 kernel: esi: f9b6f000 edi: 00000000 ebp: fa0129a0 esp: cdf97dec Sep 4 17:52:26 pc51332 kernel: ds: 007b es: 007b ss: 0068 Sep 4 17:52:26 pc51332 kernel: Process events-0 (pid: 6, threadinfo=cdf96000 task=cdffb280) Sep 4 17:52:26 pc51332 kernel: Stack: 00000400 0000001c 20000001 00000000 cdf97e38 db974f00 00000000 c03d4800 Sep 4 17:52:26 pc51332 kernel: 00000000 00000022 fffffffe ffffffef f9b6fa40 f9b6f640 fa0133a0 00000004 Sep 4 17:52:26 pc51332 kernel: 00000002 00000a00 c0384500 00000246 00000010 00000010 00000046 00000010 Sep 4 17:52:26 pc51332 kernel: splashprepare+304-912 splashprepare+0x130-0x390 splashprepare+0x130-0x390 Sep 4 17:52:26 pc51332 kernel: fbconswitch+41-496 fbconswitch+0x29-0x1f0 Sep 4 17:52:26 pc51332 kernel: redrawscreen+212-528 redrawscreen+0xd4-0x210 Sep 4 17:52:26 pc51332 kernel: completechangeconsole+43-208 completechangeconsole+0x2b-0xd0 completechangeconsole+0x2b-0xd0 Sep 4 17:52:26 pc51332 kernel: consolecallback+197-224 consolecallback+0xc5-0xe0 consolecallback+0xc5-0xe0 Sep 4 17:52:26 pc51332 kernel: workerthread+391-528 workerthread+0x187-0x210 Sep 4 17:52:26 pc51332 kernel: consolecallback+0-224 consolecallback+0x0-0xe0 Sep 4 17:52:26 pc51332 kernel: defaultwakefunction+0-16 defaultwakefunction+0x0-0x10 defaultwakefunction+0x0-0x10 Sep 4 17:52:26 pc51332 kernel: defaultwakefunction+0-16 defaultwakefunction+0x0-0x10 defaultwakefunction+0x0-0x10 Sep 4 17:52:26 pc51332 kernel: workerthread+0-528 workerthread+0x0-0x210 Sep 4 17:52:26 pc51332 kernel: kthread+212-280 kthread+0xd4-0x118 Sep 4 17:52:26 pc51332 kernel: kthread+0-280 kthread+0x0-0x118 Sep 4 17:52:26 pc51332 kernel: kernelthreadhelper+5-16 kernelthreadhelper+0x5-0x10 kernelthreadhelper+0x5-0x10 Sep 4 17:52:26 pc51332 kernel: Sep 4 17:52:26 pc51332 kernel: Code: 88 44 bd 00 89 c3 89 fa c1 fb 08 85 ff 88 5c bd 01 0f 88 e2 Sep 4 17:59:00 pc51332USR-SBIN-CRON15908: (root) CMD ( rm -fvar-spool-cron-lastrun-cron.hourly) Sep 4 18:05:46 pc51332 su: (to postgres) root ondev-pts-51 Sep 4 18:05:46 pc51332 su: pamunix2: session started for user postgres, service su Sep 4 18:05:50 pc51332 su: pamunix2: session finished for user postgres, service su Sep 4 18:09:36 pc51332 su: (to root) root on none ----------------------------------------------------------------------------------------------------- The kernel reacted with an "Oops". Never saw this before. Is this severe ? You see that the machine still worked on, i had to use the power switch. What i found out already: The kernel says Oops, if it finds something it does not understand really. He prints several registers from the cpu, the process which is causing the problem and the actual system calls to the syslog. So, in my case, events-0 is causing the trouble. Events is a kernel thread, which can't be end, even with -9. Events, like any other kernel thread, has to finish himself. But it does not. Anybody knows why ? I think i still have the kernel from the installation. Do you think i need a kernel patch ? Any other idea ? Thank you for any tip. Bernd. btw: i tested ram and harddisk, everyting o.k.