From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 90601] New: panic on write to 3ware raid array
Date: Fri, 02 Jan 2015 14:31:33 +0000 [thread overview]
Message-ID: <bug-90601-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=90601
Bug ID: 90601
Summary: panic on write to 3ware raid array
Product: IO/Storage
Version: 2.5
Kernel Version: 3.16 and above
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
Assignee: linux-scsi@vger.kernel.org
Reporter: merlin@liao.homelinux.org
Regression: No
Created attachment 162291
--> https://bugzilla.kernel.org/attachment.cgi?id=162291&action=edit
panic log
Since kernel version 3.16 we are getting kernel panics and the panic message
*might* suggest that it's related to the raid controller we use.
I did try the kernel versions 3.17, 3.18 and also and it keeps crashing.
3.15.10 runs totally fine though.
I can reproduce the crash 100% with a simple DD command
dd if=/dev/zero of=test bs=1G count=10
I've attached the backtrace and tw_cli configruation options.
We have several cluster nodes so I can try patches or give additional
information when necessary.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-01-02 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 14:31 bugzilla-daemon [this message]
2015-01-02 14:32 ` [Bug 90601] panic on write to 3ware raid array bugzilla-daemon
2015-01-02 14:33 ` bugzilla-daemon
2015-01-05 9:17 ` bugzilla-daemon
2015-01-06 15:28 ` bugzilla-daemon
2015-01-06 15:29 ` bugzilla-daemon
2015-01-06 15:30 ` bugzilla-daemon
2015-01-06 15:48 ` bugzilla-daemon
2015-01-21 11:51 ` bugzilla-daemon
2015-02-13 7:25 ` bugzilla-daemon
2015-02-13 7:54 ` bugzilla-daemon
2015-02-13 8:28 ` bugzilla-daemon
2015-02-13 16:20 ` bugzilla-daemon
2015-02-26 5:44 ` bugzilla-daemon
2015-02-26 7:32 ` bugzilla-daemon
2015-02-26 13:38 ` bugzilla-daemon
2015-04-13 16:16 ` bugzilla-daemon
2015-04-13 16:16 ` bugzilla-daemon
2015-04-16 11:21 ` bugzilla-daemon
2015-04-16 11:25 ` bugzilla-daemon
2015-04-16 11:25 ` bugzilla-daemon
2015-04-19 3:59 ` bugzilla-daemon
2015-04-19 4:00 ` bugzilla-daemon
2015-04-19 4:00 ` bugzilla-daemon
2015-04-19 4:04 ` bugzilla-daemon
2015-04-19 4:05 ` bugzilla-daemon
2015-04-19 4:07 ` bugzilla-daemon
2015-04-19 4:21 ` bugzilla-daemon
2015-04-20 17:43 ` bugzilla-daemon
2015-10-10 7:30 ` 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-90601-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).