From: "Ewan D. Milne" <emilne@redhat.com>
To: manday@openmail.cc
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI Oops: Unable to handle kernel NULL ptr dereference
Date: Thu, 10 Aug 2017 18:01:39 -0400 [thread overview]
Message-ID: <1502402499.4120.133.camel@localhost.localdomain> (raw)
In-Reply-To: <20170810170537.Horde.8CxBesYMH_QVGbAB7dui6vz@www.vfemail.net>
[cc's snipped to linux-scsi ]
On Thu, 2017-08-10 at 17:05 +0000, manday@openmail.cc wrote:
> Hello,
>
> I'd like to report this rare panic I experienced today. I've been on
> 4.12.3 since it was released and got this panic totally unexpected,
> probably when terminating my WL compositor. I attach to this message a
> capture of the screen. The problem occurred never before and never
> after since, suggesting I will not be able to reproduce it easily.
> Perhaps it means something to someone.
>
> Linux air 4.12.3 #4 SMP Fri Jul 28 12:07:06 CEST 2017 x86_64 Intel(R)
> Core(TM)i5-6267U CPU @ 2.90GHz GenuineIntel GNU/Linux
>
> I don't know what additional information might be useful so if there
> is anything else I should provide please tell me.
>
> Best regards,
> Cedric
Your stack trace indicates some kind of corruption in a kmem cache
used by the SCSI code, uncovered when the block queue was being freed.
Can you describe what SCSI hardware is connected to your machine?
A snippet of your boot messages showing the hardware probe would help.
-Ewan
next prev parent reply other threads:[~2017-08-10 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 17:05 SCSI Oops: Unable to handle kernel NULL ptr dereference manday
2017-08-10 17:38 ` Bart Van Assche
2017-08-10 22:01 ` Ewan D. Milne [this message]
2017-08-11 7:24 ` Cedric Sodhi
2017-08-11 7:35 ` Cedric Sodhi
2017-08-11 8:11 ` Cedric Sodhi
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=1502402499.4120.133.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=manday@openmail.cc \
/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