dri-devel December 2016

dri-devel@lists.freedesktop.org

237 participants
1390 discussions

[Bug 97157] MST displays fail to wake
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97157 Bug ID: 97157 Summary: MST displays fail to wake 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: dan.doel(a)gmail.com Created attachment 125450 --> https://bugs.freedesktop.org/attachment.cgi?id=125450&action=edit dmesg output Since moving to kernel 4.6, I've been having regular problems with my MST monitors failing to wake after being put to sleep. This only seems to occur after the machine has been on for a sufficient amount of time, but I usually experience it within a day of booting, and typically after the displays have been powered off for an extended period of time. There are two MST monitors, but typically only one fails to wake. Also, it is more often that the secondary display is the one that fails. However, I have had the primary display fail to come back (while the secondary one succeeds), and I have had both fail to come back as well. Sometimes, only a complete power off is able to make the monitors wake up; a reboot is not always sufficient. The dmesg displays some errors, and I've poked around a bit. It seems likely that this is related to commit f3d58dccdbf9f8c0a229d555d4b295d52e743039, which was first included in 4.6. This commit basically causes dpms to work at all with MST monitors; before it was a no-op that didn't actually put the monitors into power saving. That doesn't help narrow the problem down much, though, since a significant portion of the mst dpms code probably wasn't being exercised before that. Also, it seems notable that the error message (which seems more like a debug message) in the STANDBY/SUSPEND/OFF case keeps reporting higher numbers, as though it keeps going through the ON case, which increments the variable, but not making it through the portion of the OFF case that decrements the variable. I'll attach dmesg journal output that might be relevant. I believe the error/debug messages timestamped 'Jul 31 11:03:49' correspond to the first time one of the displays failed to wake up. I tried various ways of toggling the dpms off and on after that, so those are the subsequent error messages in the log. As far as specs go, I have: Radeon HD7870 (Pitcairn) Kernel 4.6.4 (4.6.3 also affected) 2 UP2414Q mst displays xorg-server 1.18.4 Modesetting driver Let me know if there's any more information I can try to provide. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 94153] Unresponsive system on boot with radeon + HD 3870
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94153 Bug ID: 94153 Summary: Unresponsive system on boot with radeon + HD 3870 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: g47qk(a)ukr.net Created attachment 121755 --> https://bugs.freedesktop.org/attachment.cgi?id=121755&action=edit dmesg.log saved via the serial port I'm using a HD 3870 with Debian 9 Stretch x64 (Testing). When booting to a command line, when drivers are loaded, the screen goes into power saving mode, and the system becomes unresponsive. Booting with `nomodeset' works OK. If I run "#modprobe radeon modeset=1", the screen goes power saving mode, the system stops responding and the caps lock key no longer works (kernel panic?). I've also tested with a Fedora 23 Workstation Live-CD (64-bit), Ubuntu 15.10 Desktop (64-bit) Live-CD, SystemRescueCd-x86-4.7.0 with the same results (unresponsive on driver load). I've tested a ATI X1600 Pro in the same system, and everything works fine. #lspci -nnn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3870] [1002:9501] -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 89971] HDMI out *not* working with radeon (mobile 8550g)
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89971 Bug ID: 89971 Summary: HDMI out *not* working with radeon (mobile 8550g) Product: DRI Version: DRI 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: adrianovidiugabor(a)gmail.com Created attachment 114999 --> https://bugs.freedesktop.org/attachment.cgi?id=114999&action=edit screen's content Hi all. If I'm connecting my laptop's HDMI out to my TV I get a black screen with garbage on top (see attached pic). This is with mirror mode on. If making the second screen primary, the pc blocks and I have to restart it. It won't unblock even if I disconnect the cable. If switching to one of the virtual consoles, everything works correctly as it should, so the problem seems to be related somehow to the display server. The Tv is recognized correctly by xrandr. Specs: Asus laptop, with AMD A8-5550M, Radeon 8550G(Aruba)/8670M(Hainan), OS ArchLinux(x64) Xorg-xerver 1.17, kernel 3.19.3, Mesa-git, xf86-ati-git, llvm-svn. This doesn't seem to be a regression (experienced it with older versions of the kernel and userspace components) and it's reproducible on another machine. HDMI out works on Windows and ChromeOS. Didn't try Catalyst on Linux. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 80531] New: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750]
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=80531 Priority: medium Bug ID: 80531 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750] Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fredrik(a)obra.se Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 101759 --> https://bugs.freedesktop.org/attachment.cgi?id=101759&action=edit dmesg with drm.debug=1 With 3.16-rc2 my tripple screen setup breaks. DisplayPort-0 connected 1920x1200 <- ok HDMI-0 connected 1920x1080 <- (tv) resolution out of range DVI-0 connected 1680x1050 <- ok All screens work during bootup before X starts. ddx driver 7.3.0. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 75992] New: Display freezes & corruption with an r7 260x on 3.14-rc6
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75992 Priority: medium Bug ID: 75992 Assignee: dri-devel(a)lists.freedesktop.org Summary: Display freezes & corruption with an r7 260x on 3.14-rc6 Severity: major Classification: Unclassified OS: Linux (All) Reporter: edt(a)aei.ca Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 95520 --> https://bugs.freedesktop.org/attachment.cgi?id=95520&action=edit log of boot I recently added a R7 260X to my system. While the card works with 3.13 its supposed work much better with 14-rc. This is not the case. My system is unstable without radeon.dpm=0 which was the default in .13. linux 3.14-rc6 (with an up to date arch, stable X and mesa-git (10.2) mesa 10.1 and 10.0 also show very similar problems. When X started I did notice some corruption. There are sets of two rectangles about of a height of 2 or 3 mm, width of 25m or so with a second about a cm below. The often occurs in chomium especially when scrolling. Runing the unigine-sanctuary or unigine-tropics demo/benchmark programs also produce the above problems and eventually stall. -- You are receiving this mail because: You are the assignee for the bug.

1 61

[Bug 99181] RS780 blank screen on boot
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99181 Bug ID: 99181 Summary: RS780 blank screen on boot 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: chithanh(a)gentoo.org Hardware: BIOSTAR A780L When booting with 3.15 or newer kernels, a monitor connected to the DVI port of the BIOSTAR A780L will stay blank. Kernel 3.14 and older work fine. I tried forcing the output to on with video=HDMI-A-1:e but this made no difference. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 99049] Machine freeze when clock are set to defaults
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99049 Bug ID: 99049 Summary: Machine freeze when clock are set to defaults 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: ls(a)maxux.net My laptop contains theses cards: ---- 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] (rev 81) ---- Under Gentoo, I enabled radeon and radeonsi as videos cards, everything looks fine. According to xrandr, I have providers: ---- Provider 0: id: 0x76 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:Intel Provider 1: id: 0x4f cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:01:00.0 ---- I found on the internet that DPM could cause issue, I tried: radeon.runpm=0 radeon.dpm=0 (see below) Using theses settings, I don't have any freeze when I try to use the Radeon Card (using DRI_PRIME=1), but I found that everything was slow. I checked, and I saw: --- cat /sys/class/drm/card1/device/power_method profile cat /sys/class/drm/card1/device/power_profile default cat /sys/kernel/debug/dri/65/radeon_pm_info default engine clock: 1070000 kHz current engine clock: 299990 kHz default memory clock: 900000 kHz current memory clock: 298990 kHz voltage: 1150 mV PCIE lanes: 4 --- The card is running in low profile by default, don't know why. Setting power_profile to high, mid or low doesn't change anything, but if I set power_profile back to default again, the clock is set to full speed. When clock is set to full speed, my system freeze if I try to run any 3D application (glxgears or a game using wine). Here is the dmesg log: --- radeon 0000:01:00.0: ring 0 stalled for more than 10436msec radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000014f4 last fence id 0x00000000000014f6 on ring 0) radeon 0000:01:00.0: Saved 49 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000049 radeon 0000:01:00.0: GRBM_STATUS = 0xE5D04028 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xEE400000 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00018000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80030243 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] probing gen 2 caps for device 8086:9d10 = 1724843/e [drm] PCIE gen 3 link speeds already enabled [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000100000c00 and cpu addr 0xffff88046c66dc00 radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000100000c04 and cpu addr 0xffff88046c66dc04 radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000100000c08 and cpu addr 0xffff88046c66dc08 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000100000c0c and cpu addr 0xffff88046c66dc0c radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000100000c10 and cpu addr 0xffff88046c66dc10 [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [drm:si_resume [radeon]] *ERROR* si startup failed on resume --- I found out with theses steps that, if I don't set dpm=0, I hit exactly the same issue, I guess using DPM the clock is set to high when the card is used and it crash. When the card is stuck on that loop, I need to reset the machine (but network still works). I'm using mesa-13.0.2 with a 4.7.6 kernel, I have the same issue using mesa 12.0.1 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 98988] [Regression, bisected] New BONAIRE UVD firmware causes DPM problems and extremely slow performance
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98988 Bug ID: 98988 Summary: [Regression, bisected] New BONAIRE UVD firmware causes DPM problems and extremely slow performance Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: falaca(a)gmail.com Created attachment 128327 --> https://bugs.freedesktop.org/attachment.cgi?id=128327&action=edit Kernel bisect log I have a 2GB Radeon R7 260X (BONAIRE). With kernel 4.7 and above, I was experiencing extremely slow performance. Even desktop animations on Ubuntu 16.04 w/ Unity desktop are extremely choppy, probably about 10fps. dmesg produces several instances of the following error message: [drm:ci_dpm_set_power_state [radeon]] *ERROR* ci_upload_dpm_level_enable_mask failed I did a kernel bisect, and narrowed the problem to the following commit: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/… The bisect log is attached. It seems that the commit adds support for a new firmware file, "bonaire_uvd.bin". If the driver fails in loading the new firmware file, it falls back to the legacy file, "BONAIRE_uvd.bin". To confirm that the issue is caused by the new firmware, I deleted bonaire_uvd.bin, and performance is restored to normal with the latest stable kernel (4.9.0-rc7). For what it's worth, here are the contents of /sys/kernel/debug/dri/64/radeon_pm_info while idling on the Ubuntu desktop with the new firmware: uvd disabled vce disabled power level avg sclk: 115774 mclk: 15000 And the old firmware: uvd disabled vce disabled power level avg sclk: 30248 mclk: 165000 -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 98987] [RS690] BUG: soft lockup when radeon modesetting
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98987 Bug ID: 98987 Summary: [RS690] BUG: soft lockup when radeon modesetting Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: high Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: vaclav.ovsik(a)gmail.com Created attachment 128323 --> https://bugs.freedesktop.org/attachment.cgi?id=128323&action=edit logged using netconsole - kernel 4.8.7 (Debian kernel) Dear developers, I'm unable to boot into functional system with KMS radeon. When radeon.modeset=0 on kernel command-line system it starts and run OK. Without disabled modeset the kernel 4.7, 4.8, 4.9-rc7 with 90% probability locks or crash. I'm running Debian unstable and tried Debian kernels 4.7, 4.8 from Debian and compile 4.9rc7 vanilla kernel. Attached logs through netconsole. Any idea what I can test? Thanks -- Zito ref: debian bug #845382 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845382 -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 98620] radeon kernel module NULL pointer dereference on Radeon 9550 at shut-down
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=98620 Bug ID: 98620 Summary: radeon kernel module NULL pointer dereference on Radeon 9550 at shut-down Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: arthur.marsh(a)internode.on.net Created attachment 127808 --> https://bugs.freedesktop.org/attachment.cgi?id=127808&action=edit full dmesg when crashing At shut-down: [ 2515.296325] BUG: unable to handle kernel NULL pointer dereference at 000007b4 [ 2515.300025] IP: [<f8593b36>] radeon_connector_unregister+0x6/0x40 [radeon] [ 2515.300025] *pde = 00000000 [ 2515.300025] Oops: 0000 [#1] PREEMPT SMP [ 2515.300025] Modules linked in: eata cpufreq_conservative cpufreq_powersave cp ufreq_userspace binfmt_misc nls_utf8 nls_cp437 vfat fat hwmon_vid tun cuse fuse iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp ppdev powernow_k8 amd64_ edac_mod edac_mce_amd edac_core snd_via82xx snd_ac97_codec pcspkr ac97_bus snd_m pu401_uart radeon snd_pcm snd_timer snd_rawmidi evdev snd_seq_device gameport sn d ttm drm_kms_helper soundcore serio_raw drm k8temp i2c_algo_bit fb_sys_fops i2c _viapro syscopyarea sysfillrect sysimgblt sg parport_pc parport asus_atk0110 acp i_cpufreq button tpm_tis tpm_tis_core tpm ext4 crc16 jbd2 mbcache sr_mod cdrom a ta_generic uas sd_mod usb_storage psmouse via_rhine mii pata_via ehci_pci uhci_h cd ehci_hcd usbcore usb_common libata scsi_mod [last unloaded: eata] [ 2515.300025] CPU: 0 PID: 7439 Comm: reboot Not tainted 4.9.0-rc4 #520 [ 2515.300025] Hardware name: System manufacturer System Product Name/A8V-MX, BI OS 0503 12/06/2005 [ 2515.300025] task: f2cc6080 task.stack: f3934000 [ 2515.300025] EIP: 0060:[<f8593b36>] EFLAGS: 00010286 CPU: 0 [ 2515.300025] EIP is at radeon_connector_unregister+0x6/0x40 [radeon] [ 2515.300025] EAX: f73a1000 EBX: f73a1000 ECX: 00000006 EDX: 00000000 [ 2515.300025] ESI: f5a09c64 EDI: f5a09800 EBP: f3935db4 ESP: f3935dac [ 2515.300025] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 2515.300025] CR0: 80050033 CR2: 000007b4 CR3: 33dbc000 CR4: 000006d0 [ 2515.300025] Stack: [ 2515.300025] f83471d7 f73a1000 f3935dc4 f8347967 f5a09800 f5a09c8c f3935dd8 f 83383b3 [ 2515.300025] f5a09800 f5a09800 f86a0000 f3935dec f8332ff7 f5a09800 f61d3000 f 86a0000 [ 2515.300025] f3935e04 f8333640 f8358dca 00000001 f8358dc8 f61d3068 f3935e0c f 85702ee [ 2515.300025] Call Trace: [ 2515.300025] [<f83471d7>] ? drm_connector_unregister.part.6+0x17/0x30 [drm] [ 2515.300025] [<f8347967>] drm_connector_unregister_all+0x37/0x50 [drm] [ 2515.300025] [<f83383b3>] drm_modeset_unregister_all+0x13/0x50 [drm] [ 2515.300025] [<f8332ff7>] drm_dev_unregister+0x97/0xa0 [drm] [ 2515.300025] [<f8333640>] drm_put_dev+0x30/0x70 [drm] [ 2515.300025] [<f85702ee>] radeon_pci_shutdown+0xe/0x10 [radeon] [ 2515.300025] [<c134da9d>] pci_device_shutdown+0x2d/0x70 [ 2515.300025] [<c140b834>] device_shutdown+0xb4/0x170 [ 2515.300025] [<c108126d>] kernel_restart_prepare+0x2d/0x30 [ 2515.300025] [<c10812fe>] kernel_restart+0xe/0x60 [ 2515.300025] [<c108162f>] SYSC_reboot+0x1bf/0x200 [ 2515.300025] [<c10cd2ea>] ? debug_lockdep_rcu_enabled+0x1a/0x20 [ 2515.300025] [<c10cd2ea>] ? debug_lockdep_rcu_enabled+0x1a/0x20 [ 2515.300025] [<c11f9c50>] ? mnt_get_count+0x40/0x40 [ 2515.300025] [<c11f9cbf>] ? mntput_no_expire+0x6f/0x3a0 [ 2515.300025] [<c11f9cd9>] ? mntput_no_expire+0x89/0x3a0 [ 2515.300025] [<c11f9c50>] ? mnt_get_count+0x40/0x40 [ 2515.300025] [<c11fa00b>] ? mntput+0x1b/0x30 [ 2515.300025] [<c11d7963>] ? __fput+0x153/0x1d0 [ 2515.300025] [<c107ca4f>] ? task_work_run+0x6f/0x80 [ 2515.300025] [<c10b02ac>] ? trace_hardirqs_on_caller+0xec/0x1d0 [ 2515.300025] [<c10ad2eb>] ? trace_hardirqs_off+0xb/0x10 [ 2515.300025] [<c10816da>] SyS_reboot+0x1a/0x20 [ 2515.300025] [<c1001c7a>] do_fast_syscall_32+0x9a/0x220 [ 2515.300025] [<c15ae2ec>] sysenter_past_esp+0x45/0x74 [ 2515.300025] Code: d8 e8 df 36 db ff 89 d8 e8 f8 36 db ff 89 d8 e8 11 58 c2 c8 5b 5d c3 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 8b 90 d4 02 00 00 <80> ba b4 07 00 00 00 75 01 c3 55 89 e5 53 89 c3 8d 82 e8 03 00 [ 2515.300025] EIP: [<f8593b36>] [ 2515.300025] radeon_connector_unregister+0x6/0x40 [radeon] [ 2515.300025] SS:ESP 0068:f3935dac [ 2515.300025] CR2: 00000000000007b4 [ 2516.877047] ---[ end trace 076c5e2ae2d51112 ]--- Full dmesg from boot to crash is attached. # lspci -vv -s 01:00 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV350 [Radeon 9550] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at a0000000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at b000 [size=256] Region 2: Memory at ff4f0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8 Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: radeon Kernel modules: radeonfb, radeon 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] (Secondary) Subsystem: Gigabyte Technology Co., Ltd RV350 [Radeon 9550] (Secondary) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (2000ns min), Cache Line Size: 64 bytes Region 0: Memory at 90000000 (32-bit, prefetchable) [size=256M] Region 1: Memory at ff4e0000 (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- git-bisect revealed: git bisect bad b0c80bd5d2e317f7596fe2badc1a3379fb3211e5 is the first bad commit commit b0c80bd5d2e317f7596fe2badc1a3379fb3211e5 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Tue Oct 11 10:44:24 2016 -0400 drm/radeon: fix up dp aux tear down (v2) Port the amdgpu fixes from Grazvydas to radeon. v2: drop unrelated whitespace change. bug: https://bugs.freedesktop.org/show_bug.cgi?id=98200 Reviewed-and-Tested-by: Michel Dänzer <michel.daenzer(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> :040000 040000 b187ce6d75761c9e2eed71b385c8e0f085dbfd55 aca34c667d6253da66e824b2 a624f308841555b0 M drivers Rebuilding and running the kernel with that commit removed confirmed normal shutdown. -- 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 December 2016