Load Modules Takes Forever

cameron122000 · 2008-12-29 21:08:17

Whenever my computer boots, it takes at least 30 seconds to a minute until the Load Modules section of the bootup finishes. It shows [BUSY] for the whole time, and generally freezes up the whole boot process. So I looked at my messages.log and this is what I see:

Dec 29 13:03:33 starcommand load-modules.sh: 'dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd05/13/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'pci:v00008086d0000244Esv00000000sd00000000bc06sc04i01' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:INT0800:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0501:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0700:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0303:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0B00:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'platform:parport_pc' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'platform:parport_pc' is not a valid module or alias name
Dec 29 13:03:33 starcommand load-modules.sh: 'platform:parport_pc' is not a valid module or alias name

Can anybody explain to me why this is happening now, and hasn't happened before? This just started to happen, and all I just reinstalled Arch yesterday.

string · 2008-12-29 21:16:45

Hmm.. what does /etc/udev/rules.d/81-arch.rules look like? I remember upgrading udev yesterday, sounds like a `weird` coincidence.

Last edited by string (2008-12-29 21:17:18)

cameron122000 · 2008-12-29 21:25:34

It's long, sorry.

#####################################
###### Hotplug rules - begin
# Only additional modules, 
# which are not detectable,
# are loaded here!
#####################################
# check if the device has already been claimed by a driver
ACTION!="add", GOTO="drivers_end"

# SOUND addon modules
SUBSYSTEM=="sound", RUN+="/lib/udev/load-modules.sh snd-pcm-oss"
SUBSYSTEM=="sound", RUN+="/lib/udev/load-modules.sh snd-seq-oss"

#PNP addon modules
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="PNP0800", RUN+="/lib/udev/load-modules.sh pcspkr"
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="*PNP0510*", RUN+="/lib/udev/load-modules.sh irtty-sir"
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="*PNP0511*", RUN+="/lib/udev/load-modules.sh irtty-sir"
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="PNPb02f", RUN+="/lib/udev/load-modules.sh analog"
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="PNP0501", RUN+="/lib/udev/load-modules.sh ppp-generic"

# PARPORT addon modules
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="PNP040*", RUN+="/lib/udev/load-modules.sh lp"
SUBSYSTEM=="pnp", ENV{MODALIAS}!="?*", ATTRS{id}=="PNP040*", RUN+="/lib/udev/load-modules.sh ppdev"

# fix ide cdrom detection on old proliant servers
SUBSYSTEM=="pci", ENV{MODALIAS}=="pci:v00000E11d00000001sv00000000sd00000000bc06sc02i00", RUN+="/lib/udev/load-modules.sh ide-generic"

LABEL="drivers_end"
#####################################
##### Hotplug rules - end
#####################################

#####################################
###### CD/DVD symlinks - begin
#####################################
ACTION=="add", SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", IMPORT="cdrom_id --export $tempnode"
ACTION=="add", SUBSYSTEMS=="scsi",    KERNEL=="sr[0-9]*", IMPORT="cdrom_id --export $tempnode"
ACTION=="add", SUBSYSTEMS=="scsi",    KERNEL=="scd[a-z]", IMPORT="cdrom_id --export $tempnode"
ENV{ID_CDROM}=="?*", SYMLINK+="cd/cdrom-%b"
ENV{ID_CDROM_CD_RW}=="?*", SYMLINK+="cd/cdrw-%b"
ENV{ID_CDROM_DVD}=="?*", SYMLINK+="cd/dvd-%b"
ENV{ID_CDROM_DVD_R}=="?*", SYMLINK+="cd/dvd-%b"
ACTION=="add", SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTR{removable}=="1", ATTRS{media}=="cdrom*", RUN+="cdsymlinks.sh"
ACTION=="add", SUBSYSTEMS=="scsi", KERNEL=="sr[0-9]*", ATTRS{type}=="5", RUN+="cdsymlinks.sh"
ACTION=="add", SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="5", RUN+="cdsymlinks.sh"
ACTION=="remove", SUBSYSTEMS=="block", KERNEL=="hd[a-z]", RUN+="cdsymlinks.sh"
ACTION=="remove", SUBSYSTEMS=="block", KERNEL=="sr[0-9]*", RUN+="cdsymlinks.sh"
ACTION=="remove", SUBSYSTEMS=="block", KERNEL=="sg[0-9]*", RUN+="cdsymlinks.sh"
#####################################
###### CD/DVD symlinks - end
#####################################

#####################################
# Additional Archlinux
# Permissions and Symlinks - begin
#####################################
# fix /dev/root symlink
SUBSYSTEM=="block", RUN+="root-link.sh"

# permissions for IDE CD devices
SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTR{removable}=="1", ATTRS{media}=="cdrom*", GROUP="optical"

# permissions for SCSI CD devices
SUBSYSTEMS=="scsi", KERNEL=="sr[0-9]*", ATTRS{type}=="5", SYMLINK+="scd%n", GROUP="optical"
SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="5", GROUP="optical"

# permissions for removable devices like cardreaders or sticks
KERNEL=="sd*", ATTRS{scsi_level}=="0", ATTRS{type}=="0", GROUP="storage"

# permissions for firewire external drives
KERNEL=="sd*", ATTRS{scsi_level}=="5", GROUP="storage"

# permissions for usb to scsi external adapters
KERNEL=="sd*", ATTRS{scsi_level}=="3", ATTRS{type}=="7", GROUP="storage"

# permissions for ide storage like pcmcia card readers
ACTION!="add", GOTO="pcmcia_end"
SUBSYSTEM!="block", GOTO="pcmcia_end"
KERNEL=="hd*[!0-9]", IMPORT{program}="ata_id --export $tempnode"
KERNEL=="hd*", IMPORT{parent}=="ID_*"
KERNEL=="hd*", ENV{ID_TYPE}=="generic", GROUP="storage"
LABEL="pcmcia_end"

# permissions for SCSI scanners
SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="6", GROUP="scanner"

# md block devices
KERNEL=="md[0-9]*", NAME="md%n", SYMLINK+="md/%n"

# video devices
SUBSYSTEM=="video4linux", GROUP="video"
### xorg resets those permissions, adjust your xorg.conf!
KERNEL=="nvidia*",    GROUP="video"
KERNEL=="3dfx*",    GROUP="video"

# i2c devices
KERNEL=="i2c-[0-9]*", NAME="i2c/%n", SYMLINK+="%k"

# loop devices
KERNEL=="loop[0-9]*", NAME="loop/%n", SYMLINK+="%k"

# misc
KERNEL=="nvram",   NAME="misc/%k", SYMLINK+="%k", GROUP="kmem", MODE="0640"
KERNEL=="psaux",   NAME="misc/%k", SYMLINK+="%k"
KERNEL=="uinput",  NAME="misc/%k", SYMLINK+="%k"
KERNEL=="sgi_fetchop",   MODE="0666"
KERNEL=="sonypi",        MODE="0666"
KERNEL=="inotify",    NAME="misc/%k", SYMLINK+="%k", MODE="0666"

# sound devices
# alsa devices
SUBSYSTEM=="sound",    GROUP="audio"
# oss devices
KERNEL=="audio*",     NAME="sound/%k", SYMLINK+="%k"
KERNEL=="dmmidi*",    NAME="sound/%k", SYMLINK+="%k"
KERNEL=="admmidi*",   NAME="sound/%k", SYMLINK+="%k"
KERNEL=="dsp*",       NAME="sound/%k", SYMLINK+="%k"
KERNEL=="adsp*",      NAME="sound/%k", SYMLINK+="%k"
KERNEL=="midi*",      NAME="sound/%k", SYMLINK+="%k"
KERNEL=="amidi*",     NAME="sound/%k", SYMLINK+="%k"
KERNEL=="mixer*",     NAME="sound/%k", SYMLINK+="%k"
KERNEL=="sequencer*", NAME="sound/%k", SYMLINK+="%k"

# USB devices
KERNEL=="hiddev*",    NAME="usb/%k"
KERNEL=="legousbtower*",    NAME="usb/%k", MODE="0666"
KERNEL=="dabusb*",    NAME="usb/%k"

# netlink devices
KERNEL=="route",        NAME="netlink/%k"
KERNEL=="skip",        NAME="netlink/%k"
KERNEL=="usersock",    NAME="netlink/%k"
KERNEL=="fwmonitor",    NAME="netlink/%k"
KERNEL=="tcpdiag",    NAME="netlink/%k"
KERNEL=="nflog",        NAME="netlink/%k"
KERNEL=="xfrm",        NAME="netlink/%k"
KERNEL=="arpd",        NAME="netlink/%k"
KERNEL=="route6",    NAME="netlink/%k"
KERNEL=="ip6_fw",    NAME="netlink/%k"
KERNEL=="dnrtmsg",    NAME="netlink/%k"
### ! disabled seems to break device creation !
# KERNEL=="tap*",        NAME="netlink/%k"

# IEEE1394 (firewire) devices
KERNEL=="raw1394", NAME="%k", GROUP="video"

# kbd devices
KERNEL=="kbd",        MODE="0664"

#######################################
# Permissions and Symlinks - end
#######################################

string · 2008-12-29 21:40:32

cameron122000 wrote:

It's long, sorry.

If I had a nickle for.. anyway.. seems like the problem is somewhere else. I hate to be the kind of guy who takes shots in the dark, but just to make sure, could you post /etc/rc.conf ?

cameron122000 · 2008-12-29 21:52:37

string wrote:

cameron122000 wrote:
It's long, sorry.
If I had a nickle for.. anyway.. seems like the problem is somewhere else. I hate to be the kind of guy who takes shots in the dark, but just to make sure, could you post /etc/rc.conf ?

Yeah after I posted that I knew somebody was going to say "That's what she said." Here's my /etc/rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(r8169 usblp slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !snd_pcsp)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="starcommand"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@syslog-ng @hal @network @netfs @crond @alsa @ntpd @cups slim)

cameron122000 · 2008-12-30 03:32:47

Anybody have any other ideas on what could be causing the problem? I've been doing some poking around and the load-modules.sh script is located in the UDev folder. It seems like others have also had a similar problem, but an answer was never found, or the threads just died.

grndrush · 2009-01-08 23:42:57

I'm experiencing the exact same 'problem'(?). I noticed after the last udev update the time spend in udev load at boot jumped from ~ 2.8 secs to 5.2 secs. I've noticed no other (apparent, to date) effects.

gav616 · 2009-03-17 18:29:11

im getting the same errors from 'load-modules.sh'

i noticed today after a reboot. (using testing repo)

if someone could know the package that i need to downgrade please?

Last edited by gav616 (2009-03-17 18:32:17)

gav616 · 2009-03-17 19:02:08

i downgrading 'initscripts' from 2009.03-2 to 2009.03-1 and its fixed the errors.

haxit · 2009-03-17 19:06:42

If anyone needs this, I will upload it temporarily to my server and you can downgrade. i686 only.
http://web.ncf.ca/ey723/initscripts-200 … pkg.tar.gz

takedown · 2009-03-18 14:31:08

same problem here

djgera · 2009-03-18 16:21:36

Yes, the messages "load-modules.sh: 'xyz' is not a valid module or alias name" now appears because the new initscripts, fixes a problem in minilogd[#1], before this fix, the logger command, that is used on load-modules.sh don't work (and don't work other messages logs from bootup)

This messages will always appears if you execute "udevadm trigger" when syslog-ng is loaded. (both on old initscripts or in the new).

The problem is un load-modules.sh parsing from udev

[#1] http://bugs.archlinux.org/task/13722

djgera · 2009-03-18 16:35:26

I created a bugreport here http://bugs.archlinux.org/task/13852

djgera · 2009-03-18 17:30:46

The correct title maybe: "udev trigger a event with module alias that are inexistent in modules.alias from kernel"

so this isn't a bug in load-modules.sh, but the boot process is now slow because logger now works, and logger/minilogd takes some time.

maybe a blacklist the module alias that cause this warning

djgera · 2009-03-18 22:39:29

Hi,

Users that experiment the slowness at udev startup, can do some test? It's simple

1) Install the packages that have the slowness problem.
2) Edit the file /lib/udev/load-modules.sh and change in one line LOGGER="/usr/bin/logger" with LOGGER="/bin/true"
3) Try if the slowness dissapears.
4) Please post it here the results (with what packages install for test it)

Thanks

Last edited by djgera (2009-03-18 22:40:52)

gav616 · 2009-04-02 21:12:26

djgera wrote:

Hi,
Users that experiment the slowness at udev startup, can do some test? It's simple
1) Install the packages that have the slowness problem.
2) Edit the file /lib/udev/load-modules.sh and change in one line LOGGER="/usr/bin/logger" with LOGGER="/bin/true"
3) Try if the slowness dissapears.
4) Please post it here the results (with what packages install for test it)
Thanks

fixes the errors in 'initscripts'-'2009.03-2' and speeds things up a little, so downgrade is not needed.

thank you.

Arch Linux

#1 2008-12-29 21:08:17

Load Modules Takes Forever

#2 2008-12-29 21:16:45

Re: Load Modules Takes Forever

#3 2008-12-29 21:25:34

Re: Load Modules Takes Forever

#4 2008-12-29 21:40:32

Re: Load Modules Takes Forever

#5 2008-12-29 21:52:37

Re: Load Modules Takes Forever

#6 2008-12-30 03:32:47

Re: Load Modules Takes Forever

#7 2009-01-08 23:42:57

Re: Load Modules Takes Forever

#8 2009-03-17 18:29:11

Re: Load Modules Takes Forever

#9 2009-03-17 19:02:08

Re: Load Modules Takes Forever

#10 2009-03-17 19:06:42

Re: Load Modules Takes Forever

#11 2009-03-18 14:31:08

Re: Load Modules Takes Forever

#12 2009-03-18 16:21:36

Re: Load Modules Takes Forever

#13 2009-03-18 16:35:26

Re: Load Modules Takes Forever

#14 2009-03-18 17:30:46

Re: Load Modules Takes Forever

#15 2009-03-18 22:39:29

Re: Load Modules Takes Forever

#16 2009-04-02 21:12:26

Re: Load Modules Takes Forever

Board footer