[Trac #655] wireless not working, usb discovery errors
Zarro Boogs per Child
bugtracker at laptop.org
Fri Jan 5 06:01:26 EST 2007
#655: wireless not working, usb discovery errors
----------------------+-----------------------------------------------------
Reporter: | Owner: mfoster
Type: defect | Status: new
Priority: high | Milestone: BTest-2
Component: hardware | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Changes (by johnlin):
* reporter: Quozl =>
Old description:
> Unit entered an odd mode, characterised by:
>
> * kernel warnings from the USB layer,
> * non-functioning wireless,
>
> Was working fine with build 212 before this, what changed was a manual
> reboot using shell prompt.
>
> Power cycling did not fix it.
>
> Removing power and battery for two minutes fixed it.
>
> Build: 212, Firmware: Q2B16, Unit Quozl-3, Serial Number: PCL10EN64600169
>
> {{{
> [ 28.648062] Initializing USB Mass Storage driver...
> [ 28.716810] usb 1-4: new high speed USB device using ehci_hcd and
> address 2
> [ 31.866317] usb 1-4: device descriptor read/64, error -110
> [ 47.124155] usb 1-4: device descriptor read/64, error -110
> [ 47.384125] usb 1-4: new high speed USB device using ehci_hcd and
> address 3
> [ 50.533674] usb 1-4: device descriptor read/64, error -110
> [ 65.791511] usb 1-4: device descriptor read/64, error -110
> [ 66.051489] usb 1-4: new high speed USB device using ehci_hcd and
> address 4
> [ 76.499972] usb 1-4: device not accepting address 4, error -110
> [ 76.649970] usb 1-4: new high speed USB device using ehci_hcd and
> address 5
> [ 87.098468] usb 1-4: device not accepting address 5, error -110
> [ 87.134034] usbcore: registered new interface driver usb-storage
> [ 87.168163] USB Mass Storage support registered.
> }}}
New description:
Testing BIOS:Q2B15.
Testing Image:build212.
I tried four machines and type "dmesg | grep usb or dmesg | grep usb\ 1-4"
to see if that problem appears again. But I seemed not to duplicate it
again on my four OLPC CL1 machines.
I only know one way to find whether the boot2 code version of wireless
module. It's as follows:
#lsusb -v //(bcdDevice -> 31.04)
...............
...............
Bus 001 Device 003: ID 1286:2001
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1286
idProduct 0x2001
'''bcdDevice 31.04
iManufacturer 1 Marvell
iProduct 2 MARVELL Wireless Device'''
iSerial 0
bNumConfigurations 1
Comment:
Replying to [ticket:655 Quozl]:
> Unit entered an odd mode, characterised by:
>
> * kernel warnings from the USB layer,
> * non-functioning wireless,
>
> Was working fine with build 212 before this, what changed was a manual
reboot using shell prompt.
>
> Power cycling did not fix it.
>
> Removing power and battery for two minutes fixed it.
>
> Build: 212, Firmware: Q2B16, Unit Quozl-3, Serial Number:
PCL10EN64600169
>
> {{{
> [ 28.648062] Initializing USB Mass Storage driver...
> [ 28.716810] usb 1-4: new high speed USB device using ehci_hcd and
address 2
> [ 31.866317] usb 1-4: device descriptor read/64, error -110
> [ 47.124155] usb 1-4: device descriptor read/64, error -110
> [ 47.384125] usb 1-4: new high speed USB device using ehci_hcd and
address 3
> [ 50.533674] usb 1-4: device descriptor read/64, error -110
> [ 65.791511] usb 1-4: device descriptor read/64, error -110
> [ 66.051489] usb 1-4: new high speed USB device using ehci_hcd and
address 4
> [ 76.499972] usb 1-4: device not accepting address 4, error -110
> [ 76.649970] usb 1-4: new high speed USB device using ehci_hcd and
address 5
> [ 87.098468] usb 1-4: device not accepting address 5, error -110
> [ 87.134034] usbcore: registered new interface driver usb-storage
> [ 87.168163] USB Mass Storage support registered.
> }}}
--
Ticket URL: <http://dev.laptop.org/ticket/655#comment:3>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list