From: Gregor Jasny <gjasny@wh8.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: Oops at NFS unmounting
Date: Thu, 14 Jun 2001 19:12:52 +0200 [thread overview]
Message-ID: <01061419125200.01840@backfire> (raw)
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
Hi *!
I got this Oops at unmounting a already renamed NFS source.
The umount got a SEGFAULT.
I compiled my 2.4.5 with 2.95.4 20010319 (Debian prerelease).
Regards,
-Gregor
[-- Attachment #2: oops.txt --]
[-- Type: text/plain, Size: 3006 bytes --]
ksymoops 2.4.1 on i686 2.4.5. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.5/ (default)
-m /boot/System.map-2.4.5 (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.
Warning (compare_maps): snd symbol pm_register not found in /usr/lib/alsa-modules/2.4.5/0.5/snd.o. Ignoring /usr/lib/alsa-modules/2.4.5/0.5/snd.o entry
Warning (compare_maps): snd symbol pm_send not found in /usr/lib/alsa-modules/2.4.5/0.5/snd.o. Ignoring /usr/lib/alsa-modules/2.4.5/0.5/snd.o entry
Warning (compare_maps): snd symbol pm_unregister not found in /usr/lib/alsa-modules/2.4.5/0.5/snd.o. Ignoring /usr/lib/alsa-modules/2.4.5/0.5/snd.o entry
WARNING: USB Mass Storage data integrity not assured
kernel BUG at inode.c:486!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c013f9bb>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 0000001b ebx: dd3df820 ecx: d9406000 edx: ddd3e560
esi: c022f280 edi: c022f280 ebp: 08054008 esp: d9407f04
ds: 0018 es: 0018 ss: 0018
Process umount (pid: 1551, stackpage=d9407000)
Stack: c01f79ac c01f7a0b 000001e6 dd3df820 c0140387 dd3df820 c326a7c0 dd3df820
c015399a dd3df820 c013df96 c326a7c0 dd3df820 de260c00 c326a7c0 c013227c
c326a7c0 c326a7c0 c3264e20 de260c00 c022e040 08054008 de260c34 c022f30c
Call Trace: [<c0140387>] [<c015399a>] [<c013df96>] [<c013227c>] [<c01316d4>] [<c0136baf>] [<c01326a8>]
[<c01326e0>] [<c0106a7b>] [<c010002b>]
Code: 0f 0b 83 c4 0c f6 83 f4 00 00 00 10 75 19 68 e8 01 00 00 68
>>EIP; c013f9bb <clear_inode+33/f4> <=====
Trace; c0140387 <iput+137/14c>
Trace; c015399a <nfs_dentry_iput+22/28>
Trace; c013df96 <dput+d6/144>
Trace; c013227c <kill_super+64/12c>
Trace; c01316d4 <__mntput+3c/44>
Trace; c0136baf <path_release+27/2c>
Trace; c01326a8 <sys_umount+c0/ec>
Trace; c01326e0 <sys_oldumount+c/10>
Trace; c0106a7b <system_call+33/38>
Trace; c010002b <startup_32+2b/a5>
Code; c013f9bb <clear_inode+33/f4>
00000000 <_EIP>:
Code; c013f9bb <clear_inode+33/f4> <=====
0: 0f 0b ud2a <=====
Code; c013f9bd <clear_inode+35/f4>
2: 83 c4 0c add $0xc,%esp
Code; c013f9c0 <clear_inode+38/f4>
5: f6 83 f4 00 00 00 10 testb $0x10,0xf4(%ebx)
Code; c013f9c7 <clear_inode+3f/f4>
c: 75 19 jne 27 <_EIP+0x27> c013f9e2 <clear_inode+5a/f4>
Code; c013f9c9 <clear_inode+41/f4>
e: 68 e8 01 00 00 push $0x1e8
Code; c013f9ce <clear_inode+46/f4>
13: 68 00 00 00 00 push $0x0
4 warnings issued. Results may not be reliable.
reply other threads:[~2001-06-14 17:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01061419125200.01840@backfire \
--to=gjasny@wh8.tu-dresden.de \
--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 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.