Re: 2xPIIIx450 results & NFS results
Yes, it definitely seems ASUS related... I dropped back to uni processor ASUS boards, and it's fine. didn't need the SMP anyway, just wanted to play with it some more. On Sat, 18 Sep 1999, Andrzej Bialecki wrote: > On Fri, 17 Sep 1999, Rodney W. Grimes wrote: > > > > :> I/O, and then closing it. > > > : > > > :4.0-CURRENT (SMP on an ASUS P2B-DS with two CPU's installed; BIOS revision > > > :1008.A, running `systat -vm 1' gives the normal display but without any > > > :numbers filled in, then switches over to an empty screen that says: > > > :... > > > > > > Whenever systat or top do weird things it probably means you > > > need to recompile libkvm. > > > > This is not a libkvm problem on my box, these are fresh make worlds > > on 3.3-RC as of 2 days ago. It only appears to occur when running SMP, > > The problem seems to occur reliably on ASUS boards - perhaps a > coincidence, but I have several machines here which behave this way. And > yes, libkvm is in perfect sync with the rest of the system (3.3-RC) > > Andrzej Bialecki > > // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) > // --- > // -- FreeBSD: The Power to Serve. http://www.freebsd.org > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > > > > 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: HEADSUP: wd driver will be retired!
On Sat, 11 Dec 1999, Lyndon Nerenberg wrote: > Or worse, on a file server where you lose a low-numbered disk, not > only does that one go away, but everything higher numbered loses as > well. This "feature" does nothing other than introduce a gratuitous Amen to this. If the default kernel or GENERIC shipped with the disks wired, it would be so much nicer. NT generally gets this one right, once you assign letters to partition, they tend to stick. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Minor snit in UPDATING.
19991204: The dc interface has replaced al, ax, dm, pn and mx. The former have been removed. I believe former should be latter. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel making problems
Wasn't there just a big to-do wrt to 4.0 (then -current), about the right way to do things is to install a new kernel, then build the world? I seem to remember Rod championing this method. (Had something to do with some syscall interface changing). On Sat, 27 May 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> John >Baldwin writes: > : You need to build and install a new world before a new kernel. It looks > : like this needs to go into src/UPDATING. > > Done. Others have suggested this as well. > > Warner > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: looking for "microuptime went backwards" victims...
I get it on my newsserver pretty much every night when expire runs.
12 IDE drives on 3 Promise controllers.
I was just actually about to replace the MB, thinking it was just
something freaky or unstable.
I will try the patch.
On Mon, 4 Sep 2000, Poul-Henning Kamp wrote:
>
> I'm looking for the remaining victims of the dreaded "microuptime
> went backwards" message.
>
> If you can reliably reproduce the problem, please contact me, so
> we can arrange for some very detailed tracing to try to find out
> what exactly is going on. I have not been able to trigger the
> problem in my lab in a long time.
>
> If you see the message only occationally, please try the attached
> patch and let me know if this changes the picture. The patch is
> not meant as a fix, but it might reduce the impact of this condition
> considerably when it happens. Basically by reducing the width of
> the timecounter the magnitude of the hit we take if the timecounter
> goes backwards is reduced from about an hour to approx 110msec.
>
> Reducing the width to less than 17 bits starts to run the risk of
> ambiguity due to clock rollover.
>
> This patch may not be safe with PCAUDIO.
>
> Poul-Henning
>
> Index: clock.c
> ===
> RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v
> retrieving revision 1.155
> diff -u -r1.155 clock.c
> --- clock.c 2000/07/30 21:05:22 1.155
> +++ clock.c 2000/09/04 16:34:16
> @@ -194,7 +194,7 @@
> static struct timecounter i8254_timecounter = {
> i8254_get_timecount,/* get_timecount */
> 0, /* no poll_pps */
> - ~0u,/* counter_mask */
> + 0x1,/* counter_mask */
> 0, /* frequency */
> "i8254" /* name */
> };
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> [EMAIL PROTECTED] | TCP/IP since RFC 956
> FreeBSD coreteam member | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
>
> 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: New NMBCLUSTERS tuning alternative
I love it. Haven't tried it, but the concept is great, and on the assumption it works, will make things even easier... Keep 'em coming. :) On Fri, 15 Jan 1999, Mike Smith wrote: > > With this commit, I'm trialling a simple method for providing tuning > hints for otherwise statically-set parameters from the bootloader. > > You can now say: > > set kern.ipc.nmbclusters= > > to effectively set NMBCLUSTERS to . > > I've looked at other approaches, particularly a hook in the SYSCTL_* > defines to search the environment and set the variables when the MIB > is instantiated, but this won't happen early enough for some things. > > Any suggestions welcome, of course. > > --- Forwarded Message > > msmith 1999/01/15 09:25:03 PST > > Modified files: > sys/i386/i386machdep.c > Log: > Fetch an overide for NMBCLUSTERS from the kernel environment. Never allow > the value to be reduced below that defined when the kernel was built. > > Revision ChangesPath > 1.322 +7 -1 src/sys/i386/i386/machdep.c > > Modified files: > sys/kern kern_environment.c > sys/sys systm.h > Log: > Add getenv_int(), specifically for retrieving integer values from kernel > environment variables. This makes it easy to pass tuning parameters > in from the bootloader. > > Revision ChangesPath > 1.4 +20 -1 src/sys/kern/kern_environment.c > 1.84 +2 -1 src/sys/sys/systm.h > > > --- End of Forwarded Message > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ m...@smith.net.au > \\ The race is long, and in the \\ msm...@freebsd.org > \\ end it's only with yourself. \\ msm...@cdrom.com > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Can the bootloader create a file or set a flag in the bootblocks?
It would be kind of cool if when managing a remote system if /kernel failed to boot, then on the next boot, the loader will fire up /kernel.old, or a /kernel.somethingorother. Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and have at least some assurance that I'll eventually be able to get back to a kernel I could use. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
CVS tags to use?
The readme in /usr/share/examples hasn't been updated in a while... WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x branch). Right now, I have tag=., and I can't get a compilable kernel to save my life, problems in syscons. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: "JAIL" code headed for -current.
Consider this interest. On Wed, 27 Jan 1999, Poul-Henning Kamp wrote: > > I'm polishing up the "JAIL" code I wrote and readying it for -current. > > This code provides an optional strenthening of the chroot() jail > as we know it, and will provide safe sandboxes for most practical > uses. > > The biggest impact of this is a new argument to the suser() call > all over the kernel: > > suser(NOJAIL, bla, bla); > or > suser(0, bla, bla); > > The NOJAIL option means that a jailed root fails the test. > > I will add this extra arg to suser() in the first commit. > > Each Jail can optionally be assigned one IP number, which they > have access to. All connections to and from that jail will > use that IP#. > > If there is interest, this code will be merged to 3.1 as well. > > This work was sponsored by:www.servetheweb.com > > -- > Poul-Henning Kamp FreeBSD coreteam member > p...@freebsd.org "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
mergemaster is your friend. On Fri, 12 Feb 1999, Jay Nelson wrote: > I may have missed this earlier in the thread, but has anyone given any > consideration to upgrade installs? If an upgrade doesn't plant the new > default files in /etc/default[s] after an upgrade, we now have two > places and twice the files to compare on upgrade. > > As unorthodox as it sounds, if these defaults are meant to be > unchanged, wouldn't a place like /boot/rc, or something similar, make > sense? Upgrades get the new whistles, and administrators can fiddle > files in /etc to their heart's content. > > -- Jay > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
How to freeze up your FreeBSD 5.0 box.
THis is repeatable for me at will. 5.0-current, supped as of 2/1. 4 80GIG maxtors on 2 promise IDE ultra 66 cards, exported via NFS. newfs'd an 80G FS on each drive, created one big file filled with zero's from /dev/zero on each drive. (Softupdates/UFS1) login to my other box, which has the 4 drives mounted via NFS (the other box being 4.7-stable as of 1/28/03). options from fstab are bg,intr,rw, don't recall if it was v2 or v3 NFS, although mountd was started with defaults, so I'm assuming v3. do (on the 4.7-stable box): rm /mntpt1/bigfile & rm /mntpt2/bigfile & rm /mntpt3/bigfile & rm /mntpt4/bigfile & And then switch back to the 5.0 current box, only to find out that it will not respond to any network traffic via ssh. Will respond to pings. I can type my login/pw on the console, but hitting return after typing my pw just sits there, until I ran out of VTY's. df on the 4.7 box hangs. AFter about 30 minutes, when the files finally finished being deleted, control of 5.0 box was returned, and everything was back and functioning properly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Many problems with PCMCIA/CF reader in -current.
I have a "Dazzle" CF/PCMCIA adapter, which I use to flash CF cards for some embedded devices. The notebook I use it on is a Fujistu lifebook P2120. With FreeBSD 4.8, I can dd to/from the CF card with this reader just fine. It has nary a problem. With any version of 5.x, I have a variety of problems including things like card insertion freezes the machine. I can switch consoles, but no output takes place. As soon as I remove the card all my typing "appears" in the various windows. If I do manage to reinsert it enough times so it doesn't hang, then a dd to/from the device will either occasionally hang it, or I will get a variety of I/O errors, usually relating to "device timeout". WHen this happens I cannot type anything until I pull the adapter out, so I can't do an atacontrol stuff, or look at console output, or anything... I really want this to work, but not sure what else I can do. 4.8 works fine with the exact notebook/CF adapter, everything. I try to update regularly, but so far, I don't believe a version of 5.x has ever worked. The problem with the full-time use of 4.8 is that I can't get my realtek or wifi (builtin) to work properly... Any tips/assistance appreciated. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any action on PR 10570 ? getting closer to 65K :-(
Interesting, I was considering trying this with a new UUNET connection with gated, but they're sending me 69,000+ routes. Glad I didn't try it yet. :) On Thu, 29 Apr 1999, Mike Tancsa wrote: > > I am currently using a couple of FreeBSD boxes for my border routers, and > it seems that the global routing table is getting closer and closer to 65K+ > routes (i.e. sooner than later I am going to bump into PR 10570). I am not > a systems programmer by any stretch of the imagination, so I would not know > how to go about debugging anything and everything that would be effected by > changing the size from a short to a long. I guess this PR only effects > very few people, so I can understand it not being a priority. But are > there any plans to look at it soon ? > > wat-border# netstat -nr | wc >59118 355941 4200959 > > > ---Mike > > Mike Tancsa,tel 01.519.651.3400 > Network Administrator, m...@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Jail ?
I agree, this would be way cool, and a valuable feature. On Tue, 4 May 1999, Sebastien GIORIA wrote: > Any chance to have jail include in the 3.x-STABLE before > the summer ? > > Thanks > > S. > > -- > --> Backbone Scoliosis <-- > Sebastien Gioria - FranceNet gio...@francenet.fr > Unix && Security Administrator secur...@francenet.fr > Tout FreeBSD en Francais => http://www.freebsd-fr.org > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
