stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Heusel <christian@heusel.eu>, regressions@lists.linux.dev
Cc: Tim Teichmann <teichmanntim@outlook.de>,
	x86@kernel.org, stable@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] Scheduling errors with the AMD FX 8300 CPU
Date: Sat, 25 May 2024 00:24:52 +0200	[thread overview]
Message-ID: <87r0dqdf0r.ffs@tglx> (raw)
In-Reply-To: <7skhx6mwe4hxiul64v6azhlxnokheorksqsdbp7qw6g2jduf6c@7b5pvomauugk>

Christian!

On Fri, May 24 2024 at 23:23, Christian Heusel wrote:
> Tim reports a regression on his AMD FX 8300 CPU that causes him
> scheduling errors (see dmesg below), initially on the latest stable
> kernel from Arch Linux. The issue reproduces by simply booting the
> kernel on his hardware. He also reported some ATA related errors (also
> attached below the dmesg), of which I dont know whether they are
> relevant or not.

I've earmarked this but I wont be able to look at it before monday. 

> May 23 23:36:49 archlinux kernel: smp: Bringing up secondary CPUs ...

Can you please provide the full boot log as the information which leads
up to the symptom is obviously more interesting than the symptom itself.

> May 23 23:36:49 archlinux kernel: smpboot: x86: Booting SMP configuration:
> May 23 23:36:49 archlinux kernel: .... node  #0, CPUs:      #2 #4 #6
> May 23 23:36:49 archlinux kernel: __common_interrupt: 2.55 No irq handler for vector
> May 23 23:36:49 archlinux kernel: __common_interrupt: 4.55 No irq handler for vector
> May 23 23:36:49 archlinux kernel: __common_interrupt: 6.55 No irq handler for vector
>
> ATA stuff:
>
> May 23 23:36:59 archlinux kernel: ata2.00: exception Emask 0x10 SAct 0x1fffe000 SErr 0x40d0002 action 0xe frozen

That's probably just the fallout of the above.

Thanks,

        tglx


  reply	other threads:[~2024-05-24 22:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 21:23 [REGRESSION][BISECTED] Scheduling errors with the AMD FX 8300 CPU Christian Heusel
2024-05-24 22:24 ` Thomas Gleixner [this message]
2024-05-25  0:12   ` Christian Heusel
2024-05-27 10:06     ` Thomas Gleixner
2024-05-27 12:35       ` Tim Teichmann
2024-05-27 15:01         ` Thomas Gleixner
2024-05-27 16:36           ` Tim Teichmann
2024-05-27 17:17             ` Thomas Gleixner
2024-05-28 15:43               ` Tim Teichmann
2024-05-28 19:15                 ` Thomas Gleixner
2024-05-28 19:17                   ` Jens Axboe
2024-05-28 20:19                     ` Niklas Cassel
2024-05-29 13:02                       ` Tim Teichmann
2024-05-29 18:33                         ` Niklas Cassel
2024-05-29 22:59                           ` Tim Teichmann
2024-05-28 20:19                   ` [PATCH] x86/topology/amd: Evaluate SMT in CPUID leaf 0x8000001e only on family 0x17 and greater Thomas Gleixner
2024-05-28 20:21                   ` [PATCH Resend] " Thomas Gleixner
2024-05-29  9:25 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2024-05-30 14:06 ` tip-bot2 for Thomas Gleixner

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=87r0dqdf0r.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=christian@heusel.eu \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=teichmanntim@outlook.de \
    --cc=x86@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).