All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100
Date: Thu, 30 Mar 2017 10:59:40 +0000	[thread overview]
Message-ID: <bug-100465-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2618 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100465

            Bug ID: 100465
           Summary: Hard lockup with radeonsi driver on FirePro W600,
                    W9000 and W9100
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: julien.isorce@gmail.com

Created attachment 130563
  --> https://bugs.freedesktop.org/attachment.cgi?id=130563&action=edit
dmesg

The machine completely freeze using radeonsi driver with FirePro W600, W9000
and W9100.

* Steps to reproduce:

wget
http://www.phoronix-test-suite.com/benchmark-files/GpuTest_Linux_x64_0.7.0.zip
DISPLAY=:0 ./GpuTest /test=fur /fullscreen

* Acutal result:

System and screen are frozen after a few minutes (sometimes a few seconds,
sometimes 20 min). No mouse/keyboard. Does not respond to ping. No kernel
panic. Requires hard reboot.

After reboot, no error in /var/log/kern.log. Empty dir /var/crash, empty dir
/sys/fs/pstore. Sometimes some nul characters ^@ just before the next "Linux
version".
Using a serial console does not show additional debug messages.

* Expected result:

No system freeze.

* List of things that have been tried but leading to the same result:

- kernel 4.4.X, 4.8.x packaged by ubuntu.
- amd-staging-4.9 from https://cgit.freedesktop.org/~agd5f/linux.
- a few 4.10 kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ .
- radeon.dpm=1 (all values for power_dpm_state /
power_dpm_force_performance_level)
- radeon.dpm=0 (power_mode=profile and all values for power_profile)
- radeon.msi=1 / 0.
- DRI2 / DRI3
- glamor / no accel, TearFree on / off
- single monitor, multi monitor, resolutions 1600x1200, 1920x1080.
- Latest libdrm / mesa. llvm 3.8, 4 and 5.

* List of things that avoids the system freeze:

- radeon.gartsize=512 radeon.vramlimit=1024

* Others:

- apitrace trace then replay does not lead to the freeze.
- No errors with R600_DEBUG=* or MESA_DEBUG.
- strace sometimes shows that the last call is ioctl(RADEON_CS) but not sure
how reliable this is provinding the last print might not be flush.
- Happens with 2 differents brand for the mother board.
- takes a bit longer for the mentioned GpuTest to freeze the machine on W9000
and W9100.

* TODOs:

- Try again kgdb.
- Try amdgpu instead of radeonsi.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4236 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-03-30 10:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 10:59 bugzilla-daemon [this message]
2017-03-30 11:00 ` [Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100 bugzilla-daemon
2017-03-30 12:31 ` bugzilla-daemon
2017-03-31  1:11 ` bugzilla-daemon
2017-03-31  2:21 ` bugzilla-daemon
2017-03-31  9:04 ` bugzilla-daemon
2017-03-31 14:49 ` bugzilla-daemon
2017-04-02 13:18 ` bugzilla-daemon
2017-04-03  9:19 ` bugzilla-daemon
2017-04-04 17:03 ` bugzilla-daemon
2017-04-06 16:27 ` bugzilla-daemon
2017-04-06 16:54 ` bugzilla-daemon
2017-04-10  7:44 ` bugzilla-daemon
2017-04-10 10:03 ` bugzilla-daemon
2017-04-10 22:25 ` bugzilla-daemon
2017-04-10 22:27 ` bugzilla-daemon
2017-04-10 22:28 ` bugzilla-daemon
2017-04-10 22:29 ` bugzilla-daemon
2017-04-10 22:56 ` bugzilla-daemon
2017-04-10 22:56 ` bugzilla-daemon
2017-04-18 14:23 ` bugzilla-daemon
2017-04-18 14:23 ` bugzilla-daemon
2017-04-18 14:23 ` bugzilla-daemon
2017-04-18 14:23 ` bugzilla-daemon
2017-04-18 15:19 ` bugzilla-daemon
2017-04-19 23:01 ` bugzilla-daemon
2017-04-19 23:04 ` bugzilla-daemon
2017-04-19 23:36 ` bugzilla-daemon
2019-11-19  9:27 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100465-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.