Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53290 - hotplug hangs when starting PCI hotplug after installing udev 026-ri
Summary: hotplug hangs when starting PCI hotplug after installing udev 026-ri
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Greg Kroah-Hartman (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-08 03:28 UTC by Alan Schmitt
Modified: 2004-06-08 13:57 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Schmitt 2004-06-08 03:28:02 UTC
After installing udev 026-r1 and baselayout 1.9.4-r2, I rebooted and the boot process hanged doing
Hotplug PCI
(Hotplug USB worked fine).

Reproducible: Always
Steps to Reproduce:
1. Boot
2.
3.

Actual Results:  
Hotplug hanged

Expected Results:  
System should boot.

I'm using a pure udev system, with a gentoo-development 2.6.5 kernel. I'm using
up to date ~x86 hotplug, udev, and baselayout.

I managed to boot without starting hotplug, and launched it manually. Here is
what was sent to /var/log/messages:

Jun  8 10:15:14 charm USB Universal Host Controller Interface driver v2.2
Jun  8 10:15:14 charm uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB USB (Hub #1)
Jun  8 10:15:15 charm PCI: Setting latency timer of device 0000:00:1d.0 to 64
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.0: irq 11, io base 0000bf80
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 1
Jun  8 10:15:15 charm hub 1-0:1.0: USB hub found
Jun  8 10:15:15 charm hub 1-0:1.0: 2 ports detected
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB USB (Hub #2)
Jun  8 10:15:15 charm PCI: Setting latency timer of device 0000:00:1d.1 to 64
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.1: irq 11, io base 0000bf40
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 2
Jun  8 10:15:15 charm hub 2-0:1.0: USB hub found
Jun  8 10:15:15 charm hub 2-0:1.0: 2 ports detected
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB USB (Hub #3)
Jun  8 10:15:15 charm PCI: Setting latency timer of device 0000:00:1d.2 to 64
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.2: irq 11, io base 0000bf20
Jun  8 10:15:15 charm uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 3
Jun  8 10:15:15 charm hub 3-0:1.0: USB hub found
Jun  8 10:15:15 charm hub 3-0:1.0: 2 ports detected
Jun  8 10:15:15 charm ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB USB2
Jun  8 10:15:15 charm PCI: Setting latency timer of device 0000:00:1d.7 to 64
Jun  8 10:15:15 charm ehci_hcd 0000:00:1d.7: irq 11, pci mem f9a4cc00
Jun  8 10:15:15 charm ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 4
Jun  8 10:15:15 charm PCI: cache line size of 32 is not supported by device
0000:00:1d.7
Jun  8 10:15:15 charm ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver
2003-Dec-29
Jun  8 10:15:15 charm hub 4-0:1.0: USB hub found
Jun  8 10:15:15 charm hub 4-0:1.0: 6 ports detected
Jun  8 10:15:15 charm hub 2-0:1.0: connect-debounce failed, port 2 disabled
Jun  8 10:15:16 charm tg3.c:v2.9 (March 8, 2004)
Jun  8 10:15:16 charm eth0: Tigon3 [partno(BCM95705A50) rev 3001 PHY(5705)]
(PCI:33MHz:32-bit) 10/100
/1000BaseT Ethernet 00:0f:1f:0d:8e:00
Jun  8 10:15:16 charm usb 2-2: new low speed USB device using address 2
Jun  8 10:15:16 charm drivers/usb/core/usb.c: registered new driver hiddev
Jun  8 10:15:16 charm input: USB HID v1.10 Mouse [Logitech Trackball] on
usb-0000:00:1d.1-2
Jun  8 10:15:16 charm drivers/usb/core/usb.c: registered new driver hid
Jun  8 10:15:16 charm drivers/usb/input/hid-core.c: v2.0:USB HID core driver
Jun  8 10:15:17 charm ohci1394: $Rev: 1172 $ Ben Collins <bcollins@debian.org>
Jun  8 10:15:17 charm ieee1394.agent[7123]: ... no drivers for IEEE1394 product
0x/0x/0x
Jun  8 10:15:17 charm ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] 
MMIO=[fafef800-fafeffff]  Ma
x Packet=[2048]
Jun  8 10:15:17 charm hostap_crypt: registered algorithm 'NULL'
Jun  8 10:15:17 charm ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.46_3
Jun  8 10:15:17 charm ipw2100: Copyright(c) 2003-2004 Intel Corporation
Jun  8 10:15:17 charm Detected ipw2100 PCI device at 0000:02:03.0, mem:
0xFAFEE000-0xFAFEEFFF -> f9a8
8000, irq: 11
Jun  8 10:15:17 charm eth1: Using hotplug firmware load.
Jun  8 10:15:18 charm tg3: eth0: Link is up at 100 Mbps, full duplex.
Jun  8 10:15:18 charm tg3: eth0: Flow control is off for TX and off for RX.

The system was stuck then, but did start rebooting after ctrl-alt-del (rebooting
managed to stop Hotplug PCI but hanged on Hotplug USB).

I'm ready to provide more informations here, but I do not know where to look.
Comment 1 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-06-08 11:22:41 UTC
Can you upgrade your kernel?  This is not a userspace udev issue (well, it should not be...)
Comment 2 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-06-08 11:24:14 UTC
Also, don't worry about starting hotplug, just load the modules that you know
you need to load in the modules.autoload file.  Don't have the hotplug
service try to autoload modules from a cold boot process.
Comment 3 Alan Schmitt 2004-06-08 11:55:47 UTC
I don't know where the issue comes from, but I also upgraded glibc yesterday (so maybe I should try to reemerge hotplug).

I'm not too eager to upgrade the kernel, as it would mean moving from the gentoo-dev sources to the vanilla kernel (I'm running the latest gentoo-dev kernel, unless one was released since this morning).

I can definitely live without hotplug, by the way. I just read that it was very recommended for udev systems.
Comment 4 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-06-08 13:08:10 UTC
The hotplug package is required for udev to work, but starting up the "coldboot"
process (which is what you are really doing there) is not necessary at all.

Hm, maybe I should rename that startup script to help people figure this out...

Anyway, odds are it's a kernel driver issue, so upgrading your kernel should 
fix it.

I'm going to close this bug, as it's not a udev issue at all.  If you still have
problems with the most recent, vanilla kernel, and it's a udev issue, please
reopen it.
Comment 5 Alan Schmitt 2004-06-08 13:57:32 UTC
If it is a driver issue, then another thing that was updated very recently is the ipw2100 module. I did not really suspect it since the logs say that the tg3 module is loaded after.