From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32402] Oops associated with radeon_unpin_work_func
Date: Mon, 30 May 2011 08:00:48 GMT [thread overview]
Message-ID: <201105300800.p4U80mBf026474@demeter2.kernel.org> (raw)
In-Reply-To: <bug-32402-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32402
--- Comment #18 from Stuart Foster <smf.linux@ntlworld.com> 2011-05-30 08:00:45 ---
(In reply to comment #16)
> Created an attachment (id=59942)
--> (https://bugzilla.kernel.org/attachment.cgi?id=59942) [details]
> proposed fix 2. against 2.6.39
>
> try again + fix error paths.
Ran the patch on 2.6.39 overnight (~9 hours) and there have been no problems
the problem looks fixed for me.
thanks
Stuart
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-05-30 8:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 23:13 [Bug 32402] New: Oops associated with radeon_unpin_work_func bugzilla-daemon
2011-03-31 23:20 ` [Bug 32402] " bugzilla-daemon
2011-04-01 8:12 ` bugzilla-daemon
2011-04-04 22:59 ` bugzilla-daemon
2011-04-04 23:11 ` bugzilla-daemon
2011-04-04 23:14 ` bugzilla-daemon
2011-04-04 23:17 ` bugzilla-daemon
2011-04-06 14:26 ` bugzilla-daemon
2011-04-06 14:27 ` bugzilla-daemon
2011-04-07 7:38 ` bugzilla-daemon
2011-04-14 14:11 ` bugzilla-daemon
2011-04-16 21:08 ` bugzilla-daemon
2011-04-16 21:28 ` bugzilla-daemon
2011-05-19 13:04 ` bugzilla-daemon
2011-05-29 8:30 ` bugzilla-daemon
2011-05-29 8:30 ` bugzilla-daemon
2011-05-29 10:09 ` bugzilla-daemon
2011-05-29 10:24 ` bugzilla-daemon
2011-05-30 8:00 ` bugzilla-daemon [this message]
2011-06-14 11:21 ` bugzilla-daemon
2011-06-16 14:50 ` bugzilla-daemon
2011-06-16 14:50 ` bugzilla-daemon
2011-06-26 12:58 ` bugzilla-daemon
2011-07-10 23:14 ` 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=201105300800.p4U80mBf026474@demeter2.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.