| View previous topic :: View next topic |
| Author |
Message |
altstadt
n00b
Joined: 04 Nov 2003
Posts: 16
|
 Posted: Fri Oct 29, 2004 1:18 am Post subject: shutdown problems with lo - actually devfsd, ALSA, or rmmod |
 |
|
I have two similar systems running with gentoo-sources-2.4.26-r9, but only one of them has the peculiar problem of being unable to shutdown or reboot.
No matter whether I run shutdown, halt, or reboot, one of the systems will always stop after printing the console message:
| Code: | | Bringing lo down... |
The previous driver to shut down is eth0, and it stops okay. I always have to poke the reset button on this system, or it will quite happily sit in this state for hours. This is 100% repeatable on the one system.
What is it waiting for and how can I fix it? It's not like there is any hardware in a bad state that needs to clear before the loopback driver can shut down.
Last edited by altstadt on Fri Nov 12, 2004 11:14 pm; edited 2 times in total |
|
| Back to top |
|
 |
altstadt
n00b
Joined: 04 Nov 2003
Posts: 16
|
| Posted: Fri Nov 05, 2004 5:39 pm Post subject: |
|
|
| Anyone? |
|
| Back to top |
|
|
altstadt
n00b
Joined: 04 Nov 2003
Posts: 16
|
| Posted: Fri Nov 12, 2004 11:13 pm Post subject: |
|
|
After spending a lot more time on rebooting the past few days (I was caught by the recent hotplug upgrade quagmire), I was able to look at this in far more depth.
It turns out that what was actually happening was that the lo line was the last thing printed after some other problem much earlier in the shutdown sequence. The loopback device had nothing to do with the problem, because if I manually shut down lo, then the last thing printed was the eth0 shutdown. The devfsd task was crashing and there was an error mixed in talking about a sound device going missing.
I re-emerged devfsd and fixed up its config files.
After a couple of reboots, the shutdown was now halting in ALSA lib conf.c with an additional crash in rmmod.
I re-emerged the following packages, one at a time, watching for ewarns and updating all the config files after each package:
emu10k1
alsa-lib
alsa-oss
alsa-driver
alsa-headers
alsa-tools
alsa-utils
module-init-tools
Along the way I found a few config files that looked like they had never been updated from ._cfg* files the last time the packages were built.
Now everything is working as it should. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
