From: Andrew 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: Sun, 21 Jun 2009 08:06:01 -0400 [thread overview]
Message-ID: <cb0375e10906210506k911737fp18667221596771b@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906210615450.6234@skynet.skynet.ie>
On Sun, Jun 21, 2009 at 1:16 AM, Dave Airlie<airlied@linux.ie> wrote:
>>
>> 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.
>
> You need a different userspace, -ati from koji in F11 should do it.
I'm already running that (xorg-x11-drv-ati-6.12.2-17.fc11.x86_64,
which is the latest in koji).
But the oops is in *plymouth*, which as far as I can tell uses the
framebuffer interface, so it shouldn't matter what xorg driver I have
installed. Shouldn't it be impossible for a buggy framebuffer client
to cause an oops?
>
> However we have some outstanding rs690 issues that I'm trying to track
> down as we speak,
Great! I'll keep on testing.
--Andy
>
> Dave.
>
>>
>> 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
>>
>
next prev parent reply other threads:[~2009-06-21 12:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 5:23 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
2009-06-21 5:16 ` Dave Airlie
2009-06-21 12:06 ` Andrew Lutomirski [this message]
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=cb0375e10906210506k911737fp18667221596771b@mail.gmail.com \
--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
all inboxes | Powered by JetHome®