linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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 13:29:06 -0700	[thread overview]
Message-ID: <980597f7-5170-72f2-ec2f-efc64f5e27eb@gmail.com> (raw)
In-Reply-To: <20200512111059.GA34497@piout.net>



On 5/12/2020 4:10 AM, Alexandre Belloni wrote:
> Hi,
> 
> On 12/05/2020 06:54:29+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.
>>
> 
> I think the resolution of this issue is
> 99f81afc139c6edd14d77a91ee91685a414a1c66. If this is taken, then I think
> f5aba91d7f186cba84af966a741a0346de603cd4 should also be backported.

Agreed.
-- 
Florian

  reply	other threads:[~2020-05-12 20: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
2020-05-12 11:10   ` Alexandre Belloni
2020-05-12 20:29     ` Florian Fainelli [this message]
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=980597f7-5170-72f2-ec2f-efc64f5e27eb@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --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 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).