Damaged USB recieving significant errors

Michael8 · 2017-12-20 03:32:53

Hello, I'm new to Arch Linux. A year ago, when I was using windows I damaged a USB port and had disabled it. How can I disabled the USB on Arch Linux? The following command and out (on pastebin) are:

journalctl -p 3 -xb

https://pastebin.com/PiatjE9P

Please let me know if this is the appropriate way and place to post this.

Thank you

faceyneck · 2017-12-20 04:58:36

Hello, Michael8

Have you read through this forum post?

I haven't read it myself, but I see that it's marked as [SOLVED] and so it should fix your problem.

So, it might be considered 'inappropriate' to post your question, if you had not done a search through the forums first. Not trying to be rude. Just saying....

[EDIT]Also, if you have tried other possible solutions without success, and/or have come across something you don't understand, be sure to outline that in your posts.[/EDIT]

Best of luck,
Facey

Last edited by faceyneck (2017-12-20 05:00:52)

Michael8 · 2017-12-20 07:04:39

I'll be honest, the output confused me too much. I didn't know what to search. Can you tell me how do I read the output to know which USB needs to be suspended?

faceyneck · 2017-12-21 05:32:50

Hey sure, I'll try.

Go ahead and past the output of the command from the bss post I linked to you, namely:

dmesg | tail -n 20

Probably won't find benefit in all 20, just go ahead and post the whole thing here anyway and we'll go from there.

Cheers,

Facey

paulkerry · 2017-12-31 10:08:43

Can you disable the port permanently using the system startup bios?

Mr.Elendig · 2017-12-31 19:58:25

How about grabbing something thin and sharp and unbend pins / remove any shorts? (I have not read the paste, I can't open pastebin.com)

seth · 2017-12-31 21:38:01

relevant pastebin copy (It's there twice, apparently cnp from a VTE; also some QML crashes)

[mike@MBishara_PC ~]$ journalctl -p 3 -xb
-- Logs begin at Wed 2017-12-20 04:56:22 UTC, end at Wed 2017-12-20 14:14:20 UTC. --
Dec 20 09:28:20 MBishara_PC kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
Dec 20 09:28:20 MBishara_PC kernel: usb usb3-port1: over-current condition
Dec 20 09:28:20 MBishara_PC kernel: usb usb3-port2: over-current condition
Dec 20 09:28:20 MBishara_PC kernel: usb 2-1-port1: over-current condition
Dec 20 09:28:20 MBishara_PC kernel: usb 2-1-port2: over-current condition
Dec 20 09:28:21 MBishara_PC kernel: usbhid 3-10.3:1.2: couldn't find an input interrupt endpoint
Dec 20 09:28:22 MBishara_PC kernel: usb 3-9.1.1-port2: Cannot enable. Maybe the USB cable is bad?
Dec 20 09:28:23 MBishara_PC kernel: usb 3-9.1.1-port2: Cannot enable. Maybe the USB cable is bad?
Dec 20 09:28:24 MBishara_PC kernel: usb 3-9.1.1-port2: Cannot enable. Maybe the USB cable is bad?
Dec 20 09:28:25 MBishara_PC kernel: usbhid 3-9.4:1.2: can't add hid device: -32
Dec 20 09:28:25 MBishara_PC kernel: usb 3-9.1.1-port2: Cannot enable. Maybe the USB cable is bad?
Dec 20 09:28:25 MBishara_PC kernel: usb 3-9.1.1-port2: unable to enumerate USB device

So we've two ports where the device draws too much power and one port seems toast.
I agree that removing any short (notably in case the over currents are a side effect) is preferable - if this is the cause.

Arch Linux

#1 2017-12-20 03:32:53

Damaged USB recieving significant errors

#2 2017-12-20 04:58:36

Re: Damaged USB recieving significant errors

#3 2017-12-20 07:04:39

Re: Damaged USB recieving significant errors

#4 2017-12-21 05:32:50

Re: Damaged USB recieving significant errors

#5 2017-12-31 10:08:43

Re: Damaged USB recieving significant errors

#6 2017-12-31 19:58:25

Re: Damaged USB recieving significant errors

#7 2017-12-31 21:38:01

Re: Damaged USB recieving significant errors

Board footer