| 1 |
On Tuesday 07 July 2009, walt wrote: |
| 2 |
> On 07/06/2009 04:23 PM, Mick wrote: |
| 3 |
> > On Monday 06 July 2009, walt wrote: |
| 4 |
> >> On 07/06/2009 04:39 AM, Mick wrote: |
| 5 |
> >>> On Monday 06 July 2009, walt wrote: |
| 6 |
> >>>> On 07/06/2009 03:29 AM, Mick wrote: |
| 7 |
> >>>>> I cleared out some xorg related packages at some point because my |
| 8 |
> >>>>> machine will not shutdown without a kernel oops when it is trying to |
| 9 |
> >>>>> unload the radeon driver. |
| 10 |
> >>>> |
| 11 |
> >>>> Hm. There is no reason to unload any driver or module just to shut |
| 12 |
> >>>> down. Are you sure that's the reason for the oops? |
| 13 |
> >>> |
| 14 |
> >>> Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there |
| 15 |
> >>> there are no oops with the usual messages about |
| 16 |
> >>> "vblank_disable_fn+0x79/0xd0 [drm]" and "EIP: [<e0cc14fe>] |
| 17 |
> >>> radeon_get_vblank_counter+0x7e/0xd0 [radeon]". |
| 18 |
> >> |
| 19 |
> >> Wait, when exactly do you see the 'usual' oops messages? |
| 20 |
> > |
| 21 |
> > When I try to shutdown the machine they come up on the console - |
| 22 |
> > currently running 2.6.29-gentoo-r5. Typically, the oops occurs after the |
| 23 |
> > wireless driver and alsasound modules are unloaded and occasionally after |
| 24 |
> > syslog-ng is stopped... |
| 25 |
> |
| 26 |
> Okay, I know about the alsa modules stuff, but not the wireless. The alsa |
| 27 |
> modules should *not* be unloaded on shutdown because there is no reason to |
| 28 |
> do it and it causes problems if you try. (And I'm guessing that wireless is |
| 29 |
> the same.) |
| 30 |
> |
| 31 |
> Look at /etc/conf.d/alsasound. You should have two lines there as follows: |
| 32 |
> |
| 33 |
> # Deprecated options: |
| 34 |
> # Upstream feels, and we wholehartedly agree, that this was a silly idea |
| 35 |
> UNLOAD_ON_STOP="no" |
| 36 |
> KILLPROC_ON_STOP="no" |
| 37 |
> |
| 38 |
> When I'm more awake I'll take a look at wireless. |
| 39 |
|
| 40 |
Thanks walt, but this problem is *not* related either to the usual alsasound |
| 41 |
culprit, or wireless. I have tried it with and without wireless and with and |
| 42 |
without unloading alsasound. All the errors are about radeon, nothing to do |
| 43 |
with anything else. |
| 44 |
|
| 45 |
As a side note, the new xorg server has caused 3d rendering (when I still had |
| 46 |
installed glxinfo and could compare speeds) to run like a dog. Until the |
| 47 |
2.6.29 versions I never had kernel oops, or at least not without compiling |
| 48 |
something really inappropriate in the kernel. |
| 49 |
-- |
| 50 |
Regards, |
| 51 |
Mick |
Archives