linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 71941] LSI SAS2116 does not detect disks
Date: Sat, 22 Mar 2014 14:11:54 +0000	[thread overview]
Message-ID: <bug-71941-11613-0Pe0x6M452@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71941-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=71941

kernel-bugzilla.20.drkshadow@spamgourmet.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from kernel-bugzilla.20.drkshadow@spamgourmet.com ---
The issue turned out to be hardware: Some combination of flashing the firmware
and BIOS caused all disks to register.

I did get the 18.00.00.00 driver to compile under 3.13.6, however it gave me
its own problems: as I attempted to dd if="$f" of="$f" bs=65536 across every
disk in the system simultaneously, the system would, after 20-30 minutes, lock
solid. (This process proceeded fine if of=/dev/null; I'm doing this to find
disks that I know have sector errors.) I have no dmesg output. Further,
modprobe -r was _very_ slow on this driver, eventually printing to dmesg a
trace including "warn_slowpath_fmt".

Attached is a basic patch to get the new LSI driver to compile under 3.13.6,
but no guarantees as to the quality of anything.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2014-03-22 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  7:14 [Bug 71941] New: LSI SAS2116 does not detect disks bugzilla-daemon
2014-03-22 14:11 ` bugzilla-daemon [this message]
2014-03-22 14:13 ` [Bug 71941] " 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-71941-11613-0Pe0x6M452@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).