linux-scsi.vger.kernel.org archive mirror
 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: Fri, 22 Sep 2023 17:28:08 +0000	[thread overview]
Message-ID: <bug-215788-11613-DtmMrKj07L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215788-11613@https.bugzilla.kernel.org/>

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

Damien Le Moal (damien.lemoal@wdc.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.petersen@oracle.com

--- Comment #21 from Damien Le Moal (damien.lemoal@wdc.com) ---
(In reply to Ken Link from comment #18)
> I am also experiencing this, on an Areca 1882ix-24 with firmware V1.56
> 2021-01-12 and arcmsr driver version v1.50.0X.14-20230614 in Ubuntu 22.04 on
> kernel 6.2.0. I take it the 5.18/discovery branch hasn't been merged
> anywhere yet? What more testing needs to be done? How can I help?

I do not recall if the discovery branch was applied. Would need to check again.
Given that 6.2 kernel is not LTS and I am not sure what kind of patching Ubuntu
does, could you try with the latest stable (6.5.4) or latest mainline (6.6-rc2)
?

Martin,

Did you apply that 5.18/discovery branch mentioned above ? It does not look
like t is applied.

-- 
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:[~2023-09-22 17:28 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
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 [this message]

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-DtmMrKj07L@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;
as well as URLs for NNTP newsgroup(s).