regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: adel.ks@zegrapher.com
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Kernel 5.12.10 and 5.12.9 freezing after boot-up with while sound output is looping
Date: Mon, 14 Jun 2021 07:17:45 +0200	[thread overview]
Message-ID: <YMbmeRH38Wp6BHPf@kroah.com> (raw)
In-Reply-To: <d086de2a793eb2ea52acb11ed143675c@zegrapher.com>

On Sun, Jun 13, 2021 at 08:19:37PM +0200, adel.ks@zegrapher.com wrote:
> Hello,
> 
> I am encountering an issue where my system freezes entirely after a random
> but short time after boot-up: the computer does not react to any user input,
> be it mouse, keyboard or plugging-unplugging peripherals.  The image on
> screen remains still and does not go black. Any sound that was playing at
> the moment of the freeze loops indefinitely with a period of around 1s. I
> have the intuition that the issue is sound related because of that.
> 
> Some additional information with this issue
> - Only happens only with the latest stable releases of the kernel:  5.12.9
> and 5.12.10 . 5.12.8  does not have this issue. I have not tested other
> kernel version, e.g. LTS 5.10 , to see if it's a change that got
> back-ported.

Any chance you can run 'git bisect' to find the offending change?
That's the easiest way to fix this up.

thanks,

greg k-h

  reply	other threads:[~2021-06-14  5:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 18:19 Kernel 5.12.10 and 5.12.9 freezing after boot-up with while sound output is looping adel.ks
2021-06-14  5:17 ` Greg KH [this message]
2021-06-14  9:03   ` Adel Kara Slimane
2021-06-14 11:47     ` adel.ks
2021-06-14 13:58       ` Greg KH
2021-06-14 15:12         ` adel.ks
2021-06-14 19:54           ` adel.ks
2021-06-15 17:10             ` adel.ks
2021-07-01 16:54               ` adel.ks

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=YMbmeRH38Wp6BHPf@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adel.ks@zegrapher.com \
    --cc=regressions@lists.linux.dev \
    --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).