Kobo breaking my usb ports

[geek1011]

Not again!!! This was fixed quite a few releases ago (I think 4.4.9344 or something like that), and now the issue is back in 4.7.10413.

On all my linux computers, after I unplug/plug my kobo more than 2 or 3 times, or write/read more than about 300mb (it varies), the usb port stops working (with all devices) until a reboot. I can use a different usb port, and it works another 2 or 3 times.

dmesg shows the following interesting lines on the 2nd or 3rd connection:

Spoiler:

[460780.718814] usb-storage 3-1:1.0: USB Mass Storage device detected
[460780.719020] scsi host7: usb-storage 3-1:1.0
[460781.727629] scsi 7:0:0:0: Direct-Access     Kobo     eReader-4.7.1041 0110 PQ: 0 ANSI: 2
[460781.734500] sd 7:0:0:0: [sdc] 6614013 512-byte logical blocks: (3.39 GB/3.15 GiB)
[460781.846263] sd 7:0:0:0: [sdc] Write Protect is off
[460781.846265] sd 7:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[460781.956375] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[460782.193979]  sdc:
[460782.416369] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[460782.727933] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[460802.201803] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[460802.201819] usb 3-1: USB disconnect, device number 77
[460802.312949] sd 7:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[460802.312953] sd 7:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 14 49 34 00 00 f0 00
[460802.312955] print_req_error: I/O error, dev sdc, sector 1329460
[460802.312976] sd 7:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[460802.312978] sd 7:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 14 4a 24 00 00 10 00
[460802.312979] print_req_error: I/O error, dev sdc, sector 1329700
[460802.314274] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314321] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314358] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314414] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314441] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314452] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314478] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314504] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314530] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314550] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314580] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314595] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314600] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314604] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314609] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314613] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314617] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314624] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314653] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314670] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314676] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.314690] FAT-fs (sdc): FAT read failed (blocknr 1292)
[460802.326572] sd 7:0:0:0: [sdc] Synchronizing SCSI cache
[460802.326587] sd 7:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[460802.326795] FAT-fs (sdc): Directory bread(block 12900) failed
[460802.326797] FAT-fs (sdc): Directory bread(block 12901) failed
[460802.326798] FAT-fs (sdc): Directory bread(block 12902) failed
[460802.326799] FAT-fs (sdc): Directory bread(block 12903) failed
[460802.326800] FAT-fs (sdc): Directory bread(block 12904) failed
[460802.326801] FAT-fs (sdc): Directory bread(block 12905) failed
[460802.326802] FAT-fs (sdc): Directory bread(block 12906) failed
[460802.326803] FAT-fs (sdc): Directory bread(block 12907) failed
[460802.326811] FAT-fs (sdc): Directory bread(block 1277548) failed
[460802.326812] FAT-fs (sdc): Directory bread(block 1277549) failed
[460803.366540] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460804.259921] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460804.259987] usb usb3-port1: attempt power cycle
[460805.466581] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460806.363153] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460806.363169] usb usb3-port1: unable to enumerate USB device
[460842.099840] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460842.993200] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460842.993237] usb usb3-port1: attempt power cycle
[460844.203188] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460845.096563] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[460845.096621] usb usb3-port1: unable to enumerate USB device

I am at a loss for explaining this issue. I have tried downgrading and upgrading the kernel, changing kobo sd cards, trying different usb cables, trying another kobo (it's an aura ed2), and a whole lot of other things. I am using Arch Linux, Xubuntu 17.10, Debian Sid, and Fedora 27.

Note: no, the sd card in the kobo is not failing.

[DuckieTigger]

Did you try different usb ports? Not sure from the log, but looks like it is a usb 3 port? Try a usb 2 port, or if you don't have one a usb 2 hub.

[geek1011]

Originally Posted by DuckieTigger

Did you try different usb ports? Not sure from the log, but looks like it is a usb 3 port? Try a usb 2 port, or if you don't have one a usb 2 hub.

Yep. Tried both usb 2 and 3.

[DuckieTigger]

Originally Posted by geek1011

Yep. Tried both usb 2 and 3.

Curious why the bad blocks appear. Do you unplug it right after a umount?

[davidfor]

Let me get this right:

- If you restart the device and the computer, you can plug the device in and copy as much to it as you want.
- When you eject and reconnect, you have a 50% chance of it failing when copying 300MB or so. And if it doesn't fail, it will the next time.
- And after this, the USB port doesn't work.

Does this mean if you only copy a small amount, say less than 50MB, it never fails? Or, might it be cumulative?

And what are you doing? I'm pretty sure you aren't using calibre. So, just copying books or other files to the device? Or are you updating the database. There are reports from calibre users that the connection seems to fail while reading and updating the database. I don't have a consistent feel for this other than it is more likely for USB3 connections.

Have you tried restarting the device between connections? Just wondering if this might reset something in the device that would prevent the problem. And to be fair, you would also need to try restarting the PC to see if it is something on it that is the cause. You have tried multiple PCs, but it is something that should be eliminated.

[JSWolf]

Have you tried the cable that comes with the KAE2? Other cables?

[DuckieTigger]

Originally Posted by geek1011

I am at a loss for explaining this issue. I have tried downgrading and upgrading the kernel, changing kobo sd cards, trying different usb cables, trying another kobo (it's an aura ed2), and a whole lot of other things. I am using Arch Linux, Xubuntu 17.10, Debian Sid, and Fedora 27.

Note: no, the sd card in the kobo is not failing.

Originally Posted by JSWolf

Have you tried the cable that comes with the KAE2? Other cables?

He has, which doesn't make much sense. I think the problem still lies within the cables and the Kobo being too picky about it. The USB hub in his computer shuts down after too many interruptions it thinks are caused by electro magnetic interference (the EMI lines from his log). Apparently it failed to power back up (possibly a failsafe mechanism to protect from harmful powersurges). If an EMI is false positive (and the cable or transmission itself is not to blame) then one or both sides (computer or Kobo) are not following standard protocol.

[geek1011]

Originally Posted by DuckieTigger

Curious why the bad blocks appear. Do you unplug it right after a umount?

Yep. I think the bad blocks are due to the sudden disconnect while the fat driver is trying to read. The Kobo does fscks on the user partition anyways.

[geek1011]

Originally Posted by davidfor

Let me get this right:

- If you restart the device and the computer, you can plug the device in and copy as much to it as you want.
- When you eject and reconnect, you have a 50% chance of it failing when copying 300MB or so. And if it doesn't fail, it will the next time.
- And after this, the USB port doesn't work.

Does this mean if you only copy a small amount, say less than 50MB, it never fails? Or, might it be cumulative?

And what are you doing? I'm pretty sure you aren't using calibre. So, just copying books or other files to the device? Or are you updating the database. There are reports from calibre users that the connection seems to fail while reading and updating the database. I don't have a consistent feel for this other than it is more likely for USB3 connections.

Have you tried restarting the device between connections? Just wondering if this might reset something in the device that would prevent the problem. And to be fair, you would also need to try restarting the PC to see if it is something on it that is the cause. You have tried multiple PCs, but it is something that should be eliminated.

Yep, the first bit is right, other than that I don't have to restart the Kobo, just restart the computer or change usb ports.

I am just copying files, and sometimes updating the database (all in one transaction) when I need to tweak the home screen or update series metadata. I even tried copying a large dummy file, and it seems to happen sooner with many small files.

Restarting the Kobo does nothing, as the usb port stops working even with other usb devices until a reboot.

[geek1011]

I've also found some interesting, and possibly related stuff here: https://reddit.com/r/linux/comments/...isconnects_on/ and here: https://www.linuxquestions.org/quest...abling-841593/

[Semwize]

Originally Posted by geek1011

On all my linux computers, after I unplug/plug my kobo more than 2 or 3 times, or write/read more than about 300mb (it varies), the usb port stops working (with all devices) until a reboot. I can use a different usb port, and it works another 2 or 3 times.

Exactly the same thing happens on Windows 7 64. Just changing USB ports, I have a lot of them) But it's not good.

[JSWolf]

Originally Posted by geek1011

I've also found some interesting, and possibly related stuff here: https://reddit.com/r/linux/comments/...isconnects_on/ and here: https://www.linuxquestions.org/quest...abling-841593/

Both links are not correct. Please repost.

As for Problems with Windows, I've used my H2O on Windows 7, Windows Vista, and Windows 10 all 64-bit. No problem at all with both USB 2 and USB 3 ports. I'm not sure if I've ever used the original cable. None of my cables that I've used has had an issue.

[Semwize]

Originally Posted by JSWolf

As for Problems with Windows, I've used my H2O on Windows 7, Windows Vista, and Windows 10 all 64-bit.

Problems arise after 2-3-4 connections in a row. Then you have to change the port.

And such problem only with Kobo, with other devices no problem.

[JSWolf]

I know I've plugged my H2O in more than twice before rebooting/turning off the laptop. Not all in a row. And most of those plugins are with Calibre running. I'll plug in my H2O for 2 minutes without Calibre running for 3 times. Then I'll plug in my Fiio X3II and see if the computer recognizes it and if so, I'll plug my H2O back in one more time.

[Semwize]

This problem I have for a long time, I just wasn't paying attention. But seeing the post with the same problem, confirmed that it is. It is not a coincidence, this pattern.