Re: sysctl oids (was: Re: kvm question)
In message 199901242201.raa17...@khavrinen.lcs.mit.edu, Garrett Wollman write s: On Sun, 24 Jan 1999 13:11:12 -0800, Mike Smith m...@smith.net.au said: Backwards compatibility is one thing, but new nodes should be named, not numbered. OID_AUTO is bogus because it perpetuates the numbering of nodes. Nonsense. There are plenty of contexts in which a number makes far more sense than a name -- pretty much anything in any network stack other than Chaosnet, for example. If any of us ever make good on the threat of SNMP integration, having fixed numerical identifiers will be a requirement. BS! Yes, for systematic, programatically generated subtrees i could be an advantage implementation wise, but for the root of the subtree any anything else there is no reason to. You just look up the name once and cache the numeric OID. If anything we should get rid of as many users of the numeric OIDs as possible... -- 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
Re: 4.0-Current, netscape halts system
On Sun, Jan 24, 1999 at 04:21:16PM -0800, Amancio Hasty ha...@rah.star-gate.com wrote: http://www.developer.com/experts/expertspanel.html click on Bar's Guide to the the Interactive Fiction and after the page finishes loading click Back on Netscape's tool bar. Instant core -dump. You are right. I'm running previously called 3.0-CURRENT and Netscape Navigator 4.5. Sources are from Dec.29 1998. Also I'm getting coredumps when loading a huge page containing tables(table) and then using back. It always crashes when going back, not on initial loading. Why ? -- Vallo Kallaste va...@matti.ee To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
I think this is the first step to show the bug . The next step is to pray that the netscape developer is listening so he can fix it . I think is odd that the bug doesn't happen with the linux version of netscape. Cheers, Amancio On Sun, Jan 24, 1999 at 04:21:16PM -0800, Amancio Hasty ha...@rah.star-gate.com wrote: http://www.developer.com/experts/expertspanel.html click on Bar's Guide to the the Interactive Fiction and after the page finishes loading click Back on Netscape's tool bar. Instant core -dump. You are right. I'm running previously called 3.0-CURRENT and Netscape Navigator 4.5. Sources are from Dec.29 1998. Also I'm getting coredumps when loading a huge page containing tables(table) and then using back. It always crashes when going back, not on initial loading. Why ? -- Vallo Kallaste va...@matti.ee To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm question
On Sun, 24 Jan 1999, Mike Smith wrote: On Sat, 23 Jan 1999 11:04:15 -0800 (PST), Archie Cobbs arc...@whistle.com said: Peter pointed out that having the sysctl's as symbols was a nice advantage of the current system. How important is this? I don't think it's important at all. (Then again, I liked the old system.) If we were willing to give this up, then the SYSCTL() macro could just expand to a SYSINIT() that called sysctl_add_subtree() (or whatever you want to call it) upon loading. Seems reasonable to me. The only problem with this is likely to be OID_AUTO, which I happen to think is bogus anyway. It is vital that we maintain the ability to reference sysctl entities by compile-time constant integers, so as not to break backwards compatibility with other 4.4 systems and the Stevens books. Backwards compatibility is one thing, but new nodes should be named, not numbered. OID_AUTO is bogus because it perpetuates the numbering of nodes. ...that is, IFF we're going to keep the number/name pairs as OIDs, and not only the numbers, which seems more appropriate... Andrzej Bialecki ++---++ - ab...@nask.pl ||PicoBSD|| FreeBSD in your pocket? Go and see: Research Academic |+---+| Small Embedded FreeBSD Network in Poland | |TT~~~| |http://www.freebsd.org/~picobsd/ ~-+==---+-+ - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New Syscons and GGI
Hi! Now that the console system is restructured, shouldn't we consider using GGI instead of inventing the wheel? I happened to find this link and they seem to be positive to supporting FreeBSD. http://synergy.caltech.edu/~ggi/mailinglist/ev-mar98/139.html == Regards: Tommy - The source of all good beers... thallg...@yahoo.com _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
:
: Basically this consists of a bit of code in /etc/rc and, later tonight,
: an /etc/rc.diskless script ( a new script ).
:
:before you reinvent the wheel, have you looked at my code in
:http://www.iet.unipi.it/~luigi/diskless981113/
:
:this is sliglthly pout of date wrt what i have now (an rc.diskless
:file, which essentially contains all rc modifications that you see in
:the above web page)
:
: cheers
: luigi
:---+-
: Luigi RIZZO .
I was basically just cleaning up stuff I've been using for several
months.
Your stuff looks quite similar.
What I propose is that a new kernel sysctl variable be added called
'kern.conf_dir' which the kernel initially sets to nothing.
We modify /etc/rc to detect a diskless boot ( trivial ) ... the
rc.diskless code must run before just about anything else since
the filesystems are all NFS read-only mounts ( and we want to be able
to leave them that way ).
rc.diskless figures out the IP address BOOTP assigned us and changes
kern.conf_dir to point to /conf/$IP.
/etc/rc.conf is then made 'smart' about where to look for rc.conf.local
and /etc/rc is also made smart about where to look for rc.local.
Specifically, if someone has set kern.conf_dir, *that* is where they
look.
Here is the proposed change to /etc/rc.conf ( the tail end of it ). Rather
then look for and source /etc/rc.conf.local, it uses kern.conf_dir.
##
### Allow local configuration override at the very end here ##
##
#
# If the kernel configuration script MIB exists, use it.
sysctl -n kern.conf_dir /dev/null 21
if [ $? = 0 ]; then
conf_dir=`sysctl -n kern.conf_dir`
fi
if [ X$conf_dir = X ]; then
conf_dir=/etc
fi
if [ -f $conf_dir/rc.conf.local ]; then
. $conf_dir/rc.conf.local
fi
/etc/rc must be modified to do something similar when it is ready to
run /etc/rc.local -- it would use ${kern.conf_dir}/rc.local instead.
The only non-standard item is that /etc/rc needs to bypass the standard
disk configuraton code on a diskless boot, because the fstab is the
server's, not the diskless workstation's.
My proposal pretty much keeps intact the rc / rc.conf mechanism and simply
'moves' where rc and rc.conf look for rc.local and rc.conf.local, plus
a little additional magic to allow it to hook all the MFS filesystems
into the system.
Of course, then there are all the files in /conf/IPADDRESS/... actually
not too many, but these require a little more customization depending
on how you like to setup your server.
I haven't committed the whole thing yet, I would like to get feedback on
the general idea before I do so. But it is ready to go now.
#!/bin/sh
# $Id: rc,v 1.170 1999/01/25 04:40:53 dillon Exp $
# From: @(#)rc5.27 (Berkeley) 6/5/91
#...
stty status '^T'
# Set shell to ignore SIGINT (2), but not children;
# shell catches SIGQUIT (3) and returns to single user after fsck.
trap : 2
trap : 3# shouldn't be needed
HOME=/; export HOME
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin
export PATH
# BOOTP diskless boot. We have to run the rc file early in order to
# handle read-only NFS mounts, where the various config files
# in /etc often don't apply. rc.diskless may terminate the rc script
# early or it may fall through, depending on the case.
#
if [ -f /etc/rc.diskless ]; then
if [ `/sbin/sysctl -n vfs.nfs.diskless_valid` != 0 ]; then
. /etc/rc.diskless
fi
fi
# Configure ccd devices.
if [ X$skip_diskconf != XYES -a -f /etc/ccd.conf ]; then
ccdconfig -C
fi
...
if [ X$skip_diskconf != XYES ]; then
swapon -a
fi
if [ X$skip_diskconf != XYES -a $1x = autobootx ]; then
...
else
echo Skipping disk checks ...
fi
( a couple of more minor skip_diskconf checks )
# Run custom disk mounting function ( typically setup by rc.diskless )
#
if [ X$diskless_mount_func != X ]; then
$diskless_mount_func
fi
... normal rc continues ...
# Do traditional rc.local file if it exists.
#
if [ -f $conf_dir/rc.local ]; then
echo -n 'starting local daemons:'
sh $conf_dir/rc.local
echo '.'
fi
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
199901250453.uaa00...@apollo.backplane.comMatthew Dillon writes: archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024 1024+0 records in 1024+0 records out 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec) 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w I'm getting the very same speed (on 3.0-RELEASE). 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 [no overclocking] ide_pci0: VIA 82C586x (Apollo) Bus-master IDE controller rev 0x06 on pci0.7.1 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): ST31722A, DMA, 32-bit, multi-block-16 wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S What should I check? Alex. -- Alexander B. Povolotsky[ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tark...@asteroid.svib.ru] [Urgent messages: 234-9696 аб.#35442 or tark...@pager.express.ru] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
(cont.) New Syscons and GGI
I found this log of an GGI irc meeting. http://www.uk.ggi-project.org/irc/irc-980920-log == Regards: Tommy - The source of all good beers... thallg...@yahoo.com _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3.0-CURRENT - RELENG_3: trouble ?
Marco van Hylckama Vlieg wrote: I'm running 3.0-CURRENT at the moment, last timme I built world is about 2 or 3 weeks ago I guess. What I want to do is go to 3.0-RELEASE and from then start keeping track of the 3.x-STABLE branch. Since I've read a lot about various problems people had with this I now wonder: is it safe to CVSUP to RELENG_3 right now or will bad things happen? I don't want to mess up my system. I did the 3.0-CURRENT -- 3.0-STABLE transition the last weekend without _any_ problem. Usually I cvsup every night, but I disabled this process just before the branch. One day after the branch I restarted the cvsup procedure, this time tracking RELENG_3. I made the world on last Saturday and everything worked fine [as usual :-)]. If someone could give me some guidelines on how to get going on the above described track or point me to a webpage/document or anything else that describes what to do I'd be eternally grateful. At the moment it's very unclear to me what to do and whether I'll be able to boot and/or login to my system after I went to RELENG_3. I'm running 3.0-CURRENT with everything ELF including the kernel. If you made the world before, simply repeat the procedure. Remember that there is an excellent tutorial written by Nik Clayton. -- JMA --- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 --- Go ahead... make my day. - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New Syscons and GGI
It seems Tommy Hallgren wrote: Hi! Now that the console system is restructured, shouldn't we consider using GGI instead of inventing the wheel? I happened to find this link and they seem to be positive to supporting FreeBSD. http://synergy.caltech.edu/~ggi/mailinglist/ev-mar98/139.html Hmm, I've been following what they are doing for quite awhile, and frankly I dont see why we should move at this point in time. However it is possible to write a KLD module that would provide the hooks for a GGI compliant interface, so you could write such a beast if you want GGI functionality. There also is a licencing problem with GGI, the kernel gunk is IIRC free under a BSD like licence, but the userland stuff are GPL, which we try to stay clear of for obvious reasons. - Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
: Basically this consists of a bit of code in /etc/rc and, later tonight, : an /etc/rc.diskless script ( a new script ). : :before you reinvent the wheel, have you looked at my code in :http://www.iet.unipi.it/~luigi/diskless981113/ ... I was basically just cleaning up stuff I've been using for several months. me too :) Your stuff looks quite similar. What I propose is that a new kernel sysctl variable be added called 'kern.conf_dir' which the kernel initially sets to nothing. ok, i can only suggest that if you replace the sysctl kern.conf_dir variable with a shell variable as i did, you can achieve a more portable result (this also in light of Jordan's idea of having a 2.2S CD being made... putting patches for diskless into some 'xperimnt' directory would be helpful). Other than that, i have no objections, and i am very glad you raised the issue since i am using diskless machines a lot! I haven't seen how you suggest to buildpopulate the MFS filesystems -- right now i use a rather crude method of putting all the stuff in a tgz archive on the server and expanding it at runtime on the client. I haven't solved the problem with passwords (i.e. i just copy the files from the server. -- this is clearly a security hole, perhaps YP-based solutions would be much better). cheers luigi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Jan 21, 9:40pm, Warner Losh wrote: } Subject: Re: keymaps } In message 199901220043.laa22...@lightning.itga.com.au Gregory Bond writes: } : my vote: A version of the standard keymap with CapsLock and LeftCtl } : functions swapped so the control key is under my left finger like } : God intended! } } What's wrong with us.unix.kbd? Two things for me: It's not in the sysinstall menu. I'm not sure I like the Esc - ~` swap. Does anyone know of any decent PC keyboards with a Unix-friendly layout? I'm pretty happy with the layout on a Sun Type-5 keyboard, which puts Esc right above Tab and to the left of 1 (where PC's generally have ~`). The Return key is wide, but is confined to the home row, and Backspace is also wide and is in the row immediately above it. This leaves room in the top row (below the function keys, where PC's put Backspace), for |\, which PC keyboards put in various random places, and ~`. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
Luigi Rizzo wrote: [..] I haven't seen how you suggest to buildpopulate the MFS filesystems -- right now i use a rather crude method of putting all the stuff in a tgz archive on the server and expanding it at runtime on the client. I haven't solved the problem with passwords (i.e. i just copy the files from the server. -- this is clearly a security hole, perhaps YP-based solutions would be much better). Didn't Matt have patches for initializing a MFS from a mmap'ed file rather than from swap at some point? Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
Hi, Just finsihed upgrading to 4.0-Current, and both my machines now come up with: wd0: DMA failure, DMA status 0 wd0: DMA failure, DMA status 0 wd2: DMA failure, DMA status 0 wd2: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 wd3: DMA failure, DMA status 0 wd3: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 (basically that error for all IDE drives installed). Both motherboards are P-Pro's (ones a dual, ones a single) - using Intel 440FX chipset's... DMesg shows: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20002000 on isa wdc0: unit 0 (wd0): QUANTUM FIREBALL SE4.3A, DMA wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): QUANTUM FIREBALL ST2.1A, DMA wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x20002000 on isa wdc1: unit 0 (wd2): QUANTUM FIREBALL SE4.3A, DMA wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): QUANTUM SIROCCO2550A, DMA wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S I never got these 'failures' before... (They keep popping up on the console as well :-( Can they be ignored? Can they be fixed? :) - The drives appear to work OK... The more the drives get access, the more messages I get (I guess understandably)... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
It seems Karl Pielorz wrote:
This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :(
The following patchh cures the mess, and fixes a couble of other
nits as well:
-Søren
Index: wd.c
===
RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v
retrieving revision 1.186
diff -u -r1.186 wd.c
--- wd.c1999/01/17 05:46:24 1.186
+++ wd.c1999/01/19 18:29:23
@@ -1084,10 +1086,11 @@
du = wddrives[dkunit(bp-b_dev)];
/* finish off DMA */
- if (du-dk_flags (DKFL_DMA|DKFL_USEDMA)) {
+ if ((du-dk_flags (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) {
/* XXX SMP boxes sometimes generate an early intr. Why? */
- if ((wddma[du-dk_interface].wdd_dmastatus(du-dk_dmacookie)
WDDS_INTERRUPT)
- != 0)
+ if ((wddma[du-dk_interface].wdd_dmastatus(du-dk_dmacookie)
+ WDDS_INTERRUPT) == 0)
+ return;
dmastat = wddma[du-dk_interface].wdd_dmadone(du-dk_dmacookie);
}
@@ -1568,6 +1571,7 @@
if (wdwait(du, 0, TIMEOUT) 0)
return (1);
if( command == WDCC_FEATURES) {
+ outb(wdc + wd_sdh, WDSD_IBM | (du-dk_unit 4) | head);
outb(wdc + wd_features, count);
if ( count == WDFEA_SETXFER )
outb(wdc + wd_seccnt, sector);
@@ -2289,9 +2293,8 @@
{
int err = 0;
- if ((du-dk_flags (DKFL_DMA|DKFL_USEDMA)) du-dk_dmacookie)
+ if ((du-dk_flags (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA)
wddma[du-dk_interface].wdd_dmadone(du-dk_dmacookie);
-
(void)wdwait(du, 0, TIMEOUT);
outb(du-dk_altport, WDCTL_IDS | WDCTL_RST);
DELAY(10 * 1000);
Hi,
Just finsihed upgrading to 4.0-Current, and both my machines now come up with:
wd0: DMA failure, DMA status 0
wd0: DMA failure, DMA status 0
wd2: DMA failure, DMA status 0
wd2: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
wd3: DMA failure, DMA status 0
wd3: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
wd1: DMA failure, DMA status 0
(basically that error for all IDE drives installed).
Both motherboards are P-Pro's (ones a dual, ones a single) - using Intel 440FX
chipset's...
DMesg shows:
wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20002000 on isa
wdc0: unit 0 (wd0): QUANTUM FIREBALL SE4.3A, DMA
wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): QUANTUM FIREBALL ST2.1A, DMA
wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0x20002000 on isa
wdc1: unit 0 (wd2): QUANTUM FIREBALL SE4.3A, DMA
wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S
wdc1: unit 1 (wd3): QUANTUM SIROCCO2550A, DMA
wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S
I never got these 'failures' before... (They keep popping up on the console as
well :-(
Can they be ignored? Can they be fixed? :) - The drives appear to work OK...
The more the drives get access, the more messages I get (I guess
understandably)...
-Kp
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: 4.0-Current, netscape halts system
I've a feeling that somewhere there is a memory problem. Netscape-specific perhaps, but I suspect otherwise due to what I've seen. For example: the one machine that I have which will constantly dump core when Netscape is run is an HP Vectra. I've tried 3.0, 2.2.8, all current patches, etc. Core dump. Yet when I loaded Linux, it worked without incident. I have not yet tried Linux emulation, but will give it a shot. I suspected that perhaps the netscape binary needed to be recompiled against a current system. Why? System calls are updated, etc. There might be something really funky going on. The fact that it's stripped of debugging symbols doesn't help much -- but perhaps someone more adept at debugging might take a moment to look into it. Forrest To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
On Mon, Jan 25, 1999 at 05:08:19PM +1100, Bruce Evans wrote:
Can you find out what chipset is in this guy? There's support for anything
Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V
right
now.
See kern/9550. The driver *used* to support my SiS chipset, but it no
longer does when both master and slave drive are present since I
updated about a week ago. Possibly the same bug is biting Matt.
The driver doesn't have any special support for SiS. It uses generic
support in some cases, apparently including your case. Recent fixes
made it actually initialize DMA on the correct drive, but the
initialization in generic_dmainit() is buggy (it assumes multi-word
DMA mode 2 but your IDE timing is apparently incompatible with this).
I also experienced breakage with a SiS chip set. The following lines of
code in generic_dmainit in ide_pci.c are the problem:
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf(generic_dmainit: could not set multiword DMA
mode!\n);
You can try the attached patch if you want. It seems to work here.
--
Richard Seamman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
Index: ide_pci.c
===
RCS file: /home/ncvs/src/sys/pci/ide_pci.c,v
retrieving revision 1.28
diff -c -r1.28 ide_pci.c
*** ide_pci.c 1999/01/17 05:46:25 1.28
--- ide_pci.c 1999/01/20 18:06:54
***
*** 110,115
--- 110,124
static void
generic_status(struct ide_pci_cookie *cookie);
+ static int
+ sis_dmainit(structide_pci_cookie *cookie,
+ struct wdparams *wp,
+ int (*wdcmd)(int, void *),
+ void*wdinfo);
+
+ static void
+ sis_status(struct ide_pci_cookie *cookie);
+
static void
via_571_status(struct ide_pci_cookie *cookie);
***
*** 279,285
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
!
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf(generic_dmainit: could not set multiword DMA
mode!\n);
return 1;
--- 288,294
/* If we're here, then this controller is most likely not set
for UDMA, even if the drive may be. Make the drive wise
up. */
!
if(!wdcmd(WDDMA_MDMA2, wdinfo))
printf(generic_dmainit: could not set multiword DMA
mode!\n);
return 1;
***
*** 303,308
--- 312,527
generic_status
};
+ /* SiS 5591 */
+
+ static int
+ sis_dmainit(struct ide_pci_cookie *cookie,
+ struct wdparams *wp,
+ int(*wdcmd)(int, void *),
+ void *wdinfo)
+ {
+ int r;
+ unsigned int workword, new, mask;
+ int ctlr, unit;
+ int iobase_bm;
+ pcici_t tag;
+ int unitno;
+
+ unit = cookie-unit;
+ ctlr = cookie-ctlr;
+ iobase_bm = cookie-iobase_bm;
+ tag = cookie-tag;
+
+ unitno = ctlr * 2 + unit;
+
+ if (udma_mode(wp) = 2) {
+ workword = pci_conf_read(tag, ctlr * 4 + 0x40);
+
+ /* These settings are a little arbitrary. They're taken from my
+* system, where the BIOS has already set the values, but where
+* we don't detect that we're initialized because the
+* BMISTA_DMA?CAP values aren't set by the BIOS.
+* 0x8000 turns on UDMA
+* 0x2000 sets UDMA cycle time to 2 PCI clocks for data out
+* 0x0300 sets DATC to 3 PCI clocks
+* 0x0001 sets DRTC to 1 PCI clock
+*/
+ if (unit) {
+ mask = 0x;
+ new = 0xa301;
+ } else {
+ mask = 0x;
+ new = 0xa301;
+ }
+
+ workword = mask;
+ workword |= new;
+
+ pci_conf_write(tag, ctlr * 4 + 0x40, workword);
+
+ outb(iobase_bm + BMISTA_PORT,
+(inb(iobase_bm + BMISTA_PORT) | ((unit == 0) ?
BMISTA_DMA0CAP : BMISTA_DMA1CAP)));
+
+ if (bootverbose)
+ printf(SiS 5591 dmainit: %s drive %d setting ultra DMA
mode 2\n,
+ unitno 2 ? primary : secondary,
+ unitno 1);
+ r = wdcmd(WDDMA_UDMA2, wdinfo);
+ if (!r) {
+ printf(SiS 5591 dmainit: %s drive %d
Re: IDE DMA works, I'll be a...
On Mon, Jan 25, 1999 at 12:11:01PM +0300, Alex Povolotsky wrote: 199901250453.uaa00...@apollo.backplane.comMatthew Dillon writes: archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024 1024+0 records in 1024+0 records out 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec) 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w I'm getting the very same speed (on 3.0-RELEASE). 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 [no overclocking] ide_pci0: VIA 82C586x (Apollo) Bus-master IDE controller rev 0x06 on pci0.7.1 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): ST31722A, DMA, 32-bit, multi-block-16 wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S What should I check? You need to update to 3.0-STABLE; bde committed some fixes to the VIA UDMA code there. -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| |lcrem...@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
[.] So I'd like to make another attempt to get agreement on the next step here, so that *something* can happen. We need to get more people using DEVFS, so we can gain some experience feedback. I don't think DEVFS has any issues that are not surmountable. However, at some point you must take the next step. [.] Comments?? The issue here is not whether this proposal is a sufficient *final* incarnation of DEVFS, but whether it's a sufficient next step.. How functional is DEVFS at the moment ? I was using it before the SLICE stuff was torn out, and gave up at that point. Without SLICE, does DEVFS create the devices with the same major/minor numbers as normal ? Without SLICE, is it necessary to have a /dev to boot off ? FWIW, I'm 100% behind DEVFS as none of the pitfalls affect me :-I -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com -- Brian br...@awfulhak.org br...@freebsd.org br...@openbsd.org http://www.Awfulhak.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
On Mon, Jan 25, 1999 at 04:09:27PM +0300, Alex Povolotsky wrote: 19990125080617.a3...@tidalwave.netLee Cremeans writes: ide_pci0: VIA 82C586x (Apollo) Bus-master IDE controller rev 0x06 on pci0. 7.1 Don't you know if I can upgrade only one file, ide_pci.c? STABLE seems to not much stable right now :-( Just updating wd.c and ide_pci.c should work. -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| |lcrem...@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KVA/KVM shortages
Previously on Thu, Jan 21, 1999 at 06:09:41PM +, Geoff Buckingham wrote: : On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with : 768MB RAM) poking about in the code adding: : : options VM_KMEM_SIZE=(24*1024*1024) : options VM_KMEM_SIZE_MAX=(128*1024*1024) : : seems like a good way foward. Is it? : As no one seemed to comment directly on this I thouht I would relay our experiances: panic: pmap_new_proc: u_map allocation failed Imediatly after the login promt appeared on the console:-( This was running UNI-proccessor with softupdates and ccd the application is disk and network heavy, circa 300 processes, however most memory is used as cache. This is 3.0-RELEASE with security fixes. -- GeoffB To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
Søren Schmidt wrote: This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :( The following patchh cures the mess, and fixes a couble of other nits as well: [snip] Thanks, the patch fixed the problem... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Stale files in /usr/lib
Hi folks, The following files are not being created by installworld: /usr/lib/crt0.o /usr/lib/c++rt0.o /usr/lib/gcrt0.o /usr/lib/scrt0.o /usr/lib/sgcrt0.o /usr/lib/kztail.o /usr/lib/kzhead.o Am I correct in assuming they're stale and can be removed? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Failure to make buildworld on RELENG_3
I completely re-cvsuped the sources and I still get errors in libpam.
Here is my make.conf:
# $Id: make.conf,v 1.70 1998/10/16 03:26:54 peter Exp $
#
# This file, if present, will be read by make (see /usr/share/mk/sys.mk).
# It allows you to override macro definitions to make without changing
# your source tree, or anything the source tree installs.
#
# This file must be in valid Makefile syntax.
#
# You have to find the things you can put here in the Makefiles and
# documentation of the source tree.
#
# One, and probably the most common, use could be:
#
CFLAGS= -O -pipe
#
# Another useful entry is
#
#NOPROFILE= true
# Avoid compiling profiled libraries
#
#INSTALL=install -C
# Compare before install
#
# To avoid building the default system perl
#NOPERL= true
# To avoid building the suid perl
#NOSUIDPERL= true
#
# To avoid building sendmail
#NO_SENDMAIL= true
#
# To have 'obj' symlinks created in your source directory
# (they aren't needed/necessary)
#OBJLINK= yes
#
# To compile just the kernel with special optimisations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway):
#
COPTFLAGS= -O -pipe
#
# To use an ELF kernel, you can set this flag. MAKE SURE that you have a
# working /boot/loader installed. /boot.config should specify
/boot/loader
# as the kernel. The bootblocks load the third stage loader, then it loads
# the kernel proper and any other modules you want. Its startup script
# file is /boot/loader.conf:
#
#KERNFORMAT= elf
#
# To compile and install the 4.4 lite libm instead of the default use:
#
#WANT_CSRG_LIBM= yes
#
# If you do not want unformatted manual pages to be compressed
# when they are installed:
#
#NOMANCOMPRESS= true
#
#
# If you want the compat shared libraries installed as part of your normal
# builds, uncomment these:
#
#COMPAT1X= yes
#COMPAT20= yes
#COMPAT21= yes
#
#
# If you do not want additional documentation (some of which are
# a few hundred KB's) for ports to be installed:
#
#NOPORTDOCS= true
#
#
# Default format for system documentation, depends on your printer.
# Set this to ascii for simple printers or screen
#
#PRINTERDEVICE= ps
#
#
# How long to wait for a console keypress before booting the default kernel.
# This value is approximately in milliseconds. Keypresses are accepted by
the
# BIOS before booting from disk, making it possible to give custom boot
# parameters even when this is set to 0.
#
#BOOTWAIT=0
#BOOTWAIT=3
#
# By default, the system will always use the keyboard/video card as system
# console. However, the boot blocks may be dynamically configured to use a
# serial port in addition to or instead of the keyboard/video console.
#
# By default we use COM1 as our serial console port *if* we're going to use
# a serial port as our console at all. (0x3E8 = COM2)
#
#BOOT_COMCONSOLE_PORT= 0x3F8
#
# The default serial console speed is 9600. Set the speed to a larger value
# for better interactive response.
#
#BOOT_COMCONSOLE_SPEED= 115200
#
#
# By default, this points to /usr/X11R6 for XFree86 releases 3.0 or earlier.
# If you have a XFree86 from before 3.0 that has the X distribution in
# /usr/X386, you want to uncomment this.
#
#X11BASE= /usr/X386
#
#
# If you have Motif on your system, uncomment this.
#
#HAVE_MOTIF= yes
#MOTIF_STATIC= yes
#
# If the default location of the Motif library (specified below) is NOT
# appropriate for you, uncomment this and change it to the correct value.
# If your motif is in ${X11BASE}/lib, you don't need to touch this line.
#
#MOTIFLIB= -L${X11BASE}/lib -lXm
#
#
# If you are running behind a firewall, uncomment the following to leave a
# hint for various make-spawned utilities that they should use passive FTP.
#
#FTP_PASSIVE_MODE= YES
#
# If you're resident in the USA, this will help various ports to determine
# whether or not they should attempt to comply with the various U.S.
# export regulations on certain types of software which do not apply to
# anyone else in the world.
#
USA_RESIDENT= YES
#
# Next one will help ports developers to debug
#
#FORCE_PKG_REGISTER=YES
#
#
# Port master sites.
#
# If you want your port fetches to go somewhere else than the default
# (specified below) in case the distfile/patchfile was not found,
# uncomment this and change it to a location nearest you. (Don't
# remove the /${DIST_SUBDIR}/ part.)
#
#MASTER_SITE_BACKUP?= \
# ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/
#
# If you want your port fetches to check the above site first (before
# the MASTER_SITES specified in the port Makefiles), uncomment the
# line below. You can also change the right side to point to wherever
# you want.
#
#MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP}
#
# Some ports use a special variable to point to a collection of
# mirrors of well-known software archives. If you have a mirror close
# to you, uncomment any of the following lines and change it to that
# address. (Don't remove the /%SUBDIR%/ part.)
#
# Note: the right hand sides
Re: DEVFS, the time has come...
Dear Archie, Can you point all people (and me of course) who want to test DEVFS to some common information about DEVFS (usage, possible advantages/disadvantages etc.)? I think some FAQ or so will be nice. It's really will help us to go further with this issue. Sincerely, Maxim Archie Cobbs wrote: This email was a few weeks ago, and there was a lively debate, then Julian sent an email listing some issues/requirements, and then the thread kindof died and now we're back to where we were before, which is not any further on.. [Skipped] Comments?? The issue here is not whether this proposal is a sufficient *final* incarnation of DEVFS, but whether it's a sufficient next step.. -Archie ___ Archie Cobbs?? *?? Whistle Communications, Inc.? *?? http://www.whistle.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
Re: sysctl oids (was: Re: kvm question)
On Sun, 24 Jan 1999 15:55:50 -0800 (PST), Matthew Dillon dil...@apollo.backplane.com said: Strings are a whole lot more portable then integer assignments. Nonsense. Strings are not portable at all -- they only exist in FreeBSD. The reference implementation (4.4BSD) and its other descendants use numbers. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | 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 majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
In article 399.917273...@axl.noc.iafrica.com, Sheldon Hearn a...@iafrica.com wrote: The following files are not being created by installworld: /usr/lib/crt0.o /usr/lib/c++rt0.o /usr/lib/gcrt0.o /usr/lib/scrt0.o /usr/lib/sgcrt0.o /usr/lib/kztail.o /usr/lib/kzhead.o Am I correct in assuming they're stale and can be removed? Yes, they all reside in /usr/lib/aout now. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysctl oids (was: Re: kvm question)
In message 199901251615.laa19...@khavrinen.lcs.mit.edu, Garrett Wollman write s: On Sun, 24 Jan 1999 15:55:50 -0800 (PST), Matthew Dillon dil...@apollo.backplane.com said: Strings are a whole lot more portable then integer assignments. Nonsense. Strings are not portable at all -- they only exist in FreeBSD. The reference implementation (4.4BSD) and its other descendants use numbers. Which is irrelevant, since they don't use sysctl for the same things as us anyway (apart from a very small subset which is ALREADY special cased in the kernel). -- 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
Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out L
In article 19990124225936p.wghi...@wghicks.bellsouth.net, W Gerald Hicks wghi...@bellsouth.net wrote: And if you have cvsup-mirror loaded (running cvsupd), you can even use cvsup against your local repository. Seems a good bit faster than regular CVS for checkouts and updates. It is _much_ faster. (I took some measurements a couple of years ago.) But you do lose the ability to do handy things like cvs diff, cvs log, and cvs ann. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
broken installworld when OBJLINK= yes
Hi, after several days fiddeling with the cvs and source trees I've finnaly found out, that setting OBJLINK= yes in /etc/make.conf breaks installworld's. Buildworld is successfully building the entire tree, but after that the obj link in the source-tree is pointing to an /usr/obj/aout/something and the install is failing to find the librarys. 2nd: Why is it neccessary to install shared libraries whit the schg flag set in the obj tree ? This successfully prevents from builds over nfs. sorry for my broken english Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13http://www.freibergnet.de/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote: Yes, they all reside in /usr/lib/aout now. So then for a machine that makes world with -DNOAUT they don't exist, assuming all ports have been rebuilt for an ELF world, yes? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
On 25-Jan-99 Sheldon Hearn wrote: On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote: Yes, they all reside in /usr/lib/aout now. So then for a machine that makes world with -DNOAUT they don't exist, -DNOAOUT assuming all ports have been rebuilt for an ELF world, yes? I don't know -- I've never used -DNOAOUT. :-) Somebody else will have to answer that one. Note, without those files you'll never again be able to link an a.out program on the machine. Are you sure you really want that limitation? John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't mount root. Really need help...
On Sun, 24 Jan 1999, Chris Knight wrote: Greetings, I have learned a very valuable lesson. No matter how many time I have made world, I shouldn't do it while I'm tired. Last night I synced my tree and made world. I rebooted, and was going to remake my kernel after the boot. That became an impossibility. Can't you boot kernel.old? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
On Mon, 25 Jan 1999 09:20:06 PST, John Polstra wrote: Note, without those files you'll never again be able to link an a.out program on the machine. Are you sure you really want that limitation? As I understand it, the only times this hurts me are: 1) When I want to build binaries for another (a.out-only) box. 2) When I want to use dynamically-linked a.out binaries that were compiled elsewhere on this box. Unless I'm missing something, I'm happy with that. Thanks for the feedback, I'll wait for someone else to answer on the other issue. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Dynamic sysctl registration
I've made some changes to sysctl to allow nodes to be declared dynamically either by loading kld modules which contain SYSCTL declarations or, in theory, by generating oids from some other kernel data such as the device tree. To recap for those that are interested, the existing scheme uses linker sets to represent interior nodes of the tree. Each child node has a pointer in its parent's linker set (contained in the parent's oid_arg1 field). This is hard to make dynamic because linker sets can't easily be extended without wastefully allocating and reallocating memory. I have changed the code to use an SLIST to store the list of children for an interior node. This has the advantage that nodes can be easily added and removed. There is an associated cost (about 8 bytes per node on i386) which I think is reasonable. All the oids in the kernel (or kld module) are collected together in a single linker set from which the tree is constructed by threading the oids onto their parent's list. The kernel-user interface is completely unchanged. If anyone is interested in seeing diffs (approx 23k), please contact me. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
: 'kern.conf_dir' which the kernel initially sets to nothing.
:
:ok, i can only suggest that if you replace the sysctl kern.conf_dir
:variable with a shell variable as i did, you can achieve a more
:portable result (this also in light of Jordan's idea of having a
:2.2S CD being made... putting patches for diskless into some
:'xperimnt' directory would be helpful). Other than that, i have no
:objections, and i am very glad you raised the issue since i am
:using diskless machines a lot!
That's what I had originally, but extracting the machine's IP
address is not trivial, and I didn't want to stick:
bootp_ifc=`route -n get default | fgrep interface | awk '{ print $2; }'`
bootp_ipa=`ifconfig $bootp_ifc | fgrep inet | head -1 | awk '{ print $2; }'`
In /etc/rc.conf in roder to synthesize the directory containing
rc.conf.local.
So I have rc.diskless figure it out and sto it in kern.conf_dir, and
rc.conf extracts it from that.
:I haven't seen how you suggest to buildpopulate the MFS filesystems --
:right now i use a rather crude method of putting all the stuff in a tgz
:archive on the server and expanding it at runtime on the client. I
:haven't solved the problem with passwords (i.e. i just copy the files
:from the server. -- this is clearly a security hole, perhaps YP-based
:solutions would be much better).
:
: cheers
: luigi
There isn't much to build. Most of the MFS filesystems start out
empty.
test2:/home/dillon df
Filesystem 1K-blocks UsedAvail Capacity Mounted on
209.157.86.2:/ 63503464471197680%/
209.157.86.2:/usr 508143 320642 14685069%/usr
209.157.86.2:/var63503123334609021%/var
mfs:42 959 70 813 8%/var/run
mfs:447903 596 6675 8%/var/db
mfs:46 31743429200 0%/var/tmp
mfs:48 31743829196 0%/var/spool
procfs 440 100%/proc
mfs:661511 58 1333 4%/dev
mfs:79 31743 198927215 7%/home
/var/run- starts out empty
/var/db - starts out empty
/var/tmp- starts out empty
/var/spool - simple skeleton directory structure
/dev- mount server:/ to a temporary place and use cpio to populate
/home - populate from template ( up to the user, I include a sample )
If I wanted to make a full system, I suppose I would make /var an MFS
filesystem too and use the system mtree to create it's directory structure.
But most diskless workstations do not need to run cron :-)
-Matt
Matthew Dillon
dil...@backplane.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
I sure did, but I never committed them. I would have to redo them at this point. The patch was to have MFS maintain a persistant file, so you could fsck the file as if it were a disk and then the mfs mount it. Security is an issue, but it depends on how your password file is setup. You don't have to export the server's own root - the key thing is that you want to export a shared root to all the workstations, so it would not be too hard to implement kerberos as an authentication mechanism for the workstations. At home, I just export my server's root. Point #2 is, of course, that you export a read-only root. -Matt Matthew Dillon dil...@backplane.com : :Luigi Rizzo wrote: :[..] : I haven't seen how you suggest to buildpopulate the MFS filesystems -- : right now i use a rather crude method of putting all the stuff in a tgz : archive on the server and expanding it at runtime on the client. I : haven't solved the problem with passwords (i.e. i just copy the files : from the server. -- this is clearly a security hole, perhaps YP-based : solutions would be much better). : :Didn't Matt have patches for initializing a MFS from a mmap'ed file rather :than from swap at some point? : :Cheers, :-Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KVA/KVM shortages
If you can get a kernel core, run vmstat -m on it to see what the state of the allocation hoppers was. -Matt Matthew Dillon dil...@backplane.com :As no one seemed to comment directly on this I thouht I would relay our :experiances: : :panic: pmap_new_proc: u_map allocation failed : :Imediatly after the login promt appeared on the console:-( : :This was running UNI-proccessor with softupdates and ccd the application :is disk and network heavy, circa 300 processes, however most memory is :used as cache. : :This is 3.0-RELEASE with security fixes. : :-- :GeoffB : :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: Stale files in /usr/lib
On Mon, 25 Jan 1999, John Polstra wrote: On 25-Jan-99 Sheldon Hearn wrote: On Mon, 25 Jan 1999 08:32:17 PST, John Polstra wrote: Yes, they all reside in /usr/lib/aout now. So then for a machine that makes world with -DNOAUT they don't exist, -DNOAOUT assuming all ports have been rebuilt for an ELF world, yes? I don't know -- I've never used -DNOAOUT. :-) Somebody else will have to answer that one. I did make buildworld with -DNOAOUT on -stable and it went fine. I did make installworld and it croaked because it couldn't find the afforementioned files. Now I know what is up! The answer to your question is: those files don't exist on a -DNOAOUT build as evidence by the error message I recieved. :) Catchya Later, | Give me UNIX or give me a typewriter. Jason Wells | http://www.freebsd.org/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
19990125083308.b3...@tidalwave.netLee Cremeans writes: On Mon, Jan 25, 1999 at 04:09:27PM +0300, Alex Povolotsky wrote: 19990125080617.a3...@tidalwave.netLee Cremeans writes: ide_pci0: VIA 82C586x (Apollo) Bus-master IDE controller rev 0x06 on pc i0. 7.1 Don't you know if I can upgrade only one file, ide_pci.c? STABLE seems to no t much stable right now :-( Just updating wd.c and ide_pci.c should work. No. wd.c requires some more files. I'd better wait a bit, unless some kind sou l will tell me what and how should I do. opt_ide_delay.h is the missing one for wd.c, and just updating ide_pci.c results in totally broken wd. Alex. -- Alexander B. Povolotsky[ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tark...@asteroid.svib.ru] [Urgent messages: 234-9696 аб.#35442 or tark...@pager.express.ru] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
On Mon, 25 Jan 1999 18:06:15 GMT, Jason C. Wells wrote: I did make buildworld with -DNOAOUT on -stable and it went fine. I did make installworld and it croaked because it couldn't find the afforementioned files. Well, their absence certainly doesn't blow up installworld on a -current machine. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
: 'kern.conf_dir' which the kernel initially sets to nothing.
:
:ok, i can only suggest that if you replace the sysctl kern.conf_dir
:variable with a shell variable as i did, you can achieve a more
...
That's what I had originally, but extracting the machine's IP
address is not trivial, and I didn't want to stick:
bootp_ifc=`route -n get default | fgrep interface | awk '{ print $2; }'`
bootp_ipa=`ifconfig $bootp_ifc | fgrep inet | head -1 | awk '{ print $2;
}'`
I think it is much easier than that. The kernel BOOTP support sets
the machine's hostname, so you can do something like
if [ `hostname` = ]
then
# regular non-bootp sequence
mount -u -o rw /
...
mount -a -t nonfs
else
. /etc/rc.diskless
fi
if you want, save the `hostname` before executing rc.network to
remember if you started as diskless or not.
:I haven't seen how you suggest to buildpopulate the MFS filesystems --
...
There isn't much to build. Most of the MFS filesystems start out
empty.
ok here we use a different approach. For simplicity I am using a
single MFS system with all the things you put in /var, and including
/var/dev and /var/etc (with /dev - /var/dev and /etc - /var/etc
on the diskless machine).
cheers
luigi
---+-
Luigi RIZZO .
EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione
HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
---+-
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: kvm question
Excerpts from FreeBSD-Current: 24-Jan-99 Re: kvm question by Archie co...@whistle.com Whether libkvm should even exist in a perfect world (it shouldn't) is an entirely different question. For now, we're stuck with it until somebody changes *everything* to use sysctl instead. Just as a question, how much of a performance difference is there between using libkvm and sysctl? If I were looking for a way to keep constant tabs on system performance with the minimal impact (think top, xsysinfo, sysstat, etc), which would I want to use if any difference exists at all? My suspicion would be that sysctl might actually be faster unless libkvm mmap's /dev/kmem so then that would elimiate the need for syscalls. libkvm may never fully die to support 3rd party software, but that is no reason to not upgrade the userland we do have control over so that ps and top will work under any kernel upgrade. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
yo, brian, are you on 'net'? have you had a look at the netgraph stuff? particularly the kernel nodes that we use in conjuntion with mpd, and the usserland modules of mpd that we use with it? On Mon, 25 Jan 1999, Brian Somers wrote: [.] So I'd like to make another attempt to get agreement on the next step here, so that *something* can happen. We need to get more people using DEVFS, so we can gain some experience feedback. I don't think DEVFS has any issues that are not surmountable. However, at some point you must take the next step. [.] Comments?? The issue here is not whether this proposal is a sufficient *final* incarnation of DEVFS, but whether it's a sufficient next step.. How functional is DEVFS at the moment ? I was using it before the SLICE stuff was torn out, and gave up at that point. Without SLICE, does DEVFS create the devices with the same major/minor numbers as normal ? Without SLICE, is it necessary to have a /dev to boot off ? FWIW, I'm 100% behind DEVFS as none of the pitfalls affect me :-I -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com -- Brian br...@awfulhak.org br...@freebsd.org br...@openbsd.org http://www.Awfulhak.org Don't _EVER_ lose your sense of humour ! 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: DEVFS, the time has come...
Brian Somers writes: So I'd like to make another attempt to get agreement on the next step here, so that *something* can happen. We need to get more people using DEVFS, so we can gain some experience feedback. I don't think DEVFS has any issues that are not surmountable. However, at some point you must take the next step. [.] Comments?? The issue here is not whether this proposal is a sufficient *final* incarnation of DEVFS, but whether it's a sufficient next step.. How functional is DEVFS at the moment ? I was using it before the SLICE stuff was torn out, and gave up at that point. Without SLICE, does DEVFS create the devices with the same major/minor numbers as normal ? Without SLICE, is it necessary to have a /dev to boot off ? You would have to ask Julian this question. However, my impression is that there are a couple of things that are broken, but nothing too serious that it can't be fixed/updated relatively quickly. Julian, is that accurrate? What about the MFS problem -- how hard is that to fix? I.E. What's required to get DEVFS to the point where 'the masses' (including me :-) can use it with minimal pain/disruption? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
On Sun, 24 Jan 1999, Jordan K. Hubbard wrote: I really don't understand the problems that everyone is having, myself. I've been running netscape (communicator 4.5) in -current for ages now and just switched to 4.0 without any problems. My netscape still continues to function just fine and has never crashed any of my system so much as once. Why the wide disparity in experience, I wonder? One variable may be available memory. On my system, with default datasize limit of 16M from login.conf, Netscape coredumps very frequently. With datasize unlimited, Netscape eats all the available swap (this system is 64M real 128M swap) and kills the system that way. I currently run Netscape with datasize set to 64M, pending a new disc for more swap! In this configuration, Netscape either coredumps or starts behavhing oddly about once every 3 days, but at least I can just restart it rather than needing to reboot after a swap outage. Colour depth also has an effect - changing from 8-bit to 32-bit on the X server seems to have made this worse (as you might expect). To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
Nate Williams writes: I am current as of today 4.0, I have communicator 4.5 downloaded some time ago (November more or less) directly from netscape and installed in /usr/local/netscape with a link to /usr/local/bin/netscape and I have been using it all day with no problems. My intranet if full of java and haven't had a problem, knock on wood:-) I just downloaded a 9M file after reading your mail to see if that would cause a problem and it didn't. Netscape is as stable as ever on FreeBSD Current 4.0 for me. That bothers me:-) I wonder why? I'm running 2.2-stable, so maybe that's a difference. Me too... (I get crashes running Java) -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Reboot after intense disk activity
I've been having a problem ever since I moved from 2.2.8-STABLE to 3.0-CURRENT (all elf). After long periods of intense disk activity (e.g. rm -rf * in /usr/obj or a make world) my keyboard seems to become less responsive and I can hear a quick burst of disk activity with each key press. On a couple of occasions the machine has then frozen for a few seconds (with the disk LED lit) and then rebooted. This happened last night following a cvsup of RELENG_3, removal of /usr/obj then a make buildworld. My system is current as of 16/1/99. When the machine reboots there are no core files, nothing unexpected in /var/log/messages and only around 128K of swap used (out of 160MB). Machine spec: P133, Intel 82371FB IDE controller, 2GB Seagate IDE disk, 3.2GB Quantum hard disk, 80MB RAM, 4MB Matrox Mystique 220 graphics card. Please let me know if further information is needed. Thanks, Mike -- Mike Zanker, Academic Computing Service, The Open University, UK Tel: +44 1908 652726, Fax: +44 1908 652193 Views expressed are personal and do not necessarily reflect University opinion. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
On Mon, 25 Jan 1999 18:28:10 GMT, Andrew Gordon wrote: One variable may be available memory. On my system, with default datasize limit of 16M from login.conf, Netscape coredumps very frequently. Aha! That figures. Since I upgraded to CURRENT, with its login.conf which defaults to unlimited resources, my frequent netscape core dumps have gone away. I hadn't realized why until now. Suggestion: wwhen people complain about Netscape, ask them to mail us back the output of ``ulimit -a''. Thanks, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Stale files in /usr/lib
On Mon, 25 Jan 1999, Jason C. Wells wrote: [..\ I did make buildworld with -DNOAOUT on -stable and it went fine. I did make installworld and it croaked because it couldn't find the afforementioned files. You need to make installworld with -DNOAOUT too. Otherwise it _will_ look for a.out stuff to install. Now I know what is up! - alex | Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat. | | Powered by FreeBSDhttp://www.freebsd.org/ | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
:One variable may be available memory. On my system, with default datasize :limit of 16M from login.conf, Netscape coredumps very frequently. With :datasize unlimited, Netscape eats all the available swap (this system is :64M real 128M swap) and kills the system that way. I currently run :Netscape with datasize set to 64M, pending a new disc for more swap! In :this configuration, Netscape either coredumps or starts behavhing oddly :about once every 3 days, but at least I can just restart it rather than :needing to reboot after a swap outage. : :Colour depth also has an effect - changing from 8-bit to 32-bit on the X :server seems to have made this worse (as you might expect). I've been using netscape on a 24bit color system for well over a year and have never had a serious memory leak problem or X session ( or machine ) crashing due to it. I don't leave the netscape window open all the time, though... I tend to exit out of it when I'm not using it. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dynamic sysctl registration
Doug Rabson writes: I've made some changes to sysctl to allow nodes to be declared dynamically either by loading kld modules which contain SYSCTL declarations or, in theory, by generating oids from some other kernel data such as the device tree. To recap for those that are interested, the existing scheme uses linker sets to represent interior nodes of the tree. Each child node has a pointer in its parent's linker set (contained in the parent's oid_arg1 field). This is hard to make dynamic because linker sets can't easily be extended without wastefully allocating and reallocating memory. I have changed the code to use an SLIST to store the list of children for an interior node. This has the advantage that nodes can be easily added and removed. There is an associated cost (about 8 bytes per node on i386) which I think is reasonable. All the oids in the kernel (or kld module) are collected together in a single linker set from which the tree is constructed by threading the oids onto their parent's list. The kernel-user interface is completely unchanged. If anyone is interested in seeing diffs (approx 23k), please contact me. I'm interested.. could you email me the diffs? I'm more interested in whether these patches can be committed... ? Have Poul, DG, et. al. seen them? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm question
Thomas Valentino Crimi writes: Whether libkvm should even exist in a perfect world (it shouldn't) is an entirely different question. For now, we're stuck with it until somebody changes *everything* to use sysctl instead. Just as a question, how much of a performance difference is there between using libkvm and sysctl? If I were looking for a way to keep constant tabs on system performance with the minimal impact (think top, xsysinfo, sysstat, etc), which would I want to use if any difference exists at all? My suspicion would be that sysctl might actually be faster unless libkvm mmap's /dev/kmem so then that would elimiate the need for syscalls. libkvm is probably faster, but it really doesn't matter because they're both probably about the same and the application for this stuff is not performance critical. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Dynamic sysctl registration
In message 199901252212.oaa18...@bubba.whistle.com, Archie Cobbs writes: Doug Rabson writes: If anyone is interested in seeing diffs (approx 23k), please contact me. I'm interested.. could you email me the diffs? I'm more interested in whether these patches can be committed... ? Have Poul, DG, et. al. seen them? I'm somewhat weary of doing too much for sysctl, until we have intelligently examined the stuff and decided which way we want to go with it. (This patch is probably perfectly all right, without this comment being construed as a Reviewed by: :-), but before it goes in, I would like to hear if sysctl is basically what we want or if sysctl needs to be extended (for instance in the repository direction) ? One of the weak points about the current sysctl scheme is the rather simpleminded permission scheme, will we need something more capable ? The current system is capable if you write it yourself in a function, but we don't want 100 functions doing the same thing.) We probably also need to consider name-space management... And, documentation. I do like the semi-literate programming style, where you can stick a meaningfull documentation (ie, potentially several pages of it) right there in the source, (but I don't want it compiled in and loaded!) but for it to become real documentation, SGML or -man will be needed, and that would probably be too ugly for most eyes, or no ? -- 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
removing f2c from base distribution
Ladies and Gents,
I have completed the portification of f2c and its support library.
In principle, src/usr.bin/f2c, src/lib/{libI77,libF77,libf2c}, and
src/gnu/usr.bin/cc/f77 can be moved into the attic in -current (4.x).
Appropriate adjustments to the Makefile files in src/usr.bin,
src/lib, and src/gnu/usr.bin/cc need to be made.
ftp://troutmask.apl.washington.edu/pub/f2c-freebsd.2.0.1.tar.gz
ftp://troutmask.apl.washington.edu/pub/f2c-freebsd.tgz
ftp://troutmask.apl.washington.edu/pub/f77-freebsd.0.3.tar.gz
ftp://troutmask.apl.washington.edu/pub/f77-freebsd.tgz
f2c-freebsd.2.0.1.tar.gz is a version of f2c and its library
where I have merged the version in the FreeBSD source tree from
Dec 1998 with the latest version of f2c and its library from
www.netlib.org. The Makefile in f2c-freebsd.2.0.1/libf2c is setup
to build only ELF libraries which is reasonable because this is
as a replacement for functionality in a post-elf-transition source
tree.
f2c-freebsd.tgz is a gzipped tar file of the port. It should
be placed in ports/lang. When unpacked it will produce a
directory named f2c-freebsd, and it should be able to be built
on both i386 and alpha axp architectures.
f77-freebsd.0.3.tar.gz contains the source code for a new driver
utility that is meant to replace the current f77(1) in
src/gnu/usr.bin/cc/f77. By default, the new f77 will use Sun
Microsystem's Fortran preprocessor (ports/devel/fpp), but it
can be built to use GNU cpp. The new f77 recognizes all f2c and
fpp (or cpp) options that make sense in the context of compilation.
Any option not recognized as a valid f2c or fpp (or cpp) option is
automatically passed to gcc except for gcc options that take
space delimited arguments (these aren't supported, yet).
f77-freebsd.tgz is a gzipped tar file of the port. It should
be placed in ports/lang. When unpacked it will produce a
directory named f77-freebsd. The new f77(1) should be
architecture independent, but I don't have an alpha axp machine
for testing.
NOTE: Do *NOT* try to use the f2c port with the old f77(1) from
src/gnu/usr.bin/cc/f77. The loader can't find the f2c.h header
file or the new library locations.
--
Steve
finger ka...@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
libbind, etc.
Right now we build libbind (so named, etc. can link) but don't install it in /usr/lib. However, there are parts of it that would be very nice to have available to user programs.. in particular the event library (see: nroff -man /usr/src/contrib/bind/lib/isc/eventlib.mdoc ) I would like to make this stuff available somehow as a library in /usr/lib. Would anyone violently object? And what would be the best approach? Since some of libbind is already part of libc, we proabably don't want to install all of libbind .. perhaps we could just install the event library and call it libevent ? Nordic-proof flame suit ready, -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Same module loaded twice?
In the output below, notice there are two modules named ng_sync_sr loaded in the kernel object (due to a typo), and moreover there's a netgraph module loaded in both the kernel object and the netgraph.ko object.. $ kldstat -v Id Refs AddressSize Name 14 0xf010 1be82c kernel Contains modules: Id Name 1 rootbus 2 netgraph 3 ng_sync_sr 4 ng_sync_sr 5 ufs 6 nfs 7 msdos 8 procfs 9 cd9660 10 ipfw 11 if_tun 12 if_sl 13 if_ppp 14 if_loop 15 shell 16 execgzip 17 elf 18 aout 21 0xf07f1000 3000 ng_socket.ko Contains modules: Id Name 20 ng_socket 32 0xf07f5000 4000 netgraph.ko Contains modules: Id Name 19 netgraph Why and how does the linker allow this? It seems like: - When the kernel was compiled, the ng_sync_sr conflict should have caused a failure - When the netgraph.ko was kldloaded, there should have been an error from the conflicting module names Curiously, -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Req: make update target in ports/doc
Hello, Would it be possible to add a make update target to the top Makefile in ports and doc? Similar to the Makefile in /usr/src, so that it does something like cvs -q update -P -d. It would keep the Makefiles more orthogonal, and in any case, make update types easier than cvs -q update -P -d. B-) Kind regards, Ben To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
link_elf: symbol lkmexists undefined
Since building a new kernel and a full 'make world' on Jan 24, I am seeing this at boot: avail memory = 62210048 (60752K bytes) Preloaded elf kernel kernel at 0xf02cc000. Preloaded elf module msdos.ko at 0xf02cc09c. Preloaded elf module procfs.ko at 0xf02cc13c. Preloaded elf module if_tun.ko at 0xf02cc1dc. Preloaded elf module if_disc.ko at 0xf02cc27c. Preloaded elf module linux.ko at 0xf02cc31c. Preloaded elf module vesa.ko at 0xf02cc3bc. Preloaded elf module joy.ko at 0xf02cc458. link_elf: symbol lkmexists undefined Anybody have any idea where this is coming from? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Addition to /etc/rc, maybe
How does this look? --- src/etc/rc.orig Mon Jan 25 17:39:07 1999 +++ src/etc/rc Mon Jan 25 17:43:52 1999 @@ -152,6 +152,16 @@ clean_var fi +# Load the vn module, if enabled. +if [ X$vn_enable = XYES ]; then + echo Loading vn module. + if [ -f /modules/vn.ko ]; then + kldload vn + else + echo Cannot find /modules/vn.ko. + fi +fi + # Add additional swapfile, if configured. if [ x$swapfile != xNO -a -w $swapfile -a -b /dev/vn0b ]; then echo Adding $swapfile as additional swap. --- src/etc/rc.conf.origMon Jan 25 17:36:03 1999 +++ src/etc/rc.conf Mon Jan 25 17:44:14 1999 @@ -12,7 +12,9 @@ ### Important initial Boot-time options # ## +vn_enable=NO # Set to YES if you want the vn kld loaded. swapfile=NO # Set to name of swapfile if aux swapfile desired. + # This needs pseudo-device vn or vn_enable=YES. apm_enable=NO# Set to YES if you want APM enabled. pccard_enable=NO # Set to YES if you want to configure PCCARD devices. pccard_mem=DEFAULT # If pccard_enable=YES, this is card memory address. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: dummynet causes crash?
On Sun, 24 Jan 1999, Luigi Rizzo wrote:
which version of ip_dummynet are you using. There were lately a few
changes to fix a problem related to route entries being freed in the
wrong way.
.(02:36:11)(r...@bright.reserved)
ipfw add pipe 1 ip from server to cvsup.freebsd.org
(long pause i assume DNS)
0 pipe 1 ip from 192.168.2.20 to 198.104.92.71
...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc116
interestingly enough, the above address is 0xdeadbeef + 551 (decimal).
It looks like somehow a wrong route entry was passed to ether_output().
the only thing i can think of is that dummynet doesn't like not being told
if a pipe is 'in' or 'out' :/
nope -- it can detect this by itself. the problem must be elsewhere.
if you have more input on the dummynet version (as per the CVS log)
and os version please let me know.
my ether card is a: ed card, a 'realteck 8029'
... and the network card does not make a difference, dummynet works at
a layer above.
cheers
luigi
{/home/green}$ calc 0xdeadc116 - 0xdeadc0de
56
possibly? IIRC 0xdeadc0de is used to fill freed memory areas in certain cases,
to help detect programming errors related to such.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Heads up! New swapper and VM changes have been committed to -4.x
On 24 Jan 1999, Dag-Erling Smorgrav wrote: Boris Staeblow b...@dva.in-berlin.de writes: Beside your suggestions there are much more programs which use libkvm: /bin/ps/ /libexec/rpc.rstatd/ /sbin/ccdconfig/ /sbin/dmesg/ These are statically linked, and must be relinked after libkvm has been rebuilt. /sbin/dset/ This does not exist anymore. /usr.bin/fstat/ /usr.bin/gcore/ /usr.bin/ipcs/ /usr.bin/netstat/ /usr.bin/nfsstat/ /usr.bin/systat/ /usr.bin/top/ /usr.bin/vmstat/ /usr.bin/w/ /usr.sbin/iostat/ /usr.sbin/kernbb/ /usr.sbin/kgmon/ /usr.sbin/pstat/ /usr.sbin/xntpd/xntpd/ These are dynamically linked, and will automatically pick up the new libkvm. But (most) still require the structures to be the exact same way, which is the reason for the recompile anyway... don't forget that! DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
usb driver broken?
Hi, Am I the only one who gets this when he tries to compile a kernel with the usb drivers in it? cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c ../../dev/usb/uhci.c: In function `uhci_dumpregs': ../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this function) ../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only once ../../dev/usb/uhci.c:406: for each function it appears in.) machine/cpufunc.h:284: warning: inlining failed in call to `inw' ../../dev/usb/uhci.c:406: warning: called from here *** Error code 1 Stop. Alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't mount root. Really need help...
At 06:29 PM 1/25/99 +0100, Leif Neland wrote: On Sun, 24 Jan 1999, Chris Knight wrote: Greetings, I have learned a very valuable lesson. No matter how many time I have made world, I shouldn't do it while I'm tired. Last night I synced my tree and made world. I rebooted, and was going to remake my kernel after the boot. That became an impossibility. Can't you boot kernel.old? Although I have gotten past this, it was not kernel realated. I had made world, but not yet remade my kernel. The problem was in /boot/loader, and I was able to get past it by using /boot/loader.old Thanks for the response though! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
On Sun, 24 Jan 1999, Matthew Dillon wrote: : I haven't cvs updated in 24 hours, if the Acer is newly committed then I'll : have to update again and retry. The CTX is using the Acer. : : ide_pci0: Acer Aladdin IV/V (M5229) Bus-master IDE controller rev 0x20 int a irq 0 on pci0.11.0 : : :It's there...what symptoms are you seeing? Are you overclocking? :-- :++ :| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| No overclocking. Stock CTX box. Could it be the drive, maybe? I only get 2.4 MBytes/sec, same as before. On my PPro box ( Intel PIIX3 Bus-master IDE controller ) it went from around 2.4 MB/sec to 8 MBytes/sec. archive:/cvs# time dd if=/dev/zero of=test2 bs=32k count=1024 1024+0 records in 1024+0 records out 33554432 bytes transferred in 13.700387 secs (2449159 bytes/sec) 0.000u 2.728s 0:13.75 19.7% 357+1405k 5+525io 1pf+0w Hmm, this is strange. I used to be able to get 3MB/s with an old chipset and plain K6, now with ide_pci0: Acer Aladdin IV/V (M5229) Bus-master IDE controller rev 0x20 int a $ wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): Maxtor 71626 AP, DMA, 32-bit, multi-block-32 wd0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): Maxtor 71626 AP, DMA, 32-bit, multi-block-32 wd1: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy wfd0: medium type unknown (no disk) wdc1: unit 1 (atapi): NEC CD-ROM DRIVE:285/3.04, removable, dma, iordy This is strange, because DMA enabled on wd[01] and acd0 doesn't seem to... err work. I say this because I am down to ~2.5MB/s on each hard drive, a MB or so decrease; I also seem to be reading (bs=512k) from the CD uncooked device at the right speed (~2MB/s), but it takes up 40% of the CPU, which seems to be just PIO. Anyone else? -Matt Matthew Dillon dil...@backplane.com ide_pci0: Acer Aladdin IV/V (M5229) Bus-master IDE controller rev 0x20 int a irq 0 on pci0.11.0 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): QUANTUM Bigfoot TX4.0AT, 32-bit, multi-block-16 wd0: 3832MB (7849170 sectors), 8306 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): ATAPI CDROM/V1.70, removable, dma, iordy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote: I say this because I am down to ~2.5MB/s on each hard drive, a MB or so decrease; I also seem to be reading (bs=512k) from the CD uncooked device at the right speed (~2MB/s), but it takes up 40% of the CPU, which seems to be just PIO. Anyone else? Since I rebuilt world shortly after Matt's VM surgery started, I've also noticed this -- lower apparent transfer rates from /dev/zero to disk, higher CPU usage during such transfers. I'm _not_ saying it's Matt's stuff that's done this, it's just that that was the stuff I _noticed_ happening in commit mail. I think I saw something happening to wd.c recently as well, so I _definitely_ am not going on record as laying blame. Just some confirmation. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
:On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote:
:
: I say this because I am down to ~2.5MB/s on each hard drive, a MB or
: so decrease; I also seem to be reading (bs=512k) from the CD uncooked
:...
:
:Since I rebuilt world shortly after Matt's VM surgery started, I've also
:noticed this -- lower apparent transfer rates from /dev/zero to disk,
:higher CPU usage during such transfers.
:
:I'm _not_ saying it's Matt's stuff that's done this, it's just that that
:was the stuff I _noticed_ happening in commit mail. I think I saw
:something happening to wd.c recently as well, so I _definitely_ am not
:going on record as laying blame.
:
:Just some confirmation. :-)
:
:Ciao,
:Sheldon.
Hmm, interesting. A dd copy doesn't touch on the main of what I did,
but I do have a (bad) hack in there to handle a case that John brought
up in regards to the inactive page queue getting overloaded with
clean meta-data. It might be interesting to turn that off and see if
your transfer rates improve.
You can turn off the hack by commenting out the case that activates
it: Add the #if/#endif and split the open brace out from the else,
as shown.
I would like to know if your transfer rate improves or not, and by
how much.
/*
* Figure out what to do with dirty pages when they are encountered.
* Assume that 1/3 of the pages on the inactive list are clean. If
* we think we can reach our target, disable laundering (do not
* clean any dirty pages). If we miss the target we will loop back
* up and do a laundering run.
*/
#if 0
if (cnt.v_inactive_count / 3 page_shortage) {
maxlaunder = 0;
launder_loop = 0;
} else
#endif
{
maxlaunder =
(cnt.v_inactive_target max_page_launder) ?
max_page_launder : cnt.v_inactive_target;
launder_loop = 1;
}
-Matt
Matthew Dillon
dil...@backplane.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
On Mon, 25 Jan 1999, Matthew Dillon wrote:
:On Mon, 25 Jan 1999 19:40:38 EST, Brian Feldman wrote:
:
: I say this because I am down to ~2.5MB/s on each hard drive, a MB or
: so decrease; I also seem to be reading (bs=512k) from the CD uncooked
:...
:
:Since I rebuilt world shortly after Matt's VM surgery started, I've also
:noticed this -- lower apparent transfer rates from /dev/zero to disk,
:higher CPU usage during such transfers.
:
:I'm _not_ saying it's Matt's stuff that's done this, it's just that that
:was the stuff I _noticed_ happening in commit mail. I think I saw
:something happening to wd.c recently as well, so I _definitely_ am not
:going on record as laying blame.
:
:Just some confirmation. :-)
:
:Ciao,
:Sheldon.
Hmm, interesting. A dd copy doesn't touch on the main of what I did,
but I do have a (bad) hack in there to handle a case that John brought
up in regards to the inactive page queue getting overloaded with
clean meta-data. It might be interesting to turn that off and see if
your transfer rates improve.
You can turn off the hack by commenting out the case that activates
it: Add the #if/#endif and split the open brace out from the else,
as shown.
I would like to know if your transfer rate improves or not, and by
how much.
/*
* Figure out what to do with dirty pages when they are encountered.
* Assume that 1/3 of the pages on the inactive list are clean. If
* we think we can reach our target, disable laundering (do not
* clean any dirty pages). If we miss the target we will loop back
* up and do a laundering run.
*/
#if 0
if (cnt.v_inactive_count / 3 page_shortage) {
maxlaunder = 0;
launder_loop = 0;
} else
#endif
{
maxlaunder =
(cnt.v_inactive_target max_page_launder) ?
max_page_launder : cnt.v_inactive_target;
launder_loop = 1;
}
-Matt
Matthew Dillon
dil...@backplane.com
I'd rather use if (0 cnt.v_inactive_count / 3 page_shortage) {. I'm
trying it out now, here's the before:
IOZONE performance measurements:
2972048 bytes/second for writing the file
2962863 bytes/second for reading the file
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
On Mon, 25 Jan 1999, Matthew Dillon wrote: :One variable may be available memory. On my system, with default datasize :limit of 16M from login.conf, Netscape coredumps very frequently. With I've been using netscape on a 24bit color system for well over a year and have never had a serious memory leak problem or X session ( or machine ) crashing due to it. I don't leave the netscape window open all the time, though... I tend to exit out of it when I'm not using it. -Matt Matthew Dillon dil...@backplane.com Just to clarify: 1) I'm not sure I would necesarily accuse Netscape of having a leak: what with caching pages in RAM and the allocation policy of whatever malloc they use, maybe it really needs this much and would stabilise at some size of 100M+ - I just don't have the swap space to find out. 2) I have never seen a system crash as such. However, having the X server killed due to out-of-swap leaves the console fouled up and so could easily be mis-described as a crash. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
: I would like to know if your transfer rate improves or not, and by
: how much.
:
: #if 0
: if (cnt.v_inactive_count / 3 page_shortage) {
: maxlaunder = 0;
: launder_loop = 0;
: } else
: #endif
: {
: -Matt
:
:I'd rather use if (0 cnt.v_inactive_count / 3 page_shortage) {. I'm
:trying it out now, here's the before:
:
:IOZONE performance measurements:
:2972048 bytes/second for writing the file
:2962863 bytes/second for reading the file
: Brian Feldman _ __ ___ ___ ___
Welll... I went ahead and tested it on my diskless workstation,
which actually has a DMA IDE drive connected to it at the moment
for another test I'm running.
I didn't see any change in performance. That doesn't meant that
hasn't been a chance, just that it doesn't look like the one thing
I thought might be causing it is causing it.
Are you sure the problem isn't simply that your disk is getting
a bit more full and causing the test to skip around more ( or move
to more inner tracks, which have lower transfer rates), and
thus appear to slow down a little ?
-Matt
Before ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
7809031 bytes/second for writing the file
10324440 bytes/second for reading the file
IOZONE performance measurements:
8388608 bytes/second for writing the file
10324440 bytes/second for reading the file
After ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
8103711 bytes/second for writing the file
10336864 bytes/second for reading the file
IOZONE performance measurements:
8429768 bytes/second for writing the file
10324440 bytes/second for reading the file
Matthew Dillon
dil...@backplane.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
Aha! That figures. Since I upgraded to CURRENT, with its login.conf which defaults to unlimited resources, my frequent netscape core dumps have gone away. I hadn't realized why until now. Suggestion: wwhen people complain about Netscape, ask them to mail us back the output of ``ulimit -a''. My login.conf has unlimited for everything for myself and netscape still crashes/locks up. And I have 64M/175swap so I dont think its running out of memory. --- E-Mail: Luke l...@aus.org Sent by XFMail -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
PPP (userland) troubles ?
Hi! I'am not sure where this comes from, but at the moment I have some troubles with the userland ppp. The symptoms: After establishing the connection and setting the defaultroute *nothing* works, that means, the line seems to be completely dead. Not even the peer can be pinged. However, after a short while the symptoms vanish and everything is as it should be. I don't believe in faults at my provider, since I tested it with different accounts and basically got the same results. Sometimes when I try to ping the peer, I get some sendto: no buffer space available messages before the reply packets start to drop in. Config: (very)-current, everything ELF, ppp via plain and simple modem dialup. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated.-- From The Gimp manual # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
My setup is about the same. I just modified all my login.conf defaults to be unlimited/infinity. Still the same crappy core dumps. Forrest On Mon, Jan 25, 1999 at 08:47:29PM -0500, Luke wrote: Aha! That figures. Since I upgraded to CURRENT, with its login.conf which defaults to unlimited resources, my frequent netscape core dumps have gone away. I hadn't realized why until now. Suggestion: wwhen people complain about Netscape, ask them to mail us back the output of ``ulimit -a''. My login.conf has unlimited for everything for myself and netscape still crashes/locks up. And I have 64M/175swap so I dont think its running out of memory. --- E-Mail: Luke l...@aus.org Sent by XFMail -- 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: IDE DMA works, I'll be a...
On Mon, 25 Jan 1999, Matthew Dillon wrote:
: I would like to know if your transfer rate improves or not, and by
: how much.
:
: #if 0
: if (cnt.v_inactive_count / 3 page_shortage) {
: maxlaunder = 0;
: launder_loop = 0;
: } else
: #endif
:{
:-Matt
:
:I'd rather use if (0 cnt.v_inactive_count / 3 page_shortage) {. I'm
:trying it out now, here's the before:
:
:IOZONE performance measurements:
:2972048 bytes/second for writing the file
:2962863 bytes/second for reading the file
: Brian Feldman _ __ ___ ___ ___
Welll... I went ahead and tested it on my diskless workstation,
which actually has a DMA IDE drive connected to it at the moment
for another test I'm running.
I didn't see any change in performance. That doesn't meant that
hasn't been a chance, just that it doesn't look like the one thing
I thought might be causing it is causing it.
Are you sure the problem isn't simply that your disk is getting
a bit more full and causing the test to skip around more ( or move
to more inner tracks, which have lower transfer rates), and
thus appear to slow down a little ?
No, this REALLY isn't it. I have tons free on the test drive. iozone 100 on
a 64 mb system:
{/home/green}$ diff iozone.old iozone
15,16c15,16
Writing the 100 Megabyte file, 'iozone.tmp'...37.320312 seconds
Reading the file...37.710938 seconds
---
Writing the 100 Megabyte file, 'iozone.tmp'...37.75 seconds
Reading the file...37.687500 seconds
19,20c19,20
2809665 bytes/second for writing the file
2780562 bytes/second for reading the file
---
2777684 bytes/second for writing the file
2782291 bytes/second for reading the file
-Matt
Before ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
7809031 bytes/second for writing the file
10324440 bytes/second for reading the file
IOZONE performance measurements:
8388608 bytes/second for writing the file
10324440 bytes/second for reading the file
After ( iozone 64 on a 48MB machine )
IOZONE performance measurements:
8103711 bytes/second for writing the file
10336864 bytes/second for reading the file
IOZONE performance measurements:
8429768 bytes/second for writing the file
10324440 bytes/second for reading the file
Matthew Dillon
dil...@backplane.com
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: IDE DMA works, I'll be a...
And here's with Soren's (sorry, I don't have any kind of European keyboard
mapping) patch.
{/home/green}$ diff3 iozone.old iozone iozone.newer
1:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...37.320312 seconds
Reading the file...37.710938 seconds
2:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...37.75 seconds
Reading the file...37.687500 seconds
3:15,16c
Writing the 100 Megabyte file, 'iozone.tmp'...39.187500 seconds
Reading the file...38.820312 seconds
1:19,20c
2809665 bytes/second for writing the file
2780562 bytes/second for reading the file
2:19,20c
2777684 bytes/second for writing the file
2782291 bytes/second for reading the file
3:19,20c
2675792 bytes/second for writing the file
2701101 bytes/second for reading the file
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: usb driver broken?
On Tue, 26 Jan 1999, Alex Le Heux wrote: Am I the only one who gets this when he tries to compile a kernel with the usb drivers in it? Nope. I ran into this same problem, but I haven't had a chance to query the list about it. This is produced by having USB_DEBUG turned on in your kernel config. UHCI_LEGSUP isn't defined anywhere in the usb code. cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c ../../dev/usb/uhci.c: In function `uhci_dumpregs': ../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this function) ../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only once ../../dev/usb/uhci.c:406: for each function it appears in.) machine/cpufunc.h:284: warning: inlining failed in call to `inw' ../../dev/usb/uhci.c:406: warning: called from here *** Error code 1 Stop. -- Christopher Nielsen Scient: The eBusiness Systems Innovator http://www.scient.com cniel...@scient.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
HEADS UP! (kernel thread support)
The Linuxthreads changes in the system that have been optioned out for a while have been enabled after testing by many people. this will require a recompile of at least PS and probably the usual culprits, (libkvm etc) (unless of course you've already been running with the support turned on.) julian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
yo, brian, are you on 'net'? have you had a look at the netgraph stuff? particularly the kernel nodes that we use in conjuntion with mpd, and the usserland modules of mpd that we use with it? Eh, dunno :-/ What's netgraph (it rings bells - have you mentioned it before ?) ? -- Brian br...@awfulhak.org br...@freebsd.org br...@openbsd.org http://www.Awfulhak.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Another heads-up (threads stack support)
This commit also requires a recompile of the usual cuplits. Part of the reason for this commit is to make the thread-stack and non thread stack cases be the same from the point of view of non kernel programs. his allows the 'VM_STACK' option to be turned on and off entirely vi kernel configurations and the userland to be left alone (after this that is) Testers on the ALPHA platform should contact Richard Seaman, Jr. d...@tar.com to help test the alpha version of these changes. If they are ok then this option can be made standard, allowing Pthreads stacks to be dynamic in the same way that linuxthreads are.. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb driver broken?
I had this problem too. It seems that the code included when you define USB_DEBUG has suffered some bitrot. Drop this out of your kernel config, and these compile time errors will go away. louie Hi, Am I the only one who gets this when he tries to compile a kernel with the usb drivers in it? cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/usb/uhci.c ../../dev/usb/uhci.c: In function `uhci_dumpregs': ../../dev/usb/uhci.c:406: `UHCI_LEGSUP' undeclared (first use this function) ../../dev/usb/uhci.c:406: (Each undeclared identifier is reported only once ../../dev/usb/uhci.c:406: for each function it appears in.) machine/cpufunc.h:284: warning: inlining failed in call to `inw' ../../dev/usb/uhci.c:406: warning: called from here *** Error code 1 Stop. Alex 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! (kernel thread support)
At 06:41 PM 1/25/99 -0800, Julian Elischer wrote: The Linuxthreads changes in the system that have been optioned out for a while have been enabled after testing by many people. this will require a recompile of at least PS and probably the usual culprits, (libkvm etc) (unless of course you've already been running with the support turned on.) julian Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ? Thanks Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
I recently looked at keymaps in /usr/share/syscons/keymaps and found many minor errors. In addition to that, there is so much inconsistency among existing keymaps. True that national keyboards have different layout of regular keys (alphanumeric keys and symbol keys). But, it is absurd that functions keys and special keys are handled in so many different ways. [...] But, unless there is a good reason to make other exceptions, I will modify the other national keymaps to adapt these key assignments. Any comments? I am open to suggestions. Kazu Ok, this is my second keymap proposal. Kazu * 101/102/104 Enhanced Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 Alt-SysRq(PrintScreen) - (nop) 92 PrintScreen Switch to the next vty (nscr). 92 Ctrl-PrintScreenEnter DDB (debug). 104 Pause Backscroll (slock). 104 Shift-Pause Start screen saver (saver). 104 Alt-Pause Suspend (susp). 105 Left Windowsfkey62 106 Right Windows fkey63 107 Menufkey64 108 Ctrl-Break(Pause) - (nop) The separate SysRq key doesn't exist on the enhanced keyboard. It is combined with the PrintScreen key. The SysRq code is generated when the Alt and the PrintScreen keys are pressed together. The separate Break key doesn't exist on the enhanced keyboard. It is combined with the Pause key. The Break code is generated when the Ctrl and the Pause keys are pressed together. The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. The base case for the keycode 104 is compatible with existing keymaps. The keycode 108 is new. Many keymaps lacks entries for 105 through 107. * 84 Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 SysRq - (nop) 92 Shift-PrintScreen(*)Switch to the next vty (nscr). 92 Shift-Ctrl-PrintScreen Enter DDB (debug). 104 Ctrl-Pause(NumLock) Backscroll (slock). 104 Shift-Ctrl-Alt-Pause(NumLock) Start screen saver (saver). 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). 108 Ctrl-Break(ScrollLock) - (nop) The separate PrintScreen key doesn't exist on the 84 keyboard. It is combined with the numpad * key. The PrintScreen code is generated when the Shift and the numpad * keys are pressed together. The separate Pause key doesn't exist on the 84 keyboard. It is combined with the NumLock key. The Pause code is generated when the Ctrl and the NumlLock keys are pressed together. The separate Break key doesn't exist on the 84 keyboard. It is combined with the ScrollLock key. The Break code is generated when the Ctrl and the ScrollLock keys are pressed together. * Proposed keymap Combining the support for the 84 keyboard and the enhanced keyboard described above, we will get the following keymap entries. alt ctrlalt alt ctrl code base shift ctrl shift alt shift ctrl shift - 1 esc esc esc esc esc esc debug esc 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' 70 slock slock slock slock slock slock slock slock 84 nop nop nop nop nop nop nop nop 92 nscr nscr debug debug nop nop nop nop 104 slock saver slock saver susp nop susp nop 105 fkey62fkey62fkey62fkey62fkey62fkey62fkey62fkey62 106 fkey63fkey63fkey63fkey63fkey63fkey63fkey63fkey63 107 fkey64fkey64fkey64fkey64fkey64fkey64fkey64fkey64 108 nop nop nop nop nop nop nop nop * Summary of magic key sequences 101 keyboard84 keyboard function Ctrl-Alt-Delete Ctrl-Alt-Delete reboot Ctrl-Alt-EscCtrl-Alt-Escdebug Ctrl-Alt-Space Ctrl-Alt-Space susp ScrollLock ScrollLock slock PrintScreen Shift-(Numpad *)/PrintScreennscr Ctrl-PrintScreenShift-Ctrl-(Numpad *)/PrintScreen debug Alt-PrintScreen/SysRq SysRq
Re: HEADS UP! (kernel thread support)
yes On Mon, 25 Jan 1999, Manfred Antar wrote: At 06:41 PM 1/25/99 -0800, Julian Elischer wrote: The Linuxthreads changes in the system that have been optioned out for a while have been enabled after testing by many people. this will require a recompile of at least PS and probably the usual culprits, (libkvm etc) (unless of course you've already been running with the support turned on.) julian Does this mean I can take -DCOMPAT_LINUX_THREADS out of /etc/make.conf ? Thanks Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
Brian Somers writes: yo, brian, are you on 'net'? have you had a look at the netgraph stuff? particularly the kernel nodes that we use in conjuntion with mpd, and the usserland modules of mpd that we use with it? Eh, dunno :-/ What's netgraph (it rings bells - have you mentioned it before ?) ? It was announced on freebsd-net .. beta version. Check out the blurb on our new improved web site! :-) ftp://ftp.whistle.com/pub/archie/netgraph/index.html -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
Maxim Sobolev writes: Can you point all people (and me of course) who want to test DEVFS to some common information about DEVFS (usage, possible advantages/disadvantages etc. I think some FAQ or so will be nice. It's really will help us to go further with this issue. I agree.. and I've bugged Julian to put something together... Basically, there are a few things that need to be done to get DEVFS into the 'mainstream'... and this includes SLICE. The only thing that DEVFS doesn't completely work for right now is disks, because the way disks are handled right now is all a bunch of hardwired stuff. SLICE is intended to fix this problem, and in the process make easy things like a compressed encrypted filesystem striped across a 10 disk array.. :-) So the things to do are: 1. Finish DEVFS-enabling the SCSI da disk driver. 2. Implement asynchronous device management in DEVFS (kernel thread) This solves the problem of doing lengthy I/O during interrupts. 3. Fix the MFS problem -- hopefully Matt Dillon can help here in the course of his ongoing cleanups bug fixes. 4. Completely rewrite libdisk to use and understand SLICE. (This might actually be a kharmically refreshing experience). 5. Update the installer code to work with the new libdisk OR write a compatibility layer that implements the old libdisk API on top of the new libdisk. 6. No change to fdisk(8); minor change to disklabel(8). I'm willing to take a look at the libdisk issue.. in which case a few helpful pointers from anyone who knows would be nice: - What other code beside the installer (if any) uses libdisk? - What are the relevant installer files in the source tree? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
- What other code beside the installer (if any) uses libdisk? Nothing does. That probably says something in and of itself. :) - What are the relevant installer files in the source tree? /usr/src/release/sysinstall. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: beginnings of a diskless boot sequence being committed
Luigi Rizzo writes: :I haven't seen how you suggest to buildpopulate the MFS filesystems -- ... There isn't much to build. Most of the MFS filesystems start out empty. ok here we use a different approach. For simplicity I am using a single MFS system with all the things you put in /var, and including /var/dev and /var/etc (with /dev - /var/dev and /etc - /var/etc on the diskless machine). I have a wacky idea in this vein that I want to pursue sometime -- instead of pushing off lots of symlinks for the various writable portions of the read-only root directory (which strikes as a bit odd in itself), I was considering union-mounting an MFS filesystem directly over the read-only root partition. The advantage of this approach is that you do not have to know ahead of time what portions of the read-only partition need to be writable -- files get copied into the MFS partition only if and when they are written to. Thoughts? It seems like it would be feasible, and it might even be possible to do it directly in /etc/fstab without having to put any sort of cleverness in /etc/rc. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
Вы писали: Nate Williams writes: I am current as of today 4.0, I have communicator 4.5 downloaded some time ago (November more or less) directly from netscape and installed in /usr/local/netscape with a link to /usr/local/bin/netscape and I have been using it all day with no problems. My intranet if full of java and haven't had a problem, knock on wood:-) I just downloaded a 9M file after reading your mail to see if that would cause a problem and it didn't. Netscape is as stable as ever on FreeBSD Current 4.0 for me. That bothers me:-) I wonder why? I'm running 2.2-stable, so maybe that's a difference. Me too... (I get crashes running Java) And me too.. Now netscape(with java too...) works for me, but after disabling splash... I can not understand it... I cvsupedrebuilded system at 25-jan-1999.. -- Best wishes, Eugeny http://coredumped.null.ru coredum...@coredumped.null.ru ICQ#: 5885106 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
On 26-Jan-99 Andrew Gordon wrote: On Mon, 25 Jan 1999, Matthew Dillon wrote: :One variable may be available memory. On my system, with default :datasize :limit of 16M from login.conf, Netscape coredumps very frequently. With I've been using netscape on a 24bit color system for well over a year and have never had a serious memory leak problem or X session ( or machine ) crashing due to it. I don't leave the netscape window open all the time, though... I tend to exit out of it when I'm not using it. This would indicate that it might have to do then with prolonged exposure to memory and the memory-system(s) (swap, paging). Is there anyway to monitor the syscalls and the amount of memory used and released by each call Matt? Hope ye see where I'm getting at... 1) I'm not sure I would necesarily accuse Netscape of having a leak: what with caching pages in RAM and the allocation policy of whatever malloc they use, maybe it really needs this much and would stabilise at some size of 100M+ - I just don't have the swap space to find out. Yer kidding right? A program that _needs_ 100 MB or more? Surely yer kidding... I haven't seen a program in normal corporate/home use that justifies the memory usage of 100 MB or more including NetScape's Navigator/Communicator. 2) I have never seen a system crash as such. However, having the X server killed due to out-of-swap leaves the console fouled up and so could easily be mis-described as a crash. I wonder if X could be the originator of the problems, my guess is it can't since Linux uses the same X and I haven't heard any complaints from that corner. Also it's nice that the program dumps core, but afaik without debug symbols it's not much use. --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist http://home.wxs.nl/~asmodai BSD picoBSD: The Power to Serve http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
cvsup build failure
4.0-current as of today. i am trying to make cvsup and blooie! new source - compiling ../src/TreeComp.m3 new source - compiling ../src/FSServer.m3 new source - compiling ../src/FSServerU.m3 new source - compiling ../src/Main.m3 - linking cvsupd /usr/lib/aout/crt0.o: file not recognized: File format not recognized is it to do with having NOAOUT in /etc/make.conf? randy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-Current, netscape halts system
I have been having these X lockups with the linux netscape 4.5 running. I may have exacerbated it when I installed the linux realplayer and macromedia flash plugins. I would like to have a methodology to help debug this, but I have just this one system to use as the debug system. I do also have a vt220 which I could set up if that would help. The key here is that for me it locks the system up completely. I cannot telnet in remotely and the ctrl-alt-esc key sequence does not work so its unclear to me how to debug this. Tell me what I would need to help debug it, and I will try to be of some help. Ill attach my dmesg output. -Reggie Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Jan 17 09:52:17 PST 1999 r...@trane.lambdawerks.org:/usr/src/sys/compile/TRANE Timecounter i8254 frequency 1193182 Hz CPU: Pentium/P55C (586-class CPU) Origin = GenuineIntel Id = 0x543 Stepping=3 Features=0x8003bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,MMX real memory = 134217728 (131072K bytes) config pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 config pnp 1 1 os disable config pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 config pnp 1 3 os disable config quit avail memory = 127401984 (124416K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xf02f3000. Preloaded userconfig_script /kernel.config at 0xf02f309c. Probing for devices on PCI bus 0: chip0: Intel 82439 rev 0x03 on pci0.0.0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 vga0: Matrox MGA 2164W graphics accelerator rev 0x00 int a irq 18 on pci0.18.0 bt0: Buslogic Multi-Master SCSI Host Adapter rev 0x08 int a irq 17 on pci0.19.0 bt0: BT-958 FW Rev. 5.06I Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs fxp0: Intel EtherExpress Pro 10/100B Ethernet rev 0x02 int a irq 16 on pci0.20.0 fxp0: Ethernet address 00:a0:c9:90:bb:52 Probing for PnP devices: CSN 1 Vendor ID: CTL009e [0x9e008c0e] Serial 0x0d9191f1 Comp ID: PNPb02f [0x2fb0d041] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model GlidePoint, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 bt: unit number (1) too high bt1 not found at 0x330 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: SoundBlaster 16 4.16 sbxvi0 at drq 5 on isa snd0: SoundBlaster 16 4.16 sbmidi0 at 0x330 on isa snd0: SoundBlaster MPU-401 opl0 at 0x388 on isa snd0: Yamaha OPL3 FM awe0 at 0x620 on isa awe0: SoundBlaster EMU8000 MIDI (RAM4096k) Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at bt0 bus 0 target 5 lun 0 sa0: HP C1533A 9608 Removable Sequential Access SCSI-2 device sa0: 10.0MB/s transfers (10.0MHz, offset 8) da0 at bt0 bus 0 target 0 lun 0 da0: IBM DCAS-34330W !# S65A Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at bt0 bus 0 target 4 lun 0 da1: IBM DCAS-34330W !# S65A Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) changing root device to da0s1a WARNING: / was not properly dismounted vinum: loaded cd0 at bt0 bus 0 target 1 lun 0 cd0: TOSHIBA CD-ROM XM-5701TA 0167 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [296322 x 2048 byte records] ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Asmodai == Asmodai Jeroen writes: On 26-Jan-99 Andrew Gordon wrote: On Mon, 25 Jan 1999, Matthew Dillon wrote: :One variable may be
