LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Igmar Palsenberg <i.palsenberg@jdi-ict.nl>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de,
	erich <erich@areca.com.tw>
Subject: Re: 2.6.16.32 stuck in generic_file_aio_write()
Date: Thu, 14 Dec 2006 01:10:42 -0800	[thread overview]
Message-ID: <20061214011042.7b279be6.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0612140953080.9623@jdi.jdi-ict.nl>

On Thu, 14 Dec 2006 09:55:38 +0100 (CET)
Igmar Palsenberg <i.palsenberg@jdi-ict.nl> wrote:

> 
> > > Hmm.. Switching CONFIG_HZ from 1000 to 250 seems to 'fix' the problem. 
> > > I haven't seen the issue in nearly a week now. This makes Andrew's theory 
> > > about missing interrupts very likely.
> > > 
> > > Andrew / others : Is there a way to find out if it *is* missing 
> > > interrupts ?
> > > 
> > 
> > umm, nasty.  What's in /proc/interrupts?
> 
> See below. The other machine is mostly identifical, except for i8042 
> missing (probably due to running an older kernel, or small differences in 
> the kernel config).
> 

Does the other machine have the same problems?

Are you able to rule out a hardware failure?

> [jdiict@lnx01 ~]$ cat /proc/interrupts
>            CPU0       CPU1
>   0:   73702693   74509271   IO-APIC-edge      timer
>   1:          1          1   IO-APIC-edge      i8042
>   4:       2289       8389   IO-APIC-edge      serial
>   8:          0          1   IO-APIC-edge      rtc
>   9:          0          0   IO-APIC-fasteoi   acpi
>  12:          3          1   IO-APIC-edge      i8042
>  16:  203127788          0   IO-APIC-fasteoi   uhci_hcd:usb2, eth0
>  17:        525        492   IO-APIC-fasteoi   uhci_hcd:usb4
>  18:   13000070   67584889   IO-APIC-fasteoi   arcmsr
>  19:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1
>  20:          0          0   IO-APIC-fasteoi   uhci_hcd:usb3
> NMI:          0          0
> LOC:  148127756  148133476
> ERR:          0
> MIS:          0

The disk interrupt is unshared, which rules out a few software problems, I
guess.


  reply	other threads:[~2006-12-14  9:10 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 [this message]
2006-12-14  9:25                       ` Igmar Palsenberg
2007-02-05 10:24                       ` Igmar Palsenberg
2007-02-06  2:42                         ` erich
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=20061214011042.7b279be6.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=erich@areca.com.tw \
    --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).