public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Regressions <regressions@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Broadcom 80211 Devices <brcm80211-dev-list.pdl@broadcom.com>,
	SHA cyfmac Subsystem <SHA-cyfmac-dev-list@infineon.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Cc: Hante Meuleman <hante.meuleman@broadcom.com>,
	Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
	Franky Lin <franky.lin@broadcom.com>,
	Arend van Spriel <arend.vanspriel@broadcom.com>,
	Kalle Valo <kvalo@kernel.org>,
	julien.falque@gmail.com
Subject: Fwd: Freeze after resuming from hibernation (culprit is brcmfmac change?)
Date: Mon, 15 May 2023 09:21:38 +0700	[thread overview]
Message-ID: <018f62d0-ee1d-9198-9c38-e45b10921e2e@gmail.com> (raw)

Hi,

I notice a regression report on bugzilla [1]. Quoting from it:

>  julien.falque@gmail.com 2023-05-14 09:55:38 UTC
> 
> Since a Kernel update a few weeks ago, my laptop freezes when resuming from hibernation. It seems to handle the resume process normally but at the moment I should see Gnome login screen, I either get a black screen with just a white underscore instead, or nothing displayed at all (no backlight). I can't do anything at that point and I have to hard reboot.
> 
> Steps to reproduce:
> - hibernate
> - resume
> - wait until the resuming process should finish: black screen instead of e.g. Gnome's login screen
> 
> journalctl gives nothing between the beginning of the resume and the crash, as if it never happened.
> 
> I have a Dell XPS 15 (9550) with Arch Linux. The issue happens on linux (since v6.2.0 I think) but linux-lts (currently v6.1.28) is fine.
> 
> A bisect on linux-git gave commit da6d9c8ecd00 as the cause of the problem.

See bugzilla for the full thread.

Julien: I asked you to also provide dmesg log as I don't know
what exactly happened, but you mentioned the culprit was
da6d9c8ecd00e2 ("wifi: brcmfmac: add firmware vendor info in driver info"),
which implies that the crash involves your wifi device. From my experience
though, GDM crashes are usually caused by xwayland.

Anyway, I'm adding this to regzbot:

#regzbot introduced: da6d9c8ecd00e2 https://bugzilla.kernel.org/show_bug.cgi?id=217442
#regzbot title: brcmfmac firmware vendor info addition triggers GDM crash on resuming from hibernation

Thanks. 

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217442

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-05-15  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  2:21 Bagas Sanjaya [this message]
2023-05-15  8:56 ` Fwd: Freeze after resuming from hibernation (culprit is brcmfmac change?) Hans de Goede
2023-05-15 13:09   ` Bagas Sanjaya
2023-05-15 16:43     ` Linux regression tracking (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=018f62d0-ee1d-9198-9c38-e45b10921e2e@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=SHA-cyfmac-dev-list@infineon.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=julien.falque@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pieter-paul.giesberts@broadcom.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox