[lug] Temporary system hanging

Daniel Webb lists at danielwebb.us
Tue Apr 4 11:59:10 MDT 2006


On Tue, Apr 04, 2006 at 02:42:12AM -0600, Daniel Webb wrote:

> Looking online, I see people with similar problems being solved by using the
> "noapic" kernel boot parameter.  Here goes nothing...

No luck.

Apr  4 02:45:21 nerd kernel: PCI: Found IRQ 10 for device 0000:00:0e.0
Apr  4 02:45:21 nerd kernel: PCI: Sharing IRQ 10 with 0000:00:0e.1
Apr  4 02:45:21 nerd kernel: bttv0: Bt878 (rev 17) at 0000:00:0e.0, irq: 10, latency: 32, mmio: +0xf5000000
Apr  4 02:45:21 nerd kernel: bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is +0070:13eb
Apr  4 02:45:21 nerd kernel: bttv0: using: Hauppauge (bt878) [card=10,autodetected]
Apr  4 02:45:21 nerd kernel: bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
Apr  4 02:45:21 nerd kernel: bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]


Apr  4 02:45:21 nerd kernel: via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
Apr  4 02:45:21 nerd kernel: PCI: Found IRQ 10 for device 0000:00:12.0
Apr  4 02:45:21 nerd kernel: PCI: Sharing IRQ 10 with 0000:00:0f.1
Apr  4 02:45:21 nerd kernel: IRQ routing conflict for 0000:00:10.0, have irq 3, want irq 10
Apr  4 02:45:21 nerd kernel: IRQ routing conflict for 0000:00:10.1, have irq 3, want irq 10
Apr  4 02:45:21 nerd kernel: IRQ routing conflict for 0000:00:12.0, have irq 3, want irq 10
Apr  4 02:45:21 nerd kernel: eth0: VIA Rhine II at 0xf1800000, 00:0e:a6:51:d4:42, IRQ 3.
Apr  4 02:45:21 nerd kernel: eth0: MII PHY found at address 1, status 0x786d advertising 01e1 +Link 45e1.

<snip>

Apr  4 02:45:21 nerd kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

<snip>

Apr  4 02:48:40 nerd kernel: usb-storage: device found at 4
Apr  4 02:48:40 nerd kernel: usb-storage: waiting for device to settle before scanning
Apr  4 02:48:40 nerd kernel: USB Universal Host Controller Interface driver v2.3
Apr  4 02:48:40 nerd kernel: PCI: Found IRQ 10 for device 0000:00:10.0
Apr  4 02:48:40 nerd kernel: PCI: Sharing IRQ 10 with 0000:00:0f.1
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:10.0, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:10.1, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:12.0, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.0: UHCI Host Controller
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.0: irq 3, io base 0x00008800
Apr  4 02:48:40 nerd kernel: hub 2-0:1.0: USB hub found
Apr  4 02:48:40 nerd kernel: hub 2-0:1.0: 2 ports detected
Apr  4 02:48:40 nerd usb.agent[3630]:      usb-storage: already loaded
Apr  4 02:48:40 nerd usb.agent[3556]:      usbcore: already loaded
Apr  4 02:48:40 nerd kernel: PCI: Found IRQ 10 for device 0000:00:10.1
Apr  4 02:48:40 nerd kernel: PCI: Sharing IRQ 10 with 0000:00:0f.1
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:10.0, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:10.1, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: IRQ routing conflict for 0000:00:12.0, have irq 3, want irq 10
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.1: UHCI Host Controller
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
Apr  4 02:48:40 nerd kernel: uhci_hcd 0000:00:10.1: irq 3, io base 0x00008400

Does this mean my built-in ethernet and built-in USB controller are sharing an
interrupt with a video card?  I don't know that much about how all that works,
but it doesn't sound like a good idea.





More information about the LUG mailing list