Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 08:12:47AM +0200, Roelof Osinga wrote: Especially LINT. LINT is nice if you want to look something up, but it is not a hands-on manual that leads one through all the steps needing to be taken to implement some such thingamathing or other. Since NETSMB support is not in GENERIC, you must have added it to your kernel yourself at some point. When you modify your kernel configuration you need to read the documentation to make sure you're adding all necessary components (otherwise you'll get a broken kernel config, like you did). The documentation is in LINT. While I'm typing this, it just occurred to me. Some years ago the world got rocked once again. There was something about making the world versus explicitly building it and installing it. Later it all got changed again. Every one of those changes was deemed important. Every one of those changes changed things. People don't like changes. Monkeys don't either. Dolphins I don't know. My pitch is way off. You're not exactly being specific here, but the full upgrade/rebuild procedure is spelled out in the handbook if you're confused about how to do it. Kris msg50360/pgp0.pgp Description: PGP signature
Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 07:51:12AM +0200, Roelof Osinga wrote: Did you do a make installworld? Nope. Just the buildworld. I'm redoing the things I jotted down on my logs on previous builds. Went ok these last three or so years ;). If you haven't been running 'make installworld' for the last 3 years then you haven't actually upgraded your FreeBSD system in those 3 years. Kris msg50361/pgp0.pgp Description: PGP signature
Dell Inspiron Fan support
Hello, I have recently changed OS from Linux to FreeBSD on my laptop. Everything works just excellent except for one little thing :) In Linux i was able to include Dell (2.4.x kernel) support for my laptop. Another program (some weird gkrellm plugin) allowed me to control my fan speed. This sounds silly i know.. but this really bothers me since my fans don't seem to activate automatic. For all i know it could damage my system :\ Hopefully somebody can point me into the right direction. Thanks in advance, Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NFS server not respnding!
Using FreeBSD 4.6.2-pl2 and FreeBSD 4.7-RC2 on our server system (one 4.7-RC experimental system) and utilizing AMD for mounting home space and other services via TCP protocol results in nfs server 134.93.180.216:/usr/homes: not responding nfs server 134.93.180.216:/usr/homes: is alive again very often, when load of the appropriate client is very high. That happens when on our number crunching systems utilization of CPU time is high or many users try copy from and to via SAMBA to the main NFS server system. There's one setup that I maintain where I see this a lot. If I mount the ports dir with rw perms over NFS, _AND_ am using CVSup to update the ports, I can reliably crash the NFS server. I'm not sure if this is because I'm taxing the IDE drives too much or because there's some glitch in NFS someplace. Tuning and TCP vs UDP hasn't made a difference. I'm going to give netdump_client a shot here sometime soon and see if I can't get some kind of debugging info out of the kernel. As it stands, the system has 2GB of RAM and I only allocated 1GB to swap (which isn't ever more than 1% used). FWIW, why isn't netdump_client a part of the standard distro? Seems like an invaluable tool in debugging. -sc -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Compiling a New Kernel
Being one of these difficult people who like sticking to the old way of doing things, im still compiling my kernel the old way (config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P I picked up a rumour on the mailing lists that this may no longer work in future/recent releases? Just curious ;) -- Jamie Heckford [EMAIL PROTECTED] http://www.jamiesdomain.org.uk/ FreeBSD: The Power to Serve -- Message scanned for viruses and dangerous content by http://www.newnet.co.uk/av/ and believed to be clean To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
On Fri, Oct 11, 2002 at 09:44:57AM +0100, Jamie Heckford wrote: Being one of these difficult people who like sticking to the old way of doing things, im still compiling my kernel the old way (config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P I picked up a rumour on the mailing lists that this may no longer work in future/recent releases? It's fine when you're rebuilding your kernel with the same sources as your installed world, but if you upgrade your sources and want to build the kernel then this method WILL NOT WORK in all cases (and there have been cases in the past when it would not work). This is why 'make buildkernel' and friends were introduced; they are guaranteed [1] to work properly in all cases. The exact steps are documented in the handbook. Kris [1] Modulo /COPYRIGHT :-) msg50365/pgp0.pgp Description: PGP signature
Re: Compiling a New Kernel
On Fri, Oct 11, 2002 at 09:44:57AM +0100, Jamie Heckford wrote: Being one of these difficult people who like sticking to the old way of doing things, im still compiling my kernel the old way (config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P I picked up a rumour on the mailing lists that this may no longer work in future/recent releases? Nowadays, the old way is only guarranteed to work if you've previously built and installed world, kernel with that same set of sources. The new way, 'make buildkernel' doesn't have that restriction, as it uses the compiler toolchain and so forth freshly created in the build area. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: new intel chipset and SMP Xeons
-Original Message- From: Dmitry Valdov [mailto:dv;dv.ru] Sent: October 11, 2002 05:14 To: [EMAIL PROTECTED] Subject: new intel chipset and SMP Xeons Hi! Is there a plan to support Intel E7500 chipset in -stable? Without this FreeBSD can't use 2nd CPU. I'm using FreeBSD 4.6 on an E7500 platform (a supermicro P4DPR, http://www.supermicro.com/PRODUCT/MotherBoards/E7500/P4DPR.htm) with dual XEON. This is working ok for me, I see all '4' processors (2 per xeon because of the symmetric multi-threading). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
On Fri, Oct 11, 2002 at 08:24:33AM -0700, Kevin Oberman wrote: When you build a new world (make buildworld), none of the new tools that have been built are installed. So any kernel built with this system will attempt to use the existing tools. If something critical to building the kernel, say the .mk files or compiler, have been updated and the kernel Makefile has been modified to work with the new .mk files, any attempt to build the kernel with existing, installed tools is doomed to failure. This is exactly correct. Examples in the past have included binutils/compiler upgrades and *.mk changes. Kris msg50727/pgp0.pgp Description: PGP signature
Re: kernel crashes during boot
Sean McNeil wrote: I just cvsup'd my STABLE sources and recompiled. My new kernel now panics on bootup. I couldn't get the info but I think it was a page fault 12 or something like that. AMD processor. Anyone else experiencing this? If not I will try to capture all the relevant info. Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message After cvsup on 10/10/02, I get the same error after reboot to make installworld. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ~12hrs on a 4.7-RELEASE kernel and *POW*!
Sorry, its -STABLE ... pre-RELEASE was worse :) On Fri, 11 Oct 2002, Mike Silbersack wrote: On Fri, 11 Oct 2002, Marc G. Fournier wrote: Morning all ... Just letting you know that it blew up about an hour ago, after 12hrs of uptime ... but, this time ... in a different place :) Er, -RELEASE or -STABLE? I thought Matt's changes were MFC'd after RELEASE was tagged, and hence are only on stable. Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
[no subject]
subscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
| By Jamie Heckford [EMAIL PROTECTED] | [ 2002-10-11 11:13 +0200 ] Bizarre how could it be different/not work if you have cvsup'd all of your sources including sys/ tree at exactly the same time, and compile your kernel just after the installworld? Ideally you should build, install, and boot your new kernel before installing your new world. If your new kernel fails to boot for whatever reason, you can easily boot the old kernel and have a fully functional system again. If you installworld before verifying your new kernel, you could run into worse problems if your new kernel doesn't load and you have to boot the old kernel with your new world. Regards, Aragon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
Aragon Gouveia wrote: Ideally you should build, install, and boot your new kernel before installing your new world. If your new kernel fails to boot for whatever reason, you can easily boot the old kernel and have a fully functional system again. If you installworld before verifying your new kernel, you could run into worse problems if your new kernel doesn't load and you have to boot the old kernel with your new world. The only problem that I have with this approach, is that I keep all of my source on a vinum raid-5 volume. If I reboot before doing a make installworld, then there is always the possibility that with the new kernel and the old world I may not be able to mount the volume. So I always shutdown but *not* reboot before doing the installworld. Phil. -- _-_|\ Phil Kernick E-Mail: [EMAIL PROTECTED] / \ ROTFL Enterprises Mobile: 041 61 ROTFL \_.-*_/ v Humourist, satirist, and probably a few more 'ists to boot! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kernel crashes during boot
Date: Fri, 11 Oct 2002 18:27:25 -0400 From: Bryan Berch [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Sean McNeil wrote: I just cvsup'd my STABLE sources and recompiled. My new kernel now panics on bootup. I couldn't get the info but I think it was a page fault 12 or something like that. AMD processor. Anyone else experiencing this? If not I will try to capture all the relevant info. Sean To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message After cvsup on 10/10/02, I get the same error after reboot to make installworld. This was first reported several hours ago. Looks like something did not get committed in a timely manner. In any case, the two people to report it this morning did another cvsup and it was fine. My system, updated at about 10:00 (-7) this morning, was fine. The problem systems had run cvsup about an hour to 2 hours earlier. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kernel crashes during boot
Kevin Oberman wrote: After cvsup on 10/10/02, I get the same error after reboot to make installworld. This was first reported several hours ago. Looks like something did not get committed in a timely manner. In any case, the two people to report it this morning did another cvsup and it was fine. My system, updated at about 10:00 (-7) this morning, was fine. The problem systems had run cvsup about an hour to 2 hours earlier. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message After re-cvsuping everything goes well to reboot to make installworld. The reboot fails with the following error:eisa0: EISA bus Fatal trap 12: Page fault while in kernel mode fault virtual address =0x0 fault code =supervisor read, page not present instruction pointer =0x8:0xc0372d40 stack pointer=0x10:0xc0535f1c frame pointer =0x10:0xc0535f24 code segment =base 0x0, limit 0x, type 0x1b =DPL 0, pres 1, def 32 1, gran 1 processor eflags =interrupt enable, resume IOPL = 0 current process= 0 (swapper) interrupt mask = net tty bio cam kernel: type 12 trap, code=0 stopped at nexus_print_all_resources+0x14: cmpl$0,0(%esi) TIA Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: How now, BSD crow?
Kris Kennaway wrote: On Fri, Oct 11, 2002 at 08:12:47AM +0200, Roelof Osinga wrote: Since NETSMB support is not in GENERIC, you must have added it to your kernel yourself at some point. When you modify your kernel configuration you need to read the documentation to make sure you're adding all necessary components (otherwise you'll get a broken kernel config, like you did). The documentation is in LINT. Yep. And took it out again, would still not build. Does now though. You're not exactly being specific here, but the full upgrade/rebuild procedure is spelled out in the handbook if you're confused about how to do it. And so I once did. I guess somehow a deviation from the pattern slipped in. Which I then faithfully copied at each rebuild. Also the reason I didn't check the handbook first. My bad. Sorry for the burden and thanks for the assistence! Roelof -- ___ EBOA® est. 1982 http://www.EBOA.com/tel. +31-58-2123014 mailto:info;EBOA.com?subject=Information_request To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
Phil Kernick wrote: Aragon Gouveia wrote: Ideally you should build, install, and boot your new kernel before installing your new world. If your new kernel fails to boot for whatever reason, you can easily boot the old kernel and have a fully functional system again. If you installworld before verifying your new kernel, you could run into worse problems if your new kernel doesn't load and you have to boot the old kernel with your new world. The only problem that I have with this approach, is that I keep all of my source on a vinum raid-5 volume. If I reboot before doing a make installworld, then there is always the possibility that with the new kernel and the old world I may not be able to mount the volume. So I always shutdown but *not* reboot before doing the installworld. Phil. -- _-_|\ Phil Kernick E-Mail: [EMAIL PROTECTED] / \ ROTFL Enterprises Mobile: 041 61 ROTFL \_.-*_/ v Humourist, satirist, and probably a few more 'ists to boot! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message It's early in the morning here :), but if the mount fails, you reboot and load kernel.old. At which point you should be able to mount your source. -- ian j hart To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Compiling a New Kernel
On Saturday, 12 October 2002 at 10:32:09 +0930, Phil Kernick wrote: Aragon Gouveia wrote: Ideally you should build, install, and boot your new kernel before installing your new world. If your new kernel fails to boot for whatever reason, you can easily boot the old kernel and have a fully functional system again. If you installworld before verifying your new kernel, you could run into worse problems if your new kernel doesn't load and you have to boot the old kernel with your new world. The only problem that I have with this approach, is that I keep all of my source on a vinum raid-5 volume. If I reboot before doing a make installworld, then there is always the possibility that with the new kernel and the old world I may not be able to mount the volume. So I always shutdown but *not* reboot before doing the installworld. I don't anticipate any problems with Vinum after an upgrade. The on-disk format has never changed, and though it's possible in the future, I'd hope it would do so in a compatible manner. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Left-over directory when asked to remove /var/tmp/temproot
Hello, After cvsupping/make buildworld/make buildkernel/make installkernel/mergemaster from 4.7-RELEASE to 4.7-STABLE as of about four hours ago I ran in to a slight problem with mergemaster. The mergemaster itself went perfectly fine, as I've come to expect. Unfortunately, mergemaster wasn't able to remove all of /var/tmp/tmproot when I answered yes to the question about removing the rest of /var/tmp/tmproot. After poking around, here's what I've found: blahblah# pwd /var/tmp/temproot/var blahblah# ls -alo total 6 drwxrwxrwx 3 root wheel -512 Oct 11 22:39 . drwxrwxrwx 3 root wheel -512 Oct 11 22:39 .. dr-xr-xr-x 2 root wheel schg 512 Oct 11 22:38 empty blahblah# ls -lAR * blahblah# chflags noschg empty chflags: empty: Operation not permitted chflags: empty: Operation not permitted blahblah# chmod -R 777 empty chmod: empty: Operation not permitted /var/tmp/temproot/var/empty is, well, empty. I'm probably missing something trivial with chflags. How do I make /var/tmp/temproot/var/empty deletable? Also, when did mergemaster start leaving things behind? Any ideas? Thanks, Josh P. S.: interestingly, there's also a /var/empty that's also schg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
10/11/2002 FreeBSD 4.7-stable kernel panic
Greetings all. Usually I have very few problems with FreeBSD, in fact this is my first in years so it could be a pretty bad bug, or something changed and I haven't found it yet. I upgraded to 4.7-stable today 10/11/2002. Made world, mergemastered, made and installed the kernel, rebooted and I got the kernel panic at the bottom of this mail. Here's some proc and memory stats: CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x584 Stepping = 4 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134217728 (131072K bytes) avail memory = 126668800 (123700K bytes) I can post the rest of the dmesg if needed (though I know some people get turned off at seeing an entire dmesg and this mail is long enough). For now I'll include the problem part (which I only was able to get after copying as it kept rebooting). The thing is that my old 4.6-stable kernel *works*, so I doubt this is a hardware problem on my end. This kernel, even when compiled with the GENERIC config produces the same results. I really hope this is fixable, I love my FreeBSD. Btw, please reply to [EMAIL PROTECTED] since I just unsubbed from -stable about a week ago (doh!). Any help is much appreciated. If any additional info (more dmesg, mb make, etc) is needed I will happily provide it. -Kris --Begin Kernel Panic message eiso0: (EISA Bus) Fatal trap 12: page fault while in kernel mode fault virtual address: = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc07350e0c stack pointer = 0x10:0xc0553f1c frame pointer = 0x10:0xc0553f24 code segment = base 0x0 limit 0x, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
