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: Mon, 10 Apr 2017 10:03:59 +0000	[thread overview]
Message-ID: <bug-100465-502-dKGuj2y8XX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100465-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from Julien Isorce <julien.isorce@gmail.com> ---
Thx for the answers and suggestions. In order to make sure I am still tracking
the same hard lockup, will any failure to load the gpu microcode will lead to a
total freeze of the machine ?

Currently in the setup where I can get some logs it can fail in 2 ways:

For both it starts with: "ring 0 stalled" is detected.

1: kworker triggers the gpu soft reset.

[drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs
aborting.
[drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C483
(len 254, WS 0, PS 4) @ 0xC4AD
[drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BC59
(len 74, WS 0, PS 8) @ 0xBC8E
si_mc_program::radeon_mc_wait_for_idle, the one after WREG32(vram.start) and
before 
evergreen_mc_resume. Can it freeze on a call to RREG32(SRBM_STATUS) & 0x1F00 ?

2: the gl app triggers the gpu soft reset.

The first failure is then evergreen_mc_stop::radeon_mc_wait_for_idle which
reached the timeout and then same errors as 1:
But the freeze happens a bit later in the radeon_gpu_reset sequence, in
atombios_crtc_dpms in one of its atombios_X(crtc, ATOM_Y) calls.

So my question above, will any single problem during the gpu soft reset lead to
a machine freeze ? If yes then I am probably tracking now a different freeze
that the one I reported initially.

Also in kernel's drm_drv.c::drm_err I tried to add a call to sys_sync();
(#include <linux/syscalls.h>) to make sure all errors are written on disk so
that I can read them after a reboot (Instead of having null characters ^@). But
I got an undefined reference. How could I add dependcy on fs/sync.c ? I have
not search long but at first glance tty driver calls it and there is nothing
special in the Makefile.
(As an alternative I am running a while true; sleep 0.5; sync; done but it does
not work all the time)

Thx!

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

[-- Attachment #1.2: Type: text/html, Size: 2941 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

  parent reply	other threads:[~2017-04-10 10:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 10:59 [Bug 100465] Hard lockup with radeonsi driver on FirePro W600, W9000 and W9100 bugzilla-daemon
2017-03-30 11:00 ` 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 [this message]
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-dKGuj2y8XX@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.