dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 59903] New: [RS880] Xorg.0.log: flip queue failed: Device or resource busy
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=59903 Priority: medium Bug ID: 59903 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RS880] Xorg.0.log: flip queue failed: Device or resource busy Severity: normal Classification: Unclassified OS: All Reporter: michaell(a)gmx.org Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 73686 --> https://bugs.freedesktop.org/attachment.cgi?id=73686&action=edit dmesg /var/log/Xorg.0.log is full with: [ 1599.434] (WW) RADEON(0): flip queue failed: Device or resource busy [ 1599.434] (WW) RADEON(0): Page flip failed: Device or resource busy running up-to-date gentoo-system, with the following (unstable) packages linux-3.8.0-rc5 compiled a few minutes ago xorg-server-1.13.1 compiled a few minutes ago libdrm from git compiled a few minutes ago mesa from git compiled a few minutes ago xf86-video-ati from git compiled a few minutes ago 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4290] my system is working as an htpc and is running fine, no crashes or oops slim is login my user and starts xbmc automatic xbmc in fullscreen is the only graphical application the system is connected to my tv through hdmi if i switch with my remote through the xbmc-menu or watch a video the xorg-log is spam the whole time with page filp errors if i leave xbmc alone, so the log is spam every few seconds with page flip errors is this related to this bug? https://bugs.freedesktop.org/show_bug.cgi?id=58659 my system is working fine, no crashes or oops so far -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 59219] New: [radeon BUG] Sleeping function called from invalid context
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=59219 Priority: medium Bug ID: 59219 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeon BUG] Sleeping function called from invalid context Severity: minor Classification: Unclassified OS: Linux (All) Reporter: ebiggers3(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 72816 --> https://bugs.freedesktop.org/attachment.cgi?id=72816&action=edit dmesg output showing 2 instances of radeon BUG during resume I am running linux-3.8-rc3 on AMD64 with various debugging options enabled, including CONFIG_DEBUG_SLAB. When resuming the system from suspend-to-memory, I run into a warning and stacktrace regarding kmem_cache_alloc() being called from an invalid context in ttm_bo_move_accel_cleanup(). dmesg output attached. Marked as minor because suspend still works properly (at least the times I've tried it). Based on the source code and object file it appears that the memory allocation is actually the kzalloc() at the beginning of ttm_buffer_object_transfer(). Graphics card is: 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 58914] New: Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=58914 Priority: medium Bug ID: 58914 Assignee: dri-devel(a)lists.freedesktop.org Summary: Cannot start Radeon driver: "drmOpenByBusid: drmGetBusid reports " no bus ID Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: david.hagood(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 72358 --> https://bugs.freedesktop.org/attachment.cgi?id=72358&action=edit X Start up log messages The Radeon driver will not load with the Radeon kernel drivers in Linux 3.8.0 The following is an excerpt from the startup: [ 109.112] (II) Loading extension DRI2 [ 109.112] (II) LoadModule: "radeon" [ 109.112] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [ 109.112] (II) Module radeon: vendor="X.Org Foundation" [ 109.112] compiled for 1.12.3, module version = 7.0.99 [ 109.112] Module class: X.Org Video Driver [ 109.112] ABI class: X.Org Video Driver, version 12.0 [ 109.112] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), (many cards snipped) [ 109.114] (--) using VT number 8 [ 109.119] (II) [KMS] Kernel modesetting enabled. [ 109.120] (II) RADEON(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 109.120] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 109.120] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 109.120] (==) RADEON(0): Default visual is TrueColor [ 109.120] (==) RADEON(0): RGB weight 888 [ 109.120] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 109.120] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f) [ 109.120] drmOpenDevice: node name is /dev/dri/card0 [ 109.120] drmOpenDevice: open result is 9, (OK) [ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0 [ 109.120] drmOpenDevice: node name is /dev/dri/card0 [ 109.120] drmOpenDevice: open result is 9, (OK) [ 109.120] drmOpenByBusid: drmOpenMinor returns 9 [ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0 [ 109.120] drmOpenDevice: node name is /dev/dri/card0 [ 109.120] drmOpenDevice: open result is 9, (OK) [ 109.120] drmOpenByBusid: drmOpenMinor returns 9 [ 109.120] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [ 109.120] drmOpenByBusid: drmGetBusid reports That last line is not a copy/paste issue - it literally is "[ 109.120] drmOpenByBusid: drmGetBusid reports " (as in, there is no bus ID given) Then the X Radeon driver looks for any other DRI node, fails, and dies. [ 109.120] drmOpenDevice: node name is /dev/dri/card1 [ 109.125] drmOpenByBusid: drmOpenMinor returns -1 (snip many other searches) [ 109.170] drmOpenDevice: node name is /dev/dri/card14 [ 109.174] drmOpenByBusid: drmOpenMinor returns -1 [ 109.174] drmOpenDevice: node name is /dev/dri/card15 [ 109.178] drmOpenByBusid: drmOpenMinor returns -1 [ 109.178] drmOpenDevice: node name is /dev/dri/card0 [ 109.178] drmOpenDevice: open result is 9, (OK) [ 109.178] drmOpenDevice: node name is /dev/dri/card0 [ 109.178] drmOpenDevice: open result is 9, (OK) [ 109.178] drmGetBusid returned '' [ 109.178] (EE) RADEON(0): [drm] failed to set drm interface version. [ 109.178] (EE) RADEON(0): Kernel modesetting setup failed [ 109.178] (II) UnloadModule: "radeon" [ 109.178] (EE) Screen(s) found, but none have a usable configuration. I have tried the following: 1) adding the following parameters in /etc/modprobe.d/radeon.conf options radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1 2) Adding the following to /etc/initramfs-tools/modules radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1 and rebuilding the ramdisk. The kernel has the following configuration with respect to the Radeon drivers: CONFIG_DRM_RADEON=m CONFIG_DRM_RADEON_KMS=y # CONFIG_FB_RADEON is not set -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 58747] New: [RS780] Backtrace if firmware is not available on kernel-3.7
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=58747 Priority: medium Bug ID: 58747 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RS780] Backtrace if firmware is not available on kernel-3.7 Severity: normal Classification: Unclassified OS: All Reporter: ojab(a)ojab.ru Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 72109 --> https://bugs.freedesktop.org/attachment.cgi?id=72109&action=edit Related dmesg output After updating to kernel 3.7 I get backtrace if booting without firmware available (related dmesg part in the attached file). Also reproducible with kernel 3.7.1. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 57567] New: 3.7 radeonfb broken on efivga screens
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=57567 Priority: medium Bug ID: 57567 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3.7 radeonfb broken on efivga screens Severity: normal Classification: Unclassified OS: All Reporter: bobahu4(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Ubuntu 12.10 MacPro3,1 stock 3.5 kernel and 3.7-rcX ppa kernel booting via efi with grub2 ati cards have broken framebuffer on 3.7 (all is fine on 3.5) tried 2600xt, 6870, 6970 (all have efi part in rom, showing efi boot screen) on 3.7, when radeonfb activates, I see for a moment two sides of screen (left and right) swapped (not mirrored), then(when X start) only very few lines on top of screen is actualy showing something(I can see part of mouse pointer there), rest is filled with one color. Same result with all cards I mentioned. -- You are receiving this mail because: You are the assignee for the bug.

1 70

[Bug 56878] New: FireGL Mobility T2: WebGL under firefox16 freezes system
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56878 Priority: medium Bug ID: 56878 Assignee: dri-devel(a)lists.freedesktop.org Summary: FireGL Mobility T2: WebGL under firefox16 freezes system Severity: normal Classification: Unclassified OS: Linux (All) Reporter: miri(a)turboprinzessin.de Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 69702 --> https://bugs.freedesktop.org/attachment.cgi?id=69702&action=edit kernel messages of the crash When opening http://lwn.net/Articles/522127/ with firefox16 the screen goes black for a moment and then reappears for a few seconds after which it goes black again. This cycle goes on a few times after which the system completely locks up (even Magic Sysrq seems to have no effect). I don't know if it is related but sometimes opening huge images in firefox causes X to crash, too. This, however, doesn't freeze the kernel and beside the crash itself everything works normally afterwards. kernel: 3.6.6 xorg-server: 1.13.0 xf86-video-ati: 7.0.0 mesa: 9.0 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 56743] New: Invalid command stream (bad START_3D) on DIS gpu
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56743 Priority: medium Bug ID: 56743 Assignee: dri-devel(a)lists.freedesktop.org Summary: Invalid command stream (bad START_3D) on DIS gpu Severity: normal Classification: Unclassified OS: Linux (All) Reporter: intergalactic.anonymous(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 69522 --> https://bugs.freedesktop.org/attachment.cgi?id=69522&action=edit dmesg output On my muxed hybrid system (Lenovo IdeaPad U455) X works fine with IGD gpu (RS780M), but screen gets garbled when DIS gpu (RV710) is active. In dmesg output there are lots of following messages: [drm:r600_packet3_check] *ERROR* bad START_3D [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! My system is: Lenovo IdeaPad U455 with RS780M and RV710 gpus. linux-3.7.0-rc3+ libdrm-2.4.39 xf86-video-ati-6.14.6 mesa-9.0 glu-9.0 xorg-server-1.12.3 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 56561] New: kernel > 3.4.7 breaks KMS on rv515 (r300)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56561 Priority: medium Bug ID: 56561 Assignee: dri-devel(a)lists.freedesktop.org Summary: kernel > 3.4.7 breaks KMS on rv515 (r300) Severity: major Classification: Unclassified OS: Linux (All) Reporter: inaudible(a)simplesuperlativ.es Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI I performed a system update (arch linux) but have experienced issues with KMS on any kernel past 3.4.7 (all of 3.5 up till the current 3.6.3). The boot sequence stalls at the point where the KMS hooks usually kick in and referesh the screen. I can make the kernel boot with 'nomodeset' option. https://bugs.freedesktop.org/show_bug.cgi?id=54662 looks similar, but the none of the 3.6 kernels i've tried resove this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 56329] New: System does not hibernate ATI Technologies Inc RV370 secondary [Sapphire X550 Silent]
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56329 Priority: medium Bug ID: 56329 Assignee: dri-devel(a)lists.freedesktop.org Summary: System does not hibernate ATI Technologies Inc RV370 secondary [Sapphire X550 Silent] Severity: normal Classification: Unclassified OS: Linux (All) Reporter: orion(a)cora.nwra.com Hardware: x86 (IA32) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI System fails to hibernate with: 01:00.1 Display controller: ATI Technologies Inc RV370 secondary [Sapphire X550 Silent] Was working fine with an nVidia card. /var/log/pm-suspend.log ends with: Tue Oct 23 09:41:42 MDT 2012: performing hibernate Nothing of note in /var/log/messages. Screen goes blank even with no suspend console, but system does not hibernate. kernel 3.6.3-1.fc17.i686.PAE xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.i686 mesa-dri-drivers-8.0.4-1.fc17.i686 [ 5.972923] [drm] Initialized drm 1.1.0 20060810 [ 6.005177] [drm] radeon defaulting to kernel modesetting. [ 6.005182] [drm] radeon kernel modesetting enabled. [ 6.005275] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [ 6.009395] [drm] initializing kernel modesetting (RV380 0x1002:0x5B63 0x17AF:0x3000). [ 6.009431] [drm] register mmio base: 0xDFDE0000 [ 6.009435] [drm] register mmio size: 65536 [ 6.009576] [drm] Generation 2 PCI interface, using max accessible memory [ 6.009633] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 6.009637] [drm] Driver supports precise vblank timestamp query. [ 6.009763] [drm] radeon: irq initialized. [ 6.012413] [drm] Detected VRAM RAM=256M, BAR=256M [ 6.012421] [drm] RAM width 128bits DDR [ 6.014950] [drm] radeon: 256M of VRAM memory ready [ 6.014955] [drm] radeon: 512M of GTT memory ready. [ 6.014987] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 6.016566] [drm] radeon: 1 quad pipes, 1 Z pipes initialized. [ 6.019858] [drm] PCIE GART of 512M enabled (table at 0x00000000C0040000). [ 6.031353] [drm] Loading R300 Microcode [ 6.035532] [drm] radeon: ring at 0x00000000A0001000 [ 6.035557] [drm] ring test succeeded in 1 usecs [ 6.035921] [drm] ib test succeeded in 0 usecs [ 6.036254] [drm] Radeon Display Connectors [ 6.036258] [drm] Connector 0: [ 6.036260] [drm] DVI-I-1 [ 6.036262] [drm] HPD2 [ 6.036265] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 6.036266] [drm] Encoders: [ 6.036268] [drm] CRT1: INTERNAL_DAC1 [ 6.036270] [drm] DFP2: INTERNAL_DVO1 [ 6.036272] [drm] Connector 1: [ 6.036274] [drm] DVI-I-2 [ 6.036276] [drm] HPD1 [ 6.036278] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 6.036280] [drm] Encoders: [ 6.036281] [drm] CRT2: INTERNAL_DAC2 [ 6.036283] [drm] DFP1: INTERNAL_TMDS1 [ 6.036285] [drm] Connector 2: [ 6.036287] [drm] SVIDEO-1 [ 6.036288] [drm] Encoders: [ 6.036290] [drm] TV1: INTERNAL_DAC2 [ 6.115216] [drm] fb mappable at 0xC00C0000 [ 6.115220] [drm] vram apper at 0xC0000000 [ 6.115222] [drm] size 7680000 [ 6.115224] [drm] fb depth is 24 [ 6.115225] [drm] pitch is 6400 [ 6.115334] fbcon: radeondrmfb (fb0) is primary device [ 6.165930] [drm] crtc 1 is connected to a TV [ 6.276745] fb0: radeondrmfb frame buffer device [ 6.276748] drm: registered panic notifier [ 6.276755] [drm] Initialized radeon 2.24.0 20080528 for 0000:01:00.0 on minor 0 [ 51.816328] [drm] crtc 1 is connected to a TV -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 56081] New: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=56081 Priority: medium Bug ID: 56081 Assignee: dri-devel(a)lists.freedesktop.org Summary: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS Severity: major Classification: Unclassified OS: Linux (All) Reporter: autonymous(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 68683 --> https://bugs.freedesktop.org/attachment.cgi?id=68683&action=edit Xorg.0.log Using AMD A4-3420M APU, have NOT been able to use the R600 driver on either Suse (12.x, factory), Arch Linux (latest built, or git xorg/mesa/dri build), or Ubuntu (12.04, 12.10b2). ALL various combinations of xorg 1.12/1.13, xorg-video-ati, mesa, and kernel 3.5-3.6 give the same black screen after startup, transition to Xorg corrupts all VT's. KMS for Single user or non-X sessions works fine. Grub boot with "radeon.audio=0" does alleviate some corruption on VT7 (but not enough to be usable). Changing accel options or even disabling accel has no effect. Appears there is something specific to the A4-3420M(6410D, chipID 0x9644, identified by system as a Sumo2) that is affected by this. -- You are receiving this mail because: You are the assignee for the bug.

1 16

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013