https://bugs.freedesktop.org/show_bug.cgi?id=29200
Summary: [wine] Warcraft 3 crashes after trying to launch again
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: magnus(a)jensenligan.se
Hi, i'm trying to play Warcraft III and i can get it to launch sometimes but if
i exit after a succesful launch it will not launch again and i have to reboot.
i Get error message in dmesg about rejected command stream, please tell me
about how to debug this error further if that will help the driver.
radeon 0000:01:00.0: r600_cs_track_check:286 mask 0x0000000F | 0x0000000F no cb
for 0
radeon 0000:01:00.0: r600_packet3_check:1247 invalid cmd stream 470
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream
--
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=28223
Summary: Screen Blanks on launching racing game Vdrift
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: other
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: hysvats(a)gmail.com
Created an attachment (id=35808)
--> (https://bugs.freedesktop.org/attachment.cgi?id=35808)
Xorg.log
KMS Driver Stack details :
=========================
1) Kernel-2.6.32-21-generic-pae
2) Libdrm-2.4.19
3) Mesa-7.8-rc2
4) Xorg-server-1.7.4
5) ddx: xf86-video-ati-6.13.0
System Environment :
===================
O.S. - Ubuntu-10.04(32bit)
Asic - M97
CPU - Intel(R) Core(TM)@ 1.86GHz
Steps to Reproduce:
===================
1) Install Phoronix-test-suite from
http://www.phoronix-test-suite.com/releases/repo/pts.debian/files/phoronix-…
2) Install vdrift racing game
phoronix-test-suite install vdrift
3) Run the game with 1280x1024 or any other resolution
phoronix-test-suite run vdrift
Observation :
=============
Screen Blanks and intermittent corruption observed on the Desktop
--
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=27723
Summary: Vtx endian setup error under big endain CPU
Product: Mesa
Version: unspecified
Platform: PowerPC
OS/Version: other
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: raoxianhong(a)163.net
There is an error at line 965 of r700_assembler.c(mesa 7.8.1):
vfetch_instruction_ptr->m_Word2.f.endian_swap = SQ_ENDIAN_NONE;
the correct must be:
vfetch_instruction_ptr->m_Word2.f.endian_swap =
#if BIGENDIAN_CPU
SQ_ENDIAN_8IN32;
#else
SQ_ENDIAN_NONE;
#endif
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=42787
Summary: Video flickers on X1200 / RS690 over DVI
Product: Drivers
Version: 2.5
Kernel Version: 3.0.0
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: stephan.diestelhorst(a)gmail.com
Regression: No
I still experience flickering on the DVI of my on-board graphics card if I set
the mode to 1920x180 (ragrdless which timing 59.9 / 60 Hz). Tried both KMS /
UMS, no real difference. AFAICS, all pathes in other bug reports should be
picked up by now. It seems that graphics activity (moving a translucent
window) is more prone to blanking the display.
Killing upowerd does not help, so it is not a polling issue. CPU is is not
properly detected by the BIOS (too old, no upgrade available), so it may (?) be
that some registers (MTRRs?) are not set up properly.
Reducing the resolution does seem to help.
--
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=54381
Summary: [drm:radeon_atom_pick_pll] *ERROR* unable to allocate
a PPLL
Product: Drivers
Version: 2.5
Kernel Version: 3.7.2 and up
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: rose(a)semkath.de
Regression: No
I'm running a 3 monitor setup with a Radeon HD graphics card [Radeon HD 6000
Series]. I'm not using the proprietary drivers. Connectors are: 2 DVI and 1
HDMI. When I change the second DVI connection from a monitor to a projector and
try to set the correct resolution (1920x1080) it fails with the following error
message:
[15189.014994] [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL
[15189.015008] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on
[CRTC:12]
It changes the resolution but there are black areas at the sides and at the
bottom of the displayed picture. It only happens if I connect the projector,
not when the usual monitor is connected. This problem does not exist with
kernel version 3.6.11.
$ scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux semkath-desktop 3.8.0 #1 SMP PREEMPT Wed Feb 20 18:31:08 CET 2013 x86_64
AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux
Gnu C 4.7.2
Gnu make 3.82
binutils 2.23.1
util-linux 2.22.2
mount debug
module-init-tools 12
e2fsprogs 1.42.6
Linux C Library 2.16
Dynamic linker (ldd) 2.16
Procps UNKNOWN
Net-tools 1.60_p20120127084908
Kbd 1.15.5
Sh-utils 8.21
Modules Loaded snd_aloop kvm_amd firewire_ohci k10temp i2c_piix4
firewire_core
--
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=48357
Bug #: 48357
Summary: Display resolutions not detected correctly after
startup with VGA over DisplayPort
Classification: Unclassified
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: heroeschman(a)gmx.de
Created attachment 59545
--> https://bugs.freedesktop.org/attachment.cgi?id=59545
dmesg
Hi.
One of my monitors is a VGA LCD connected over DisplayPort. After startup not
all resolutions are detected but only resolutions up to 1024x768. However if i
disconnect the monitor and reconnect it again (at 287.472381 in the log file)
all screen resolutions are detected correctly.
The initial detection does not work and dmesg shows
"[drm:radeon_dp_i2c_aux_ch], aux i2c too many retries, giving up"
error messages. drm_helper_probe_single_connector_modes() then falls back and
probes some modes up to 1024x768 that is why higher resolutions are missing. No
idea why it works after reconnecting the monitor.
dmesg log is "dmesg | grep drm" with drm.debug=0x0e from a 3.4-rc1 kernel but
the problem already happend in earlier versions. The problem also happens if
only the VGA monitor is connected.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=34772
Summary: [radeon] [R300] GPU lockups with when KMS is enabled
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: rbrito(a)ime.usp.br
Regression: No
Created an attachment (id=57062)
--> (https://bugzilla.kernel.org/attachment.cgi?id=57062)
dmesg output right after the lock up, obtained via the network
Hi there.
I have been getting some Oopses/stack traces when I try to use my iBook G4
(with an "ATI Technologies Inc M11 NV/FireGL Mobility T2e" card) and I enable
KMS.
The userland here is Debian unstable with the DRM from experimental, but I am
willing to test anything that you would like me to.
For example, attached is the last of a series of such Oopses that I got when I
tried to test if a video was playing or not with mplayer.
I tried to use 2.6.39-rc{5,6}, but upon boot I get messages telling me that
there were failures and that hardware acceleration will be disabled and I that
I get is a desktop with colors distorted like if there were some endianness
issues.
This is, BTW, part of my attempts to get Linux running well on PowerPC, with
some of my logs (with photos) present at my homepage:
http://www.ime.usp.br/~rbrito/linux/debug-r300/
Please, if there is anything that I can provide to fix this, let me know and I
will do my best.
Thanks, Rogério Brito.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=42603
Summary: Watching video with radeon oss driver sometimes leads
to kernel panic
Product: Drivers
Version: 2.5
Kernel Version: 3.0.17
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: bugzilla.kernel.org(a)boris64.net
Regression: No
Created an attachment (id=72119)
--> (https://bugzilla.kernel.org/attachment.cgi?id=72119)
picture of panic
Watching video (mostly flashvideo and dvb-s/c in kaffeine)
sometimes leads to kernel panic with the radeon oss driver.
This is somehow not reproducable, but happens about once a week.
It happens for quite some time (1/2 a year?) now,
also happened on older kernels, actually since i own this card...
Attached is a screenshot of the panic.
Used software:
kernel-3.0.17
xorg-server-1.11.3
mesa+xf86-video-radeon: latest git snapshot(s)
--
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=42616
Summary: Radeon Kernel Mode Setting sets wrong mode
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: thomas.jones(a)utoronto.ca
Regression: No
I have a Radeon HD 3470, connected to a Dell P2010H monitor via Display Port.
The monitor's native resolution is 1600x900, and everything works correctly
with UMS, however if I use KMS I cannot use that mode, I can use at least
1024x768, 1280x1024, and 1152x864 with KMS, but no matter how I try I cannot
get it to work in 1600x900. I have tried with the CVT timings, (reduced
blanking and not) and with the ones provided in the monitor's EDID.
If I attempt to set any of those modes (the 1600x900) with KMS on the monitor
claims that I'm using an unsupported mode. UMS works just fine though.
I'm running Fedora, and I don't think this is a regression in the kernel since
I don't think this computer has ever worked with KMS.
Right now what I've done is I have set the kernel command line to boot with
1152x864 and KMS, then I tried to use xrandr to change modes and the monitor
just complained.
dmesg doesn't seem to have anything useful to say, and neither does Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.