From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73931] New: rmmod radeon and kernel crash
Date: Sun, 13 Apr 2014 06:48:14 +0000 [thread overview]
Message-ID: <bug-73931-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=73931
Bug ID: 73931
Summary: rmmod radeon and kernel crash
Product: Drivers
Version: 2.5
Kernel Version: 3.14
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: pali.rohar@gmail.com
Regression: No
Created attachment 132051
--> https://bugzilla.kernel.org/attachment.cgi?id=132051&action=edit
rmmod_radeon_kernel_panic
After calling rmmod radeon, kernel show lots of error lines and then crash.
It looks like that radeon module does not cleanup hwmon interface at exit.
After calling rmmod radeon there is still hwmon interface:
$ readlink /sys/class/hwmon/hwmon1
../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon1
And after calling ls, or cat in hwmon1 kernel crash...
See attachment from syslog.
$ lspci -nn
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun
XT [Radeon HD 8670A/8670M/8690M] [1002:6660]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-04-13 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 6:48 bugzilla-daemon [this message]
2014-04-14 14:36 ` [Bug 73931] rmmod radeon and kernel crash bugzilla-daemon
2014-04-14 16:11 ` bugzilla-daemon
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@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.