https://bugzilla.kernel.org/show_bug.cgi?id=213079
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|NEW |NEEDINFO
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #19 from Erhard F. (erhar...@mailbox.org) ---
(Luckily) I am no longer able to reproduce this. Re-tested on 5.19-rc5.
Perhaps the problem was also specific for this specific NVMe SSD. I swapped it
for another one and now I have not
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #18 from Erhard F. (erhar...@mailbox.org) ---
The 'hackfix for MSI init' patch also applies on top of v5.14-rc6.
But unchanged the G5 runs later into bug #213837.
--
You may reply to this email to add a comment.
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=213079
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Attachment #297439|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=213079
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Attachment #297473|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #15 from Erhard F. (erhar...@mailbox.org) ---
(In reply to Oliver O'Halloran from comment #13)
> In the meanwhile, can you try the patch above? That seems to fix bug which
> is causing MSIs to be unusable. I'm not 100% sure why that
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #14 from Erhard F. (erhar...@mailbox.org) ---
Thanks for the patch! I will try it as soon as I get to this G5 again.
Don't know whether write access is necessary to trigger the bug. The past
weekend I've seen it only by doing an
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #13 from Oliver O'Halloran (ooh...@gmail.com) ---
Hi,
I got a loaner G5 with an NVMe drive, but I haven't been able to replicate the
crash you're seeing. However, I think that's probably because I'm only reading
from the NVMe since
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #12 from Oliver O'Halloran (ooh...@gmail.com) ---
Created attachment 297755
--> https://bugzilla.kernel.org/attachment.cgi?id=297755=edit
hackfix for MSI init
--
You may reply to this email to add a comment.
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #11 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 297473
--> https://bugzilla.kernel.org/attachment.cgi?id=297473=edit
dmesg (5.13-rc6 + DEBUG_VM_PGTABLE, PowerMac G5 11,2)
The trace got some additional data with
https://bugzilla.kernel.org/show_bug.cgi?id=213079
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Attachment #296759|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #9 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 297437
--> https://bugzilla.kernel.org/attachment.cgi?id=297437=edit
dmesg (5.13-rc6 w. patch fbbefb3 reverted + debug, PowerMac G5 11,2)
--
You may reply to this
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #8 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 297435
--> https://bugzilla.kernel.org/attachment.cgi?id=297435=edit
dmesg (5.13-rc6 + debug, PowerMac G5 11,2)
--
You may reply to this email to add a comment.
You
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #7 from Erhard F. (erhar...@mailbox.org) ---
(In reply to Oliver O'Halloran from comment #5)
> Could you add "debug" to the kernel command line and post the dmesg output
> for a boot with the patch applied and reverted?
Ok, on top of
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #6 from Erhard F. (erhar...@mailbox.org) ---
This is already a custom built kernel with lots of debugging options turned on
(see bugzilla attached kernel .config). But of course I can add "debug" to the
other kernel command line
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #5 from Oliver O'Halloran (ooh...@gmail.com) ---
Hmm, it's pretty weird to see an NVMe drive using LSIs. Not too sure what to
make of that. I figure there's something screwy going on with interrupt
routing, but I don't have any g5
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #4 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 297191
--> https://bugzilla.kernel.org/attachment.cgi?id=297191=edit
bisect.log
Turns out the problem was introduced between v5.11 and v5.12 by following
commit:
#
17 matches
Mail list logo
