From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 32982] Kernel locks up a few minutes after boot
Date: Sun, 17 Apr 2011 18:20:47 GMT [thread overview]
Message-ID: <201104171820.p3HIKlFC000484@demeter1.kernel.org> (raw)
In-Reply-To: <bug-32982-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32982
--- Comment #9 from Rafael J. Wysocki <rjw@sisk.pl> 2011-04-17 18:20:39 ---
On Sunday, April 17, 2011, Linus Torvalds wrote:
> Is this machine running a RAID5 setup or something like that?
>
> There is a known interaction with the new block layer plugging code
> and MD. The "hung task" report in that bugzilla looks very much like
> that issue. And you do have "root=/dev/md0", so clearly there's some
> md thing going on.
>
> And bisecting might not work all that well for it, because I suspect
> it ends up being very much a matter of IO patterns how it triggers.
>
> Neil supposedly has a patch for it, but I haven't seen it yet. Neil, Jens?
>
> Linus
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2011-04-17 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-32982-2300@https.bugzilla.kernel.org/>
2011-04-11 23:05 ` [Bug 32982] Kernel locks up a few minutes after boot bugzilla-daemon
2011-04-11 23:09 ` bugzilla-daemon
2011-04-11 23:14 ` bugzilla-daemon
2011-04-11 23:15 ` bugzilla-daemon
2011-04-12 18:34 ` bugzilla-daemon
2011-04-12 18:40 ` bugzilla-daemon
2011-04-12 18:42 ` bugzilla-daemon
2011-04-13 18:49 ` bugzilla-daemon
2011-04-14 15:57 ` bugzilla-daemon
2011-04-14 19:24 ` bugzilla-daemon
2011-04-15 10:23 ` bugzilla-daemon
2011-04-17 18:20 ` bugzilla-daemon [this message]
2011-05-01 9:35 ` bugzilla-daemon
2011-05-01 11:22 ` 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=201104171820.p3HIKlFC000484@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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