LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "erich" <erich@areca.com.tw>
To: "Igmar Palsenberg" <i.palsenberg@jdi-ict.nl>
Cc: "Andrew Morton" <akpm@osdl.org>,
	"linux kernel" <linux-kernel@vger.kernel.org>, <npiggin@suse.de>
Subject: Re: 2.6.16.32 stuck in generic_file_aio_write()
Date: Tue, 6 Feb 2007 10:42:38 +0800	[thread overview]
Message-ID: <000501c74998$79b41490$4e00a8c0@erich2003> (raw)
In-Reply-To: <Pine.LNX.4.58.0702051118230.30521@jdi.jdi-ict.nl>

Dear Igmar Palsenberg,

I can not make sure it is hardware problem, but I have interest in this 
case's reproducing.
If you tell me your platform's construction, I will try it and give you good 
solution.
Does your RAID adapter's firmware version work on 1.42?
Areca firmware had fix some hardware bugs and rare sg length handle in this 
version.

Best Regards
Erich Chen

----- Original Message ----- 
From: "Igmar Palsenberg" <i.palsenberg@jdi-ict.nl>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>; <npiggin@suse.de>; "erich" 
<erich@areca.com.tw>
Sent: Monday, February 05, 2007 6:24 PM
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@jdi-ict.nl 


  reply	other threads:[~2007-02-06  3:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 12:41 Igmar Palsenberg
2006-11-29 15:20 ` Igmar Palsenberg
2006-11-30  1:23 ` erich
2006-11-30  9:48   ` Igmar Palsenberg
2006-12-01  5:22 ` Andrew Morton
2006-12-01  8:56   ` Igmar Palsenberg
2006-12-04 21:03     ` Igmar Palsenberg
2006-12-06 15:17       ` Igmar Palsenberg
2006-12-06 15:40         ` Andrew Morton
2006-12-06 16:14           ` Igmar Palsenberg
2006-12-07  9:58           ` Igmar Palsenberg
2006-12-07 12:29             ` Igmar Palsenberg
2006-12-14  8:15               ` Igmar Palsenberg
2006-12-14  8:42                 ` Andrew Morton
2006-12-14  8:55                   ` Igmar Palsenberg
2006-12-14  9:10                     ` Andrew Morton
2006-12-14  9:25                       ` Igmar Palsenberg
2007-02-05 10:24                       ` Igmar Palsenberg
2007-02-06  2:42                         ` erich [this message]
2007-02-12  9:26                           ` Igmar Palsenberg
2007-02-19 13:25                           ` Igmar Palsenberg

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='000501c74998$79b41490$4e00a8c0@erich2003' \
    --to=erich@areca.com.tw \
    --cc=akpm@osdl.org \
    --cc=i.palsenberg@jdi-ict.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --subject='Re: 2.6.16.32 stuck in generic_file_aio_write()' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).