Date: Mon, 10 Apr 2000 07:35:05 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Chris Wasser <cwasser@v-wave.com> Cc: questions@FreeBSD.org Subject: Re: Fwd: Major AMD K7 Problems under 4.0-S Message-ID: <17955.955344905@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 09 Apr 2000 22:02:40 MDT." <20000409220240.A54143@area51.v-wave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Chris, It looks to me like you have APM enabled in your BIOS, please try to disable that. Poul-Henning In message <20000409220240.A54143@area51.v-wave.com>, Chris Wasser writes: >Oops, got warnings about excessive cross postings, sorry. Re-sending just >incase it didn't make it to the list. > >----- Forwarded message from Chris Wasser <cwasser@v-wave.com> ----- > >Date: Sun, 9 Apr 2000 21:52:55 -0600 >From: Chris Wasser <cwasser@v-wave.com> >To: questions@FreeBSD.ORG >Cc: bugs@FreeBSD.ORG, hardware@FreeBSD.ORG >Subject: Major AMD K7 Problems under 4.0-S >X-Mailer: Mutt 1.0.1i > >I'm sure this has been hashed over and over countless times, but I can't >seem to resolve this problem locally and figured I'd shoot it out to the >mailing list here and see if anyone has any ideas. This machine is having >critical problems preventing it from being put into production and I'd >_really_ appriciate any information/insight/ideas people can shoot over to >me to try. > >Please respond on questions/bugs@FreeBSD.ORG or via email to the above >address (not subscribed to freebsd-hardware) > >Please note, I have an identical AMD K7-700 system running, the only >difference is it has a ASUS K7M motherboard and 3c905B-TX nics and a >Mach64-GB AGP video card. It does not exibit this behavior. It uses the >AMD-751 and VIA 82C686 chipset. > >Here's the system: > >AMD K7-700 (0.18fab) running @ 700MHz (100x7.0) >256MB PC133 (Running @ 100MHz) >1 3Com 3c905C-TX connected @ 10Base-T to a cablemodem (xl0) >1 3Com 3c905C-TX connected @ 100Base-T full-duplex to LAN (xl1) >EpoX 7KXA motherboard (VIA KX133 chipset/82C686) >2 x Quantum KX 20GB ATA-66 (running @ ATA-66) >ASUS 50x ATA-33 IDE CDROM >ATI Rage 128-RF AGP running @ AGP2x >300W power supply > >The system and kernel were cvsup'd and built on March 30th/2000 from >stock 4.0-RELEASE .. xl0 was enabled but there was no active connection >during this test. The only active card w/link was xl1 @ 100Base-T >full-duplex (switched). > >The actual time and my date below for the dmesg output is inaccurate >(forgot to set the system date & time in the bios, nothing major.), it >was re-compiled today [not cvsup'd, just recompiled the kernel when I >added new options, the source on the system is from March30th, the only >change I made to the actual source tree was from PR17831 which I submitted >a few days ago.] (April 9th) > >When doing file xfers on the local lan (xl1) the system will eventually >produce error messages up microuptime() going backwards: > >microuptime() went backwards (3821.740589 -> 3821,720223) >microuptime() went backwards (3821.774554 -> 3821,731215) >..etc etc > >I had to terminate syslogd because it was spending so much time logging >that it was dragging down the system when the microuptime() messages >started appearing (choppy keyboard response over ssh and locally at >console and the load avg was a solid 2.01 across the board) > >This happens under heavy network load (transferring +7GB files over the >local LAN) and processes start showing negative run times or completely >outrageous run time: > >root 0 0.0 0.0 0 0 ?? DLs 10:19AM 11:36.96 (swapper) >root 5 0.0 0.0 0 0 ?? DL 10:19AM 359:53.83 (syncer) >root 2 0.0 0.0 0 0 ?? DL 10:19AM 11:48.00 (pagedaemon) > >I set sysctl to use accurate time measurements thinking that might provide >a solution (after cruising through older mailing list archives and made >no difference): > >kern.timecounter.method: 1 >kern.timecounter.hardware: i8254 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?17955.955344905>