All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	o-takashi@sakamocchi.jp
Cc: Mark Broadworth <a.mark.broadworth@gmail.com>,
	matthias.schrumpf@freenet.de, LKML <linux-kernel@vger.kernel.org>,
	aros@gmx.com,
	Linux FireWire <linux1394-devel@lists.sourceforge.net>
Subject: Re: Regression from dcadfd7f7c74ef9ee415e072a19bdf6c085159eb
Date: Tue, 7 Nov 2023 14:02:42 +0700	[thread overview]
Message-ID: <ZUnhEjtUihOFQ9t1@debian.me> (raw)
In-Reply-To: <f878b188-3fe4-420c-9bcb-b431ac6088dd@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

On Mon, Nov 06, 2023 at 02:14:39PM -0600, Mario Limonciello wrote:
> Hi,
> 
> I recently came across a kernel bugzilla that bisected a boot problem [1]
> introduced in kernel 6.5 to this change.
> 
> commit dcadfd7f7c74ef9ee415e072a19bdf6c085159eb (HEAD -> dcadfd7f7c7)
> Author: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> Date:   Tue May 30 08:12:40 2023 +0900
> 
>     firewire: core: use union for callback of transaction completion
> 
> Removing the firewire card from the system fixes it for both reporters
> (CC'ed)
> 
> As the author of this issue can you please take a look at it?
> 

Thanks for the forwarding regression report from Bugzilla. I'm adding it
to regzbot:

#regzbot introduced: dcadfd7f7c74ef https://bugzilla.kernel.org/show_bug.cgi?id=217993
#regzbot title: completing firewire transaction callback with union bootloops AMD Ryzen 7 system
#regzbot link: https://lore.kernel.org/regressions/f878b188-3fe4-420c-9bcb-b431ac6088dd@amd.com/

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-07  7:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 20:14 Regression from dcadfd7f7c74ef9ee415e072a19bdf6c085159eb Mario Limonciello
2023-11-07  7:02 ` Bagas Sanjaya [this message]
2024-01-19 14:08   ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-07 12:17 ` Takashi Sakamoto
2023-11-07 21:27   ` Mario Limonciello
2023-11-08  5:16     ` Takashi Sakamoto
2023-11-20  5:41       ` Linux regression tracking (Thorsten Leemhuis)
2023-11-28  5:24       ` Takashi Sakamoto
2023-11-28  6:09         ` Mario Limonciello
2023-12-03 12:29           ` Takashi Sakamoto
2023-12-05 20:04             ` Mario Limonciello
2023-12-10  8:02               ` Takashi Sakamoto
2024-01-16  1:49 ` Takashi Sakamoto

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=ZUnhEjtUihOFQ9t1@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=a.mark.broadworth@gmail.com \
    --cc=aros@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mario.limonciello@amd.com \
    --cc=matthias.schrumpf@freenet.de \
    --cc=o-takashi@sakamocchi.jp \
    --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.