Yeah. So this is my new blog. I thought, it would be a nice place to collect various bits of information that I noticed during my work that could be useful to other people too (as well as me, having a head like a sieve). So enjoy it, if you like!

Yesterday, I suddenly wasn’t able to use my AF9015-based DVB-T USB stick anymore. It only worked for about a minute, then the image froze and dmesg said the following:

[10633.166371] usb 1-3: USB disconnect, address 5
[10633.186247] af9015: bulk message failed:-22 (8/-339951920)
[10633.186254] af9013: I2C read failed reg:d417
[10633.186258] af9015: bulk message failed:-22 (8/-1067461161)
[10633.186265] af9013: I2C read failed reg:d417
[10633.186279] af9015: bulk message failed:-22 (9/-339951284)
[10633.186282] mt2060 I2C write failed

I was not even able to rmmod the dvb-usb-af9015 kernel module, the rmmod process just hung itself up.

After two hours of compiling a new driver version, experimenting with kernel parameters and getting a new firmware version, I finally booted into my rarely used Windows system. The first thing I saw was the “USB 2.0 device on USB 1.1 bus”, and as I also could not get a movie stream, I tried to plug the DVB-T stick into a different USB port. And voilà, suddenly everything worked again, as well on Windows as later on Linux. No more error messages in the kernel log, everything just fine as before.

But I wonder if I have been using this USB port before — as far as I can remember, the DVB-T stick had always been on the other port… Yet another proof for me to never trust yourself

Update: Unfortunately, this solution did not help for long. After about two weeks, the error is still there, and also occurs more frequently, near to once an evening (until I reboot). So maybe, it hasn’t even to do with switching USB ports, and my hardware is beginning to fail…

Update: Seems it is fixed now, using revision dca0fed8d68b (Sat Sep 26 19:27:52 2009 +0200) of anttip’s repository. At least it worked for over 4 hours now