All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paul.menzel@giantmonkey.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Erich Schubert <erich@debian.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	801925@bugs.debian.org,
	Alexandre Rossi <alexandre.rossi@gmail.com>
Subject: Re: NULL pointer dereference: IP: [<f828a00c>] sr_runtime_suspend+0xc/0x20 [sr_mod]
Date: Tue, 19 Jan 2016 17:52:53 +0100	[thread overview]
Message-ID: <1453222373.3588.3.camel@giantmonkey.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1601191127020.1727-100000@iolanthe.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]

Dear Alan, dear Erich,


Am Dienstag, den 19.01.2016, 11:38 -0500 schrieb Alan Stern:
> On Tue, 19 Jan 2016, Erich Schubert wrote:

> > Attached are photos of the Kernel null pointer BUG that I'm observing.
> > 
> > These shots are with 4.4.0-rc8.
> > As you can see, I have a similar trace to Paul, but the error occurs
> > one stack frame earlier?
>
> Yours is only slighly similar to Paul's.  He got an error in 
> sr_runtime_suspend, but your error occurs in sd_resume -- a completely
> different function in a different source file.

if I remember correctly, it happened it different places for me too. In
the backlog you should see, that Ben gave me a patch to try and then it
wasn’t triggered as it failed somewhere else.

> > Maybe Alex issue is the same bug, but triggered slightly different or
> > just the kernel compiled differently.
> > __rpm_callback, scsi_autopm_put_device, __pm_runtime_resume, sd_probe
> > is present in all of these traces.
> > 
> > Sorry, I do not have a lot of time right now to help testing or debugging.
>
> I can't tell what's going wrong without some real debugging.  This
> means somebody has to build and test a patched kernel.  There are no
> problems on my computer, so it will have to be one or more of you
> guys.

Could you please attach the debugging patch. Hopefully Alexandre, Erich,
or I will have some spare time to build an image from it.

Alan, thank you a lot for being so responsive and helpful!


Thanks,

Paul
-- 
GPG-Schlüssel: 33623E9B
Fingerabdruck = 0EB1 649D 4361 D04F 3C70  6F71 4DD7 BF75 3362 3E9B

Giant Monkey Software Engineering GmbH

Brunnenstr. 7D
10119 Berlin Mitte

Geschäftsführer Adrian Fuhrmann, Lion Vollnhals und Paul Menzel

USt-IdNr.: DE281524720
HRB 139495 B Amtsgericht Charlottenburg

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-19 16:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGKbab941Nh7Sy1NTZC6ySxG_P5g7HpjATQ_GSCvDY8y=qgmHA@mail.gmail.com>
2016-01-19 16:38 ` NULL pointer dereference: IP: [<f828a00c>] sr_runtime_suspend+0xc/0x20 [sr_mod] Alan Stern
2016-01-19 16:52   ` Paul Menzel [this message]
2016-01-19 21:08     ` Alan Stern
2016-01-19 23:20       ` Paul Menzel
2016-01-20 22:07       ` Alexandre Rossi
2016-02-09 16:47         ` Paul Menzel
2016-02-09 19:56           ` Alexandre Rossi
2016-02-09 20:51             ` Ben Hutchings
2016-02-18 16:27             ` Alan Stern
2016-02-22 23:15               ` Alexandre Rossi
2016-02-23 15:14                 ` Alan Stern
2015-10-16  1:05 Paul Menzel
2015-10-16  7:54 ` Paul Menzel
2015-10-16  8:52   ` Paul Menzel
2015-10-20  1:39   ` Ben Hutchings
2015-10-31  9:39     ` Paul Menzel
2015-11-01  1:56       ` Alan Stern
2015-11-01  2:05       ` Alan Stern
2016-01-09 15:23         ` Paul Menzel
2016-01-09 16:36           ` Alan Stern
2016-01-10 11:44             ` Erich Schubert
2016-01-10 15:32               ` 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=1453222373.3588.3.camel@giantmonkey.de \
    --to=paul.menzel@giantmonkey.de \
    --cc=801925@bugs.debian.org \
    --cc=alexandre.rossi@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=erich@debian.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.