From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215443] [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1]
Date: Mon, 03 Jan 2022 15:26:56 +0000 [thread overview]
Message-ID: <bug-215443-206035-7PA7vE3gdj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215443-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215443
--- Comment #3 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Alex Deucher from comment #2)
> does appending amdgpu.runpm=0 on the kernel command line help?
I doubt it as amdgpu is not even built (# CONFIG_DRM_AMDGPU is not set, see
attached .config).
The card in question is a Radeon HD 6670 using the radeon drm module. Sorry I
forgot to mention that!
--
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:[~2022-01-03 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 14:35 [Bug 215443] New: [radeon] BUG: Unable to handle kernel data access on read at 0xc007ffffffff9130, Oops: Kernel access of bad area, sig: 11 [#1] bugzilla-daemon
2022-01-01 14:37 ` [Bug 215443] " bugzilla-daemon
2022-01-03 15:10 ` bugzilla-daemon
2022-01-03 15:26 ` bugzilla-daemon [this message]
2022-08-26 14:36 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2022-01-01 14:35 [Bug 215443] New: " bugzilla-daemon
2022-01-01 14:37 ` [Bug 215443] " bugzilla-daemon
2022-01-03 15:10 ` bugzilla-daemon
2022-01-03 15:26 ` bugzilla-daemon
2022-08-26 14:36 ` 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-215443-206035-7PA7vE3gdj@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.