https://bugzilla.kernel.org/show_bug.cgi?id=53391
Summary: nouveau: wrong display output order
Product: Drivers
Version: 2.5
Kernel Version: 3.8-rc6
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: stijn+bugs(a)linux-ipv6.be
…
[View More]Regression: No
My graphics card is a Gainward GTX480
(http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1
mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being
the closest to the PCIe slot, then DVI 2, and finally the mini HDMI.
My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor
to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor
on DVI 1. Grub is displayed on the primary monitor, and the kernel initially
outputs to the primary monitor as well.
However, as soon as the nouveau module is loaded, the primary monitor goes to
standby and the kernel now uses the secondary monitor (on DVI 2) as primary.
When X starts (no Xorg.conf file), it is also displayed on the secondary
monitor.
When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the
primary monitor. X with nvidia.ko also uses DVI 1 as the primary display.
Finally, when booting Windows, the startup screen is also displayed on the
monitor connected to DVI 1.
Here comes the weird part: when I am in X, and run xrandr, it does show 3
connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only
active one. So it seems that in X, the output order is correct, but with
nouveaufb the DVI connectors are swapped.
I will attach the output of dmesg here. If anything else is needed, please let
me know and I'll be happy to add it.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=203439
Bug ID: 203439
Summary: amdgpu: [REG 4.20 -> 5.0] Brightness minimum level is
too high
Product: Drivers
Version: 2.5
Kernel Version: 5.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)…
[View More]kernel-bugs.osdl.org
Reporter: spaz16(a)wp.pl
Regression: No
I have Huawei Matebook D 14 with AMD Ryzen 2500U.
Since kernel 5.0.x the minimum brightness level is too high. It is not possible
to dim the display as much as on previous kernel version. Kernel 4.20 also
allows to disable the backlight on level 0.
Value of "0" in "/sys/class/backlight/amdgpu_bl0/brightness" currently doesn't
disable backlight as in previous version. Value of "1" means the screen is dim,
but not as much as in kernel 4.20. Sometimes the screen is still too bright
even on level 0 in kernel 5.0.
Since commit 206bbafe00dcacccf40e6f09e624329ec124201b I can see the define:
> #define AMDGPU_DM_DEFAULT_MIN_BACKLIGHT 12
Maybe it should be defined to "0" to restore the old behavior? (I haven't
tested yet)
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=85421
Bug ID: 85421
Summary: radeon stalled, GPU lockup, reset and failed on
resume; crashed by firefox.
Product: Drivers
Version: 2.5
Kernel Version: 3.16.3
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: …
[View More]drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: htl10(a)users.sourceforge.net
Regression: No
Created attachment 152191
--> https://bugzilla.kernel.org/attachment.cgi?id=152191&action=edit
/var/log/messages from radeon 0000:00:01.0: ring 0 stalled to reboot.
I was away from the computer when the radeon dri driver crashed; I left a fair
number of firefox windows on/tab, some of them may have videos (from BBC news
web site) and animated gifs from another web site on; but it crashed about 5-10
minutes after I was away and I was aware of it because the laptop blipped.
# lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Mullins [Radeon R3 Graphics]
some excerpt from the attached logs are:
...
[ 8770.250116] radeon 0000:00:01.0: ring 0 stalled for more than 10012msec
[ 8770.250128] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000056034
last fence id 0x0000000000056031 on ring 0)
[ 8770.298635] radeon 0000:00:01.0: Saved 14196 dwords of commands on ring 0.
[ 8770.298663] radeon 0000:00:01.0: GPU softreset: 0x0000000C
...
[ 8770.313299] radeon 0000:00:01.0: GPU reset succeeded, trying to resume
...
[ 8770.339724] [drm] ring test on 0 succeeded in 3 usecs
[ 8770.518568] [drm:cik_ring_test] *ERROR* radeon: ring 1 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[ 8770.752885] [drm:cik_sdma_ring_test] *ERROR* radeon: ring 3 test failed
(0xCAFEDEAD)
[ 8770.752892] [drm:cik_resume] *ERROR* cik startup failed on resume
[ 8780.753181] radeon 0000:00:01.0: ring 0 stalled for more than 10001msec
[ 8780.753193] radeon 0000:00:01.0: GPU lockup (waiting for 0x00000000000560f7
last fence id 0x0000000000056031 on ring 0)
[ 8780.753199] [drm:cik_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 8780.753209] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
[ 8780.753215] radeon 0000:00:01.0: ib ring test failed (-35).
[ 8780.762131] radeon 0000:00:01.0: GPU softreset: 0x0000000C
...
The kernel is a largely fedora 3.16.3-200 one grabbed from the koji srpm but
with the additional patch from
https://bugzilla.kernel.org/show_bug.cgi?id=71051#c8
drv ati 7.4.0 , mesa 10.2.8, glamor from git 347ef4 .
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=107381
Bug ID: 107381
Summary: radeon VCE init error (-110) -- AMD/Intel Mars Hybrid
Graphics
Product: Drivers
Version: 2.5
Kernel Version: 4.3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)…
[View More]kernel-bugs.osdl.org
Reporter: schmod(a)gmail.com
Regression: No
Created attachment 192261
--> https://bugzilla.kernel.org/attachment.cgi?id=192261&action=edit
dmesg output
Since upgrading to Ubuntu 15.10, I have encountered graphics performance
issues, and have occasionally experienced lockups during boot.
I have encountered this issue on kernel 4.2.0 and 4.3.0, and it seems to have
affected users on other distributions as well:
https://bugs.launchpad.net/fedora/+source/linux/+bug/1512848https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803087https://bugzilla.redhat.com/show_bug.cgi?id=1262649
Notably, this issue seems to primarily impact users with The ATI "Mars"
chipset, on machines that have an Intel/AMD hybrid graphics hardware
configuration.
This shows up in dmesg (full log attached, because there's a fair amount of
seemingly-useful context):
[ 4.917369] radeon 0000:01:00.0: VCE init error (-110).
Some other context from my PC:
$ xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x6a cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 5
associated providers: 2 name:Intel
Provider 1: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 0
associated providers: 2 name:radeon
Provider 2: id: 0x41 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 0
associated providers: 2 name:radeon
$ lspci -k (trimmed to omit likely-irrelevant devices)
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller
(rev 09)
Subsystem: Samsung Electronics Co Ltd Device c0e6
Kernel driver in use: ivb_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor
PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
DeviceName: Onboard IGD
Subsystem: Samsung Electronics Co Ltd Device c0e6
Kernel driver in use: i915
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon
HD 8670A/8670M/8750M] (rev ff)
Kernel driver in use: radeon
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=51381
Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for
more than 5secs aborting, when disabled via
vgaswitcheroo
Product: Drivers
Version: 2.5
Kernel Version: Linux version 3.6.9-1-ARCH (tobias@T-POWA-LX) (gcc
version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 4
08:04:10 CET 2012
Platform: All
OS/Version: …
[View More]Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: a(a)anrd.net
Regression: Yes
Created an attachment (id=88591)
--> (https://bugzilla.kernel.org/attachment.cgi?id=88591)
journald log
After updating from 3.6.6 to 3.6.9 my laptop with Intel graphics and ATI HD
5650 will not resume from suspend. I use vgaswitcheroo to disable the ATI card
at boot. On resume the computer almost hangs (I can press power button and wait
5 minutes for a proper shutdown, but no other interaction is possible). It logs
a lot of messages saying:
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing D098 (len 72,
WS 0, PS 0) @ 0xD0C7
Steps to reproduce:
echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch
[suspend and resume]
Actual results:
Almost freeze.
Expected results:
Resume and work as normal.
Log is attached, but if you need anything else just ask.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=203905
Bug ID: 203905
Summary: amdgpu:actual_brightness has unreal/wrong value
Product: Drivers
Version: 2.5
Kernel Version: 5.1.9
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
…
[View More]Reporter: bjo(a)nord-west.org
Regression: No
Radeon R5/R6/R7 Graphics in a Thinkpad A275 has wrong values on
actual_brightness of amdgpu_bl0. While max_brightness is 255 and it can be set
to 255, actual_brightness reports a 5 digit number like 12470. As a result,
tools which want to change the brightness related to actual_brightness fail, as
brightness does not accept any 5 digit number,
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=200695
Bug ID: 200695
Summary: Blank screen on RX 580 with amdgpu.dc=1 enabled (no
displays detected)
Product: Drivers
Version: 2.5
Kernel Version: 4.18.0-rc7
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: …
[View More]drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: claude(a)mathr.co.uk
Regression: No
Created attachment 277633
--> https://bugzilla.kernel.org/attachment.cgi?id=277633&action=edit
dmesg after boot with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6
When amdgpu.dc=1 is initialized at boot, the console goes blank as it thinks
all displays are disconnected. Xorg is not able to enable the display either.
With amdgpu.dc=0 all is fine. Tried with various (mostly Debian) kernels from
4.16 through 4.18~rc4, all have the issue. I built a 4.18~rc7 from kernel.org
to rule out Debian patches being the issue and will provide logs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
[View Less]