[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0702051118230.30521@jdi.jdi-ict.nl>
Date: Mon, 5 Feb 2007 11:24:30 +0100 (CET)
From: Igmar Palsenberg <i.palsenberg@...-ict.nl>
To: Andrew Morton <akpm@...l.org>
cc: linux-kernel@...r.kernel.org, npiggin@...e.de,
erich <erich@...ca.com.tw>
Subject: Re: 2.6.16.32 stuck in generic_file_aio_write()
> Does the other machine have the same problems?
It does. It seems to depend on the interrupt frequency : Setting KERNEL_HZ=250
makes it ony appear once a month or so, with KERNEL_HZ=1000, it will
occur within a week. It does happen a lot less with the other machine,
which isn't under disk activity load as much as the other machine.
> Are you able to rule out a hardware failure?
Well.. It's too much coincidence that 2 (almost identical) machines show
the same weard behaviour. What strikes me that only *disk* interrupts
after a while don't get handled. The machine itself is alive, just all
disk IO is blocked, which makes it pretty much useless.
Erich, could this be some sort of hardware problem ? I know it's a PITA to
reproduce, but setting CONFIG_HZ to 1000 and bashing the machine with
diskactivity seems to help :)
Regards,
Igmar
--
Igmar Palsenberg
JDI ICT
Zutphensestraatweg 85
6953 CJ Dieren
Tel: +31 (0)313 - 496741
Fax: +31 (0)313 - 420996
The Netherlands
mailto: i.palsenberg@...-ict.nl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists