https://bugs.freedesktop.org/show_bug.cgi?id=31619
Summary: Desktop freezes quickly every now and then with dynpm
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: ernstp(a)gmail.com
This is with linux 2.6.37 from xorg-edgers.
If I do
echo dynpm > /sys/class/drm/card0/device/power_method
Run compiz
Grab a window and move it around, every now it freezes quickly and the resumes.
The mouse movement during that period is completely lost.
I'll try more kernels...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=34155
Summary: [drm:radeon_crtc_page_flip] *ERROR* failed to reserve
new rbo buffer before flip
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: alexandre.f.demers(a)gmail.com
I have a 780G chipset (HD3200), using xf86-video-ati 6.14.0 with Xserver 1.9,
kernel 2.6.37 and 2.6.38-rc4. Looking in my kern.log, I see regularly this
error message:
[drm:radeon_crtc_page_flip] *ERROR* failed to reserve new rbo buffer before
flip
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=34096
Summary: r300: Cannot get a relocation in
radeon_drm_cs_write_reloc.
Product: Mesa
Version: git
Platform: Other
URL: http://www.minecraft.net/
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=43168)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43168)
more dmesg output
When starting the game Minecraft, I'm getting these messages in the terminal:
radeon: The kernel rejected CS, see dmesg for more information.
r300: Cannot get a relocation in radeon_drm_cs_write_reloc.
dmesg:
[ 527.282839] [drm:r100_packet3_load_vbpntr] *ERROR* No reloc for packet3 47
[ 527.282841] [drm] ib[13751]=0xC0052F00
[ 527.282842] [drm] ib[13752]=0x00000023
[ 527.282843] [drm] ib[13753]=0x08010803
[ 527.282844] [drm] ib[13754]=0x000EA840
[ 527.282845] [drm] ib[13755]=0x000EA858
[ 527.282846] [drm] ib[13756]=0x00000802
[ 527.282847] [drm] ib[13757]=0x000EA84C
[ 527.282849] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
If needed, I will try and bisect when I have more time.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 6.13.2
-- xserver: 1.9.4
-- mesa: 04c5cc5b8bec1f34f2405b08fd0d9ed6bd70ea61
-- drm: 2.4.23
-- kernel: 2.6.37
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=38173
Summary: DXT3 and DXT5 broken on Cayman gpu
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bobahu4(a)gmail.com
Using linux 3.0-rc2 kernel and mesa@git-eca3e91 + ati-ddx from git
libtxc_dxtn is also installed.
Radeon 6970 using g3d driver.
Runing texcmp test from demos.
DXT1 works fine, DXT3 and DXT5 gives broken image (on both ARGB and RGB modes)
same corruptions can be seen in sauerbraten menu (image on bg - corrupted) or
in quake4, unigine tropics.
exactly same system with 6870 gpu - dxt1, dxt3, dxt5 works fine.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=33038
Summary: celestia crashes with error: "radeon_cs_gem.c:181:
cs_gem_write_reloc: Assertion `boi->space_accounted'
failed"
Product: Mesa
Version: 7.10
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: acelists(a)atlas.sk
Celestia program starts, draws the universe for a few seconds, then crashes
with the error message: "radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion
`boi->space_accounted' failed".
Using kernel 2.6.36.2 (2.6.37 already out, but hangs the X server at start),
Mesa 7.10 r600c, radeon 6.13.99-af2e6d7d2f1b3d8f8f6b0acfb2b7b0cfaff7bcdb.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=38010
Summary: DVI output not working with radeon on RV610
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: darkbasic4(a)gmail.com
Created an attachment (id=47622)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47622)
dmesg
Hi, I have an RV610 card attached to an LG 22LH2000. The LG 22LH2000 has a
1366x768 native resolution and does have VGA and HDMI but not DVI. The Radeon
HD2400 does have VGA and DVI but not HDMI, so I'm using a DVI-HDMI converter.
When I use the VGA output everything works fine, but I don't get a 1:1 pixel
mapping because I have to set a 1360x768 or 1368x768 resolution and the monitor
is not smart enough when using vga. Instead when I attach the monitor to my
laptop's Intel GMA45 HDMI output I can get a 1:1 pixel mapping even using a
1360x768 resolution.
Unfortunately when using the HD2400 DVI output the monitor does not show
anything, at least after loading the radeon module. In fact when loading the
bios or starting grub the DVI output works flawlessly. nomodeset does not help.
I even tried setting another resolution with xrandr (it automatically set
1920x1080i, but I tried 1360x768, 1280x800, 1024x768 and 800x600 and it still
does not work).
Distro is Debian Unstable amd64 with kernel 2.6.39 and xorg-edgers ppa.
It's the only monitor I will be able to use for a couple of months, it's
critical for me to get it working.
Thank you
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=28905
Summary: missing scene triangle in scorched3d using KMS r600
Product: Mesa
Version: 7.6
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: acelists(a)atlas.sk
I see a missing part of the scene when playing Scorched3d. It is triangle
shaped region originating from the bottom of the window. It only happens when
using KMS. UMS renders fine. I am using xorg 1.7.7, mesa 7.8.1, radeon driver
6.13, kernel 2.6.34.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30502
Summary: atmospheres of planets get transparent when going away
from planets in celestia
Product: Mesa
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: acelists(a)atlas.sk
Created an attachment (id=39071)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39071)
Far view of Titan - atmosphere transparent
The atmosphere of some planets (not all) gets transparent when approaching the
planets. As intended, the atmosphere of Titan should be opaque at all distances
(except when standing on the surface). However, currently it gets more
transparent as the observer is moving AWAY from the planet. From the distance,
atmosphere is invisible, near the planet it is opaque.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=40034
Summary: E-350 misprocesses shader
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: curaga(a)operamail.com
Created an attachment (id=50154)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50154)
Screenshot of the failure
If you pull from my e350bug branch (
http://cgit.freedesktop.org/~cand/mesa/log/?h=e350bug ) and execute
"pp_jimenezmlaa=8 glxgears", you should see a fully white window. What actually
happens on the E-350 is attached.
The gist is "a long shader; output = white;", which should always create white,
since the shader has no kilp/discard. While this would rarely happen in
practise (the glsl compiler would eliminate dead code), this is a clear bug,
and I believe this is causing me other grief.
While the branch is based on ~4 weeks old master, the bug is present when
merged with today's master.
The kernel I'm on is 3.0.1.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.