Bug 33815 - BUG: unable to handle kernel NULL pointer dereference at (null)
Summary: BUG: unable to handle kernel NULL pointer dereference at (null)
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
Depends on:
Reported: 2011-02-01 10:26 UTC by Francesco Marella
Modified: 2018-06-12 19:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

dmesg (44.13 KB, patch)
2011-02-01 10:26 UTC, Francesco Marella
no flags Details | Splinter Review
dmesg agpmode=-1 (40.31 KB, text/plain)
2011-02-01 14:49 UTC, Francesco Marella
no flags Details
lspci vnn (5.48 KB, text/plain)
2011-02-01 15:44 UTC, Francesco Marella
no flags Details
drm patch (1.18 KB, patch)
2011-02-01 16:06 UTC, Alex Deucher
no flags Details | Splinter Review

Description Francesco Marella 2011-02-01 10:26:07 UTC
Created attachment 42817 [details] [review]

Kernel oops booting with radeon kms
Comment 1 Alex Deucher 2011-02-01 10:51:11 UTC
I suspect this is a problem with agpgart-via.  Does booting with radeon.agpmode=-1 on the kernel command line in grub help?
Comment 2 Francesco Marella 2011-02-01 14:49:32 UTC
Created attachment 42828 [details]
dmesg agpmode=-1

No, doesn't help.
Comment 3 Alex Deucher 2011-02-01 15:38:18 UTC
Can you attach the output of 'lspci -vnn' ?
Comment 4 Francesco Marella 2011-02-01 15:44:11 UTC
Created attachment 42830 [details]
lspci vnn
Comment 5 Alex Deucher 2011-02-01 16:06:09 UTC
Created attachment 42837 [details] [review]
drm patch

This drm patch will fix it.  The 0x4243 pci id is a bridge device, not a gpu.
Comment 6 Adam Jackson 2018-06-12 19:09:45 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.