https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #30 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Can confirm, disabling CONFIG_X86_VSMP corrects the issue.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #29 from Barret Rhoden (b...@google.com) ---
Ah, nice find. That other bug (201339) looks like the root cause of this one.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=202511
vladimir gerasimov (v...@ggpi.org) changed:
What|Removed |Added
CC||v...@ggpi.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #27 from Michael A. Leonetti (mikealeone...@gmail.com) ---
(In reply to Michel Dänzer from comment #26)
> When the amdgpu driver is built into the kernel, so must be all the
> microcode files under /lib/firmware/amdgpu/ that it needs
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #26 from Michel Dänzer (mic...@daenzer.net) ---
When the amdgpu driver is built into the kernel, so must be all the microcode
files under /lib/firmware/amdgpu/ that it needs with your GPU.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #25 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281359
--> https://bugzilla.kernel.org/attachment.cgi?id=281359=edit
fb: switching to amdgpudrmfb from EFI VGA freeze 4.19.23
Barret,
I will apply the
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #24 from Barret Rhoden (b...@google.com) ---
Created attachment 281345
--> https://bugzilla.kernel.org/attachment.cgi?id=281345=edit
Print module reserved percpu allocations
Hi Michael -
Can you apply this patch and report back
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #23 from Michael A. Leonetti (mikealeone...@gmail.com) ---
(In reply to Bjorn Helgaas from comment #21)
> Thanks! Unless somebody has a better idea, I would try building 4.17.19
> with the print options.
>
> Config differences that
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #22 from Barret Rhoden (b...@google.com) ---
As far as the bisection goes, from the original bisect report, both of the
commits that were merged were good. i.e. 3a3869f1 merged two good commits:
3036bc45364f and 488ad6d3678b. Only
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #21 from Bjorn Helgaas (bhelg...@google.com) ---
Thanks! Unless somebody has a better idea, I would try building 4.17.19 with
the print options.
Config differences that might conceivably be related:
--- config-4.17.txt
https://bugzilla.kernel.org/show_bug.cgi?id=202511
Michael A. Leonetti (mikealeone...@gmail.com) changed:
What|Removed |Added
Attachment #281261|0 |1
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #19 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281263
--> https://bugzilla.kernel.org/attachment.cgi?id=281263=edit
4.18 config
Would you like me to build the 4.17.19 kernel with the print options
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #18 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281261
--> https://bugzilla.kernel.org/attachment.cgi?id=281261=edit
4.17.19 config
Absolutely. Let me post the two configs then.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #17 from Bjorn Helgaas (bhelg...@google.com) ---
Created attachment 281259
--> https://bugzilla.kernel.org/attachment.cgi?id=281259=edit
per-cpu alloc info (broken)
FWIW, I pulled out the per-cpu alloc info and what looks like the
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #16 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281247
--> https://bugzilla.kernel.org/attachment.cgi?id=281247=edit
dmesg 4.18.0 with debugs
Did I do this correctly? I see a lot more call track
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #15 from Bjorn Helgaas (bhelg...@google.com) ---
Created attachment 281143
--> https://bugzilla.kernel.org/attachment.cgi?id=281143=edit
per-cpu alloc debug patch
I think bisecting again would be a poor use of your time unless
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #14 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Is there anything else I can try? Should I do the first bisect again?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #13 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281107
--> https://bugzilla.kernel.org/attachment.cgi?id=281107=edit
bisect log 2
I'm not sure if this is helpful. Basically all of the builds that I did
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #12 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Rather, I appreciate the help.
I'll start bisecting after work and post a reply as soon as I have the result.
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #11 from Bjorn Helgaas (bhelg...@google.com) ---
Yes. I don't have any better ideas. I'm not sure why git bisect wasn't smart
enough to narrow it down further by itself. Sorry, I know bisecting is
painful.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #10 from Michael A. Leonetti (mikealeone...@gmail.com) ---
I'd love to get it settled too (for obvious reasons). I guess a good place to
start is the bisect that Bjorn Helgaas requested?
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #9 from Christian König (christian.koe...@amd.com) ---
Yeah, I also would be really interested what the root cause is.
As far as I know we don't have any large per CPU data in amdgpu, so no idea how
this can happen.
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #8 from Bjorn Helgaas (bhelg...@google.com) ---
Even if this is "special", e.g., some strange kconfig or build/install issue,
this is a really painful issue to debug. It would be tremendous if we could
fail more gracefully, with some
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #7 from Michael A. Leonetti (mikealeone...@gmail.com) ---
It could be special. If so I'd love to know what it is that I'm doing wrong. So
far all of the 4.17 kernels I've tried works and Windows works on the laptop.
I'll see if I can
https://bugzilla.kernel.org/show_bug.cgi?id=202511
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #5 from Bjorn Helgaas (bhelg...@google.com) ---
The bisect log in comment #3 shows 3a3869f1c443 ("Merge tag 'pci-v4.18-changes'
of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci") as the first bad
commit. That's a large
https://bugzilla.kernel.org/show_bug.cgi?id=202511
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #3 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281033
--> https://bugzilla.kernel.org/attachment.cgi?id=281033=edit
bisect log
Here is the bisect log as requested.
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=202511
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #1 from Michael A. Leonetti (mikealeone...@gmail.com) ---
Created attachment 281011
--> https://bugzilla.kernel.org/attachment.cgi?id=281011=edit
4.17.19 working amdgpu dmesg
For reference here is my dmesg from the 4.17.19 which
30 matches
Mail list logo