Linux-kernel mailing list archive 2000-23,: Unstable Server kernel 2.2.14 and NFS

# Unstable Server kernel 2.2.14 and NFS

Deven.Phillips@webmail.hnl.viata.com, CISSP (Deven.Phillips@webmail.hnl.viata.com,)
Mon, 5 Jun 2000 20:41:48 -0000

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Tigran Aivazian: "[2.4.0-test1-ac8] es1371+bttv mystery."
- Previous message: Ward Vandewege: "Re: RFC Maestro-3i"
- Next in thread: Dominik Kubla: "Re: Unstable Server kernel 2.2.14 and NFS"
- Reply: Dominik Kubla: "Re: Unstable Server kernel 2.2.14 and NFS"
- Reply: Marcelo Tosatti: "Re: Unstable Server kernel 2.2.14 and NFS"

To Whom it may concern,

We run a homogeneous Linux network, currently two servers, 1 router, 45
workstations. We run our /home off of a Linux NFS server with the following
specs:

SuperMicro PIIIDME M/B
Dual PIII 550MHz
1GB ECC PC100 SDRAM
1 Adaptec 29160 ULTRA160 Controller
1 AMI MegaRAID controller
1 System Drive - IBM 7200RPM SCSI2 on Adaptec Card
4 Data Drives - RAID5 on the MegaRAID
1 Davicom 10/100 Ethernet Card
1 Matrox G400 32MB Video Card
1 Plextor 8x20 CD-R

I am running Mandrake 7.0 w/ kernel 2.2.14

Services on this server:
NFS
Sendmail
YPServ
YPPasswdd
IMAP
Samba

Problem Description:

At unpredictable intervals the server crashes without warning. Usually the
load on the server is minimal. Most of the time, I get no information in the
system logs. The most recent crash actually made me happy in that it spit out
the following Stack Trace.

<BEGIN STACK TRACE>
Unable to handle kernel NULL pointer dereference at virtual address 00000018
current->tss.cr3=00101000,cr3=00101000
*pde = 00000000
Oops: 0000
CPU: 1
EIP: 0010:[<01145a0>]
EFLAGS: 00010207
eax: 00000000 ebx: c0258000 ecx: cfa18000 edx: 00000000 esi: fbfa4000
edp: fbfa5f80 esp: fbfa5f60 ds: 0018 es: 018 ss: 0018
Process swapper (pid:0, process nr: 1, stackpage = fbfa5000)
Stack:
00000000 00000000 00000000 00000080 00000018 00000004 00000001 c0273c20
00000000 c0108814 00000000 00000000 00000000 00000000 00000000 00000000
00000018 c025fb27 00000000 c025fb14 00000010 00000246 00000000 00000000
Call Trace:
[<00000000>][<00000000>][<00000000>][<00000080>]
[<00000018>][<00000004>][<00000001>][<00000000>]

[<00000000>][<c0108814>][<00000000>][<00000000>]
[<00000000>][<00000000>][<00000000>][<00000000>]

[<00000018>][<00000000>][<00000010>][<00000246>]
[<00000000>][<00000000>][<00000000>][<c10b0b87>]

[<00000282>][<00000001>][<00000001>][<00000010>]
[<00000000>][<000001ff>][<00000000>][<00000282>]

CODE: 8b 42 18 c1 f8 01 03 42 1c 89 42 18 8b 52 34 81 fa 00 80 25

Kernel Panic: Attempted to kill the idle task!
Uanble to handle kernel NULL pointer dereference.
<END STACK TRACE>

Is this a hardware issue, or am I running come conflicting services, or
what???

Any help in making our file server more stable is very appriciated.

    --
    Security Officer
    Viata Online, Inc.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Tigran Aivazian: "[2.4.0-test1-ac8] es1371+bttv mystery."
- Previous message: Ward Vandewege: "Re: RFC Maestro-3i"
- Next in thread: Dominik Kubla: "Re: Unstable Server kernel 2.2.14 and NFS"
- Reply: Dominik Kubla: "Re: Unstable Server kernel 2.2.14 and NFS"
- Reply: Marcelo Tosatti: "Re: Unstable Server kernel 2.2.14 and NFS"