public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Oliver Neukum <oneukum@suse.de>
Cc: linux-usb@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oliver Neukum <oliver@neukum.name>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [2.6.39] crash in acm_ctrl_msg+0x16/0x59
Date: Wed, 01 Jun 2011 09:05:44 +0200	[thread overview]
Message-ID: <4DE5E4C8.5060706@gmail.com> (raw)
In-Reply-To: <201105311037.46856.oneukum@suse.de>

Il 31/05/2011 10:37, Oliver Neukum ha scritto:
> Am Montag, 30. Mai 2011, 21:32:54 schrieb Riccardo Magliocchetti:
>>>> So we are trying to talk to a device that is already gone.
>>>> Is there anything unusual about your device? Could you
>>>> post "lsusb -v"?
>>>
>>> Yes, the unusual thing is that is very prone to freezing when booting,
>>> in fact it freezed when i got the crash in the laptop. Will post lsusb
>>> output later in the day.
>>
>> Here's the lsusb -v
>
> There is something strange going on. This is a cdc-ether device.
> Are you using any additional patches?

I'm using a vanilla 2.6.39. I can get only lsusb when the phone is 
booted and in that case it is recgnized as cdc-ether.

This is what i got when i attached the phone switched off like when i 
got the crash:

usb 6-1: new full speed USB device number 3 using uhci_hcd
usb 6-1: New USB device found, idVendor=1d50, idProduct=5119
usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 6-1: Product: Neo1973 Bootloader U-Boot 1.3.2-dirty-moko12
usb 6-1: Manufacturer: OpenMoko, Inc
usb 6-1: SerialNumber: 0000000
cdc_acm 6-1:1.0: This device cannot do calls on its own. It is not a modem.
cdc_acm 6-1:1.0: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN 
adapters
hub 6-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 6-1: USB disconnect, device number 3
usb 6-1: new full speed USB device number 4 using uhci_hcd
usb 6-1: device descriptor read/64, error -71
usb 6-1: device descriptor read/64, error -71
usb 6-1: new low speed USB device number 5 using uhci_hcd
usb 6-1: device descriptor read/64, error -71
usb 6-1: new full speed USB device number 6 using uhci_hcd
usb 6-1: device not accepting address 6, error -71
usb 6-1: new full speed USB device number 7 using uhci_hcd
usb 6-1: device not accepting address 7, error -71
hub 6-0:1.0: unable to enumerate USB device on port 1

thanks,
riccardo

  reply	other threads:[~2011-06-01  7:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 14:04 [2.6.39] crash in acm_ctrl_msg+0x16/0x59 Riccardo Magliocchetti
2011-05-30  5:54 ` Oliver Neukum
2011-05-30  9:19   ` Riccardo Magliocchetti
2011-05-30 19:32     ` Riccardo Magliocchetti
2011-05-31  8:37       ` Oliver Neukum
2011-06-01  7:05         ` Riccardo Magliocchetti [this message]
2011-06-01  7:34           ` Oliver Neukum
2011-06-01 18:04             ` Riccardo Magliocchetti
2011-06-02 19:34               ` Oliver Neukum
2011-06-03  7:06                 ` Riccardo Magliocchetti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DE5E4C8.5060706@gmail.com \
    --to=riccardo.magliocchetti@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.name \
    --cc=oneukum@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox