mysql & FreeBSD 4.0 problem
Hello. I have some problem with MySQL & 4.0 If MySQL compile -static on last snapshots (I tried snapshots 2214 & 2313), mysqld don't work correctly. After starting mysqld listen port and don't print errors, but telnet localhost 3306 don't write mysql version (mysqld nothing print :( ) and mysql client can't connect too. Telnet don't break connection while i don't kill mysqld. Mysql dynamicaly compiled work correct (mysqld print version number if connect on it port). On old snapshots (i tried on 2112) and FreeBSD 3.x (i tried 3.4 stable 2125) all work OK. I test it on different computers SMP/non SMP. -- Tolyar. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-current breaks building jpeg shared library
Vallo Kallaste wrote: > Strange, I always thought the -current list is for general issues > related to -current branch and for true kernel hackers exist -hackers. Ok, now you know differently. No problem. :) -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: top %s not correct
Nathan Sheeley writes: > >As of roughly Mon Mar 6 19:37:1 CST 2000 /usr/bin/top doesn't show the >correct (or any) percentage CPU usage. (example below.) A minor issue I >know, just wanted to point it out if its part of a larger issue. > My top is from March 8th and it shows the CPU usage just fine. Something else must be wrong with your installation. Are your kernel and utilities in synch ? --- Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: top %s not correct
I have the similar problem on ASUS P2B-D/P2B-DS (SMP) but not only top %s and on the top without parameters. After starting system top work correctly but after some minutes (~2-5) top write zeros. >From two equal computers only one have this problem. BIOS upgrade was not resolve this problem. On 15-Mar-2000 Nathan Sheeley wrote: > > As of roughly Mon Mar 6 19:37:1 CST 2000 /usr/bin/top doesn't show the > correct (or any) percentage CPU usage. (example below.) A minor issue I > know, just wanted to point it out if its part of a larger issue. > > Since upgrading to -current I've noticed: > o sound now works with my es1371 sb128 pci card, where it didn't no > matter what I tried in 3.4 stable. > o things that allocate? shared memory (Linux CivCTP, wine) now work > when I use a SMP kernel (I have a Abit BP6 w/2 433 Celerons) > o my machine locks up after about 20 hours of uptime. > > Obviously the last one is quite annoying, but I haven't been able to > get any info yet on why the crashes happen (I have a dumpdev now, so > it refuses to crash ;) > > Nate > > last pid: 49105; load averages: 2.06, 1.63, 1.28 > up 1+04:43:59 00:24:42 > 30 processes: 3 running, 27 sleeping > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% > idle > Mem: 51M Active, 7520K Inact, 18M Wired, 760K Cache, 10M Buf, 47M Free > Swap: 256M Total, 1560K Used, 254M Free > > PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND > 49045 nobody30 1 14676K 14340K RUN1 3:18 0.00% 0.00% > setiathome > 49048 nobody30 1 14676K 14340K CPU0 0 3:12 0.00% 0.00% > setiathome > 49070 nsheeley 2 0 49372K 42720K select 1 0:04 0.00% 0.00% > XF86_SVGA > 199 root 10 0 928K 160K nanslp 1 0:01 0.00% 0.00% cron > 160 root 2 0 872K 252K select 1 0:01 0.00% 0.00% syslogd > 49076 nsheeley 10 0 3272K 1984K nanslp 1 0:01 0.00% 0.00% xearth > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Tolyar. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)
On Tue, 14 Mar 2000 11:27:34 CST, Visigoth wrote: > Did anybody get a chance to look at this and decide that it wasn't > the case or was? I was suprised because I didn't hear _anything_ and am > wondering if I was doing something wrong... Sorry, I read your original post, but somehow a reply like the one that follows didn't make it out of my MUA. :-) Please send me an example of what master.passwd lines look like with MD5 passwords look like and I'll have a look at 200.backup-passwd for you. For security's sake, I suggest you create a dummy user for this purpose and remove the user as soon as you've sent me the master.passwd line for it. Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: suggestion: a g77 -> f77 link
David O'Brien wrote: > > NO. I will not apply this link. BSD has always had a "f77" command. It > has not always had a "g77" command. The G77 developers should have > installed a "f77" compatability link. It is their fault this misspelling > is perpitrating forward. All the world is not Gfoo. I agree: all the world is not Gfoo. But my argument is: when GNU C was integrated in FreeBSD, a "gcc" command was added. Once the GNU Fortran compiler has been also integrated, a "g77" command should be added, too. This is ugly, but it's coherent with "gcc" and may avoid some problems for some users. Anyway, I don't want to start a "g77 war" :-) If nobody likes the idea, OK, I'll forget it. I hate Fortran, after all! --I am not a Quiche Eater, however-- ;-) Cheers, -- JMA Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pc98
Just curious, who is or are the current and active maintainers of pc98? -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]> VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl For dust thou art, and unto dust shalt thou return. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pc98
> who is or are the current and active maintainers of pc98? contact to [EMAIL PROTECTED] -- Motomichi Matsuzaki <[EMAIL PROTECTED]> Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: top %s not correct
on Ons, Mar 15, 2000 at 12:29:29pm +0300, Zherdev Anatoly wrote: > > I have the similar problem on ASUS P2B-D/P2B-DS (SMP) but not only top %s > and on the top without parameters. After starting system top work correctly > but after some minutes (~2-5) top write zeros. > > >From two equal computers only one have this problem. BIOS upgrade was not > resolve this problem. This is a known problem with some ASUS SMP boards. The fix is to use the following in your kernel config file: device apm0at nexus? flags 0x20 instead of the default. -- Anders Andersson[EMAIL PROTECTED] Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
Please leave the wd driver for those who cannot use the ATA driver. At least until the ATA driver gets support for more older disks. I cant be the only person using an old 80 MB IDE drive as / with another drive as /usr (a 400 MB SCSI). I haven't tried for a couple of months but the ATA driver didn't work over several different world builds back then and I haven't seen commits to indicate it will work now. dmesg from a less than a week old -CURRENT says the disk is: wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 77MB (158440 sectors), 932 cyls, 10 heads, 17 S/T, 512 B/S wdc0: driver is using old-style compatability shims Lots of people may say "buy new hardware" but the fact is that my 486DX4-100 with these crappy old disks does extremely well as my user-mode ppp connection to the net using NAT. It also runs a DHCP server, Squid proxy server, name server, and IMAP server very nicely. I also have no money for my FreeBSD hobby. Some of you will say "stick with 4.0-RELEASE or earlier" and thats what I'll have to do if wd goes but I do prefer to keep all 3 of my machines running -CURRENT so I can easily recover from bad -CURRENT experiences by grabbing binaries from another machine etc... (Of course I build world on the Celeron 300a and install it on the others). On Tue, 14 Mar 2000, Soren Schmidt wrote: > It seems Bruce Evans wrote: > > On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote: > > > > > Yes... > > > > > > That's right. > > > > > > Use ata and related stuff instead. > > > > No. > > Yes. > > -Søren > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
It seems Matthew Sean Thyer wrote: > Please leave the wd driver for those who cannot use the ATA driver. > At least until the ATA driver gets support for more older disks. > > I cant be the only person using an old 80 MB IDE drive as / with > another drive as /usr (a 400 MB SCSI). > > I haven't tried for a couple of months but the ATA driver didn't > work over several different world builds back then and I haven't > seen commits to indicate it will work now. dmesg from a less than > a week old -CURRENT says the disk is: Well, you could supply me with data on what goes wrong and help to get it resolved, thats the way things work around here... The wd driver is only removed from current, so you will still be able to follow 4.x... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Why not gzip iso images?
After reading the announcement... Congratulations to the FreeBSD community another milestone! A great OS... But for the ISO images... IS it a problem to gzip them They take less space on the master site and the mirror sites and they take less bandwidth! Shouldn't be a problem I think! Less bandwidth and less time to download even economical a good thing! With regards, Arnout Boer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
It's been my experience that gzipping an ISO (or other compression tools) do not make enough different to justify the time it takes to both compress and uncompress these things. For example, the time needed to un-gzip the ISO could be longer than the time it would take to download the space that was saved by it. Matt -- Matt Heckaman [[EMAIL PROTECTED]|[EMAIL PROTECTED]] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Wed, 15 Mar 2000, Arnout Boer wrote: : Date: Wed, 15 Mar 2000 07:42:11 -0500 : From: Arnout Boer <[EMAIL PROTECTED]> : To: [EMAIL PROTECTED] : Subject: Why not gzip iso images? : : After reading the announcement... : Congratulations to the FreeBSD community : another milestone! : A great OS... : : But for the ISO images... IS it a problem to gzip : them : They take less space on the master site and the mirror : sites and they take less bandwidth! : : Shouldn't be a problem I think! : : Less bandwidth and less time to download : even economical a good thing! : : With regards, : : Arnout Boer : : : : : To Unsubscribe: send mail to [EMAIL PROTECTED] : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
Matt Heckaman wrote: > It's been my experience that gzipping an ISO (or other compression tools) > do not make enough different to justify the time it takes to both compress > and uncompress these things. For example, the time needed to un-gzip the > ISO could be longer than the time it would take to download the space that > was saved by it. This would only happen once for the user. But for the FTP server, the amount of saved bandwidth accumulates with each download. Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
* Kai Voigt <[EMAIL PROTECTED]> [000315 05:47] wrote: > Matt Heckaman wrote: > > It's been my experience that gzipping an ISO (or other compression tools) > > do not make enough different to justify the time it takes to both compress > > and uncompress these things. For example, the time needed to un-gzip the > > ISO could be longer than the time it would take to download the space that > > was saved by it. > > This would only happen once for the user. But for the FTP server, the > amount of saved bandwidth accumulates with each download. I feel pretty confident assuming that most people that burn ISOs probably keep enough disk space free to hold one and not much more, going from a requirement of ~650MB to ~1.2GB wouldn't be a smart move imo. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
I still have hardware that works with wd and not ata. I posted awhile ago that ata gets stuck in a retry loop on my system. This is with a CVSUP of a couple of days ago. I can provide logins on the box if someone wants to take a look at it. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
It seems David Gilbert wrote: > I still have hardware that works with wd and not ata. I posted awhile > ago that ata gets stuck in a retry loop on my system. This is with a > CVSUP of a couple of days ago. > Be sure you have the abosolutely latest version of the ata driver, a bug was fixed in the last couble of days. > I can provide logins on the box if someone wants to take a look at it. Nice to know, but it wont help much as long as the system wont boot, unless you also have a serial console and a remote reset on that box. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
Thus spake Bill Fumerola ([EMAIL PROTECTED]): > (4) The developers all dropped FreeBSD and are now running Redhat. That's it, I believe. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
On Wed, Mar 15, 2000 at 02:53:57PM +0100, Alexander Langer wrote: > Thus spake Bill Fumerola ([EMAIL PROTECTED]): > > > (4) The developers all dropped FreeBSD and are now running Redhat. > > That's it, I believe. [ ... ] And Joan Rivers is now a Kernel hacker... (smirk) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: top %s not correct
On 15-Mar-2000 Anders Andersson wrote: > on Ons, Mar 15, 2000 at 12:29:29pm +0300, Zherdev Anatoly wrote: >> >> I have the similar problem on ASUS P2B-D/P2B-DS (SMP) but not only top %s >> and on the top without parameters. After starting system top work correctly >> but after some minutes (~2-5) top write zeros. >> >> >From two equal computers only one have this problem. BIOS upgrade was not >> resolve this problem. > > This is a known problem with some ASUS SMP boards. > > The fix is to use the following in your kernel config file: > > device apm0at nexus? flags 0x20 > > instead of the default. Thank you. It's work now :) -- Tolyar. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world: install-info: unrecognized option
Hiya, I just cvsupped a couple of hours ago, after a successful build, the install phase fails: ** snip snip ** ===> lib/libcom_err/doc install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err).A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Stop. ** snip snip ** I'm running 3.4-STABLE, trying to cvsup to cvs-tag RELENG_4. Regards Rasmus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
On Mar 15, Soren Schmidt wrote: > It seems Mathew Kanner wrote: > > disks on Promise controllers. I believe that the problems lies with > > multiple cards on the same interupt but what do I know -- execpt that > > the problem goes away when I disable most devices in the BIOS. > > The motherboard is a abit BE6-II, I've enabled most BIOS > > periphs such as serial ports, printer ports, usb, vga ints but not APM. > > Hmm, I've seen references on the net to the BE6 having trouble with > ATA PCI controllers in one of the slots if the internal controller > is enabled, I dont know which slot that is unfortunately, so moving > things around is my best guess. I did get hit by that, in this case it's the 5th pci slot. When there a controller in there, the system just locks completly. > Btw are you running the latest 4.0 or -current code ? there was > a time when we had problems with the HPT and Promise controllers ? The kernel in question was cvsup'ed right at the change. I'm going to try 4.0 today. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world: install-info: unrecognized option
Please read UPDATING for details on how to upgrade to 4.0 from earlier releases. The quick summary to deal with your problem is: make -DNOINFO installworld make installworld There are other problems you might bump into, so do your homework first. Jim Bloom [EMAIL PROTECTED] Rasmus Skaarup wrote: > > Hiya, > > I just cvsupped a couple of hours ago, after a successful build, the > install phase fails: > > ** snip snip ** > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development > tools." --defentry="* libcom_err: (com_err).A Common Error > Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development > tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > Stop. > > ** snip snip ** > > I'm running 3.4-STABLE, trying to cvsup to cvs-tag RELENG_4. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
transition...
Well, Here we are again. Another branch off the FreeBSD code and the mailing lists are going to be confusing. CURRENT is starting to see posts of the 5.0 code and STABLE is starting to see things of 4.0. I read CURRENT and STABLE at the moment because I have myservers on 3.x and my laptop running 4.0. Just thought I would bring it up. Maybe we should have another mailing lists for the other version. 3.x-STABLE is said to make it to 3.7 (If the timeline stays the same it will be almost a year before we reach this point) 4.x-RELEASE (Currently in the middle) 5.0-CURRENT (The new branch (HEAD) for current) Just thanking out loud -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- echo Mhbqnrnes Stbjr | tr "[a-y]" "[b-z]" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world: install-info: unrecognized option
On Wed, Mar 15, 2000 at 03:54:05PM +0100, Rasmus Skaarup wrote: > > Hiya, > > I just cvsupped a couple of hours ago, after a successful build, the > install phase fails: > > ** snip snip ** > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development > tools." --defentry="* libcom_err: (com_err).A Common Error > Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development > tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > Stop. > > ** snip snip ** > > I'm running 3.4-STABLE, trying to cvsup to cvs-tag RELENG_4. > Follow the instructions at the end of src/UPDATING. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
build failure w/ current
make world fails: cvsup from 3/15/00 14:00 GMT or so. ===> sys/boot/i386/libi386 cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/libi386/aout_freebsd.c -o aout_freebsd.o cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/libi386/biosdisk.c -o biosdisk.o /usr/src/sys/boot/i386/libi386/biosdisk.c: In function `bd_print': /usr/src/sys/boot/i386/libi386/biosdisk.c:242: syntax error before `,' /usr/src/sys/boot/i386/libi386/biosdisk.c:289: case label not within a switch statement /usr/src/sys/boot/i386/libi386/biosdisk.c:293: default label not within a switch statement /usr/src/sys/boot/i386/libi386/biosdisk.c: At top level: /usr/src/sys/boot/i386/libi386/biosdisk.c:301: syntax error before `}' /usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:123: warning: `bd_opendisk' used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:124: warning: `bd_closedisk' used but never defined *** Error code 1 Stop in /usr/src/sys/boot/i386/libi386. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
possible simple install-info fix
Hi,
I was looking into fixing the install-info problem, and wondered if the
solution is really as easy as it seems:
cvs diff: Diffing src
Index: src/Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.141
diff -u -r1.141 Makefile.inc1
--- Makefile.inc1 2000/03/09 06:28:19 1.141
+++ Makefile.inc1 2000/03/15 15:34:25
@@ -183,7 +183,7 @@
WMAKE= ${WMAKEENV} ${MAKE} -f Makefile.inc1
# install stage
-IMAKEENV= ${CROSSENV}
+IMAKEENV= ${CROSSENV} INSTALLINFO="${WORLDTMP}/usr/bin/install-info"
IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1
USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \
I've done an installworld between -CURRENTs (where we wouldn't
encounter the problem anyway) and it used the correct install-info.
If anyone is willing to test an upgrade from 3.4 -> 4.0 with this
fix, I'd appreciate it. Otherwise, I'll do it tomorrow.
If we happen to slide tags and make a new release, this'd be great
for cvsup upgrade path to the release.
Neil
--
Neil Blakey-Milner
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: transition...
On Wed, 15 Mar 2000, Ron 'The InSaNe One' Rosson wrote: > Well, > Here we are again. Another branch off the FreeBSD code and the mailing > lists are going to be confusing. CURRENT is starting to see posts of the > 5.0 code and STABLE is starting to see things of 4.0. I read CURRENT and > STABLE at the moment because I have myservers on 3.x and my laptop > running 4.0. > > Just thought I would bring it up. Maybe we should have another mailing > lists for the other version. > > 3.x-STABLE is said to make it to 3.7 (If the timeline stays the same it > will be almost a year before we reach this point) > > 4.x-RELEASE (Currently in the middle) > > 5.0-CURRENT (The new branch (HEAD) for current) Yep. But why call them "stable", "current", etc. Just call the FreeBSD3, FreeBSD4, FreeBSD5 and alias the existing lists to them. Or, to ease the transition, keep "current" for 4.x and start a new list for 5.x. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B?75,#M#L#M;v6H$N$40FFb(B(B
$BFMA3$N%a!<%k<:Ni$$$?$7$^$9!#$b$7!"A4$/6=L#$NL5$$FbMF$H(B
$B$*46$8$K$J$kMM$G$7$?$i!"$*e$2%a%s%P!<%-%c%s%Z!<%s(B
$B"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#(B
$B$3$N!"%S%8%M%9$NN)$A>e$2$K$46(NO$/$@$5$kJ}$4O"Mm$/$@$5$$(B
$B$<$R!"N)>e$2%a%s%P!<$K$J$C$F?75,;v6H$r$$$C$7$g$K@9$j>e$2(B
$B$^$;$s$+!)(B
$B"c>&:`"d(B
$B!&:#!"7]G=?M$KL)$+$J%V!<%`4pAC2=>QIJ(B
$B!&%=!<%W!&%X%"%1%"%7%j!<%:!J0lHL>.GdE9F~!*%@%$%(%C%H4XO"?)IJ!&0{NAIJ(B
$B!&=w@-!&CK@-$NBN=-$d9u$:$_$NG:$_2r>C$3$@$o$j$N0oIJEy$N(B
$B0lHL$G$OF~$GB(%3%_%C%7%g%sH/@8(B
$B!&%T%s%l%Y%kM-$j!&9_3JL5$7(B
$B!&>R2p.Gd$j$b%*%C%1!e$N(B4$B#0!s!*!*(B
$B!&>R2p\:Y@bL@$K$D$$$F$O(B
http://wz.333.ne.jp/gmembers/455626959/
$B$r$4Mw$/$@$5$$!#(B $B$4O"Mm!"$4;22C$*BT$A$7$F$$$^$9!*!*(B
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)
Thanks for the security tips ;) here are 2 lines which (note to the kiddies) have been removed from my server already. testing:$1$SXz../0Y$mGwyWA9Paeirm51PUrQcU1:1001:999::0:0:asdf:/home/testing :/sbin/nologin sheldonh:$1$27hU2NXY$SHPU3A1sEBceacO0Pdjlk0:1002:1002::0:0:Sheldon Hearn:/home/sheldonh:/sbin/nologin Sorry about the char wrapping but I am sure you get the idea ;) Thanks Damieon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: possible simple install-info fix
Don't forget to test the case of cross platform installs. You can build on one
platform and install on another with the mounts having the target mounted on the
build machine or the source and object mounted on the target machine after the
build was done on a different architecture.
I believe this patch will not work in all cases. Maybe Marcel can shed some
more light on this issue.
Jim Bloom
[EMAIL PROTECTED]
Neil Blakey-Milner wrote:
>
> Hi,
>
> I was looking into fixing the install-info problem, and wondered if the
> solution is really as easy as it seems:
>
> cvs diff: Diffing src
> Index: src/Makefile.inc1
> ===
> RCS file: /home/ncvs/src/Makefile.inc1,v
> retrieving revision 1.141
> diff -u -r1.141 Makefile.inc1
> --- Makefile.inc1 2000/03/09 06:28:19 1.141
> +++ Makefile.inc1 2000/03/15 15:34:25
> @@ -183,7 +183,7 @@
> WMAKE= ${WMAKEENV} ${MAKE} -f Makefile.inc1
>
> # install stage
> -IMAKEENV= ${CROSSENV}
> +IMAKEENV= ${CROSSENV} INSTALLINFO="${WORLDTMP}/usr/bin/install-info"
> IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1
>
> USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \
>
> I've done an installworld between -CURRENTs (where we wouldn't
> encounter the problem anyway) and it used the correct install-info.
>
> If anyone is willing to test an upgrade from 3.4 -> 4.0 with this
> fix, I'd appreciate it. Otherwise, I'll do it tomorrow.
>
> If we happen to slide tags and make a new release, this'd be great
> for cvsup upgrade path to the release.
>
> Neil
> --
> Neil Blakey-Milner
> [EMAIL PROTECTED]
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: build failure w/ current
On 15-Mar-00 Kent Hauser wrote: > > make world fails: > > cvsup from 3/15/00 14:00 GMT or so. > > > > ===> sys/boot/i386/libi386 > cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common >-I/usr/src/sys/boot/i386/libi386/../btx/lib > -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 >-DTERM_EMU > -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/libi386/aout_freebsd.c >-o > aout_freebsd.o > cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common >-I/usr/src/sys/boot/i386/libi386/../btx/lib > -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMSPEED=9600 >-DTERM_EMU > -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/libi386/biosdisk.c -o >biosdisk.o > /usr/src/sys/boot/i386/libi386/biosdisk.c: In function `bd_print': > /usr/src/sys/boot/i386/libi386/biosdisk.c:242: syntax error before `,' > /usr/src/sys/boot/i386/libi386/biosdisk.c:289: case label not within a switch >statement > /usr/src/sys/boot/i386/libi386/biosdisk.c:293: default label not within a switch >statement > /usr/src/sys/boot/i386/libi386/biosdisk.c: At top level: > /usr/src/sys/boot/i386/libi386/biosdisk.c:301: syntax error before `}' > /usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' used but >never defined > /usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' used but never >defined > /usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used but never >defined > /usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used but never >defined > /usr/src/sys/boot/i386/libi386/biosdisk.c:123: warning: `bd_opendisk' used but never >defined > /usr/src/sys/boot/i386/libi386/biosdisk.c:124: warning: `bd_closedisk' used but >never defined > *** Error code 1 > > Stop in /usr/src/sys/boot/i386/libi386. > *** Error code 1 > > Stop in /usr/src/sys/boot/i386. > *** Error code 1 > > Stop in /usr/src/sys/boot. > *** Error code 1 > > Stop in /usr/src/sys. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. Please try http://people.FreeBSD.org/~jhb/patches/biosdisk.patch (relative to /sys/boot/i386/libi386). It looks like some extra stuff was accidentally spammed into the recent commit to biosdisk.c. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys Revisted..
On Tue, 14 Mar 2000, Jay Oliver wrote: > Ok... how is it possible to identify different revisions? As far as I can > tell, the cards are being reported to be identical, though they're almost > certainly not. And since they both worked fine under 'pn', will it be > possible in the future to have support for the current non working revision > via dc? Look at the output of the dc driver. One is probed as a PNIC blah blah blah the other as a PNIC II. On the cards themselves different chips are used. Under 3.x, one would attach to the pn driver, one would not, etc, etc. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
In the last episode (Mar 15), Maxim Sobolev said: > I've just upgraded my production server to the 4.0-RELEASE and found > that squid23 when compiled with -Os option dying with signal 11 on > each attempt to load page. When I recompiled it with -O fault > disappeared. After some digging into the sources with gdb I found This is just a 'me too'. I get it with -O2 (-Os implies -O2, so it's probably the same problem). -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pccard not working on 4.0-RELEASE
In accordance with Murphy's law, 4.0-RELEASE seems to have broken pccard
support for me. I have a WaveLAN wireless LAN card and use the optional
ISA-to-pccard bridge. On a two week old -current, it was working just
fine, displaying the following:
pcic: polling mode
pcic: polling mode
pcic0: at port 0x3e0 iomem 0xd on isa0
pccard0: on pcic0
pccard1: on pcic0
My kernel config file says:
device pcic0 at isa? port 0x3e0 iomem 0xd
device wi
Notice that I don't specify an irq for pcic0, because I am really short of
them. So pcic is run in polling mode. I also tried specifying an irq with
exactly the same result.
With a 4.0-RELEASE kernel it does not work, pcic0 is simply not found and
absolutely no message is being displayed. Applying the below patch which
effectively backs out revision 1.89 of sys/pccard/pcic.c makes the card
work again. It is very unfortunate that it is too late to fix this :(
Blaz Zupan, [EMAIL PROTECTED], http://home.amis.net/blaz/
Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia
Index: pcic.c
===
RCS file: /ftp/pub/FreeBSD/development/FreeBSD-CVS/src/sys/pccard/pcic.c,v
retrieving revision 1.89
retrieving revision 1.88
diff -u -r1.89 -r1.88
--- pcic.c 2000/03/10 05:43:28 1.89
+++ pcic.c 2000/02/21 06:56:29 1.88
@@ -27,7 +27,7 @@
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
- * $FreeBSD: src/sys/pccard/pcic.c,v 1.89 2000/03/10 05:43:28 imp Exp $
+ * $FreeBSD: src/sys/pccard/pcic.c,v 1.88 2000/02/21 06:56:29 imp Exp $
*/
#include
@@ -44,10 +44,6 @@
#include
#include
-/* Get pnp IDs */
-#include
-#include
-
/*
* Prototypes for interrupt handler.
*/
@@ -80,20 +76,9 @@
u_char *regs; /* Pointer to regs in mem */
} pcic_slots[PCIC_MAX_SLOTS];
+static int pcic_irq;
static struct slot_ctrl cinfo;
-static struct isa_pnp_id pcic_ids[] = {
- {PCIC_PNP_82365,NULL}, /* PNP0E00 */
- {PCIC_PNP_CL_PD6720,NULL}, /* PNP0E01 */
- {PCIC_PNP_VLSI_82C146, NULL}, /* PNP0E02 */
- {PCIC_PNP_82365_CARDBUS,NULL}, /* PNP0E03 */
- {0}
-};
-
-static int validunits = 0;
-
-#define GET_UNIT(d)*(int *)device_get_softc(d)
-#define SET_UNIT(d,u) *(int *)device_get_softc(d) = (u)
/*
* Internal inline functions for accessing the PCIC.
@@ -279,16 +264,16 @@
struct slot *slt;
struct pcic_slot *sp;
unsigned char c;
+ void *ih;
char *name;
+ int i;
int error;
- struct resource *r;
+ struct resource *res = 0;
int rid;
static int maybe_vlsi = 0;
- /* Check isapnp ids */
- error = ISA_PNP_PROBE(device_get_parent(dev), dev, pcic_ids);
- if (error == ENXIO)
- return (ENXIO);
+ if (device_get_unit(dev) != 0)
+ return ENXIO;
/*
* Initialise controller information structure.
@@ -304,26 +289,22 @@
cinfo.maxmem = PCIC_MEM_WIN;
cinfo.maxio = PCIC_IO_WIN;
- if (bus_get_resource_start(dev, SYS_RES_IOPORT, 0) == 0)
- bus_set_resource(dev, SYS_RES_IOPORT, 0, PCIC_INDEX0, 2);
- rid = 0;
- r = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0, ~0, 1, RF_ACTIVE);
- if (!r) {
- if (bootverbose)
- device_printf(dev, "Cannot get I/O range\n");
- return ENOMEM;
- }
-
- sp = &pcic_slots[validunits * PCIC_CARD_SLOTS];
- for (slotnum = 0; slotnum < PCIC_CARD_SLOTS; slotnum++, sp++) {
+ sp = pcic_slots;
+ for (slotnum = 0; slotnum < PCIC_MAX_SLOTS; slotnum++, sp++) {
/*
* Initialise the PCIC slot table.
*/
sp->getb = getb1;
sp->putb = putb1;
- sp->index = rman_get_start(r);
- sp->data = sp->index + 1;
- sp->offset = slotnum * PCIC_SLOT_SIZE;
+ if (slotnum < 4) {
+ sp->index = PCIC_INDEX_0;
+ sp->data = PCIC_DATA_0;
+ sp->offset = slotnum * PCIC_SLOT_SIZE;
+ } else {
+ sp->index = PCIC_INDEX_1;
+ sp->data = PCIC_DATA_1;
+ sp->offset = (slotnum - 4) * PCIC_SLOT_SIZE;
+ }
/*
* XXX - Screwed up slot 1 on the VLSI chips. According to
* the Linux PCMCIA code from David Hinds, working chipsets
@@ -463,13 +444,47 @@
* Allocate a slot and initialise the data structures.
*/
validslots++;
- sp->slotnum = slotnum + validunits * PCIC_CARD_
Re: Why not gzip iso images?
On Wed, 15 Mar 2000, Alfred Perlstein wrote: > I feel pretty confident assuming that most people that burn ISOs probably > keep enough disk space free to hold one and not much more, going from > a requirement of ~650MB to ~1.2GB wouldn't be a smart move imo. fetch -o - ftp://path/to/iso.gz | gunzip -c - > /path/to/image.iso Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
Dan Nelson wrote: > > In the last episode (Mar 15), Maxim Sobolev said: > > I've just upgraded my production server to the 4.0-RELEASE and found > > that squid23 when compiled with -Os option dying with signal 11 on > > each attempt to load page. When I recompiled it with -O fault > > disappeared. After some digging into the sources with gdb I found > > This is just a 'me too'. I get it with -O2 (-Os implies -O2, so it's > probably the same problem). > I've noticed various compile-time optimization bugs as well. For example, I tried building Qt with -mpentium -O3 -pipe, and somewhere during the build, I get "Internal compiler error." Falling back to the stock optimization levels of -O2 fixed this. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Serious documentation problems for 4.0 and 5.0
Hi, I found serious problems on documentations of both 4.0 and 5.0. README.TXT and RELEASE.TXT have obsolete descriptions. ---<< README.TXT >>--- - FreeBSD 4.0 --- SNAPSHOT Version ,, - /()` >>> No, 4.0 is official RELEASE, and SNAPSHOT is 5.0 \ \___ / | This is a binary snapshot of 4.0-current, the /- _ `-/ ' (HEAD) branch which is currently moving towards (/\/ \ \ /\ the release of 4.0. / / | `\ >>> No, again. For the latest 4.0-current (HEAD branch) snapshot releases, please install from: ftp://current.freebsd.org/pub/FreeBSD >>> No, again. ---<< RELEASE.TXT >>--- RELEASE NOTES FreeBSD Release 4.0-SNAP This is a 4.0-CURRENT release SNAPshot of FreeBSD, an active development branch which will produce its first release in early March 2000. Those features which have also been back-ported to the 3.x-stable branch (the next release for which will be 3.5) are marked [MERGED]. >>> No, No For the latest of these 4.0-current snapshots, you should always see: ftp://current.freebsd.org/pub/FreeBSD >>> NO. -- Motomichi Matsuzaki <[EMAIL PROTECTED]> Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gcc -Os optimisation broken (RELENG_4)
Hi,
I've just upgraded my production server to the 4.0-RELEASE and found that
squid23 when compiled with -Os option dying with signal 11 on each attempt to
load page. When I recompiled it with -O fault disappeared. After some digging
into the sources with gdb I found that fault came from dereferencing NULL
pointer somewhere in the DNS query procedures. I've tracked the source of this
pointer and found that the function rfc1035QuestionPack (rfc1035.c) called from
rfc1035BuildAQuery receives NULL pointer instead of the supplied hostname as a
3rd argument. Following is two debugging sessions with squid compiled with -Os
and -O (faulty call is in the end of the output):
-Maxim
-Os:
Script started on Wed Mar 15 10:16:16 2000
root@vega# gdb squid
GNU gdb 4.18
[GDB copyright omitted]
(gdb) set args -C -N -d 10
(gdb) b rfc1035BuildAQuery
Breakpoint 1 at 0x8096cb1: file rfc1035.c, line 472.
(gdb) r
Starting program: /usr/ports/www/squid23/work/squid-2.3.STABLE2/src/squid -C -N
-d 10
[unrelevant squid output omitted]
Breakpoint 1, 0x8096cb1 in rfc1035BuildAQuery (
hostname=0x84a5900 "www.yahoo.com", buf=0x8212c00 "", szp=0x8212e00)
at rfc1035.c:472
472 size_t sz = *szp;
(gdb) n
473 memset(&h, '\0', sizeof(h));
(gdb)
472 size_t sz = *szp;
(gdb)
473 memset(&h, '\0', sizeof(h));
(gdb)
474 h.id = rfc1035Qid();
(gdb)
476 h.rd = 1;
(gdb)
477 h.opcode = 0; /* QUERY */
(gdb)
478 h.qdcount = (unsigned int) 1;
(gdb)
479 offset += rfc1035HeaderPack(buf + offset, sz - offset, &h);
(gdb)
480 offset += rfc1035QuestionPack(buf + offset,
(gdb) print hostname
$1 = 0x84a5900 "www.yahoo.com"
(gdb) list
475 h.qr = 0;
476 h.rd = 1;
477 h.opcode = 0; /* QUERY */
478 h.qdcount = (unsigned int) 1;
479 offset += rfc1035HeaderPack(buf + offset, sz - offset, &h);
480 offset += rfc1035QuestionPack(buf + offset,
481 sz - offset,
482 hostname,
483 RFC1035_TYPE_A,
484 RFC1035_CLASS_IN);
(gdb) s
rfc1035QuestionPack (buf=0x8212c0c "", sz=500, name=0x0, type=1, class=1)
at rfc1035.c:201
201 off += rfc1035NamePack(buf + off, sz - off, name);
(gdb) q
The program is running. Exit anyway? (y or n) y
root@vega# exit
Script done on Wed Mar 15 10:17:46 2000
-O:
Script started on Wed Mar 15 09:57:49 2000
root@vega# gdb squid
[GDB copyright omitted]
(gdb) set args -C -N -d 10
(gdb) b rfc1035BuildAQuery
Breakpoint 1 at 0x8096321: file rfc1035.c, line 469.
(gdb) r
Starting program: /usr/ports/www/squid23/work/squid-2.3.STABLE2/src/squid -C -N
-d 10
[unrelevant squid output omitted]
Breakpoint 1, 0x8096321 in rfc1035BuildAQuery (
hostname=0x84a5900 "www.yahoo.com", buf=0x8212c00 "", szp=0x8212e00)
at rfc1035.c:469
469 {
(gdb) n
472 size_t sz = *szp;
(gdb)
473 memset(&h, '\0', sizeof(h));
(gdb)
474 h.id = rfc1035Qid();
(gdb)
475 h.qr = 0;
(gdb)
476 h.rd = 1;
(gdb)
477 h.opcode = 0; /* QUERY */
(gdb)
478 h.qdcount = (unsigned int) 1;
(gdb)
479 offset += rfc1035HeaderPack(buf + offset, sz - offset, &h);
(gdb)
480 offset += rfc1035QuestionPack(buf + offset,
(gdb) print hostname
$1 = 0x84a5900 "www.yahoo.com"
(gdb) list
475 h.qr = 0;
476 h.rd = 1;
477 h.opcode = 0; /* QUERY */
478 h.qdcount = (unsigned int) 1;
479 offset += rfc1035HeaderPack(buf + offset, sz - offset, &h);
480 offset += rfc1035QuestionPack(buf + offset,
481 sz - offset,
482 hostname,
483 RFC1035_TYPE_A,
484 RFC1035_CLASS_IN);
(gdb) s
rfc1035QuestionPack (buf=0x8212c0c "", sz=500, name=0x84a5900 "www.yahoo.com",
type=1, class=1) at rfc1035.c:201
201 off += rfc1035NamePack(buf + off, sz - off, name);
(gdb) q
The program is running. Exit anyway? (y or n) y
root@vega# exit
Script done on Wed Mar 15 09:59:28 2000
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
make world fail!
just cvsup up 3 hrs ago. try to make world, following error been given.. cc -O -pipe -I/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../../common -I/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../btx/lib -I/mnt/ad5s 1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8 -DCOMS PEED=9600 -DTERM_EMU -I/usr/obj/mnt/ad5s1e/FreeBSD-CURRENT/src/i386/usr/include -c /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/vidconsole.c -o vidcons ole.o /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c: At top level: /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:301: syntax err or before `}' /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:103: warning: ` bd_printslice' used but never defined /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:106: warning: ` bd_strategy' used but never defined /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:108: warning: ` bd_open' used but never defined /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:109: warning: ` bd_close' used but never defined /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:123: warning: ` bd_opendisk' used but never defined /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:124: warning: ` bd_closedisk' used but never defined *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
It seems Mathew Kanner wrote: > Hi All, > I wanted to document my difficuties with Vinum and multiple > disks on Promise controllers. I believe that the problems lies with > multiple cards on the same interupt but what do I know -- execpt that > the problem goes away when I disable most devices in the BIOS. > The motherboard is a abit BE6-II, I've enabled most BIOS > periphs such as serial ports, printer ports, usb, vga ints but not APM. Hmm, I've seen references on the net to the BE6 having trouble with ATA PCI controllers in one of the slots if the internal controller is enabled, I dont know which slot that is unfortunately, so moving things around is my best guess. Btw are you running the latest 4.0 or -current code ? there was a time when we had problems with the HPT and Promise controllers ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
Dan Nelson wrote: > In the last episode (Mar 15), Maxim Sobolev said: > > I've just upgraded my production server to the 4.0-RELEASE and found > > that squid23 when compiled with -Os option dying with signal 11 on > > each attempt to load page. When I recompiled it with -O fault > > disappeared. After some digging into the sources with gdb I found > > This is just a 'me too'. I get it with -O2 (-Os implies -O2, so it's > probably the same problem). Any comments from the "compiler gurus"? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
> : pcic0: at port 0x3e0 iomem 0xd on isa0 > This is a slight lie. > You might want to try this at 0x3e2. It is worth a shot. Bingo, it works! Now I'm wondering, GENERIC says: device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable Neither seems quite correct for my situation, where I use device pcic0 at isa? port 0x3e2 iomem 0xd Is there a standard for this and are the above addresses just backwards? I'll do another test with just device pcic0 at isa? as specified in LINT. Blaz Zupan, [EMAIL PROTECTED], http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Installing 4.0 from scratch...
Folks, I've got a machine I'd like to test 4.0 on (and a second hard drive I can use for the testing), but I'd prefer to install 4.0 from scratch on that hard drive, as opposed to trying the upgrade path. Do you use the same boot floppies and simply specify the path as being i386/RELEASES/4.0-RELEASE instead? Or would this require somehow using the snapshots? And how do you do that? I don't recall these questions being answered in the Handbook or discussed any time recently on this list, but if I've missed something, I would appreciate it if you would point me at the appropriate FM to R. Thanks! -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Wed, Mar 15, 2000 at 08:14:37AM -0500, Matt Heckaman wrote: > It's been my experience that gzipping an ISO (or other compression tools) > do not make enough different to justify the time it takes to both compress > and uncompress these things. For example, the time needed to un-gzip the > ISO could be longer than the time it would take to download the space that > was saved by it. Alas, that is just not true for many of us who are in bandwidth-poor countries. Over here, it can take 3 to BIGNUM hours to download an ISO image (there aren't any up-to-date local mirrors), depending on time of day and the phase of the moon. I think compression would definitely help. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
In message <[EMAIL PROTECTED]> Blaz Zupan writes: : > : pcic0: at port 0x3e0 iomem 0xd on isa0 : > This is a slight lie. : > You might want to try this at 0x3e2. It is worth a shot. : : Bingo, it works! Now I'm wondering, GENERIC says: : : device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd : device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable : : Neither seems quite correct for my situation, where I use : : devicepcic0 at isa? port 0x3e2 iomem 0xd : : Is there a standard for this and are the above addresses just : backwards? I'll do another test with just : : devicepcic0 at isa? : : as specified in LINT. The old code wouldn't even look at the second pcic entry. It will just blindly probe at both 3e0 and 3e2 and claim that it was really at 3e0. It would try to share interupts between these two entries and would generally not work at all on systems that had multiple pcic cards in them (I have about 6 different pcic isa cards that play better together now than before, but still not to the level I'd call working). I did have some code in place to try to search out the pcic devices, but it made it impossible to specify the management irq for those devices so I've never committed it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
In message <[EMAIL PROTECTED]> Blaz Zupan writes: : pcic0: at port 0x3e0 iomem 0xd on isa0 This is a slight lie. : device pcic0 at isa? port 0x3e0 iomem 0xd You might want to try this at 0x3e2. It is worth a shot. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
At 12:48 PM 3/15/00 -0500, Donn Miller wrote: >I've noticed various compile-time optimization bugs as well. For >example, I tried building Qt with -mpentium -O3 -pipe, and somewhere >during the build, I get "Internal compiler error." Falling back to >the stock optimization levels of -O2 fixed this. Ports are working with -02 -pipe -march=pentiumpro here, but there has been a problem with buildworld. Fatal compiler errors, sometimes a system seizure, panic, or spontaneous reboot. No problem building the kernel with those flags, last night tried using just -O -pipe for buildworld and seized. Fresh source install of RC3 and cvsup to RELENG_4 building now. One more try before trying with 4.0R. Was thinking an elusive hardware problem, which is not entirely ruled out, but maybe there is an issue with the compiler. Also seem to have worse problems with softupdates enabled on either the src or /usr/obj directory, but /usr doesn't seem to matter. Not related most likely, but am beginning to wonder about many things. Sanity included. 8-/ Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
> The old code wouldn't even look at the second pcic entry. It will > just blindly probe at both 3e0 and 3e2 and claim that it was really at > 3e0. It would try to share interupts between these two entries and > would generally not work at all on systems that had multiple pcic > cards in them (I have about 6 different pcic isa cards that play > better together now than before, but still not to the level I'd call > working). I just tried the way it was specified in LINT: device pcic0 at isa? It does not work. So the only way it works for me is: device pcic0 at isa? port 0x3e2 iomem 0xd Great, I'm a happy camper again :) > I did have some code in place to try to search out the pcic devices, > but it made it impossible to specify the management irq for those > devices so I've never committed it. I'm wondering, why use the management irq at all? Is polling in this situation really so bad? It really shouldn't matter much if the system detects the card removal right away or half a second later, does it? Blaz Zupan, [EMAIL PROTECTED], http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
In message <[EMAIL PROTECTED]> Blaz Zupan writes: : Notice that I don't specify an irq for pcic0, because I am really short of : them. So pcic is run in polling mode. I also tried specifying an irq with : exactly the same result. irqs shouldn't matter one way or the other. : With a 4.0-RELEASE kernel it does not work, pcic0 is simply not found and : absolutely no message is being displayed. Applying the below patch which : effectively backs out revision 1.89 of sys/pccard/pcic.c makes the card : work again. It is very unfortunate that it is too late to fix this :( Yes. I was nervous about adding PnP support this late in the game, but jordan said go for it. I'm curious, if you try to add options PNPBIOS to your kernel, does that fix this problem? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)
On Wed, 15 Mar 2000 10:11:06 CST, Visigoth wrote: > Thanks for the security tips ;) here are 2 lines which (note to > the kiddies) have been removed from my server already. Thanks for taking the time. I tested these over here and the passwords are not disclosed by 200.backup-passwd. So what version do you have installed? You should have rev 1.6. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
In my expierience, these drivers/cards work the best: ed0: For ISA anything, works like a charm rl0: The Realtek driver is rather fast, useful with those $10 PCI NICs fxp0: The Intel driver is by far the highest preformance model, beats the 3com (second best) hands down with much lower CPU overhead. Good cards (Intel server adapters) are expensive though. Usualy you can get away by getting cheapy models (still pricy). Thats what I've found, nothing official here. Yann > > I will attest to that, as I have several Solaris-x86 machines, some on > 2.6. and some on 2.7, all running the DEC cards in 100T-FDX mode like a > champ. As some are news servers, they run 20-30mpbs constantly almost > 24/7 without a hitch, so they work well under Solaris. Guess it was > dumb to assume they would work as well on FBSD, but I had hoped. I have > piles of the DEC cards around. > > I wonder what really has the best driver under FBSD, as far as reliability > and performance, and yes I also want 100T-FDX as my entire network is > interconnected with Cisco Catalyst Switches. I got the inside scoop on > the DEC cards for Solaris from some Sun engineers. Has anyone actually > ever rated/tested the various NIC's for FBSD?? > > -Howard > > > > That's not spurprising. When I tried it, Solaris 2.6 x86 didn't support > > full-duplex 100Base-TX on very many devices. The DEC tulip cards were one of > > the few that had drivers that supported full-duplex. > > > > Charles > > > > -Original Message- > > From: Howard Leadmon [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, March 12, 2000 4:24 PM > > To: Alfred Perlstein > > Cc: [EMAIL PROTECTED] > > Subject: Re: Buffer Problems and hangs in 4.0-CURRENT.. > > > > ... > > > > I used the DEC based cards as I had seen so many people raving > > about them, and at least under Solaris they claim the DEC tulip based > > boards are the hot ticket. > > > > ... > > > > > --- > Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net > ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > >
Re: Why not gzip iso images?
At 05:53 AM 3/15/00 -0800, Alfred Perlstein wrote: >* Kai Voigt <[EMAIL PROTECTED]> [000315 05:47] wrote: > > Matt Heckaman wrote: > > > It's been my experience that gzipping an ISO (or other compression tools) > > > do not make enough different to justify the time it takes to both > compress > > > and uncompress these things. For example, the time needed to un-gzip the > > > ISO could be longer than the time it would take to download the space > that > > > was saved by it. > > > > This would only happen once for the user. But for the FTP server, the > > amount of saved bandwidth accumulates with each download. > >I feel pretty confident assuming that most people that burn ISOs probably >keep enough disk space free to hold one and not much more, going from >a requirement of ~650MB to ~1.2GB wouldn't be a smart move imo. AFAICR, the one time that a gzip and bzip version were available the size was not all that significant and there were promptly removed. However, if you consider the size of the file and the possibility of corruption, then it should be archived with gzip and forget the compression (gzip -1). Now it can be checked for errors. Another issue is the size. Many factors determine how quickly one can obtain the ISO. It would be nice if it were broken into smaller volumes. About 10-20 MB each would be good. That way should something fail, there less time and bandwidth wasted should one need to start over. Call me a disinterested 3rd party. Never pull the ISO, only the parts needed. ;) Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
Anatoly Vorobey <[EMAIL PROTECTED]> wrote: > On Wed, Mar 15, 2000 at 08:14:37AM -0500, Matt Heckaman wrote: > > It's been my experience that gzipping an ISO (or other compression tools) > > do not make enough different to justify the time it takes to both compress > > and uncompress these things. For example, the time needed to un-gzip the > > ISO could be longer than the time it would take to download the space that > > was saved by it. > > Alas, that is just not true for many of us who are in bandwidth-poor > countries. Over here, it can take 3 to BIGNUM hours to download an ISO > image (there aren't any up-to-date local mirrors), depending on time of > day and the phase of the moon. I think compression would definitely help. While you are right about the download/gunzip times, compression doesn't help that much. As has been mentioned in -hackers, the ISO images only compress by 3% or so, or around ~20MB. So, instead of a 640MB ISO image, you have a 620MB image. Is the 20MB significant? (I don't know.) -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
Robert Watson wrote: > > Sounds good to me, as long as it runs :-). > > BTW, ran into another nit from the 02/13 snapshot. I installed the > X-kern-developer distribution, discovered X11 didn't work, so went back > into sysinstall to install X11 stuff. I selected some combination of X11 > components, and chose releng3.freebsd.org as the source -- sysinstall > coredumped. A second attempt at the same resulted in sysinstall hanging. > > This seems to be reproduceable -- what can I do to give you better > debugging information? cd /usr/src/release/sysinstall CC="gcc -g" make all ./sysinstall [list the exacts steps you took, so I can reproduce it too, or find that I can't :)] (core dump) gdb ./sysinstall sysinstall.core Usual procedure here (backtrace, etc). The problem will most likely be the member of a structure pointed by a NULL pointer being reference. Eg, mediaDevice->shutdown(...), i->kids. It would help further if you then break-pointed the function where the problem happened, and stepped through it to pinpoint when the variable turned to NULL (eg, mediaDevice->get(mediaDevice, ...)). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pccard not working on 4.0-RELEASE
In message <[EMAIL PROTECTED]> Blaz Zupan writes: : I'm wondering, why use the management irq at all? Is polling in this : situation really so bad? It really shouldn't matter much if the system : detects the card removal right away or half a second later, does it? For the install disk, it likely doesn't make sense to use the management irq. For most people, polling is sufficient. The management IRQ reduces the window where you can hang the machine due to the driver talking to hardware that is now sitting in the user's hands... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
In my expierience, these drivers/cards work the best: ed0: For ISA anything, works like a charm rl0: The Realtek driver is rather fast, useful with those $10 PCI NICs fxp0: The Intel driver is by far the highest preformance model, beats the 3com (second best) hands down with much lower CPU overhead. Good cards (Intel server adapters) are expensive though. Usualy you can get away by getting cheapy models (still pricy). Thats what I've found, nothing official here. Yann > > I will attest to that, as I have several Solaris-x86 machines, some on > 2.6. and some on 2.7, all running the DEC cards in 100T-FDX mode like a > champ. As some are news servers, they run 20-30mpbs constantly almost > 24/7 without a hitch, so they work well under Solaris. Guess it was > dumb to assume they would work as well on FBSD, but I had hoped. I have > piles of the DEC cards around. > > I wonder what really has the best driver under FBSD, as far as reliability > and performance, and yes I also want 100T-FDX as my entire network is > interconnected with Cisco Catalyst Switches. I got the inside scoop on > the DEC cards for Solaris from some Sun engineers. Has anyone actually > ever rated/tested the various NIC's for FBSD?? > > -Howard > > > > That's not spurprising. When I tried it, Solaris 2.6 x86 didn't support > > full-duplex 100Base-TX on very many devices. The DEC tulip cards were one of > > the few that had drivers that supported full-duplex. > > > > Charles > > > > -Original Message- > > From: Howard Leadmon [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, March 12, 2000 4:24 PM > > To: Alfred Perlstein > > Cc: [EMAIL PROTECTED] > > Subject: Re: Buffer Problems and hangs in 4.0-CURRENT.. > > > > ... > > > > I used the DEC based cards as I had seen so many people raving > > about them, and at least under Solaris they claim the DEC tulip based > > boards are the hot ticket. > > > > ... > > > > > --- > Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net > ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > >
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: ata + vinum problems
On Mar 15, Mathew Kanner wrote:
> On Mar 15, Soren Schmidt wrote:
> > Btw are you running the latest 4.0 or -current code ? there was
> > a time when we had problems with the HPT and Promise controllers ?
>
> The kernel in question was cvsup'ed right at the change. I'm
> going to try 4.0 today.
Replying to myself. By now this is probably the wrong list.
I'm not sure what to do anymore. I've tried to set the bios
settings back to what I've had when it worked it it doesn't seem to
want to go. I've set the drives for ata/66 and ata/33. I've moved
IRQ's around and even tried forcing them. Here are sets of dmesg and
backtraces. This also happens with a kernel and modules compiled on
sunday.
The part that really bothers me is that I have a nearly
identical machine, except for an extra drive in it that originally had
the same problems but when I disabled the extra periphs, the problem
went away.
Any suggestions?
--Mat
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #5: Tue Mar 14 22:07:49 GMT 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/KAZE
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x387f9ff
real memory = 536870912 (524288K bytes)
avail memory = 516157440 (504060K bytes)
Preloaded elf kernel "kernel" at 0xc03e3000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
pcib1: at device 1.0 on pci0
pci1: on pcib1
pci1: at 0.0
isab0: at device 7.0 on pci0
isa0: on isab0
atapci0: port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: at 7.2
chip1: port 0x5000-0x500f at device 7.3 on
pci0
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xa400-0xa47f mem 0xe606-0xe606007f
irq 7 at device 11.0 on pci0
xl0: Ethernet address: 00:50:da:d6:6a:d0
miibus0: on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: supplying EUI64: 00:50:da:ff:fe:d6:6a:d0
atapci1: port
0xb800-0xb83f,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa807 mem
0xe600-0xe601 irq 5 at device 13.0 on pci0
ata2: at 0xa800 on atapci1
ata3: at 0xb000 on atapci1
atapci2: port
0xcc00-0xcc3f,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 mem
0xe604-0xe605 irq 10 at device 15.0 on pci0
ata4: at 0xbc00 on atapci2
ata5: at 0xc400 on atapci2
atapci3: port
0xe000-0xe03f,0xdc00-0xdc03,0xd800-0xd807,0xd400-0xd403,0xd000-0xd007 mem
0xe602-0xe603 irq 11 at device 17.0 on pci0
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-0x6f on isa0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: parallel port not found.
ad0: 26063MB [52953/16/63] at ata0-master using UDMA33
ad4: 26063MB [52953/16/63] at ata2-master using UDMA66
ad6: 26063MB [52953/16/63] at ata3-master using UDMA66
ad8: 26063MB [52953/16/63] at ata4-master using UDMA66
ad10: 26063MB [52953/16/63] at ata5-master using UDMA66
acd0: CD-RW at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
vinum: loaded
vinum: reading configuration from /dev/ad6s1e
vinum: updating configuration from /dev/ad8s1e
vinum: updating configuration from /dev/ad10s1e
vinum: updating configuration from /dev/ad4s1e
xl0: starting DAD for fe80:0001::0250:daff:fed6:6ad0
xl0: DAD complete for fe80:0001::0250:daff:fed6:6ad0 - no duplicates found
---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:304
#1 0xc017f12c in poweroff_wait (junk=0xc03167af, howto=0)
at ../../kern/kern_shutdown.c:554
#2 0xc02ba019 in trap_fatal (frame=0xc031fe64, eva=48)
at ../../i386/i386/trap.c:924
#3 0xc02b9cf1 in trap_pfault (frame=0xc031fe64, usermode=0, eva=48)
at ../../i386/i386/trap.c:817
#4 0xc02b98e7 in trap (frame={tf_fs = -1070530544, tf_es = -1072234480,
tf_ds = -1028915184, tf_edi = 0, tf_esi = 0, tf_ebp = -1070465368,
tf_isp = -1070465392, tf_ebx = -1070364388, tf_edx = 1074316384,
tf_ecx = -1030807537, tf_eax = 0, tf_trapno = 12, tf_err = 0,
tf_eip = -1071262112, tf_cs = 8, tf_eflags = 66054, tf_esp = -856772416,
tf_ss = -1070465344}) at ../../i386/i386/trap.c:423
#5 0xc025d660 in acquire_lock (lk=0xc033891c)
at ../../ufs/ffs/ffs_softdep.c:282
#6 0xc02627
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Sorry about that guys and gals. I was using my ISPs webmail system, and each time I hit sent I got a wonderous Internal Server Error message, and of course I couldn't tell if it got sent or not :). Delete at your own free will. Yann > Why 6 copies of this? > > > This message is in MIME format. > >
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
On Wed, Mar 15, 2000 at 12:17:02PM -0800, yramin wrote: > fxp0: The Intel driver is by far the highest preformance model, beats > the 3com (second best) hands down with much lower CPU overhead. People say that alot. But does anyone have any real measurements [taken in the last three months]? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
On Wed, Mar 15, 2000 at 10:51:55AM -0600, Dan Nelson wrote: > I get it with -O2 (-Os implies -O2, so it's probably the same problem). Not quite. -0s ==> all the -O2 optimizations that do not increase code size. -Os can also perform other optimizations not part of -O2 that decrease code size. The -Os ==> -O2 only tells you how "risky" in optimizing -Os is willing to be. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
In the last episode (Mar 15), David O'Brien said: > On Wed, Mar 15, 2000 at 10:51:55AM -0600, Dan Nelson wrote: > > I get it with -O2 (-Os implies -O2, so it's probably the same > > problem). > > Not quite. -0s ==> all the -O2 optimizations that do not increase > code size. -Os can also perform other optimizations not part of -O2 > that decrease code size. The -Os ==> -O2 only tells you how "risky" > in optimizing -Os is willing to be. Too risky, apparently :) Maxim: It looks like you've done quite a big of debugging already; can you get this bug to appear in a small piece of code? I'm sure the gcc developers would be able to fix the problem pretty quickly if it's easily reproducable. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: possible simple install-info fix
On Wed, 15 Mar 2000, Neil Blakey-Milner wrote: > Hi, > > I was looking into fixing the install-info problem, and wondered if the > solution is really as easy as it seems: Hmmm I had been thinking all along that the problem with install-info was that the system couldn't use the new binary. Are you saying here that installworld is trying to use the old version of install-info that is installed in the system? Please say it isn't so... If install-info is needed to do installworld, shouldn't it be considered a build tool, with all of the build platform/install platform gymnastics that implies? FWIW, I agree that fixing this will significantly lower the bar for 3.x -> 4.0 upgrades. Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
> fxp0: The Intel driver is by far the highest preformance model, > beats the 3com (second best) hands down with much lower CPU > overhead. Do you actually have any numbers to quantify this? There's nothing in the driver architecture nor any of my testing that would suggest this is actually the case at this point. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! old wd driver going away
Soren Schmidt <[EMAIL PROTECTED]> writes: > Well, you could supply me with data on what goes wrong and help > to get it resolved, thats the way things work around here... I'm really ready to do this as i've the same pb with a not so old Desktop under one of the latest 4.0 Current before the 5.0 fork. I've posted my system informations in this list (<[EMAIL PROTECTED]>). Ahem, sorry, I've forgot to mention the version of ATA driver (it was a cvsup on March 9). I'm currently make a new 4-Stable world and gonna try again with ata-all.c v 1.50. > The wd driver is only removed from current, so you will still > be able to follow 4.x... Sure wd is working, but i can't imagine why ata don't on a 3 years old system... -- Eric Jacoboni Ta mère, son mot de passe c'est « toto » ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
Jeffrey J. Mountin <[EMAIL PROTECTED]> wrote in list.freebsd-current: > AFAICR, the one time that a gzip and bzip version were available the size > was not all that significant and there were promptly removed. That's true. Most of the files in the ISO images are already compressed, so trying to gzip it saves only a few percent. Also take into account that many people are downloading and recoding the images on Windows boxes, which don't have gzip by default. > However, if you consider the size of the file and the possibility of > corruption, then it should be archived with gzip and forget the compression > (gzip -1). Now it can be checked for errors. Jordan kindly provides MD5 checksums of the ISO images, which are much more reliable than gzip's checksums. > Another issue is the size. Many factors determine how quickly one can > obtain the ISO. It would be nice if it were broken into smaller > volumes. About 10-20 MB each would be good. That way should something > fail, there less time and bandwidth wasted should one need to start over. That would just make things more complicated, and there's no reason for that. That's what the "reget" command is good for -- no reason to start over at all. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Batteries not charging
I am running 4.0 on my laptop and just noticed that it dow not charge the batteries while it is plugged into an AC source. Under 3.x +PAO it would. Does anyone have any ideas? Here is the entry from my kernel's config file: device apm0at nexus? flags 0x20 # Advanced Power Management Here is what I get in my dmesg: apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- UNIX _is_ user-friendly. It's just not ignorant-friendly and idiot-friendly. Build a system even a fool can use,and only a fool will want to use it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
< said: > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. As of about four years ago, the relative performance of the network interfaces was fairly clear: 1) Intel 2) DEC (now also Intel) 3) vendor not disclosed to me 4) 3Com The reason why Intel's NIC did better in these tests was that their PCI interfaces were comparatively very efficient. Since every major vendor has gone through several revs of silicon, there is some reason to believe that quality vendors' NICs now differ only in the inherent quality of their programming model. (So these old results should mean less today.) I always specify Intel NICs today, unless I don't care about performance (in which case I get a $20 RealTek card). There's probably no reason to prefer it over the current 3Com offering (for example) except that 3Com always seems to cost more. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
On Wed, Mar 15, 2000 at 01:04:06PM -0800, yramin wrote: > I did a few trials FTPing a 600MB file around on a 100Mb switched ... > machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. Much has changed since 3.2. Does anyone have any real data on a 4.0-CURRENT box within the past 3 months? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
Re: HEADS UP! old wd driver going away
On Wed, Mar 15, 2000 at 10:49:43PM +1030, Matthew Sean Thyer wrote: > Please leave the wd driver for those who cannot use the ATA driver. > At least until the ATA driver gets support for more older disks. ... > I haven't tried for a couple of months but the ATA driver didn't work Such a report is _useless_ and can only create FUD. The ATA driver has changed quite a lot. How about *TRYING* the latest ATA driver before even emailing this list with concerns. You may surprisingly find that ATA works just great for you know, and you've done damage rather than help with this email. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD branches?
Does anyone know what they are now or will be? I want to follow 4.0-stable if there will be one. Right now I have been cvsup'ing from 4.0-RC to 5.0-current. I am assuming there will be: 3-stable 4-stable 5-current Yes, no, maybe? Will 4.0-RELEASE turn into the 4-stable branch? -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trouble with CVSUP to 4.0 Release, any ideas??
Not really sure where to start, but here goes. I have several DEC PC164SX machines running FreeBSD-Current, and my last cvsup was like Feb 28. While I had the chance yesterday I decided to change my cvs tag to RELENG_4 and bring things up to release. All seemed simple enough as I have sup'ed this box many times in the past with no problems. So I ran the sup's and then built a new kernel, as well as did a make world to make sure everything was at the release level. That all went fine, then I rebooted, and many things just were not working right. I can get on the console, but not remotely and things like sendmail and procmail processes all seemed to be hanging. I then thought maybe I should build a new kernel after the installworld, so went to try that. To my surprise I got the errors I'll include below. I then also just tried to do another buildworld, and that also blew up (errors below). As I mentioned, I was just trying to sup from Feb 28 to RELEASE, not all that far of a jump. Finally I took another Alpha I had sitting around, I think it's last sup was like Feb 21, and tried to upgrade it to RELEASE. Again that machine is now in total shambles and basically unusable unless I reload from scratch. Heck I even tried running an rm -rf on one of them under the /usr/src dir and grabbing a fresh cvs tree, but still can't compile. Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do I have to do a clean reload?? MAKE KERNEL DEPEND: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mno-fp-regs -Wa,-mev56 ../../alpha/alpha/genassym.c In file included from ../../alpha/alpha/genassym.c:43: ../../sys/systm.h:331: invalid #-line In file included from ../../alpha/alpha/genassym.c:45, from ../../alpha/alpha/genassym.c:43: ../../sys/proc.h:47: invalid #-line In file included from ../../sys/signal.h:245, from ../../sys/proc.h:50, from ../../alpha/alpha/genassym.c:43: ../../sys/ucontext.h:34: invalid #-line ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match In file included from ../../alpha/alpha/genassym.c:50: ../../sys/socket.h:232: invalid #-line In file included from ../../alpha/alpha/genassym.c:51: ../../sys/resource.h:101: invalid #-line ../../sys/resource.h:123: invalid #-line In file included from ../../alpha/alpha/genassym.c:52: ../../sys/resourcevar.h:98: invalid #-line In file included from ../../alpha/alpha/genassym.c:59, from ../../alpha/alpha/genassym.c:52: ../../vm/vm_map.h:380: invalid #-line In file included from from from from ../../netinet6/in6.h:453: invalid #-line In file included from from from ../../nfs/nfs.h:728: invalid #-line *** Error code 1 Stop in /usr/src/sys/compile/U3. MAKE BUILDWORLD: -- >>> Rebuilding the temporary build tree -- rm -rf /usr/obj/usr/src/alpha mkdir -p /usr/obj/usr/src/alpha/usr/bin mkdir -p /usr/obj/usr/src/alpha/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/alpha/usr/games mkdir -p /usr/obj/usr/src/alpha/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/alpha/usr/libexec/elf mkdir -p /usr/obj/usr/src/alpha/usr/sbin mkdir -p /usr/obj/usr/src/alpha/usr/share/misc mkdir -p /usr/obj/usr/src/alpha/usr/include/arpa mkdir -p /usr/obj/usr/src/alpha/usr/include/g++/std mkdir -p /usr/obj/usr/src/alpha/usr/include/objc mkdir -p /usr/obj/usr/src/alpha/usr/include/protocols mkdir -p /usr/obj/usr/src/alpha/usr/include/readline mkdir -p /usr/obj/usr/src/alpha/usr/include/rpc mkdir -p /usr/obj/usr/src/alpha/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/alpha/usr/include/openssl mkdir -p /usr/obj/usr/src/alpha/usr/include/security mkdir -p /usr/obj/usr/src/alpha/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/alpha/sys -- >>> stage 1: bootstrap tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/alpha DESTDIR=/usr/obj/usr/src/alpha INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=alpha TOOLS_PREFIX=/usr/obj/usr/src/alpha PATH=/usr/obj/usr/src/alpha/usr/sbin:/usr/obj/usr/src/alpha/usr/bin:/usr/obj/usr/src/alpha/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/usr/src/alpha/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/alpha/usr/include /usr/src/games/fortune/strfile/strfile.c
Re: FreeBSD branches?
On Wed, Mar 15, 2000 at 06:15:37PM -0500, Ted Sikora wrote: > Does anyone know what they are now or will be? I want to follow > 4.0-stable if there will be one. Right now I have been cvsup'ing > from 4.0-RC to 5.0-current. I am assuming there will be: > > 3-stable > 4-stable > 5-current > > Yes, no, maybe? Will 4.0-RELEASE turn into the 4-stable branch? Right now we have all three. 3-stable uses the tag RELENG_3, 4-stable uses RELENG_4, and 5-current uses '.'. The 4-stable branch was created first, then 4.0-RELEASE was tagged (using RELENG_4_0_0_RELEASE) as a snapshot of 4-stable. That's normally how releases work, they are a snapshot of the appropriate -stable branch. (3.0 was an exception to this.) -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Wed, 15 Mar 2000, Anatoly Vorobey wrote: > Alas, that is just not true for many of us who are in bandwidth-poor > countries. Over here, it can take 3 to BIGNUM hours to download an ISO > image (there aren't any up-to-date local mirrors), depending on time of > day and the phase of the moon. I think compression would definitely help. As much as I sympathize with the plight of people who have to pay for slow b/w, we're talking about something that is a luxury, not a necessity. Sure, having a gzip'ed version of the iso image avaiable is probably a good idea, but if you want your stuff gzip'ed just do an ftp install. Those bits are already gzip'ed for you. Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
| > Alas, that is just not true for many of us who are in bandwidth-poor | > countries. Over here, it can take 3 to BIGNUM hours to download an ISO | > image (there aren't any up-to-date local mirrors), depending on time of | > day and the phase of the moon. I think compression would definitely help. | | As much as I sympathize with the plight of people who have to pay | for slow b/w, we're talking about something that is a luxury, not a | necessity. Sure, having a gzip'ed version of the iso image avaiable is | probably a good idea, but if you want your stuff gzip'ed just do an ftp | install. Those bits are already gzip'ed for you. Of course, you can always be good little FreeBSD users and order the CD. -Dan -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic during make depend
Well now...
Successfully did a buildworld with -O -pipe -march=pentiumpro, installworld
was good, remade /dev and built a generic kernel. Config'd my local kernel
and within the first few lines of 'make depend' it bombed:
> gdb -k kernel.debug vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
SMP 2 cpus
IdlePTD 3633152
initial pcb at 23a6e0
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0100
fault virtual address = 0x16
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc013e14a
stack pointer = 0x10:0xc9bf7e04
frame pointer = 0x10:0xc9bf7e08
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 182 (mysqld)
interrupt mask = net tty bio cam <- SMP: XXX
trap number = 12
panic: page fault
mp_lock = 0102; cpuid = 1; lapic.id = 0100
boot() called on cpu#1
syncing disks... 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73 73
giving up on 44 buffers
Uptime: 2h1m7s
dumping to dev #ad/0x20001, offset 45056
dump ata0: resetting devices .. done
128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110
109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88
87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63
62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38
37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:304
304 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:304
#1 0xc01471f8 in poweroff_wait (junk=0xc021574f, howto=-920381984) at
../../kern/kern_shutdown.c:554
#2 0xc01e5047 in trap_fatal (frame=0xc9bf7dc4, eva=22) at
../../i386/i386/trap.c:924
#3 0xc01e4cdd in trap_pfault (frame=0xc9bf7dc4, usermode=0, eva=22) at
../../i386/i386/trap.c:817
#4 0xc01e48db in trap (frame={tf_fs = -920387560, tf_es = -910229488,
tf_ds = -1072037872, tf_edi = 0,
tf_esi = -925050432, tf_ebp = -910197240, tf_isp = -910197264,
tf_ebx = 14, tf_edx = 1107296256,
tf_ecx = 16777217, tf_eax = 1107296256, tf_trapno = 12, tf_err = 0,
tf_eip = -1072438966, tf_cs = 8,
tf_eflags = 66182, tf_esp = -1058693248, tf_ss = -910197212}) at
../../i386/i386/trap.c:423
#5 0xc013e14a in funsetown (sigio=0xe) at ../../kern/kern_descrip.c:365
#6 0xc015f2fa in soclose (so=0xc8dcd9c0) at ../../kern/uipc_socket.c:239
#7 0xc0157582 in soo_close (fp=0xc0e59f80, p=0xc92415e0) at
../../kern/sys_socket.c:180
#8 0xc013ee05 in fdrop (fp=0xc0e59f80, p=0xc92415e0) at ../../sys/file.h:211
#9 0xc013ed43 in closef (fp=0xc0e59f80, p=0xc92415e0) at
../../kern/kern_descrip.c:1059
#10 0xc013eac0 in fdfree (p=0xc92415e0) at ../../kern/kern_descrip.c:929
#11 0xc0140201 in exit1 (p=0xc92415e0, rv=11) at ../../kern/kern_exit.c:186
#12 0xc0148ce6 in sigexit (p=0xc92415e0, sig=11) at ../../kern/kern_sig.c:1480
#13 0xc0148a60 in postsig (sig=11) at ../../kern/kern_sig.c:1383
#14 0xc01e4ad0 in trap (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi =
673009436, tf_esi = 673009436,
tf_ebp = -1077938476, tf_isp = -910196780, tf_ebx = 672450920,
tf_edx = 1953525504, tf_ecx = 134519040,
tf_eax = 256000, tf_trapno = 12, tf_err = 1953525544, tf_eip =
672389099, tf_cs = 31, tf_eflags = 66050,
tf_esp = -1077938500, tf_ss = 47}) at ../../i386/i386/trap.c:159
#15 0x2813d7eb in ?? ()
cannot read proc at 0
Wiped the compile dir and started over with no problems.
This was with a RELENG_4 cvsup from ealier today (posted to -current, but
this is a follow-up from earlier).
Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Mar 15, 9:03am, Kris Kennaway wrote: } Subject: Re: Why not gzip iso images? } On Wed, 15 Mar 2000, Alfred Perlstein wrote: } } > I feel pretty confident assuming that most people that burn ISOs probably } > keep enough disk space free to hold one and not much more, going from } > a requirement of ~650MB to ~1.2GB wouldn't be a smart move imo. } } fetch -o - ftp://path/to/iso.gz | gunzip -c - > /path/to/image.iso This doesn't allow you to restart a failed transfer, which you might want to be able to do if it takes two or three days to transfer the entire file. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
Mike, These are my own perosnal findings with machines I've tinkered with. Nothing scientific about them. I did a few trials FTPing a 600MB file around on a 100Mb switched network between to machines (they were not identical, but used the same ones for both tests), once with Intel PRO/100 adapters, and once with 3com parralel tasking (forgot the model number) adapters. I watched top both times, and noticed that the Intels had lower interupt %s, and finished the job about 5-30 seconds faster (varied on each run). Both machines used wu-ftpd and were running FreeBSD 3.2 - R at the time. > > fxp0: The Intel driver is by far the highest preformance model, > > beats the 3com (second best) hands down with much lower CPU > > overhead. > > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. >
RE: Why not gzip iso images?
> But for the ISO images... IS it a problem to gzip > them > They take less space on the master site and the mirror > sites and they take less bandwidth! Since almost the entire content of the ISO image is already gzipped, the size savings works out to be a percent or two, or at least did when 3.4 was released. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble with CVSUP to 4.0 Release, any ideas??
On Wed, 15 Mar 2000, Howard Leadmon wrote: > Any ideas how to fix this, or to get to 4.0 RELEASE on my other alphas do > I have to do a clean reload?? > > ../../sys/ucontext.h:34: invalid #-line > ../../alpha/alpha/genassym.c:44: #-lines for entering and leaving files don't match Can I see the contents of /usr/src/sys/ucontext.h -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Wed, Mar 15, 2000 at 12:17:02PM -0800, yramin wrote: : > fxp0: The Intel driver is by far the highest preformance model, beats : > the 3com (second best) hands down with much lower CPU overhead. : : People say that alot. But does anyone have any real measurements [taken : in the last three months]? I'm able to get approx the same ftp preformance out of both cards (9MB/s over a kinda busy ethernet). Didn't think to look at the cpu load. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in4.0-CURRENT..)
At 12:53 PM -0800 2000/3/15, Mike Smith wrote: > Do you actually have any numbers to quantify this? There's nothing in > the driver architecture nor any of my testing that would suggest this is > actually the case at this point. Sigh Sounds like I need to take another benchmarking side-trip. I happen to have a reasonably powerful box with a quite recent 3.x-STABLE and an Intel EtherExpress Pro 100+ NIC, and a 3Com3c905 NIC that I can borrow out of another machine. I'd also like to play with upgrading to 4.0 on another disk on this machine, so maybe I can do this as well. If someone can point me at some instructions on how I can install 4.0 on a second disk on the same machine (so that I can keep my 3.x-STABLE, thankyouverymuch ;-), I'll be glad to try some benchmarking with ftp'ing and scp'ing large files around on our internal backbone. -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
In message <[EMAIL PROTECTED]>, Mike Smith writes: >> fxp0: The Intel driver is by far the highest preformance model, >> beats the 3com (second best) hands down with much lower CPU >> overhead. > >Do you actually have any numbers to quantify this? There's nothing in >the driver architecture nor any of my testing that would suggest this is >actually the case at this point. The FreeBSD fxp driver does a lot to reduce the number of transmit interrupts; only 1/120 of transmitted packets result in interrupts. See the code relating to FXP_CXINT_THRESH. Assuming an even balance of transmitted and received packets, this should reduce the total number of interrupts by nearly 50%. I don't know if drivers for other cards do (or even can) use this approach. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
> In message <[EMAIL PROTECTED]>, Mike Smith writes: > >> fxp0: The Intel driver is by far the highest preformance model, > >> beats the 3com (second best) hands down with much lower CPU > >> overhead. > > > >Do you actually have any numbers to quantify this? There's nothing in > >the driver architecture nor any of my testing that would suggest this is > >actually the case at this point. > > The FreeBSD fxp driver does a lot to reduce the number of transmit > interrupts; only 1/120 of transmitted packets result in interrupts. See > the code relating to FXP_CXINT_THRESH. > > Assuming an even balance of transmitted and received packets, this should > reduce the total number of interrupts by nearly 50%. I don't know if > drivers for other cards do (or even can) use this approach. This is why I'm asking for real information here; so far all I'm hearing is folklore. The xl driver, for example, does both transmit and receive interrupt coalescing, which should make it superior again, right? 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Best NIC for FBSD (was: Buffer Problems and hangs in 4.0-CURRENT..)
In article [EMAIL PROTECTED]> you write: >> In message <[EMAIL PROTECTED]>, Mike Smith writes: >> >> fxp0: The Intel driver is by far the highest preformance model, >> >> beats the 3com (second best) hands down with much lower CPU >> >> overhead. >> > >> >Do you actually have any numbers to quantify this? There's nothing in >> >the driver architecture nor any of my testing that would suggest this is >> >actually the case at this point. >> >> The FreeBSD fxp driver does a lot to reduce the number of transmit >> interrupts; only 1/120 of transmitted packets result in interrupts. See >> the code relating to FXP_CXINT_THRESH. >> >> Assuming an even balance of transmitted and received packets, this should >> reduce the total number of interrupts by nearly 50%. I don't know if >> drivers for other cards do (or even can) use this approach. > >This is why I'm asking for real information here; so far all I'm hearing >is folklore. The xl driver, for example, does both transmit and receive >interrupt coalescing, which should make it superior again, right? 8( I've found that fxp and xl are roughly on a par for cpu overhead when under heavy http traffic, with xl holding a slight edge last time I looked. Of course, if you _really_ want to reduce cpu load, the Alteon cards (and the ti driver) beat both of them. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
On Mar 15, Greg Lehey wrote: > > Replying to myself. By now this is probably the wrong list. > > I'm not sure what to do anymore. I've tried to set the bios > > settings back to what I've had when it worked it it doesn't seem to > > want to go. I've set the drives for ata/66 and ata/33. I've moved > > IRQ's around and even tried forcing them. Here are sets of dmesg and > > backtraces. This also happens with a kernel and modules compiled on > > sunday. > > The part that really bothers me is that I have a nearly > > identical machine, except for an extra drive in it that originally had > > the same problems but when I disabled the extra periphs, the problem > > went away. > > I'm a bit behind in my mail, and I don't have time to give this proper > attention yet, but I do see that your problem relates to soft > updates. It's not clear that the soft updates themselves are a cause > of the problem, or just a facilitator, but it would be interesting to > see what happens if you turn them off. Note also that there are some > bogons in your config, to judge by the vinum startup messages. I'll > analyse this in a day or two when I (hopefully) have more time. The bogons me were messing me around with Vinum before I figured out that the crash had messed up one of the disklabels. This occurs occasionally after a crash. I did try it couple of days back with and without softupdates. Softupdates only made the problems appear more quickly but I've lost track of all the combinations that's I've tried so I should try one more time without. Thanks, --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mysql & FreeBSD 4.0 problem
On Wed, Mar 15, 2000 at 11:51:52AM +0300, Zherdev Anatoly wrote: > Hello. > > I have some problem with MySQL & 4.0 > > If MySQL compile -static on last snapshots (I tried snapshots 2214 > & 2313), mysqld don't work correctly. > After starting mysqld listen port and don't print errors, but > telnet localhost 3306 don't write mysql version (mysqld nothing print :( ) > and mysql client can't connect too. > > Telnet don't break connection while i don't kill mysqld. > > Mysql dynamicaly compiled work correct (mysqld print version number if connect > on it port). > > On old snapshots (i tried on 2112) and FreeBSD 3.x (i tried 3.4 stable > 2125) all work OK. > I test it on different computers SMP/non SMP. I added additional support for pthread_cancel() on 27 January that doesn't interact with the static linker well. This is almost surely the reason you're having problems. I'm very close (an hour, maybe) to checking a fix into the RELENG_4 branch, as well as the head. Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
Maxim Sobolev <[EMAIL PROTECTED]> wrote: > I've just upgraded my production server to the 4.0-RELEASE and found that > squid23 when compiled with -Os option dying with signal 11 on each attempt to > load page. When I recompiled it with -O fault disappeared. Which brings us back to the popular topic of which optimization levels are reliable. Building 5.0-CURRENT with "-Os -mpentium" failed for me with gas complaining (unknown opcode I think, but don't hold me to it). I went back to "-O -mpentium" and that worked fine. On another machine, "-O2 -mpentiumpro" worked, too. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic during make depend
"Jeffrey J. Mountin" wrote: > Successfully did a buildworld with -O -pipe -march=pentiumpro, installworld > was good, remade /dev and built a generic kernel. Config'd my local kernel > and within the first few lines of 'make depend' it bombed: Sounds like one of those nasty gcc optimization bugs. I generally build my kernel and world with -mpentium -O3 -pipe, and I haven't seen any bugs at all. I build everything with these flags without problems. The only problems I've see, as mentioned previously, was in building Qt. I've gotten an "Internal compiler error" with those flags, but reverting to what Troll put in qt/configs solved the problems. Apparently, there's both compile-time and run-time bugs with gcc's opt. code. I think there are some bugs with the pentium-specific flags in gcc, excluding the generic-pentium flag of -mpentium. I would try using -mpentium -O3 -pipe --- I'm pretty confident that will solve your problems, and you can still get generic pentium optimization levels. Of course, I don't really know if there's anything to be gained by using these flags over the stock -O -pipe -- but I do it anyways for the psychological reassurance (placebo effect). I definitely think building XFree86 with pentium opt. is a great idea. But with buildworld and buildkernel, my advice would be to just use -mpentium, as it's probably the "happiest medium" between pentium opt. and stability. From what I've heard, compiling mission critical stuff with -mpentiumpro is a bad idea. Hmmm... didn't -mpentiumpro come from pgcc? I think the best place to use -mpentiumpro is in compiling multimedia type stuff, where stability isn't important but speed is. Basically, gcc is a very good compiler. But, it isn't exactly the best compiler to use for optimization. Someone told me that Sun's and DEC's compilers, for example, blow away gcc in terms of speed. But, they aren't portable. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic during make depend
On 2000-Mar-16 15:04:00 +1100, Donn Miller <[EMAIL PROTECTED]> wrote: >Basically, gcc is a very good compiler. But, it isn't exactly the >best compiler to use for optimization. Someone told me that Sun's and >DEC's compilers, for example, blow away gcc in terms of speed. But, >they aren't portable. I think it's very dependent on the target architecture and how popular that architecture is. Traditionally, the M68K and SPARC families were the most popular, and gcc generated the best (or equal best) code on them. The i386 is now a more popular family but, at the high end, optimisation is restricted by the difficulty of obtaining accurate documentation. The Alpha is a very difficult processor to generate good code for (and I suspect the IA64 will be worse). DEC (and now Compaq) have put a lot of effort into tweaking their compiler - I don't believe anything like the same amount of effort has been expended on the gcc backend (and I wouldn't expect it). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
port/XFree86-4 make install fail.
"make all" success without any problem.
however, make install fail ;(
following are the error msg.
anyway I can fix this problem?
thx~
##
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 298 296 300 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 291 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
Stop in
/mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs/Xserver
/Xext.
*** Error code 1
Stop in
/mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs/Xserver
.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
FYI: 4.0-RELEASE with international CVS repository source codes
If you are NOT an US resident, and try to use FreeBSD 4.0-RELEASE which was built with the source code of cvsup.internat.freebsd.org (which is not available at ftp.freebsd.org 'cause it's in US), try: ftp://current.jp.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE/> This release is build at current.jp.FreeBSD.org, not a mirror of the one at ftp.internat.FreeBSD.org. Sorry no packages are available due to the lack of HDD space. If something goes wrong, please email to me. P.S.: current.jp.FreeBSD.org serves daily FreeBSD snapshots with international codes, which is not available at current.freebsd.org. If you have also interested, check /pub/FreeBSD/snapshots/i386 directory. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: port/XFree86-4 make install fail.
Idea Receiver wrote: > > "make all" success without any problem. > however, make install fail ;( > > following are the error msg. [snip] > xf86vmode.c: In function `ProcXF86VidModeGetMonitor': > xf86vmode.c:1320: Unable to generate reloads for: > (insn 298 296 300 (parallel[ > (set (reg:SI 0 %eax) > (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0 > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -34 [0xffde])) 0)) > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -36 [0xffdc])) 0)) > (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) > (const_int -40 [0xffd8])) 0)) This sounds like a problem with older 4.0-currents. Did you make world and your kernel recently? -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
