-CURRENT slowdown in last 2 weeks
I am noticing a severe slowdown on my -CURRENT system. It actually started after Feb [3-5] changes in intrupt handling, but I didn't really notice until I run a make world (which I delayed doing because of, well you guess, the libc breakage). When I say severe I mean make buildworld takes x3 longer. Am I alone in this, or is it well known (even though I didn't see it discussed, but I might have overlooked)? Could it be related instead to all the lock reversal messages I've been getting ever since? I know it's an interrupt issue because it only happens when I'm exercising my HD. I guess it's time to put /usr/src and maybe even /usr/obj on an NFS server, I'm sure it can't be slower... *grin* anti-flame mode I'm not complaining, I'm offering to debug! /anti-flame mode Bye, Andrea -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest alpha breakage
I cvsup every day in periodic/daily- maybe I just missed this one. This has been dead for several days- sorryu I guess I missed your mail about it Umm... yup... sorry for the noise Matthew Jacob writes: === libcrypto ( echo "#ifndef MK1MF_BUILD"; echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */"; echo " #define CFLAGS \"cc\""; echo " #define PLATFORM \"`uname -s`-`uname -m`\""; echo " #define DATE \"`LC_TIME=C date`\""; echo "#endif" ) buildinf.h make: don't know how to make bn-alpha.pl. Stop *** Error code 2 This looks like the libcrypto breakage that I was complainging about. I thought this was fixed last night -- have you cvsup'ed recently? Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Building procedure of krb5 is broken
At 20 Feb 2001 09:44:01 GMT,
Makoto MATSUSHITA wrote:
It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to
src/kerberos5/lib/libgssapi/Makefile is required to fix this, since
krb5_err.h is not in ${KRB5DIR}/lib/krb5.
In my environment, buildworld was finished with attached patch. I
don't know KRB4 should be defined in this file or not. But in
crypto/heimdal/kdc/headers.h, krb.h (this file is not exist in heimdal
distribution) is included if KRB4 is defined.
So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is
failed because krb.h is not found.
Any ideas?
--
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
[EMAIL PROTECTED] // FreeBSD Project
krb.diff
Re: Building procedure of krb5 is broken
On Wed, Feb 21, 2001 at 10:06:29PM +0900, Jun Kuriyama wrote:
At 20 Feb 2001 09:44:01 GMT,
Makoto MATSUSHITA wrote:
It seems that add 'CFLAGS+=-I${KRB5OBJDIR}' to
src/kerberos5/lib/libgssapi/Makefile is required to fix this, since
krb5_err.h is not in ${KRB5DIR}/lib/krb5.
In my environment, buildworld was finished with attached patch. I
don't know KRB4 should be defined in this file or not. But in
crypto/heimdal/kdc/headers.h, krb.h (this file is not exist in heimdal
distribution) is included if KRB4 is defined.
So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is
failed because krb.h is not found.
Last I looked (before assar's import), MAKE_KERBEROS5=yes required
that you also have MAKE_KERBEROS4=yes due to such dependencies.
Cheers,
--
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Building procedure of krb5 is broken
"Jacques A. Vidrine" [EMAIL PROTECTED] writes: On Wed, Feb 21, 2001 at 10:06:29PM +0900, Jun Kuriyama wrote: So if MAKE_KERBEROS5=YES is set in /etc/make.conf, buildworld is failed because krb.h is not found. Last I looked (before assar's import), MAKE_KERBEROS5=yes required that you also have MAKE_KERBEROS4=yes due to such dependencies. Which is bogus. I think Jun Kuriyama's patch is correct and I'm trying it now, but buildworld takes a little while to complete :-) /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Building procedure of krb5 is broken
At 21 Feb 2001 14:19:28 +0100, Assar Westerlund wrote: Which is bogus. I think Jun Kuriyama's patch is correct and I'm trying it now, but buildworld takes a little while to complete :-) Just FYI, I've tested buildworld with that patch in environments below. :-) (1) MAKE_KERBEROS4=YES (2) MAKE_KERBEROS4=YES and MAKE_KERBEROS5=YES (3) MAKE_KERBEROS5=YES (4) No MAKE_KERBEROS* -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Building procedure of krb5 is broken
kuriyama In my environment, buildworld was finished with attached kuriyama patch. I don't know KRB4 should be defined in this file or kuriyama not. Sorry I should say when building of krb5 is failed; make buildworld seems OK, but 'make release' will fail during 'release.2' target; there is no MAKE_KERBEROS* variable definition. Anyway, I'll wait until tomorrow's job starts at current.jp.FreeBSD.org :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Building procedure of krb5 is broken
Jun Kuriyama [EMAIL PROTECTED] writes: Just FYI, I've tested buildworld with that patch in environments below. :-) (1) MAKE_KERBEROS4=YES (2) MAKE_KERBEROS4=YES and MAKE_KERBEROS5=YES (3) MAKE_KERBEROS5=YES (4) No MAKE_KERBEROS* Thanks for your testing. I've commited the fix. A, maybe this will also fix "make release". It has been dying in the kerberos area the last few days. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT slowdown in last 2 weeks
Andrea Campi wrote: I am noticing a severe slowdown on my -CURRENT system. It actually started after Feb [3-5] changes in intrupt handling, but I didn't really notice until I run a make world (which I delayed doing because of, well you guess, the libc breakage). When I say severe I mean make buildworld takes x3 longer. Hmmm. Buit world yesterday evening on a 733 VAIO, UDMA ATA drive, took around 1h15mn, which is fairly much what I would expect... U using SCSI? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernfs
It seems the error for kernfs is activating a couple of other warnings: WARNING: unknown option `KERNFS' removed from /usr/obj/home/src/sys/DCS/opt_dont use.h WARNING: option `FFS' moved from opt_ffs.h to opt_dontuse.h WARNING: unknown option `FFS_ROOT' removed from /usr/obj/home/src/sys/DCS/opt_ff s.h -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You'll never see all the places, or read all the books, but fortunately, they're not all recommended. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems syncing disks in recent -current (since 19th)
Hi Kirk, A number of us have problem reliably syncing disks with softupdates in recent -current from about the 19th. Is it possible that you broke something with your recent commit? Cheers, Joe PGP signature
MP-safe midi(4) and sequencer callout priority
The patch at http://people.FreeBSD.org/~tanimura/patches/midimutex.diff.gz makes midi(4) MP-safe. With this patch, my kernel with WITNESS and INVARIANTS plays my favorite midi tunes just fine, except that the callout used by the midi sequencer gets delayed under a heavy load. As the sequencer uses callout in order to wait until the next midi message is ready to be transmitted, the callout should run at PI_AV so that a tune will not sound messy. John, have you got any plan to modify the priority of a callout? Cameron, as pcm(4) interacts with few of the other subsystems in the kernel like midi(4), why don't you start making pcm(4) MP-safe? Multimedia devices should benefit very much from kernel execution in parallel. The only one thing to note is to not access a device in parallel to mess it up. We have to add a mutex to a device and share the mutex between the pcm part and the midi part of the driver. Could you please let me know when pcm(4) gets MP-safe, and we will see how we can share device mutexes between pcm(4) and midi(4). -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -CURRENT slowdown in last 2 weeks
On 20-Feb-01 Andrea Campi wrote: I am noticing a severe slowdown on my -CURRENT system. It actually started after Feb [3-5] changes in intrupt handling, but I didn't really notice until I run a make world (which I delayed doing because of, well you guess, the libc breakage). When I say severe I mean make buildworld takes x3 longer. Hmm, Feb 3-5 (looks). You mean the preemptive scheduling committed on Feb 1? Can you try updating to early this week to see if it goes away? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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
