[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <D54AL6MM062P.3HR3L0TZ9ERII@cknow.org>
Date: Thu, 24 Oct 2024 21:44:13 +0200
From: "Diederik de Haas" <didi.debian@...ow.org>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>
Cc: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>, "Arnd Bergmann"
<arnd@...db.de>, "Armin Wolf" <W_Armin@....de>, "Guenter Roeck"
<linux@...ck-us.net>, "Vinod Koul" <vkoul@...nel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: Error "ee1004 3-0050: probe with driver ee1004 failed with
error -5" since 6.11
Hi Uwe,
On Mon Oct 7, 2024 at 4:38 PM CEST, Uwe Kleine-König wrote:
> On Sat, Sep 28, 2024 at 08:54:12AM +0200, Diederik de Haas wrote:
> > On Fri Sep 27, 2024 at 11:59 PM CEST, Uwe Kleine-König wrote:
> > > [ extensive description on what to do when git bisect results
> > > in a merge commit as 'first bad commit' ]
> >
> > This is awesome, thank you very much :)
>
> Were you able to understand that, or did you just bookmark it for the
> next time? If you still have questions, don't hesitate to ask.
Thanks for the offer :)
> > I haven't made up my mind yet whether I'll apply it to this specific
> > issue. It doesn't cause any actual problems (AFAICT) and most
> > importantly, it seems to be fixed in 6.12(-rc1) already.
> > And the 6.11 kernel is only a 'temporary' one which I don't care (much)
> > about, while it is fixed in the kernel I do care about (6.12).
>
> It might be beneficial to find the commit between 6.11 and 6.12-rc1
> that's fixing the issue. That would allow to backport the fix to 6.11.x.
Today I finally had time to try it out ... to find I can no longer
reproduce it. At least not reliably. I've seen the error message once
with 6.11-rc1 today, but not since. When I now boot 6.11-rc1, I do not
see it and I've rebooted several times.
I did upgrade the BIOS to a new (beta) version since my previous
attempts, which may play a factor? But that seems like a minor change.
So it could be that my previous bisect operation wasn't reliable either.
The issue wasn't a big deal to begin with but mostly interesting to
enhance my git bisect skills. But now that I can't reliably reproduce
the issue, that makes even that moot.
So I'm hereby stopping my attempts to bisect this issue.
Cheers,
Diederik
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists