From: Andrew Morton <akpm@zip.com.au>
To: Raphael Manfredi <Raphael_Manfredi@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-pre7 - known issue with ext3?
Date: Tue, 12 Feb 2002 00:10:40 -0800 [thread overview]
Message-ID: <3C68CE00.993721C2@zip.com.au> (raw)
In-Reply-To: <3057.1013498512@nice.ram.loc>
Raphael Manfredi wrote:
>
> I've got the following panic trace on the console this morning:
>
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[__insert_into_lru_list+28/92] Not tainted
> EFLAGS: 00010286
> eax: 00000000 ebx: 00000002 ecx: cce5ce40 edx: c02b5e94
> esi: cce5ce40 edi: cce5ce40 ebp: cfa11640 esp: cefb7ea0
> ds: 0018 es: 0018 ss: 0018
> Process perl (pid: 14685, stackpage=cefb7000)
> Stack: 00000002 c012b4c5 cce5ce40 00000002 cce5ce40 00000400 c012b4d5 cce5ce40
> c012be08 cce5ce40 00001000 00027000 00000000 cfa11640 00000400 00000000
> c012c357 cfa11640 c1225a80 00000000 00001000 c1225a80 40018000 cfa11640
> Call Trace: [__refile_buffer+73/80] [refile_buffer+9/16]
> [__block_commit_write+124/192] [generic_commit_write+51/92]
> [ext3_commit_write+290/436] [generic_file_write+1184/1720]
> [ext3_file_write+67/76] [sys_write+142/196] [system_call+51/64]
>
> Are there known problems with the implementation of ext3 on this kernel, or
> is the root cause elsewhere, and it's only an accident that it was in ext3
> code at the time?
>
Something corrupted a buffer-head from your freelist.
Please send me your .config and a description of the hardware.
Also a description of what sorts of things the machine is
being used for. Also please run memtest86 for 12 hours or
more and let me know the results.
Thanks.
-
prev parent reply other threads:[~2002-02-12 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 7:21 Raphael Manfredi
2002-02-12 8:10 ` Andrew Morton [this message]
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=3C68CE00.993721C2@zip.com.au \
--to=akpm@zip.com.au \
--cc=Raphael_Manfredi@pobox.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®