From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213961] Oops while loading radeon driver
Date: Thu, 05 Aug 2021 08:04:08 +0000 [thread overview]
Message-ID: <bug-213961-206035-BcDapI0Wat@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213961-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213961
--- Comment #8 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
Great:
[ 15.246367] NIP [bea42a80] radeon_agp_head_init+0x1c/0xf8 [radeon]
[ 15.246969] LR [bea39860] radeon_driver_load_kms+0x1bc/0x1f4 [radeon]
[ 15.247160] Call Trace:
[ 15.247168] [f2b75c30] [c0c1ec60] 0xc0c1ec60 (unreliable)
[ 15.247180] [f2b75c50] [bea39860] radeon_driver_load_kms+0x1bc/0x1f4
[radeon]
[ 15.247343] [f2b75c80] [be8cc74c] drm_dev_register+0x10c/0x268 [drm]
[ 15.247718] [f2b75cb0] [bea36484] radeon_pci_probe+0x108/0x190 [radeon]
[ 15.248001] [f2b75cd0] [c03832fc] pci_device_probe+0xf4/0x1a4
So we now know we have a NULL pointer dereference in radeon_agp_head_init().
Looks like all this code is quite recent, at least there are recent
modification, so I think you should address it with RADEON people, I'm not sure
the problem is a PPC32 subject.
--
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-08-05 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 16:45 [Bug 213961] New: Oops while loading radeon driver bugzilla-daemon
2021-08-04 5:44 ` [Bug 213961] " bugzilla-daemon
2021-08-04 13:29 ` bugzilla-daemon
2021-08-04 13:30 ` bugzilla-daemon
2021-08-04 14:26 ` bugzilla-daemon
2021-08-04 19:53 ` bugzilla-daemon
2021-08-04 19:54 ` bugzilla-daemon
2021-08-04 19:55 ` bugzilla-daemon
2021-08-05 8:04 ` bugzilla-daemon [this message]
2021-08-05 10:52 ` bugzilla-daemon
2021-08-05 11:00 ` bugzilla-daemon
2021-08-05 11:43 ` 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-213961-206035-BcDapI0Wat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).