From: Cedric Sodhi <ManDay@openmail.cc>
To: "Ewan D. Milne" <emilne@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI Oops: Unable to handle kernel NULL ptr dereference
Date: Fri, 11 Aug 2017 09:35:10 +0200 [thread overview]
Message-ID: <20170811073509.GC2729@air> (raw)
In-Reply-To: <1502402499.4120.133.camel@localhost.localdomain>
The following shows in dmesg when the USB side is plugged in:
usb 1-3: new high-speed USB device number 5 using xhci_hcd
usb 1-3: New USB device found, idVendor=174c, idProduct=55aa
usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 1-3: Product: ASM1153 USB3.0 TO SATA
usb 1-3: Manufacturer: Liangteng
usb 1-3: SerialNumber: 1153201404001
usb-storage 1-3:1.0: USB Mass Storage device detected
usb-storage 1-3:1.0: Quirks match for vid 174c pid 55aa: 400000
scsi host3: usb-storage 1-3:1.0
scsi 3:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6
sd 3:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: [sdb] Spinning up disk...
ready
sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 3:0:0:0: [sdb] Attached SCSI disk
On Thu, Aug 10, 2017 at 06:01:39PM -0400, Ewan D. Milne wrote:
> [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
>
>
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next prev parent reply other threads:[~2017-08-11 13:34 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
2017-08-11 7:24 ` Cedric Sodhi
2017-08-11 7:35 ` Cedric Sodhi [this message]
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=20170811073509.GC2729@air \
--to=manday@openmail.cc \
--cc=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/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