linux-kernel - Re: Error "ee1004 3-0050: probe with driver ee1004 failed with error -5" since 6.11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <D4HPXGCB5GGE.1KQFZR61CHMVF@cknow.org>
Date: Sat, 28 Sep 2024 08:54:12 +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>, "Diederik de Haas"
 <didi.debian@...ow.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 Fri Sep 27, 2024 at 11:59 PM CEST, Uwe Kleine-König wrote:
> On Fri, Sep 27, 2024 at 02:57:30PM +0200, Diederik de Haas wrote:
> > On Thu Sep 26, 2024 at 2:44 PM CEST, Greg Kroah-Hartman wrote:
> > > On Thu, Sep 26, 2024 at 02:35:05PM +0200, Diederik de Haas wrote:
> > > > I updated an amd64 machine to (Debian's) 6.11 kernel and got this error:
> > > > ``ee1004 3-0050: probe with driver ee1004 failed with error -5``
> > > > 
> > > > which I didn't get with 6.10.9.
> > >
> > > bisect would be great, thanks!
> > 
> > $ git bisect log
> > git bisect start
> > # status: waiting for both good and bad commits
> > # good: [6150e5e1ae2d8ad72f52217f8f41fe446cae9e27] eeprom: ee1004: Instantiate jc42 devices for DIMMS implementing Rev.1 SPD
> > git bisect good 6150e5e1ae2d8ad72f52217f8f41fe446cae9e27
> > # status: waiting for bad commit, 1 good commit known
> > # bad: [8400291e289ee6b2bf9779ff1c83a291501f017b] Linux 6.11-rc1
> > ... [omitted for brevity] ...
> > # bad: [7a46b17d4c00c2547b5bd82eec9489b19128fd65] Merge tag 'dmaengine-6.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine
> > git bisect bad 7a46b17d4c00c2547b5bd82eec9489b19128fd65
> > # first bad commit: [7a46b17d4c00c2547b5bd82eec9489b19128fd65] Merge tag 'dmaengine-6.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine
>
> The following is completely generic. Note I didn't try to to understand
> the problem, just giving some hint how to further improve the bisection
> result.
>
> [ 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 :)

I already thought that this git bisect result wasn't very useful as I
failed to see the logic of dmaengine changes being relevant for this
issue.
And I (indeed) didn't know what to do when a git bisect resulted in a
merge commit as 'first bad commit', so your description will surely come
in handy (someday).

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).

So if there isn't a follow up from me on this issue, it certainly is NOT
related to your message, which I appreciate a LOT :-)
(And I'm pretty sure there'll be other instances where a git bisect
results in a merge commit ...)

Cheers,
  Diederik


Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)