From: Max Kellermann <max@duempel.org>
To: Andrew Morton <akpm@osdl.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 11:07:44 +0100 [thread overview]
Message-ID: <20060301100744.GA1041@roonstrasse.net> (raw)
In-Reply-To: <20060228221948.3d76f80b.akpm@osdl.org>
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.
Max
next prev parent reply other threads:[~2006-03-01 10:08 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 [this message]
2006-03-01 10:22 ` Andrew Morton
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=20060301100744.GA1041@roonstrasse.net \
--to=max@duempel.org \
--cc=akpm@osdl.org \
--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