Summary: | sys-apps/baselayout-1.12.4-r2: boot issues w/ USB/coldplug | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | uberlord |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | kernel config |
Description
Toralf Förster
2006-08-12 06:24:46 UTC
With the following setting the "old" working behaviour is restored: tfoerste@n22 ~ $ grep -e ^RC_COLD -e ^RC_HOT -e ^RC_PL /etc/conf.d/rc RC_HOTPLUG="yes" RC_COLDPLUG="no" RC_PLUG_SERVICES="!net.eth0" During boot process I can see the message that net.eth0 is starting, after 6 seconds it DHCPCD times out and a static address is assigned to that adapter. After that the normal boot process continues (starting dnsmasq, apache2, snort, ....) so what sort of kernel configuration do you have ? are those things built as kernel modules ? Created attachment 94113 [details]
kernel config
Right, built as much as possible as modules.
I attached my kernel config here.
Here are my init levels:
tfoerste@n22 ~ $ rc-status boot
Runlevel: boot
modules [ started ]
checkroot [ started ]
rmnologin [ started ]
consolefont [ started ]
checkfs [ started ]
bootmisc [ started ]
hostname [ started ]
localmount [ started ]
net.lo [ started ]
coldplug [ started ]
serial [ started ]
keymaps [ started ]
urandom [ started ]
clock [ started ]
tfoerste@n22 ~ $ rc-status default
Runlevel: default
sshd [ started ]
local [ started ]
net.eth0 [ started ]
xdm [ started ]
netmount [ stopped ]
vixie-cron [ started ]
syslog-ng [ started ]
mysql [ started ]
acpid [ started ]
smartd [ started ]
cupsd [ started ]
apache2 [ started ]
klive [ started ]
alsasound [ started ]
dnetc [ started ]
kmyfirewall [ started ]
sendmail [ started ]
ntpd [ stopped ]
clamd [ started ]
dnsmasq [ started ]
lisa [ stopped ]
snort [ started ]
so let me see ... you have devices hooked up at boot, you have coldplugging turned off, you have your kernel built as modules, and you're wondering why things arent working ? the point of coldplugging is to detect all the devices you had plugged in already and load the modules for them (In reply to comment #4) > so let me see ... you have devices hooked up at boot, you have coldplugging > turned off, you have your kernel built as modules, and you're wondering why > things arent working ? With the old baselayout I had RC_COLDPLUG="no" without any problems, that's why I used the same value for the new one. > the point of coldplugging is to detect all the devices you had plugged in > already and load the modules for them Right, I've turned it on now. My actual problem is to reproduce the behaviour that the boot process doesn't continue after cupsd. (Un)fortunatly it's currently working (I'm not happy about an issue which cannot be reproduced. I'll close this bug until I can reproduce the hang on the boot process. |