From: Oliver Neukum <oneukum@suse.com>
To: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>,
linux-usb@vger.kernel.org
Subject: Re: Kernel Oops in cdc_acm
Date: Tue, 26 May 2020 10:08:48 +0200 [thread overview]
Message-ID: <1590480528.2838.24.camel@suse.com> (raw)
In-Reply-To: <20200525191624.GA28647@math.uni-bielefeld.de>
Am Montag, den 25.05.2020, 21:16 +0200 schrieb Jean Rene Dawin:
Hi,
good, so the primary bug is fixed. I will send it upstream.
May I include your "Reported-by:" to give you the deserved fame?
> The first time the battery is removed and inserted again, everything is
> quite fine. Except that the USB cable has to be plugged out and in for the
> connection to be re-established. But that was needed in previous
> kernels, too.
Yes, I know. It sucks. But I cannot tell that it is the same device
in the kernel. Nor can I reestablish the connection, as it is done with
AT commands. It also means I cannot support reset_resume(). It sucks.
Any ideas?
I can only encourage you to contact the people developing the tool set
you are using.
> # turn on phone
> [ 572.928634] ------------[ cut here ]------------
> [ 572.928643] WARNING: CPU: 0 PID: 0 at kernel/workqueue.c:1473 __queue_work+0x38a/0x430
This is extremely interesting and unexpected. It is in USB core. I am
looking into this.
Regards
Oliver
next prev parent reply other threads:[~2020-05-26 8:08 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 [this message]
2020-05-26 11:16 ` Jean Rene Dawin
2020-05-26 11:13 ` Oliver Neukum
2020-05-26 19:57 ` Jean Rene Dawin
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=1590480528.2838.24.camel@suse.com \
--to=oneukum@suse.com \
--cc=jdawin@math.uni-bielefeld.de \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.