| 1 |
On 07/06/2009 04:23 PM, Mick wrote: |
| 2 |
> On Monday 06 July 2009, walt wrote: |
| 3 |
>> On 07/06/2009 04:39 AM, Mick wrote: |
| 4 |
>>> On Monday 06 July 2009, walt wrote: |
| 5 |
>>>> On 07/06/2009 03:29 AM, Mick wrote: |
| 6 |
>>>>> I cleared out some xorg related packages at some point because my |
| 7 |
>>>>> machine will not shutdown without a kernel oops when it is trying to |
| 8 |
>>>>> unload the radeon driver. |
| 9 |
>>>> |
| 10 |
>>>> Hm. There is no reason to unload any driver or module just to shut down. |
| 11 |
>>>> Are you sure that's the reason for the oops? |
| 12 |
>>> |
| 13 |
>>> Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there |
| 14 |
>>> there are no oops with the usual messages about |
| 15 |
>>> "vblank_disable_fn+0x79/0xd0 [drm]" and "EIP: [<e0cc14fe>] |
| 16 |
>>> radeon_get_vblank_counter+0x7e/0xd0 [radeon]". |
| 17 |
>> |
| 18 |
>> Wait, when exactly do you see the 'usual' oops messages? |
| 19 |
> |
| 20 |
> When I try to shutdown the machine they come up on the console - currently |
| 21 |
> running 2.6.29-gentoo-r5. Typically, the oops occurs after the wireless |
| 22 |
> driver and alsasound modules are unloaded and occasionally after syslog-ng is |
| 23 |
> stopped... |
| 24 |
|
| 25 |
Okay, I know about the alsa modules stuff, but not the wireless. The alsa |
| 26 |
modules should *not* be unloaded on shutdown because there is no reason to |
| 27 |
do it and it causes problems if you try. (And I'm guessing that wireless is |
| 28 |
the same.) |
| 29 |
|
| 30 |
Look at /etc/conf.d/alsasound. You should have two lines there as follows: |
| 31 |
|
| 32 |
# Deprecated options: |
| 33 |
# Upstream feels, and we wholehartedly agree, that this was a silly idea |
| 34 |
UNLOAD_ON_STOP="no" |
| 35 |
KILLPROC_ON_STOP="no" |
| 36 |
|
| 37 |
When I'm more awake I'll take a look at wireless. |
Archives