From: bugzilla-daemon@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: Fri, 26 Aug 2022 14:36:28 +0000 [thread overview]
Message-ID: <bug-215443-206035-s7AbLn26FS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215443-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215443
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
Have not seen this since quite a few stable kernel releases on the same
hardware. I think it's save to close here.
--
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-08-26 14:37 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
2022-08-26 14:36 ` bugzilla-daemon [this message]
-- 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-s7AbLn26FS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.