From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91961] Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0) Date: Thu, 10 Sep 2015 14:12:27 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0172128913==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E75606E415 for ; Thu, 10 Sep 2015 07:12:27 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0172128913== Content-Type: multipart/alternative; boundary="1441894347.0071cf3c0.22971"; charset="UTF-8" --1441894347.0071cf3c0.22971 Date: Thu, 10 Sep 2015 14:12:27 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=91961 Bug ID: 91961 Summary: Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0) Product: DRI Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: ikalvachev@gmail.com Created attachment 118192 --> https://bugs.freedesktop.org/attachment.cgi?id=118192&action=edit Kernel logs from running both test at the same time and from running the second test only.. Built-in tests are enabled by the module "option radeon test=3". The integer value bits are used as flags what test to run on the module load. Running both test takes about 1-2 minutes to complete. The first one turns off the display and trashes the system in a way that the first key pressed hangs it hard - no flashing LEDs, no Magic SysRq. --- The first test moves data from system ram to video ram and back. It runs for about a minute. During that time the monitor is turning off and on again (DELLs do that if DPMS signaling is not exactly right, its on DVI port). The rest of the system seems to function. Boot loading seams to finish and sometimes I can salvage complete kernel message log. Pressing CapsLock turns on its LED, but second press have no effect. Even pressing Magic SysRq first doesn't provide any control of the system. It hangs hard and only reset helps. The seconds test is about syncing between GPU rings. It seems to finish without error if run after the first one. However if I run it alone with "test=2", I get a bunch of timeouts, "GPU lockup" and other errors. When run alone the test doesn't prevent setting of working graphic mode. My videocard is Radeon HD5670 (Redwood). I have confirmation that the same happens on Tahiti chipsets. -- You are receiving this mail because: You are the assignee for the bug. --1441894347.0071cf3c0.22971 Date: Thu, 10 Sep 2015 14:12:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
Bug ID 91961
Summary Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0)
Product DRI
Version unspecified
Hardware Other
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/Radeon
Assignee dri-devel@lists.freedesktop.org
Reporter ikalvachev@gmail.com

Created attachment 118192 [details]
Kernel logs from running both test at the same time and from running the second
test only..

Built-in tests are enabled by the module "option radeon test=3". The integer
value bits are used as flags what test to run on the module load.

Running both test takes about 1-2 minutes to complete. The first one turns off
the display and trashes the system in a way that the first key pressed hangs it
hard - no flashing LEDs, no Magic SysRq.

---
The first test moves data from system ram to video ram and back.
It runs for about a minute. During that time the monitor is turning off and on
again (DELLs do that if DPMS signaling is not exactly right, its on DVI port).
The rest of the system seems to function. Boot loading seams to finish and
sometimes I can salvage complete kernel message log. Pressing CapsLock turns on
its LED, but second press have no effect. Even pressing Magic SysRq first
doesn't provide any control of the system. It hangs hard and only reset helps.

The seconds test is about syncing between GPU rings.
It seems to finish without error if run after the first one.
However if I run it alone with "test=2", I get a bunch of timeouts, "GPU
lockup" and other errors. When run alone the test doesn't prevent setting of
working graphic mode.

My videocard is Radeon HD5670 (Redwood).
I have confirmation that the same happens on Tahiti chipsets.


You are receiving this mail because:
  • You are the assignee for the bug.
--1441894347.0071cf3c0.22971-- --===============0172128913== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0172128913==--