From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Justin Madru <jdm64@gawab.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Wed, 9 Apr 2008 08:24:35 -0700 [thread overview]
Message-ID: <200804090824.35825.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <47FC4C9B.1030703@gawab.com>
On Tuesday, April 08, 2008 9:56 pm Justin Madru wrote:
> Jesse Barnes wrote:
> > Yeah, seems pretty weird. Given that you see it w/o the fb stuff loaded
> > as well and we still have a few open bugs against the intel X driver
> > regarding VT switch & mode programming, I don't think this is a real
> > kernel regression. It's more likely that some timing or memory layout
> > changed subtly and is causing to to hit one of our existing bugs more
> > frequently that you did before. Can you file a bug against the intel X
> > driver at
> > bugs.freedesktop.org so we can track it there? Unless we can find a way
> > to reproduce it reliably it'll probably take a long time to fix, but we
> > don't want to lose it either...
>
> Well, I'll file a bug on bugs.freedesktop.org, but if you don't think
> it's a kernel regression then I'll wait until the final release of
> 2.6.25 comes out (unless you _really_ need me to file it sooner).
Well, given what we've tested so far, it really doesn't seem like a
framebuffer layer regression nor a DRM regression... I suppose you could try
bisecting, but given that the problem doesn't happen everytime that might
take awhile...
> This is what I have in my config:
> > CONFIG_PREEMPT_RCU=y
> > CONFIG_IO_DELAY_NONE=y
>
> By the way is the intel driver that you work on the same that's enabled by:
> > CONFIG_AGP_INTEL=m
> > CONFIG_DRM_I915=m
>
> Or is there another X.org intel driver? And if so how are they
> (agp/drm/X.org) related?
You could try using the X vesa driver instead of the intel driver...
Jesse
next prev parent reply other threads:[~2008-04-09 15:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 19:02 Justin Madru
2008-03-12 19:36 ` Jesse Barnes
[not found] ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09 ` Jesse Barnes
2008-03-14 4:22 ` Justin Madru
2008-03-14 17:29 ` Jesse Barnes
2008-03-15 3:48 ` Justin Madru
2008-03-15 17:35 ` Jesse Barnes
2008-03-15 18:16 ` Bryce Harrington
2008-03-17 1:28 ` Justin Madru
2008-03-18 19:07 ` Bryce Harrington
2008-03-18 20:00 ` Jesse Barnes
2008-03-18 20:53 ` Bryce Harrington
2008-03-18 21:14 ` Bryce Harrington
2008-03-18 21:17 ` Jesse Barnes
2008-03-19 23:38 ` Justin Madru
2008-03-19 23:48 ` Jesse Barnes
2008-03-20 2:00 ` Bryce Harrington
2008-03-25 3:07 ` Justin Madru
2008-03-25 20:08 ` Jesse Barnes
2008-03-26 18:32 ` Justin Madru
2008-03-31 19:24 ` Justin Madru
2008-04-01 20:22 ` Jesse Barnes
2008-04-09 4:56 ` Justin Madru
2008-04-09 15:24 ` Jesse Barnes [this message]
2008-04-14 3:46 ` Justin Madru
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=200804090824.35825.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=jdm64@gawab.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome