https://bugzilla.kernel.org/show_bug.cgi?id=39612
Summary: radeon blocks with new style fencing
Product: Drivers
Version: 2.5
Kernel Version: >= 2.6.37
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: linas_fi(a)ymail.com
CC: alexdeucher(a)gmail.com
Regression: Yes
I am using a Radeon HD 3600 in kernel 2.6.36 with xf86-video-ati (KMS). Since
2.6.37 when starting the X server the screen goes black and never shows the
desktop.
kernel 2.6.36
startx -> Screen goes black -> The wallpaper appears -> The DE loads
kernel >= 2.6.37
startx -> Screen goes black -> You can't switch virtual terminals -> REISUB ->
Downgrade kernel
Reproducible: Always
Bisecting shows that it started failing at
d0f8a854c340986359a3b0a97e380c71def7a440: drm/radeon/kms/r6xx+: use new style
fencing (v3)
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git;a=commi…
Downstream bug https://bugs.archlinux.org/task/23422
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=64257
Priority: medium
Bug ID: 64257
Assignee: dri-devel(a)lists.freedesktop.org
Summary: RS880 issues with r600-llvm-compiler
Severity: normal
Classification: Unclassified
OS: All
Reporter: mike(a)fireburn.co.uk
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Hi
Kwin starts with a black screen if I use r600-llvm-compiler on my RS880
When I switched off the llvm parts and just ran glxgears using
r600-llvm-compiler the gears looked like they were layered wrongly and slightly
darker
I'm not sure when this regression appeared - I'm guessing within the last two
weeks - I mostly ssh into the box
I'm always running the latest llvm, clang, libdrm and mesa
I didn't see anything strange in my dmesg or .xsession-errors or from the
glxgears text output
Could this be due to RS880 being singled out in llvm as a separate processor
variant?
ie r600g/llvm: Update radeon family mappings for LLVM backend or [PATCH 1/2]
R600: Add some new processor variants
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=50521
Summary: nouveau_acpi call _DSM with wrong parameter
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: alex.williamson(a)redhat.com
CC: alan(a)lxorguk.ukuu.org.uk, daniel(a)ffwll.ch
Regression: No
Cloning for nouveau
+++ This bug was initially created as a clone of Bug #32602 +++
Both drivers/gpu/drm/i915/intel_acpi.c and
drivers/gpu/drm/nouveau/nouveau_acpi.c call _DSM methods with parameters of
_DSM(Buffer, Integer, Integer, Integer). The ACPI spec defines the parameters
to be _DSM(Buffer, Integer, Integer, Package). On a UL30VT, the AML preforms
operations on Arg3 which are not valid for an Integer data type, resulting in
ACPI faults. Excerpt of DSDT:
Method (_DSM, 4, NotSerialized)
{
If (LEqual (Arg0, Buffer (0x10)
{
/* 0000 */ 0xA0, 0xA0, 0x95, 0x9D, 0x60, 0x00, 0x48, 0x4D,
/* 0008 */ 0xB3, 0x4D, 0x7E, 0x5F, 0xEA, 0x12, 0x9F, 0xD4
}))
{
Store (Zero, Local0)
Store (ShiftLeft (DerefOf (Index (Arg3, 0x03)), 0x18), Local0)
Add (ShiftLeft (DerefOf (Index (Arg3, 0x02)), 0x10), Local0, Local0)
Add (ShiftLeft (DerefOf (Index (Arg3, One)), 0x08), Local0, Local0)
Add (ShiftLeft (DerefOf (Index (Arg3, Zero)), Zero), Local0, Local0)
...
The Index operation is only valid on a Buffer, String, or Package, which is
perfectly reasonable given the definition of the _DSM call.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=50594
Bug #: 50594
Summary: VDPAU checks version of wrong DRM driver
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: s_j_newbury(a)yahoo.co.uk
I have two DRM devices, i965 on-board, and a Radeon HD5450 in a docking
station.
When both devices are enabled in my Xorg server layout "Screen0" is the i965,
and "Screen1", the Radeon.
When I run vdpauinfo or try using mplayer -vo vdpau on the Radeon, I
get the error:
do_winsys_init: DRM version is 1.6.0 but this driver is only
compatible with 2.3.x (kernel 2.6.34) or later.
This is the version of the intel DRM driver!
The i965 obviously doesn't do VDPAU, since it's a "classic" driver, the Radeon,
seems to be properly configured. DRI works fine on both. (glxgears etc)
I checked to see if it makes a difference whether card0<->card1, but it always
looks at the wrong DRM.
--
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=63599
Priority: medium
Bug ID: 63599
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600][r600] GPU lockup CP stall (kernel 3.8, 3.9)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: wojtask9(a)wp.pl
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 78069
--> https://bugs.freedesktop.org/attachment.cgi?id=78069&action=edit
lspci
This happens always with KDM, LightDM/XDM (xdm-archlinux package). Login screen
freezes (but I can move mouse pointer).
First I thought that was my configuration error but the same issue with knoppix
livecd (7.0.5, kernel 3.6.10, mesa-9.0.1)
Without Display Manager (startx from console) result is the same. Screen
appears but is frozen (test using xfce4 and kde). Without DM I don't see any
GPU lockup but Xorg.0.log shows errors.
Setting R600_HYPERZ=0 or R600_DEBUG=nohyperz doesn't help
system
kernel 3.8.5 or 3.9.0-rc7
mesa 9.1.1
other packages are up to date form arch repository
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=48191
Summary: radeon: trace dumped from r600_hdmi.c
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: dgbaley27(a)0x01b.net
Regression: No
Created an attachment (id=81831)
--> (https://bugzilla.kernel.org/attachment.cgi?id=81831)
dmesg output
This has been happening since 3.5, but I've just booted 3.6 and I am still
getting some worrying stuff in the kernel log. dmesg output attached. The trace
begins on line 631. I am passing audio=1 to radeon.ko. Audio does work despite
this error.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=38242
Summary: Distortion or console image displayed when starting
Widelands
Product: Drivers
Version: 2.5
Kernel Version: 3.0-rc4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: jlp.bugs(a)gmail.com
Regression: No
I just installed Widelands game (build15) on the new computer with following
hardware:
* ASUS P8H67 revision 3.0 motherboard - BIOS 1003
* Intel Core i5 2500K CPU
* Gigavyte GV-R575SL-1GI GPU (AMD Radeon HD 5750)
* 8 GiB DDR3 memory
I get this bug when I start the game. When the game comes up for the first time
the image is distorted. To get image back to normal I have to switch to some
other console, with Ctrl+Alt+F1 for example, and than back to the console with
X11. Then the image is OK and I can play the game. When I start the game for
the second time the image of the last visited non-x console is displayed. But
this is juts image, it appears it doesn't actually switch to that console, just
displays image of it and I still have to use keyboard to switch to non-X
console and back to console with X to fix the image.
I've also discovered a workaround for this behaviour. If I start the game from
terminal emulator (KDE Konzole) with "SDL_VIDEODRIVER=x11 widelands" there is
no problem. In this case the game first tries to use X11 and without the option
it tries to autodetect what to use so it looks like the bug happens when
probing other modes.
The software used is:
* Linux kernel 3.0-rc4
* Widelands build15
* mesa git-42e7a13
* libdrm from git
* xf86-video-ati from git
* xorg-server 1.10.99.901
* libsdl 1.2.14
* sdl-gfx 2.0.22
--- Comment #1 from Jure Repinc <jlp.bugs(a)gmail.com> 2011-06-25 15:09:11 ---
Created an attachment (id=63482)
--> (https://bugzilla.kernel.org/attachment.cgi?id=63482)
dmesg
--- Comment #2 from Jure Repinc <jlp.bugs(a)gmail.com> 2011-06-25 15:12:31 ---
Created an attachment (id=63492)
--> (https://bugzilla.kernel.org/attachment.cgi?id=63492)
lspci
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=36892
Summary: page faults / general protection faults under heavy 3d
load
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: niels_ole(a)salscheider-online.de
Regression: No
I get page faults or general protection faults under heavy 3d load (like
"sauerbraten", but sometimes switching windows with kwin is enough) in random
processes. I have a radeon hd 6870 and use r600g from mesa git.
This happens on 3.0-rc1 and 2.6.39. I am not sure if this is a problem with
older kernels, too, since I get gpu lockups with them.
I am not sure what could cause these problems, maybe some bug in gem / ttm?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.