From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: stable/linux-4.4.y bisection: baseline.login on at91-sama5d4_xplained
Date: Tue, 12 May 2020 10:27:44 +0200 [thread overview]
Message-ID: <20200512082744.GB3526567@kroah.com> (raw)
In-Reply-To: <2db7e52e-86ae-7c87-1782-8c0cafcbadd8@collabora.com>
On Tue, May 12, 2020 at 06:54:29AM +0100, Guillaume Tucker wrote:
> Please see the bisection report below about a boot failure.
>
> Reports aren't automatically sent to the public while we're
> trialing new bisection features on kernelci.org but this one
> looks valid.
>
> It appears to be due to the fact that the network interface is
> failing to get brought up:
>
> [ 114.385000] Waiting up to 10 more seconds for network.
> [ 124.355000] Sending DHCP requests ...#
> ..#
> .#
> timed out!
> [ 212.355000] IP-Config: Reopening network devices...
> [ 212.365000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> #
>
>
> I guess the board would boot fine without network if it didn't
> have ip=dhcp in the command line, so it's not strictly a kernel
> boot failure but still an ethernet issue.
>
> There wasn't any failure reported by kernelci on linux-4.9.y so
> maybe this patch was applied by mistake on linux-4.4.y but I
> haven't investigated enough to prove this.
It wasn't applied "by mistake", as the commit log for this says it
resolves an issue that was created in 2c7b49212a86 ("phy: fix the use of
PHY_IGNORE_INTERRUPT") which was in 3.11.
I'll go revert this now, as regressions are not good, perhaps some other
change that happened between 4.5 and 4.9 in this area keeps the error
you are seeing from happening.
thanks,
greg k-h
next prev parent reply other threads:[~2020-05-12 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5eb8399a.1c69fb81.c5a60.8316@mx.google.com>
2020-05-12 5:54 ` stable/linux-4.4.y bisection: baseline.login on at91-sama5d4_xplained Guillaume Tucker
2020-05-12 8:27 ` Greg Kroah-Hartman [this message]
2020-05-12 11:10 ` Alexandre Belloni
2020-05-12 20:29 ` Florian Fainelli
2020-05-12 21:15 ` Sasha Levin
2020-05-15 8:14 ` Henri Rosten
2020-05-15 8:38 ` Henri Rosten
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=20200512082744.GB3526567@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.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.