All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>, xiangfeix.ma@intel.com
Subject: Re: Call Trace when adding vCPU to guest
Date: Wed, 10 Apr 2024 15:38:09 +0200	[thread overview]
Message-ID: <87bk6h49tq.ffs@tglx> (raw)
In-Reply-To: <b4929457-23b8-4ad4-8324-cc1cde5ecece@leemhuis.info>

On Wed, Apr 10 2024 at 09:34, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> I noticed a report about a regression in bugzilla.kernel.org.
>
> Thomas, I wonder if it's caused by your topology changes. But it's just
> a wild guess and I might be totally wrong there, so feel free to ignore
> this mail. I already asked for a bit more log output and a bisection in
> the ticket.
>
> To quote from https://bugzilla.kernel.org/show_bug.cgi?id=218698
>
>> Environment:
>> 
>> Host OS: CentOS 9
>> Host kernel: 6.9.0-rc1
>> KVM commit: 9bc60f73
>> Qemu commit: e5c6528d
>> Guest kernel: 6.9-rc2
>> Guest commit: 39cd87c4eb2b893354f3b850f916353f2658ae6f
>> Guest repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> 
>> 
>> Bug detail description: 
>> 
>> When hot adding a vCPU to the guest, the guest happens Call Trace and reboot.

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=a9025cd1c673a8d6eefc79d911075b8b452eba8f

It'll be in rc4

Thanks,

        tglx

  reply	other threads:[~2024-04-10 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  7:34 Call Trace when adding vCPU to guest Linux regression tracking (Thorsten Leemhuis)
2024-04-10 13:38 ` Thomas Gleixner [this message]
2024-04-10 13:48   ` Thorsten Leemhuis
2024-04-10 14:52     ` Thomas Gleixner
2024-04-10 16:25       ` Linux regression tracking (Thorsten Leemhuis)
2024-04-10 17:29         ` 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=87bk6h49tq.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=xiangfeix.ma@intel.com \
    /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.