Bug 30088 - USB2-port1 error; "bad cable?" (Dell XPS8950 w/AMD RX6600XT graphics)
Summary: USB2-port1 error; "bad cable?" (Dell XPS8950 w/AMD RX6600XT graphics)
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-23 22:19 CET by Pierre Fortin
Modified: 2022-02-24 19:31 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Pierre Fortin 2022-02-23 22:19:55 CET
Description of problem: Brand new system (see also 30087). 

On boot, besides no video, I was getting error messages about 1 per second complaining of USB2-port1 possible bad cable. Ran Dell diagnostics; all fine.

Swapped wired mouse and keyboard connections and error message no longer appears. Filing this because it should not matter which device is connected to port1; and to inform others of the workaround.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. make wired keyboard/mouse connections to new machine.
2. boot up (no video due to bug 30087)
3. switch to other vtys; messages about once per second (no login required)
Comment 1 sturmvogel 2022-02-24 08:12:51 CET
Sorry for your bad start.
As this might related be related to a a real damaged cable this is nothing what Mageia can fix. USB-Ports on a machine are controlled by different hubs/controllers with different abilitys/functionalitys. So error messages on one port could occur even if they don't show up at another one.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED

Comment 2 Pierre Fortin 2022-02-24 10:26:22 CET
Everything is brand new out of the boxes.  Will see if Cauldron from a good mirror solves this...
Comment 3 Thomas Backlund 2022-02-24 19:31:27 CET
Yeah, just because everything is "new" cables and/or hw can be bad. also the connector could be dirty, or the hw in your system is from a "buggy revision" that might need new bios/firmware or some errata fix in the kernel... 

Theese things happends all the time, and sometimes as you noticed a fix can be as simple as switching port...

Note You need to log in before you can comment on or make changes to this bug.