[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130503165720.GC8320@zod.gha.chartermi.net>
Date: Fri, 3 May 2013 12:57:20 -0400
From: Josh Boyer <jwboyer@...il.com>
To: Daniel Vetter <daniel.vetter@...ll.ch>
Cc: Dave Airlie <airlied@...ux.ie>,
Linus Torvalds <torvalds@...ux-foundation.org>,
DRI mailing list <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
intel-gfx <intel-gfx@...ts.freedesktop.org>
Subject: Re: [git pull] drm for 3.10-rc1
On Fri, May 03, 2013 at 06:08:52PM +0200, Daniel Vetter wrote:
>On Fri, May 3, 2013 at 4:39 PM, Josh Boyer <jwboyer@...il.com> wrote:
>> On Fri, May 03, 2013 at 02:25:57AM +0100, Dave Airlie wrote:
>>>The following changes since commit b6a9b7f6b1f21735a7456d534dc0e68e61359d2c:
>>>
>>> mm: prevent mmap_cache race in find_vma() (2013-04-04 11:46:28 -0700)
>>>
>>>are available in the git repository at:
>>>
>>> git://people.freedesktop.org/~airlied/linux.git drm-next
>>>
>>>for you to fetch changes up to 307b9c022720f9de90d58e51743e01e9a42aec59:
>>>
>>> qxl: update to new idr interfaces. (2013-05-03 10:37:20 +1000)
>>>
>>>----------------------------------------------------------------
>>
>> So something in this batch of commits breaks a Macbook Pro Retina I have
>> sitting here. If I boot a Fedora kernel based on Linux
>> v3.9-8153-g5a148af, things boot up as they did previously with 3.9.0 and
>> are generally working fine. If I boot with a kernel based on Linux
>> v3.9-8933-gce85722, it will boot but as soon as plymouth starts, I get
>> nothing but static on the screen (like 1950s TV static).
>>
>> This machine is using i915 graphics, so I booted with nomodeset and did
>> the 'modprobe drm debug=15; modprobe i915 modeset=1' trick and it
>> repeated the failure with that. I've gathered a bunch of data like
>> dmesg, an intel_reg_snapshot, etc. It's all attached below.
>>
>> I'll start bisecting to see if I can narrow down the commit that broke
>> things, but I thought I would give a heads up now in case anyone has any
>> ideas.
>
>Looked through the log files and didn't see a clue. And usually DP
>tends to fail pretty noisily. So I think the bisect result would be
>interestin. Meanwhile:
Yeah, working on that.
>- do you have drm.debug=0xe dmesg for a working kernel, too?
No, but I can try and get one.
>- is the panel completely dead or is just the backlight on (or panel
>on but backlight off)?
Backlight is on. Literally static flickering on the screen.
Occasionally it will flicker from static to black back and forth. But
the backlight is clearly on and what is trying to render (the GDM screen
normally) is just coming up as static.
josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists