Bug 21367

Summary: could not find ioremap agp regions! on PowerPC
Product: DRI Reporter: Tormod Volden <bugzi11.fdo.tormod>
Component: DRM/RadeonAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: svu
Version: unspecified   
Hardware: PowerPC   
OS: All   
URL: https://bugs.launchpad.net/bugs/345542
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg with drm debug=1 none

Description Tormod Volden 2009-04-23 15:23:00 UTC
Created attachment 25076 [details]
dmesg with drm debug=1

Forwarded from Ubuntu bug https://bugs.launchpad.net/bugs/345542

DRM fails to initialize on PowerPC with Ubuntu kernel 2.6.28-5-powerpc, based on 2.6.28.1 (the 2.6.28-4-powerpc, based on 2.6.28, worked fine).

[drm:radeon_do_init_cp] *ERROR* could not find ioremap agp regions!

Unlike the problem with 2.6.29 reported earlier (http://bugzilla.kernel.org/show_bug.cgi?id=12441), "nopat" does not help.

The original reporters will also try newer kernels or build newer drm modules, but the reduced support for PowerPC in Ubuntu makes it more challenging.
Comment 1 Michel Dänzer 2009-04-27 09:05:07 UTC
I haven't seen this on my PowerBook with upstream kernels up to 2.6.29.1, so 'on powerpc' may be too broad.

One thing I notice is that the dmesg seems to be from a 64 bit kernel. Are people also seeing this on machines running 32 bit kernels?


> DRM fails to initialize on PowerPC with Ubuntu kernel 2.6.28-5-powerpc, based
> on 2.6.28.1 (the 2.6.28-4-powerpc, based on 2.6.28, worked fine).

So it should be possible to isolate the kernel change that causes or at least triggers it?


> Unlike the problem with 2.6.29 reported earlier
> (http://bugzilla.kernel.org/show_bug.cgi?id=12441), "nopat" does not help.

Yeah, PAT is an x86 feature...
Comment 2 Sergey V. Udaltsov 2009-04-27 13:58:58 UTC
2.6.28-6-powerpc64-smp

I do not have 32-bit kernel.
Comment 3 Tormod Volden 2009-04-27 14:53:29 UTC
> I haven't seen this on my PowerBook with upstream kernels up to 2.6.29.1, so
> 'on powerpc' may be too broad.

I only added it to the title to narrow it down to powerpc (and to differentiate it from the i386 issue with the same error message), I didn't mean to imply it touches all powerpc. Please correct the title if it can be understood the wrong way.

> So it should be possible to isolate the kernel change that causes or at least
> triggers it?

I don't know if we can hope that anyone will bisect it, so I was hoping for an educated guess from someone here :) At least I checked the Ubuntu changes between those two versions and I could not see anything relevant AFAICS. There are deb's for vanilla kernels, but unfortunately not built for powerpc. I hope someone will at least built the newer drm modules and check.
Comment 4 Tormod Volden 2009-04-27 15:08:27 UTC
Two other guys are using 32 bit kernel (on G4's).
Comment 5 Tormod Volden 2009-05-03 15:34:31 UTC
According to http://lists.x.org/archives/xorg-devel/2009-May/000825.html this is a bug in the Ubuntu kernel.
Comment 6 Tormod Volden 2009-05-07 15:04:00 UTC
I think Alex was onto something in that thread: http://lists.x.org/archives/xorg-devel/2009-May/000816.html

The Ubuntu changes introduced in this version is mainly his jumbo patch "radeon: add support for RS600, R6xx, and R7xx GPUs" http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=commit;h=85568da345d4348f33c69043c9bc4e78ad819706

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.