All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73931] rmmod radeon and kernel crash
Date: Mon, 14 Apr 2014 16:11:46 +0000	[thread overview]
Message-ID: <bug-73931-2300-WGxCXnrQyn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73931-2300@https.bugzilla.kernel.org/>

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

--- Comment #2 from Pali Rohár <pali.rohar@gmail.com> ---
Created attachment 132221
  --> https://bugzilla.kernel.org/attachment.cgi?id=132221&action=edit
syslog output after modprobe radeon

Yes, your patch fixing original problem. Maybe this is candidate for stable
releases. Patch tested on 3.14 and system working fine after rmmoding radeon
module, no crash after calling: find /sys

But now there is another new kernel crash. When I modprobe radeon module again
(after previous successful rmmod), kernel crash. See syslog output in
attachment.

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

  parent reply	other threads:[~2014-04-14 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  6:48 [Bug 73931] New: rmmod radeon and kernel crash bugzilla-daemon
2014-04-14 14:36 ` [Bug 73931] " bugzilla-daemon
2014-04-14 16:11 ` bugzilla-daemon [this message]
2014-04-14 16:53 ` bugzilla-daemon
2014-04-14 18:27 ` bugzilla-daemon
2014-04-14 19:06 ` bugzilla-daemon
2014-04-14 20:53 ` bugzilla-daemon
2014-04-14 21:25 ` bugzilla-daemon
2014-04-14 21:44 ` bugzilla-daemon
2014-04-21 12:53 ` bugzilla-daemon
2014-04-30 14:22 ` bugzilla-daemon
2018-06-08 10:41 ` 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-73931-2300-WGxCXnrQyn@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.