From: "Dave Airlie" <airlied@gmail.com>
To: "Sitsofe Wheeler" <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird Xorg radeon mirroring with linux-next-20080515 [paritial bisect]
Date: Fri, 16 May 2008 09:18:26 +1000 [thread overview]
Message-ID: <21d7e9970805151618i71ccc581j7e07082bd0b7a8e@mail.gmail.com> (raw)
In-Reply-To: <g0iadj$dip$1@ger.gmane.org>
>>> Hi,
>>>
>>> When using the radeon xorg driver with linux-next-20080515 there is a
>>> strange mirroring/stretching effect in the bottom eighth of the screen.
>>> The problem seems to have started sometime between linux-next-20080513
>>> and linux-next-20080515.
>>>
>>> (Do you always have to have done bisection before reporting
>>> regressions?)
>>>
>>>
>> NO!
>
> Ah, now you tell me : ) It sounded like bisection was what you did if you
> weren't a regular dev and you wanted your bug to get attention. I've
> spent a while trying to bisect this but didn't get all the way. My tests
> make me believe it lies somewhere between commits
> f5fbb15f66bd0a6017e4ca513217e823395502b7 and
> 6a305693b777ecd710107387a9753117a54bcbf9 ...
>
> The problem doesn't manifest directly after Xorg is started after boot -
> it seems to happen a few seconds later while services are still being
> started. Switching to a VT and back can make the problem go away.
>
wierd got any fglrx or anything installed on you're system.. the
radeon drm hasn't seen any changes that should affect this sorta
thing, do you run radeonfb or vesafb?
Dave.
next prev parent reply other threads:[~2008-05-15 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:00 Weird Xorg radeon mirroring with linux-next-20080515 Sitsofe Wheeler
2008-05-15 17:35 ` Chris Snook
2008-05-15 21:36 ` Weird Xorg radeon mirroring with linux-next-20080515 [paritial bisect] Sitsofe Wheeler
2008-05-15 23:18 ` Dave Airlie [this message]
2008-05-16 7:39 ` Sitsofe Wheeler
2008-05-16 15:53 ` Weird Xorg stretching (setfont) Sitsofe Wheeler
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=21d7e9970805151618i71ccc581j7e07082bd0b7a8e@mail.gmail.com \
--to=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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®