From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64891] [snd_hda_codec] BUG: soft lockup - CPU#0 stuck for 22s (when using vgaswitcheroo)
Date: Tue, 30 Jun 2015 22:15:36 +0000 [thread overview]
Message-ID: <bug-64891-2300-9XLa7pODwM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64891-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=64891
Tommaso Falchi Delitala <volalto86@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |volalto86@gmail.com
--- Comment #46 from Tommaso Falchi Delitala <volalto86@gmail.com> ---
Created attachment 181501
--> https://bugzilla.kernel.org/attachment.cgi?id=181501&action=edit
dmesg showing lockpuos (radeon off)
I still experience lockups related to audio with discrete card disabled via
vgaswitcheroo. Moreover the systems hangs at shutdown.
Kernel 4.0.6-1-ARCH
AMD Mobility Radeon HD5470 + intel integrated.
# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS: :DynOff:0000:01:00.0
2:DIS-Audio: :Off:0000:01:00.1
Interesting dmesg print:
snd_hda_intel 0000:01:00.1: Disabling via VGA-switcheroo
snd_hda_intel 0000:01:00.1: Cannot lock devices!
INFO: task kworker/u16:0:6 blocked for more than 120 seconds.
Tainted: G W 4.0.6-1-ARCH #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u16:0 D ffff880132fd7ca8 0 6 2 0x00000000
Workqueue: hd-audio1 hdmi_repoll_eld [snd_hda_codec_hdmi]
See complete dmesg 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
prev parent reply other threads:[~2015-06-30 22:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64891-2300@https.bugzilla.kernel.org/>
2013-12-13 11:54 ` [Bug 64891] [snd_hda_codec] BUG: soft lockup - CPU#0 stuck for 22s (when using vgaswitcheroo) bugzilla-daemon
2013-12-13 14:19 ` bugzilla-daemon
2013-12-13 14:29 ` bugzilla-daemon
2013-12-26 20:01 ` bugzilla-daemon
2013-12-27 22:22 ` bugzilla-daemon
2013-12-27 22:32 ` bugzilla-daemon
2013-12-28 15:12 ` bugzilla-daemon
2013-12-28 15:22 ` bugzilla-daemon
2013-12-28 15:36 ` bugzilla-daemon
2013-12-28 21:10 ` bugzilla-daemon
2013-12-28 21:13 ` bugzilla-daemon
2013-12-28 22:03 ` bugzilla-daemon
2013-12-28 23:16 ` bugzilla-daemon
2013-12-29 15:10 ` bugzilla-daemon
2013-12-29 21:12 ` bugzilla-daemon
2013-12-30 22:50 ` bugzilla-daemon
2013-12-30 23:59 ` bugzilla-daemon
2013-12-31 0:07 ` bugzilla-daemon
2013-12-31 0:09 ` bugzilla-daemon
2013-12-31 0:20 ` bugzilla-daemon
2013-12-31 0:49 ` bugzilla-daemon
2013-12-31 1:05 ` bugzilla-daemon
2013-12-31 1:06 ` bugzilla-daemon
2013-12-31 1:18 ` bugzilla-daemon
2013-12-31 1:50 ` bugzilla-daemon
2013-12-31 1:58 ` bugzilla-daemon
2013-12-31 12:49 ` bugzilla-daemon
2013-12-31 20:55 ` bugzilla-daemon
2013-12-31 21:02 ` bugzilla-daemon
2014-01-02 22:19 ` bugzilla-daemon
2014-02-15 13:04 ` bugzilla-daemon
2015-06-30 22:15 ` bugzilla-daemon [this message]
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-64891-2300-9XLa7pODwM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).