public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Max Kellermann <max@duempel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc[1-5]: soft lockups on Athlon64 X2
Date: Wed, 1 Mar 2006 02:22:35 -0800	[thread overview]
Message-ID: <20060301022235.51f47b42.akpm@osdl.org> (raw)
In-Reply-To: <20060301100744.GA1041@roonstrasse.net>

Max Kellermann <max@duempel.org> wrote:
>
> On 2006/03/01 07:19, Andrew Morton <akpm@osdl.org> wrote:
> > Strange.  I did remove a cond_resched() from
> > invalidate_mapping_pages() so that it could be run under spinlock
> > but I cannot believe that you had so many pages cached that the
> > invalidate took more than ten seconds.
> > 
> > Does the machine recover and otherwise work OK?
> 
> The mount indeed took more than ten (wallclock) seconds during which
> the lockups occured, and after that it seemed usable (I rebooted
> shortly after because I feared fs corruption).  Normally, this mount
> takes 2 seconds or so - it's a crypted 200GB XFS partition.  The same
> goes for the "bugged" kernel with "nosmp": mount is finished quickly.
> 

How is it encrypted?   (With which kernel encryption stuff?)

I guess it'd be useful to see where all that time is spent, if you have
time.   Enable CONFIG_PROFILING, boot with `profile=1', do:

readprofile -r
mount ...
readprofile -n -v -m /boot/System.map | sort -n -k 3 | tail -40

(Make sure it's the correct System.map).

  reply	other threads:[~2006-03-01 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 12:27 2.6.16-rc[1-5]: soft lockups on Athlon64 X2 Max Kellermann
2006-03-01  6:19 ` Andrew Morton
2006-03-01 10:07   ` Max Kellermann
2006-03-01 10:22     ` Andrew Morton [this message]
2006-03-01 22:23       ` Max Kellermann

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=20060301022235.51f47b42.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@duempel.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