dri-devel May 2015

dri-devel@lists.freedesktop.org

191 participants
1132 discussions

[Bug 77269] New: libdrm (git) 2.4.52 make check fail
by bugzilla-daemon＠freedesktop.org 12 Dec '16

12 Dec '16

https://bugs.freedesktop.org/show_bug.cgi?id=77269 Priority: medium Bug ID: 77269 Assignee: dri-devel(a)lists.freedesktop.org Summary: libdrm (git) 2.4.52 make check fail Severity: normal Classification: Unclassified OS: All Reporter: monts.here2(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: libdrm Product: DRI ====config======== Core i3 haswell uname -a Linux em1 3.15.0-0.rc0.git9.2.fc21.x86_64 #1 SMP Mon Apr 7 13:25:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux gcc -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-isl=/builddir/build/BUILD/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/cloog-install --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) =======config======== ./autogen.sh --enable-udev --disable-radeon --disable-nouveau make -j8 make -j check <===== fails ../build-aux/test-driver: line 95: 23128 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: updatedraw PASS: gem_flink ../build-aux/test-driver: line 95: 23130 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: setversion PASS: gem_readwrite PASS: gem_mmap make[5]: Entering directory `/opt/src/drm/tests' Making all in modeprint make[6]: Entering directory `/opt/src/drm/tests/modeprint' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/opt/src/drm/tests/modeprint' Making all in kmstest make[6]: Entering directory `/opt/src/drm/tests/kmstest' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/opt/src/drm/tests/kmstest' Making all in modetest make[6]: Entering directory `/opt/src/drm/tests/modetest' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/opt/src/drm/tests/modetest' Making all in vbltest make[6]: Entering directory `/opt/src/drm/tests/vbltest' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/opt/src/drm/tests/vbltest' make[6]: Entering directory `/opt/src/drm/tests' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/opt/src/drm/tests' make[5]: Leaving directory `/opt/src/drm/tests' ============================================================================ Testsuite summary for libdrm 2.4.52 ============================================================================ # TOTAL: 11 # PASS: 9 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=DRI ============================================================================ make[4]: *** [test-suite.log] Error 1 make[4]: Leaving directory `/opt/src/drm/tests' make[3]: *** [check-TESTS] Error 2 make[3]: Leaving directory `/opt/src/drm/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/opt/src/drm/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/opt/src/drm/tests' make: *** [check-recursive] Error 1 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89534] GPU lockup with wine
by bugzilla-daemon＠freedesktop.org 08 Dec '16

08 Dec '16

https://bugs.freedesktop.org/show_bug.cgi?id=89534 Bug ID: 89534 Summary: GPU lockup with wine 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: john.ettedgui(a)gmail.com Created attachment 114220 --> https://bugs.freedesktop.org/attachment.cgi?id=114220&action=edit dmesg part for the lockup Hi there, I have found some games that cause some GPU lockups, some more violent than others. All of them unfortunately are running through wine. I am not exactly sure if they are all related or not, but I'll give a small summary of these, they are all using the Unreal Engine 3. I started with Injustice Gods Among US: I didn't see any crash with pure wine, only with nine. They seemed more likely with higher graphical settings, though there was one stage that I had to play without nine as it always crashed. With the same configuration using Nine I played Batman Arkham Asylum with no crash (older game same engine, maybe less demanding?). Then Batman Arkham City has been similar to Injustice, but it also has crashed with standard wine (meaning without nine), just less frequently. And finally, the one that really brings me here now, Batman Arkham Origins, I can't get past the main screen, with nine or pure wine it crashes at the same place. I've tried with both linux 3.19 and linux 4.0rc3, with the radeon and the generic modesetting ddx and it's all the same. I am on latest mesa-git and llvm-svn. The end results is the screen is dead, but I can still remote ssh in the machine most times, then there's not much I can do but restart the machine... I'll attach the dmesg I grabbed from my last try with Batman Arkham Origins. I am not exactly sure where the issue really is, so for now I've put it in DRI. My specs are: Radeon 280x Xorg 1.17 Linux 3.19/4.0rc3 x64 mesa-git llvm-svn As always I'm open to trying patches, bisect etc... though since I never played these games before, I cannot say if it worked or not better in previous releases. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 35

[Bug 90202] Firefox nightly hangs with accelerated layers and latest r600 driver
by bugzilla-daemon＠freedesktop.org 25 Nov '16

25 Nov '16

https://bugs.freedesktop.org/show_bug.cgi?id=90202 Bug ID: 90202 Summary: Firefox nightly hangs with accelerated layers and latest r600 driver Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: ernstp(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org (This is not #81680 btw, this is separate...) If I enable layers.acceleration.force-enabled in Firefox nightly, Firefox always hangs after a little while of browsing. This is a regression somewhere, this worked during a couple of months... -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 67435] New: HDMI audio silent on Radeon Mobility HD4650
by bugzilla-daemon＠freedesktop.org 07 Nov '16

07 Nov '16

https://bugs.freedesktop.org/show_bug.cgi?id=67435 Priority: medium Bug ID: 67435 Assignee: dri-devel(a)lists.freedesktop.org Summary: HDMI audio silent on Radeon Mobility HD4650 Severity: normal Classification: Unclassified OS: All Reporter: kris(a)syntosis.net Hardware: All Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI I cannot get any audio through the HDMI port, internal speakers work as they should. Kernel option is properly set, and everything is unmuted. Audio worked fine in the 3.9 kernels, and stopped working somewhere in 3.10 Currently using 3.11-rc2 and still have the same issue. relevant info from dmesg: ------- Kernel command line: BOOT_IMAGE=/vmlinuz-3.11.0-rc2 radeon.dpm=1 radeon.audio=1 video=1360x768 rootfstype=btrfs root=/dev/sda3 [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV730 0x1002:0x9480 0x104D:0x9035). [drm] register mmio base: 0xD0020000 [drm] register mmio size: 65536 radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) radeon 0000:01:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF [drm] Detected VRAM RAM=512M, BAR=256M [drm] RAM width 128bits DDR [drm] radeon: 512M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV730 Microcode [drm] PCIE GART of 512M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff88013856dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff88013856dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 and cpu addr 0xffffc90010d9c598 [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [drm] Driver supports precise vblank timestamp query. radeon 0000:01:00.0: irq 50 for MSI/MSI-X radeon 0000:01:00.0: radeon: using MSI. [drm] radeon: irq initialized. [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] ib test on ring 5 succeeded [drm:radeon_atombios_get_lvds_info] *ERROR* Bad LCD record 217 [drm] radeon atom DIG backlight initialized [drm] Radeon Display Connectors [drm] Connector 0: [drm] LVDS-1 [drm] Encoders: [drm] LCD1: INTERNAL_UNIPHY2 [drm] Connector 1: [drm] VGA-1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] Connector 2: [drm] HDMI-A-1 [drm] HPD1 [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] radeon: dpm initialized [drm] fb mappable at 0xC035F000 [drm] vram apper at 0xC0000000 [drm] size 4325376 [drm] fb depth is 24 [drm] pitch is 5632 fbcon: radeondrmfb (fb0) is primary device radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device radeon 0000:01:00.0: registered panic notifier [drm] Initialized radeon 2.34.0 20080528 for 0000:01:00.0 on minor 0 ---- -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 67713] New: Atombios stuck in a loop on Trinity 7500G
by bugzilla-daemon＠freedesktop.org 03 Nov '16

03 Nov '16

https://bugs.freedesktop.org/show_bug.cgi?id=67713 Priority: medium Bug ID: 67713 Assignee: dri-devel(a)lists.freedesktop.org Summary: Atombios stuck in a loop on Trinity 7500G Severity: normal Classification: Unclassified OS: All Reporter: mike(a)fireburn.co.uk Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 83583 --> https://bugs.freedesktop.org/attachment.cgi?id=83583&action=edit Dmesg A trinity system freezes if X is in the forefront Caught this when I was in a VT - I'll attach the dmesg RADEON_VA=0 is coded in /etc/environment as a solution to frequent freeze ups (I'm not sure if this is still required or not) bug 65958 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] Let me know if there's anything else you need -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 90666] Stacktrace / Warning during switch (ctrl+alt+f1) to console on zbook 14 (Radeon/intel)
by bugzilla-daemon＠freedesktop.org 02 Nov '16

02 Nov '16

https://bugs.freedesktop.org/show_bug.cgi?id=90666 Bug ID: 90666 Summary: Stacktrace / Warning during switch (ctrl+alt+f1) to console on zbook 14 (Radeon/intel) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: bla(a)thera.be Switching to console worked, in my attempt for 4.0 it didn't work at all. Including stack traces which might help fix some errors though. This is zbook 14 - dual gpu with intel/vga_switcheroo. Linux feather 4.1.0-rc5-bla+ #4 SMP PREEMPT Tue May 26 19:17:04 CEST 2015 x86_64 GNU/Linux This is plain 4.1.0-rc5 with 2 more commits from main git. No `my' changes. Rest is Debian Jessie: ii xserver-xorg-video-ati 1:7.5.0-1 [ 28.837695] ------------[ cut here ]------------ [ 28.838452] WARNING: CPU: 0 PID: 4639 at drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0x176/0x180() [ 28.839231] No drm_driver.set_busid() implementation provided by 0xffffffff824e77c0. Use drm_dev_set_unique() to set the unique name explicitly. [ 28.839285] Modules linked in: [ 28.840540] nfnetlink_queue nfnetlink_log nfnetlink btrfs xor tpm_infineon raid6_pq intel_rapl iosf_mbi x86_pkg_temp_thermal joydev crc32_pclmul iwlmvm iwlwifi xhci_pci xhci_hcd e1000e intel_smartconnect tpm_tis tpm_rng tpm [ 28.842975] CPU: 0 PID: 4639 Comm: Xorg Not tainted 4.1.0-rc5-bla+ #4 [ 28.844343] Hardware name: Hewlett-Packard HP ZBook 14/198F, BIOS L71 Ver. 01.20 07/28/2014 [ 28.845571] 00000000ffffffff 00000000671b4f82 ffffffff82175639 ffffffff81d55e44 [ 28.846843] ffff880087c47d10 ffffffff810e423c ffff880087c47de0 ffff88043a007000 [ 28.848186] ffff880438b10cc0 fffffffffffffff2 0000000000000007 ffffffff810e42c8 [ 28.849439] Call Trace: [ 28.850708] [<ffffffff81d55e44>] ? dump_stack+0x4a/0x74 [ 28.851873] [<ffffffff810e423c>] ? warn_slowpath_common+0x7c/0xb0 [ 28.853236] [<ffffffff810e42c8>] ? warn_slowpath_fmt+0x58/0x80 [ 28.854588] [<ffffffff81581806>] ? drm_setversion+0x176/0x180 [ 28.855845] [<ffffffff81581256>] ? drm_ioctl+0x316/0x5b0 [ 28.856977] [<ffffffff81581690>] ? drm_noop+0x30/0x30 [ 28.858051] [<ffffffff81221dee>] ? do_filp_open+0x3e/0xb0 [ 28.859291] [<ffffffff81224388>] ? do_vfs_ioctl+0x308/0x510 [ 28.860191] [<ffffffff81175f9c>] ? __audit_syscall_entry+0xbc/0x110 [ 28.861068] [<ffffffff8105c01b>] ? syscall_trace_enter_phase1+0x13b/0x1a0 [ 28.861920] [<ffffffff812245c6>] ? SyS_ioctl+0x36/0x80 [ 28.862775] [<ffffffff81d638d7>] ? system_call_fastpath+0x12/0x6a [ 28.863634] ---[ end trace fdbd327690626ad6 ]--- [ [ 29.315320] ------------[ cut here ]------------ [ 29.315328] WARNING: CPU: 0 PID: 4639 at drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0x176/0x180() [ 29.315334] No drm_driver.set_busid() implementation provided by 0xffffffff824e77c0. Use drm_dev_set_unique() to set the unique name explicitly. [ 29.315336] Modules linked in: [ 29.315337] nfnetlink_queue nfnetlink_log nfnetlink btrfs xor tpm_infineon raid6_pq intel_rapl iosf_mbi x86_pkg_temp_thermal joydev crc32_pclmul iwlmvm iwlwifi xhci_pci xhci_hcd e1000e intel_smartconnect tpm_tis tpm_rng tpm [ 29.315351] CPU: 0 PID: 4639 Comm: Xorg Tainted: G W 4.1.0-rc5-bla+ #4 [ 29.315353] Hardware name: Hewlett-Packard HP ZBook 14/198F, BIOS L71 Ver. 01.20 07/28/2014 [ 29.315354] 00000000ffffffff 00000000671b4f82 ffffffff82175639 ffffffff81d55e44 [ 29.315357] ffff880087c47d10 ffffffff810e423c ffff880087c47de0 ffff88043a007000 [ 29.315360] ffff880436fd8cc0 fffffffffffffff2 0000000000000007 ffffffff810e42c8 [ 29.315362] Call Trace: [ 29.315368] [<ffffffff81d55e44>] ? dump_stack+0x4a/0x74 [ 29.315373] [<ffffffff810e423c>] ? warn_slowpath_common+0x7c/0xb0 [ 29.315376] [<ffffffff810e42c8>] ? warn_slowpath_fmt+0x58/0x80 [ 29.315378] [<ffffffff81581806>] ? drm_setversion+0x176/0x180 [ 29.315380] [<ffffffff81581256>] ? drm_ioctl+0x316/0x5b0 [ 29.315382] [<ffffffff81581690>] ? drm_noop+0x30/0x30 [ 29.315386] [<ffffffff81221dee>] ? do_filp_open+0x3e/0xb0 [ 29.315389] [<ffffffff81224388>] ? do_vfs_ioctl+0x308/0x510 [ 29.315393] [<ffffffff81175f9c>] ? __audit_syscall_entry+0xbc/0x110 [ 29.315396] [<ffffffff8105c01b>] ? syscall_trace_enter_phase1+0x13b/0x1a0 [ 29.315398] [<ffffffff8122e163>] ? __fget+0x63/0xa0 [ 29.315400] [<ffffffff812245c6>] ? SyS_ioctl+0x36/0x80 [ 29.315404] [<ffffffff81d638d7>] ? system_call_fastpath+0x12/0x6a [ 29.315406] ---[ end trace fdbd327690626ad7 ]--- [ 29.317397] dmar: DRHD: handling fault status reg 2 [ 29.317400] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7300000000 DMAR:[fault reason 05] PTE Write access is not set [ 29.581646] dmar: DRHD: handling fault status reg 2 [ 29.581651] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7300000000 DMAR:[fault reason 05] PTE Write access is not set [ 29.591198] dmar: DRHD: handling fault status reg 2 [ 29.591205] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr 7300000000 DMAR:[fault reason 05] PTE Write access is not set -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 84156] New: Half of lighting gets broken in older apps
by bugzilla-daemon＠freedesktop.org 30 Oct '16

30 Oct '16

https://bugs.freedesktop.org/show_bug.cgi?id=84156 Priority: medium Bug ID: 84156 Assignee: dri-devel(a)lists.freedesktop.org Summary: Half of lighting gets broken in older apps Severity: normal Classification: Unclassified OS: All Reporter: smoki00790(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa This is from old bug 77785 and about old games where seems like GLSL is not used. In examples i can mention it happens when truck/vehicle turn on lights. Useful apitrace from 18 WoS: Pedal to the Metal game - it is OpenGL game running under wine: https://dl.dropboxusercontent.com/u/74553632/pttm_trace2.7z The same issue i found that can be reproduced is with 3DMark2001 http://www.futuremark.com/benchmarks/legacy (which is mostly for benchmarking DirectX8 features. So it happens too in 'Car Chase' test, but only when wine is used with UseGLSL disabled. http://wiki.winehq.org/UsefulRegistryKeys -- You are receiving this mail because: You are the assignee for the bug.

1 6

[PATCH RFC 0/4] Linking DRM Connectors to Backlight Devices
by David Herrmann 24 Oct '16

24 Oct '16

Hi This series introduces a link between DRM connectors and backlight-class devices. It tries to solve some long standing issues: * User-space currently has a hard-time figuring out which backlight device to use, and which backlight device belongs to which display. So far, most systems only provide backlight-devices for internal displays, so figuring out the connection is easy, but that might change with more capable external connectors. If multiple backlights are available, the easiest solution is to simply write to all of them and hope at least one of them works. This obviously fails if the devices interact badly, so it's not really a solution. * User-space needs root privileges to write to sysfs. There are no char-devs that can be used to control access-management to the backlight API, so /sys is the only interface available. So far, udev policy has been "/sys is read-only for non-root" and it's not going to change. char-devs are *THE* standard way to provide non-root user-space APIs, so use them! Several solutions have been discussed so far, but we never agreed on one. I'm aware of at least the following solutions: * Provide char-devs for backlight devices and a sysfs link from connectors to backlight devices. This way, user-space can managed access to char-devs *and* get proper topology information. However, this might be an n:m relationship (n:1 for displays exposed as multiple connectors, 1:m for boards with multiple backlights? whatever..) and it sounds like a waste of resources to add char-devs just to write brightness values. * Do everything in privileged user-space. One daemon that provides an unprivileged-API and forwards writes to /sys. It reads topology information from udev hwdb. This circumvents the ugly sysfs API and not really solves the problem. It should work, though ugly. * Add a DRM connector property that takes brightness values. This is the nicest solution for user-space, but introduces a whole lot of issues on the kernel side. There already is a backlight-class and we had a hard-time trying to move it into DRM drivers, so no-one ever did the work. This series tries to solve this problem with a much simpler approach: Instead of moving backlights into DRM, we simply link DRM properties to a backlight device. That is, the kernel manages a link between a connector and a backlight device (or n backlight devices) which can be modified by udev in case the kernel got it wrong (we don't want huge board-fixup-tables in the kernel). User-space can now use the simpl DRM API to manage backlights, and the kernel does not need any special driver code to make it work. Patch #1 and #2 are cleanups and can be applied right away. #3 adds in-kernel backlight APIs and #4 implements the connector-backlight link. Comments welcome! David David Herrmann (4): backlight: use static initializers backlight: use spin-lock to protect device list backlight: add kernel-internal backlight API drm: link connectors to backlight devices drivers/gpu/drm/Kconfig | 1 + drivers/gpu/drm/Makefile | 2 +- drivers/gpu/drm/drm_backlight.c | 387 ++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/drm_crtc.c | 45 +++-- drivers/gpu/drm/drm_drv.c | 11 + drivers/gpu/drm/drm_sysfs.c | 53 +++++ drivers/video/backlight/backlight.c | 91 +++++++-- include/drm/drm_backlight.h | 44 ++++ include/drm/drm_crtc.h | 3 + include/linux/backlight.h | 17 ++ 10 files changed, 622 insertions(+), 32 deletions(-) create mode 100644 drivers/gpu/drm/drm_backlight.c create mode 100644 include/drm/drm_backlight.h -- 2.1.0

6 24

[Bug 84771] New: nouveau MMIO read write FAULT HUB_INIT timed out errors
by bugzilla-daemon＠bugzilla.kernel.org 22 Oct '16

22 Oct '16

https://bugzilla.kernel.org/show_bug.cgi?id=84771 Bug ID: 84771 Summary: nouveau MMIO read write FAULT HUB_INIT timed out errors Product: Drivers Version: 2.5 Kernel Version: 3.17-rc4 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: christtchin(a)gmail.com Regression: No Created attachment 150771 --> https://bugzilla.kernel.org/attachment.cgi?id=150771&action=edit dmesg of regular boot + startx Trying to run Arch Linux on a Lenovo Y400 with an nvidia GT750M graphics card. When trying to boot the nouveau drivers consistently spit out multiple errors. Computer continues the boot process. Errors also occur whenever I try to run anything with hardware acceleration, such as Xorg. It is a similar output to the one that occurs during boot: PBUS, PIBUS, and PGRAPH errors. Attached is a dmesg log of a regular boot and startx. Also a log of opening up Xorg: http://pastebin.com/w48Dx4qq And a log of opening up weston: http://pastebin.com/1VPFgapP -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

[Bug 83531] New: radeon 6650m cannot boot without radeon.runpm=0
by bugzilla-daemon＠bugzilla.kernel.org 21 Oct '16

21 Oct '16

https://bugzilla.kernel.org/show_bug.cgi?id=83531 Bug ID: 83531 Summary: radeon 6650m cannot boot without radeon.runpm=0 Product: Drivers Version: 2.5 Kernel Version: 3.13-3.15.10 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: kvbevsauce(a)gmail.com Regression: No my laptop is a lenovo z575 with an amd a6-3420 apu and a 6650m for hybrid graphics. I am running fedora 20 with the latest kernel of 3.15.10 ever since I updated to kernel 3.13 sometime ago when hybrid DPM was enabled my laptop will not boot without the above kernel parameter. i have the plymouth boot screen disabled so it shows text based boot. the moment the boot text "fedora 20 hisenbug" shows up, between 3 and 5 seconds later the cursor will stop blinking and the system will be frozen. sometimes more boot text shows up after sometimes not. any help to get dynamic power management working. -- You are receiving this mail because: You are watching the assignee of 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 May 2015