From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88911] New: Radeon: Patch "drm/radeon: fix speaker allocation setup" causes kernel lockup
Date: Tue, 25 Nov 2014 19:22:20 +0000 [thread overview]
Message-ID: <bug-88911-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=88911
Bug ID: 88911
Summary: Radeon: Patch "drm/radeon: fix speaker allocation
setup" causes kernel lockup
Product: Drivers
Version: 2.5
Kernel Version: 3.17.3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: klaus.kusche@computerix.info
Regression: No
Since 3.17.3, my system (Dell precision M 6700 notebook with AMD Cap Verde
graphics) locks up hard as soon as I connect a beamer via HDMI
(both when connected to the HDMI output and when connected to the DP output
via a DP/HDMI adapter) while X is running or before starting X
(console mode only is fine). 3.17.2 worked.
With good luck, the system is still alive, but keyboard, display and mouse
are locked up, because X hangs. The system shuts down on soft power off,
but with 10 seconds delay and the filesystems still mounted:
X seems to be unkillable.
With bad luck, the fan goes to 100 % and the kernel seems to be dead:
Zero disk activity, hard power off is the only way out.
The faulty patch is "drm/radeon: fix speaker allocation setup":
Applying or reverting this patch only makes the difference.
--
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
next reply other threads:[~2014-11-25 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 19:22 bugzilla-daemon [this message]
2014-11-26 3:35 ` [Bug 88911] Radeon: Patch "drm/radeon: fix speaker allocation setup" causes kernel lockup bugzilla-daemon
2014-12-08 15:52 ` 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-88911-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.