1 |
On Sunday 04 April 2010 01:52:17 Adam wrote: |
2 |
> > Probably neither. Can you Ctrl+F12 to see what the logs are |
3 |
> > saying? I've been getting kernel Oops! on shutdown on one |
4 |
> > machine of mine with the 2.6.31-gentoo-r10 kernel. Might be |
5 |
> > similar |
6 |
> |
7 |
> Ok, i found this, which is mentioning fglrx, and the problem may have |
8 |
> started when i changed driver versions. |
9 |
> |
10 |
> So is it possible for an X driver to cause filesystem issues? I would |
11 |
> have assumed not. |
12 |
> |
13 |
> |
14 |
> |
15 |
> Apr 4 10:38:08 sphinx shutdown[5768]: shutting down for system reboot |
16 |
> Apr 4 10:38:09 sphinx init: Switching to runlevel: 6 |
17 |
> Apr 4 10:38:09 sphinx gnome-session[5585]: WARNING: Detected that |
18 |
> screensaver has left the bus |
19 |
> Apr 4 10:38:09 sphinx gnome-keyring-daemon[5614]: dbus failure |
20 |
> unregistering from session: Connection is closed |
21 |
> Apr 4 10:38:09 sphinx su[5753]: pam_unix(su:session): session closed |
22 |
> for user root |
23 |
> Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1d.1: release dev 2 |
24 |
> ep81-INT, period 8, phase 4, 93 us |
25 |
> Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1a.0: release dev 4 |
26 |
> ep81-INT, period 8, phase 4, 14 us |
27 |
> Apr 4 10:38:09 sphinx kernel: __ratelimit: 20 callbacks suppressed |
28 |
> Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in |
29 |
> preemptible [00000000] code: X/5275 |
30 |
> Apr 4 10:38:09 sphinx kernel: caller is KAS_GetExecutionLevel+0xd/0x120 |
31 |
> [fglrx] |
32 |
> Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P |
33 |
> 2.6.31-gentoo-r6 #4 |
34 |
> Apr 4 10:38:09 sphinx kernel: Call Trace: |
35 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffff811bc329>] ? |
36 |
> debug_smp_processor_id+0xd9/0xe0 |
37 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa022514d>] ? |
38 |
> KAS_GetExecutionLevel+0xd/0x120 [fglrx] |
39 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02403e9>] ? |
40 |
> MCIL_GetExecutionLevel+0x39/0x80 [fglrx] |
41 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02ecacb>] ? |
42 |
> CallbackQueueAccess+0x2b/0x2a0 [fglrx] |
43 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e49a0>] ? |
44 |
> UnRegisterIRQClient_Worker+0x0/0xe0 [fglrx] |
45 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa023ff42>] ? |
46 |
> MCIL_bMiniportCapEnabled+0x82/0xa0 [fglrx] |
47 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e4323>] ? |
48 |
> UnRegisterIRQClient+0x83/0xe0 [fglrx] |
49 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e163e>] ? |
50 |
> IRQMGR_IRQSourceSupported+0x7e/0xa0 [fglrx] |
51 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02e1791>] ? |
52 |
> IRQMGR_Access+0x131/0x190 [fglrx] |
53 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa0256e83>] ? |
54 |
> fireglAsyncioUnregisterIntMsgHandlers+0x2c3/0x3c0 [fglrx] |
55 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa0283794>] ? |
56 |
> asyncIONotifyMsg+0x234/0x3e0 [fglrx] |
57 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa02560b9>] ? |
58 |
> firegl_asyncio_write+0x189/0x250 [fglrx] |
59 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffffa0229048>] ? |
60 |
> ip_firegl_write+0x58/0xa0 [fglrx] |
61 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffff810abecb>] ? vfs_write+0xcb/0x180 |
62 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffff810ac083>] ? sys_write+0x53/0xa0 |
63 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffff8100b4c2>] ? |
64 |
> system_call_fastpath+0x16/0x1b |
65 |
> Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in |
66 |
> preemptible [00000000] code: X/5275 |
67 |
> Apr 4 10:38:09 sphinx kernel: caller is |
68 |
> KCL_SPINLOCK_STATIC_Grab+0x25/0x110 [fglrx] |
69 |
> Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P |
70 |
> 2.6.31-gentoo-r6 #4 |
71 |
> Apr 4 10:38:09 sphinx kernel: Call Trace: |
72 |
> Apr 4 10:38:09 sphinx kernel: [<ffffffff811bc329>] ? |
73 |
> debug_smp_processor_id+0xd9/0xe0 |
74 |
|
75 |
It could be that this kernel does not play well with fglrx? I would unmask |
76 |
the next kernel up the tree and try that out. This particular kernel version |
77 |
you are running had a few bugs hanging around, which may affect your problem. |
78 |
|
79 |
PS. My machine that keeps crashing on shutdown doesn't always crash at |
80 |
exactly the same point - but it is well after X has been stopped and |
81 |
invariably after the fs has been unmounted. |
82 |
|
83 |
PPS. Clutching at straws, but just for testing purposes you may want to boot |
84 |
with no X, just on a console and try shuting down from there? |
85 |
|
86 |
-- |
87 |
Regards, |
88 |
Mick |