LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Igmar Palsenberg <i.palsenberg@jdi-ict.nl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: 2.6.16.32 stuck in generic_file_aio_write()
Date: Wed, 6 Dec 2006 17:14:08 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0612061655160.11560@jdi.jdi-ict.nl> (raw)
In-Reply-To: <20061206074008.2f308b2b.akpm@osdl.org>


> > Done some more digging : isn't http://lkml.org/lkml/2006/10/13/139 somehow 
> > related ? I do see pagefaults, and inode locks and mmap_locks. 
> > 
> 
> I thought it was, but from my look through yout 8-billion-task backtrace,
> no task was stuck in D-state with the appropriate call trace.
> 
> So I don't know what's causing this.  In the first trace you have at least
> four D-state kjournalds and a lot of processes stuck on an i_mutex.  I
> guess it's consistent with an IO system which is losing completion
> interrupts. 

Hmm.. Is there any way to make sure ? I've got a second machine (almost 
identical), which doesn't show this.

The main difference is the running kernel. I've had them at the same 
kernel, at which bad machine still crashes.

/proc/interrupts

Bad machine  : 18:   11160637   11235698   IO-APIC-fasteoi   arcmsr
Good machine : 18:   61658630   79352227   IO-APIC-level  arcmsr

Bad machine is running 2.6.19, good is running 2.6.14.7-grsec, which 
probably accounts for these changes.

> AFAICT in the second trace all you have is a lot of processes
> stuck on i_mutex for no obvious reason - I don't know why that would
> happen.

It's consequent, also the traces.
 
> How long does it take for this to happen?

Days to a week tops. It does happen less frequent with the 2.6.19, 
2.6.16.32 triggered it almost daily.

> Yes, lockdep might find something.

I've enabled most debug options. I'll boot the other kernel tomorrow.



Regards,


	Igmar

  reply	other threads:[~2006-12-06 16:14 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 [this message]
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
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=Pine.LNX.4.58.0612061655160.11560@jdi.jdi-ict.nl \
    --to=i.palsenberg@jdi-ict.nl \
    --cc=akpm@osdl.org \
    --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).