All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 215788] arcmsr driver on kernel 5.16 and up fails to initialize ARC-1280ML RAID controller
Date: Wed, 06 Apr 2022 08:26:33 +0000	[thread overview]
Message-ID: <bug-215788-11613-nd5G5m1pF9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215788-11613@https.bugzilla.kernel.org/>

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

--- Comment #7 from Damien Le Moal (damien.lemoal@wdc.com) ---
On Wed, 2022-04-06 at 06:59 +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215788
> 
> --- Comment #6 from Jernej Simončič (jernej-bugzilla.kernel@ena.si) ---
> Doesn't help unfortunately.

Hmm... And everything is OK if you comment out that function call ?

Can you post the output of these commands for the RAID disk ?

sg_inq /dev/sdX
sg_inq --vpd /dev/sdX
sg_vpd -E /dev/sdX
sg_logs -l -l /dev/sdX

And then last:

sg_vpd --force --page=0xb9 /dev/sdX

This last command could be the one crashing the HBA/drive so beware.
Your drive clearly should not be supporting vpd page 0xb9, so
sd_read_cpr() should be a nop, doing nothing. It does not seem to be
the case. Maybe this adapter uses page 0xb9 as a vendor specific one,
causing problems. The above commands will allow checking that.

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

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

  parent reply	other threads:[~2022-04-06 11:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 10:50 [Bug 215788] New: arcmsr driver on kernel 5.16 and up fails to initialize ARC-1280ML RAID controller bugzilla-daemon
2022-04-01 11:00 ` [Bug 215788] " bugzilla-daemon
2022-04-02  7:56 ` bugzilla-daemon
2022-04-05  5:08 ` bugzilla-daemon
2022-04-05 19:44 ` bugzilla-daemon
2022-04-05 19:51 ` bugzilla-daemon
2022-04-05 23:29 ` bugzilla-daemon
2022-04-06  6:59 ` bugzilla-daemon
2022-04-06  8:26 ` bugzilla-daemon [this message]
2022-04-06 16:35 ` bugzilla-daemon
2022-04-06 16:43 ` bugzilla-daemon
2022-04-06 22:49 ` bugzilla-daemon
2022-04-07  4:01 ` bugzilla-daemon
2022-04-07  7:10 ` bugzilla-daemon
2022-04-07  7:20   ` Damien Le Moal
2022-04-07  7:18 ` bugzilla-daemon
2022-04-07  7:20 ` bugzilla-daemon
2022-04-21  6:52 ` bugzilla-daemon
2022-04-25  2:28 ` bugzilla-daemon
2022-04-25 14:17 ` bugzilla-daemon
2023-09-21 21:13 ` bugzilla-daemon
2023-09-22  8:32 ` bugzilla-daemon
2023-09-22 13:49 ` bugzilla-daemon
2023-09-22 17:28 ` 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-215788-11613-nd5G5m1pF9@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 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.