linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Simon Gaiser <simon@invisiblethingslab.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	emmi@emmixis.net, schwagsucks@gmail.com,
	"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" 
	<linux-ide@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 217114 - Tiger Lake SATA Controller not operating correctly [bisected]
Date: Fri, 3 Mar 2023 17:12:09 +0900	[thread overview]
Message-ID: <414d105f-4197-9bef-18cf-f44d422ffd62@opensource.wdc.com> (raw)
In-Reply-To: <fa07d882-499a-4d49-8ab2-679298f16c54@leemhuis.info>

On 3/3/23 16:30, Thorsten Leemhuis wrote:
> On 03.03.23 08:10, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Hi, this is your Linux kernel regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org that apparently
>> affects 6.2 and later as well as 6.1.13 and later, as it was already
>> backported there.
>>
>> As many (most?) kernel developer don't keep an eye on bugzilla, I
>> decided to forward the report by mail. Quoting from
>> https://bugzilla.kernel.org/show_bug.cgi?id=217114 :
>>
>>>  emmi@emmixis.net 2023-03-02 11:25:00 UTC
>>>
>>> As per kernel problem found in https://bbs.archlinux.org/viewtopic.php?id=283906 ,
>>>
>>> Commit 104ff59af73aba524e57ae0fef70121643ff270e
>>
>> [FWIW: That's "ata: ahci: Add Tiger Lake UP{3,4} AHCI controller" from
>> Simon Gaiser]
> 
> BTW, there is one thing I wondered after sending above mail: was it
> really wise to merge this to mainline two days before 6.2 was released?
> Yes, the change subject's makes it sounds like this is a hardware
> enablement, but the `Mark the Tiger Lake UP{3,4} AHCI controller as
> "low_power"` at the beginning of the change description shines a
> different light on it.

Yes, I made the decision to send this patch as a "fix" rather than a change, and
that was rc8. In retrospect, maybe not the best decision. But the patch was
fixing issues for Simon, so...

Anyway, will follow this. I requested more information on Bugzilla. The issue
here is that it may be due to the device having a bad LPM support (there are
many) rather than the controller itself. Need to sort this out.



-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2023-03-03  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  7:10 [regression] Bug 217114 - Tiger Lake SATA Controller not operating correctly [bisected] Linux regression tracking (Thorsten Leemhuis)
2023-03-03  7:30 ` Thorsten Leemhuis
2023-03-03  8:12   ` Damien Le Moal [this message]
2023-03-03  9:48 ` Damien Le Moal
2023-03-03 10:38   ` Simon Gaiser
2023-03-04 13:58   ` Linux regression tracking (Thorsten Leemhuis)
2023-03-04 14:12     ` Greg KH

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=414d105f-4197-9bef-18cf-f44d422ffd62@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=emmi@emmixis.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=schwagsucks@gmail.com \
    --cc=simon@invisiblethingslab.com \
    --cc=stable@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).