Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Oct 2002 18:39:41 -0700
From:      Adam Weinberger <adam@vectors.cx>
To:        abe <abe@informationwave.net>
Cc:        questions@freebsd.org
Subject:   Re: fatal trap 12, system crashes
Message-ID:  <20021007013941.GF44643@vectors.cx>
In-Reply-To: <20021007013027.GA71902@dipole.informationwave.net>
References:  <20021007011110.GA66840@dipole.informationwave.net> <20021007010931.GE44643@vectors.cx> <20021007013027.GA71902@dipole.informationwave.net>

next in thread | previous in thread | raw e-mail | index | archive | help
please don't forget to cc: the list when replying.

you still haven't told me what is staying static. you're using different
hard drives. are you saying that all of a sudden, no matter what
computer you use, this happens? perhaps an airborne computer virus...

you say that the computer is not working. but yet you've replaced every
single item. including the hard drive. you installed a fresh version of
freebsd on a new drive, and it still crashed. with all other new
hardware. do i have that right?

-Adam


>> (10.06.2002 @ 1830 PST): abe said, in 4.4K: <<
> replaced the drive almost every other time.  it crashes on network activity after ipfw loads
> the rules.  That's why I was able to do an FTP install.  I would guess it's with IPFW... Not
> sure though.
> 
> -abe
> 
> On Sun, Oct 06, 2002 at 06:09:31PM -0700, Adam Weinberger wrote:
> > man... that has got to be the longest line i've ever seen ::). consider
> > an enter key now and again.
> > 
> > you've tested a great many peripherals and environments. what is it that
> > is staying static throughout your tests? the one particular drive with
> > the root dir on it?
> > 
> > i'd install the src distros from the cdrom, and then run mergemaster(8)
> > to see if there's any weird configuration difference.
> > 
> > also, how did you install via ftp if the machine crashes as soon as
> > there's network activity? or is this problem only present after the
> > install process?
> > 
> > -Adam
> > 
> > 
> > >> (10.06.2002 @ 1811 PST): abe said, in 2.8K: <<
> > > 
> > > Hello,
> > > 
> > >     I've got a rather odd issue, but not unique from what I've seen on
> > >     other threads (whose solutions unfortunately did not work).  I
> > >     have had a machine running in a datacenter for 7 months if not
> > >     more without problems, and 1.5 years prior to that without
> > >     problems as well.  The other night, suddenly the machine rebooted
> > >     and came back up with a panic.  This happened immediately after
> > >     rc.firewall was run it appeared.  I spent about 4 hours in the
> > >     datacenter trying to diagnose the issue and had no luck so brought
> > >     the machine home with me that night.  I've been working on it for
> > >     about a week now trying various methods of troubleshooting and
> > >     haven't had any luck.  I also tried to get a backtrace but that's
> > >     not turning out so well either.  It seems even with a debugging
> > >     kernel and the correct options set in rc.conf for dumpdev and
> > >     savecore it will produce no usable output, if any.  /var/crash is
> > >     empty aside from 'minfree'.  With all of that said, as it may be
> > >     obvious already this message is going to be a bit lengthy as I am
> > >     going to try to provide as much detail as possible considering the
> > >     lack of a backtrace.  I have tried several hardware
> > >     configurations, including brand new hardware.  Two different CPUs
> > >     (AMD thunderbird 700 and 750mhz), 7 different memory modules all
> > >     tested via memtest with 12 iterations at least with no errors, 4
> > >     different network cards: 3com 3905b/c, dlink (rtl8129), and a
> > >     netgear.  I have used an abit kt7-raid, asus a7a 266, and another
> > >     abit board.  I have used 4 different hard disks, 2 western
> > >     digitals, both brand new, and 2 maxtors, fairly new.  I have also
> > >     swapped out power supplies, cables, network equipment (switch,
> > >     direct via crossover), etc.  That's an idea of what I've done thus
> > >     far with hardware, and to sum that up we can think of the hardware
> > >     collectively as three different machines.  As far as installation
> > >     media goes, I've tried via FTP and cdrom.  The systems I've used,
> > >     are 4.5-RELEASE, 4.5-RELEASE-p20, 4.6.2-p2.  I've reinstalled
> > >     several times attempting to spot an error in installation or my
> > >     methods.  I've changed my rules for IPFW to very primitive ones to
> > >     test, and had no luck.  The minute after loading them, and then
> > >     attempting to communicate with any type of network service, the
> > >     machine panics. I have a video which is approximately 2 megs in
> > >     size, and a photo of the error and it occuring.  The video is at
> > >     http://dipole.informationwave.net/~abe/crash.mpg, and the photo is
> > >     http://dipole.informationwave.net/~abe/fbsd.jpg.  If anyone has
> > >     any ideas as to what could be causing this, or a solution, that'd
> > >     be great.  Also any other information that would assist in solving
> > >     this issue that I haven't already provided will be given if
> > >     requested.  Any feedback would be greatly appreciated.
> > > 
> > >     Regards,
> > > 
> > > Abe  
> > > 
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe
> > > freebsd-questions" in the body of the message
> > > 
> > >> end of "fatal trap 12, system crashes" from abe <<
> > 
> > 
> > --
> > "Oh good, my dog found the chainsaw."
> >         -Lilo, "Lilo & Stitch"
> > Adam Weinberger
> > adam@vectors.cx
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> 
>> end of "Re: fatal trap 12, system crashes" from abe <<


--
"Oh good, my dog found the chainsaw."
        -Lilo, "Lilo & Stitch"
Adam Weinberger
adam@vectors.cx


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?20021007013941.GF44643>