Strange problem with Innokin EZ-WATT, whilst charging from USB

coralfang · 07-04-2018, 10:49 AM

I have an Innokin EZ-WATT vaporiser (e-cigarette), which is typically charged up whilst i'm at the computer. Always had some weird issues with it, if the device is left connected to USB at boot, the BIOS never advances until it's disconnected. If the device is connected before udev runs at boot, the system halts, but resumes fine once the device is disconnected.

Whilst charging (after booting the machine to the login screen), my Slackware Linux machine gets spammed with this in dmesg:

Code:

[   35.194550] usb 5-1.1: device descriptor read/64, error -32
[   35.296500] usb 5-1-port1: attempt power cycle
[   35.816404] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   35.876383] usb 5-1.1: new low-speed USB device number 33 using xhci_hcd
[   35.876910] usb 5-1.1: Device not responding to setup address.
[   36.080904] usb 5-1.1: Device not responding to setup address.
[   36.156390] usb 11-4: new low-speed USB device number 16 using ohci-pci
[   36.288390] usb 5-1.1: device not accepting address 33, error -71
[   36.297393] usb 11-4: device descriptor read/64, error -62
[   36.556323] usb 5-1.1: new low-speed USB device number 34 using xhci_hcd
[   36.556838] usb 5-1.1: Device not responding to setup address.
[   36.761006] usb 5-1.1: Device not responding to setup address.
[   36.968401] usb 5-1.1: device not accepting address 34, error -71
[   36.968573] usb 5-1-port1: unable to enumerate USB device
[   37.120442] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   37.120463] usb usb7-port4: unable to enumerate USB device
[   37.376415] usb 5-1.1: new low-speed USB device number 35 using xhci_hcd
[   37.442574] usb 5-1.1: device descriptor read/64, error -32
[   37.610617] usb 5-1.1: device descriptor read/64, error -32
[   37.776423] usb 5-1.1: new low-speed USB device number 36 using xhci_hcd
[   37.842565] usb 5-1.1: device descriptor read/64, error -32
[   38.010628] usb 5-1.1: device descriptor read/64, error -32
[   38.112563] usb 5-1-port1: attempt power cycle
[   38.640455] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   38.700445] usb 5-1.1: new low-speed USB device number 37 using xhci_hcd
[   38.700977] usb 5-1.1: Device not responding to setup address.
[   38.904937] usb 5-1.1: Device not responding to setup address.
[   39.112368] usb 5-1.1: device not accepting address 37, error -71
[   39.380394] usb 5-1.1: new low-speed USB device number 38 using xhci_hcd
[   39.380960] usb 5-1.1: Device not responding to setup address.
[   39.528501] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   39.528514] usb usb7-port4: attempt power cycle
[   39.584998] usb 5-1.1: Device not responding to setup address.
[   39.792437] usb 5-1.1: device not accepting address 38, error -71
[   39.792653] usb 5-1-port1: unable to enumerate USB device
[   40.144490] usb 11-4: new low-speed USB device number 18 using ohci-pci
[   40.285385] usb 11-4: device descriptor read/64, error -62
[   40.367442] usb 5-1.1: new low-speed USB device number 39 using xhci_hcd
[   40.433552] usb 5-1.1: device descriptor read/64, error -32
[   40.602579] usb 5-1.1: device descriptor read/64, error -32
[   40.768465] usb 5-1.1: new low-speed USB device number 40 using xhci_hcd
[   40.834662] usb 5-1.1: device descriptor read/64, error -32
[   41.002555] usb 5-1.1: device descriptor read/64, error -32
[   41.104641] usb 5-1-port1: attempt power cycle
[   41.624499] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   41.684468] usb 5-1.1: new low-speed USB device number 41 using xhci_hcd
[   41.685099] usb 5-1.1: Device not responding to setup address.
[   41.889073] usb 5-1.1: Device not responding to setup address.
[   41.964467] usb 11-4: new low-speed USB device number 19 using ohci-pci
[   42.096469] usb 5-1.1: device not accepting address 41, error -71
[   42.105470] usb 11-4: device descriptor read/64, error -62
[   42.364477] usb 5-1.1: new low-speed USB device number 42 using xhci_hcd
[   42.365104] usb 5-1.1: Device not responding to setup address.
[   42.568959] usb 5-1.1: Device not responding to setup address.
[   42.776480] usb 5-1.1: device not accepting address 42, error -71
[   42.776712] usb 5-1-port1: unable to enumerate USB device
[   42.928448] usb usb7-port4: Cannot enable. Maybe the USB cable is bad?
[   42.928467] usb usb7-port4: unable to enumerate USB device
[   43.184490] usb 5-1.1: new low-speed USB device number 43 using xhci_hcd
[   43.250697] usb 5-1.1: device descriptor read/64, error -32
[   43.418627] usb 5-1.1: device descriptor read/64, error -32
[   43.584454] usb 5-1.1: new low-speed USB device number 44 using xhci_hcd
[   43.650708] usb 5-1.1: device descriptor read/64, error -32
[   43.818698] usb 5-1.1: device descriptor read/64, error -32
[   43.920662] usb 5-1-port1: attempt power cycle

My question is, why is this happening, and how can i completely ignore this device, regardless of which USB port it's connected to? I'm stuck with this, because the device has no vendor id, nor product id that i can blacklist/ignore via udev rules.

What is the device trying to do? AFAIK, the micro USB connection shouldn't do anything other than allow for charging up the device. I'm confused, but really want to hide this spam from dmesg/logs relating to the device.

ondoho · 07-05-2018, 04:41 AM

Quote:

Originally Posted by coralfang

how can i completely ignore this device

in BIOS, just tell it to never try to boot from USB
in linux - with a udev rule i guess: http://reactivated.net/writing_udev_rules.html

coralfang · 07-05-2018, 12:04 PM

Quote:

Originally Posted by ondoho

in BIOS, just tell it to never try to boot from USB
in linux - with a udev rule i guess: http://reactivated.net/writing_udev_rules.html

That's the weird thing. I have usb devices as the lowest boot priority, so it should never try to boot form usb unless i trigger the manual boot choice menu.

As for udev, i am unable to write a rule, as the device has no product id etc such as 12ab:34cd, and i can't just ignore an entire usb socket, as other devices are often switched out etc.

michaelk · 07-05-2018, 12:52 PM

IMHO I would purchase a USB wall charger with the proper current requirements and not use the computer.

I have not read up on how USB 3.0 works with high current devices but I assume when plugged in at power up or prior to udev the USB 5 VDC might be current limiting which is why you never see the BIOS advance or halts. I don't know if there is a misbehaving circuit inside your device or this is just how it works but I doubt there is a fix and would not trust the charging circuit.

ondoho · 07-05-2018, 04:15 PM

Quote:

Originally Posted by coralfang

That's the weird thing. I have usb devices as the lowest boot priority, so it should never try to boot form usb unless i trigger the manual boot choice menu.

As for udev, i am unable to write a rule, as the device has no product id etc such as 12ab:34cd, and i can't just ignore an entire usb socket, as other devices are often switched out etc.

8 hours after my suggestion, i'm pretty sure you haven't explored all possibilities of writing udev rules yet...

but honestly, why make yourself suffer when you can use a standard USB charger instead... every thrift store has a box full of them for very small money.

coralfang · 07-05-2018, 04:29 PM

Quote:

Originally Posted by michaelk

IMHO I would purchase a USB wall charger with the proper current requirements and not use the computer.

I have not read up on how USB 3.0 works with high current devices but I assume when plugged in at power up or prior to udev the USB 5 VDC might be current limiting which is why you never see the BIOS advance or halts. I don't know if there is a misbehaving circuit inside your device or this is just how it works but I doubt there is a fix and would not trust the charging circuit.

AFAIK, this is how all of them work. As i replaced my old device previously with an identical one, which did the same thing.

As for charging from the wall, i guess i'll just get a usb/wall charger for it.

coralfang · 07-05-2018, 04:30 PM

Quote:

Originally Posted by ondoho

8 hours after my suggestion, i'm pretty sure you haven't explored all possibilities of writing udev rules yet...

but honestly, why make yourself suffer when you can use a standard USB charger instead... every thrift store has a box full of them for very small money.

I don't see how i can blacklist it with udev though? The device has no identifier at all, so i can't seem to understand how to block it.

ondoho · 07-05-2018, 04:38 PM

Quote:

Originally Posted by coralfang

The device has no identifier at all

how did you test that?
hint: look at the article i linked, then maybe also:
http://dt.iki.fi/udev/
https://hackaday.com/2009/09/18/how-...te-udev-rules/

coralfang · 07-05-2018, 06:23 PM

Quote:

Originally Posted by ondoho

how did you test that?
hint: look at the article i linked, then maybe also:
http://dt.iki.fi/udev/
https://hackaday.com/2009/09/18/how-...te-udev-rules/

Quote:

ATTRS{idVendor}=="XXXX", ATTRS{idProduct}=="XXXX",

The ecig has no vendor or product id, it isn't recognized as a valid device, that's the problem.
When it's connected there is never any information on vendor/product. #

Say if you were to blacklist a device, you require the vendor/product id to do that.
This device just constantly triggers a bunch of invalid usb messages whilst it is charging.

ondoho · 07-06-2018, 04:53 PM

Quote:

Originally Posted by coralfang

Say if you were to blacklist a device, you require the vendor/product id to do that.

but there's so many more attributes to check for.
well, i don't know this device, maybe it really doesn't provide anything.

michaelk · 07-06-2018, 05:02 PM

Since the device hangs the computer before the operating system is even started I would not trust it and think the best option is using a USB wall charger.