Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 174698 - System hangs during boot after update
Summary: System hangs during boot after update
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-15 17:51 UTC by Andreas Dehmel
Modified: 2007-04-17 19:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Description of the boot process (boot-desc.txt,649 bytes, text/plain)
2007-04-15 17:53 UTC, Andreas Dehmel
Details
Output of rc-status --all (after login and starting missing services) (rc-status-desc.txt,7.23 KB, text/plain)
2007-04-15 17:54 UTC, Andreas Dehmel
Details
Directory listing of /etc/init.d (init.d-dir.txt,3.33 KB, text/plain)
2007-04-15 17:56 UTC, Andreas Dehmel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Dehmel 2007-04-15 17:51:32 UTC
Several weeks ago, my Gentoo system suddenly started hanging during boot after an update (unfortunately I don't know the exact date...). I had hoped to fix it myself somehow, but since I can find no clues whatsoever in the log files or the console output, I didn't get anywhere. I can CTRL-C at the problematic point, which gives me am interrupt in net.lo and if I then enter interactive boot mode and skip net.lo/net/netmount/portmap, but boot net.eth0, I can boot the system successfully and once I can log in as root I can also start these services without problems (trying to boot net.lo or netmount causes a hangup that can't be interrupted by CTRL-C anymore and requires CTRL-ALT-DEL). Once properly booted, the system is totally stable, including hour-long compile marathons or gaming sessions; fsck didn't show anything either. log files don't show anything, I also tried upping the debugging level in /etc/conf.d/rc, but didn't get anything usable either. The problem is probably caused by something I did (although I didn't do much except for updating the system, including revdep-rebuild), but the fact that I get no feedback from the system _what_ the problem might be is something I definitely consider a system bug. I hope someone can give me at least some hints where to look (I do _NOT_ intend to reinstall). I'll attach a description of the boot sequence, rc-status and a listing of my /etc/init.d directory separately. ATM I wonder whether net and net.lo in /etc/init.d being almost identical files (diff is 4 lines) may have something to do with it, but don't want to start deleting/renaming files without being sure.


Reproducible: Always

Steps to Reproduce:




Dead standard desktop system, nothing even slightly exotic. Standard ethernet with fixed IP only, no WLAN or PCMCIA. Kernel is 2.6.18-gentoo-r6.
Comment 1 Andreas Dehmel 2007-04-15 17:53:07 UTC
Created attachment 116320 [details]
Description of the boot process

After interactive boot starts, I prefixed each line with the choice I make to get the system up and running.
Comment 2 Andreas Dehmel 2007-04-15 17:54:15 UTC
Created attachment 116322 [details]
Output of rc-status --all (after login and starting missing services)
Comment 3 Andreas Dehmel 2007-04-15 17:56:51 UTC
Created attachment 116324 [details]
Directory listing of /etc/init.d

I think net and net.lo shouldn't be two separate files. I don't think the difference between the two causes the hangup, though:

906a907,908
>       elif [[ -n ${metric} ]] ; then
>               eval "metric_${IFVAR}=\"${metric}\""
Comment 4 Roy Marples (RETIRED) gentoo-dev 2007-04-16 14:27:10 UTC
We don't install /etc/init.d/net.

Try deleting it.
Comment 5 Andreas Dehmel 2007-04-17 19:37:17 UTC
Deleting it actually solved my problem :-) !!! System now boots fine once again, thanks a lot.
One more question for potential future problems, though (I'm quite new to Gentoo, so I may have overloocked something): is there some sort of reference for the files in /etc, along the lines of "if you have an up-to-date system it should look something like this, you should have these files and you shouldn't have these"? Doing this for everything would be way too much work, of course, but for something like init.d it should be doable. Also, is there a reference which rc-level the scripts should be run at? Some are apparently quite flexible, but I don't think everything'll work in either boot or default...
Anyway, thanks again, this is a real relief.