dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4 since fix incorrect mutex usage v3
Date: Wed, 25 Nov 2015 10:04:17 +0000	[thread overview]
Message-ID: <bug-93079-502-EahoebkqGD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93079-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Andy Furniss <adf.lists@gmail.com> ---
Seems this is the correct bad.

Ran all day yesterday without issue on the one before.

Booted into kernel set on the "bad" this morning and was locked within 10
minutes browsing.

Slightly different - no Oops,  similar trace, rcu_preempt detected stalls on
CPUs/tasks.

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

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

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

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

  parent reply	other threads:[~2015-11-25 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 15:54 [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4 bugzilla-daemon
2015-11-23 15:55 ` bugzilla-daemon
2015-11-23 20:58 ` [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4 since fix incorrect mutex usage v3 bugzilla-daemon
2015-11-25 10:04 ` bugzilla-daemon [this message]
2015-11-25 10:05 ` bugzilla-daemon
2015-11-26  9:39 ` bugzilla-daemon
2015-12-02 13:18 ` bugzilla-daemon
2015-12-02 21:46 ` bugzilla-daemon
2015-12-13 10:33 ` 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-93079-502-EahoebkqGD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox