https://bugzilla.kernel.org/show_bug.cgi?id=214967 Damien Le Moal (damien.lemoal@xxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damien.lemoal@xxxxxxx --- Comment #6 from Damien Le Moal (damien.lemoal@xxxxxxx) --- (In reply to Bart Van Assche from comment #5) > On 11/15/21 2:34 PM, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=214967 > > > > --- Comment #4 from Matthew Perkowski (mgperkow@xxxxxxxxx) --- > > 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@xxxxxxxxxxxxxxxxxx/ Can you try these ? > > This commit: 2360fa1812cd ("libata: cleanup NCQ priority handling")? > > Damien, can you take a look? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
