lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADnq5_NwNLCaN-aoULaZxnjwxP+PAn6b8ngUsfwNAv4v2vxM2g@mail.gmail.com>
Date:	Sun, 4 Jan 2015 12:26:38 -0500
From:	Alex Deucher <alexdeucher@...il.com>
To:	Alex Kuznetsoff <dri-devel@...dex.ru>
Cc:	David Airlie <airlied@...ux.ie>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Radeon R9 290 problem

On Fri, Jan 2, 2015 at 11:23 AM, Alex Kuznetsoff <dri-devel@...dex.ru> wrote:
> I have an AMD Radeon R9 290 video card, and since commit https://github.com/torvalds/linux/commit/96212fe8c27b I cannot boot into the system any more with CONFIG_DRM_RADEON turned on ([m]). These are the symptoms: the screen either reports NO SIGNAL (sometimes all the LEDs, scroll lock, caps lock and num lock start to blink synchronously) - I had a lot of this while bisecting v3.12.0 to v3.13.0, or, in newer kernels, including v3.18, the image just freezes somewhere around "Waiting for uevents to be processed" and nothing more happens on the screen. In both cases I have to use the reboot button.
>
> Here's the output of lspci | grep ATI:
>
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8
>
> Here's my kernel config:
>
> https://bpaste.net/show/8c353c80e37e
>
> It works in 3.12 series up to 3.12.34 (it is the last version I checked) and doesn't work in 3.13 to v3.18 (b2776bf).

That commit is the first commit to enable hawaii support in the driver
so prior to that, the driver was not loaded on your hardware.  X was
probably using vesa or some firmware fbdev interface.  Please file a
bug (https://bugs.freedesktop.org) and attach your xorg log and dmesg
output.

Alex

> _______________________________________________
> dri-devel mailing list
> dri-devel@...ts.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ