* 2.4.17smp kernel oops in nfs client
@ 2002-01-19 18:18 Steinar Hauan
2002-01-20 18:17 ` Trond Myklebust
0 siblings, 1 reply; 3+ messages in thread
From: Steinar Hauan @ 2002-01-19 18:18 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: TEXT/PLAIN, Size: 400 bytes --]
hello,
log monitoring revealed that a user processed crashed a few days
ago and left an ooops message along with a zombie user process
(in non-interruptible disk wait).
the machine was still running fine with +2 extra load.
ksymoops output attached along with other details.
regards,
--
Steinar Hauan, dept of ChemE -- hauan@cmu.edu
Carnegie Mellon University, Pittsburgh PA, USA
[-- Attachment #2: Type: TEXT/PLAIN, Size: 2967 bytes --]
ksymoops 2.4.3 on i686 2.4.17. Options used
-v /beowulf/install/kernel/linux-2.4.17-node-p6-apollo-pro/vmlinux (specified)
-k ksyms (specified)
-l /proc/modules (default)
-o /lib/modules/2.4.17/ (default)
-m /boot/System.map-2.4.17 (default)
Jan 16 14:26:19 c1n04 kernel: invalid operand: 0000
Jan 16 14:26:19 c1n04 kernel: CPU: 1
Jan 16 14:26:19 c1n04 kernel: EIP: 0010:[clear_inode+25/160] Not tainted
Jan 16 14:26:19 c1n04 kernel: EIP: 0010:[<c0148c89>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Jan 16 14:26:19 c1n04 kernel: EFLAGS: 00010202
Jan 16 14:26:19 c1n04 kernel: eax: 00000001 ebx: e0ff2060 ecx: e0ff2080 edx: e0ff2060
Jan 16 14:26:19 c1n04 kernel: esi: f895f320 edi: f896e880 ebp: 00000000 esp: f3ee7ee4
Jan 16 14:26:19 c1n04 kernel: ds: 0018 es: 0018 ss: 0018
Jan 16 14:26:19 c1n04 kernel: Process rm (pid: 14338, stackpage=f3ee7000)
Jan 16 14:26:19 c1n04 kernel: Stack: f7964200 f896e880 00000000 c0149651 e0ff2060 c014966a e0ff2060 e296ee20
Jan 16 14:26:19 c1n04 kernel: e0ff2060 e0ff2ba0 c0147ad6 e0ff2060 e0ff2060 3c45d3da e0ff2ba0 e0ff2060
Jan 16 14:26:19 c1n04 kernel: e296ee20 e0ff2060 e296ee20 f895e2ba e296ee20 00000001 e0ff2ba0 e296ee20
Jan 16 14:26:19 c1n04 kernel: Call Trace: [<f896e880>] [iput+177/464] [iput+202/464] [d_delete+86/176] [<f895e2ba>]
Jan 16 14:26:19 c1n04 kernel: Call Trace: [<f896e880>] [<c0149651>] [<c014966a>] [<c0147ad6>] [<f895e2ba>]
Jan 16 14:26:19 c1n04 kernel: [<f895e327>] [vfs_unlink+281/368] [lookup_hash+70/192] [sys_unlink+154/256] [system_call+51/56]
Jan 16 14:26:19 c1n04 kernel: [<f895e327>] [<c0140c19>] [<c013fb86>] [<c0140d0a>] [<c0106f1b>]
Jan 16 14:26:19 c1n04 kernel: Code: 0f 0b 8b 83 08 01 00 00 a9 10 00 00 00 75 02 0f 0b a9 20 00
>>EIP; c0148c88 <clear_inode+18/a0> <=====
Trace; f896e880 <[nfs]nfs_sops+0/60>
Trace; f896e880 <[nfs]nfs_sops+0/60>
Trace; c0149650 <iput+b0/1d0>
Trace; c014966a <iput+ca/1d0>
Trace; c0147ad6 <d_delete+56/b0>
Trace; f895e2ba <[nfs]nfs_safe_remove+11a/140>
Trace; f895e326 <[nfs]nfs_unlink+46/60>
Trace; f895e326 <[nfs]nfs_unlink+46/60>
Trace; c0140c18 <vfs_unlink+118/170>
Trace; c013fb86 <lookup_hash+46/c0>
Trace; c0140d0a <sys_unlink+9a/100>
Trace; c0106f1a <system_call+32/38>
Code; c0148c88 <clear_inode+18/a0>
00000000 <_EIP>:
Code; c0148c88 <clear_inode+18/a0> <=====
0: 0f 0b ud2a <=====
Code; c0148c8a <clear_inode+1a/a0>
2: 8b 83 08 01 00 00 mov 0x108(%ebx),%eax
Code; c0148c90 <clear_inode+20/a0>
8: a9 10 00 00 00 test $0x10,%eax
Code; c0148c94 <clear_inode+24/a0>
d: 75 02 jne 11 <_EIP+0x11> c0148c98 <clear_inode+28/a0>
Code; c0148c96 <clear_inode+26/a0>
f: 0f 0b ud2a
Code; c0148c98 <clear_inode+28/a0>
11: a9 20 00 00 00 test $0x20,%eax
[-- Attachment #3: Type: TEXT/PLAIN, Size: 258 bytes --]
nfs 73692 2 (autoclean)
nfsd 67488 8 (autoclean)
lockd 47808 1 (autoclean) [nfs nfsd]
sunrpc 64500 1 (autoclean) [nfs nfsd lockd]
autofs4 8548 2 (autoclean)
[-- Attachment #4: Type: TEXT/PLAIN, Size: 631 bytes --]
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux c1n04 2.4.17 #1 SMP Wed Dec 26 11:56:55 EST 2001 i686 unknown
Gnu C 2.96
Gnu make 3.79.1
util-linux 2.11f
mount 2.11g
modutils 2.4.12
e2fsprogs 1.25
Linux C Library 2.2.4
Dynamic linker (ldd) 2.2.4
Procps 2.0.7
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded nfs nfsd lockd sunrpc autofs4
[-- Attachment #5: Type: TEXT/PLAIN, Size: 3886 bytes --]
00:00.0 Host bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266] (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 8
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=16M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0a.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 (rev 0b) (prog-if 00 [VGA])
Subsystem: Silicon Integrated Systems [SiS] SiS6326 GUI Accelerator
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d2000000 (32-bit, prefetchable) [size=8M]
Region 1: Memory at d2800000 (32-bit, non-prefetchable) [size=64K]
Region 2: I/O ports at d000 [size=128]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at d400 [size=256]
Region 1: Memory at d2810000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at d800 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
[-- Attachment #6: Type: TEXT/PLAIN, Size: 804 bytes --]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 6
cpu MHz : 1011.230
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 2018.50
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 6
cpu MHz : 1011.230
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 2018.50
[-- Attachment #7: Type: TEXT/PLAIN, Size: 125 bytes --]
Linux version 2.4.17 (root@fs) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-101)) #1 SMP Wed Dec 26 11:56:55 EST 2001
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: 2.4.17smp kernel oops in nfs client
2002-01-19 18:18 2.4.17smp kernel oops in nfs client Steinar Hauan
@ 2002-01-20 18:17 ` Trond Myklebust
2002-01-21 14:26 ` Steinar Hauan
0 siblings, 1 reply; 3+ messages in thread
From: Trond Myklebust @ 2002-01-20 18:17 UTC (permalink / raw)
To: Steinar Hauan; +Cc: linux-kernel
>>>>> " " == Steinar Hauan <hauan@cmu.edu> writes:
> hello,
> log monitoring revealed that a user processed crashed a few
> days ago and left an ooops message along with a zombie user
> process (in non-interruptible disk wait).
Hi,
Did you find any other NFS related messages in your syslog? Short of
a bug in truncate_inode_pages(), I really can't see how this could
happen. Certainly whatever is was should at least have triggered a
couple of NFS warnings...
Cheers,
Trond
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: 2.4.17smp kernel oops in nfs client
2002-01-20 18:17 ` Trond Myklebust
@ 2002-01-21 14:26 ` Steinar Hauan
0 siblings, 0 replies; 3+ messages in thread
From: Steinar Hauan @ 2002-01-21 14:26 UTC (permalink / raw)
To: Trond Myklebust; +Cc: linux-kernel
On 20 Jan 2002, Trond Myklebust wrote:
> >>>>> " " == Steinar Hauan <hauan@cmu.edu> writes:
>
> > hello,
> > log monitoring revealed that a user processed crashed a few
> > days ago and left an ooops message along with a zombie user
> > process (in non-interruptible disk wait).
>
> Did you find any other NFS related messages in your syslog? Short of
> a bug in truncate_inode_pages(), I really can't see how this could
> happen. Certainly whatever is was should at least have triggered a
> couple of NFS warnings...
there are no nfs error or warning messages at all on either the server
or the client for one week prior to the crash. this includes logs created
by kern.* and *.debug entries in syslog.conf.
regards,
--
Steinar Hauan, dept of ChemE -- hauan@cmu.edu
Carnegie Mellon University, Pittsburgh PA, USA
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-01-21 14:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-19 18:18 2.4.17smp kernel oops in nfs client Steinar Hauan
2002-01-20 18:17 ` Trond Myklebust
2002-01-21 14:26 ` Steinar Hauan
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®