From owner-freebsd-stable  Thu Oct  7 17:18:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from wank.necropolis.org (wank.westin16.flyingcroc.net [207.246.128.93])
	by hub.freebsd.org (Postfix) with ESMTP
	id C45E214BB7; Thu,  7 Oct 1999 17:18:44 -0700 (PDT)
	(envelope-from todd@flyingcroc.net)
Received: from localhost (todd@localhost)
	by wank.necropolis.org (8.9.3/8.9.3) with ESMTP id RAA95413;
	Thu, 7 Oct 1999 17:24:14 -0700 (PDT)
	(envelope-from todd@flyingcroc.net)
X-Authentication-Warning: wank.necropolis.org: todd owned process doing -bs
Date: Thu, 7 Oct 1999 17:24:14 -0700 (PDT)
From: Todd Backman <todd@flyingcroc.net>
X-Sender: todd@wank.necropolis.org
To: Stevan Arychuk <sa-list@avantgo.com>
Cc: FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG
Subject: Re: SMP + fxp0 wierdness
In-Reply-To: <37FD3391.1F84611A@avantgo.com>
Message-ID: <Pine.BSF.4.10.9910071722010.93506-100000@wank.necropolis.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


We run about 50 machines with a similar setup (asus p2bd mb) all of which
run quite well. We have NMBCLUSERS=30720 though...

- Todd

On Thu, 7 Oct 1999, Stevan Arychuk wrote:

> Greetings,
> 
> We're running 3.3-REL on dual processor PII-450's, with a N440BX
> motherboard, using the onboard EtherExpress Pro (fxp) NIC and 512MB RAM.
> 
> These machines are running custom software that excercises the disk, CPU
> and network quite heavily.  The SMP machines seem to have both "fxp0:
> device timeout" problems, and spontaneous reboots.  We were uable to get
> a working savecore until now, and have traced the reboots back to the
> fxp driver as well.  Here are the debug outputs, and any custom changes
> to our kernel config.
> 
> Could this be a problem with SMP + fxp combination?  Any other thoughts
> or ideas?  
> 
> We've serached, and read, and searched all the FAQ's for both of these
> problems, and have pretty well come up empty.  Suggestions for the next
> course of action?
> 
> Thanks in advance for anyones help.
> 
> Regards,
> 
> Stevan Arychuk
> AvantGo Inc.
> stevan@avantgo.com
> 
> 
> --- gdb output ---
> 
> IdlePTD 2641920
> initial pcb at 21d290
> panicstr: page fault
> panic messages:
> ---
> Fatal trap 12: page fault while in kernel mode
> mp_lock = 00000002; cpuid = 0; lapic.id = 01000000
> fault virtual address   = 0x293a84d4
> fault code              = supervisor write, page not present
> instruction pointer     = 0x8:0xc018979e
> stack pointer           = 0x10:0xff804f78
> frame pointer           = 0x10:0xff804f88
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = Idle
> interrupt mask          = net  <- SMP: XXX
> trap number             = 12
> panic: page fault
> mp_lock = 00000002; cpuid = 0; lapic.id = 01000000
> boot() called on cpu#0
> 
> syncing disks... 200 190 169 149 106 37 1 1 1 1 1 1 1 1 1 1 1 1 1 1
> giving up
> 
> dumping to dev 20401, offset 524288
> dump 256 255 254 253 ...<clip> ...1 
> 
> #0  0xc013d473 in boot ()
> (kgdb) bt
> #0  0xc013d473 in boot ()
> #1  0xc013d741 in panic ()
> #2  0xc01ce080 in trap_fatal ()
> #3  0xc01cdcfb in trap_pfault ()
> #4  0xc01cd95a in trap ()
> #5  0xc018979e in fxp_add_rfabuf ()
> #6  0xc0188af5 in fxp_intr ()
> 
> --- Instruction pointer trace ---
> 
> freebsd# nm /kernel |grep c01897 
> c01897e0 t fxp_mdi_read
> 
> --- Kernel Config ---
> 
> Everything is generic except for:
> 
> maxusers        512
> options         NMBCLUSTERS=33280
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message