From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0
Date: Fri, 22 Aug 2014 12:13:42 +0000 [thread overview]
Message-ID: <bug-81861-11613-rcxSV8ODsY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81861-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=81861
--- Comment #6 from linux-ide@crashplan.pro ---
When connecting just a single 4 drive group to the good ports (for example 2C)
of the external PCIe expander card:
cold boot = doesn't detect any of the 4 PUIS drives
warm boot = does detect all 4 PUIS drives
When powering up using the warm boot method there don't seem to be errors
reported by smartctl neither sg_ses.
However this cold boot issue might be a different issue from this kernel crash.
According to debug messages first a "Set Features" (0xEF) is being sent. My
guess is that this set features issues subcommand (0x07): spin up media.
And later on the "Identify Device" (0xEC) is sent.
When I correctly read the Hitachi specification the Spin Up (Set Features)
should be sent after "Drive Identify". For this Hitachi HDS5C3020BLE630 the
Drive_Identify (# sg_sat_identify -v /dev/sdb) word 2 outputs "738c" (hex),
which translates to specification "Need Set Feature for spin-up after power-up
Identify Device is complete" according to HGST specification page 127.
Is there a boot parameter (or similar way) to load the mvsas driver without
sending the "Set Features" (0xEF) command?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-22 12:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 17:33 [Bug 81861] New: mvsas.ko v0.8.16 error messages and kernel crashes attaching 4 SATA drives to specific HP SAS expander ports bugzilla-daemon
2014-08-07 20:29 ` [Bug 81861] " bugzilla-daemon
2014-08-08 8:19 ` bugzilla-daemon
2014-08-08 8:24 ` [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0 bugzilla-daemon
2014-08-08 8:34 ` bugzilla-daemon
2014-08-12 20:09 ` bugzilla-daemon
2014-08-12 22:02 ` bugzilla-daemon
2014-08-21 18:35 ` bugzilla-daemon
2014-08-22 12:13 ` bugzilla-daemon [this message]
2014-08-22 12:16 ` bugzilla-daemon
2014-08-22 12:17 ` bugzilla-daemon
2014-08-22 13:19 ` bugzilla-daemon
2014-08-22 14:05 ` bugzilla-daemon
2014-08-22 17:00 ` bugzilla-daemon
2014-08-22 17:36 ` bugzilla-daemon
2014-08-23 20:04 ` bugzilla-daemon
2014-08-23 20:06 ` bugzilla-daemon
2014-08-23 22:12 ` bugzilla-daemon
2014-09-23 21:56 ` bugzilla-daemon
2014-09-24 0:32 ` Elliott, Robert (Server Storage)
2014-09-26 7:04 ` bugzilla-daemon
2014-10-19 15:56 ` bugzilla-daemon
2014-12-17 19:49 ` bugzilla-daemon
2015-01-26 23:19 ` bugzilla-daemon
2015-01-26 23:20 ` bugzilla-daemon
2015-01-26 23:21 ` bugzilla-daemon
2015-04-23 11:31 ` bugzilla-daemon
2015-04-29 13:40 ` bugzilla-daemon
2015-04-29 14:20 ` James Bottomley
[not found] ` <CAC2CY-2YAy8GfjCHO+PrFWAuBnhfnMvK33KJ3YCVRZXJMEHykQ@mail.gmail.com>
2015-04-29 15:41 ` James Bottomley
2015-04-29 16:24 ` Adam Talbot
2015-04-29 18:05 ` James Bottomley
2015-04-29 18:07 ` Adam Talbot
2015-04-29 18:10 ` James Bottomley
2015-04-29 19:09 ` Nathan Rennie-Waldock
2015-10-05 0:07 ` Nathan Rennie-Waldock
2015-04-29 13:41 ` 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-81861-11613-rcxSV8ODsY@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 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.