All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, hch@lst.de,
	m.szyprowski@samsung.com,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!)
Date: Thu, 15 Dec 2022 20:23:59 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2212152017110.3532114@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <CABXGCsPnpu0TGHnvXM1we7q1t3tJAOYW2rA=AMvf7ZahcYvpRQ@mail.gmail.com>

Hi,

On Thu, 15 Dec 2022, Mikhail Gavrilov wrote:

> The kernel 6.2 preparation cycle has begun and yesterday after the
> kernel was updated on my Fedora Rawhide all audio devices disappeared.

I can confirm this breaks audio in our SOF tests if I cherry-pick the 
identified patch ffcb754584603a to sound tree. This affects audio on a 
very large number of x86 systems.

Br, Kai

WARNING: multiple messages have this Message-ID (diff)
From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org, hch@lst.de,
	m.szyprowski@samsung.com
Subject: Re: [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!)
Date: Thu, 15 Dec 2022 20:23:59 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2212152017110.3532114@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <CABXGCsPnpu0TGHnvXM1we7q1t3tJAOYW2rA=AMvf7ZahcYvpRQ@mail.gmail.com>

Hi,

On Thu, 15 Dec 2022, Mikhail Gavrilov wrote:

> The kernel 6.2 preparation cycle has begun and yesterday after the
> kernel was updated on my Fedora Rawhide all audio devices disappeared.

I can confirm this breaks audio in our SOF tests if I cherry-pick the 
identified patch ffcb754584603a to sound tree. This affects audio on a 
very large number of x86 systems.

Br, Kai

  reply	other threads:[~2022-12-15 18:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 14:17 [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!) Mikhail Gavrilov
2022-12-15 18:23 ` Kai Vehmanen [this message]
2022-12-15 18:23   ` Kai Vehmanen
2022-12-16  0:06 ` Joan Bruguera
2022-12-16  6:46 ` Christoph Hellwig
2022-12-16  6:46   ` Christoph Hellwig
2022-12-16 11:40   ` Robin Murphy
2022-12-16 11:40     ` Robin Murphy
2022-12-16 12:15     ` Christoph Hellwig
2022-12-16 12:15       ` Christoph Hellwig
2022-12-16 12:52       ` Robin Murphy
2022-12-16 12:52         ` Robin Murphy
2022-12-22 12:17 ` [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!) #forregzbot Thorsten Leemhuis
2022-12-24  7:20   ` Thorsten Leemhuis
     [not found] <CABXGCsPnpu0TGHnvXM1we7q1t3tJAOYW2rA=>
2022-12-15 23:52 ` [6.2][regression] after commit ffcb754584603adf7039d7972564fbf6febdc542 all sound devices disappeared (due BUG at mm/page_alloc.c:3592!) Joan Bruguera

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=alpine.DEB.2.22.394.2212152017110.3532114@eliteleevi.tm.intel.com \
    --to=kai.vehmanen@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=tiwai@suse.de \
    /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.