Re: fs corruption (ATA / 4.4-REL)
ian j hart writes: > A re-read of your original post reveals it's a k6 450. Touch the CPU > heatsink. If you burn your finger that's the problem :) > > Seriously tho' there were problems with one of the k6 chips, but it's > so long ago I can't remember clearly whether it's the 450. What's the > core voltage printed on the chip, and what's the M/B core voltage set > to. > There should also be a revision number. While you do that I'll see if I > can find the info. If I'm correct there were two versions with different > core voltages - one of which was suspect. Anyone remember this? > > What brand is the mobo, maybe someone else has one. I had very similar problems with a K6-2 450 on an Ax59Pro. The K6-2 was the "original" version, with a 2.4V core voltage. I ended up underclocking the processor to 400MHz, and the problems disappeared. //Raymond. -- Raymond Wiker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
mod times after cvsup
I just cvsup'd RELENG_4_4_0_RELEASE in preparation for buildworld, and I noticed something odd about the modification times of some of the files in /usr/src. And I don't mean the S1G, Dec 1969 bug. % cd /usr/src && ls -ld [A-Z]* -rw-r--r-- 1 root wheel 4735 Sep 5 1999 COPYRIGHT drwxr-xr-x 2 root wheel512 Apr 15 23:23 CVS -rw-r--r-- 1 root wheel 7486 Oct 1 01:28 Makefile -rw-r--r-- 1 root wheel 26977 Sep 14 13:47 Makefile.inc1 -rw-r--r-- 1 root wheel 9761 Aug 27 1999 Makefile.upgrade -rw-r--r-- 1 root wheel 2642 Oct 27 2000 README -rw-r--r-- 1 root wheel 35884 Sep 14 13:46 UPDATING The mtime on Makefile.inc1 is Sept 14, which is correct and matches the time in the RCS Id. But the date on Makefile is Oct 1, the time I cvsup'd. In the CVS repo, the date for the RELENG_4_4_0_RELEASE version of /usr/src/Makefile should be April 25, which I can see from http://www.FreeBSD.org/cgi/cvsweb.cgi/src. Feel free to whack me with a clue stick if I'm off base, but I thought cvsup was supposed to preserve the mtime from the repo. The man page says it does. And there were lots of files dated Oct 1. The contents of the files are correct, so this isn't going to break buildworld or anything, it just surprised and puzzled me. Anyway, I'm running 4.2-Release and I'm getting ready to build 4.4-Release. I ftp'd and installed the new cvsup-16.1e package (nogui binary for those of us without modula-3). My cvsup file: *default host=cvsup16.freebsd.org *default prefix=/usr *default base=/var/cvsup *default delete use-rel-suffix compress src-all release=cvs tag=RELENG_4_4_0_RELEASE As I read the cvsup man page, I shouldn't need (and probably shouldn't use) the "preserve" keyword. I ran the telnet test on cvsup16, and it should be ok: % telnet cvsup16.freebsd.org 5999 Trying 128.143.108.35... Connected to warhammer.mcc.virginia.edu. Escape character is '^]'. OK 16 1 SNAP_16_1d CVSup server ready --Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ipfilter accounting on VLAN
Hello I've notice one strangeness in accounting, produced by ipfilter 3.4.20 on FreeBSD 4.4-STABLE (ipf is built-in on system) Numbers in accounting rules, which applies to VLAN interface (vlan0, vlan1, vlan2, etc) - VLANs have dot1q encapsulation, just get doubled, seems to be that ipf counts packets twice - one time on physical iface, second - on logical. Accounting on physical interfaces works just fine. Any help would be great, please CC: me, I'm not in list -- Michael Vasilenko To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld problems in gnu/usr.bin/perl/perl
See http://people.freebsd.org/~jdp/s1g/ for the complete story. Guilherme Oliveira <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 10/01/2001 08:00 PM To: Brad McNeney <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc: Subject: Re: make buildworld problems in gnu/usr.bin/perl/perl I've had a similar problem with 4.3. Someone in this list resolved my problem updating cvsup to the latest version, rm -rf /usr/src and cvsup'ing again from 0. It was some type of a bug related to files dated with 1 billion seconds (or minutes, don't know). []'s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld problems in gnu/usr.bin/perl/perl
I've had a similar problem with 4.3. Someone in this list resolved my problem updating cvsup to the latest version, rm -rf /usr/src and cvsup'ing again from 0. It was some type of a bug related to files dated with 1 billion seconds (or minutes, don't know). []'s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 127/8 continued
On Fri, Sep 28, 2001 at 02:49:02PM -0700, Gary W. Swearingen wrote: > Both "ifconfig" and "networking" man pages mention "point to point", > but neither gives a clue as to what it might be or that it isn't > supported by the Ethernet drivers (though I guess the later really > belongs in the driver man pages -- a caution would be good though). Have you tried investigating the netgraph subsystem, and ng_ether(4) in particular, perhaps in connection with the mpd-netgraph port? I haven't done it myself, but I'd be surprised if you couldn't use that combination to produce a PPPoE link. It can do just about anything else. I do use mpd-netgraph to run an MS-PPTP VPN link to the office, and it does that nicely. Entirely different issue of course, but I was most impressed with the ng framework when I read about it. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Fwd: Warning: could not send message for past 4 hours]
On 2001.10.01 12:54 Michael Sierchio wrote: > > WTF is this happening? You have a reverse-DNS problem(s) with your e-mail. FreeBSD.org is setup to reject mail that doesn't satisfy reverse-DNS tests. It's an anti-SPAM measure increasingly common on the net. Scream at your ISP to get their DNS configuration fixed--it took mine quite awhile . . . :( -- jmc MacroHard -- the perfection of form over substance, marketing over performance, and greed over design . . . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fs corruption (ATA / 4.4-REL)
Keith Mitchell wrote: > > On Mon, Oct 01, 2001 at 10:51:19PM +0100, ian j hart wrote: > > A re-read of your original post reveals it's a k6 450. Touch the CPU > > heatsink. If you burn your finger that's the problem :) > > Its a K6-2 450. The heatsink is fine (not even remotely warm to the > touch). All the fans are running correctly and the ambiant temp in > the case seems ok. The MB doesn't have the env monitoring stuff so > I don't know the exact temps. > > > Seriously tho' there were problems with one of the k6 chips, but it's > > so long ago I can't remember clearly whether it's the 450. What's the > > core voltage printed on the chip, and what's the M/B core voltage set > > to. > > There should also be a revision number. While you do that I'll see if I > > can find the info. If I'm correct there were two versions with different > > core voltages - one of which was suspect. Anyone remember this? > > I remember something about that. I have the later revision (the one with > the 2.2 core voltage).. I don't know what the version of the chip is. > The stepping is 12. (it would require me to take the heatsink off and > unglue it (from the heatsink compound)). Yeah, I think this is the good one. > > > What brand is the mobo, maybe someone else has one. > > Its an FIC PA-2013. Never seen one of these, sorry. > > I did check the IDE cable. I didn't see any problem with it. I replaced > it with a brand new cable I had in a box and it didn't make any > difference. > > It should be noted, that I have had FreeBSD on this machine before. It > was a while ago (3.2 I believe). But, until now, I haven't done to much > with this system. 3.2 installed fine and I didn't have any corruption > problems. I haven't gotten very far with 4.4 though... Can't get past > compining the stuff in ports. > > -- > Keith Mitchell > Email: [EMAIL PROTECTED] PGP key available upon request Well I'm about out of good advice appart from the usual stuff, which you seem to have covered :( Pull ALL the cards and the LS120 and run from one drive if possible. Beg/borrow/steal an old display card (ISA is good when you're desperate). A bad bus master implementation/duff card could hog the bus. If both drives fail like this you are left with the M/B as prime suspect. This is pretty thin I know. BTW the transfer rate on the Yamaha looks a bit strange. -- ian j hart To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: buildkernel - more
On Sun, Sep 30, 2001 at 07:55:16PM +, Alastair Hogge wrote: > [Sorry for starting this in a new thread, but I lost all my emails] > > Hello, > > In the last episode I had a helpful tip from someone (sorry can't remember > there name :-( ). The tip was to make, make install the kernel from the > kernel directory instead of make buildkernel from /usr/src (the usaul way > right?). Well this tip did help me, I was able to build.install the kernel ( > thank you very much someon). This tip was fo systems that hadn't run > make buildworld (?). I had already done the buildworld thing I just still > got errors. Why? > > Just to go over what I used to do (using 4.4-STABLE): > > cd /usr/src/sys/i386/conf/ > cp GENERIC FREEBIE > ee FREEBIE # change ident from GENERIC to FREEBIE > config FREEBIE > cd ../../compile/FREEBIE > make depend > cd /usr/src > make buildkernel KERNCONF=FREEBIE > > I would then get the errors with ipfilter. > So after the helpfull tip from I would > > # make depend > make > make install > > Now that woked. > I would just like to know why I'm having trouble with my original > way? You have stale files in your object tree. You should always nuke the object tree between source updates, # rm -rf /usr/obj -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dirprefcode on snapshot mfsroot
Then tell me why the author of dirpref code tested his code with "tar -xzf port.tgz" refrer http://www.ptci.ru/gluk/dirpref/old/dirpref.html Tom wrote: > On Tue, 2 Oct 2001, Dennis Berger wrote: > > > Hi, > > today I installed the latest freebsd-stable-4.4-20011001 snapshot from > > stable.freebsd.org. But while extracting the portsdir I was surprised > > that there was no speed up. I checked the newfsversion shipped with the > > snapshot installdisk and realize that this is an old newfs version that > > does not create a filesystem with the new dirpref code. Did somebody > > forgot to implement it into this newfs version ? or to copy it over the > > old one > > The dirpref change never changed how newfs works, just how directories > are located on the disk. Would the dirpref change even speed up an > extract operation? Quite likely not. It might speed reading the > directories once written. > > Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dirprefcode on snapshot mfsroot
On Tue, 2 Oct 2001, Dennis Berger wrote: > Hi, > today I installed the latest freebsd-stable-4.4-20011001 snapshot from > stable.freebsd.org. But while extracting the portsdir I was surprised > that there was no speed up. I checked the newfsversion shipped with the > snapshot installdisk and realize that this is an old newfs version that > does not create a filesystem with the new dirpref code. Did somebody > forgot to implement it into this newfs version ? or to copy it over the > old one The dirpref change never changed how newfs works, just how directories are located on the disk. Would the dirpref change even speed up an extract operation? Quite likely not. It might speed reading the directories once written. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
problems with BusLogic (aka Mylex) BT-948 controller
A while back, I had written about repeated kernel warnings of CCB timeouts on one of my machines. The messages are like these, with varying hex values: Sep 30 03:07:18 lorax /kernel: (da0:bt0:0:0:0): CCB 0xc7830040 - timed out Sep 30 03:07:26 lorax /kernel: (da0:bt0:0:0:0): CCB 0xc7830040 - timed out Sep 30 03:07:26 lorax /kernel: bt0: No longer in timeout This card worked flawlessly under BSD/OS, where Buslogic controllers were the preferred devices. The driver under BSD/OS was extremely well done. Simply installing FreeBSD on this box resulted in these errors. The above errors are repored under a recent kernel/world. FreeBSD lorax.kciLink.com 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 26 10:06:43 EDT 2001 [EMAIL PROTECTED]:/usr/obj/u/lorax1/usr/src/sys/LORAX i386 The dmesg output is below. My query last December resulted in two replies. One person said running a cron job to sync once per minute cleared his problem with a Mylex 958. Another person said to check cables. I recall someone saying that the drive was going bad, but that was directly to me, not the list. http://www.freebsd.org/cgi/getmsg.cgi?fetch=177791+0+/usr/local/www/db/text/2000/freebsd-stable/20001210.freebsd-stable In the archives, I found a query from July 2000 with similar issues with a Mylex 958. There was one response to it (not linked in the archive) that indicated an older BIOS should be used in the card. I have BIOS 5.05R, which is older than the BIOS in the original query. http://www.freebsd.org/cgi/getmsg.cgi?fetch=907153+909002+/usr/local/www/db/text/2000/freebsd-stable/2709.freebsd-stable http://www.freebsd.org/cgi/getmsg.cgi?fetch=1089306+1092247+/usr/local/www/db/text/2000/freebsd-stable/2709.freebsd-stable Also, from December 1997, I found a message regarding older Adaptec controllers getting these errors under load. This person said as far as he can tell it is a driver issue, since the cards work fine with other operating systems, similar to my experience. http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2928+/usr/local/www/db/text/2000/freebsd-stable/2618.freebsd-stable Other than these kernel warnings (and the pause caused by these timeouts) the machine runs just fine. It has never crashed either under BSD/OS nor FreeBSD on its own... Does this seem like a driver issue? I kind of feel like it is as it only happens under heavy load. I get the timeouts on the second drive as well when I pound on it. I don't think both drives are going bad simultaneously... Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Wed Sep 26 10:06:43 EDT 2001 [EMAIL PROTECTED]:/usr/obj/u/lorax1/usr/src/sys/LORAX Timecounter "i8254" frequency 1196664 Hz CPU: Pentium/P54C (199.42-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127860736 (124864K bytes) Preloaded elf kernel "kernel" at 0xc02d4000. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm: found APM BIOS v1.1, connected at v1.1 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 de0: port 0x6000-0x607f mem 0xe080-0xe080007f irq 5 at device 17.0 on pci0 de0: DEC DE500-XA 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:f8:03:1e:19 pci0: at 18.0 irq 9 bt0: port 0x6100-0x6103 mem 0xe0801000-0xe0801fff irq 10 at device 19.0 on pci0 bt0: BT-948 FW Rev. 5.05R Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs sis0: port 0x6200-0x62ff mem 0xe0802000-0xe0802fff irq 11 at device 20.0 on pci0 sis0: Ethernet address: 00:02:e3:15:61:04 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: at iomem 0xc-0xc7fff,0xc8000-0xcbfff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging Waiting 5 seconds for SCSI devices to settle de0: enabling 10baseT port Mounting root from ufs:/dev/da0s1a da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) da1 at bt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfe
