All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 02 Jan 2014 22:19:15 +0000	[thread overview]
Message-ID: <bug-64891-2300-jU38QjHExw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64891-2300@https.bugzilla.kernel.org/>

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

--- Comment #44 from Joaquín Aramendía <samsagax@gmail.com> ---
Created attachment 120671
  --> https://bugzilla.kernel.org/attachment.cgi?id=120671&action=edit
Nouveau locked dmesg 3.13rc6 patched

Ok. Then I got 3.13rc6 with the patch from comment #37. Entering
multi-user.target went fine. Then I tried to enter X. Here is the dmesg from
that run. It took me almost 15 minutes of lockup. This time it got to print a
trace. It seems that is only related to nouveau.

Hope this helps

-- 
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-01-02 22:19 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 [this message]
2014-02-15 13:04 ` bugzilla-daemon
2015-06-30 22:15 ` 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-64891-2300-jU38QjHExw@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.