Date: Mon, 28 Aug 1995 15:44:16 -0500 (CDT) From: Jim Bryant <jbryant@argus.iadfw.net> To: rashid@haven.ios.com (Rashid Karimov.) Cc: freebsd-hackers@freebsd.org Subject: Re: S.O.S -2.1Stable and ASUSP54TP4 Message-ID: <199508282044.PAA16108@argus.iadfw.net> In-Reply-To: <199508281445.KAA13236@haven.ios.com> from "Rashid Karimov." at Aug 28, 95 10:45:34 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply:
> From: "Rashid Karimov." <rashid@haven.ios.com>
> Subject: S.O.S -2.1Stable and ASUSP54TP4
> To: hackers@freebsd.org
> Date: Mon, 28 Aug 1995 10:45:34 -0400 (EDT)
>
> Hi there folx,
>
>
>
>
> After having a lot of problems with different
> motherboards under FreeBSD I've switched to the
> "editor's choice" - ASUS P54TP4 mb.,which was
> recommended here by Jordan :)
> Few problems went away ( like random reboots and
> stuff), but oneremains consistent:
Great motherboard! I've got one running RELEASE w/o problems using the
133MHz iron, 32m, Seagate [Barracuda] and Connor 2 Giggers,
Adaptec 2940-W [PCI], Toshiba 4x CD-ROM [SCSI], Colorado 350 Tape,
IBM 230M M-O, 1.44M and 2.88M floppies, soundblaster-16, siig hi-irq 4-port
ISA async card, 3com 3c5x9 ISA ethernet, and ATI Pro-Graphics Turbo Mach64 PCI
video...
The only problems seem to be that startx won't get the X-server running without
a panic unless you are initially logged in as root, su to root creates the
same panic, and the fact that the boot floppies don't boot period, not even
the level 1 bootstrap... Had to load from the CD in DOG.
> the freaking system loks each and every day and
> I think this is because of .... something related
> to HD activity/driver/adapter/whatever.
>
> The system is P90,Adaptec 2940 PCI _SCSI adapter,
> SMC EtherPower.
>
>
> The symptoms:
>
> system locks at random times w/o any messages at the console/
> log files. Locks means the system becomes unreachable neither
Are you using non-parity memory? As you know, memory errors will not trap
unless you are using parity memory. If you want to use FreeBSD for anything
other than home-use, I strongly suggest parity memory. (Get a warrantee!)
> from the local net nor from the console
> After I hit "reboot" switch, system reboots up to the fsck
> level and it starts complaining that it can't read partition
> information off the second HDD ( Seagate Barracuda 4 Gb) (!).
Are you properly terminated? Is the BIOS termination set on/off as
appropriate?
Another side note, We have many Barracudas that work well, but I have
personally come across three that either went bad or had to be returned
initially.
> If one hits "reboot" again and goes to the Adaptec BIOS and runs
> disk utilities --> media check from there - the BIOS (!) complains
> that it can not talk to the second HD.
>
> The problem goes away _only after powercycling the whole PC.
> I never saw the stuff like this before ... any suggestions ?
> Any bugs in Adaptec BIOSes ? Release numbers ?
>
> I've changed the Adaptecs - just in case... didn't help.
> Will try to do the same with Seagate Barracuda ... never
> had the problem with 'em before though
I have yet to have a problem with Adaptec in either the 1542CF or the 2940W
controllers. The ahc driver seems to detect the wide channel just fine, even
though I haven't got anything connected to it [YET!]...
>
> Everything is fine till you don;t have too much activity going
> on system. Some of the servers I have here run for months w./o
> problems - but they do DNS/WWW/INN stuff.
> As soon as you put 3000- 4000 users on the system - that when
> the shit begins.
>
> Till now _the most stable version is SNAP back from Feb 95.
> It is up for 24 days, runs 4000 account, 50-70 users online.
> Bad things about it :
> no support for 2940,SMC EtherPower and QUOTAs don't work.
>
Just reboot it every few days, and replace sendmail with something newer.
the 0210-SNAP was kinda wierd for me... But then that's with a lot of
activity.
Looking at the lint file, QUOTA still is tagged saying it's problematic...
I haven't played with 'options QUOTA' for months though...
> I don't want to get rid of this perfect test place for FreeBSD
> but I can not stand by PC and wait to reboot it all the time.
> Looks to me that no1 runs the FreeBSD in such complex env. so
I'll take bets on that one... Buy me a beer :)
> I'd like to be able to continue this, but there is always a
> limit :(
>
>
>
>
> Rashid
The best thing I can recommend is to check the cabling and termination on
the drives... is the barracuda on the end of the scsi chain? I can help
you if you don't have the drive termination right on that one [I don't have
docs for the connor jumpers].
Jim
--
All opinions expressed are mine, if you | "I will not be pushed, stamped,
think otherwise, then go jump into turbid | briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner"
jbryant@argus.iadfw.net, Sr. System/Network Admin, Internet America
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508282044.PAA16108>