From owner-freebsd-questions Thu Dec 17 16:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13307 for freebsd-questions-outgoing; Thu, 17 Dec 1998 16:29:59 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mw1.texas.net (mw1.texas.net [206.127.30.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13300 for ; Thu, 17 Dec 1998 16:29:47 -0800 (PST) (envelope-from rsnow@texas.net) Received: from basil.dympna.COM (mnet06-62.sat.texas.net [209.99.48.230]) by mw1.texas.net (2.4/2.4) with ESMTP id SAA14687; Thu, 17 Dec 1998 18:29:37 -0600 (CST) Received: from solo (solo [134.132.228.3]) by basil.dympna.COM (8.9.1/8.8.7) with SMTP id SAA83916; Thu, 17 Dec 1998 18:29:58 -0600 (CST) (envelope-from rsnow@texas.net) Message-ID: <000b01be2a1d$c53733a0$03e48486@dympna.com> From: "Rob Snow" To: , "Brett Stockdale" Cc: Subject: Re: FreeBSD Locks up Date: Thu, 17 Dec 1998 18:31:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett, Are you, by chance, running a PCI NIC (EtherExpress Pro in my case)? If so, try turning off PCI write combining. Had the same problem, that fixed it. PS. Took several days to figure it out, I was sure it was (in about this order) CAM, TCP Stack, SCSI, SAMBA, NFS...... -Rob -----Original Message----- From: David Greenman To: Brett Stockdale Cc: Date: Thursday, December 17, 1998 2:00 PM Subject: Re: FreeBSD Locks up > We have fixed quite a few bugs since 2.2.5; is it possible to upgrade to >2.2.8 and see if the problems persist? > >-DG > >David Greenman >Co-founder/Principal Architect, The FreeBSD Project > >> I just received and installed Freebsd 3.0 on a 75Mhz pentium with 48 >>Meg RAM, a Adaptec 2940 SCSI host adapter and a Seagate 1.1 Gig hard drive >>sda0 (this drive is strickly for win95) and a Seagate 520 Meg hard drive sda1, >>this is set up for freebsd all 520 Meg. after a period of time my system locks >>up, sometimes I get the following message. >> >>da1:ahc0:0:2:0): tagged openings now 64 >>da1:ahc0:0:2:0): tagged openings now 63 >>da1:ahc0:0:2:0): tagged openings now 62 >>da1:ahc0:0:2:0): tagged openings now 61 >> >>and sometimes nothing. At this point I either press the reset button on the >>front of my machine or have to power down in order to get the system up and >>running again. freebsd 2.1.5 will install and run fine with no problem. I >>upgraded to 2.2.5 when I purchased the complete FreeBSD this also gave a >>different lock up. Do you have any ideas you have of what >>the problem is, is there a patch for this yet? >> >> I can reinstall FreeBSD 2.1.5 and let it run for days without locking up. >>This is the 4 set of disks I have brought from Walnut Creek and really would >>like to get this up and running so as to learn more about this system. >> >> Any help would be appreciated >> >> Brett Stockdale >> >> bstockr@concentric.net >> bstockr@netscape.net >> >> >> >> >>____________________________________________________________________ >>More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-questions" in the body of the message > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message