mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-kernel@vger.kernel.org, jforbes@redhat.com, rppt@kernel.org
Subject: Re: Kernel crash while doing chroot'ed grub2-mkconfig on qemu-emulated Nehalem CPU since late November 6.13 snapshot
Date: Sun, 05 Jan 2025 23:09:21 -0800	[thread overview]
Message-ID: <6414e871b2c9800c3ffa2245c73eb5d039d4eda7.camel@redhat.com> (raw)
In-Reply-To: <Z3iUBbvKPdW80yMs@bombadil.infradead.org>

On Fri, 2025-01-03 at 17:51 -0800, Luis Chamberlain wrote:

> On Thu, Jan 02, 2025 at 12:16:03PM -0800, Adam Williamson wrote:
> > 
> > I have emailed the author and reviewer of
> > 5185e7f9f3bd754ab60680814afd714e2673ef88 (also CCed on this mail) but
> > have not heard back from them yet. I've sunk over a week into this bug
> > at this point so it'd be great if someone could look at it. It's not
> > the biggest regression in the world, but it is a bit awkward for our
> > automated testing (I'll have to fiddle around to try and set CPU model
> > 'host' for the most badly-affected tests but ensure we still have
> > enough tests with 'nehalem' to confirm our baseline isn't moved).
> > 
> > Thanks, and happy new year!
> 
> Can you test this:
> 
> https://lore.kernel.org/lkml/20250103065631.26459-1-jgross@suse.com/T/#u                                                                                                                      
> 
>   Luis
> 
Hi Luis! Unfortunately, it doesn't look like it helps. The crashes
still happen.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net





  parent reply	other threads:[~2025-01-06  7:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 16:51 Adam Williamson
2025-01-02 20:16 ` Adam Williamson
2025-01-04  1:51   ` Luis Chamberlain
2025-01-04  2:57     ` Adam Williamson
2025-01-06  7:09     ` Adam Williamson [this message]
2025-01-10  9:57   ` Mike Rapoport
2025-01-10 17:28     ` Adam Williamson
2025-01-11  8:50       ` Mike Rapoport
     [not found]         ` <358da653bcd8b7875f59e673e5572bddd3677aea.camel@redhat.com>
     [not found]           ` <9cb0bdfc94643fb1544671837b357bc49800ce3f.camel@redhat.com>
2025-01-14  7:55             ` Adam Williamson
2025-01-14  8:08               ` Adam Williamson

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=6414e871b2c9800c3ffa2245c73eb5d039d4eda7.camel@redhat.com \
    --to=awilliam@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rppt@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

all inboxes | Powered by JetHome®