On Thu, May 17, 2001 at 04:30:18PM -0500, HOEFFNER at dcmir.med.umn.edu wrote:
> Hi
> 
> This should be breeze for you hardware types. I'm wondering if this is of
> concern and how to fix the problem.
> 
> I'm just finishing up an install of RH7.1 on a Dell Dimension somethingorother
> and am finding a *LOT* of lines in /var/log/messages that look like this:
> 
> May 17 11:36:55 yggr kernel: usb-uhci.c: interrupt, status 3, frame# 1280
> May 17 11:36:55 yggr kernel: usb-uhci.c: interrupt, status 3, frame# 1282
> May 17 11:36:55 yggr kernel: usb-uhci.c: interrupt, status 3, frame# 1401
> May 17 11:36:55 yggr kernel: usb-uhci.c: interrupt, status 3, frame# 1403
> May 17 11:36:55 yggr kernel: usb-uhci.c: too many bad statuses
> May 17 11:50:00 yggr kernel: es1371: unloading
> May 17 11:50:00 yggr kernel: Uniform CD-ROM driver unloaded
> May 17 11:50:00 yggr kernel: hdc: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33)
> 
> /var/log/dmesg:
> 
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-uhci.c: $Revision: 1.251 $ time 20:53:29 Apr  8 2001
> usb-uhci.c: High bandwidth mode enabled
> PCI: Found IRQ 9 for device 00:07.2
> PCI: The same IRQ used for device 00:10.0
> usb-uhci.c: USB UHCI at I/O 0x1400, IRQ 9
> usb-uhci.c: Detected 2 ports
> usb.c: new USB bus registered, assigned bus number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> hub.c: USB new device connect on bus1/2, assigned device number 2
> usb.c: USB device 2 (vend/prod 0x3f0/0x107) is not claimed by any active driver.
> 
> 
> /proc/interrupts
> 
>            CPU0       
>   0:      58912          XT-PIC  timer
>   1:        713          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   8:          1          XT-PIC  rtc
>   9:      16087          XT-PIC  usb-uhci, es1371      <---???
>  10:       6542          XT-PIC  ide2
>  11:      12032          XT-PIC  eth0
>  12:      21580          XT-PIC  PS/2 Mouse
>  15:       3408          XT-PIC  ide1
> NMI:          0 
> ERR:          0
> 
> Eventually, the es1371 entry goes away. The way I see this, there is a conflict
> between the sound card and the USB port, and the USB eventually wins so the
> sound card gives up. Booting into winders98 (the original os), shows both of
> these devices on IRQ9, though they both claim no conflicts (Yeah, it's M$...,
> and when it boots into winders, the "boot sound" comes out a little choppy, so
> it would seem that something is wrong there). They are both automatically
> configured in winders. The Dell site really doesn't go into this too much,
> though I noticed a few errors in their description compared to what I've seen
> on the machine, so I'm not all that happy with what I read there either.

There is no conflict. Most PCI cards play nicely with each other and share their interupts. Especially low-bandwidth ones like sound/usb/serial.

What you see are two unrelated events. The kernel module loader saw that nobody used module es1731 and unloaded it. It is normal. For instance on my laptop, the video/network/sound/modem are all on IRQ 11, even though there are plenty of free IRQs.

What is not normal is the bad status on the usb controller but that I cannot help you with.

> Is this easily fixed? Not being much of a pc type, I'm really not sure how to
> go about it. Bios has none of this, just IRQ5 as reserved for legacy reasons,
> so it must've been set during the install.

A new usb linux driver might fix it. Or play with the USB devices you have to see if one of them is causing it.

florin

-- 

"you have moved your mouse, please reboot to make this change take effect"