https://bugs.freedesktop.org/show_bug.cgi?id=85638
Bug ID: 85638
Summary: system crash randomly with no errors
Product: DRI
Version: XOrg CVS
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: marcoboffo.waves(a)gmail.com
Created attachment 108676
--…
[View More]> https://bugs.freedesktop.org/attachment.cgi?id=108676&action=edit
Picture of my screen
Everyday, my system crashes randomly and shows random colors on my screens.
(Yes, dual monitor)
I can't reproduce the bug but it seems to happen on large screen update or
little gnome3 transitions.
complete dmesg: http://pastebin.com/szzwGKx2
uname -r: 3.17.1-1-ARCH
The Xorg.log is untouched since the beginning of this month, so I don't think
it can be relevant for the bugfix.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=85469
Bug ID: 85469
Summary: Brightness too high on internal AMD/ATI graphics
device, but fine with external AMD/ATI graphics card
Product: DRI
Version: XOrg CVS
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
…
[View More]Reporter: paulepanter(a)users.sourceforge.net
Created attachment 108433
--> https://bugs.freedesktop.org/attachment.cgi?id=108433&action=edit
output of `radeonreg regs dce4` built from radeontool-1.6.3-10-g6b5e7c6
As reported on the list dri-devel [1], the brightness of the internal graphics
card is too high on the ASRock E350M1 [2].
Please find the output of `radeonreg regs dce4` attached and I’ll attach the
Linux kernel 3.16.5 messages and the Video BIOS too.
[1] Brightness too high on internal AMD/ATI graphics device, but fine with
external AMD/ATI graphics card
http://lists.freedesktop.org/archives/dri-devel/2014-July/thread.html#63006
[2] http://www.asrock.com/mb/amd/e350m1/
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=85180
Bug ID: 85180
Summary: [drm:r100_ring_test] *ERROR* radeon: ring test failed
(scratch(0x15E4)=0xCAFEDEAD)
Product: DRI
Version: unspecified
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
…
[View More]Reporter: wrgcpp(a)gmail.com
Created attachment 108036
--> https://bugs.freedesktop.org/attachment.cgi?id=108036&action=edit
dmesg
I'm using Debian Jessie, kernel 3.16.3, my graphic card is
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350
[Radeon 9550]
System is booting normally, but GPU acceleration can't start.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=84500
Priority: medium
Bug ID: 84500
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: …
[View More]DRI
On a 7950, I keep getting this error from time to time in dmesg:
radeon 0000:01:00.0: Packet0 not allowed!
I have associated this error with playing either html5 or flash videos. It may
happen when playing offline movies, but I can't tell since I haven't tested it.
When the error happens, there is a slight "stuttering" (from a fraction of
second to a few seconds). And then it continues.
There is nothing in Xorg.0.log about it, and no other message than "radeon
0000:01:00.0: Packet0 not allowed!" in dmesg.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=84106
Priority: medium
Bug ID: 84106
Assignee: dri-devel(a)lists.freedesktop.org
Summary: GPU faults with Xonotic 0.7
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 106566
…
[View More] --> https://bugs.freedesktop.org/attachment.cgi?id=106566&action=edit
dmesg
I have an HD 7950 with latest graphic stack from git, including LLVM 3.6 git
from today. kernel is drm-next-3.18-wip from today
(3.17.0-rc5-drm-next-3.18-wip).
I was running some benchmarks
(http://openbenchmarking.org/result/1409197-SO-1407298SO78) while I noticed
sometimes the picture froze and then after a second or two it kept running the
benchmark ultra fast. when the benchmark finished I noticed lots of GPU faults
in dmesg: https://paste.lugons.org/show/5981/
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=83800
Priority: medium
Bug ID: 83800
Assignee: dri-devel(a)lists.freedesktop.org
Summary: 3DMark2003 crashes radeon with wine 1.7.26 + gallium
nine
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
…
[View More] Product: DRI
HD 7950
Linux 3.17.0-rc2-core-avx-i-drm-next-3.18 20140912
llvm 3.6 git
xorg-server 1.15.1 + glamor git
mesa git + gallium nine
wine 1.7.26 + gallium nine
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=83792
Priority: medium
Bug ID: 83792
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Kernel hangs on boot without nomodeset option
Severity: normal
Classification: Unclassified
OS: All
Reporter: wayland(a)wayland.id.au
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Hi all. I …
[View More]have a Radeon FireMV 2400. I'm attempting to upgrade from Fedora 13
(kernel 2.6.33) to Fedora 20. More recent kernels have not worked for me; I
recently discovered that if I use the nomodeset option, then I can book, but
xorg no longer functions. Since it seems that using the nomodeset option is no
longer going to be supported, I need to make this work without the nomodeset
option. Unfortunately, the computer hangs (no ping via network) during boot.
I tried to give it the netconsole option, but this did not seem to produce any
results. What else can I try to help resolve this problem?
Thanks,
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=83742
Priority: medium
Bug ID: 83742
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi KMS] Monitors on DP outputs not enabled
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: RalfPeter.Rohbeck(a)quantum.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
…
[View More] Product: DRI
I've been running with 4 monitors on my 7850 for a long time but after a Debian
jessie upgrade the two monitors on the DP outputs are no longer enabled.
Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760881
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=83708
Priority: medium
Bug ID: 83708
Assignee: dri-devel(a)lists.freedesktop.org
Summary: mplayer plays video using gpu hardware
acceleraing(vdpau,uvd) kernel panic, Unable to handle
kernel paging request at virtual address
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: zduo006(a)163.com
…
[View More]Hardware: SPARC
Status: NEW
Version: 9.2
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 106051
--> https://bugs.freedesktop.org/attachment.cgi?id=106051&action=edit
kernel panic messages
Hi, I try to using gpu hardware accelerate to play video from mplayer
(vdpau+uvd) . The machine architecture is sparc64,video card is radeon
HD7450,OS version is redhat7,kernel version is 3.10.0, mplayer version is
1.1-21,mesa version is 9.2.5-6. But everything is ok on X86 platforms, all
versions are the same.
The kernel panic occured when radeon call radeon_cs_ioctl to receive
the command stream from libdrm interface. and then radeon_cs_ib_chunk() call
radeon_uvd_cs_parse to parse the command.
First I thought this error maybe occured in a permanent position and
maybe the ioctl data or size mismatch between user space and kernel space ,I
set 1 to /sys/module/drm/para... to open drm debug switch , after I catch the
messages, the panic occur everywhere .the error context maybe after
RADEON_GEM_WAIT_IDLE? after RADEON_GEM_CREATE and so forth. so is not the data
stream error during ioctl.
And I check the changelog from 3.10 to 3.15, no patch about this.
Other, I run rpm -e mesa-vdpau-drivers to uninstall the devices driver
from mesa ,the mplayer can play video stably using cpu , when I install this
package,the blue screen is come out . and I must run mplayer -vo x11 to solve
the blue screen problem.
Because I am not clearly about the framework of the mesa-vdpau-driver
and uvd. Can anyone help me ? Thks
the error messages is below:
pid=3037, dev=0xe200, auth=1, RADEON_GEM_WAIT_IDLE
Oct 8 21:43:26 localhost kernel: [17318.899669] pid=4483, dev=0xe200, auth=1,
RADEON_GEM_WAIT_IDLE
Oct 8 21:43:26 localhost kernel: [17318.902069] Unable to handle kernel paging
request at virtual address 000000ca14312000
Oct 8 21:43:26 localhost kernel: [17318.902090] tsk->{mm,active_mm}->context =
0000000000000a2b
Oct 8 21:43:26 localhost kernel: [17318.902104] tsk->{mm,active_mm}->pgd =
fffff80008f90000
Oct 8 21:43:26 localhost kernel: [17318.902119] \|/ ____ \|/
Oct 8 21:43:26 localhost kernel: [17318.902119] "@'/ .. \`@"
Oct 8 21:43:26 localhost kernel: [17318.902119] /_| \__/ |_\
Oct 8 21:43:26 localhost kernel: [17318.902119] \__U_/
Oct 8 21:43:26 localhost kernel: [17318.902169] mplayer(4483): Oops [#1]
Oct 8 21:43:26 localhost kernel: [17318.902186] CPU: 28 PID: 4483 Comm:
mplayer Not tainted 3.10.0-54.0.1.el7.4ACL.sparc64 #1
Oct 8 21:43:26 localhost kernel: [17318.902201] task: fffff800faa2a200 ti:
fffff800fbec4000 task.ti: fffff800fbec4000
Oct 8 21:43:26 localhost kernel: [17318.902220] TSTATE: 0000004411001607 TPC:
00000000007f573c TNPC: 00000000007f5740 Y: 00000000 Not tainted
Oct 8 21:43:26 localhost kernel: [17318.902252] TPC:
<radeon_uvd_cs_parse+0x414/0x7b4>
Oct 8 21:43:26 localhost kernel: [17318.902267] g0: 0000000000083a15 g1:
000000ca14312000 g2: 000000ca14312000 g3: 0000000004314000
Oct 8 21:43:26 localhost kernel: [17318.902285] g4: fffff800faa2a200 g5:
fffff800fc2fe000 g6: fffff800fbec4000 g7: 0000000010000000
Oct 8 21:43:26 localhost kernel: [17318.902301] o0: 0000000000000000 o1:
fffff800fbec7860 o2: 0000000000000000 o3: 0000000004314000
Oct 8 21:43:26 localhost kernel: [17318.902317] o4: 0000000000000800 o5:
fffff800f62d4840 sp: fffff800fbec6f91 ret_pc: 00000000007f56f4
Oct 8 21:43:26 localhost kernel: [17318.902336] RPC:
<radeon_uvd_cs_parse+0x3cc/0x7b4>
Oct 8 21:43:26 localhost kernel: [17318.902352] l0: fffff80008dbbbc0 l1:
0000000000a213c8 l2: 0000000000000003 l3: 0000000000000001
Oct 8 21:43:26 localhost kernel: [17318.902366] l4: 000000000000ef10 l5:
0000000000d7fb10 l6: 0000000000d7fae8 l7: 0000000000d7fac8
Oct 8 21:43:26 localhost kernel: [17318.902382] i0: fffff800fbec7948 i1:
0000000000000000 i2: 000000000000ec00 i3: fffff800e30b9000
Oct 8 21:43:26 localhost kernel: [17318.902398] i4: 000000ca14312000 i5:
0000000000000000 i6: fffff800fbec7091 i7: 00000000007a1e5c
Oct 8 21:43:26 localhost kernel: [17318.902429] I7:
<radeon_cs_ioctl+0x394/0x930>
Oct 8 21:43:26 localhost kernel: [17318.902439] Call Trace:
Oct 8 21:43:26 localhost kernel: [17318.902458] [00000000007a1e5c]
radeon_cs_ioctl+0x394/0x930
Oct 8 21:43:26 localhost kernel: [17318.902486] [000000000073d1ac]
drm_ioctl+0x2fc/0x420
Oct 8 21:43:26 localhost kernel: [17318.902516] [0000000000518c94]
vfs_ioctl+0x24/0x40
Oct 8 21:43:26 localhost kernel: [17318.902537] [0000000000519518]
do_vfs_ioctl+0x440/0x4e0
Oct 8 21:43:26 localhost kernel: [17318.902560] [00000000005195e4]
SyS_ioctl+0x2c/0x50
Oct 8 21:43:26 localhost kernel: [17318.902588] [00000000004061b4]
linux_sparc_syscall+0x34/0x44
Oct 8 21:43:26 localhost kernel: [17318.902607] Disabling lock debugging due
to kernel taint
Oct 8 21:43:26 localhost kernel: [17318.902633] Caller[00000000007a1e5c]:
radeon_cs_ioctl+0x394/0x930
Oct 8 21:43:26 localhost kernel: [17318.902657] Caller[000000000073d1ac]:
drm_ioctl+0x2fc/0x420
Oct 8 21:43:26 localhost kernel: [17318.902681] Caller[0000000000518c94]:
vfs_ioctl+0x24/0x40
Oct 8 21:43:26 localhost kernel: [17318.902702] Caller[0000000000519518]:
do_vfs_ioctl+0x440/0x4e0
Oct 8 21:43:26 localhost kernel: [17318.902721] Caller[00000000005195e4]:
SyS_ioctl+0x2c/0x50
Oct 8 21:43:26 localhost kernel: [17318.902742] Caller[00000000004061b4]:
linux_sparc_syscall+0x34/0x44
Oct 8 21:43:26 localhost kernel: [17318.902757] Caller[fffff801086074ac]:
0xfffff801086074ac
Oct 8 21:43:26 localhost kernel: [17318.902765] Instruction DUMP: 913b6000
c25fa7cf b800401c <e0072008> 80a42000 12480007 fa072004 11002884 130035fe
Oct 8 21:43:30 localhost kernel: [17323.141686] pid=3037, dev=0xe200, auth=1,
RADEON_GEM_CREATE
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]