From: "Steve Hindle" <mech422@gmail.com>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
linux-ide@vger.kernel.org
Subject: Re: PROBLEM: Hardlock with 2.6.1[678] on Abit AI7, ICH5 + XFS, SATA under heavy I/O load
Date: Wed, 4 Oct 2006 22:27:18 -0700 [thread overview]
Message-ID: <9a0545880610042227i7960737alb49480c609cff802@mail.gmail.com> (raw)
In-Reply-To: <20061005043154.GA11811@melbourne.sgi.com>
On 10/4/06, David Chinner <dgc@sgi.com> wrote:
> On Wed, Oct 04, 2006 at 06:28:35PM -0700, Steve Hindle wrote:
> > Hello,
> >
> > My machine is hardlocking with recent kernels (including 2.6.18-mm3)
> > under heavy I/O load (for instance, just compiling the kernel is
> > enough to lock the machine). No bug,oops,or panic and nothing in the
> > system logs.
>
> Does it happen on any other filesystems? Is this your root filesystem
> that is hanging?
>
no, its not my root - but my other partitions are also XFS and are on
the same drive...
so not really any way to check ATM.
> Journalling filesystems shouldn't get corrupted by hangs or
> crashes...
I understood this in theory - but was rather pleased theory == practice.
However, I didn't even notice a 'not unmounted cleanly' message during
subsequent boots?
I might just have missed it though - Debian's boot has gotten much
'chattier' over the years...
Steve
prev parent reply other threads:[~2006-10-05 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 1:28 PROBLEM: Hardlock with 2.6.1[678] on Abit AI7, ICH5 + XFS, SATA under heavy I/O load Steve Hindle
2006-10-05 4:31 ` David Chinner
2006-10-05 5:27 ` Steve Hindle [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=9a0545880610042227i7960737alb49480c609cff802@mail.gmail.com \
--to=mech422@gmail.com \
--cc=dgc@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.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