public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 218035] New: Adaptec 7805H (pm80xx) hangs even on light I/O with some Seagate HDDs
Date: Sun, 22 Oct 2023 12:43:41 +0000	[thread overview]
Message-ID: <bug-218035-11613@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 218035
           Summary: Adaptec 7805H (pm80xx) hangs even on light I/O with
                    some Seagate HDDs
           Product: IO/Storage
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: nickosbarkas@gmail.com
        Regression: No

Created attachment 305277
  --> https://bugzilla.kernel.org/attachment.cgi?id=305277&action=edit
pm80xx hangs with Exos 7E2

Hello guys,
this is an old issue that happens when reading/writing data on specific
 Seagate SAS HDDs on a pm80xx based adapter.

Affected models:
ST2000NM0045 (Constellation ES.3)
ST4000NM0023 (Enterprise Capacity v5 or Exos 7E2)

Please note that neither the disks nor the adapter are defective, they work
fine. The disks have the latest available microcode installed, but the issue
occurred with the factory microcode too. 

Even with very small sequential or random I/O, the driver enters into a not
workable state.

linux-scsi thread for this issue:
https://www.spinics.net/lists/linux-scsi/msg116653.html


I have uploaded a dmesg excerpt with debug logging that shows what happens when
I run a random i/o test with 128k block reads with 32 threads for 1 minute.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2023-10-22 12:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-218035-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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