From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 214967] mvsas not detecting some disks
Date: Tue, 16 Nov 2021 03:08:23 +0000 [thread overview]
Message-ID: <bug-214967-11613-kpYowokcLj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214967-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214967
--- Comment #12 from Matthew Perkowski (mgperkow@gmail.com) ---
(In reply to Damien Le Moal from comment #11)
> (In reply to Matthew Perkowski from comment #8)
> > (In reply to Damien Le Moal from comment #6)
> > > (In reply to Bart Van Assche from comment #5)
> > > > On 11/15/21 2:34 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> > > > > https://bugzilla.kernel.org/show_bug.cgi?id=214967
> > > > >
> > > > > --- Comment #4 from Matthew Perkowski (mgperkow@gmail.com) ---
> > > > > Bisection has identified commit
> > 2360fa1812cd77e1de13d3cca789fbd23462b651
> > > as
> > > > > the
> > > > > origin of the issue.
> > >
> > > Hmm... It seems very strange that this patch creates the problem. Even
> with
> > > a bug, the worst that could happen is failing to detect NCQ priority
> > support.
> > >
> > > The problem is likely related to the errors "ata14.00: Read log page 0x08
> > > failed, Emask 0x1" which come from the kernel trying to access a non
> > > existent log page (IDENTIFY DEVICE data log), which is tried when probing
> > > for NCQ priority support.
> > >
> > > libata ignores this error, not enabling the feature that was being
> probed.
> > > The mvsas driver may not.
> > >
> > > I posted a patch yesterday to prevent such access to log pages not
> > supported
> > > by the device. See:
> > >
> > > https://lore.kernel.org/linux-ide/20211115060559.232835-1-damien.
> > > lemoal@opensource.wdc.com/
> > >
> > > Can you try these ?
> > >
> > >
> > > >
> > > > This commit: 2360fa1812cd ("libata: cleanup NCQ priority handling")?
> > > >
> > > > Damien, can you take a look?
> >
> > I will try rebuilding with the patches at my first opportunity and report
> > back.
>
> That would be great. Thanks.
Looks like your hunch may have been right on. I applied your patches to a fresh
copy of the 5.15.2 source (which was not working properly with my RR 2744 card
via the mvsas driver in vanilla form), and the issue did not arise when I
booted into it.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-11-16 3:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 14:08 [Bug 214967] New: mvsas not detecting some disks bugzilla-daemon
2021-11-08 16:28 ` [Bug 214967] " bugzilla-daemon
2021-11-14 0:19 ` bugzilla-daemon
2021-11-14 0:56 ` bugzilla-daemon
2021-11-15 22:34 ` bugzilla-daemon
2021-11-15 23:13 ` bugzilla-daemon
2021-11-15 23:24 ` bugzilla-daemon
2021-11-15 23:34 ` bugzilla-daemon
2021-11-15 23:53 ` bugzilla-daemon
2021-11-15 23:59 ` bugzilla-daemon
2021-11-16 0:04 ` bugzilla-daemon
2021-11-16 0:04 ` bugzilla-daemon
2021-11-16 3:08 ` bugzilla-daemon [this message]
2021-11-16 3:11 ` bugzilla-daemon
2021-11-16 3:16 ` bugzilla-daemon
2021-11-16 8:09 ` bugzilla-daemon
2021-11-16 12:29 ` bugzilla-daemon
2021-11-16 23:55 ` bugzilla-daemon
2024-02-04 21:19 ` bugzilla-daemon
2025-01-18 3:07 ` 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-214967-11613-kpYowokcLj@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.