Re: Wierd AMD panics caused by VMWare?
On Wed, 23 Feb 2000, Matthew Dillon wrote: [I wrote] :See PR 16568. pmap_remove_all() doesn't flush the TLB properly in :FreeBSD-3.x on i386's. Somehow this doesn't cause many problems, but :it fairly reliably breaks the free() in fdfree() when there was a file :descriptor larger than about 1000 (this gives a free() of more than :MAXALLOCSAVE = 2 pages) when there is a lot of fork() activity. Ahh. I presume you will commit this patch now that Bjoern has confirmed that it works? Not until the reason that it works is understood. I don't know why an unconditional invltlb() didn't work either, it should have. Maybe the __asm macro is being optimized out. I verified that the unconditional invtlb() doesn't work. Better yet, replacing the invltlb_1pg() in the loop doesn't work. I think this means that we've changed the page tables too early for a page elsewhere. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
yes, current is broke...
I'm guessing this is related to jkh's mention of OpenSSH coming into the tree, but I'm posting it anyway. Just in case it helps. my cvsup is less then 4 hours old. === libssl rm -f .depend mkdep -f .depend -a-DTERMIOS -DANSI_SOURCE -DNO_IDEA - I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto - I/usr/obj/usr/src/secure/lib/libssl -DL_ENDIAN - DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/i386/usr/include /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/bio_ssl.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s2_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_both.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_pkt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_srvr.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_algs.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_asn1.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_cert.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_ciph.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_err.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_err2.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_rsa.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_sess.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_stat.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_txt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_clnt.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_enc.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_lib.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_meth.c /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_srvr.c cd /usr/src/secure/lib/libssl; make _EXTRADEPEND echo libssl.so.1: /usr/obj/usr/src/secure/lib/libssl/openssl/opensslconf.h .depend === libssh make: don't know how to make strlcat.c. Stop *** Error code 2 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yes, current is broke...
Yes it is. strlcat and strlcpy are not needed in libssh since they are in the libc already. They existed in the port because earlier version of 3.x did not have them. Mark is in the middle of committing all of the changes. It might be a little while until everything is clean again. Jim Bloom [EMAIL PROTECTED] Dan Langille wrote: I'm guessing this is related to jkh's mention of OpenSSH coming into the tree, but I'm posting it anyway. Just in case it helps. my cvsup is less then 4 hours old. === libssl cd /usr/src/secure/lib/libssl; make _EXTRADEPEND echo libssl.so.1: /usr/obj/usr/src/secure/lib/libssl/openssl/opensslconf.h .depend === libssh make: don't know how to make strlcat.c. Stop *** Error code 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0 wierdness with Compex Freedomline
On Thu, Feb 24, 2000 at 02:07:40PM -0500, Garrett Wollman wrote: On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser [EMAIL PROTECTED] said: Assuming you mean ``100BASE-T (half duplex)'' here... This is not quite right. In a CSMA/CD medium access protocol, like that used by Ethernet, the actual capacity of the link is always(*) somewhat less than 100%; the exact value depends on the precise parameters of the transmissions at both ends.(**) Ok ... we all know what exactly should be theoretical maximum and all ... but that wasn't exactly my question ... I have having weird problems with the network performance permanently dropping to below 100 kB/s (while still in 100 Mbps/FDX). Is there anybody that could give a plausible explanation for this break-down ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yes, current is broke...
At 01:59 PM 2/24/00 -0800, Alfred Perlstein wrote: * Dan Langille [EMAIL PROTECTED] [000224 13:45] wrote: I'm guessing this is related to jkh's mention of OpenSSH coming into the tree, but I'm posting it anyway. Just in case it helps. my cvsup is less then 4 hours old. === libssl rm -f .depend mkdep -f .depend -a-DTERMIOS -DANSI_SOURCE -DNO_IDEA - I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto - I/usr/obj/usr/src/secure/lib/libssl -DL_ENDIAN - DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/i386/usr/include Yes, Mark is currently ripping into libcryto and friends pretty roughly, this is sorta expected. :) With 48 commits (so far) to -current (only 1 to -stable) he's on a rampage! CVSup'd in the middle and of course building is broken. Check commits, check mail, check more commits, repeat several times Need to wait for him to either run out of code to commit or steam or Dew or smokes or whatever's keeping him going. Then we can all resume building. Meantime I'll just sit back and cheer. ;) Go Mark, Go Mark 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
solved (was Re: disklabels partition sizes differ ...)
Hi Bruce, it's running now. I removed every slice and started over. I randomly choosed another size for the WIn98 slice (~6GB) installed after that FreeBSD and now I don't get that messages anymore. Maybe fdisk was the culprit ... have no other explanation. Thanks for your help and patience Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with IBM Netfinity 5000 Server
On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: I also set these flags at my /etc/make.conf CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -O6 (any -O above 3) is nonsense with the base GCC compiler. I really have to wonder what people think they are getting by using such hight -O values. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wierd AMD panics caused by VMWare?
There's something fishy going on here. I have a feeling that the issue may be related to the reallocation fragmentation -- we might be running the system out of KVM and there are *NO* NULL checks in the file descriptor allocation code. I'm trying to instrument the code and duplicate the problem now, and will go from there. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/crypto/libdes [...]
Gimme a break, I'm getting there! :-)
M
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
On Thu, Feb 24, 2000 at 09:34:36PM +0200, Mark Murray wrote:
markm 2000/02/24 21:34:35 SAST
IP libdes. All hail libcrypto!
With -current (cvsuped from cvsup.freebsd.org/cvsup.internat.freebsd.org) as
of right now (23:40 +0100):
stage 4: populating /usr/obj/usr/src/i386/usr/include
[...]
cd /usr/src/secure/lib/libcrypto; make beforeinstall
[...]
cd /usr/src/secure/lib/libdes; make beforeinstall
cd: can't cd to /usr/src/secure/lib/libdes
*** Error code 2
Patch for Makefile.inc1 1.138 included.
/s/Udo
--
Booze is the answer. I don't remember the question.
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=patch
--- Makefile.inc1.origThu Feb 24 23:24:49 2000
+++ Makefile.inc1 Thu Feb 24 23:36:15 2000
@@ -585,7 +585,6 @@
.if exists(${.CURDIR}/secure/lib/libcrypto)
cd ${.CURDIR}/secure/lib/libcrypto; ${MAKE} beforeinstall
.endif
- cd ${.CURDIR}/secure/lib/libdes;${MAKE} beforeinstall
.if exists(${.CURDIR}/secure/lib/libssl)
cd ${.CURDIR}/secure/lib/libssl;${MAKE} beforeinstall
.endif
--M9NhX3UHpAaciwkO--
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) )
megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 Adaptec AHA-294X Ultra SCSI host adapter scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] [3.0 GB] Then tried /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt Its slow, but the server does not crash. However, if Queing enabled, it does crash. ie. the card is still unstable. That more or less confirms what I thought. -- \\ 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: dc0 wierdness with Compex Freedomline
Ok ... we all know what exactly should be theoretical maximum and all ... but that wasn't exactly my question ... I have having weird problems with the network performance permanently dropping to below 100 kB/s (while still in 100 Mbps/FDX). Is there anybody that could give a plausible explanation for this break-down ? Most likely you have a duplex mismatch, ie. one end full duplex, the other half duplex. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with IBM Netfinity 5000 Server
At 02:51 PM 2/24/00 -0800, David O'Brien wrote:
On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote:
I also set these flags at my /etc/make.conf
CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations
COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops
-O6 (any -O above 3) is nonsense with the base GCC compiler.
I really have to wonder what people think they are getting by using such
hight -O values.
Maybe due to things like the Apache ports' Makefile:
#
# Set APACHE_PERF_TUNING env. variable to YES to get maximum performance
#
.if defined(APACHE_PERF_TUNING) ${APACHE_PERF_TUNING} == YES
OPTIM+= -DBUFFERED_LOGS
CFLAGS+= -O6 -fomit-frame-pointer
.endif
... and not reading the man page or looking at the source.
Hey program does this, looks good, and so
Also, the various optimization levels (et all) choice keeps coming up, but
-O6 is not mentioned in the man pages. Must be magic then. ;)
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: dc0 wierdness with Compex Freedomline
No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX cables are used simultaneous. Due to the small ethernet frame size, it is next to impossible to get the full speed for data transmission. FreeBSD has been able to do that (full speed) for several years now. I measured this myself way back in June 1997, between a P-133 and a PPro-200. You can do much better with current hardware. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wierd AMD panics caused by VMWare?
Ok, I've reproduced the crash. It isn't running out of KVM. I suspect there is a bug in kmem_malloc() or kmem_free(), or possibly kmem_malloc() of a previously freed space. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with a Compaq Prosigna 300m P75
Does anyone know how to allow 3.4 or 4.0 to read the memory on the riser board. The Compaq smart start reads it and it shows up when the system boots. It knows the riser board is there, because the CPU is on it Scott
Marathon
At 12:58 AM 2/25/00 +0200, Mark Murray wrote: Gimme a break, I'm getting there! :-) So when is this event scheduled to end, so we can go for a test drive? 57^H^H61 commits to -current and counting... 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: Marathon
On Thu, 24 Feb 2000, Jeffrey J. Mountin wrote: So when is this event scheduled to end, so we can go for a test drive? 57^H^H61 commits to -current and counting... The last message to show up in the series said Mark was finished and about to collapse unconscious, so I guess that means "let the bug reports begin"! Please check that your bug hasn't already been reported before mailing, though, eh? Making Mark pass out again in fright due to 3000 new messages in -current when he wakes up won't help anyone, least of all him :-) Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Patch to try (was Re: Wierd AMD panics caused by VMWare?)
Please try the following patch and tell me if the crashes still occur.
If this fixes the problem then I'm homing in on the bug.
I am beginning to suspect that there is a case where a pmap can get
cleared without the tlb being flushed, causing origpte to be 0 when the
new pte is later created again at the same spot. When the new
page is allocated and added to the pmap later on, it fails to flush
the tlb entry in pmap_enter() because it believes it does not have to.
This would explain why messing with the pmap_remove_all() case does
not do what we expect -- I suspect that routine is not being called
at all in certain cases.
I have not found the case where the pmap gets cleared without being
flushed yet but when I force the flush in pmap_enter(), it seems to
stop the crashes (but I can't be 100% sure because I had to mess
around with that file descriptor program to get it to crash the first
time).
(This patch is relative to 3.x)
-Matt
Matthew Dillon
[EMAIL PROTECTED]
Index: pmap.c
===
RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v
retrieving revision 1.219.2.6
diff -u -r1.219.2.6 pmap.c
--- pmap.c 1999/09/02 23:56:47 1.219.2.6
+++ pmap.c 2000/02/25 00:06:50
@@ -2204,7 +2204,7 @@
*/
if ((origpte ~(PG_M|PG_A)) != newpte) {
*pte = newpte | PG_A;
- if (origpte)
+ /*if (origpte)*/
invltlb_1pg(va);
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Patch to try (was Re: Wierd AMD panics caused by VMWare?)
:This would explain why messing with the pmap_remove_all() case does :not do what we expect -- I suspect that routine is not being called :at all in certain cases. : :I have not found the case where the pmap gets cleared without being :flushed yet but when I force the flush in pmap_enter(), it seems to :stop the crashes (but I can't be 100% sure because I had to mess :around with that file descriptor program to get it to crash the first :time). Is it possible that a speculative read by the cpu is causing the TLB to load the invalid pte entry after we have cleared it but before we have created a new entry? This would not cause a fault, but it would load the TLB and cause a problem when we later initialize the pte but fail to invalpg1 the VA. A sequence like this: pmap_remove_all() called on pa tlb at VA flushed (something happens to cause the cpu to load the tlb at VA without faulting). pmap_enter() called with new pte (kernel memory is freed and then later allocated again). Old contents was 0 so pmap_enter() does not flush the tlb at VA. TLB still contains the invalid pte. System resumes operation, but invalid tlb entry for VA is still in the tlb. Bewm. Personally speaking I think we should simply invalidate the tlb at VA whenever we modify a pte, no matter what the original contents of that pte was. For both 3.x and 4.x. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loadedby /boot/loader.
I can reliably reproduce this problem with the following lines in /boot/loader.conf.local splash_bmp_load="YES" bitmap_name="/boot/earth.bmp" bitmap_load="YES" I have the same VESA and splash screen options in my kernel now (sources cvsup'ed yesterday) that I did on the system previously (sources from 9/22/99). Those are the only lines in the file. If I comment them out, it boots normally. dmesg, etc. available on request. I'm also willing to try patches, etc. This is an all-IDE system. I can try enabling a splash screen on my SCSI + IDE CD system at home if you want and see if that breaks too... Let me know, Doug -- "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: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) )
At 03:22 PM 2/24/2000 -0800, Mike Smith wrote: megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 Adaptec AHA-294X Ultra SCSI host adapter scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] [3.0 GB] Then tried /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt Its slow, but the server does not crash. However, if Queing enabled, it does crash. ie. the card is still unstable. That more or less confirms what I thought. It would seem that way. Although I would have thought it would have crashed a little more consistently on LINUX. I suppose it is possible its an issue of drive compatibility and turning off the tagging avoided the issue. In that mode, the card was quite stable and performed as expected, but not quite as fast as on FreeBSD. I think I will stick to the Mylex cards for now. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Patch to try (was Re: Wierd AMD panics caused by VMWare?)
"Matthew" == Matthew Dillon [EMAIL PROTECTED] writes: Matthew Please try the following patch and tell me if the crashes Matthew still occur. If this fixes the problem then I'm homing in on Matthew the bug. Matthew I am beginning to suspect that there is a case where a Matthew pmap can get cleared without the tlb being flushed, causing Matthew origpte to be 0 when the new pte is later created again at Matthew the same spot. When the new page is allocated and added to Matthew the pmap later on, it fails to flush the tlb entry in Matthew pmap_enter() because it believes it does not have to. Matthew This would explain why messing with the pmap_remove_all() Matthew case does not do what we expect -- I suspect that routine is Matthew not being called at all in certain cases. Matthew I have not found the case where the pmap gets cleared Matthew without being flushed yet but when I force the flush in Matthew pmap_enter(), it seems to stop the crashes (but I can't be Matthew 100% sure because I had to mess around with that file Matthew descriptor program to get it to crash the first time). So... to get this straight, you'd like us to back out that other patch and apply this one? I have to be honest that the machine that we have is only doing this once a month because we kept adding RAM to it until it stopped exhibiting the symptoms often. If it helps, it appears to us that 3.0 didn't have the problem and 3.2 did. 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
anon FTP setup on Feb 23 SNAP
The first time I thought I made a typo, but the second time through it happened again. It seems that even if you choose NO to setup anon FTP, it still gets setup. Anyone else notice this ? This was through the standard installation. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loadedby /boot/loader.
On Thu, 24 Feb 2000, Mike Smith wrote: It seems Mike Smith wrote: That's possible; it may be that the kernel linker is calling something before you expect it to be called. Well, its rather that the delayed probe rutine I register with config_intrhook_establish() is called before interrupts are actually working, that would explain why it times out on the probe... This didn't happen before, so thats probably why it breaks... It should break SCSI systems too, ass they do the same... Hmm. You're assuming that interrupts are working when the hooks are run, rather than assuming that it's safe to do things which will subsequently cause interrupts which ought to be correctly handled. I'd hazard a guess that the presence of modules is causing the kernel linker to run and pull all the sysctl hooks for modules it's finding. I'm probably wrong, just a guess. It certainly seems like the intrhooks are called really early. I did a little bit of experimenting with this problem last night, and that's the most I found: intrhooks really seem to be called to early. I guess I'll go look up cold usage, and see if it necessarily has to be done that early. I'll also investigate that sysctl possibility. -- \\ 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] -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with IBM Netfinity 5000 Server
On Thu, 24 Feb 2000, David O'Brien wrote: On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote: I also set these flags at my /etc/make.conf CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -O6 (any -O above 3) is nonsense with the base GCC compiler. I really have to wonder what people think they are getting by using such hight -O values. I looked at the code for gcc a while back, and it looks like optimization levels of 3 and above are considered 3. So, -O6 is the same as -O3. I think gcc a long time ago had flags that went this high. I think pgcc uses -O6, though. Sometimes when using flags -mpentium -O3 -pipe, I'll get an "internal compiler error" unless I bump down the opt to -O2 or lower. This is good -- you want to have a compiler error saying the compiler can't do it, rather than having it creating the code anyway with bugs. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
I'd hazard a guess that the presence of modules is causing the kernel linker to run and pull all the sysctl hooks for modules it's finding. I'm probably wrong, just a guess. ... I'll go look up cold usage, and see if it necessarily has to be done that early. I'll also investigate that sysctl possibility. Oops. I meant sysinit, not sysctl. -- \\ 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: Problem with IBM Netfinity 5000 Server
Donn Miller wrote: I looked at the code for gcc a while back, and it looks like optimization levels of 3 and above are considered 3. So, -O6 is the same as -O3. I think gcc a long time ago had flags that went this high. I think pgcc uses -O6, though. Sometimes when using flags -mpentium -O3 -pipe, I'll get an "internal compiler error" unless I bump down the opt to -O2 or lower. This is good -- you want to have a compiler error saying the compiler can't do it, rather than having it creating the code anyway with bugs. - Donn Thanks you all, I do know gcc do nothing more as optimization levels large than 3. 3 Month ago I try install RedHat 6.1 to this IBM 5000 server, eepro100 module could only found by install and never success load this module. This Month I try install RedHat 6.2, it can found eepro100, and most important is everythings work fine !! So I think maybe FreeBSD problem only ? 3 Month ago 4.0-Current cannot see anything as I plug any PCI interface at 1th-4th slot, only can found device at 5th PCI slot. This Month 4.0-Current RC is out, I'm happy to re-build all things from cvsup source, update everything as /usr/src/UPDATE says, after reboot, I see the missing device I plug at 4th PCI slot, but after few seconds I login at console, this IBM Server direct reboot. Nothing Panic, just like M$ Windows crash = Server Reset ? After a longtime disk check, I login again, Server Reset again Don't things realy strage ? Everything wroks fine if 1th-4th PCI slot is empty, no device attached. Same kernel, Same Applications its running To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with IBM Netfinity 5000 Server
- Original Message - From: "urania" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, February 24, 2000 10:05 PM Subject: Re: Problem with IBM Netfinity 5000 Server Thanks you all, I do know gcc do nothing more as optimization levels large than 3. 3 Month ago I try install RedHat 6.1 to this IBM 5000 server, eepro100 module could only found by install and never success load this module. This Month I try install RedHat 6.2, it can found eepro100, and most important is everythings work fine !! So I think maybe FreeBSD problem only ? 3 Month ago 4.0-Current cannot see anything as I plug any PCI interface at 1th-4th slot, only can found device at 5th PCI slot. This Month 4.0-Current RC is out, I'm happy to re-build all things from cvsup source, update everything as /usr/src/UPDATE says, after reboot, I see the missing device I plug at 4th PCI slot, but after few seconds I login at console, this IBM Server direct reboot. Nothing Panic, just like M$ Windows crash = Server Reset ? After a longtime disk check, I login again, Server Reset again Don't things realy strage ? Everything wroks fine if 1th-4th PCI slot is empty, no device attached. Same kernel, Same Applications its running aren't pci slots 1 through 4 "hot-pluggable" on the '5000? - jason allum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loadedby /boot/loader.
On Thu, 24 Feb 2000, Mike Smith wrote: I'd hazard a guess that the presence of modules is causing the kernel linker to run and pull all the sysctl hooks for modules it's finding. I'm probably wrong, just a guess. ... I'll go look up cold usage, and see if it necessarily has to be done that early. I'll also investigate that sysctl possibility. Oops. I meant sysinit, not sysctl. Well, I don't think that's it. I've tried moving it around a bit. None of the code is called until the intrhook handler is called back, so I don't see how it can be the sysinit itself causing the failure. -- \\ 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] -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: anon FTP setup on Feb 23 SNAP
I just did an install of the Feb 22 snap. The new wording for the anon ftp section is really screwy. It's been turned around. The old straight forward "Do you want to enable anon ftp?" was fine. Hrmm. -Bill On Thu, Feb 24, 2000 at 08:57:11PM -0500, Mike Tancsa wrote: The first time I thought I made a typo, but the second time through it happened again. It seems that even if you choose NO to setup anon FTP, it still gets setup. Anyone else notice this ? This was through the standard installation. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: anon FTP setup on Feb 23 SNAP
I just did an install of the Feb 22 snap. The new wording for the anon ftp section is really screwy. It's been turned around. The old straight forward "Do you want to enable anon ftp?" was fine. It's been turned around because people usually just hit return without reading the dialogs and I didn't think defaulting to anonymous ftp access was an especially good idea. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with -current snapshot of 02242000
Tried to install the snapshot, but it hangs at Probing devices. ALT-F2 shows as last entry: DEBUG: Found a disk device named mlxd0 Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL will ask if you really want to stop the install. System is an AMD K7-750, 256MB memory, some Matrox Millinium PCI card, Intel fxp, Mylex AcceleRaid 250 controller. Any ideas ? Mike ? -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: anon FTP setup on Feb 23 SNAP
At 07:51 PM 2/24/2000 -0800, Bill Swingle wrote: I just did an install of the Feb 22 snap. The new wording for the anon ftp section is really screwy. It's been turned around. The old straight forward "Do you want to enable anon ftp?" was fine. Hrmm. OK, I am embarrassed now :-) I cant believe I didnt read the damn prompt. Its a good thing I didnt have a dialog box ask me today, "Destory the Hard drive ? Yes/No" ;-) One of those days... ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mergemaster fail with crypto changes
Hi all,
I don't have crypto in my source tree, because I'm in Japan,
I get following error using mergemaster.
--8-8-Cut here-8-8-
# mergemaster
install: /usr/src/etc/../crypto/openssh/ssh_config: No such file or directory
*** Error code 71
Stop in /usr/src/etc.
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the
temproot environment
--8-8-Cut here-8-8-
In /usr/src/etc/Makefile (rev 1.214), it should check for existance of
crypto directory.
--- Makefile.ctmFri Feb 25 11:53:34 2000
+++ MakefileFri Feb 25 13:47:10 2000
@@ -20,7 +20,7 @@
${.CURDIR}/../usr.bin/mail/misc/mail.rc \
${.CURDIR}/../usr.bin/locate/locate/locate.rc
-.if !defined(NO_OPENSSH)
+.if exists(${.CURDIR}../crypto) !defined(NO_OPENSSH)
BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \
${.CURDIR}/../crypto/openssh/sshd_config
.endif
=--
_ _Munehiro (haro) Matsuda
-|- /_\ |_|_| Office of Business Planning Development, Kubota Corp.
/|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome
Chuo-ku Tokyo 103, Japan
Tel: +81-3-3245-3318 Fax: +81-3-32454-3315
Email: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: anon FTP setup on Feb 23 SNAP
On Thu, Feb 24, 2000 at 08:29:01PM -0800, Jordan K. Hubbard wrote: I just did an install of the Feb 22 snap. The new wording for the anon ftp section is really screwy. It's been turned around. The old straight forward "Do you want to enable anon ftp?" was fine. It's been turned around because people usually just hit return without reading the dialogs and I didn't think defaulting to anonymous ftp access was an especially good idea. :) I agree but the wording is a bit weird. Maybe it should read: "Do you want to enable anon ftp?" but if they just hit return it defaults to no. -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mergemaster fail with crypto changes
While I was working on this project before I found out that Mark was 95%
done already, I made those tests be:
.in !defined(NO_OPENSSH) !defined(NOCRYPT)
NOCRYPT has been the standard way of indicating that the cryptograph
package has not been installed.
Jim Bloom
[EMAIL PROTECTED]
Munehiro Matsuda wrote:
Hi all,
I don't have crypto in my source tree, because I'm in Japan,
I get following error using mergemaster.
--8-8-Cut here-8-8-
# mergemaster
install: /usr/src/etc/../crypto/openssh/ssh_config: No such file or directory
*** Error code 71
Stop in /usr/src/etc.
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the
temproot environment
--8-8-Cut here-8-8-
In /usr/src/etc/Makefile (rev 1.214), it should check for existance of
crypto directory.
--- Makefile.ctmFri Feb 25 11:53:34 2000
+++ MakefileFri Feb 25 13:47:10 2000
@@ -20,7 +20,7 @@
${.CURDIR}/../usr.bin/mail/misc/mail.rc \
${.CURDIR}/../usr.bin/locate/locate/locate.rc
-.if !defined(NO_OPENSSH)
+.if exists(${.CURDIR}../crypto) !defined(NO_OPENSSH)
BIN1+= ${.CURDIR}/../crypto/openssh/ssh_config \
${.CURDIR}/../crypto/openssh/sshd_config
.endif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: anon FTP setup on Feb 23 SNAP
I agree but the wording is a bit weird. Maybe it should read: "Do you want to enable anon ftp?" but if they just hit return it defaults to no. There's no way to make a libdialog yes/no requestor "default to no" or I'd have done exactly that. C'mon, give me at least minimum credit for having thought this out. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth ceff744c subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Marathon
At 04:33 PM 2/24/00 -0800, Kris Kennaway wrote: On Thu, 24 Feb 2000, Jeffrey J. Mountin wrote: So when is this event scheduled to end, so we can go for a test drive? 57^H^H61 commits to -current and counting... The last message to show up in the series said Mark was finished and about to collapse unconscious, so I guess that means "let the bug reports begin"! Please check that your bug hasn't already been reported before mailing, though, eh? Making Mark pass out again in fright due to 3000 new messages in -current when he wakes up won't help anyone, least of all him :-) Looks like 61 messages for 209 deltas is the final total, but may have missed a few messages, since I didn't find the "done" part. No to mention my CVSup output shows DG following right behind him. 'Cept it looks like Brian F impersonating him. shrug No matter, build in progress. Dependant ports to follow. Hmmm... maybe should have toasted the RSAref port, then build, then install and see if the "just works" part mentioned does work Why not in progress... kudos/complaints to follow. ;) As for checking first. Usually wait a day before even building, but tend to get a bit more adventuresome around release time. Otherwise my build dies and it's usually fixed or at least spoken for. 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: Problems with -current snapshot of 02242000
Tried to install the snapshot, but it hangs at Probing devices. ALT-F2 shows as last entry: DEBUG: Found a disk device named mlxd0 Verbose boot seems not to show more. System is still active, ALT-CONTROL-DEL will ask if you really want to stop the install. System is an AMD K7-750, 256MB memory, some Matrox Millinium PCI card, Intel fxp, Mylex AcceleRaid 250 controller. Any ideas ? Mike ? This is a weird one; I've seen it a couple of times now. Try hitting Esc or Enter _once_ on the vty with the "probing devices" message. It almost looks like something's losing the display update... -- \\ 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
IPSec/VPN Config
Hi all, Is there a howto/example guide for configuring IPSec for -current. Needless to say I've spent fruitless hours trying to convince "setkey" to sent an IPSec packet to my network's internet gateway w/o success. My setup is typical: mobile/dynamic-assigned-ip-address freebsd box trying to contact fixed address/private address network/(net 10)/ network via an Ascend router with IPSec support. But according to "tcpdump" my IPSec packets never leave. Help would be appreciated. Thanks a bunch. Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs commit: src/sys/boot/common load_elf.c module.c (fwd)
For all of you seeing problems with eg. the if_xl module's dependancies on the miibus module, this should be the cure. --- Forwarded Message Return-Path: msmith Delivered-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] Received: from hub.freebsd.org by localhost with POP3 (fetchmail-5.1.2) for msmith@localhost (single-drop); Thu, 24 Feb 2000 22:46:09 -0800 (PST) Received: by hub.freebsd.org (Postfix, from userid 538) id A3E2637BE11; Thu, 24 Feb 2000 21:10:48 -0800 (PST) Delivered-To: [EMAIL PROTECTED] Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DD14D37BE06; Thu, 24 Feb 2000 21:10:46 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: (from bp@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA99104; Thu, 24 Feb 2000 21:10:46 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Message-Id: [EMAIL PROTECTED] From: Boris Popov [EMAIL PROTECTED] Date: Thu, 24 Feb 2000 21:10:46 -0800 (PST) To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/boot/common load_elf.c module.c Sender: [EMAIL PROTECTED] Precedence: bulk X-UIDL: 655f06170f338e0f7535db07e4c59457 bp 2000/02/24 21:10:45 PST Modified files: sys/boot/common load_elf.c module.c Log: Fix the loader to handle module dependencies properly. More fixes will be provided after modmetadata appears in the kernel. Reviewed by: msmith Approved by: jkh Revision ChangesPath 1.13 +9 -40 src/sys/boot/common/load_elf.c 1.13 +75 -71src/sys/boot/common/module.c --- End of Forwarded Message -- \\ 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: IPSec/VPN Config
Hi all, Is there a howto/example guide for configuring IPSec for -current. Hi, I prepared one and sent the patches to freebsd-doc yesterday. I'll attach IPsec part from the document to end of this mail. Also, http://www.kame.net/newsletter/19991007/ might have better description about IPsec tunnel setup. Thanks, Yoshinobu Inoue Needless to say I've spent fruitless hours trying to convince "setkey" to sent an IPSec packet to my network's internet gateway w/o success. My setup is typical: mobile/dynamic-assigned-ip-address freebsd box trying to contact fixed address/private address network/(net 10)/ network via an Ascend router with IPSec support. But according to "tcpdump" my IPSec packets never leave. Help would be appreciated. Thanks a bunch. Kent --- +IPsec + +The current KAME supports both transport mode and tunnel mode. +However, tunnel mode comes with some restrictions. + +IPsec requires fairly complex configuration, so here we show transport +mode only. http://www.kame.net/newsletter/ has more comprehensive +examples. + +Let's setup security association to deploy a secure channel between +HOST A (10.2.3.4) and HOST B (10.6.7.8). Here we show a little +complicated example. From HOST A to HOST B, only old AH is used. +From HOST B to HOST A, new AH and new ESP are combined. + +Now we should choose algorithm to be used corresponding to "AH"/"new +AH"/"ESP"/"new ESP". Please refer to the "setkey" man page to know +algorithm names. Our choice is MD5 for AH, new-HMAC-SHA1 for new AH, +and new-DES-expIV with 8 byte IV for new ESP. + +Key length highly depends on each algorithm. For example, key +length must be equal to 16 bytes for MD5, 20 for new-HMAC-SHA1, +and 8 for new-DES-expIV. Now we choose "MYSECRETMYSECRET", +"KAMEKAMEKAMEKAMEKAME", "PASSWORD", respectively. + +OK, let's assign SPI (Security Parameter Index) for each protocol. +Please note that we need 3 SPIs for this secure channel since three +security headers are produced (one for from HOST A to HOST B, two for +from HOST B to HOST A). Please also note that SPI MUST be greater +than or equal to 256. We choose, 1000, 2000, and 3000, respectively. + + +(1) + HOST A -- HOST B + + (1)PROTO=AH + ALG=MD5(RFC1826) + KEY=MYSECRETMYSECRET + SPI=1000 + +(2.1) + HOST A -- HOST B + -- +(2.2) + + (2.1) + PROTO=AH + ALG=new-HMAC-SHA1(new AH) + KEY=KAMEKAMEKAMEKAMEKAME + SPI=2000 + + (2.2) + PROTO=ESP + ALG=new-DES-expIV(new ESP) + IV length = 8 + KEY=PASSWORD + SPI=3000 + +Now, let's setup security association. Execute "setkey" on both HOST +A and B: + +# setkey -c +add 10.2.3.4 10.6.7.8 ah 1000 -m transport -A keyed-md5 "MYSECRETMYSECRET" ; +add 10.6.7.8 10.2.3.4 ah 2000 -m transport -A hmac-sha1 "KAMEKAMEKAMEKAMEKAME" ; +add 10.6.7.8 10.2.3.4 esp 3000 -m transport -E des-cbc "PASSWORD" ; +^D + +Actually, IPsec communication doesn't process until security policy +entries will be defined. In this case, you must setup each host. + +At A: +# setkey -c +spdadd 10.2.3.4 10.6.7.8 any -P out ipsec + ah/transport/10.2.3.4-10.6.7.8/require ; +^D + +At B: +spdadd 10.6.7.8 10.2.3.4 any -P out ipsec + esp/transport/10.6.7.8-10.2.3.4/require ; +spdadd 10.6.7.8 10.2.3.4 any -P out ipsec + ah/transport/10.6.7.8-10.2.3.4/require ; +^D + +To utilize the security associations installed into the kernel, you +must set the socket security level by using setsockopt(). +This is per-application (or per-socket) security. For example, +the "ping" command has the -P option with parameter to enable AH and/or ESP. + +For example: +% ping -P "out ipsec \ + ah/transport/10.0.1.1-10.0.2.2/use \ + esp/tunnel/10.0.1.1-10.0.1.2/require" 10.0.2.2 + +If there are proper SAs, this policy specification causes ICMP packet +to be AH transport mode inner ESP tunnel mode like below. + + HOST C --- GATEWAY D -- HOST E + 10.0.1.110.0.1.2 10.0.2.1 10.0.2.2 + | | || + | === ESP ===| + AH == + + end of USAGE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with IBM Netfinity 5000 Server
On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA [EMAIL PROTECTED] wrote: I've a Netfinity 5000 Server, internal 5 PCI slot onborad. If i put one Intel 82558 NIC at 5th PCI Slot, everythings goes fine. Every times i put the same Intel NIC to any other PCI slots ( 1th ~ 4th ), after system login prompt , i also login as root, then system direct reboot # I also set these flags at my /etc/make.conf # CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations # # To avoid building various parts of the base system: NO_SENDMAIL= true #NO_CVS= true # # To compile just the kernel with special optimisations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway): # COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops Please forget the "special" optimization parameters and compile world and kernel with standard -O -pipe. Make sure you don't have any unusual tweaks anywhere. Then compile GENERIC kernel and try it out. I don't think the optimizing compiler is bad idea but I haven't seen any significant gains versus dying kernels and weird acting standard system binaries. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! OpenSSH is about to enter the tree.
At 11:37 PM -0800 2/23/00, Jordan K. Hubbard wrote: Since it came down to making openssl actually useful for something or taking it out of the tree, we accelerated progress somewhat on the openssh integration work. Sounds like a good idea. I will also be delaying -current's release date until March 10th in order to give this more proper testing. I think it's worth the wait to have openssh included. One minor thought. In OpenBSD there is still a port for ssh1, and they have it so the port for ssh1 starts that up on port 2022. We (at RPI) have found a few ssh clients that do not work well with openssh, and I think it would be a good idea to do something similar to what openbsd did with the port for ssh1. (maybe not exactly the same -- maybe have it just some messages that the ssh1-build process will print out so people are aware of that option. 4.0-release wouldn't have to wait for those adjustments to the ssh1 port, of course) --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0 wierdness with Compex Freedomline
On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser [EMAIL PROTECTED] said: The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps-MB/s you divide by 8] I realize my punctuation may be off, but there you are. Assuming you mean ``100BASE-T (half duplex)'' here... This is not quite right. In a CSMA/CD medium access protocol, like that used by Ethernet, the actual capacity of the link is always(*) somewhat less than 100%; the exact value depends on the precise parameters of the transmissions at both ends.(**) -GAWollman (*)In non-trivial conditions; i.e., when actual work is being done. (**)I've heard numbers between 70% and 95%. -- 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: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) )
Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware up within a few minutes. The Dell 3.00 firmware remains stable under the same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a firmware lockup - the SCSI bus is hung and usually the PCI bus as well. I am going to test the card in another older MB to see if its some strange interaction. What MB chipset are you using to test with ? I've been testing most recently with the Intel 450NX and AMD 751. OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but it crashes hard when you write to the partition. I am going to try and reflash the card to the latest AMI BIOS and see what happens. How about with FreeBSD and the Dell firmware? Let's keep the number of variables down. 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: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
It seems Mike Smith wrote: Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? We've seen this before, but back then no solution was found either, it dissaperead all by itself... ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
natd, firewall, and RFC1918...?
I have been wondering what the right answer to this scenario is. Here is the scenario: machine A -- outside ip (internet) machine B -- router, natd, registered ip and set to stop RFC1918 on the public interface machine C -- inside LAN, unregisterd ip 192.168.0.0/16 When I connect to machine A from machine C, machine B (natd) seems to translate the addresses correctly like this: Out [TCP] "machine C's ip" -- "machine A's ip" aliased to [TCP] "machine B's ip" -- "machine A's ip" but when the packet comes back in, I get this: In [TCP] "machine A's ip" -- "machine B's ip" aliased to [TCP] "machine A's ip" -- "machine C's ip" ^ ^ ^ ^ ^ ^ ^ ^ and this brakes my ipfw rule of: "deny ip from any to 192.168.0.0/16 via outside_interface" ... which is part of the example from rc.firewall "stopping RFC1918 on the public interface." So, I always just delete this rule to get the packet inside the LAN. questions are: 1. Is this right? Is natd behaving correctly when the packet comes back in for unregistered ips? I would think that it would be aliased to like this, "machine B's ip" -- machine C's ip" like a proxy? But this would still break the rule "... from any ...". 2. If so, is it correct to not include the ipfw rule above when stopping RFC1918? Better yet, what is the correct way of writing the rule? correct me if my assumptions are wrong. using 4.0current-2000.02.14 --- arnee To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0 wierdness with Compex Freedomline
On Thu, Feb 24, 2000 at 07:48:35PM +0100, Dieter Rothacker wrote: No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX cables are used simultaneous. Due to the small ethernet frame size, it is next to impossible to get the full speed for data transmission. You're right, I stand corrected. FDX is 100Mbps wide, but bi-directional, so it's only 12MB/s maximum theoretical speed (not including protocol overhead and what-not) .. I was basing the original opinion posted on assumed total bandwidth (100Mbps both ways) which is incorrect. I apologize for my ignorance :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. Soren - this is somewhat of a showstopper. Can you reproduce it there? ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa040) Mounting root from ufs:/dev/ad0s3a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 If at the boot prompt I: unload load kernel boot there's no problem. Also there's no problem if loading modules from /boot/loader.conf with a kernel suped and built on Feb. 17th with today's buildworld. Mike Smith wrote: it does : I've tried loading miibus alone : works fine loading miibus, then if_xl : loops in loading miibus Ok. We know that hurts, don't do that. 8) From the above remark should I conclude that it's a known problem and we should refrain from loading modules from the boot loader until it works? Or would it help send boot_verbose output from my kernel as well? -- Yarema To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ 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
/usr/share/examples/kld/cdev broken
Hi, It seems that /usr/share/examples/kld/cdev example is broken for a long time, which obviously not we want for 4.0-RELEASE. Could someone review my docs/16173 PR and commit it with corrections if it will be necessary (I'm really not very prominent as a kld hacker)? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USA_RESIDENT= in latest current
Perhaps, but take a look at the installation... it sets it to USA_RESIDENT="YES" (note WITH quotes). Fixed, whoops! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: disklabels partition sizes differ from FreeBSDs syslog messages on mounting
On Thu, Feb 24, 2000 at 05:43:04AM +1100, Bruce Evans wrote: what do you mean exactly with "old systems" ? FreeBSD-3.x, or FreeBSD--current with the wd driver. Oh, that you mean ... Well but I'm running a very up to date -current. FreeBSD titan.klemm.gtn.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Feb 22 12:11:23 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/TITAN i386 I even updated the boot loader by cd /usr/src/sys/boot make clean all install -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loadedby /boot/loader.
On Thu, 24 Feb 2000, Soren Schmidt wrote: It seems Mike Smith wrote: Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? We've seen this before, but back then no solution was found either, it dissaperead all by itself... Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW. Nick spent a couple of hours looking at it without much success. I'll try some things today to see if the probe is being called with interrupts disabled. -- 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
dc0 wierdness with Compex Freedomline
Hello, I am experiencing some weird problems with the dc-driver for a specific ethernet-card ... the Compex Freedomline (10/100 Mbps). The card perfectly seems to autodetect the mode it should operate on and seems to indeed be working just fine just after the system has booted up. --[dmesg]--- dc0: Intel 21143 10/100BaseTX port 0xb400-0xb47f mem 0xdd00-0xdd7f irq 11 at device 12.0 on pci0 dc0: Ethernet address: 00:80:48:e7:1a:8e miibus0: MII bus on dc0 dcphy0: Intel 21143 NWAY media interface on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto --[ifconfig]-- sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 130.89.226.126 netmask 0x broadcast 130.89.255.255 ether 00:80:48:e7:1a:8e media: autoselect (100baseTX full-duplex) status: active supported media: autoselect 100baseTX full-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP 100baseTX hw-loopback none Downloading an 128 MB-file from the network to /dev/null results in speeds like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) After a (little) while though network performance almost comes to a halt somewhere around 6 to 32 kB/s ... and never seems to "recover" again. --[uname]-- FreeBSD cam043216.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Feb 19 10:29:30 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/DINGO i386 Anybody that could help me out trying to figure out why the card seems to break down like this ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: natd, firewall, and RFC1918...? apologies!
sorry, i'm suppose to post this under freebsd-questions. this should teach me posting early in the morning :-) To continue the questions... if the sample ipfw rule "deny all from any to 192.168.0.0/16 via outside_interfaces" doesn't always work. Should it be included in the rc.firewall example? arnee wrote: I have been wondering what the right answer to this scenario is. Here is the scenario: machine A -- outside ip (internet) machine B -- router, natd, registered ip and set to stop RFC1918 on the public interface machine C -- inside LAN, unregisterd ip 192.168.0.0/16 When I connect to machine A from machine C, machine B (natd) seems to translate the addresses correctly like this: Out [TCP] "machine C's ip" -- "machine A's ip" aliased to [TCP] "machine B's ip" -- "machine A's ip" but when the packet comes back in, I get this: In [TCP] "machine A's ip" -- "machine B's ip" aliased to [TCP] "machine A's ip" -- "machine C's ip" ^ ^ ^ ^ ^ ^ ^ ^ and this brakes my ipfw rule of: "deny ip from any to 192.168.0.0/16 via outside_interface" ... which is part of the example from rc.firewall "stopping RFC1918 on the public interface." So, I always just delete this rule to get the packet inside the LAN. questions are: 1. Is this right? Is natd behaving correctly when the packet comes back in for unregistered ips? I would think that it would be aliased to like this, "machine B's ip" -- machine C's ip" like a proxy? But this would still break the rule "... from any ...". 2. If so, is it correct to not include the ipfw rule above when stopping RFC1918? Better yet, what is the correct way of writing the rule? correct me if my assumptions are wrong. using 4.0current-2000.02.14 --- arnee 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
strange things ...
I cvsup'd this morning the sources, the original installed system was 4.0-2214. Built a new kernel, installed it, rebooted - locked out? Huh ... root's password won't run anymore and I have no glue why ... Gruss O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
I'm also experiencing this under current since the Mega Patch, I'm running on Celeron 500. Asus P99B Board (2 IDE, 128MB Ram, 4.3 GB Hard Disk). But if I don't load any modules, it works fine.
Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) )
At 12:26 AM 2/24/2000 -0800, Mike Smith wrote: OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but it crashes hard when you write to the partition. I am going to try and reflash the card to the latest AMI BIOS and see what happens. How about with FreeBSD and the Dell firmware? Let's keep the number of variables down. 8) I cant disklabel the drive when using the 3.00 firmware from dell. newmail# disklabel -Brw amrd0 auto newmail# disklabel -e amrd0 disklabel: ioctl DIOCGDINFO: Invalid argument Its entirely possible the card is cooked. I am going to test the latest firmware with LINUX when I get back to the office today. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: natd, firewall, and RFC1918...? apologies!
On Thu, Feb 24, 2000 at 04:13:34AM -0800, arnee wrote:
sorry, i'm suppose to post this under freebsd-questions. this should teach
me posting early in the morning :-)
To continue the questions... if the sample ipfw rule "deny all from any to
192.168.0.0/16 via outside_interfaces" doesn't always work. Should it be
included in the rc.firewall example?
Please see PR conf/13769 for the same problem and a possible workaround.
Note, that:
: After translation by natd, packets re-enter the firewall at the rule
: number following the rule number that caused the diversion (not the
: next rule if there are several at the same number).
Depending on the actual config, there could be a clean solution for this
problem. For example, I use dedicated IP number for NATD, and my NATD
rules look very close to the following:
# Outside interface ruleset
${IPFW} add 5 skipto 6 ip from any to ${ALIAS_IP} in
...
# Stop RFC1918 nets usage on the outside interface
${IPFW} add reject log ip from ${RFC1918_A} to any
${IPFW} add reject log ip from ${RFC1918_B} to any
${IPFW} add reject log ip from ${RFC1918_C} to any
${IPFW} add deny log ip from any to ${RFC1918_A}
${IPFW} add deny log ip from any to ${RFC1918_B}
${IPFW} add deny log ip from any to ${RFC1918_C}
...
# IP de-aliasing
${IPFW} add 6 divert natd ip from any to ${ALIAS_IP} in
# Deny log everything that isn't de-aliased
${IPFW} add deny log ip from any to ${ALIAS_IP} in
# Pass all that is de-aliased
${IPFW} add allow ip from any to any in
Also, the description of how packets re-enter firewall filter provided
in etc/rc.firewall is obsoleted and should be replaced to match the
reality. I will fix that. If you have something to say further, please
followup on PR 13769.
arnee wrote:
I have been wondering what the right answer to this scenario is. Here is
the scenario:
machine A -- outside ip (internet)
machine B -- router, natd, registered ip and set to stop RFC1918 on the
public interface
machine C -- inside LAN, unregisterd ip 192.168.0.0/16
When I connect to machine A from machine C, machine B (natd) seems to
translate the addresses correctly like this:
Out [TCP] "machine C's ip" -- "machine A's ip" aliased to
[TCP] "machine B's ip" -- "machine A's ip"
but when the packet comes back in, I get this:
In [TCP] "machine A's ip" -- "machine B's ip" aliased to
[TCP] "machine A's ip" -- "machine C's ip"
^ ^ ^ ^ ^ ^ ^ ^
and this brakes my ipfw rule of:
"deny ip from any to 192.168.0.0/16 via outside_interface" ... which is
part of the example from rc.firewall "stopping RFC1918 on the public
interface." So, I always just delete this rule to get the packet inside
the LAN.
questions are:
1. Is this right? Is natd behaving correctly when the packet comes back
in for unregistered ips? I would think that it would be aliased to like
this, "machine B's ip" -- machine C's ip" like a proxy? But this
would still break the rule "... from any ...".
2. If so, is it correct to not include the ipfw rule above when stopping
RFC1918? Better yet, what is the correct way of writing the rule?
correct me if my assumptions are wrong.
using 4.0current-2000.02.14
---
arnee
--
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
Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) )
At 12:26 AM 2/24/00 -0800, Mike Smith wrote: OK, on the PERC2/SC and LINUX with the firmware from Dell (3.00), it pukes with Redhat LINUX. I am able to talk to the card, fdisk and newfs it, but it crashes hard when you write to the partition. I am going to try and reflash the card to the latest AMI BIOS and see what happens. How about with FreeBSD and the Dell firmware? Let's keep the number of variables down. 8) OK, I have flashed the BIOS of the card to the latest version from AMI, and booted it up with RedHAT (latest kernel compiled) with various patches, and the driver compiled directly into the kernel, not as a module. Note, these are the drivers that come with RedHAT. I havent tried the RPMs directly from AMI/Dell megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 Adaptec AHA-294X Ultra SCSI host adapter scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns megaraid: v107 (December 22, 1999) megaraid: found 0x8086:0x1960:idx 0:bus 0:slot 10:func 1 scsi1 : Found a MegaRAID controller at 0xd0002000, IRQ: 12 megaraid: [GH6D:1.43] detected 1 logical drives scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.25/3.2.4 Adaptec AHA-294X Ultra SCSI host adapter scsi1 : AMI MegaRAID GH6D 254 commands 16 targs 1 chans 8 luns SCSI device sdc: hdwr sector= 512 bytes. Sectors= 6199296 [3027 MB] [3.0 GB] Then tried /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt /usr/local/bin/bonnie -s 100 -d /mnt Its slow, but the server does not crash. However, if Queing enabled, it does crash. However, this could be due to the old Segates ( ST31055W ) that I am using to test with. I did try the same on FreeBSD, but it did not have any positive effect. So it seems the card does work... ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
http download of iso ??
Is it possible to get the RC2 iso via http?? The reason I ask is that the firewall here blocks ftp. PS...Please email directly as this address is not on the mailing list Thank you, William To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange things ...
On Thu, 24 Feb 2000, O. Hartmann wrote: I cvsup'd this morning the sources, the original installed system was 4.0-2214. Built a new kernel, installed it, rebooted - locked out? Huh ... root's password won't run anymore and I have no glue why ... You were using DES crypt libraries but didn't install them in the upgrade. Add the "DES" distribution in sysinstall, or the crypto/ and secure/ source directories and rebuild. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
Soren Schmidt wrote: It seems Mike Smith wrote: Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? We've seen this before, but back then no solution was found either, it dissaperead all by itself... -Søren Perhaps this will help. Attached is a copy of a boot_verbose dmesg when my box DOES boot. When it does NOT boot the screen shows something like this: ... Device configuration finished. bpf: lo0 attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default Linux-ELF exec handler installed IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed no devsw (majdev=0 bootdev=0xa020) Mounting root from ufs:/dev/ad0s1a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 ... Seems like it craps out right after the linux module kicks in at 'Linux-ELF exec handler installed'. The platform in this case is a Celleron 466/ASUS MES-N/SiS® 620 AGPset. http://www.asus.com.tw/products/motherboard/pentiumpro/mes-n/index.html http://www.sis.com.tw/products/pentium2/620.htm Hope this helps. Incidentally ata(4) states: The currently supported controllers with their maximum speed include: ... SiS 5591 Ultra DMA 33 (UDMA2), 33 MB/sec ... yet the above URL claims: The IDE controller is ATA-3 compliant, supporting PIO mode 0/1/2/3/4, DMA multiword 0/1/2 and Ultra DMA 33/66 operations. The two IDE channels are fully independent with dedicated 16 double-word FIFO built-in. I understand there's little (if any) perfrmance difference between UDMA33 and UDMA66. Just wondering why UDMA66 was not supported for this controller. -- Yarema Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Wed Feb 23 11:03:02 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ASUSMESN Calibrating clock(s) ... TSC clock: 466827092 Hz, i8254 clock: 1193128 Hz Timecounter "i8254" frequency 1193128 Hz Timecounter "TSC" frequency 466827092 Hz CPU: Pentium II/Pentium II Xeon/Celeron (466.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 266326016 (260084K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x00369000 - 0x0fdf4fff, 262717440 bytes (64140 pages) avail memory = 254541824 (248576K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f99d0 bios32: Entry = 0xf04c0 (c00f04c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x4f0 pnpbios: Found PnP BIOS data at 0xc00fca10 pnpbios: Entry = f:ca40 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f54a0 Preloaded elf kernel "kernel" at 0xc035. VESA: information block 56 45 53 41 00 02 00 01 00 01 04 00 00 00 22 00 00 01 20 00 00 01 14 01 00 01 36 01 00 01 40 01 00 01 00 01 01 01 03 01 05 01 07 01 21 01 80 01 81 01 82 01 89 01 8d 01 0d 01 10 01 13 01 16 01 VESA: 35 mode(s) found VESA: v2.0, 2048k memory, flags:0x4, mode table:0xc02f0ea2 (122) VESA: SiS VESA: Silicon Integrated Systems Corp. 6306 0A Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1):mode 1 addr port (0x0cf8) is 0x80010010 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=06201039) devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=06201039) pcib0: Host to PCI bridge on motherboard found- vendor=0x1039, dev=0x0620,
Re: dc0 wierdness with Compex Freedomline
On Thu, Feb 24, 2000 at 12:04:38PM +0100, Pascal Hofstee wrote: media: autoselect (100baseTX full-duplex) Downloading an 128 MB-file from the network to /dev/null results in speeds like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps-MB/s you divide by 8] I realize my punctuation may be off, but there you are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0 wierdness with Compex Freedomline
Don't forget protocol overhead. Chris Wasser wrote: On Thu, Feb 24, 2000 at 12:04:38PM +0100, Pascal Hofstee wrote: media: autoselect (100baseTX full-duplex) Downloading an 128 MB-file from the network to /dev/null results in speeds like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps-MB/s you divide by 8] I realize my punctuation may be off, but there you are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- PETER SCHWENK| UNIX System Administrator Department of Mathematical Sciences | University of Delaware [EMAIL PROTECTED]| (302)831-0437 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
It seems Mike Smith wrote: Forgive me if I'm beating a dead horse... I'm still having the following problem if I load any modules from /boot/loader.conf: I've reproduced this here, and narrowed it down to Soren's ATA megacommit on the 18th. Unfortunately, the newbus patches (tested) and the other gunk (untested) ended up lumped in together, and I'm not having a lot of luck working out what exactly might be causing this. That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. You didn't mention the 0xa5 test, and I forgot to tell you that I backed it out as well (no change). Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. Try a network interface module, if you haven't already. I was loading if_wi. The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? That's possible; it may be that the kernel linker is calling something before you expect it to be called. Also, I note that you've only partially newbussed the code; I don't see any busspace/busdma stuff in there. Is there another megapatch coming? -- \\ 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: Crashing netscape?
On Tue, 22 Feb 2000, Alexander Leidinger wrote: But this didn't solve the crash at exit. But... rm -rf /usr/lib/compat/* cd /usr/src/lib/compat/compat22/ make all install clean cd ../compat3x.i386/ make all install clean solved this for me (YMMV). After doing this, I noticed some crud lying around on my machine that might have been contributing to problems for me. I noticed that the aout version of libc was coming from /usr/lib/aout, which I guess is an old place that libraries were kept. This is probably one more thing people can look for to ensure that they are using the newest versions of the compatibility libraries. Alex. -- alex varju [EMAIL PROTECTED] just a guy webct canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0 wierdness with Compex Freedomline
On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser wrote: Downloading an 128 MB-file from the network to /dev/null results in speeds like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network) The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s (megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps-MB/s you divide by 8] I realize my punctuation may be off, but there you are. No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX cables are used simultaneous. Due to the small ethernet frame size, it is next to impossible to get the full speed for data transmission. -- Dieter Rothacker To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
It seems Mike Smith wrote: That megapatch was only newbus patches and cosmetics around that, one new item was cmd646 support but that is hardly the problem here. You didn't mention the 0xa5 test, and I forgot to tell you that I backed it out as well (no change). yeah, cosmetics :) Soren - this is somewhat of a showstopper. Can you reproduce it there? Nope, I've tried several machines here, no problems, even with tons of modules.. Try a network interface module, if you haven't already. I was loading if_wi. Still no problems... The only thing I can come up with is that _something_ makes the delayed probe be called _before_ interrupts are up and running. That will make it fail like this. Quuestion is is something else messing with those hooks ? That's possible; it may be that the kernel linker is calling something before you expect it to be called. Well, its rather that the delayed probe rutine I register with config_intrhook_establish() is called before interrupts are actually working, that would explain why it times out on the probe... This didn't happen before, so thats probably why it breaks... It should break SCSI systems too, ass they do the same... Also, I note that you've only partially newbussed the code; I don't see any busspace/busdma stuff in there. Is there another megapatch coming? Busspace is a joke, I'm perfectly fine with calling those macros in[bwl]/out[bwl] like they should be :) Busdma, hmm, well I dont see that helping here either And no, no more mega patches before 4.0, this should probably have waited too, but there has been pushed very stronly for this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
