Re: 1131 unneeded includes in the kernel...
UNNEEDED #includes in the FreeBSD kernel : : dev/randomdev/harvest.c sys/libkern.h sys/linker.h sys/mbuf.h dev/randomdev/hash.c dev/randomdev/yarrow.h sys/mbuf.h dev/randomdev/randomdev.c sys/rman.h sys/signalvar.h dev/randomdev/yarrow.c sys/linker.h sys/mbuf.h ... Thanks! Dealt with. M -- 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
A SMPng suggestion..
If you are running -current with the SMPng code, it would probably be very production to stick the following options in your kernel config, especially if you are having crashes: SMP_DEBUG DIAGNOSTIC INVARIANTS INVARIANT_SUPPORT Using these allow for more useful error messages allowing the developers to track down bugs that you may run into more easily. Thanks. -- 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
Re: Initial installation console
On 20-Sep-00 Alfred Perlstein wrote: * Forrest Aldrich [EMAIL PROTECTED] [000920 12:46] wrote: Can the configuration for bootup and initial installation be configured to detect (and configure) a serial console. This would be very useful for rackmount systems. Yes, I know it can be done manually after the installation is completed with a monitor; but this would save some time. If I'm missing something obvious, please let me know. I just tested it with a 2u system, booted up with a serial console, and it wasn't detected. If you boot without a keyboard attached and make sure you're using "Com1" then it should work. No, it doesn't. :( The probe keyboard option is off in both -stable and -current due to all the broken K7 motherboards running around whose keyboards weren't being recognized. If we can get some better keyboard probing code in boot2, then we can reactivate the option. However, before installing, you can mount the kernel floppy, and type 'echo -P /mnt/boot.config' and then unmount the floppy and boot from the floppies to get the old behavior. -Alfred -- 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
Re: OpenBSD errata 008 also applies to FreeBSD
On Fri, Jul 07, 2000, Marius Bendiksen wrote: It appears msdosfs is using a vnode after having released its reference on it, which could lead to a bad things under high load. I've patched the OpenBSD errata to apply cleanly to FreeBSD. Yes, I remember you bringing this up a while back. I don't see anything wrong with the patch, and the last time I applied it and tested it my box stopped panicing under a test. :) Adrian -- Adrian Chadd"The main reason Santa is so jolly is [EMAIL PROTECTED] because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenBSD errata 008 also applies to FreeBSD
It appears msdosfs is using a vnode after having released its reference on it, which could lead to a bad things under high load. I've patched the OpenBSD errata to apply cleanly to FreeBSD. Yes, I remember you bringing this up a while back. I don't see anything wrong with the patch, and the last time I applied it and tested it my box stopped panicing under a test. :) ISTR having made it available from home.eunet.no/~mbendiks as well, together with some other patches. I was planning on submitting them to the PR system RSN. Marius To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildkernel broken?
An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. - Donn {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. {standard input}:2344: Error: Subtraction of two symbols in different sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file address 940. {standard input}:2346: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 946. {standard input}:2346: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 958. {standard input}:2347: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 976. {standard input}:2349: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 982. {standard input}:2349: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 994. {standard input}:2350: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1012. {standard input}:2352: Error: Subtraction of two symbols in different sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file address 1024. {standard input}:2367: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1034. {standard input}:2372: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1051. {standard input}:2375: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1074. {standard input}:2378: Error: Subtraction of two symbols in different sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file address 1096. {standard input}:2384: Error: Subtraction of two symbols in different sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at file address 1117. {standard input}:2389: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1135. {standard input}:2392: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1154. {standard input}:2395: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1176. {standard input}:2397: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1195. {standard input}:2400: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1218. {standard input}:2402: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1237. {standard input}:2407: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1279. {standard input}:2410: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1302. {standard input}:2412: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1321. {standard input}:2418: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1363. {standard input}:2424: Error: Subtraction of two symbols in different sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file address 1405. {standard input}:2430: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1428. {standard input}:2433: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1444. {standard input}:2436: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 1467. {standard input}:2439: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1486. {standard input}:2442: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file address 1509. {standard input}:2445: Error: Subtraction of two symbols in different sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file
Re: buildkernel broken?
On Thu, Sep 21, 2000, Donn Miller wrote: An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. - Donn {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. I get that too on a source tree cvsupped about an hour or two ago. Adrian -- Adrian Chadd"The main reason Santa is so jolly is [EMAIL PROTECTED] because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: On Thu 2000-09-21 (08:48), Donn Miller wrote: An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. Do you have a populated /usr/obj? (ie, with nm) I've been doing "make buildkernel installkernel" in /usr/src without doing a "make buildworld" first. Is this OK? I guess the buildkernel created a /usr/obj, but I deleted it and tried buildkernel again with the same results. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu, Sep 21, 2000 at 10:00:59AM -0400, Donn Miller wrote: On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: On Thu 2000-09-21 (08:48), Donn Miller wrote: An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. Do you have a populated /usr/obj? (ie, with nm) I've been doing "make buildkernel installkernel" in /usr/src without doing a "make buildworld" first. Is this OK? I guess the buildkernel created a /usr/obj, but I deleted it and tried buildkernel again with the same results. - Donn FWIW, I have the same problem on 4.1-STABLE cvsupped 10 mins ago from cvsup.nl.freebsd.org. I noticed these lines in the build log: ... cd /usr/obj/usr/src/sys/PCWIN002; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin MACHINE=i386 make KERNEL=kernel depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/genassym.c sh /usr/src/sys/kern/genassym.sh genassym.o assym.s nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory rm -f param.c cp /usr/src/sys/conf/param.c . perl5 /usr/src/sys/kern/vnode_if.pl -h /usr/src/sys/kern/vnode_if.src ... Especially: nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory Which is quite correct since I blew away /usr/obj after my last buildworld (FreeBSD 4.1-STABLE #0: Wed Sep 13 14:45:31 CEST 2000). Is this a problem? Should I have done a buildworld before a buildkernel now? --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kldload and alternate kernel locations...
Normally, kldload can only find .ko modules in /boot/kernel. What if you have KERNEL=MYKERNEL set in /etc/make.conf, for instance, which will result in a kernel installed in /boot/MYKERNEL? kldload doesn't find the modules then (because all the .ko's are in /boot/MYKERNEL). I've first noticed this problem at start-up, when I got the message: green_saver: not found or something to that extent. Basically, there's a line in /etc/rc.i386 which says: kldstat -v | grep -q _saver || kldload ${saver}_saver I think we should change it to something like kldstat -v | grep -q _saver || kldload /boot/${kernel}/${saver}_saver because kldload can't find modules not installed in /boot/kernel. I think /etc/rc.i386 should include /boot/loader.conf to determine the location of the .ko modules, since that's where $kernel is defined. Another solution (instead of modifying rc.i386) would be to modify kldload so that it somehow checks the value of $kernel set in /boot/loader.conf to check the location of kernel modules. I think this is a more elegant solution, but I don't know if it's necessarily easier. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'host' command with CNAMEs
As I recall, Sean Kelly wrote: I've got two machines here, one running 4.1-STABLE (from Aug 3) and a 5.0-CURRENT (from Aug 10) and both of them show the same issue. When you use the 'host' command to resolve a CNAME, it will show all the A records twice: (7) smkelly@edgemaster:~$ host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 It is more complicated than that... the bug only shows up if you specify an alias name... $ host releng4.freebsd.org releng4.freebsd.org is a nickname for usw3.FreeBSD.org usw3.FreeBSD.org has address 209.180.6.227 usw3.FreeBSD.org has address 209.180.6.227 $ $ host usw3.freebsd.org usw3.freebsd.org has address 209.180.6.227 $ - Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'host' command with CNAMEs
I think this is a bug in that version of Bind as it also happens on my Solaris machine here on which I compiled up bind v8.2.2 recently... Scot On Thu, 21 Sep 2000, Tim Zingelman wrote: As I recall, Sean Kelly wrote: I've got two machines here, one running 4.1-STABLE (from Aug 3) and a 5.0-CURRENT (from Aug 10) and both of them show the same issue. When you use the 'host' command to resolve a CNAME, it will show all the A records twice: (7) smkelly@edgemaster:~$ host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 It is more complicated than that... the bug only shows up if you specify an alias name... $ host releng4.freebsd.org releng4.freebsd.org is a nickname for usw3.FreeBSD.org usw3.FreeBSD.org has address 209.180.6.227 usw3.FreeBSD.org has address 209.180.6.227 $ $ host usw3.freebsd.org usw3.freebsd.org has address 209.180.6.227 $ - Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
processes only consume system time ????
This happens with freshly built -CURRENT, on an uniprocessor machine: $ cat loop.c main() { while (1); } $ time ./loop [ wait for ten seconds... ] ^C real0m9.982s user0m0.000s sys 0m5.689s Uh? Other utilities, such as top(1) and systat(1) show that 100% of time is accounted to the system. I imagine that this is related to SMPng... Any clues? Cheers, -- JMA ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMPng panic message
Hi, When I boot an SMP kernel (updated 2 days ago) I get the following panic message - panic: cpu_switch: chooseproc returned NULL cpuid = 0; lapic_id = db tr Debugger(..) panic(..) sw0_3(2,c03876f8,0,0,0) at sw0_3 msleep(c038f958,0,30,c03890dc,64) at msleep+0x235 random_kthread(c038a37c) at random_kthread+0x79 Without the random dev KLD I get the same panic message so I didn't bother with a trace.. (I can get one if its needed :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu 2000-09-21 (16:27), Stijn Hoop wrote: nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory Yep, this is the problem. Which is quite correct since I blew away /usr/obj after my last buildworld (FreeBSD 4.1-STABLE #0: Wed Sep 13 14:45:31 CEST 2000). Is this a problem? Yep. Should I have done a buildworld before a buildkernel now? I'm trying to convince Marcel that since we already let you use gcc from out the tree, there's no reason we should prevent people from running 'nm' from out the tree. Since he knows more about this sort of thing, and says there may be a problem, I'll leave it to him. Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu 2000-09-21 (08:48), Donn Miller wrote: An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. Do you have a populated /usr/obj? (ie, with nm) Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
On Thu 2000-09-21 (10:00), Donn Miller wrote: On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: On Thu 2000-09-21 (08:48), Donn Miller wrote: An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. Do you have a populated /usr/obj? (ie, with nm) I've been doing "make buildkernel installkernel" in /usr/src without doing a "make buildworld" first. Is this OK? I guess the buildkernel created a /usr/obj, but I deleted it and tried buildkernel again with the same results. No, it's not ok. I have patches awaiting some final decision from Marcel that'll make it possible. It mostly works, but OBJFORMAT_PATH doesn't have access to the same PATH we're exporting during the kernel build, meaning 'nm' won't work. They look something like: cvs diff: cannot find Makefile Index: Makefile.inc1 === RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.167 diff -u -r1.167 Makefile.inc1 --- Makefile.inc1 2000/09/03 02:58:39 1.167 +++ Makefile.inc1 2000/09/06 21:10:53 @@ -193,6 +193,14 @@ PATH=${TMPPATH} WMAKE= ${WMAKEENV} ${MAKE} -f Makefile.inc1 +# kernel stage +.if ${BUILD_ARCH} == ${MACHINE_ARCH} +KMAKEENV= ${WMAKEENV} \ + OBJFORMAT_PATH=${WORLDTMP}/usr/libexec:/usr/libexec +.else +KMAKEENV= ${WMAKEENV} +.endif + # install stage IMAKEENV= ${CROSSENV} \ PATH=${STRICTTMPPATH}:${INSTALLTMP} @@ -383,6 +391,9 @@ .if empty(INSTALLKERNEL) INSTALLKERNEL= ${_kernel} .endif +.else +.BEGIN: + @echo " Kernel configuration ${_kernel} does not exist; not building" .endif .endfor @@ -409,10 +420,10 @@ ${MAKE} -f ${KRNLSRCDIR}/dev/aic7xxx/Makefile .if !defined(NO_KERNELDEPEND) cd ${KRNLOBJDIR}/${_kernel}; \ - ${WMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} depend + ${KMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} depend .endif cd ${KRNLOBJDIR}/${_kernel}; \ - ${WMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} all + ${KMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} all .endfor # Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Intel 815e and SMbus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, is the SMBus on the 815e different from the old BX? I'm running 4.1 but it can't find any SMB device. (ASUS CULS2) Is it supported in -current? Thanks, Harry belenus GmbH Harald Schmalzbauer Sys/Net Admin Tel: +49 (89) 21979-120 Fax: +49 (89) 21979-111 www.belenus.com -BEGIN PGP SIGNATURE- Version: PGP 6.5.2 iQA/AwUBOconylXEptsBus8cEQIJRACffYkwORv8IfuNt/fUfxitTKVygc0AnRsL hbqPjHnS9PrxqJcrg7XQdRiE =ubXC -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new idle_proc() makes my laptop very hot
Hi. After new idle_proc() committed to the tree, my laptop become very hot as if under heavy cpu load even when cpu is actually 95%~ idle. If I understand collectly, idle_proc() doesn't contain any HLT instruction in i386 UP case which former idle() had. Attached patch adds back the HLT in i386 UP case and seems to fix my problem, although I'm totally unfamiliar with SMP nor alpha. Other than that, current runs quite fine in normal operation here. Thanks. -- Takaya Ogawa [EMAIL PROTECTED] hlt.patch
Fsck wrappers, revisited
I've updated my fsck wrappers patchset to the latest netbsd and freebsd fsck patches. I'd appreciate some feedback on them before I run off and commit them (with my mentor, of course.) For those who aren't in the know, the general idea is that a single wrapper program spawns a FS-specific fsck process a la mount and mount_*, making multiple-FS support a lot easier. (Think about having fsck_ext2fs, fsck_msdos and fsck_ffs doing your FSes on bootup..) They can be found at http://www.freebsd.org/~adrian/fsck/ . PLEASE read the README before you use them, as there are a few gotchas. Thanks! Adrian -- Adrian Chadd"The main reason Santa is so jolly is [EMAIL PROTECTED] because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Notebook current rebooting problems
Hi all, I am new to -current but running FreeBSD since 2.2.?. current was a result of haveing problems with my notebook after running a long time with 3.x and 4.x. till the last cvsup mid of august and now there must have been changes which cases my notebook to hang when rebooting. it is a Kapok 8700 (233MhZ/128MB/4GB/ESS1879) which is sold under different brands. now i successfully updated to current running in the same problem. if power on is done it boots fine. also shutdown -h now and power off / power on works. but reboot or shutdown -r now makes the box shutting down and it looks like it trys to start (cleaning the screen) and then hangs forever. only power off is possible. i want to stay with this box on current because i always was interested in it so any idea that rebooting works again would be great. there are 2 more questions: 1. i run vmware and after the update the rtc.ko und vm..ko modules cant get loaded. trying to reinstall from the ports works for rtc (but results in exec format error again) and fails for vmware. there was a note about people complaining about the linux emulation after upgrading to current and not moving the old moules away. i moved /modules and /modules.old away and let only an empty /modules. the onld kernel is still in / but when booting it is noted /boot/kernel... kde2 and other software atarts fine. 2. the notebook has an ESS1879 sound card which was the second reason to upgrade. pcm/sbc finds the card without problems at boot time. but artsd from kde2/b5 locks the pc when it is startet. many thanks for any hints. Best rgards, / Mit freundlichen Grüßen, Karl M. Joch _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel broken?
In message [EMAIL PROTECTED] Donn Miller writes: : I've been doing "make buildkernel installkernel" in /usr/src without doing : a "make buildworld" first. Is this OK? NO. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
I can second this... on my PC the cpu used to run around about 84 degrees F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F while the case runs at 80 degrees F. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Fri, 22 Sep 2000, Takaya Ogawa wrote: Hi. After new idle_proc() committed to the tree, my laptop become very hot as if under heavy cpu load even when cpu is actually 95%~ idle. If I understand collectly, idle_proc() doesn't contain any HLT instruction in i386 UP case which former idle() had. Attached patch adds back the HLT in i386 UP case and seems to fix my problem, although I'm totally unfamiliar with SMP nor alpha. Other than that, current runs quite fine in normal operation here. Thanks. -- Takaya Ogawa [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
I can second this... on my PC the cpu used to run around about 84 degrees F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F while the case runs at 80 degrees F. While you're tinkering with SMPng, be VERY SURE that you do not have acpi enabled (ie. make sure it's not in your kernel config). We're not yet handling thermal management, and this *will* hurt you. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : I can second this... on my PC the cpu used to run around about 84 degrees : F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F : while the case runs at 80 degrees F. My laptop does seem to run *MUCH* warmer than before as well. It runs hot to begin with, but with the latest kernels it runs really hot. It used to get this hot only when I compiled -j 4. I don't have ACPI enabled and am using UP kernel. There really needs to be a HLT in the idle loop to keep idle machines cools. The thermal management code, iirc, works in conjunction with this by lower the clock rate when things aren't too loaded, but that is a fairly complex thign to wait for. It also seems to help mostly on lightly loaded machines. HLT helps more than you'd otherwise think...c Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
My laptop does seem to run *MUCH* warmer than before as well. It runs hot to begin with, but with the latest kernels it runs really hot. It used to get this hot only when I compiled -j 4. I don't have ACPI enabled and am using UP kernel. There really needs to be a HLT in the idle loop to keep idle machines cools. If I remember from a discussion with John Baldwin, the reason we don't do this (yet) is that HLT only wakes up when you take an interrupt, and there are cases where we can't guarantee that we'll take an interrupt in order to get us out of the HLT. The thermal management code, iirc, works in conjunction with this by lower the clock rate when things aren't too loaded, but that is a fairly complex thign to wait for. It also seems to help mostly on lightly loaded machines. HLT helps more than you'd otherwise think...c HLT helps a lot, yes, but the thermal management code is responsible for running the system fan(s) in ACPI mode as well as throttling the CPU. In some cases, that's a real issue (eg. I'm building the world now and extremely worried about how hot this system is because I forgot to turn ACPI off first. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
In message [EMAIL PROTECTED] Mike Smith writes: : If I remember from a discussion with John Baldwin, the reason we don't do : this (yet) is that HLT only wakes up when you take an interrupt, and : there are cases where we can't guarantee that we'll take an interrupt in : order to get us out of the HLT. I thought that's what the timer interrupts were for... We can't guarantee that we'll get one? That seems very serious to me. Think about the MP environment. There's one timer interrupt, and more than one CPU. In the UP case, you could probably rely on HLT to DTRT though; this is an optimisation that will probably come back shortly. : HLT helps a lot, yes, but the thermal management code is responsible for : running the system fan(s) in ACPI mode as well as throttling the CPU. In : some cases, that's a real issue (eg. I'm building the world now and : extremely worried about how hot this system is because I forgot to turn : ACPI off first. 8) Ah. I don't have a system fan :-) Some of us need them. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
Warner Losh [EMAIL PROTECTED] wrote: Mike Smith writes: If I remember from a discussion with John Baldwin, the reason we don't do this (yet) is that HLT only wakes up when you take an interrupt, and there are cases where we can't guarantee that we'll take an interrupt in order to get us out of the HLT. I thought that's what the timer interrupts were for... We can't guarantee that we'll get one? That seems very serious to me. The problem is that one cpu may wich to schedule a process to run on the idle cpu, but it can't because the idle cpu is halted and won't wake up until the next irq. Tony. -- en oeccget g mtcaaf.a.n.finch v spdlkishrhtewe y[EMAIL PROTECTED] eatp o v eiti i d.[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
In message [EMAIL PROTECTED] Tony Finch writes: : Warner Losh [EMAIL PROTECTED] wrote: : Mike Smith writes: : : If I remember from a discussion with John Baldwin, the reason we : don't do this (yet) is that HLT only wakes up when you take an : interrupt, and there are cases where we can't guarantee that we'll : take an interrupt in order to get us out of the HLT. : : I thought that's what the timer interrupts were for... We can't : guarantee that we'll get one? That seems very serious to me. : : The problem is that one cpu may wich to schedule a process to run on : the idle cpu, but it can't because the idle cpu is halted and won't : wake up until the next irq. Since I'm running a UP kernel, that can't happen. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
: If I remember from a discussion with John Baldwin, the reason we : don't do this (yet) is that HLT only wakes up when you take an : interrupt, and there are cases where we can't guarantee that we'll : take an interrupt in order to get us out of the HLT. : : I thought that's what the timer interrupts were for... We can't : guarantee that we'll get one? That seems very serious to me. : : The problem is that one cpu may wich to schedule a process to run on : the idle cpu, but it can't because the idle cpu is halted and won't : wake up until the next irq. Since I'm running a UP kernel, that can't happen. Actually, there are pathalogical cases where it could, but they are, well, pathalogical. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'host' command with CNAMEs
As I recall, Sean Kelly wrote: I've got two machines here, one running 4.1-STABLE (from Aug 3) and a 5.0-CURRENT (from Aug 10) and both of them show the same issue. When you use the 'host' command to resolve a CNAME, it will show all the A records twice: (7) smkelly@edgemaster:~$ host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 It is more complicated than that... the bug only shows up if you specify an alias name... You are both correct. In fact, it looks like you're stating the exact same thing. The obvious problem is that if 'host' is resolving a CNAME, there are two independant places which display the real address. My guess is that at some point, two independant developers decided to change the way 'host' deals with CNAMEs, but they put their code in different places. When they commited their code to the CVS repository, there were no conflicts, and the second one to commit failed to notice that a part of his code was already implemented. This bug was actually fixed in rev. 8.28 of host.c (BIND v8.2.1), but was resurrected in rev. 8.31 (BIND v8.2.2-REL). Since ISC doesn't release their CVS logs to the public, I can't find out why this was done (perhaps a developer commited something based on an earlier rev., and didn't merge this change). If anybody wants it, I've made a patch to correct the problem (see attached). It applies against src/contrib/bind/bin/host/host.c of 5-CURRENT (although host.c is the same in RELENG_4, and it applies cleanly there). I heard somewhere that the contrib/ tree shouldn't contain local changes, but I'm unclear as to where local changes to contribited software go, so I made it against that. Once you've applied it, all you should have to do is `( cd /usr/src/usr.bin/host make)`, although I haven't tested that approach. This should also apply cleanly to host.c of BIND 8.2.3-T5B, as that's what is in FreeBSD. Hope this helps -- Dima Dorfman [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for my public PGP key. "When in doubt, use brute force." -- Ken Thompson Index: host.c === RCS file: /usr/cvs/FreeBSD/src/contrib/bind/bin/host/host.c,v retrieving revision 1.1.1.3 diff -u -r1.1.1.3 host.c --- host.c 2000/05/26 07:17:07 1.1.1.3 +++ host.c 2000/09/21 23:46:26 @@ -696,8 +696,18 @@ if (!hp-ad) if (verbose isls == 0) printf("The following answer is not verified as authentic by the server:\n"); - while (--ancount = 0 cp cp eom) + while (--ancount = 0 cp cp eom) { cp = pr_rr(cp, answer-qb2, stdout, filter); + /* +* When we ask for address and there is a CNAME, it +* seems to return both the CNAME and the address. +* Since we trace down the CNAME chain ourselves, we +* don't really want to print the address at this +* point. +*/ +if (cname ! verbose) +return (1); +} } if (!verbose) return (1);
Re: 'host' command with CNAMEs
BIND 4 and BIND 8 bugs can be reported to [EMAIL PROTECTED] BIND 9 bugs can be reported to [EMAIL PROTECTED] Mark P.S. don't bother submitting this as it will just land in my mailbox. --ELM969581696-60857-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit As I recall, Sean Kelly wrote: I've got two machines here, one running 4.1-STABLE (from Aug 3) and a 5.0-CURRENT (from Aug 10) and both of them show the same issue. When you use the 'host' command to resolve a CNAME, it will show all the A records twice: (7) smkelly@edgemaster:~$ host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 It is more complicated than that... the bug only shows up if you specify an alias name... You are both correct. In fact, it looks like you're stating the exact same thing. The obvious problem is that if 'host' is resolving a CNAME, there are two independant places which display the real address. My guess is that at some point, two independant developers decided to change the way 'host' deals with CNAMEs, but they put their code in different places. When they commited their code to the CVS repository, there were no conflicts, and the second one to commit failed to notice that a part of his code was already implemented. This bug was actually fixed in rev. 8.28 of host.c (BIND v8.2.1), but was resurrected in rev. 8.31 (BIND v8.2.2-REL). Since ISC doesn't release their CVS logs to the public, I can't find out why this was done (perhaps a developer commited something based on an earlier rev., and didn't merge this change). If anybody wants it, I've made a patch to correct the problem (see attached). It applies against src/contrib/bind/bin/host/host.c of 5-CURRENT (although host.c is the same in RELENG_4, and it applies cleanly there). I heard somewhere that the contrib/ tree shouldn't contain local changes, but I'm unclear as to where local changes to contribited software go, so I made it against that. Once you've applied it, all you should have to do is `( cd /usr/src/usr.bin/host make)`, although I haven't tested that approach. This should also apply cleanly to host.c of BIND 8.2.3-T5B, as that's what is in FreeBSD. Hope this helps -- Dima Dorfman [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for my public PGP key. "When in doubt, use brute force." -- Ken Thompson --ELM969581696-60857-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=host-cname.diff Content-Description: /usr/home/dima/host-cname.diff Content-Transfer-Encoding: 7bit Index: host.c === RCS file: /usr/cvs/FreeBSD/src/contrib/bind/bin/host/host.c,v retrieving revision 1.1.1.3 diff -u -r1.1.1.3 host.c --- host.c2000/05/26 07:17:07 1.1.1.3 +++ host.c2000/09/21 23:46:26 @@ -696,8 +696,18 @@ if (!hp-ad) if (verbose isls == 0) printf("The following answer is not verified as authent ic by the server:\n"); - while (--ancount = 0 cp cp eom) + while (--ancount = 0 cp cp eom) { cp = pr_rr(cp, answer-qb2, stdout, filter); + /* + * When we ask for address and there is a CNAME, it + * seems to return both the CNAME and the address. + * Since we trace down the CNAME chain ourselves, we + * don't really want to print the address at this + * point. + */ +if (cname ! verbose) +return (1); +} } if (!verbose) return (1); --ELM969581696-60857-0_-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
I don't have it enabled... I am not even on my laptop with -CURRENT... this is on my regular PC... and I'm taking my thermal readings by banging around on some memory addys through /dev/io with a little hack of a program I wrote as a windowmaker dockapp for this purpose... = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Thu, 21 Sep 2000, Mike Smith wrote: I can second this... on my PC the cpu used to run around about 84 degrees F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F while the case runs at 80 degrees F. While you're tinkering with SMPng, be VERY SURE that you do not have acpi enabled (ie. make sure it's not in your kernel config). We're not yet handling thermal management, and this *will* hurt you. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new idle_proc() makes my laptop very hot
My system fans always stay on... but again this is not in a laptop .. it is on my regular pc... = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Thu, 21 Sep 2000, Mike Smith wrote: My laptop does seem to run *MUCH* warmer than before as well. It runs hot to begin with, but with the latest kernels it runs really hot. It used to get this hot only when I compiled -j 4. I don't have ACPI enabled and am using UP kernel. There really needs to be a HLT in the idle loop to keep idle machines cools. If I remember from a discussion with John Baldwin, the reason we don't do this (yet) is that HLT only wakes up when you take an interrupt, and there are cases where we can't guarantee that we'll take an interrupt in order to get us out of the HLT. The thermal management code, iirc, works in conjunction with this by lower the clock rate when things aren't too loaded, but that is a fairly complex thign to wait for. It also seems to help mostly on lightly loaded machines. HLT helps more than you'd otherwise think...c HLT helps a lot, yes, but the thermal management code is responsible for running the system fan(s) in ACPI mode as well as throttling the CPU. In some cases, that's a real issue (eg. I'm building the world now and extremely worried about how hot this system is because I forgot to turn ACPI off first. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: processes only consume system time ????
On 21-Sep-00 Jose M. Alcaide wrote: This happens with freshly built -CURRENT, on an uniprocessor machine: $ cat loop.c main() { while (1); } $ time ./loop [ wait for ten seconds... ] ^C real0m9.982s user0m0.000s sys 0m5.689s Uh? Other utilities, such as top(1) and systat(1) show that 100% of time is accounted to the system. I imagine that this is related to SMPng... Yes. This is a FAQ. The accounting is screwed up, and some of the statistics are wrong. Your system is scheduling processes close enough to normal that you shouldn't have any problems. Any clues? Cheers, -- JMA -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B;K>e:GBg5,LO$N%&%'%V7O:G?7%S%8%M%9>pJs$G$9!#(B
$B!z!y!z!y!z@$3&:GBg5i$N%7%g%C%T%s%0%b!<%k$,F|K\>eN&!*!z!y!z!y!z(B 10$B7n%*!<%W%sA0$ND6%l%">pJs$G$9!#(B $B$9$G$K?tI4K|E@$N%"%$%F%`$re$2$i$l$k%S%8%M%9%Q!<%H%J!<$r(B $BJg=8$$$?$7$^$9!#(B $BEPO?5Z$S>\:Y$O2<5-%[!<%`%Z!<%8$r$4Mw2<$5$$!#(B $B"-!!"-!!"-!!"-!!"-!!"-!!"-!!"-!!(B http://www.starmax-japan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 1131 unneeded includes in the kernel...
On Wednesday, 20 September 2000 at 3:10:21 -0400, Brandon D. Valentine wrote: On Tue, 19 Sep 2000, Matthew Jacob wrote: Oh- don't get me wrong. Valuable info. Thanks. What would be very cool is to feed this into another script which strips these unnecesary includes out. Then do a test build of LINT in your local tree and if it succeeds commit a mass removal of them. The same concept could be applied to the greater source tree. Things aren't that simple. I've checked some of the vinum ones, and I find something like: #ifdef VINUMDEBUG #include sys/reboot.h #endif sys/reboot.h has been flagged as unnecessary. Obviously the #ifdef's have to do as well--if the script is correct. There are a number of options in Vinum which never get as far as the source tree. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message