On Sunday 04 April 2010 01:52:17 Adam wrote: > > Probably neither. Can you Ctrl+F12 to see what the logs are > > saying? I've been getting kernel Oops! on shutdown on one > > machine of mine with the 2.6.31-gentoo-r10 kernel. Might be > > similar > > Ok, i found this, which is mentioning fglrx, and the problem may have > started when i changed driver versions. > > So is it possible for an X driver to cause filesystem issues? I would > have assumed not. > > > > Apr 4 10:38:08 sphinx shutdown[5768]: shutting down for system reboot > Apr 4 10:38:09 sphinx init: Switching to runlevel: 6 > Apr 4 10:38:09 sphinx gnome-session[5585]: WARNING: Detected that > screensaver has left the bus > Apr 4 10:38:09 sphinx gnome-keyring-daemon[5614]: dbus failure > unregistering from session: Connection is closed > Apr 4 10:38:09 sphinx su[5753]: pam_unix(su:session): session closed > for user root > Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1d.1: release dev 2 > ep81-INT, period 8, phase 4, 93 us > Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1a.0: release dev 4 > ep81-INT, period 8, phase 4, 14 us > Apr 4 10:38:09 sphinx kernel: __ratelimit: 20 callbacks suppressed > Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in > preemptible [00000000] code: X/5275 > Apr 4 10:38:09 sphinx kernel: caller is KAS_GetExecutionLevel+0xd/0x120 > [fglrx] > Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P > 2.6.31-gentoo-r6 #4 > Apr 4 10:38:09 sphinx kernel: Call Trace: > Apr 4 10:38:09 sphinx kernel: [<ffffffff811bc329>] ? > debug_smp_processor_id+0xd9/0xe0 > Apr 4 10:38:09 sphinx kernel: [<ffffffffa022514d>] ? > KAS_GetExecutionLevel+0xd/0x120 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02403e9>] ? > MCIL_GetExecutionLevel+0x39/0x80 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02ecacb>] ? > CallbackQueueAccess+0x2b/0x2a0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e49a0>] ? > UnRegisterIRQClient_Worker+0x0/0xe0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa023ff42>] ? > MCIL_bMiniportCapEnabled+0x82/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e4323>] ? > UnRegisterIRQClient+0x83/0xe0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e163e>] ? > IRQMGR_IRQSourceSupported+0x7e/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e1791>] ? > IRQMGR_Access+0x131/0x190 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa0256e83>] ? > fireglAsyncioUnregisterIntMsgHandlers+0x2c3/0x3c0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa0283794>] ? > asyncIONotifyMsg+0x234/0x3e0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa02560b9>] ? > firegl_asyncio_write+0x189/0x250 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffffa0229048>] ? > ip_firegl_write+0x58/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [<ffffffff810abecb>] ? vfs_write+0xcb/0x180 > Apr 4 10:38:09 sphinx kernel: [<ffffffff810ac083>] ? sys_write+0x53/0xa0 > Apr 4 10:38:09 sphinx kernel: [<ffffffff8100b4c2>] ? > system_call_fastpath+0x16/0x1b > Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in > preemptible [00000000] code: X/5275 > Apr 4 10:38:09 sphinx kernel: caller is > KCL_SPINLOCK_STATIC_Grab+0x25/0x110 [fglrx] > Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P > 2.6.31-gentoo-r6 #4 > Apr 4 10:38:09 sphinx kernel: Call Trace: > Apr 4 10:38:09 sphinx kernel: [<ffffffff811bc329>] ? > debug_smp_processor_id+0xd9/0xe0
It could be that this kernel does not play well with fglrx? I would unmask the next kernel up the tree and try that out. This particular kernel version you are running had a few bugs hanging around, which may affect your problem. PS. My machine that keeps crashing on shutdown doesn't always crash at exactly the same point - but it is well after X has been stopped and invariably after the fs has been unmounted. PPS. Clutching at straws, but just for testing purposes you may want to boot with no X, just on a console and try shuting down from there? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
