af9015, af9013 DVB-T problems

To the maintainer of the af9015, af9013 modules:

A recent kernel (but the problem had been the same with older kernels):
2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux

Latest (as of yesterday) checkout of v4l-dvb (but the problem had been the same with older checkouts).

Dual channel USB DVB-T stick initialized ok, but
regularly the stick does not tune properly on one of the two channels and the kernel shows these error messages at the same time:

[14410.717905] af9015: command failed:2
[14410.717913] af9013: I2C read failed reg:d330
[18208.030546] af9015: command failed:2
[18208.030554] af9013: I2C read failed reg:d2e6

I'm willing to help debug. Who is the maintainer of af9015, af9013?

Cheers,
Chris

Am 13.06.2010 09:12, schrieb C. Hemsing:

which and on which usb hardware?

Is the device really supported?

State Your USB-Hardware with lsusb and lspci -nnvvv , pls.

I can confirm the intermittent disconnects and ehci force halts on debian x...2.6.32-5 and kernel.org x...2.6.34 for

Bus 001 Device 007: ID 04ca:f001 Lite-On Technology Corp. (dib3000mc)
Bus 001 Device 002: ID 1462:8807 Micro Star International DIGIVOX mini III [af9015] Bus 004 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter (rt73usb)

on

00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 86) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. K8T NEO 2 motherboard [1462:7020]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 21
Region 0: Memory at fbefd400 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ehci_hcd

and

00:0e.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 63) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 10
Region 0: Memory at febfe800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd

suggest we subscribe and CC [email protected],
http://www.linux-usb.org/mailing.html

ehci-hcd is broken and halts silently or disconnects after hours or a few days, with the wlan usb adapter I was able to catch a dmesg err message like "ehci...force halt... handshake failed" once only.

The rt73usb was reinitialized by uhci as full speed device then, but it did not work with wpa_supplicant, manual device removal was necessary, so it should be of no use if we add dvb-usb driver reinits on i2c failures, too.

The disconnects with dvb-usb need reboot cause driver cannot be removed with modprobe.

This long standing bug is really nasty and makes permanent high speed usb connections unusable on Linux, at least with this VIA hardware.

No debug parms in modules, we need to ask linux-usb how to debug this.

y
tom

How do you know the bug is in ehci-hcd and not in the hardware?

Can you please post the error message?

That sounds like it might be a bug in dvb-usb driver. It always should be possible to remove the driver.

You can start by building a kernel with CONFIG_USB_DEBUG enabled.

Alan Stern

Am 13.06.2010 15:57, schrieb Alan Stern:

All 3 usb devices and 2 different series VIA usb hosts and Hemsing's and many other broken i2c comms reporter's on linux-media are broken instead? Well, if we get that confirmed, I'll buy 2 of those with NEC chipset:
http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=190318779935

Jun  3 08:38:29 tom3 kernel: [75071.004062] ehci_hcd 0000:00:0e.2: force halt; handhake cc9c0814 0000c000 00000000 -> -110
Jun  3 08:45:13 tom3 kernel: [75475.004061] ehci_hcd 0000:00:0e.2: force halt; handhake cc9c0814 0000c000 00000000 -> -110

Previous debian testing version of Linux tom3 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux, not yet reproduced with current version.

Sure.

Yes, will do it, thx.

y
tom

It's certainly possible and has been known to happen.

You may need to copy the "broken periodic workaround" code from the PCI_VENDOR_ID_INTEL case in ehci_pci_setup(), drivers/usb/host/ehci-pci.c into the PCI_VENDOR_ID_VIA case.

Alan Stern

Am 13.06.2010 17:22, schrieb Alan Stern:

Reproducible with the new debian testing kernel:

[90395.572222] usb 4-4: USB disconnect, address 3
[90395.585864] wlan0: deauthenticating from 00:19:cb:87:5e:4a by local choice (reason=3)
[90396.100206] usb 4-4: new high speed USB device using ehci_hcd and address 4
[90411.192304] hub 4-0:1.0: unable to enumerate USB device on port 4
[90411.448242] usb 3-2: new full speed USB device using uhci_hcd and address 3
[90411.635297] usb 3-2: not running at top speed; connect to a high speed hub
[90411.757316] usb 3-2: New USB device found, idVendor=148f, idProduct=2573
...
[90412.212601] Registered led device: rt73usb-phy4::quality
[90414.004060] ehci_hcd 0000:00:0e.2: force halt; handhake cca1a814 0000c000 00000000 -> -110

Trying to reproduce in full speed only mode without ehci_hcd driver loaded.

Yes, will do this on the machine with the 2.6.34 kernel and watch the dvb-usb stick for disconnects to report.

Thank You very much,
y
tom