dri-devel October 2016

dri-devel@lists.freedesktop.org

215 participants
1390 discussions

[Bug 84500] New: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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: 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.

1 56

[Bug 84106] New: GPU faults with Xonotic 0.7
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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 --> 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.

1 7

[Bug 84017] New: HD 4670 only works with MSI disabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=84017 Priority: medium Bug ID: 84017 Assignee: dri-devel(a)lists.freedesktop.org Summary: HD 4670 only works with MSI disabled Severity: normal Classification: Unclassified OS: All Reporter: egore(a)gmx.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 106459 --> https://bugs.freedesktop.org/attachment.cgi?id=106459&action=edit dmesg of bootup using radeon.msi=-1 As mentioned on the dri-devel mailing list [1] the HD 4670 in one of my older systems is only capable of doing any 3D when booting with "radeon.msi=0". Find the dmesg of a and lspci output attached. [1] http://lists.freedesktop.org/archives/dri-devel/2014-September/067758.html -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 83800] New: 3DMark2003 crashes radeon with wine 1.7.26 + gallium nine
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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 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.

1 18

[Bug 83792] New: Kernel hangs on boot without nomodeset option
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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 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.

1 15

[Bug 83742] New: [radeonsi KMS] Monitors on DP outputs not enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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 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.

1 8

[Bug 83708] New: mplayer plays video using gpu hardware acceleraing(vdpau,uvd) kernel panic, Unable to handle kernel paging request at virtual address
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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 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.

1 20

[Bug 83616] New: Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=83616 Priority: medium Bug ID: 83616 Assignee: dri-devel(a)lists.freedesktop.org Summary: Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4 Severity: normal Classification: Unclassified OS: All Reporter: freedesktop(a)voorpost.net Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa linux git 86302eeadebfab94530b00f5e53a23f911ff41e4 is the first bad commit launching xonotic hangs and resets the gpu, game video output looks corrupted, then eventually reboots the system, or can only sysrq out mesa git current xorg server 1.16 [ 414.741] (--) RADEON(0): Chipset: "ATI RV730XT [Radeon HD 4670]" (ChipID = 0x9490) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 83556] New: Problem with resolution using adapter dvi to dsub
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=83556 Priority: medium Bug ID: 83556 Assignee: dri-devel(a)lists.freedesktop.org Summary: Problem with resolution using adapter dvi to dsub Severity: normal Classification: Unclassified OS: Linux (All) Reporter: filip.gawin(a)zoho.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Hi, I using i5 3470, radeon hd 7850 1gb, asrock b75 pro3. And also samsung syncmaster 710n, which has only d-sub port. My card hasn't it so I use adapter. My system tells me that the max resolution is 1024x800. But native of my monitor is 1280x1024. I can set wanted resolution using: xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync xrandr --addmode DVI-0 1280x1024_60.00 xrandr --output DVI-0 --mode 1280x1024_60.00 But adding it to start script doesn't chance anythink. How can i get native resolution on start X without complicate? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 82889] New: [drm:si_dpm_set_power_state] *ERROR* si_disable_ulv failed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=82889 Priority: medium Bug ID: 82889 Assignee: dri-devel(a)lists.freedesktop.org Summary: [drm:si_dpm_set_power_state] *ERROR* si_disable_ulv failed Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mmstickman(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Yet another bug I've encountered on my Radeon HD 7950 with kernel 3.16. -- You are receiving this mail because: You are the assignee for the bug.

1 25

← Newer
1
...
9
10
11
12
13
14
15
...
139
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2016