From: Andy Lutomirski <luto@mit.edu>
To: Dave Airlie <airlied@linux.ie>
Cc: torvalds@linux-foundation.org, dri-devel@lists.sf.net,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm: previous pull req + 1.
Date: Sat, 20 Jun 2009 23:41:21 -0400 [thread overview]
Message-ID: <4A3DABE1.50309@mit.edu> (raw)
In-Reply-To: <alpine.DEB.2.00.0906200619520.27130@skynet.skynet.ie>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
Dave Airlie wrote:
> Hi Linus,
>
> Please pull the 'drm-linus' branch from
> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus
>
> This is the same tree from the previous pull request + the fix from Pierre
> that actually makes the PAE/GEM combination on i965 work. \o/
>
I tried this tree (specifically, a merge of Linus' fb20871 this tree) on
Fedora 11 with modesetting enabled on an integrated Radeon 2100, and
plymouthd crashes immediately with a corrupt page table. Photo
attached. After the crash, bootup stops, although ctrl-alt-del works.
This is on a Gigabyte GA-MA74GM-S2 (RS690 chipset) with a somewhat old
BIOS which has never had reliable graphics on X with any kernel and
userspace I've tried, modesetting or otherwise, so this isn't a
regression per se. But on F11's kernel, I can at least boot to a
console with modesetting enabled and nothing dies until I try to start
X, and, with modesetting off on older kernels I can boot just fine
(again, until I try to use X, at which point things break).
I'd be happy to test things to help debug.
Thanks,
Andy
[-- Attachment #2: radeon_modeset_crash.jpg --]
[-- Type: image/jpeg, Size: 278259 bytes --]
next prev parent reply other threads:[~2009-06-21 3:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 5:23 [git pull] drm: previous pull req + 1 Dave Airlie
2009-06-21 0:04 ` Maxim Levitsky
2009-06-21 0:42 ` Linus Torvalds
2009-06-21 14:47 ` Maxim Levitsky
2009-06-21 21:24 ` Chris Wilson
2009-06-22 18:09 ` Maxim Levitsky
2009-06-29 7:57 ` Chris Wilson
2009-06-30 9:49 ` Chris Wilson
2009-07-09 23:11 ` Eric Anholt
2009-06-21 1:33 ` Dave Airlie
2009-06-21 3:41 ` Andy Lutomirski [this message]
2009-06-21 5:16 ` Dave Airlie
2009-06-21 12:06 ` Andrew Lutomirski
2009-06-21 16:46 ` Linus Torvalds
2009-06-21 17:13 ` Linus Torvalds
2009-06-21 18:50 ` Andrew Lutomirski
2009-06-21 19:47 ` Linus Torvalds
2009-06-21 21:14 ` Andrew Lutomirski
2009-06-22 0:05 ` Andrew Lutomirski
2009-06-22 19:20 ` Arnaldo Carvalho de Melo
2009-06-21 22:40 ` Dave Airlie
2009-06-22 8:18 ` Thomas Hellström
2009-06-22 8:30 ` Dave Airlie
2009-06-22 18:22 ` Linus Torvalds
2009-06-22 18:59 ` Andrew Lutomirski
2009-06-22 19:43 ` Linus Torvalds
2009-06-23 0:01 ` Benjamin Herrenschmidt
2009-06-23 0:00 ` Benjamin Herrenschmidt
2009-06-23 0:24 ` Linus Torvalds
2009-06-23 1:04 ` Benjamin Herrenschmidt
2009-06-23 1:18 ` Jesse Barnes
2009-06-23 1:58 ` Benjamin Herrenschmidt
2009-06-23 2:07 ` Jesse Barnes
2009-06-23 2:26 ` Benjamin Herrenschmidt
2009-06-23 15:40 ` Jesse Barnes
2009-06-23 7:48 ` Michel Dänzer
2009-06-23 15:39 ` Jesse Barnes
2009-06-23 16:28 ` Jesse Barnes
2009-06-22 23:57 ` Benjamin Herrenschmidt
2009-06-21 22:41 ` Dave Airlie
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=4A3DABE1.50309@mit.edu \
--to=luto@mit.edu \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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