All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: "Dennis J.A. Bijwaard" <dennis@h8922032063.dsl.speedlinq.nl>,
	bijwaard@gmail.com, sct@redhat.com, adilger@clusterfs.com,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup detected on CPU#0! in sys_close and ext3
Date: Wed, 15 Nov 2006 10:29:00 +1100	[thread overview]
Message-ID: <20061114232900.GD3155@zip.com.au> (raw)
In-Reply-To: <20061114020125.636c9006.akpm@osdl.org>

On Tue, Nov 14, 2006 at 02:01:25AM -0800, Andrew Morton wrote:
> > It did for me in all cases. Should it be taking long enough to trigger
> > the softlock timeout to do this? The size of the device is approx 280gig.
> 
> It's a bit of a worry if it's taking all that time to shoot down 4g of
> pagecache.  The 280G will affect things - the radix-tree will be sparse and
> the invalidate has firther to walk.  But still...

Yeah. I would've thought that legitimate usage would not trigger such
things, which is why I have it on whilst I'm building this box up.

> I assume that a fsck does the same thing?

Just did an e2fsck and it did the same thing.

-- 
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby

      reply	other threads:[~2006-11-14 23:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15 17:56 BUG: soft lockup detected on CPU#0! in sys_close and ext3 Dennis J.A. Bijwaard
2006-10-15 19:12 ` Andrew Morton
2006-10-15 21:58   ` Dennis J.A. Bijwaard
2006-11-14  9:58     ` CaT
2006-11-14 10:01       ` Andrew Morton
2006-11-14 23:29         ` CaT [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=20061114232900.GD3155@zip.com.au \
    --to=cat@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=bijwaard@gmail.com \
    --cc=dennis@h8922032063.dsl.speedlinq.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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.