# See also bug 403871
reassign 392915 linux-2.6
tags 392915 upstream fixed-upstream patch
kthxbye
On Wed, 2007-01-10 at 23:35 +0100, Andreas Johansson wrote:
On Wed, Jan 10, 2007 at 10:15:15AM +0100, Michel Dänzer wrote:
Thanks. I think this is another integer overflow bug in the radeon DRM;
On Wed, Jan 10, 2007 at 06:45:57PM +1100, Dave Airlie wrote:
can you attach lspci -vv for both cases?
Here they are, for reference.
(The one with 32MB AGP aperture was taken from a system running
a radeon.ko with Michel's patch to radeon_cp.c.)
--
Andreas Johansson
On Wed, Jan 10, 2007 at 10:15:15AM +0100, Michel Dänzer wrote:
Thanks. I think this is another integer overflow bug in the radeon DRM;
can you try the attached patch?
Yes, this enables me to use a 32MB AGP aperture setting in the BIOS.
Thanks for finding the cause of this problem!
I used the
On Tue, 2007-01-09 at 22:54 +0100, Andreas Johansson wrote:
On Tue, Jan 09, 2007 at 06:18:24PM +0100, Michel Dänzer wrote:
I'm not sure how this could happen though; can you also post the full
kernel output, or at least everything related to AGP and the DRI?
Sure. Attached are the
On Tue, 2007-01-09 at 16:27 +0100, Andreas Johansson wrote:
Attached are two log files, one from a hanging session (the 32MB one)
and one from a working (the 128MB one). The diff mostly seems to be
due to different offsets.
Hmm, it looks like the framebuffer and AGP areas end up overlapping
On Tue, Jan 09, 2007 at 06:18:24PM +0100, Michel Dänzer wrote:
I'm not sure how this could happen though; can you also post the full
kernel output, or at least everything related to AGP and the DRI?
Sure. Attached are the entries from /var/log/messages that I believe
matches the two Xorg log
I'm not sure how this could happen though; can you also post the full
kernel output, or at least everything related to AGP and the DRI?
Sure. Attached are the entries from /var/log/messages that I believe
matches the two Xorg log files. Below are the results of grep:ing
for agp and drm.
can
On Sun, 2007-01-07 at 19:41 +0100, Andreas Johansson wrote:
Yes, if the agpgart driver can print a message about the aperture size
being too small, it should also be able report failure such that the X
server doesn't initialize the DRI.
Ah, sorry, my wording when referring to fd.o bug 6111
On Sat, 2007-01-06 at 20:09 +0100, Andreas Johansson wrote:
The problem can be worked around by changing the AGP Aperture BIOS
setting. Changing this from 32MB to 256MB let me enable DRI. (As
suggested by https://bugs.freedesktop.org/show_bug.cgi?id=6111#c30)
I'm not sure this can be
I'm not sure this can be considered a bug in the radeon driver then,
unless maybe there's a way for it to detect the unusable AGP aperture
size.
Prior to upgrading to etch this system ran sarge with X.org packages
(6.9) from backports.org. Those were usable even with the aperture
size set to 32MB
On Sun, 2007-01-07 at 14:35 +0100, Andreas Johansson wrote:
If there are unusable aperture size, ideally either the
agpgart driver or the X server should refuse them. (Unless it's
hardware and/or BIOS bugs.)
Yes, if the agpgart driver can print a message about the aperture size
being too
Yes, if the agpgart driver can print a message about the aperture size
being too small, it should also be able report failure such that the X
server doesn't initialize the DRI.
Ah, sorry, my wording when referring to fd.o bug 6111 was a bit
unclear. On my system at least, agpgart doesn't complain
I've also experienced this bug, so this is more of a confirmation of
this problem on another system.
Running xserver-xorg-video-ati 6.6.3-2 on my system with DRI enabled
causes the X server to hang in some kind of loop. Keyboard and mouse
are unusable, but the system is still up, and remote
Michel Dänzer [EMAIL PROTECTED] writes:
If you suspect the hardware might be faulty, you could verify that with
another OS.
FYI, I changed my radeon 8500 by a new 9250, and everything works
nice. The strange thing is that I tried the 8500 in another computer
(also debian sid) where I don't
Michel Dänzer [EMAIL PROTECTED] writes:
It doesn't. Writeback is a minor performance optimization, the lack of
which should not affect operation of the X server.
If you suspect the hardware might be faulty, you could verify that with
another OS.
I tried on ubuntu 6.06, and it's having the
Michel Dänzer [EMAIL PROTECTED] writes:
On Wed, 2006-10-25 at 23:04 +0200, [EMAIL PROTECTED] wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
But it doesn't happen with version 6.6.2?
I'm not sure exactly when it stops working...
That would be very helpful to know though. Please try
On Wed, 2006-10-25 at 23:04 +0200, [EMAIL PROTECTED] wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
But it doesn't happen with version 6.6.2?
I'm not sure exactly when it stops working...
That would be very helpful to know though. Please try older versions,
e.g. from
Michel Dänzer [EMAIL PROTECTED] writes:
On Thu, 2006-10-19 at 21:41 +0200, [EMAIL PROTECTED] wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
And this doesn't happen with version 6.6.2? If so, it would be great if
you could try isolating the upstream change that causes it with
git-bisect.
Michel Dänzer [EMAIL PROTECTED] writes:
And this doesn't happen with version 6.6.2? If so, it would be great if
you could try isolating the upstream change that causes it with
git-bisect.
I'm afraid that's a bit too much as I don't know anything about git...
Loaddri
Does it also
On Thu, 2006-10-19 at 21:41 +0200, [EMAIL PROTECTED] wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
And this doesn't happen with version 6.6.2? If so, it would be great if
you could try isolating the upstream change that causes it with
git-bisect.
I'm afraid that's a bit too much as I
Package: xserver-xorg-video-ati
Version: 1:6.6.3-1
Severity: grave
When starting xserver, screen is blank (black) and the systems is frozen (SysRq
not working).
'vesa' drivers works but is really slow...
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL [Radeon
8500 LE]
On Sat, 2006-10-14 at 08:58 +0200, [EMAIL PROTECTED] wrote:
Package: xserver-xorg-video-ati
Version: 1:6.6.3-1
Severity: grave
When starting xserver, screen is blank (black) and the systems is frozen
(SysRq not working).
'vesa' drivers works but is really slow...
01:00.0 VGA compatible
22 matches
Mail list logo
