Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

ohci: early return



I'm using an ehci+ohci host controller in a pci-express slot on
6.99.19/amd64, for a uaudio sound card (dmesg at the end).

The first issue is: this uaudio0 is not detected at boot, nor can I
detect it using drvctl. I have to physically unplug and replug the
soundcard after boot. Any ideas why this is necessary?

Second issue: About once a day (usually when starting audio playback),
I get:

Apr 16 09:58:10 yt /netbsd: ohci1: isoc TD alloc failed
Apr 16 09:58:10 yt syslogd[174]: last message repeated 3 times
Apr 16 09:58:10 yt /netbsd: ohci_device_isoc_start: not in progress 
0xfffffe870f5eac38
Apr 16 09:58:10 yt /netbsd: usb_transfer_complete: bad dequeue 
0xfffffe8874b1b138 != 0xfffffe870f5eac38
Apr 16 09:58:10 yt /netbsd: ohci_device_isoc_start: not in progress 
0xfffffe870f5ead70
Apr 16 09:58:10 yt /netbsd: usb_transfer_complete: bad dequeue 
0xfffffe870f5eab00 != 0xfffffe870f5ead70
Apr 16 09:58:10 yt /netbsd: usb_insert_transfer: xfer=0xfffffe870f5eac38 not 
busy 0x0000009e
Apr 16 09:58:10 yt /netbsd: usb_transfer_com_start: not in progress 
0xfffffe870f5eaea8
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 3127 times
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abi_device_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 882 times
Apr 16 10:00:20 yt /netbsd: ohci_device_e_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 882 times
Apr 16 10:00:20 yt /netbsd: ohci_device_e_isoc_abort: e_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 882 times
Apr 16 10:00:20 yt /netbsd: ohci_device_bort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 882 times
Apr 16 10:00:20 yt /netbsd: ohci_device_bort: early return_device_isoc_abort: 
early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_bort: early return_devrn
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 9 times
Apr 16 10:00:20 yt /netbsd: ohci_device_bort: early returnreturn
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 4328 times
Apr 16 10:00:20 yt /netbsd: ly return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt syslogd[174]: last message repeated 883 times
Apr 16 10:00:20 yt /netbsd: ly returneturn
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ly returneturnoc_abort: early return
Apr 16 10:00:20 yt /netbsd: ohci_device_isoc_abort: early return
...

And the console is completely spammed with this message.

Today I also saw:
Apr 16 10:00:34 yt syslogd[174]: klog failed: Bad address
Apr 16 10:01:27 yt syslogd[174]: last message repeated 883 times

"drvctl -d ohci0" returns (i.e., doesn't hang) but doesn't stop the
console from being spammed with the early return messages, so I don't
think it works.

I usually reboot at this point.

dmesg:
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
ohci0 at pci2 dev 0 function 0: vendor 0x9710 product 0x9990 (rev. 0x00)
ohci0: interrupting at ioapic1 pin 8
ohci0: OHCI version 1.0
usb0 at ohci0: USB revision 1.0
ehci0 at pci2 dev 0 function 1: vendor 0x9710 product 0x9990 (rev. 0x00)
ehci0: interrupting at ioapic1 pin 8
ehci0: EHCI version 1.0
ehci0: companion controller, 1 port each: ohci0
usb1 at ehci0: USB revision 2.0
ohci1 at pci2 dev 0 function 2: vendor 0x9710 product 0x9990 (rev. 0x00)
ohci1: interrupting at ioapic1 pin 12
ohci1: OHCI version 1.0
usb2 at ohci1: USB revision 1.0
ehci1 at pci2 dev 0 function 3: vendor 0x9710 product 0x9990 (rev. 0x00)
ehci1: interrupting at ioapic1 pin 12
ehci1: EHCI version 1.0
ehci1: companion controller, 1 port each: ohci1
usb3 at ehci1: USB revision 2.0
ohci2 at pci2 dev 0 function 4: vendor 0x9710 product 0x9990 (rev. 0x00)
ohci2: interrupting at ioapic1 pin 13
ohci2: OHCI version 1.0
usb4 at ohci2: USB revision 1.0
ehci2 at pci2 dev 0 function 5: vendor 0x9710 product 0x9990 (rev. 0x00)
ehci2: interrupting at ioapic1 pin 13
ehci2: EHCI version 1.0
ehci2: companion controller, 1 port each: ohci2
usb5 at ehci2: USB revision 2.0
ohci3 at pci2 dev 0 function 6: vendor 0x9710 product 0x9990 (rev. 0x00)
ohci3: interrupting at ioapic1 pin 14
ohci3: OHCI version 1.0
usb6 at ohci3: USB revision 1.0
ehci3 at pci2 dev 0 function 7: vendor 0x9710 product 0x9990 (rev. 0x00)
ehci3: interrupting at ioapic1 pin 14
ehci3: EHCI version 1.0
ehci3: companion controller, 1 port each: ohci3
usb7 at ehci3: USB revision 2.0

ehci0: handing over full speed device on port 1 to ohci0
uaudio0 at uhub0 port 1 configuration 1 interface 0
uaudio0: C-Media Electronics Inc. USB Advanced Audio Device, rev 1.10/1.00, 
addr 2
uaudio0: audio rev 1.00
audio1 at uaudio0: full duplex, playback, capture, independent
uhidev5 at uhub0 port 1 configuration 1 interface 3
uhidev5: C-Media Electronics Inc. USB Advanced Audio Device, rev 1.10/1.00, 
addr 2, iclass 3/0
uhid2 at uhidev5: input=16, output=16, feature=0

Ideas? Patches? :)
 Thomas


Home | Main Index | Thread Index | Old Index