From: Paul Menzel <paul.menzel@giantmonkey.de>
To: Alexandre Rossi <alexandre.rossi@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Erich Schubert <erich@debian.org>,
Ben Hutchings <ben@decadent.org.uk>,
SCSI development list <linux-scsi@vger.kernel.org>,
801925@bugs.debian.org
Subject: Re: NULL pointer dereference: IP: [<f828a00c>] sr_runtime_suspend+0xc/0x20 [sr_mod]
Date: Tue, 09 Feb 2016 17:47:00 +0100 [thread overview]
Message-ID: <1455036420.11996.5.camel@giantmonkey.de> (raw)
In-Reply-To: <CAM79t8GJvQPzOt1oDikxv3wPZ9xgVMez5EUgXmeVH2zKJCeaAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
Dear Debian and Linux folks,
Am Mittwoch, den 20.01.2016, 23:07 +0100 schrieb Alexandre Rossi:
> >> Could you please attach the debugging patch. Hopefully Alexandre, Erich,
> >> or I will have some spare time to build an image from it.
> >
> > Actually, this patch is an attempt at a fix. After looking more
> > carefully at your log pictures, I realized what the problem must be.
> >
> > It's too bad nobody was able to capture a log where the error
> > occurred in sr_runtime_suspend, though -- all the logs in the bug
> > report show sd_runtime_resume.
>
> I just tested the patch applied on top of 4.3.3 (4.3.3-6 in Debian).
>
> It still crashes at boot, but the stacktrace is different : it happens
> in blk_post_runtime_resume . Maybe I'm bit by a different bug or maybe
> the I need to try with 4.4.
>
> I'll post the captured log when I have access to a wired network. I'd
> be happy to provide the logs of a debugging patch.
I tried Linux 4.3.5-1 [1], which entered Debian Sid/unstable yesterday,
and I get the same null pointer dereference as Alexandre.
As this is Linux 4.3 and not 4.4, I guess this is a different problem
though. Alexandre, where you able to capture the stack trace? I’d submit
a new bug report with this.
Thanks,
Paul
[1] http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_4.3.5-1_changelog
--
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 --]
next prev parent reply other threads:[~2016-02-09 16:47 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
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 [this message]
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=1455036420.11996.5.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.