public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>, "Armin Wolf" <W_Armin@gmx.de>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Vinod Koul" <vkoul@kernel.org>,
	"Diederik de Haas" <didi.debian@cknow.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Error "ee1004 3-0050: probe with driver ee1004 failed with error -5" since 6.11
Date: Sat, 28 Sep 2024 08:54:12 +0200	[thread overview]
Message-ID: <D4HPXGCB5GGE.1KQFZR61CHMVF@cknow.org> (raw)
In-Reply-To: <sr6p4lwnlznee73t4jof537dcwdl6m6vxriwk3pk4dnlxyaih4@6wv52esrfpyq>

[-- Attachment #1: Type: text/plain, Size: 2601 bytes --]

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


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-09-28  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 12:35 Error "ee1004 3-0050: probe with driver ee1004 failed with error -5" since 6.11 Diederik de Haas
2024-09-26 12:44 ` Greg Kroah-Hartman
2024-09-27 12:57   ` Diederik de Haas
2024-09-27 21:59     ` Uwe Kleine-König
2024-09-28  6:54       ` Diederik de Haas [this message]
2024-10-07 14:38         ` Uwe Kleine-König
2024-10-24 19:44           ` Diederik de Haas

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=D4HPXGCB5GGE.1KQFZR61CHMVF@cknow.org \
    --to=didi.debian@cknow.org \
    --cc=W_Armin@gmx.de \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=u.kleine-koenig@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox