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 20:04:38 +0200	[thread overview]
Message-ID: <4DE67F36.8060600@gmail.com> (raw)
In-Reply-To: <201106010934.45691.oneukum@suse.de>

Hi,

Il 01/06/2011 09:34, Oliver Neukum ha scritto:
> Am Mittwoch, 1. Juni 2011, 09:05:44 schrieb Riccardo Magliocchetti:
>>>> 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:
>
> Then please post lsusb -v of that state. This is a log of a connection
> going wrong due to a bad cable or interference. Does that always happen?

yes it does always happen because (i think) the device hangs, so lsusb 
does not show the device.

thanks,
riccardo

  reply	other threads:[~2011-06-01 18:04 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
2011-06-01  7:34           ` Oliver Neukum
2011-06-01 18:04             ` Riccardo Magliocchetti [this message]
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=4DE67F36.8060600@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