Re: filemap.c bad pmd

[Harald Welte]

On Fri, Jan 16, 2004 at 11:16:20AM +0100, Harald Staub wrote:
> Hello Harald Welte
> 
> Sorry for asking you directly, please give me a hint if I should ask on a 
> mailing list or so.

no problem.

> One of our news servers just had a kernel panic that has similarities to a 
> problem you had in August:
> 
> <http://www.ussg.iu.edu/hypermail/linux/kernel/0308.1/0778.html>
> "2.4.18/2.4.20 filemap.c pmd bug (was Re: Problem with mm in 2.4.19 and 
> 2.4.20)"

mh.  So we can acknowledge that there is a problem.  
 
> Since I could not find a solution, I would like to ask you if you have a 
> hint for me.  Below are some details.

No, I didn't receive any hint from one of the filesystem/mm developers :(

> Harald Staub
> staub@xxxxxxxxx

Hey, you are one of the admins of the switch.ch newsservers?  They're
one of the biggest in europe (besides belnet.be and garr.it), aren't
they?

> filemap.c:2228: bad pmd 214001e3.
> Unable to handle kernel paging request at virtual address e15dc264
>  printing eip:
> f88ac2e4
> *pde = 214001e3
> *pte = bf8ed65a
> Oops: 0000
> CPU:    1
> EIP:    0060:[<f88ac2e4>]    Tainted: P
> EFLAGS: 00010202
> eax: 00005e00   ebx: 6a5605ea   ecx: 0000000a   edx: 17a82000
> esi: 00010000   edi: 00000020   ebp: e15dc200   esp: c1c15ee0
> ds: 0068   es: 0068   ss: 0068
> Process swapper (pid: 0, stackpage=c1c15000)
> Stack: f7910000 00010000 00000020 0000000b 00000001 c02303d9 00002ae0 
> 00000000
>        c037998c c0379960 000005ea f7906d80 01000040 f88ab30c f7910000 
>        f7917bec
>        00000001 f7c33dc0 04000001 c0395a88 c0108cd1 0000000b f79a3c00 
>        c1c15f7c
> Call Trace:    [<c02303d9>] [<f88ab30c>] [<c0108cd1>] [<c0108ef7>] 
> [<c01052b0>]
>   [<c01052b0>] [<c01052b0>] [<c01052b0>] [<c01052dc>] [<c0105342>] 
>   [<c0117b7f>]
>   [<c0117a8e>]
> 
> Code: 83 7d 64 00 74 0a 68 1d 03 00 00 e8 78 b0 86 c7 8b 44 24 28
>  <0>Kernel panic: Aiee, killing interrupt handler!

that oops is not very helpful as long as it isn't processed by ksymoops
(which only you can do with your original kernel binary and system.map)

> ProLiant DL380, dual PIII 1GHz, 1GB RAM, kernel 2.4.24 with some patches 
> (usagi, exec_shield; not used on this machine, but patched in: xfs, 
> cryptoloop), highmem (4GB) support, inn 2.4.1
> Disks connected to "Compaq Smart Array 5300 Controller" (SCSI) and aic7xxx 
> (IDE RAID)

mh, as indicated in my original posting, I was running a pretty standard
configuration (no patches, no highmem, not even SMP) and had the same
problem with an inn (2.3.x) server.

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

Attachment: signature.asc
Description: Digital signature