From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: kernel lockups with 2.6.36
Date: Wed, 17 Nov 2010 00:39:54 -0700 [thread overview]
Message-ID: <201011170039.54869.thomas@fjellstrom.ca> (raw)
In-Reply-To: <201011141009.15691.thomas@fjellstrom.ca>
On November 14, 2010, you wrote:
> Today I experienced something odd, several kernel threads locked up in
> several different subsystems. It caused X to lock up, and not draw
> anything, access to nfs died, and trying to unmount, remount readonly, or
> do much other than ssh and copy files with scp (which may or may not have
> been in cache, might have been) locked up.
>
> I'm using a vanila 2.6.36.
>
> It looks to me like fscache/cachefiles may have started the problem, but I
> can't be sure, and I'm not entirely sure why that would cause i915 to lock
> up as well. I've disabled cachefiles for now, thinking that might make it
> go away. (its locked up twice today)
>
> here's the entire dmesg:
[snip]
Does anyone know whats going on here? Is it just a fscache bug? Or something a
little more insidious (since it seemed to cause a drm/intel_gfx lockup as
well?)
--
Thomas Fjellstrom
thomas@fjellstrom.ca
prev parent reply other threads:[~2010-11-17 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 17:09 Thomas Fjellstrom
2010-11-17 7:39 ` Thomas Fjellstrom [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=201011170039.54869.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome