All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dennis J.A. Bijwaard" <dennis@h8922032063.dsl.speedlinq.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: bijwaard@gmail.com,
	"Dennis J.A. Bijwaard" <dennis@h8922032063.dsl.speedlinq.nl>,
	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: Sun, 15 Oct 2006 23:58:55 +0200	[thread overview]
Message-ID: <20061015215854.GA12890@jumbo.lan> (raw)
In-Reply-To: <20061015121202.378bdd41.akpm@osdl.org>

Hi Andrew,

Thanks for your reply. The machine has 512MB and some more swap:

Mem:    510960k total,   504876k used,     6084k free,     1868k buffers
Swap:   674640k total,     2652k used,   671988k free,   354832k cached

Machine may be slow for current standards, it has 2 * 500Mhz

Kind regards,
                Dennis

* Andrew Morton <akpm@osdl.org> [061015 21:13]:
> On Sun, 15 Oct 2006 19:56:40 +0200
> "Dennis J.A. Bijwaard" <dennis@h8922032063.dsl.speedlinq.nl> wrote:
> 
> > I got two soft lockups on one of the CPUs just now. I'm unsure if this
> > problem is in ext3, sys_close, or general kernel, so I've CC'd the
> > kernel list.
> > 
> > [1.] One line summary of the problem:
> > 
> > BUG: soft lockup detected on CPU#0! in sys_close/fput and ext3 journaling
> 
> Both warnings occurred when the kernel was tearing down large amounts of
> pagecache via invalidate_inode_pages().  One instances was a blockdev
> (probably the final close on the dvd) and the other was a regular file
> (perhaps a large dvd image?)
> 
> The CPU is slow: 500MHz pIII.  How much memory does it have?
> 
> So the kernel was doing a lot of work, on a slow CPU.  Perhaps that simply
> exceeded the softlockup timeout.  If that's true then the machine should
> have recovered.  Once it did, and once it didn't.  I don't know why it
> didn't.
> 

  reply	other threads:[~2006-10-15 22:02 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 [this message]
2006-11-14  9:58     ` CaT
2006-11-14 10:01       ` Andrew Morton
2006-11-14 23:29         ` CaT

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=20061015215854.GA12890@jumbo.lan \
    --to=dennis@h8922032063.dsl.speedlinq.nl \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=bijwaard@gmail.com \
    --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.