IronPort-SDR: a7SB3qEGM1rkE0RD3FLc9FLLzgs/+3VcPSeUx/duCTfhn+95L5MiTwUgB4Y0fkuGFzWnKE5dyJ
 mwBcdHWH9hz5Dbd9kilYOL9P0mAqngGLoqhqSVUs1VZbvGynejJOP1lq3Ixhek9n/TV561BqM1
 BkA1QxYa7iV3UpPZSiZs9RPkA9cuCD+SJWW3ysQYp8Pon1DP3Sn1svExTP1/Yh5nPlTmB7SOE6
 2tbO/0UCqRFntBKVDHj0pEQbdzz7Fdqw5LYCOllavvp4CFcEPM514Wo4Gc1Vn7YyvsT+IIqfMK
 x58=
IronPort-SDR: 61o9yE0Dqz0Os4t5sFC0k3dbFymDPjOsTKuNZqqSfsYesttaZX1XB3tWMQst5UXwGB/O8rGIOz
 7cd+6O5jKQCe9/+COM+nqr8tVLV6hLbx753JgDp3p8zrJRFzovB6wWDmQieTr1QDr2hbd4dUWe
 g8jKZgTz0LvRWwt3CfMj2IuRu551vEWW9q08Pa/cjzpY8/4Poadsm0em+Hg0mM9NEAIXvEf1Ys
 99dTjURyShBVrhqatGpN0zV5Rtu/Fq96oJHZcyZ/9DgOEfXIzt3F74zOgeL/QrXHF3gk8m7THB
 GXc=
WDCIronportException: Internal
Message-ID: <414d105f-4197-9bef-18cf-f44d422ffd62@opensource.wdc.com>
Date:   Fri, 3 Mar 2023 17:12:09 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Subject: Re: [regression] Bug 217114 - Tiger Lake SATA Controller not
 operating correctly [bisected]
Content-Language: en-US
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>
References: <ad02467d-d623-5933-67e0-09925c185568@leemhuis.info>
 <fa07d882-499a-4d49-8ab2-679298f16c54@leemhuis.info>
From:   Damien Le Moal <damien.lemoal@opensource.wdc.com>
Organization: Western Digital Research
In-Reply-To: <fa07d882-499a-4d49-8ab2-679298f16c54@leemhuis.info>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

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