Post, Mark K wrote: > illegal operation: 0001 [#1] > CPU: 0 Not tainted > Process init (pid: 1, task: 00000000007c1748, ksp: 00000000007c3ca0) > Krnl PSW : 0704200180000000 0000000000000002 (0x2) > Krnl GPRS: 0000000000000001 0000000000000000 0000000003cdb2a8 > 0000000000000085 > 00000000007c3cf0 0000000000000001 00000000010c6160 > 0000000000000001 > 0000000003cdb3c8 00000000000a3898 0000000003cdb3c8 > 0000000000000000 > 0000000000000085 0000000000446888 000000000025970c > 00000000007c3b38 > Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Call Trace: > ([<0000000000259434>] mpage_writepages+0x23c/0xb40) > [<00000000001b07ca>] do_writepages+0x5a/0x74 > [<0000000000256a8c>] sync_inodes+0x540/0x1204 > [<00000000001fdad4>] sys_sync+0x30/0x84 > [<000000000010f774>] sysc_noemu+0x10/0x16 > [<00000200001464aa>] 0x200001464aa > > <0>Kernel panic - not syncing: Attempted to kill init! > HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 > 0014259E *Ouch*. In mpage_writepages()? This is pretty much in the very core kernel near I/O page cache and file system, not somewhere near networking. Both CTC device driver and all user space components like Yast avert suspicion as far as I can tell.
Is there another message right before "illegal operation: 0001 [#1]"? Probably one that says "kernel BUG" or "Ooops" or similar? Usually kernel traps use illegal opcodes to crash the thing on purpose, but they are supposed to print a useful message before that. cheers, Carsten ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
