[OpenAFS-devel] [Hein Roehrig <hein@acm.org>] Bug#88851: oops with openafs-client
Sam Hartman
hartmans@mit.edu, 88851-quiet@bugs.debian.org
07 Mar 2001 17:02:10 -0500
The Debian packages do not contain any changes that should matter for
the kernel. Advice for attempting to debug appreciated.
------- Start of forwarded message -------
Subject: Bug#88851: oops with openafs-client
Reply-To: Hein Roehrig <hein@acm.org>, 88851@bugs.debian.org
Resent-From: Hein Roehrig <hein@acm.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Sam Hartman <hartmans@debian.org>
Resent-Date: Wed, 07 Mar 2001 17:33:02 GMT
Resent-Message-ID: <handler.88851.B.9839855904429@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
From: Hein Roehrig <hein@acm.org>
To: submit@bugs.debian.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 07 Mar 2001 18:19:40 +0100
Message-Id: <E14ahbC-0001RL-00@godot.normed.de>
Package: openafs-client
Version: 1.0.2-3
I can reproducibly create kernel oopses by rsyncing large amounts of
data (my homedirectory) into AFS. The oopses always start like
Mar 7 18:14:16 giek kernel: Bad refCount 0 on inode 0xd1b5a86c
Mar 7 18:14:16 giek kernel: printing eip:
Mar 7 18:14:16 giek kernel: d1a2677d
My /var/cache/openafs has its own 500MB ext2 file system and the cache
is configured to use 200MB. Forcing fsck on that filesystem does not
yield any problem. Purging /var/cache/openafs does not affect the
error. The systme is running a self-compiled SMP 2.4.2 kernel with the
appropriate openafs-modules built from openafs-modules-source. Here is
a typical ksymoops output:
ksymoops 2.3.7 on i686 2.4.2. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.2/ (default)
-m /boot/System.map-2.4.2 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Mar 7 18:14:16 giek kernel: d1a2677d
Mar 7 18:14:16 giek kernel: Oops: 0002
Mar 7 18:14:16 giek kernel: CPU: 1
Mar 7 18:14:16 giek kernel: EIP: 0010:[mga:mga_res_ctx+1262173/86211002]
Mar 7 18:14:16 giek kernel: EFLAGS: 00010286
Mar 7 18:14:16 giek kernel: eax: 00000023 ebx: d1b5a86c ecx: 0000001f edx: 00000002
Mar 7 18:14:16 giek kernel: esi: c8a9f440 edi: d1b5a86c ebp: 00000001 esp: ca8d5eb0
Mar 7 18:14:16 giek kernel: ds: 0018 es: 0018 ss: 0018
Mar 7 18:14:16 giek kernel: Process rsync (pid: 373, stackpage=ca8d5000)
Mar 7 18:14:16 giek kernel: Stack: d1a48ea0 00000000 d1b5a86c d1a32e5b 3a9299cb 0000000a 3a9299cb d1a32fcf
Mar 7 18:14:16 giek kernel: d1a48ea0 00000000 d1b5a86c d1a32e5b c8a9f460 c8a9f440 c8a9f4c0 c0145989
Mar 7 18:14:16 giek kernel: c8a9f440 c02555d8 c8a9f440 c0145d80 c8a9f440 d1b5a86c c8a9f7c0 00000000
Mar 7 18:14:16 giek kernel: Call Trace: [mga:mga_res_ctx+1403264/86069911] [mga:mga_res_ctx+2523980/84949195] [mga:mga_res_ctx+1313083/86160092] [mga:mga_res_ctx+1313455/86159720] [mga:mga_res_ctx+1403264/86069911] [mga:mga_res_ctx+2523980/84949195] [mga:mga_res_ctx+1313083/86160092]
Mar 7 18:14:16 giek kernel: Code: c6 05 ff ff ff ff 2a 83 c4 10 83 c4 0c c3 90 55 57 56 53 8b
Using defaults from ksymoops -t elf32-i386 -a i386
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: c6 05 ff ff ff ff 2a movb $0x2a,0xffffffff
Code; 00000007 Before first symbol
7: 83 c4 10 add $0x10,%esp
Code; 0000000a Before first symbol
a: 83 c4 0c add $0xc,%esp
Code; 0000000d Before first symbol
d: c3 ret
Code; 0000000e Before first symbol
e: 90 nop
Code; 0000000f Before first symbol
f: 55 push %ebp
Code; 00000010 Before first symbol
10: 57 push %edi
Code; 00000011 Before first symbol
11: 56 push %esi
Code; 00000012 Before first symbol
12: 53 push %ebx
Code; 00000013 Before first symbol
13: 8b 00 mov (%eax),%eax
1 warning issued. Results may not be reliable.
------- End of forwarded message -------