All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: wim@djo.tudelft.nl
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: crash by cdc_acm driver in kernels 4.8-rc1/5
Date: Wed, 28 Sep 2016 17:23:30 +0200	[thread overview]
Message-ID: <1475076210.4635.18.camel@suse.com> (raw)
In-Reply-To: <20160928150856.GA1424@djo.tudelft.nl>

On Wed, 2016-09-28 at 17:08 +0200, Wim Osterholt wrote:
> On Wed, Sep 28, 2016 at 11:16:04AM +0200, Oliver Neukum wrote:
> > this should show you where it crashes. In addition I've attached
> > a patch with paranoid debugging. Could you compile and test a kernel
> > with it?
> > 
> > 	Regards
> > 		Oliver
> 
> If you mean
>   echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
> etc, then it will take some time because I don't have the cabling not
> available now for a serial dump.
> 
> Just 4.8-rc8 with the patched modules gave an oops of less than one screen
> while the machine stayed responsive long enough to grab it with the mouse
> and put it in a file:
> 
> HP src # sync
> HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer dereference at 00000249

The last view lines before that please with the debugging level ramped
up to 9 please.

	Regards
		Oliver

  reply	other threads:[~2016-09-28 15:23 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 11:58 crash by cdc_acm driver in kernels 4.8-rc1/5 Wim Osterholt
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 [this message]
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=1475076210.4635.18.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wim@djo.tudelft.nl \
    /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.