All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Self <jason@bluehome.net>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Regression/boot failure on 5.16.3
Date: Fri, 4 Feb 2022 12:06:18 -0800	[thread overview]
Message-ID: <20220204120618.152ac91f@valencia> (raw)
In-Reply-To: <f0bd183125c2773afbfc9563cb4949ad055b7075.camel@sipsolutions.net>


[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]

On Fri, 04 Feb 2022 15:34:33 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:

> > 
> > The computer (amd64) fails to boot. The init was stuck at the
> > synchronization of the time through the network. This began between
> > 5.16.2 (good) and 5.16.3 (bad.) This continues on 5.16.4 and 5.16.5.
> > Git bisect revealed the following. In this case the nonfree firmwre
> > is not present on the system. Blacklisting the iwflwifi module
> > works as a workaround for now.
> > 
> > 6b5ad4bd0d78fef6bbe0ecdf96e09237c9c52cc1 is the first bad commit
> > commit 6b5ad4bd0d78fef6bbe0ecdf96e09237c9c52cc1
> >   
> 
> I checked out this commit and ran a test with no firmware present, but
> couldn't reproduce any crash.

I can confirm it still happens on 5.17-rc2. For the environment, Debian
11 with only the Main repo enabled.

lspci says:
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi
WiFi

There is also a USB WiFi attached (AR9271)

> Could you take a picture when it crashes? Perhaps boot without 'quiet'
> on the command line, or boot into recovery mode or such where you
> actually see the output?

They are attached:
* Raise network interfaces takes several seconds;
* Network Time Synchronization stuck.

[-- Attachment #1.2: Network Ttime Synchronization stuck.JPG --]
[-- Type: image/jpeg, Size: 504520 bytes --]

[-- Attachment #1.3: Raise network interfaces takes several seconds.JPG --]
[-- Type: image/jpeg, Size: 449349 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-02-04 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 14:11 Fw: Regression/boot failure on 5.16.3 Jason Self
2022-02-04 14:34 ` Johannes Berg
2022-02-04 20:06   ` Jason Self [this message]
2022-02-04 20:08     ` Jason Self
  -- strict thread matches above, loose matches on Subject: below --
2022-02-04  0:19 Jason Self
2022-02-04  7:00 ` Greg KH
2022-02-04  8:48 ` Thorsten Leemhuis
2022-02-08  8:50 ` Stefan Agner
2022-02-08 18:05   ` Jason Self
2022-02-08 18:22     ` Thorsten Leemhuis

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=20220204120618.152ac91f@valencia \
    --to=jason@bluehome.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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.