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: Mon, 05 Feb 2018 22:03:56 +0000 [thread overview]
Message-ID: <bug-198669-2300-x5FJmw06sl@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 #4 from roger@beardandsandals.co.uk (roger@beardandsandals.co.uk) ---
Well it moved the problem. It crashed somewhere else in the driver with some
message about scratch. Sorry I cannot tell you what is was because I screwed up
the save of the the kernel message buffer, and now I cannot get the thing to
glitch again. My normal method of stamping on the floor next to the system is
not working. I think I might have overdone it and now the thing has bedded in.
Going to leave it powered off overnight and try again in the morning.
--
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
next prev parent reply other threads:[~2018-02-05 22:04 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 [this message]
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
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-x5FJmw06sl@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.