Re: Problem with commit drm/i915: Fix detection of base of stolen memory in 3.2.45

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2013-05-17 at 14:42 +0200, Yves-Alexis Perez wrote:
> Hi,
> 
> I have a problem with recently released 3.2.45, and especially after
> commit 53e587aa5ca81497d0ea6e340320ec5778d1f311.
> 
> 
> On at least two boxes (Dell E4300 with GMA4500 and Thinkpad T61 with
> i965), as soon as i915 is loaded, backlight is switched of and doesn't
> reappear. The systems works fine, just no display.
> 
> Dmesg of a boot with drm.debug=0xf is attached. Note that it seems that
> "found %d bytes of stolen memory at %08lx\n" message is never printed,
> so I guess i915_stolen_to_physical() somehow returns 0 but I didn't yet
> instrumented the code to check that.
> 
> My guess would be that if base of stolen memory is not correctly detected
> on these boxes and then the aperture is too small for anything (thus
> the *ERROR* message).
> 
> I've tried mainline and 3.8.13 (which has the commit backported) and
> both seem fine so I'm only mailing stable@ for now.
[...]

Given these results, I'll just revert this for now on 3.2.y.  If someone
can provide a backport of this that works properly for all hardware
generations then I can apply that later.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]