USB error while system is loading

surrealistic · 2013-11-04 10:31:41

Hi! when ArchLinux is loading shows this line:

usb 3-1.1: string descriptor 0 read error: -22

What it means? Is there anything not working right?

Thanks!

Pse · 2013-11-04 17:32:46

I see the same. I suspect the bluetooth controller is bugged (though it works fine). I see those messages during boot and when turning off/on the bluetooth adapter.

Last edited by Pse (2013-11-04 17:34:05)

surrealistic · 2013-11-04 18:51:46

Yes, I see this message during boot, shutdown, and reboot, but I don't apreciate any problems when I'm using some USB device or something :S.

WonderWoofy · 2013-11-04 20:23:45

What level error is it in dmesg? If it is in loglevel warn (4), then it can probably be safely ignored. Currently the standard Arch kernel is patched to take down the loglevel from debug (7) to warn (4). But I have found that this can lead to a number of messages from the wl module being printed in the console. So I boot with the kernel parameters "quiet loglevel=3" and these messages are done away with.

Also, it might help if you actually indicated what the offending USB hardware actually is. It may not be important, but when you ask a question, ideally you should provide as much detail as possible about your situation.

surrealistic · 2013-11-04 20:42:20

Hi! This is the result of dmesg |grep usb:

[    2.128128] usbcore: registered new interface driver usbfs
[    2.128151] usbcore: registered new interface driver hub
[    2.128196] usbcore: registered new device driver usb
[    2.461576] usb 3-1: new high-speed USB device number 2 using ehci-pci
[    2.691764] usb 4-1: new high-speed USB device number 2 using ehci-pci
[    2.885433] usb 3-1.1: new full-speed USB device number 3 using ehci-pci
[    2.970456] usb 3-1.1: string descriptor 0 read error: -22
[    3.048773] usb 3-1.3: new high-speed USB device number 4 using ehci-pci
[    9.063479] usbcore: registered new interface driver btusb
[    9.232163] input: HD WebCam as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input15
[    9.232309] usbcore: registered new interface driver uvcvideo
[    9.325737] usbcore: registered new interface driver ath3k
[    9.577033] usb 3-1.1: USB disconnect, device number 3
[    9.764624] usb 3-1.1: new full-speed USB device number 5 using ehci-pci
[    9.849782] usb 3-1.1: string descriptor 0 read error: -22

I don't know if it was what you meant.

Thanks!

WonderWoofy · 2013-11-04 20:47:58

Oh, not quite. But if you check the output of dmesg --help you can see how you can specify the loglevel it outputs. Unsurprisingly, it is the '--level' (-l) flag So it takes a comma separated list of arguments for each level you want it to show you. So in this case you would do dmesg --level warn.

If the message shows up in that output (you might want to grep for it), then it is loglevel warn (4). Typically the things printed there are really just warnings and not an indication of impending doom. You can set the loglevel that is printed to the console with dmesg as well. Again, check out the --help or man page for more.

surrealistic · 2013-11-04 21:29:17

This is the result of dmesg --level=warn:

[    0.000000] ACPI: RSDP 0000000096ffe014 00024 (v02 ACRSYS)
[    0.000000] ACPI: XSDT 0000000096ffe210 000AC (v01 ACRSYS ACRPRDCT 00000001      01000013)
[    0.000000] ACPI: FACP 0000000096ffb000 0010C (v05 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: DSDT 0000000096fec000 0BB9E (v01 ACRSYS ACRPRDCT 00000000 1025 00040000)
[    0.000000] ACPI: FACS 0000000096fba000 00040
[    0.000000] ACPI: UEFI 0000000096ffd000 00236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: ASF! 0000000096ffc000 000A5 (v32 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: HPET 0000000096ffa000 00038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: APIC 0000000096ff9000 0008C (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: MCFG 0000000096ff8000 0003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: SLIC 0000000096feb000 00176 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: SSDT 0000000096fea000 006FE (v01 ACRSYS ACRPRDCT 00001000 1025 00040000)
[    0.000000] ACPI: BOOT 0000000096fe8000 00028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: ASPT 0000000096fe3000 00034 (v07 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: DBGP 0000000096fe2000 00034 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: FPDT 0000000096fe0000 00044 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: MSDM 0000000096fdf000 00055 (v03 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] ACPI: SSDT 0000000096fde000 00926 (v01 ACRSYS ACRPRDCT 00003000 1025 00040000)
[    0.000000] ACPI: SSDT 0000000096fdd000 00A92 (v01 ACRSYS ACRPRDCT 00003000 1025 00040000)
[    0.000000] ACPI: SSDT 0000000096fd9000 02185 (v01 ACRSYS ACRPRDCT 00001000 1025 00040000)
[    0.000000] ACPI: BGRT 0000000096fdc000 00038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
[    0.000000]   Normal   [mem 0x100000000-0x25f5fffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00001000-0x00087fff]
[    0.000000]   node   0: [mem 0x00100000-0x1fffffff]
[    0.000000]   node   0: [mem 0x20200000-0x40003fff]
[    0.000000]   node   0: [mem 0x40005000-0x90daffff]
[    0.000000]   node   0: [mem 0x921b0000-0x967befff]
[    0.000000]   node   0: [mem 0x96fff000-0x96ffffff]
[    0.000000]   node   0: [mem 0x100000000-0x25f5fffff]
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2017807
[    0.000000] Policy zone: Normal
[    0.000000] Memory: 7931112K/8199448K available (5050K kernel code, 799K rwdata, 1696K rodata, 1140K init, 1288K bss, 268336K reserved)
[    0.021919] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.029132] ACPI: All ACPI Tables successfully acquired
[    0.272785] ACPI: Executed 1 blocks of module-level executable AML code
[    0.298392] ACPI: SSDT 0000000096df7018 0083B (v01  PmRef  Cpu0Cst 00003001 INTL 20120215)
[    0.298743] ACPI: Dynamic OEM Table Load:
[    0.298745] ACPI: SSDT           (null) 0083B (v01  PmRef  Cpu0Cst 00003001 INTL 20120215)
[    0.311516] ACPI: SSDT 0000000096df8a98 00303 (v01  PmRef    ApIst 00003000 INTL 20120215)
[    0.311892] ACPI: Dynamic OEM Table Load:
[    0.311894] ACPI: SSDT           (null) 00303 (v01  PmRef    ApIst 00003000 INTL 20120215)
[    0.324725] ACPI: SSDT 0000000096df6d98 00119 (v01  PmRef    ApCst 00003000 INTL 20120215)
[    0.325071] ACPI: Dynamic OEM Table Load:
[    0.325073] ACPI: SSDT           (null) 00119 (v01  PmRef    ApCst 00003000 INTL 20120215)
[    0.342508] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
[    0.342513] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
[    0.645943] ACPI: Enabled 6 GPEs in block 00 to 3F
[    0.821576] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.898224] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130517/nsarguments-95)
[    0.898252] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130517/nsarguments-95)
[    0.898269] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130517/nsarguments-95)
[    0.898288] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130517/nsarguments-95)
[    1.708606] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    2.108454] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[    2.847901] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    7.612271] ACPI Warning: 0x0000000000003040-0x000000000000305f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130517/utaddress-251)
[    7.628773] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130517/utaddress-251)
[    7.628785] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20130517/utaddress-251)
[    7.628789] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20130517/utaddress-251)
[    7.628794] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20130517/utaddress-251)
[    7.628797] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20130517/utaddress-251)
[    7.628802] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    7.966257] [Firmware Bug]: battery: (dis)charge rate invalid.
[    8.146230] acer_wmi: Enabling Launch Manager failed: 0xe2 - 0x0
[   20.828858] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
[  134.452375] vboxdrv: fAsync=0 offMin=0x1d0 offMax=0xf3b6
[ 1448.696188] acer_wmi: Unknown function number - 4 - 0
[ 1448.696439] acer_wmi: Unknown function number - 4 - 0
[ 1449.162959] acer_wmi: Unknown function number - 4 - 0
[ 1449.163125] acer_wmi: Unknown function number - 4 - 0
[ 1449.343484] acer_wmi: Unknown function number - 4 - 0
[ 1449.343665] acer_wmi: Unknown function number - 4 - 0
[ 1449.523825] acer_wmi: Unknown function number - 4 - 0
[ 1449.524000] acer_wmi: Unknown function number - 4 - 0
[ 1449.598191] acer_wmi: Unknown function number - 4 - 0
[ 1449.598376] acer_wmi: Unknown function number - 4 - 0
[ 1449.757403] acer_wmi: Unknown function number - 4 - 0
[ 1449.757583] acer_wmi: Unknown function number - 4 - 0
[ 1449.927183] acer_wmi: Unknown function number - 4 - 0
[ 1449.927372] acer_wmi: Unknown function number - 4 - 0
[ 1450.088396] acer_wmi: Unknown function number - 4 - 0
[ 1450.088623] acer_wmi: Unknown function number - 4 - 0
[ 1450.256140] acer_wmi: Unknown function number - 4 - 0
[ 1450.256369] acer_wmi: Unknown function number - 4 - 0
[ 1450.383428] acer_wmi: Unknown function number - 4 - 0
[ 1450.383669] acer_wmi: Unknown function number - 4 - 0

And this is the result of dmesg --level=err:

[    2.970456] usb 3-1.1: string descriptor 0 read error: -22
[    9.849782] usb 3-1.1: string descriptor 0 read error: -22

The message shown is in err

WonderWoofy · 2013-11-04 21:42:39

Yeah, okay you probably don't want to suppress that then. Not because those messages necessarily mean something bad (honestly I don't know), but you don't want to silence other err messages that might be coming through to the console.

Edit: So you never mentioned anything about the hardware in question. Also, a quick googling of the error message indicates that others have experienced a similar error message with gigabyte motherboards when the IOMMU Controller setting is disabled in the bios. Any chance you are using a gigabyte mobo?

Last edited by WonderWoofy (2013-11-04 21:48:26)

surrealistic · 2013-11-04 21:47:02

Thank you, so there isn't a problem, really? not dangerous, right?

WonderWoofy · 2013-11-04 21:55:13

As I said above, I honestly don't know what this is trying to tell you. But from what I have read elsewhere, it would seem that others have seen this without their machines blowing up. So it depends on what you consider "not dangerous" I guess.

surrealistic · 2013-11-04 22:08:36

Thank you, I would like that not show the message and fix it if may cause problems while working or something.

WonderWoofy · 2013-11-04 22:11:59

Did you see my edit a few posts above?

surrealistic · 2013-11-04 22:33:55

oh! I'm sorry, I don't see the edited post I have an Acer laptop, I guess that is an Acer motherboard.

Arch Linux

#1 2013-11-04 10:31:41

USB error while system is loading

#2 2013-11-04 17:32:46

Re: USB error while system is loading

#3 2013-11-04 18:51:46

Re: USB error while system is loading

#4 2013-11-04 20:23:45

Re: USB error while system is loading

#5 2013-11-04 20:42:20

Re: USB error while system is loading

#6 2013-11-04 20:47:58

Re: USB error while system is loading

#7 2013-11-04 21:29:17

Re: USB error while system is loading

#8 2013-11-04 21:42:39

Re: USB error while system is loading

#9 2013-11-04 21:47:02

Re: USB error while system is loading

#10 2013-11-04 21:55:13

Re: USB error while system is loading

#11 2013-11-04 22:08:36

Re: USB error while system is loading

#12 2013-11-04 22:11:59

Re: USB error while system is loading

#13 2013-11-04 22:33:55

Re: USB error while system is loading

Board footer