From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Peter Rosin <peda@axentia.se>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pwm@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
Thierry Reding <thierry.reding@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: Re: PWM regression causing failures with the pwm-atmel driver
Date: Wed, 24 May 2023 08:07:00 +0200 [thread overview]
Message-ID: <20230524060700.ryvnijygnitogesx@pengutronix.de> (raw)
In-Reply-To: <a2ed99b3-ee2a-6393-de98-3305c57dacc4@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Tue, May 23, 2023 at 10:42:34PM +0200, Peter Rosin wrote:
> 2023-05-23 at 01:34, Peter Rosin wrote:
> > So, I took a step back and can only conclude that there must be some
> > another regression to find, and I was confused by that other regression.
> > In short, I was on 6.1.<foo> and everything was fine, and then I bumped
> > to 6.3 and a process crashed. I went to 6.2 and that same process also
> > crashed. I then totally focused on v6.1..v6.2 to figure out the problem.
> > I simply assumed v6.3 had the same problem because the symptom from
> > 30.000ft was the same (that process died). I failed to go back to v6.3
> > to confirm that it was indeed the same problem as I had found in the
> > v6.1..v6.2 range.
> >
> > My bad, it seems I have another day of bisections lined up.
>
> For closure, I ended up with this:
> https://lore.kernel.org/lkml/221d19e2-6b92-7f38-7d8a-a730f54c33ea@axentia.se/
>
> I.e. another v6.1..v6.2 regression that caused sound failures.
> The two problems looked very similar to the suffering application.
>
> Anyway, sorry again for the noise.
OK. After your first mail I had the impression there is another PWM
releated problem to be reported, but it seems this isn't the case.
Just to have that explicit: Did I understand you right?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-24 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 20:42 PWM regression causing failures with the pwm-atmel driver Peter Rosin
2023-05-24 6:07 ` Uwe Kleine-König [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-24 7:45 Peter Rosin
2023-05-22 15:19 Peter Rosin
2023-05-22 16:25 ` Thierry Reding
2023-05-22 17:23 ` Uwe Kleine-König
2023-05-22 19:28 ` Peter Rosin
2023-05-22 20:43 ` Uwe Kleine-König
2023-05-22 23:34 ` Peter Rosin
2023-05-23 20:31 ` Thierry Reding
2023-05-24 6:37 ` Uwe Kleine-König
2023-06-20 14:24 ` Thorsten Leemhuis
2023-06-20 15:43 ` Peter Rosin
2023-06-20 16:30 ` Linux regression tracking #update (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=20230524060700.ryvnijygnitogesx@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=claudiu.beznea@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=peda@axentia.se \
--cc=regressions@leemhuis.info \
--cc=thierry.reding@gmail.com \
/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).