All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>,
	Yazen Ghannam <yazen.ghannam@amd.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <naoya.horiguchi@nec.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Machine check recovery broken in v6.9-rc1
Date: Thu, 4 Apr 2024 16:39:53 -0700	[thread overview]
Message-ID: <Zg86SZYDppxffEvv@agluck-desk3> (raw)
In-Reply-To: <Zg8kLSl2yAlA3o5D@agluck-desk3>

On Thu, Apr 04, 2024 at 03:05:33PM -0700, Tony Luck wrote:
> v6.8 works. v6.9-rc1 fails with:
> 
> kernel BUG at include/linux/swapops.h:119
> 
> 117 static inline unsigned long swp_offset_pfn(swp_entry_t entry)
> 118 {
> 119         VM_BUG_ON(!is_pfn_swap_entry(entry));
> 120         return swp_offset(entry) & SWP_PFN_MASK;
> 121 }
> 
> 
> I've messed up the bisection three times now and ended up
> pointing at some innocent looking commit. So I wonder if
> anyone else has noticed and tried debugging.

I think I know why I messed up the bisection. I thought
the failure happens every time. But it seems that it only
happens most of the time. I must have accidentally marked
a build as "good" because I got "lucky" and my test passed.

Back to the bisect grindstone :-(

-Tony


  reply	other threads:[~2024-04-04 23:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 22:05 Machine check recovery broken in v6.9-rc1 Tony Luck
2024-04-04 23:39 ` Tony Luck [this message]
2024-04-05  7:19 ` David Hildenbrand
2024-04-05 15:05   ` Luck, Tony
2024-04-05 23:58     ` Tony Luck
2024-04-06  2:18       ` Oscar Salvador
2024-04-06  3:54         ` Oscar Salvador
2024-04-06  4:13           ` Oscar Salvador
2024-04-07  0:08             ` Luck, Tony
2024-04-07  3:59               ` Miaohe Lin
2024-04-07  4:51               ` Oscar Salvador

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=Zg86SZYDppxffEvv@agluck-desk3 \
    --to=tony.luck@intel.com \
    --cc=bp@alien8.de \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=yazen.ghannam@amd.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.