From: Thomas Gleixner <tglx@linutronix.de>
To: Laura Nao <laura.nao@collabora.com>
Cc: kernel@collabora.com, laura.nao@collabora.com,
linux-kernel@vger.kernel.org, regressions@leemhuis.info,
regressions@lists.linux.dev, x86@kernel.org
Subject: Re: [REGRESSION] mainline boot regression on AMD Stoney Ridge Chromebooks
Date: Wed, 10 Apr 2024 21:34:33 +0200 [thread overview]
Message-ID: <87il0p2era.ffs@tglx> (raw)
In-Reply-To: <20240410161141.261818-1-laura.nao@collabora.com>
Laura!
On Wed, Apr 10 2024 at 18:11, Laura Nao wrote:
> On 4/10/24 15:57, Thomas Gleixner wrote:
>> I just moved the exit check a bit so we should see the scan info. That
>> should tell me what goes south.
>
> Here's the full kernel log with the latest patch applied:
> https://pastebin.com/raw/r2CkP396
Ok. Now I can see it.
pr_info("NPP %u\n", tscan.amd_nodes_per_pkg);
The output is:
<6>[ 0.000000] NPP 3
The original code then reads out 1, which is what's expected on that
machine.
Now that bogus value '3' is used later in
a %= b / 3
as b == 2, the division result is zero, which makes the %= operation
crash with a division by zero. As there are no handlers yet, nothing to
see.
The problem causing the bogus readout sits between my keyboard and my
chair.
I'll send out the fixes with proper change logs later tonight.
Thanks for all your help!
tglx
next prev parent reply other threads:[~2024-04-10 19:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 17:52 [REGRESSION] mainline boot regression on AMD Stoney Ridge Chromebooks Laura Nao
2024-03-28 9:44 ` Laura Nao
2024-03-28 11:50 ` Laura Nao
2024-04-04 8:24 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-04 9:26 ` Laura Nao
2024-04-04 13:01 ` Thomas Gleixner
2024-04-04 13:05 ` Thomas Gleixner
2024-04-04 15:23 ` Laura Nao
2024-04-04 16:14 ` Thomas Gleixner
2024-04-04 18:06 ` Thomas Gleixner
2024-04-04 19:14 ` Thomas Gleixner
2024-04-04 20:05 ` Thomas Gleixner
2024-04-05 8:14 ` Laura Nao
2024-04-05 8:42 ` Thomas Gleixner
2024-04-05 10:32 ` Laura Nao
2024-04-05 13:38 ` Thomas Gleixner
2024-04-05 13:58 ` Laura Nao
2024-04-05 14:59 ` Thomas Gleixner
2024-04-08 8:20 ` Thomas Gleixner
2024-04-08 11:06 ` Laura Nao
2024-04-08 14:19 ` Thomas Gleixner
2024-04-09 10:07 ` Laura Nao
2024-04-09 12:25 ` Thomas Gleixner
2024-04-10 8:15 ` Laura Nao
2024-04-10 13:57 ` Thomas Gleixner
2024-04-10 16:11 ` Laura Nao
2024-04-10 19:34 ` Thomas Gleixner [this message]
2024-04-10 19:45 ` [patch 0/2] x86/cpu/amd: Fixup the topology rework fallout Thomas Gleixner
2024-04-10 19:45 ` [patch 1/2] x86/cpu/amd: Make the CPUID 0x80000008 parser correct Thomas Gleixner
2024-04-11 12:45 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2024-04-12 10:12 ` tip-bot2 for Thomas Gleixner
2024-04-10 19:45 ` [patch 2/2] x86/cpu/amd: Make the NODEID_MSR union actually work Thomas Gleixner
2024-04-11 12:45 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2024-04-12 10:12 ` tip-bot2 for Thomas Gleixner
2024-04-11 11:27 ` [patch 0/2] x86/cpu/amd: Fixup the topology rework fallout Laura Nao
2024-04-11 11:37 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 12:14 ` 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=87il0p2era.ffs@tglx \
--to=tglx@linutronix.de \
--cc=kernel@collabora.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--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