Bug 94153 - Unresponsive system on boot with radeon + HD 3870
Summary: Unresponsive system on boot with radeon + HD 3870
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-15 09:59 UTC by Andriy Dmytruk
Modified: 2016-02-24 17:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg.log saved via the serial port (46.64 KB, text/plain)
2016-02-15 09:59 UTC, Andriy Dmytruk
no flags Details
dmesg.log with nomodeset (56.73 KB, text/plain)
2016-02-15 10:05 UTC, Andriy Dmytruk
no flags Details
Xorg.log with nomodeset (108.27 KB, text/plain)
2016-02-15 10:07 UTC, Andriy Dmytruk
no flags Details
Kernel 4.4 dmesg.log saved via the serial port (47.49 KB, text/plain)
2016-02-23 06:02 UTC, Andriy Dmytruk
no flags Details
Kernel 4.4 dmesg.log with nomodeset (49.18 KB, text/plain)
2016-02-23 06:03 UTC, Andriy Dmytruk
no flags Details
Kernel 4.4 Xorg.log with nomodeset, video HD3870 (111.01 KB, text/plain)
2016-02-23 06:22 UTC, Andriy Dmytruk
no flags Details
Kernel 4.4 Xorg.log, video ATI X1600 (82.99 KB, text/plain)
2016-02-23 06:24 UTC, Andriy Dmytruk
no flags Details
lspci -nnn (2.52 KB, text/plain)
2016-02-23 06:27 UTC, Andriy Dmytruk
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andriy Dmytruk 2016-02-15 09:59:54 UTC
Created attachment 121755 [details]
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]
Comment 1 Andriy Dmytruk 2016-02-15 10:05:52 UTC
Created attachment 121756 [details]
dmesg.log with nomodeset
Comment 2 Andriy Dmytruk 2016-02-15 10:07:04 UTC
Created attachment 121757 [details]
Xorg.log with nomodeset
Comment 4 Andriy Dmytruk 2016-02-17 05:53:09 UTC
(In reply to Michel Dänzer from comment #3)
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=96ea47c0ec8c012509116bee8c57414281428fc4
> 
> might help.

Sorry for my English. I am newbie. I do not know if I can patch the kernel.
Can you tell me ? This patch is included in the kernel 4.3?
Comment 5 Chí-Thanh Christopher Nguyễn 2016-02-20 17:52:01 UTC
The patch is in kernel 4.4 but not in kernel 4.3.
Comment 6 Andriy Dmytruk 2016-02-23 05:58:22 UTC
I tried kernel 4.4 from Sid. All the same. Patch the kernel did not help.
Comment 7 Andriy Dmytruk 2016-02-23 06:02:28 UTC
Created attachment 121906 [details]
Kernel 4.4 dmesg.log saved via the serial port
Comment 8 Andriy Dmytruk 2016-02-23 06:03:34 UTC
Created attachment 121907 [details]
Kernel 4.4 dmesg.log with nomodeset
Comment 9 Andriy Dmytruk 2016-02-23 06:22:16 UTC
Created attachment 121909 [details]
Kernel 4.4 Xorg.log with nomodeset, video HD3870
Comment 10 Andriy Dmytruk 2016-02-23 06:24:40 UTC
Created attachment 121910 [details]
Kernel 4.4 Xorg.log, video ATI X1600
Comment 11 Andriy Dmytruk 2016-02-23 06:27:05 UTC
Created attachment 121911 [details]
lspci -nnn
Comment 12 Andriy Dmytruk 2016-02-24 17:42:50 UTC
All the same with kernel 4.5.

~$ uname -a
Linux dmytruk1 4.5.0-rc4-amd64 #1 SMP Debian 4.5~rc4-1~exp1 (2016-02-18) x86_64 GNU/Linux


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.