All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198669] Driver crash at radeon_ring_backup+0xd3/0x140 [radeon]
Date: Tue, 06 Feb 2018 15:53:14 +0000	[thread overview]
Message-ID: <bug-198669-2300-XHoXHh0KpN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198669-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198669

--- Comment #8 from Christian König (christian.koenig@amd.com) ---
(In reply to roger@beardandsandals.co.uk from comment #7)
> The original point I made in the bug report was that this bug is not about
> the mechanical hardware glitch. It as about the driver being in what is
> obviously a failure mode and attempting a recovery that fails and leaves the
> system in unusable state.

You are missing the point. The driver fails to recover because the hardware is
buggy and not because there is any problem with the recovery routine.

In other words we read back an impossible value from the hardware and that is
why the system is failing.

I mean I can handle this impossible value at this code location, but as you
actually figured out by yourself it then fails at the next best location.

There are simply hundreds or even thousands of locations where the assumption
is that the hardware works correctly and we don't handle the case to get
nonsense values.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-02-06 15:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 17:39 [Bug 198669] New: Driver crash at radeon_ring_backup+0xd3/0x140 [radeon] bugzilla-daemon
2018-02-04 17:41 ` [Bug 198669] " bugzilla-daemon
2018-02-04 18:26 ` bugzilla-daemon
2018-02-04 20:55 ` bugzilla-daemon
2018-02-05 12:16 ` bugzilla-daemon
2018-02-05 22:03 ` bugzilla-daemon
2018-02-06 14:05 ` bugzilla-daemon
2018-02-06 14:12 ` bugzilla-daemon
2018-02-06 15:19 ` bugzilla-daemon
2018-02-06 15:53 ` bugzilla-daemon [this message]
2018-02-06 21:39 ` bugzilla-daemon
2018-02-07  8:22 ` bugzilla-daemon
2018-02-07  9:12 ` bugzilla-daemon
2018-02-07  9:16 ` bugzilla-daemon
2018-02-07 12:45 ` bugzilla-daemon
2018-12-03  3:55 ` bugzilla-daemon
2018-12-03  8:14 ` bugzilla-daemon
2018-12-03  8:18 ` bugzilla-daemon
2018-12-03 11:12 ` 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-198669-2300-XHoXHh0KpN@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.