Date: Tue, 4 May 1999 05:10:02 -0700 (PDT) From: Wham Bang <wham_bang@yahoo.com> To: freebsd-questions@FreeBSD.ORG Cc: Doug White <dwhite@resnet.uoregon.edu> Subject: Re: Crash and burn with 100mbps on 3c905 (3.1-STABLE) Message-ID: <19990504121002.22279.rocketmail@web106.yahoomail.com>
next in thread | raw e-mail | index | archive | help
Hello again,
Still page faulting...
--- Doug White <dwhite@resnet.uoregon.edu> wrote:
> On Mon, 3 May 1999, Wham Bang wrote:
>
> > I have a box I'm trying to set up as a gateway for a few machines.
> > It's got both a 3c509 (ISA) and a 3c905 (PCI) card installed. The
> > 509 is hooked up to a cable modem and the 905 to a 100BaseT hub.
> > [...]
>
> What brand/model of hub?
>
Linksys Etherfast 10/100 Auto-Sensing 5-Port Workgroup Hub
(aka EFAH05W).
> > [...]
> > xl0: autoneg not complete (forcing half-duplex, 10Mbps)
> >
> > (This might not be verbatim, I'm going from memory since I am
> > at work and the machine at home.) This message is odd since
> > (as mentioned above) the LEDs indicate 100mbps...
>
> Then force it.
>
> ifconfig xl0 media 100baseTX
>
When I read it, I thought for sure this would get me around the
problem, but it turns out that even after this, the machine still
page faults and goes down hard, with the exact same error message
(except for ping's PID, of course). :( See below for error message.
> > An "ifconfig -a" after the machine comes up shows the interface
> > is up, but I can't ping the box from another machine, and
> > whenever I try to ping out, I crash and burn with a message
> > that looks roughly like "segfault while in kernel mode (ping)" -
> > and the machine reboots.
>
> Can you grab the actual message? That is a bad bug if it's there.
>
Here it is:
---------------
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x8
fault code = supervisor write, page not present
instruction pointer = 0x8:0xf020188e
stack pointer = 0x10:0xf4508cfc
frame pointer = 0x19:0xf4508d14
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def 32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL=0
current process = 226 (ping)
interrupt mask = net tty
trap number = 12
panic: page fault
-----------------
And here's ifconfig -a output just before:
-----------------
xl0: flags = 8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu1500
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
ether 00:60:97:07:6c:b2
media: 10baseT/UTP <half-duplex> (100baseTX <half-duplex>)
supported media: autoselect 100basetTX <full-duplex> 100baseTX
<half-duplex> 100baseT/UTP 10baseT/UTP <full-duplex> 10baseT/UTP
10baseT/UTP <half-duplex>
------------------
Of course, if I force 100baseTX media, then the ifconfig output
changes accordingly, but the machine still goes down hard.
I'll try to remove the 509 tonight to see if it has anything to
do with it. Maybe I should try 0xff000000 as the netmask too?
I'm grasping at straws... BTW, the machine is and old P66, 64MB
RAM, 1.7GB IDE drive with the whole disk dedicated to FreeBSD.
Does this error message mean anything to the gurus out there?
Your help is greatly appreciated,
===
Wham! <wham_bang@yahoo.com>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990504121002.22279.rocketmail>