Andrew, I've got this trace on an AMD64 machine at startup: Unable to handle kernel paging request at 0000000000100288 RIP: {do_task_stat+980} PML4 1a42f067 PGD 13fad067 PMD 0 Oops: 0000 [1] CPU 0 Modules linked in: usbserial parport_pc lp parport joydev sg st sd_mod sr_mod scsi_mod ohci1394 ieee1394 usbhid yentd Pid: 11522, comm: pidof Not tainted 2.6.9-rc1-mm4 RIP: 0010:[] {do_task_stat+980} RSP: 0018:00000100112e7cc8 EFLAGS: 00010283 RAX: 00000000000fff68 RBX: 000001000eb909d0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00000000000fff68 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 000001001ff0f140 R11: 0000000000000065 R12: 0000000000000001 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000 FS: 0000002a9588d6e0(0000) GS:ffffffff805a72c0(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000100288 CR3: 0000000000101000 CR4: 00000000000006e0 Process pidof (pid: 11522, threadinfo 00000100112e6000, task 0000010013464230) Stack: 0000000000000001 0000000000000246 0000000000000001 0000000000100000 00000100112e7d88 0006000000000006 0000000000000246 00000100112e7e28 0000000000000001 0000000200000010 Call Trace:{avc_has_perm+90} {avc_has_perm+90} {inode_has_perm+134} {inode_has_perm+134} {proc_info_read+107} {vfs_read+228} {sys_read+83} {system_call+126} Code: 48 8b b7 20 03 00 00 48 01 b4 24 38 01 00 00 4c 03 bf 28 03 RIP {do_task_stat+980} RSP <00000100112e7cc8> CR2: 0000000000100288 It is not reproducible, but looks suspicious to me. Attached are the .config and the output of dmesg. Greets, RJW -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"