All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 10:51:41 +0100	[thread overview]
Message-ID: <3E35012D.69A90F93@aitel.hist.no> (raw)
In-Reply-To: 20030126231015.6ad982e4.akpm@digeo.com

Andrew Morton wrote:
> 
>   Which _looks_ like a request queueing problem, but Andres says it goes
>   away when devfs is disabled in config.  So I've dropped the smalldevfs
>   patch for now - would be appreciated if devfs users could retest this
>   patch, with CONFIG_DEVFS=y.

mm6 works where mm5 failed. You are probably right suspecting devfs,
I have devfs enabled although I don't actually use it.  No problems
with RAID1 either.

I enabled hangcheck timer, and gets this now and then:

Warning! Detected 2106 micro-second gap between interrupts.
  Compensating for 1 lost ticks.
Call Trace:
 [<c010a6ad>] handle_IRQ_event+0x29/0x4c
 [<c010a881>] do_IRQ+0xbd/0x138
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c01093e0>] common_interrupt+0x18/0x20
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106ce3>] default_idle+0x23/0x28
 [<c0106d63>] cpu_idle+0x37/0x48
 [<c0105000>] rest_init+0x0/0x50
 [<c010504d>] rest_init+0x4d/0x50

Warning! Detected 2043 micro-second gap between interrupts.
  Compensating for 1 lost ticks.
Call Trace:
 [<c010a6ad>] handle_IRQ_event+0x29/0x4c
 [<c010a881>] do_IRQ+0xbd/0x138
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c01093e0>] common_interrupt+0x18/0x20
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106ce3>] default_idle+0x23/0x28
 [<c0106d63>] cpu_idle+0x37/0x48
 [<c0105000>] rest_init+0x0/0x50
 [<c010504d>] rest_init+0x4d/0x50


Helge Hafting

WARNING: multiple messages have this Message-ID (diff)
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 10:51:41 +0100	[thread overview]
Message-ID: <3E35012D.69A90F93@aitel.hist.no> (raw)
In-Reply-To: 20030126231015.6ad982e4.akpm@digeo.com

Andrew Morton wrote:
> 
>   Which _looks_ like a request queueing problem, but Andres says it goes
>   away when devfs is disabled in config.  So I've dropped the smalldevfs
>   patch for now - would be appreciated if devfs users could retest this
>   patch, with CONFIG_DEVFS=y.

mm6 works where mm5 failed. You are probably right suspecting devfs,
I have devfs enabled although I don't actually use it.  No problems
with RAID1 either.

I enabled hangcheck timer, and gets this now and then:

Warning! Detected 2106 micro-second gap between interrupts.
  Compensating for 1 lost ticks.
Call Trace:
 [<c010a6ad>] handle_IRQ_event+0x29/0x4c
 [<c010a881>] do_IRQ+0xbd/0x138
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c01093e0>] common_interrupt+0x18/0x20
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106ce3>] default_idle+0x23/0x28
 [<c0106d63>] cpu_idle+0x37/0x48
 [<c0105000>] rest_init+0x0/0x50
 [<c010504d>] rest_init+0x4d/0x50

Warning! Detected 2043 micro-second gap between interrupts.
  Compensating for 1 lost ticks.
Call Trace:
 [<c010a6ad>] handle_IRQ_event+0x29/0x4c
 [<c010a881>] do_IRQ+0xbd/0x138
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c01093e0>] common_interrupt+0x18/0x20
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106cc0>] default_idle+0x0/0x28
 [<c0106ce3>] default_idle+0x23/0x28
 [<c0106d63>] cpu_idle+0x37/0x48
 [<c0105000>] rest_init+0x0/0x50
 [<c010504d>] rest_init+0x4d/0x50


Helge Hafting
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2003-01-27  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27  7:10 2.5.59-mm6 Andrew Morton
2003-01-27  7:10 ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:17 ` 2.5.59-mm6 Andres Salomon
2003-01-27  8:24   ` 2.5.59-mm6 Joshua Kwan
2003-01-27  8:40     ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:46       ` 2.5.59-mm6 Joshua Kwan
2003-01-27  9:51 ` Helge Hafting [this message]
2003-01-27  9:51   ` 2.5.59-mm6 Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27 12:27 2.5.59-mm6 Luuk van der Duim
2003-01-27 18:50 ` 2.5.59-mm6 Mike Galbraith
2003-01-27 19:17   ` 2.5.59-mm6 Zwane Mwaikambo
     [not found]   ` <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>
2003-01-27 20:11     ` 2.5.59-mm6 Mike Galbraith
2003-01-27 21:13       ` 2.5.59-mm6 Zwane Mwaikambo

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=3E35012D.69A90F93@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.