dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 91969] [radeonsi][bonaire] Stalls with Borderlands 2
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=91969 Bug ID: 91969 Summary: [radeonsi][bonaire] Stalls with Borderlands 2 Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: shawn.starr(a)rogers.com QA Contact: dri-devel(a)lists.freedesktop.org kernel 4.3.0-rc0 (Fedora snapshot) mesa git master / with also experimental radeonsi shader cache (still stalls with it even) LLVM trunk (Sept 10th, 2015 build) I've done some profiling of Borderlands 2 (just the menu intro) and discovered what may be causing the stalls. Apitrace: https://drive.google.com/open?id=0Bze7CJKD12nORWQ4RTdIbk4zT1k Results from profile show the following calls with spikes: 25208614 [glDrawRangeElements] 25208651 [glLinkProgram] 29526799 [glDrawRangeElements] 29526657 [glDrawRangeElements] -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 84232] New: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=84232 Priority: medium Bug ID: 84232 Assignee: dri-devel(a)lists.freedesktop.org Summary: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend Severity: normal Classification: Unclassified OS: All Reporter: vitalif(a)yourcmc.ru Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 106717 --> https://bugs.freedesktop.org/attachment.cgi?id=106717&action=edit Blender output with R600_DEBUG=compute,fs,vs,gs,ps,cs I'm trying to run Blender using Mesa OpenCL implementation on a radeonsi card. First the kernel didn't want to compile, but that was caused by a bug in it (they were using . instead of -> in 1 place), and after fixing this bug I've got the kernel to compile... ...But after that, LLVM started to crash during translation of IR into shader code with R600 backend. I've done some investigation and figured out that the crash is caused by a PHINode containing itself. SIAnnotateControlFlow::handleLoopCondition() can't handle such situation - it recurses into itself, calls Phi->eraseFromParent() inside the inner execution, returns into outer one, gets zeroed out object and crashes when trying to do something with its members... for example when trying to erase it again. I've tried to understand the semantics of such PHINodes from reading the code and got a suspicion that the rest of LLVM code just ignores PHINodes equal to their parent, so I've tried to fix the bug by making handleLoopCondition() skip IncomingValues equal to the Phi itself, but the bug didn't go away! Surprisingly, PHINode may not just contain itself directly, but it also may contain itself inside another PHINode, i.e. Phi->getIncomingValue(0)->getIncomingValue(0) == Phi, which results in the same problem with SIAnnotateControlFlow... I'll attach Blender output with R600_DEBUG = trace everything and a stack trace of the crash. The bug reproduced with llvm 3.5 and snapshot of 3.6; blender is 2.71; Mesa is from OIBAF's repository. sudo -E CYCLES_OPENCL_TEST=1 R600_DEBUG=compute,fs,vs,gs,ps,cs blender cup\ of\ coffee\ 5.blend &> kernel-llvm.log -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 89659] GPU Hangs with dota2
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89659 Bug ID: 89659 Summary: GPU Hangs with dota2 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: kontakt(a)ib-guder.de Created attachment 114442 --> https://bugs.freedesktop.org/attachment.cgi?id=114442&action=edit dmesg after a crash Hello, I get reproducible GPU hangs often within one minute spectating a game in dota2. Other OpenGL applications runs without hangs. The screen stays black, the keyboard doesn't work after a crash. Networking via ssh works. Archlinux 64bit Mesa: 10.5.1 Linux: 3.18.6 and 3.14.53 Thank you and best wishes Tom Guder -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89059] Dota crashes constantly before 10min mark
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89059 Bug ID: 89059 Summary: Dota crashes constantly before 10min mark Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: jarkko_korpi(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org I got oibaf ppa. They started to use LLVM 3.6 compiler around that time I started to have unstable dota. I cant finnish any dota 2 games. The computer hangs before 10min mark while in dota. But I have played around 2hour episode of game of thrones from tell tale. So this sounds only dota 2 issue for me. I could see console a message something like this: "Still active bo inside vm" The computer freezes, most of the times I could only force boot. Gpu r9 290 3.19.0-031900rc7 OpenGL renderer string: Gallium 0.4 on AMD HAWAII OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-08a06b6 2015-02-10 trusty-oibaf-ppa) -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 90284] radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed.
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=90284 Bug ID: 90284 Summary: radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed. Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: niklas(a)trippler.no Created attachment 115515 --> https://bugs.freedesktop.org/attachment.cgi?id=115515&action=edit journalctl -r -x --boot=-4 Graphics card: AMD R9 290 Kernel: Linux archfractal 4.0.1-1-ARCH #1 SMP PREEMPT Monitors connected: 2 DE: Xfce Relevant packages: local/xf86-video-ati 1:7.5.0-2 (xorg-drivers xorg) local/lib32-mesa 10.5.4-1 local/lib32-mesa-libgl 10.5.4-1 local/lib32-mesa-vdpau 10.5.4-1 local/linux 4.0.1-1 (base) local/xorg-server 1.17.1-5 (xorg) This bug, which is triggered by dota2 (Valve game), locks up both displays for a few seconds before they blink black and freeze in the last frame displayed, requireing a system reboot. The bug seems to happen with others (same symptoms / log messages) using other applications (chrome html5 video was mentioned), but dota2 seems like one of the few recreatable ways to trigger the bug. Steps to recreate: Have steam and dota 2 installed (might have to remove steams own bundled libstdc++ libraries as they conflict with mesa). Launch dota 2 with any video settings Start a new lobby with "cheats enabled" and "all pick" game mode (these don't matter, but make it faster to recreate) Pick the hero "Chaos Knight" and enter the game Type in chat "-lvlup 24" to gain max level and skill up everything Click R to use ulti (which spawns copies of himself) Hold-drag mouse over all the illusions and the hero. When the mouse button is released the above bug triggers, crashing the displaydriver and taking the computer down with it. In the log attached (journal_log) the bug is triggered at 17:43:50, the first line there is: "kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x000cc801" I noticed a few lines later the following lines appeared: May 02 17:44:01 archfractal kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed May 02 17:44:01 archfractal kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed I guessed the bug had something to do with dpm, and disabled it (kernel parameter radeon.dpm=0). When I had done this the bug could still be recreated, but the log showed completely different error messages. This log is also attached as "journal_log_radeon_dpm_is_0" I had to gzip the first log to fit within the 3M file size limit -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 103881] New: HP Compaq dc5750 fails to resume from suspend
by bugzilla-daemon＠bugzilla.kernel.org 02 Apr '18

02 Apr '18

https://bugzilla.kernel.org/show_bug.cgi?id=103881 Bug ID: 103881 Summary: HP Compaq dc5750 fails to resume from suspend Product: Drivers Version: 2.5 Kernel Version: 4.1.6.i386 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: jefferym(a)gmail.com Regression: No Created attachment 186431 --> https://bugzilla.kernel.org/attachment.cgi?id=186431&action=edit Patch adding the dc5750 to the list of radeon rs4xxx quirks The HP Compaq dc5750 is unable to resume from the suspend state. With the system suspended and I press the power button on the front of the machine I expect it to wake up. When the button is pressed the HDD and CD drive lights activate briefly and the fan powers on. The video output does not appear to resume and stays black. I have to hard power the system to bring it back. Attempting to suspend/resume has this issue every time I have tried it. I observed this behavior on kernels 4.1.6 and 4.0.5. Setting devices in /sys/power/pm_debug resulted in the system failing to resume. The freezer method in /sys/power/pm_debug did not have an issue resuming. I enabled /sys/power/pm_trace and after the hard boot I was able to find a reasonable hash matches line: ' pci 0000:01:05.0: hash matches'. Additionally /sys/power/pm_trace_dev_match was able to resolve this to `radeon`. I was able to boot using a serial console and prevented the radeon driver from loading. In this state it was able to suspend and resume properly. From this state I let the radeon driver load again and the system would fail to resume from suspend. I was able to add this system to the list of RS480 quirks. The system was able to suspend and resume normally with the change. It worked with the Xserver running as well. It appears to be running normally. I have attached the patch I tested against the 4.0.5 and 4.1.6 kernels. Is there anything else I should test? -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[Bug 79895] New: Google Hangout crashes radeon
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=79895 Priority: medium Bug ID: 79895 Assignee: dri-devel(a)lists.freedesktop.org Summary: Google Hangout crashes radeon Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Kernel 3.15.0-rc8 + PTE patches [380782.919272] Watchdog[21745]: segfault at 0 ip 00007f405eb822b8 sp 00007f404b8b9850 error 6 in chrome[7f405afc6000+5807000] [380783.427655] radeon 0000:01:00.0: ring 0 stalled for more than 11720msec [380783.427659] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000006e62e5 last fence id 0x00000000006e62e4 on ring 0) [380783.427662] radeon 0000:01:00.0: failed to get a new IB (-35) [380783.852997] radeon 0000:01:00.0: Saved 240 dwords of commands on ring 0. [380783.853042] radeon 0000:01:00.0: GPU softreset: 0x0000006C [380783.853043] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 [380783.853044] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380783.853045] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380783.853046] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380783.853080] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380783.853082] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380783.853083] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [380783.853084] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 [380783.853085] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 [380783.853086] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483106 [380783.853087] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [380783.853089] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [380783.853090] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [380784.261939] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF [380784.261993] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140 [380784.263140] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 [380784.263141] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380784.263142] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380784.263143] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380784.263177] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380784.263178] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380784.263180] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [380784.263181] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [380784.263182] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [380784.263183] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [380784.263184] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [380784.263261] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [380784.301675] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [380784.301678] [drm] PCIE gen 3 link speeds already enabled [380784.303658] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [380784.303740] radeon 0000:01:00.0: WB enabled [380784.303742] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880417946c00 [380784.303743] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880417946c04 [380784.303744] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880417946c08 [380784.303745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880417946c0c [380784.303746] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880417946c10 [380784.304140] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90006135a18 [380784.625264] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [380784.625268] [drm:si_resume] *ERROR* si startup failed on resume [380784.625304] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed [380784.625374] switching from power state: [380784.625376] ui class: none [380784.625377] internal class: boot [380784.625378] caps: [380784.625379] uvd vclk: 0 dclk: 0 [380784.625380] power level 0 sclk: 50000 mclk: 15000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625381] status: c b [380784.625382] switching to power state: [380784.625383] ui class: performance [380784.625384] internal class: none [380784.625385] caps: [380784.625386] uvd vclk: 0 dclk: 0 [380784.625387] power level 0 sclk: 30000 mclk: 15000 vddc: 850 vddci: 875 pcie gen: 3 [380784.625388] power level 1 sclk: 50100 mclk: 125000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625390] power level 2 sclk: 81000 mclk: 125000 vddc: 1090 vddci: 875 pcie gen: 3 [380784.625390] status: r -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 69670] New: KWin crashes when switching to OpenGL 3.1 + Raster
by bugzilla-daemon＠freedesktop.org 31 Mar '18

31 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=69670 Priority: medium Bug ID: 69670 Assignee: dri-devel(a)lists.freedesktop.org Summary: KWin crashes when switching to OpenGL 3.1 + Raster Severity: normal Classification: Unclassified OS: Linux (All) Reporter: omegatype(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.2 Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 86306 --> https://bugs.freedesktop.org/attachment.cgi?id=86306&action=edit kwin stderr KWin crashes with the following message after switching from OpenGL 2.0 + Raster to OpenGL 3.1 + Raster: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. kwin: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Some information about the system (Arch Linux x86_64): $ uname -srvm Linux 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 19:30:21 CEST 2013 x86_64 $ sudo lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] $ yaourt -Qs mesa | egrep '^[^ ]' extra/ati-dri 9.2.0-2 extra/glu 9.0.0-2 multilib/lib32-ati-dri 9.2.0-1 multilib/lib32-glu 9.0.0-2 multilib/lib32-libtxc_dxtn 1.0.1-5 multilib/lib32-mesa 9.2.0-1 multilib/lib32-mesa-libgl 9.2.0-1 extra/mesa 9.2.0-2 extra/mesa-demos 8.1.0-1 extra/mesa-libgl 9.2.0-2 $ yaourt -Qs xf86-video-ati extra/xf86-video-ati 1:7.2.0-1 (xorg-drivers xorg) # cat /etc/X11/xorg.conf.d/05-glamor.conf Section "Module" Load "dri2" Load "glamoregl" EndSection # cat /etc/X11/xorg.conf.d/50-device.conf Section "Device" Identifier "Default Device" Driver "radeon" Option "SwapbuffersWait" "off" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "EnablePageFlip" "on" Option "AccelDFS" "on" Option "XV_VSYNC" "on" Option "AccelMethod" "glamor" #Option "AccelMethod" "EXA" EndSection -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 59681] New: Sony VAIO VPCZ23A4R: radeon doesn't like undocking
by bugzilla-daemon＠bugzilla.kernel.org 25 Mar '18

25 Mar '18

https://bugzilla.kernel.org/show_bug.cgi?id=59681 Summary: Sony VAIO VPCZ23A4R: radeon doesn't like undocking Product: Drivers Version: 2.5 Kernel Version: 3.10-rc5 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: patrakov(a)gmail.com Regression: No Created an attachment (id=104661) --> (https://bugzilla.kernel.org/attachment.cgi?id=104661) The end of the dmesg I have a Sony VAIO VPCZ23A4R laptop. It has a dock station with several devices in it: # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06) 08:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 0a:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 14:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 15:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 15:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 16:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] 16:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series] 17:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:00.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:01.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:02.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:03.0 PCI bridge: Intel Corporation Device 151b (rev 01) 18:04.0 PCI bridge: Intel Corporation Device 151b (rev 01) 19:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06) 1a:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller (rev b2) 1b:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) aep-vaio ~ # lspci -n 00:00.0 0600: 8086:0104 (rev 09) 00:02.0 0300: 8086:0126 (rev 09) 00:16.0 0780: 8086:1c3a (rev 04) 00:1a.0 0c03: 8086:1c2d (rev 04) 00:1b.0 0403: 8086:1c20 (rev 04) 00:1c.0 0604: 8086:1c10 (rev b4) 00:1c.1 0604: 8086:1c12 (rev b4) 00:1c.2 0604: 8086:1c14 (rev b4) 00:1c.3 0604: 8086:1c16 (rev b4) 00:1c.6 0604: 8086:1c1c (rev b4) 00:1d.0 0c03: 8086:1c26 (rev 04) 00:1f.0 0601: 8086:1c4b (rev 04) 00:1f.2 0104: 8086:282a (rev 04) 00:1f.3 0c05: 8086:1c22 (rev 04) 02:00.0 0280: 8086:0091 (rev 34) 03:00.0 ff00: 10ec:5209 (rev 01) 04:00.0 0c03: 1033:0194 (rev 04) 05:00.0 0200: 10ec:8168 (rev 06) 08:00.0 0604: 8086:151b (rev 01) 0a:00.0 0604: 8086:151b (rev 01) 0a:03.0 0604: 8086:151b (rev 01) 0a:04.0 0604: 8086:151b (rev 01) 14:00.0 0604: 8086:151b (rev 01) 15:03.0 0604: 8086:151b (rev 01) 15:04.0 0604: 8086:151b (rev 01) 16:00.0 0300: 1002:6740 16:00.1 0403: 1002:aa90 17:00.0 0604: 8086:151b (rev 01) 18:00.0 0604: 8086:151b (rev 01) 18:01.0 0604: 8086:151b (rev 01) 18:02.0 0604: 8086:151b (rev 01) 18:03.0 0604: 8086:151b (rev 01) 18:04.0 0604: 8086:151b (rev 01) 19:00.0 0200: 10ec:8168 (rev 06) 1a:00.0 0101: 11ab:6121 (rev b2) 1b:00.0 0c03: 1033:0194 (rev 04) Devices up to and including 05:00.0 are in the laptop itself, and everything below is in the dock station. I have tested the laptop with linux-3.10-rc5 with this patch series applied: https://lkml.org/lkml/2013/6/13/349 The testcase is: boot with the dock station attached, let Xorg start (it will use both Intell and Radeon cards), switch to a virtual console, press the Undock button. Yes I know that GPU hotplug is not yet supported in Xorg, but attempting it should not lead to messages like "kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1591!" The part of the dmesg after the undocking attempt, captured over netconsole, is attached to this bug. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 4

[Bug 81689] New: Black screen in info-beamer
by bugzilla-daemon＠freedesktop.org 07 Mar '18

07 Mar '18

https://bugs.freedesktop.org/show_bug.cgi?id=81689 Priority: medium Bug ID: 81689 Assignee: dri-devel(a)lists.freedesktop.org Summary: Black screen in info-beamer Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sa(a)whiz.se Hardware: x86 (IA32) Status: NEW Version: 10.2 Component: Drivers/Gallium/r600 Product: Mesa The multimedia presenter info-beamer ( http://info-beamer.org/ ) just renders a black screen with r600g. It's working fine with software rendering and on Intel hardware. Not a regression, or at least present in Mesa 9.2. I've made an apitrace of one of the beamer demos: https://my.owndrive.com/public.php?service=files&t=cef11b335be2741058363783… The trace renders correctly but gives a lot of errors, so this might be a bug in info-beamer: 0 87813 glGetUniformLocation(program = 0, name = "Color") = -1 87813: warning: glGetError(glGetUniformLocation) = GL_INVALID_VALUE 87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION in glReadBuffer(buffer=0x405) 87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION in glDrawBuffer(buffer=0x405) 0 87872 glPopAttrib() 87872: warning: glGetError(glPopAttrib) = GL_INVALID_OPERATION 87882: glDebugOutputCallback: High severity API error 1, GL_INVALID_VALUE in glGetUniformLocation System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 7.4.0 -- xserver: 1.16.0 -- mesa: 10.2.4 -- drm: 2.4.54 -- kernel: 3.13 -- You are receiving this mail because: You are the assignee for the bug.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016