From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213079] [bisected] IRQ problems and crashes on a PowerMac G5 with 5.12.3
Date: Mon, 07 Jun 2021 04:13:16 +0000 [thread overview]
Message-ID: <bug-213079-206035-3N91WROjuQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213079-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213079
--- Comment #5 from Oliver O'Halloran (oohall@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 hardware to replicate this with.
Could you add "debug" to the kernel command line and post the dmesg output for
a boot with the patch applied and reverted?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-06-07 4:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 11:58 [Bug 213079] New: IRQ problems and crashes on a PowerMac G5 with 5.13-rc1 bugzilla-daemon
2021-05-15 11:58 ` [Bug 213079] " bugzilla-daemon
2021-05-15 12:30 ` bugzilla-daemon
2021-05-15 14:50 ` [Bug 213079] IRQ problems and crashes on a PowerMac G5 with 5.12.3 bugzilla-daemon
2021-06-06 18:14 ` [Bug 213079] [bisected] " bugzilla-daemon
2021-06-07 4:13 ` bugzilla-daemon [this message]
2021-06-07 6:49 ` bugzilla-daemon
2021-06-17 23:48 ` bugzilla-daemon
2021-06-17 23:51 ` bugzilla-daemon
2021-06-17 23:52 ` bugzilla-daemon
2021-06-17 23:54 ` bugzilla-daemon
2021-06-18 23:29 ` bugzilla-daemon
2021-07-05 14:11 ` bugzilla-daemon
2021-07-05 14:20 ` bugzilla-daemon
2021-07-05 16:04 ` bugzilla-daemon
2021-07-23 12:47 ` bugzilla-daemon
2021-08-20 0:12 ` bugzilla-daemon
2021-08-20 0:13 ` bugzilla-daemon
2021-08-20 16:39 ` bugzilla-daemon
2022-07-07 10:30 ` bugzilla-daemon
2022-07-29 7:01 ` bugzilla-daemon
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=bug-213079-206035-3N91WROjuQ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.