linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: sal@agora.pl
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.18/2.4.20 filemap.c pmd bug (was Re: Problem with mm in 2.4.19 and 2.4.20)
Date: Mon, 11 Aug 2003 09:34:43 +0200	[thread overview]
Message-ID: <20030811073443.GA8953@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030208121633.GB17017@virgin.gazeta.pl>

[-- Attachment #1: Type: text/plain, Size: 2834 bytes --]

Przemys?aw Maciuszko wrote:

>I have a problem with one news server (feeder) box running INN.
>Under heavy load i get the following error on the console:
>
>filemap.c:2084: bad pmd 2bc001e3
>
>This showed few times during last few days and few times server 'hanged up'
>after this.

I can confirm this problem.  It happens on one of my newsservers as well,
currently at least once per day.  It is a dual PIII 650MHz, 1GB RAM,
200GB spool (scsi hardware raid array attached to adaptec aic7xxx), six
seperate SCSI disks attached to a seperate aic7xxx controller for
overview, running inn-2.3.2.

We've tried  RedHat kernels 2.4.18-3, 2.4.18-17.7, 2.4.20-19.7 and 
2.4.20-19.7bigmem as well as a kernel.org 2.4.20 - all with the same 
problem.

After the filemap.c / pmd_ERROR() printk, the box either hangs (no 
further printout, not that often) or has a stack overflow (most of the 
time):

filemap.c:2258: bad pmd c0003000(00000000000001e3).
do_IRQ: stack overflow: -864
c0252845 fffffca0 206d6564 c2426000 00000000 c0117b20 c0101018 c024bd2c
c2426000 00000018 00000018 00000000 c0117b20 c0101018 c2426470 6f6e0018
40320018 ffffff00 c0117b43 00000010 00000202 7369636e 3e65642e 613c200a
Call Trace:   [<c0117b20>] do_page_fault [kernel] 0x0 (0xc242634c))
[<c0117b20>] do_page_fault [kernel] 0x0 (0xc2426368))
[<c0117b43>] do_page_fault [kernel] 0x23 (0xc2426380))
[<c0117b20>] do_page_fault [kernel] 0x0 (0xc242645c))
[<c0108cc4>] error_code [kernel] 0x34 (0xc2426464))
[<c0117fc5>] do_page_fault [kernel] 0x4a5 (0xc2426498))
[<c0117b20>] do_page_fault [kernel] 0x0 (0xc2426574))
[<c0108cc4>] error_code [kernel] 0x34 (0xc242657c))
[<c0117fc5>] do_page_fault [kernel] 0x4a5 (0xc24265b0))
[<c0117b20>] do_page_fault [kernel] 0x0 (0xc242668c))
[<c0108cc4>] error_code [kernel] 0x34 (0xc2426694))
[<c0117fc5>] do_page_fault [kernel] 0x4a5 (0xc24266c8))
[<c0117b20>] do_page_fault [kernel] 0x0 (0xc24267a4))
[<c0108cc4>] error_code [kernel] 0x34 (0xc24267ac))

The messages are always preceded by a '(scsi0:A:0:0): Locking max tag 
count at 64' message. The scsi device number is changing, so it cannot 
be a single device

>Anyone has an idea what can cause it?

Unfortunately I'm not very familiar with the linux MM subsystem.  But 
since I consider this now as a confirmed bug, maybe some of the other 
lkml folks have an idea what might be going on.

>I'm using Linux Debian on dual PIII 1.1Ghz, 1GB RAM, LVM version 1.0.6
>Qlogic FC 2200F driver version 6.01

We don't use lvm, so the similarities seem to be:  Dual PIII, 
SCSI, INN

--
- Harald Welte <laforge@gnumonks.org>               http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-11  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 12:16 Problem with mm in 2.4.19 and 2.4.20 Przemysław Maciuszko
2003-08-11  7:34 ` Harald Welte [this message]
2003-08-11  9:48   ` 2.4.18/2.4.20 filemap.c pmd bug (was Re: Problem with mm in 2.4.19 and 2.4.20) Christoph Hellwig
2003-08-11 10:21     ` Harald Welte

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=20030811073443.GA8953@sunbeam.de.gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sal@agora.pl \
    /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 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).