From: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Kernel Oops in cdc_acm
Date: Tue, 26 May 2020 21:57:50 +0200 [thread overview]
Message-ID: <20200526195750.GA10336@math.uni-bielefeld.de> (raw)
In-Reply-To: <1590491586.2838.38.camel@suse.com>
Oliver Neukum wrote on Tue 26/05/20 13:13:
> Hi,
>
> may I ask whether you did the test with removing the battery twice with
> an older kernel? Could you please go back to
> f6cc6093a729ede1ff5658b493237c42b82ba107
> and repeat the test of a second battery removal with that state?
> I just cannot find anything pointing to a change that could cause
> this issue within that time.
Hi,
testing with f6cc6093a729ede1ff5658b493237c42b82ba107 looks like this:
=========== 1 =============
# remove battery first time
[ 447.818693] usb 1-2: USB disconnect, device number 2
[ 447.856667] cdc_acm 1-2:1.3: failed to set dtr/rts
# loop disconnect/connect
# insert battery first time
[ 481.267878] usb 1-2: new high-speed USB device number 20 using ehci-pci
# turn on phone first time
[ 488.984876] cdc_acm 1-2:1.3: failed to set dtr/rts
[ 490.562661] usb 1-2: USB disconnect, device number 20
[ 504.341285] usb 1-2: new high-speed USB device number 21 using ehci-pci
# unplug/plug USB cable - network ok
=========== 2 =============
# remove battery second time
[ 576.310900] usb 1-2: USB disconnect, device number 22
[ 576.334020] cdc_acm 1-2:1.3: failed to set dtr/rts
# loop disconnect/connect
# insert battery second time
[ 606.764940] usb 1-2: new high-speed USB device number 38 using ehci-pci
# turn on phone second time
[ 616.398126] usb 1-2: USB disconnect, device number 38
[ 616.418763] cdc_acm 1-2:1.3: acm_port_activate - usb_submit_urb(ctrl irq) failed
[ 630.208351] usb 1-2: new high-speed USB device number 39 using ehci-pci
# unplug/plug USB cable - network ok
=========== 3 =============
# remove battery third time
[ 711.081997] usb 1-2: USB disconnect, device number 40
[ 711.099678] cdc_acm 1-2:1.3: failed to set dtr/rts
# loop disconnect/connect
# insert battery third time
[ 744.458707] usb 1-2: new high-speed USB device number 58 using ehci-pci
# turn on phone third time
[ 751.195202] cdc_acm 1-2:1.3: failed to set dtr/rts
[ 752.213695] cdc_acm 1-2:1.3: failed to set dtr/rts
[ 752.457590] usb 1-2: USB disconnect, device number 58
# unplug/plug USB cable - network ok
Interesting is, that at the second time, the usb disconnect message
conmes first, and then a message from cdc_acm acm_port_activate.
Regards,
Jean Rene
next prev parent reply other threads:[~2020-05-26 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 12:00 Kernel Oops in cdc_acm Jean Rene Dawin
2020-05-25 12:28 ` Oliver Neukum
2020-05-25 19:16 ` Jean Rene Dawin
2020-05-26 8:08 ` Oliver Neukum
2020-05-26 11:16 ` Jean Rene Dawin
2020-05-26 11:13 ` Oliver Neukum
2020-05-26 19:57 ` Jean Rene Dawin [this message]
2020-05-27 8:53 ` Oliver Neukum
2020-05-28 8:51 ` Jean Rene Dawin
2020-06-03 7:26 ` Jean Rene Dawin
2020-05-27 8:28 ` Jean Rene Dawin
2020-05-27 9:33 ` Oliver Neukum
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=20200526195750.GA10336@math.uni-bielefeld.de \
--to=jdawin@math.uni-bielefeld.de \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).