All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	parthiban@linumiz.com, saravanan@linumiz.com,
	'karthikeyan' <karthikeyan@linumiz.com>,
	"bumyong.lee" <bumyong.lee@samsung.com>,
	'Linux regressions mailing list' <regressions@lists.linux.dev>
Subject: Re: dmaengine: CPU stalls while loading bluetooth module
Date: Tue, 26 Mar 2024 14:50:05 +0100	[thread overview]
Message-ID: <8734a80b-c7a9-4cc2-91c9-123b391d468c@leemhuis.info> (raw)
In-Reply-To: <9490757c-4d7c-4d8b-97e2-812a237f902b@leemhuis.info>

Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.

Vinod Koul, what's your option here? We have two reports about
regressions caused by 22a9d958581244 ("dmaengine: pl330: issue_pending
waits until WFP state") [v6.8-rc1] now:

https://lore.kernel.org/lkml/1553a526-6f28-4a68-88a8-f35bd22d9894@linumiz.com/

https://lore.kernel.org/all/ZYhQ2-OnjDgoqjvt@wens.tw/
[the first link points to the start of this thread]

To me it sounds like this is a change that better should be reverted,
but you are of course the better judge here.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

On 20.03.24 07:28, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 20.03.24 01:49, bumyong.lee wrote:
>>>>> Hmmm. 6.8 final is due. Is that something we can live with? Or would
>>>>> it be a good idea to revert above commit for now and reapply it when
>>>>> something better emerged? I doubt that the answer is "yes, let's do
>>>>> that", but I have to ask.
>>>>
>>>> I couldn't find better way now.
>>>> I think it's better to follow you mentioned
>>>
>>> 6.8 is out, but that issue afaics was not resolved, so allow me to ask:
>>> did "submit a revert" fell through the cracks or is there some other
>>> solution in the works? Or am I missing something?
>>
>> "submit a revert" would fix the issue. but it would make another issue
>> that the errata[1] 719340 described.
> 
> "Make" as it "that other issue was present before the culprit was
> applied"? Then that other issue does not matter due to the "no
> regression" rule and how Linus afaics wants to see it applied in
> practice. For details on the latter, see the quotes from him here:
> https://docs.kernel.org/process/handling-regressions.html
>  Hence please submit a revert (or tell me if I misunderstood something)
> -- or of course a workaround for the other issue that does not cause the
> regression people reported.
> 
>> [...]
>> [1]: https://developer.arm.com/documentation/genc008428/latest
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
> 
> 
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot poke

  reply	other threads:[~2024-03-26 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240305062038epcas2p143c5e1e725d8a934b0208266a2f78ccb@epcas2p1.samsung.com>
2024-03-05  6:20 ` dmaengine: CPU stalls while loading bluetooth module karthikeyan
2024-03-05  7:13   ` bumyong.lee
2024-03-08  8:51     ` Linux regression tracking (Thorsten Leemhuis)
2024-03-08 10:07       ` bumyong.lee
2024-03-19  9:07         ` Linux regression tracking (Thorsten Leemhuis)
2024-03-20  0:49           ` bumyong.lee
2024-03-20  6:28             ` Linux regression tracking (Thorsten Leemhuis)
2024-03-26 13:50               ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-03-28  6:51                 ` Vinod Koul
2024-03-28 15:06                   ` Linux regression tracking (Thorsten Leemhuis)
2024-04-25 10:03                     ` Thorsten Leemhuis
2024-04-29  4:49                       ` Vinod Koul
2024-04-29  4:58                         ` Linux regression tracking (Thorsten Leemhuis)

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=8734a80b-c7a9-4cc2-91c9-123b391d468c@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bumyong.lee@samsung.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=karthikeyan@linumiz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parthiban@linumiz.com \
    --cc=regressions@lists.linux.dev \
    --cc=saravanan@linumiz.com \
    --cc=vkoul@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.