From: Wim Osterholt <wim@djo.tudelft.nl>
To: oliver@neukum.org
Cc: oneukum@suse.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Wim Osterholt <wim@djo.tudelft.nl>
Subject: crash by cdc_acm driver in kernels 4.8-rc1/5
Date: Thu, 8 Sep 2016 13:58:03 +0200 [thread overview]
Message-ID: <20160908115803.GA28274@djo.tudelft.nl> (raw)
L.S.
up to vanilla kernel 4.7.3 I've seen no problems.
On two different dekstops running vanilla kernel-4.8 I can force a crash by
inserting an USB-modem that requires module cdc_acm.ko .
(Strangely enough that doesn't happen on my laptop.)
The moment that cdc_acm loads (manually or automatically - the hardware needs
to be present) a kernel oops occurs.
The system remains responsive for a while, but a reboot is necessairy.
If you try a neat shutdown, the system will hang forever after 'remounting fs
read-only'. You'll need a power-down.
The oops tells things that I didn't all write down, but it says
null pointer dereference at 00000246
...
failed while handling devices/pci0000:00/0000:00:1d.3/usb7/7-1/7-1:1d etc.
...
udevd .. is taking too long..
Could someone please explain and repair the magic that is happening here?
Thanks in advance, Wim Osterholt.
----- wim@djo.tudelft.nl -----
next reply other threads:[~2016-09-08 12:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 11:58 Wim Osterholt [this message]
2016-09-08 12:20 ` Oliver Neukum
2016-09-08 12:58 ` Wim Osterholt
2016-09-08 13:05 ` Oliver Neukum
2016-09-08 15:00 ` Wim Osterholt
2016-09-08 16:54 ` Wim Osterholt
2016-09-09 13:24 ` Wim Osterholt
2016-09-12 2:43 ` Wim Osterholt
2016-09-20 13:05 ` Oliver Neukum
2016-09-20 15:45 ` Wim Osterholt
2016-09-21 12:21 ` Oliver Neukum
2016-09-21 16:21 ` Wim Osterholt
2016-09-21 16:41 ` Wim Osterholt
2016-09-22 14:40 ` Oliver Neukum
2016-09-22 17:56 ` Wim Osterholt
2016-09-22 19:21 ` Wim Osterholt
2016-09-23 10:04 ` Wim Osterholt
2016-09-27 16:34 ` Wim Osterholt
2016-09-28 9:16 ` Oliver Neukum
2016-09-28 14:46 ` Wim Osterholt
2016-09-28 15:08 ` Wim Osterholt
2016-09-28 15:23 ` Oliver Neukum
2016-09-29 13:26 ` Wim Osterholt
2016-10-06 10:53 ` Oliver Neukum
2016-10-17 14:10 ` Oliver Neukum
2016-10-17 15:20 ` Wim Osterholt
2016-10-18 12:18 ` Oliver Neukum
2016-10-18 14:51 ` Wim Osterholt
2016-11-05 13:34 ` Wim Osterholt
2016-11-15 0:16 ` Wim Osterholt
2016-11-15 11:07 ` Oliver Neukum
2016-11-15 11:26 ` poma
2016-11-15 13:29 ` Wim Osterholt
2016-11-16 12:34 ` Oliver Neukum
2016-11-16 15:07 ` Wim Osterholt
2016-11-17 1:57 ` Wim Osterholt
2016-11-17 9:14 ` Wim Osterholt
2016-11-17 16:11 ` Wim Osterholt
2016-11-21 13:19 ` Oliver Neukum
2016-11-21 15:58 ` Wim Osterholt
2016-11-21 20:23 ` Wim Osterholt
2016-11-21 23:49 ` poma
2016-11-22 17:50 ` Bjørn Mork
2016-11-23 0:48 ` Wim Osterholt
2016-11-22 15:38 ` Wim Osterholt
2016-11-22 18:08 ` Bjørn Mork
2016-11-23 0:54 ` Wim Osterholt
2016-11-23 7:37 ` Bjørn Mork
2016-11-23 15:02 ` Alan Stern
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=20160908115803.GA28274@djo.tudelft.nl \
--to=wim@djo.tudelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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
all inboxes | Powered by JetHome®