From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Pascal Haakmat <a.haakmat@chello.nl>
Cc: linux-kernel@vger.kernel.org,
"linux-xfs@oss.sgi.com" <linux-xfs@oss.sgi.com>
Subject: Re: XFS Oopses with 2.4.5 and 2.4.14?
Date: Wed, 28 Nov 2001 17:05:41 +0100 [thread overview]
Message-ID: <3C050B55.A3F3129B@loewe-komp.de> (raw)
In-Reply-To: <000701c177e6$7317af40$ea9133d5@groni1.gr.nl.home.com> <20011128155716.A7302@awacs.dhs.org>
Pascal Haakmat schrieb:
>
> Given the following Oopses, is it wise to continue running the XFS
> filesystem, or might there be some other underlying problem that is causing
> these Oopses?
>
> Kernel 2.4.5 + XFS 1.0.1:
I crosspost this to xfs-mailing list.
The filesystem itself looks good.
I'm still experiencing problems in the nfsd codepath. 2.4.4-xfs fixed a bug for this.
Now I run 2.4.9-xfs and wait for the next crash that seems to happen when
uptime gets > 13 days ;-(
BTW, it is recommended to compile the kernel with
$ kgcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>
> Nov 25 07:28:23 awacs kernel: Unable to handle kernel paging request at virtual address 0cb73058
> Nov 25 07:28:23 awacs kernel: printing eip:
> Nov 25 07:28:23 awacs kernel: c01d6493
> Nov 25 07:28:23 awacs kernel: *pde = 00000000
> Nov 25 07:28:23 awacs kernel: Oops: 0000
> Nov 25 07:28:23 awacs kernel: CPU: 0
> Nov 25 07:28:23 awacs kernel: EIP: 0010:[xfs_inactive_free_eofblocks+615/720]
> Nov 25 07:28:23 awacs kernel: EFLAGS: 00010206
> Nov 25 07:28:23 awacs kernel: eax: 0cb73000 ebx: dfecf400 ecx: dfecf400 edx: ce19b830
> Nov 25 07:28:23 awacs kernel: esi: c0042bd8 edi: da742f20 ebp: 00000000 esp: dffe7f2c
> Nov 25 07:28:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 25 07:28:23 awacs kernel: Process kupdated (pid: 6, stackpage=dffe7000)
> Nov 25 07:28:23 awacs kernel: Stack: dfec6c00 00000000 dfec6c44 dffe6650 00000001 dfecf514 00000010 00000001
> Nov 25 07:28:23 awacs kernel: dfecf514 00000000 00000010 00000001 00000000 00000008 00000008 00000040
> Nov 25 07:28:23 awacs kernel: 00000000 00000000 00000000 de64d500 df196f20 00000026 dfaeaa00 00000000
> Nov 25 07:28:23 awacs kernel: Call Trace: [xfs_inactive_free_eofblocks+17/720] [load_msg+176/240] [block_write+1347/1376] [do_remount+122/172] [do_mount+537/740] [kernel_thread+35/48]
> Nov 25 07:28:23 awacs kernel:
> Nov 25 07:28:23 awacs kernel: Code: f7 40 58 ff 01 00 00 75 14 66 83 be 52 01 00 00 00 75 0a 8b
>
> Kernel 2.4.14 + XFS 1.0.2:
>
> Nov 26 04:16:23 awacs kernel: Unable to handle kernel paging request at virtual address ff689108
> Nov 26 04:16:23 awacs kernel: printing eip:
> Nov 26 04:16:23 awacs kernel: c01c5955
> Nov 26 04:16:23 awacs kernel: *pde = 00000000
> Nov 26 04:16:23 awacs kernel: Oops: 0000
> Nov 26 04:16:23 awacs kernel: CPU: 1
> Nov 26 04:16:23 awacs kernel: EIP: 0010:[xfs_syncsub+2309/3056] Not tainted
> Nov 26 04:16:23 awacs kernel: EFLAGS: 00010246
> Nov 26 04:16:23 awacs kernel: eax: 00000000 ebx: 00000000 ecx: dffbe914 edx: c490bbd8
> Nov 26 04:16:23 awacs kernel: esi: ff689100 edi: c84ab740 ebp: c03c4760 esp: c1955f24
> Nov 26 04:16:23 awacs kernel: ds: 0018 es: 0018 ss: 0018
> Nov 26 04:16:23 awacs kernel: Process kupdated (pid: 7, stackpage=c1955000)
> Nov 26 04:16:23 awacs kernel: Stack: dffbe914 00000001 00000001 00000000 00000001 00000008 00000008 00000040
> Nov 26 04:16:23 awacs kernel: 00000000 00000000 00000000 dd2bda00 c79a91a0 c197bfac c0114539 c1955f9c
> Nov 26 04:16:23 awacs kernel: de302f40 dbde0000 0000001a 00000046 00000286 00000001 00000286 00000003
> Nov 26 04:16:23 awacs kernel: Call Trace: [schedule+969/1504] [xfs_sync+21/32] [linvfs_write_super+42/48] [sync_supers+199/256] [sync_old_buffers+44/128]
> Nov 26 04:16:23 awacs kernel: [kupdate+317/336] [_stext+0/64] [kernel_thread+38/48] [kupdate+0/336]
> Nov 26 04:16:23 awacs kernel:
> Nov 26 04:16:23 awacs kernel: Code: 39 56 08 0f 85 22 f8 ff ff 8b 44 24 78 05 14 01 00 00 50 e8
> -
next prev parent reply other threads:[~2001-11-28 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000701c177e6$7317af40$ea9133d5@groni1.gr.nl.home.com>
2001-11-28 14:57 ` XFS Oopses with 2.4.5 and 2.4.14? Pascal Haakmat
2001-11-28 15:29 ` Juergen Sauer
2001-11-28 16:05 ` Peter Wächtler [this message]
2001-11-28 15:29 Elgar, Jeremy
[not found] <fa.ih0gaiv.iio4rf@ifi.uio.no>
[not found] ` <fa.ge28glv.66a6b8@ifi.uio.no>
2001-11-28 15:48 ` Eric Sandeen
2001-11-28 16:31 ` Pascal Haakmat
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=3C050B55.A3F3129B@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=a.haakmat@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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.