From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 93051] New: Oops in kmem_cache_alloc / scsi_host_alloc_command
Date: Tue, 10 Feb 2015 16:56:06 +0000 [thread overview]
Message-ID: <bug-93051-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=93051
Bug ID: 93051
Summary: Oops in kmem_cache_alloc / scsi_host_alloc_command
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.16.0-29-generic #39-Ubuntu
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: nathan.renniewaldock+kernelbugs@gmail.com
Regression: No
Created attachment 166341
--> https://bugzilla.kernel.org/attachment.cgi?id=166341&action=edit
oops 2015-01-30
Read errors on SCSI controllers appear to cause an oops.
Since I changed to an SAS controller, I was getting an oops immediately after a
read error. I've now moved the offending drive back to SATA and not had an oops
since.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-02-10 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:56 bugzilla-daemon [this message]
2015-02-10 16:56 ` [Bug 93051] Oops in kmem_cache_alloc / scsi_host_alloc_command bugzilla-daemon
2015-02-10 16:56 ` bugzilla-daemon
2015-02-10 16:56 ` bugzilla-daemon
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=bug-93051-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).