[ltp] Alarming boot messages...

[paul marwick]

Richard wrote:
>
> On Mon, 5 Nov 2007, paul marwick wrote:
>
>> Richard wrote:
>>
>>> What that means is the USB hub is reporting excess current draw from 
>>> connected devices. In general, a USB port may provide only 500mA of 
>>> current, and connected devices are expected to be "well behaved"*. 
>>> If you use an unpowered hub, then each branch can only draw 100mA.
>>>
>>> lsusb -v will tell you more.
>>>
>>>
>>> I'm guessing you have too many connected USB devices, and inadequate 
>>> power?
>>
>> Hmm. That makes it even stranger, since its only occurring during 
>> boot, when I have no USB devices plugged in. I'll plug in something 
>> and see if any new messages appear....
>
>
> IIRC, some of the internal peripherals (Bluetooth, synaptics, 
> ultraport, fingerprint reader) are USB, so you do essentially have 
> several devices.

I wasn't aware of that. I've just done an lsusb -v, but looking through 
the output, I can't find anything that looks like an active USB device.

Also tried plugging in my most recent USB device (a Seagate Freeagent GO 
120 GB hard drive). Messages generated are as below:

usb 1-4: new high speed USB device using ehci_hcd and address 2
Device driver usbdev1.2_ep00 lacks bus and class support for being resumed.
usb 1-4: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
Device driver host2 lacks bus and class support for being resumed.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Device driver usbdev1.2_ep01 lacks bus and class support for being resumed.
Device driver usbdev1.2_ep81 lacks bus and class support for being resumed.
Device driver target2:0:0 lacks bus and class support for being resumed.
scsi 2:0:0:0: Direct-Access Seagate FreeAgent Go 100F PQ: 0 ANSI: 4

All the messages look normal... I'm still a bit concerned about the 
intermittent nature of the report.

> The good news is that this is just a warning message. If nothing bad 
> actually happens, you can probably ignore it. My guess is that the 
> problem has been there all along, but you've just started to use a 
> distro/kernel version that actually notifies you in an obvious manner.

:) I hope you're right.... I'll have to check the configuration of the 
two 2.6.22.9 kernels and see if there are any differences in the way 
they set up USB support. That might explain why the Vector kernel is 
producing the messages while the Zenwalk one isn't.

Regards, Paul.