STARTUP ARCH. (was Re: swap_pager_swap_init())
John Baldwin wrote: The swap pager getpages/putpages routines depend on swap_pager_swap_init() being called before they are called. However, swap_pager_swap_init() isn't called until the pagedaemon starts up. Granted, it should always be run before init has a chance to exec swapon via /etc/rc, however, would it be more correct to instead let swap_pager_swap_init() be run by a SI_SUB_VM SYSINIT (SI_ORDER_ANY, with the other VM sysinit's bumped up to be less than ANY). The race is incredibly small, but I'd feel better if it was more correct. Comments? This heavy a change probably belongs on -arch; I will tell you what I think, and why, and let consensus sort it out. I don't think there is a race; the stuff is not really started until the scheduler is run, and that is the last thing; before that, it is merely on a run queue. A serious monkey-wrench in your plan is that the proc structure for the thing is allocated out of a zone, and the VM system is not really up at that point, sp doing it that early is not really an option. My gut tells me that it should actually _at least_ be after the SI_SUB_MBUF has started. You can _probably get away with as early as after the SI_SUB_VM_CONF has occurred (notice how this happens well after the SI_SUB_VM). But earlier is worse. Basically, the VM system comes up in stages: o load the loader o make real mem look like 16M o load the kernel o statically allocate some pages and page tables o build a VM that looks just like real memory o use a stack trampoline to enter into the virtualized version of the kernel address space at the relocation address o cpu_startup --- everything above this line needs a serious cleanup pass --- o Start running init_main.c (the stuff you are poking into right now) o Get the tunables from the loader o Start the console o Print the first thing we ever print to say we are on our way to being alive o Allocate some more stuff semi-statically by grabbing physical memory via VALLOC() o Create some page tables that can be used by the VM system to refer to the allocations that have already taken place o Remap the kernel into a single 4G page, if the CPU supports it, with the global bit, if the CPU supports it, to avoid CR3 reload shootdowns o Start the VM system, which startups up malloc() and friends --- Now you have a VM system that can't swap, but can fault to get pages from unallocated physical memory --- The problem is that the machdep.c code needs to have executed, as well as the pmap.c code, before you start trying to do zone allocations, and the VM system needs to be there and capable of fault handling for grow_kernel() (page table allocations to grow the KVA that wasn't preallocated) before you can do malloc's. This should probably be documented somewhere _AFTER_ it is cleaned up to get rid of magic incantations, like NKPDE, KPTDI, MPPTDI, APTPTDI, PTDPTDI, UMAXPTDI, and UMAXPTEOFF; I could document it all now (I spent two weeks running a backup tape through my dental fillings over it, and I'm the original author of the SYSINT() code), but it would show everyone the skid marks on our underwear. Maybe Kirk's new book will cover it, or maybe it wants another book on top of that one. This is heavy /* You are not expected to understand this.*/ territory... I haven't really looked at whether it tries to do an allocation immediately, or if it just sits there like a lump until first reference. If it's not using zinit(), with the interrupt flag, it's probably not safe that early; if it's not, please don't change it, since it will eat KVA space and potentially not use it after the change, when it didn't before (only if it's not). The reason I say don't change this, even if it's not a problem (e.g. it sits like a lump), is that you will still end up limiting what's permissable later. Generally, the order of operations is the way that it is not because it was arbitrarily decreed thus, but to permit the most flexibility for implementation for the people who follow, and are unlucky enough to not have metal dental fillings. I suspect that for the IA64 and Alpha support at e.g. 512G of physical RAM, we are going to want to dynamically allocate swap_pager_object_list, instead of using a static allocation, and moving it up too far from where it is would break that (bigtime). My personal preference is, to quote Buckaroo Banzai, Hey, hey... don't pull on that: you never know what those things are attached to, that far inside the brain when it comes to startup ordering, since some of it works because I built an initial dependency graph before SYSINIT went in, and some of it works because nothing anyone has done since then and committed has intermittently broken the dependency graph (if they broke it, they were lucky and it wasn't intermittent, so their system
New web utility
Title: I noticed your email address on a list serve related to technology and web development. With your permission, wewould like to send you information regarding new web tools and utilities based on your interests. Please click thefollowing link and opt-in to our product updates and e-newsletter, click here: http://216.133.228.90/Cordially,Victor BlackHigh-Tech-Communications.com If you would like to be removed from our database, please click here: http://216.133.228.90/remove.cgi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More ATA disks with tagged queueing ?
It seems [EMAIL PROTECTED] wrote: After applaying the next patch I can now see in dmesg output: ad4: 19574MB IBM-DPTA-372050 [39770/16/63] at ata2-master tagged UDMA66 ad6: 19623MB IC35L020AVER07-0 [39870/16/63] at ata3-master tagged UDMA66 . This configuration (ad6 is the IBM's Deskstar 60GXP(?) series disk) was 'tested' by the 'make -j32 buildworld' with the /usr/obj on the ad6 disk. Does this mean that this disk really support tagged queueing ? Yups, else it would have failed bitterly.. The diskid (IC...) has me somewhat stumped though, I would have thougt the used something like all other IBM disks. Is this a genuine IBM disk or is it some kind of OEM/rebadged device ? Is there any way to test/demonstarte this ? Not without instrumenting the code currently -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problems with ata probing twice.
matusita I have similar problem; 'ata' bus is detected twice. I've just updated to 5-current as of yesterday (yeh!), but no helps. 'ata' driver detects the second devices which is _not_ on this machine. Attached below is a full and verbose dmesg output. Most part of kernel configulation is as same as GENERIC, only some unused devices and options are wiped out. Note again that this machine worked well with 4-stable kernel. What's wrong with me? or something goes wrong in 5-current kernel? -- - Makoto `MAR' MATSUSHITA Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Thu Jun 21 14:19:43 JST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNAPSHOTS_CURRENT Calibrating clock(s) ... TSC clock: 501112757 Hz, i8254 clock: 1193126 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 501138091 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 268435456 (262144K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x00395000 - 0x0fff7fff, 264646656 bytes (64611 pages) avail memory = 257662976 (251624K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fad10 bios32: Entry = 0xfb180 (c00fb180) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb1b0 pnpbios: Found PnP BIOS data at 0xc00fbdd0 pnpbios: Entry = f:be00 Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel kernel at 0xc036f000. random: entropy source null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fdd40 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base d200, size 22, enabled found- vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 found- vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 found- vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base f000, size 4, enabled found- vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 map[20]: type 4, range 32, base e000, size 5, enabled found- vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=12 map[90]: type 4, range 32, base 5000, size 4, enabled found- vendor=0x8086, dev=0x7113, revid=0x02 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 map[10]: type 1, range 32, base d244, size 12, enabled map[14]: type 4, range 32, base e400, size 6, enabled map[18]: type 1, range 32, base d242, size 17, enabled found- vendor=0x8086, dev=0x1229, revid=0x09 bus=0, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=15 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d2441000, size 12, enabled map[14]: type 4, range 32, base e800, size 6, enabled map[18]: type 1, range 32, base d240, size 17, enabled found- vendor=0x8086, dev=0x1229, revid=0x09 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d100, size 24, enabled found- vendor=0x102c, dev=0x00c0, revid=0x64 bus=0, slot=11, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode0xf000-0xfff pcib1: memory decode 0xfff0-0xf pcib1: prefetched decode 0xfff0-0xf pci1: physical bus=1 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 ostat0=50 ostat2=00 ata0-slave: ATAPI probe 00 00 ata0-master: ATAPI probe 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA probe 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 ata1: at 0x170 irq 15 on atapci0
Re: More ATA disks with tagged queueing ?
Hi, Am Do , dem 21. Jun 2001, um 9:10 +0200 Uhr schrubte Søren Schmidt zum Thema [Re: More ATA disks with tagged queueing ?]: Yups, else it would have failed bitterly.. The diskid (IC...) has me somewhat stumped though, I would have thougt the used something like all other IBM disks. Is this a genuine IBM disk or is it some kind of OEM/rebadged device ? It is the new way IBM names the disk products. Take a look: http://www.storage.ibm.com/techsup/hddtech/modnum.htm Riggs -- - Die Welt schläft tief schon lange Zeit | Sent with RiggiSmooth [tm] - -- Mich nur flieht die Dunkelheit| - -- --- Denn per Infrarot seh ich| just to fit your --- Die Nacht ist wirklich widerlich. | primitive screen. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More ATA disks with tagged queueing ?
On Thu, Jun 21, 2001 at 09:10:33AM +0200, Søren Schmidt wrote: It seems [EMAIL PROTECTED] wrote: After applaying the next patch I can now see in dmesg output: ad4: 19574MB IBM-DPTA-372050 [39770/16/63] at ata2-master tagged UDMA66 ad6: 19623MB IC35L020AVER07-0 [39870/16/63] at ata3-master tagged UDMA66 . This configuration (ad6 is the IBM's Deskstar 60GXP(?) series disk) was 'tested' by the 'make -j32 buildworld' with the /usr/obj on the ad6 disk. Does this mean that this disk really support tagged queueing ? Yups, else it would have failed bitterly.. The diskid (IC...) has me somewhat stumped though, I would have thougt the used something like all other IBM disks. Is this a genuine IBM disk or is it some kind of OEM/rebadged device ? Yes, this IS genuine IBM disk. See: http://www.storage.ibm.com/hardsoft/diskdrdl/desk/ds60gxp.htm So I'll continue to use patched 'sys/dev/ata/ata-disk.c' and hope this will work ;-) N.Dudorov Is there any way to test/demonstarte this ? Not without instrumenting the code currently -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More ATA disks with tagged queueing ?
It seems Nickolay N. Dudorov wrote: The diskid (IC...) has me somewhat stumped though, I would have thougt the used something like all other IBM disks. Is this a genuine IBM disk or is it some kind of OEM/rebadged device ? Yes, this IS genuine IBM disk. See: http://www.storage.ibm.com/hardsoft/diskdrdl/desk/ds60gxp.htm So I'll continue to use patched 'sys/dev/ata/ata-disk.c' and hope this will work ;-) :) well could you try this patch instead, that should work with all future IBM ATA disks (as long a they stick to this scheme that is, and still support tags) Index: ata-disk.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.108 diff -u -r1.108 ata-disk.c --- ata-disk.c 2001/06/08 05:24:13 1.108 +++ ata-disk.c 2001/06/21 07:43:55 @@ -856,6 +856,14 @@ return 1; i++; } + /* +* check IBM's new obscure way of naming drives +* we want IC (IBM CORP) and AV (ATA interface) +* but doesn't care about the other crap (size, capacity etc) +*/ + if (!strncmp(AD_PARAM-model, IC, 2) + !strncmp(AD_PARAM-model + 8, AV, 2) ) + return 1; } return 0; } -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversal
tacho lock order reversal tacho 1st 0xc03f0140 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007 tacho 2nd 0xcaec972c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016 Exactly the same kernel message was here. Revision ID is: galtvalion % grep FreeBSD: src/sys/ufs/ffs/ffs_vnops.c ffs_vnops.c: * $FreeBSD: src/sys/ufs/ffs/ffs_vnops.c,v 1.79 2001/05/01 08:34:44 phk Exp $ It's 5-current CVSuped a few days ago. There are two UFS filesystems in this note PC, and one of them employs softupdate. galtvalion % mount -t ufs /dev/ad0s1a on / (ufs, local, noatime) /dev/ad0s1e on /pub (ufs, local, noatime, soft-updates) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More ATA disks with tagged queueing ?
On Thu, Jun 21, 2001 at 09:46:43AM +0200, Søren Schmidt wrote: It seems Nickolay N. Dudorov wrote: The diskid (IC...) has me somewhat stumped though, I would have thougt the used something like all other IBM disks. Is this a genuine IBM disk or is it some kind of OEM/rebadged device ? Yes, this IS genuine IBM disk. See: http://www.storage.ibm.com/hardsoft/diskdrdl/desk/ds60gxp.htm So I'll continue to use patched 'sys/dev/ata/ata-disk.c' and hope this will work ;-) :) well could you try this patch instead, that should work with all future IBM ATA disks (as long a they stick to this scheme that is, and still support tags) Yes this patch (obviously) work. And what about new (or future) Travelstar models with the names of the IC25T048ATDA05 sort ? (No, I have no such disks :-) N.Dudorov Index: ata-disk.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.108 diff -u -r1.108 ata-disk.c --- ata-disk.c2001/06/08 05:24:13 1.108 +++ ata-disk.c2001/06/21 07:43:55 @@ -856,6 +856,14 @@ return 1; i++; } + /* + * check IBM's new obscure way of naming drives + * we want IC (IBM CORP) and AV (ATA interface) + * but doesn't care about the other crap (size, capacity etc) + */ + if (!strncmp(AD_PARAM-model, IC, 2) + !strncmp(AD_PARAM-model + 8, AV, 2) ) + return 1; } return 0; } -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CPUTYPE warning
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: June 5th doesn't work (dumps core when it gets to crt1.c). Today's won't build anything at all. I think I've found the problem - what doesn't work is: - building crt1.c with -fno-builtin - building anything with gcc compiled with -fno-builtin The source dates probably aren't relevant, June 5th is simply the oldest -CURRENT I've tried to run with -fno-builtin in CFLAGS. I've now gone back to adding it to CFLAGS only when WARNS is 1 or higher. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! S/Key is ancient, OPIE is new
Mark Murray [EMAIL PROTECTED] writes: I want to remove S/Key from CURRENT completely, and replace it with OPIE where necessary. How will this affect OpenSSH's SKeyAuthentication option, which is required for certain types of token-based authentication (like CryptoCard)? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -fno-builtin warning (was: CPUTYPE warning)
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: I think I've found the problem - what doesn't work is: - building crt1.c with -fno-builtin - building anything with gcc compiled with -fno-builtin Ah, no, I understand now: crt1 is the first item to be built in the libraries stage of buildworld, i.e. the first item to be built with the cross-tools, which were built with -fno-builtin, so the problem seems quite simple: gcc built with -fno-builtin suffers an internal error and a core dump if you try to compile anything with it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
picobsd and mdconfig
vnconfig has changed to mdconfig in -current, but the
picobsd build script still references vnconfig, also
CONFIG isn't defined anywhere in the script, resulting
in the process dying when it tries to configure the
kernel, a couple of punctuation mods here and there,
and dumped the vnode is... log.
Index: picobsd
===
RCS file: /home/ncvs/src/release/picobsd/build/picobsd,v
retrieving revision 1.7
diff -r1.7 picobsd
3c3
# $FreeBSD: src/release/picobsd/build/picobsd,v 1.7 2001/06/21 08:49:46 luigi Exp $
---
# $FreeBSD$
80,85d79
NO_DEVFS=yes # DEVFS is currently broken. Always set this.
# Find a suitable vnode
VNUM=`mount | awk /vn/ { num++ } END { printf \%d\, num }`
log --- Using vn${VNUM}...
161d154
echo - vnode is $VNUM
329c322
dd if=${BUILDDIR}/picobsd.bin of=/dev/rfd0.${FLOPPY_SIZE}
---
dd if=${BUILDDIR}/picobsd.bin of=/dev/fd0
427c420
gzip -9 etc/*
---
for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
436,437d428
free_vnode
448c439
disklabel -rw vn${VNUM} fd${MFS_SIZE} || fail $? mfs_disklabel
---
disklabel -rw md${VNUM} fd${MFS_SIZE} || fail $? mfs_disklabel
450c441
disklabel -rw vn${VNUM} auto || fail $? mfs_disklabel
---
disklabel -rw md${VNUM} auto || fail $? mfs_disklabel
452,454c443,445
newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn${VNUM}c /dev/null
mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
log `df /dev/vn${VNUM}c`
---
newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
mount /dev/md${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
log `df /dev/md${VNUM}c`
528c519
cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
---
cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
533,534c524,525
fsck -p /dev/rvn${VNUM}c
vnconfig -u vn${VNUM}
---
fsck -p /dev/md${VNUM}c
vnconfig -u md${VNUM}
540,541c531,532
umount /dev/vn${VNUM} 2 /dev/null || true
vnconfig -u vn${VNUM} 2 /dev/null || true
---
umount /dev/md${VNUM} 2 /dev/null || true
mdconfig -d -u ${VNUM} 2 /dev/null || true
557,559c548,550
no_vnconfig)
echo Error while doing vnconfig of ${imgname} on /dev/rvn${VNUM}...
echoMost probably your running kernel doesn't have the vn(4) device.
---
no_mdconfig)
echo Error while doing mdconfig of ${imgname} on /dev/md${VNUM}...
echoMost probably your running kernel doesn't have the md(4) device.
562c553
echo Error while labeling ${MFS_NAME} size ${MFS_SIZE}
---
echo Error while labeling ${MFS_NAME} size ${MFS_SIZE}.
565c556
echo Error while mounting ${MFS_NAME} (/dev/vn${VNUM}c) on ${MFS_MOUNTPOINT}
---
echo Error while mounting ${MFS_NAME} (/dev/md${VNUM}c) on ${MFS_MOUNTPOINT}.
568c559
echo Error while making hierarchy in ${MFS_MOUNTPOINT}
---
echo Error while making hierarchy in ${MFS_MOUNTPOINT}.
574c565
echo Error while doing disklabel on of floppy.img size $FLOPPY_SIZE
---
echo Error while doing disklabel on of floppy.img size $FLOPPY_SIZE.
577c568,576
echo Error: you must build PICOBSD${suffix} kernel first
---
echo Error: you must build PICOBSD${suffix} kernel first.
;;
ftree_copy)
echo Error while copying floppy tree to ${MFS_MOUNTPOINT}.
echoPerhaps ${MFS_MOUNTPOINT} is out of space.
;;
kernel_copy)
echo Error while copying PICOBSD${suffix}/kernel to ${MFS_MOUNTPOINT}.
echoPerhaps ${MFS_MOUNTPOINT} is out of space.
594c593
# Create a zero-filled disk image with a boot sector, and vnconfig it.
---
# Create a zero-filled disk image with a boot sector, and mdconfig it.
602c601,602
vnconfig -c -s labels vn${VNUM} ${imgname} || fail $? no_vnconfig
---
VNODE=`mdconfig -a -t vnode -s ${imgsize}k -f ${imgname}` || fail $? no_mdconfig
VNUM=`echo ${VNODE} | sed 's/^md//'`
622c622
disklabel -Brw -b ${boot1} -s ${b2} vn${VNUM} fd${FLOPPY_SIZE} || \
---
disklabel -Brw -b ${boot1} -s ${b2} md${VNUM} fd${FLOPPY_SIZE} || \
625c625
newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/vn${VNUM}c /dev/null
---
newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
627c627
mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT}
---
mount /dev/md${VNUM}c ${MFS_MOUNTPOINT}
636c636,639
cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel
---
du -k kernel.gz
df -k ${MFS_MOUNTPOINT}
cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
714a718,723
# Ugh.
if [ ! $CONFIG ]; then
CONFIG=config
fi
717,719c726,730
THETYPE=$1
SITE=$2
set_type $THETYPE
---
# First, check if arguments where passed to us before parsing.
if [ $2 ]; then
THETYPE=$1
SITE=$2
set_type $THETYPE
721c732
# If $1=package, it creates a neat set of floppies
---
# If
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled: | vnconfig has changed to mdconfig in -current, but the | picobsd build script still references vnconfig, also | CONFIG isn't defined anywhere in the script, resulting | in the process dying when it tries to configure the | kernel, a couple of punctuation mods here and there, | and dumped the vnode is... log. Hi Omachonu, Do you mind posting a URL with the above patch in unified form? (i.e. diff -u) Thanks, Michael -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: support Pentium3 SSE
On Wed, Jun 20, 2001 at 05:39:55PM -0400, Andrew Gallatin wrote: While we're at it, I know that the AMD AthlonMP supports SSE, but I can't seem to find which bits they're using in their features for it. It would be nice if somebody who knew that spoke up so that we supported SSE on Palamino right off the bat.. Is this page any good to you: http://www.sandpile.org/ia32/cpuid.htm Otherwise, maybe we can ask someone in AMD. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote: On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled: | vnconfig has changed to mdconfig in -current, but the | picobsd build script still references vnconfig, also | CONFIG isn't defined anywhere in the script, resulting | in the process dying when it tries to configure the | kernel, a couple of punctuation mods here and there, | and dumped the vnode is... log. Hi Omachonu, Do you mind posting a URL with the above patch in unified form? (i.e. diff -u) http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch Thanks, Michael -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Omachonu Ogali [EMAIL PROTECTED] http://www.informationwave.net To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 11:02:02AM -0400, Omachonu Ogali scribbled:
| On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
| On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| | vnconfig has changed to mdconfig in -current, but the
| | picobsd build script still references vnconfig, also
| | CONFIG isn't defined anywhere in the script, resulting
| | in the process dying when it tries to configure the
| | kernel, a couple of punctuation mods here and there,
| | and dumped the vnode is... log.
|
| Hi Omachonu,
|
| Do you mind posting a URL with the above patch
| in unified form? (i.e. diff -u)
|
|
|http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch
Attached is my questions about this.
The rest of it looks great. We shouldn't have any problem
with this patch at all. I will test this tonight or at USENIX.
--
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+
| --- src/release/picobsd/build/picobsd.origThu Jun 21 04:49:46 2001
| +++ src/release/picobsd/build/picobsd Thu Jun 21 10:08:00 2001
| @@ -2,3 +2,3 @@
| -gzip -9 etc/*
| +for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
| log --- Compressed files in etc/
Good idea!
| +newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
| +mount /dev/md${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
| +log `df /dev/md${VNUM}c`
| }
| @@ -527,3 +518,3 @@
| log --- Copy generic floppy_tree into MFS...
| - cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
| + cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
| +
| +du -k kernel.gz
| +df -k ${MFS_MOUNTPOINT}
| +cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
Why do you call du and df?
Re: support Pentium3 SSE
On Thu, Jun 21, 2001 at 04:07:25PM +0100, David Malone scribbled: | On Wed, Jun 20, 2001 at 05:39:55PM -0400, Andrew Gallatin wrote: | While we're at it, I know that the AMD AthlonMP supports SSE, but I I think we already detect AthlonMP's SSE automatically. I recall reading Peter's dmesg of his Tyan board and seeing SSE in the config. | can't seem to find which bits they're using in their features for it. | It would be nice if somebody who knew that spoke up so that we | supported SSE on Palamino right off the bat.. | Is this page any good to you: | http://www.sandpile.org/ia32/cpuid.htm | Otherwise, maybe we can ask someone in AMD. If only we had libraries that did SSE/3DNOW -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:17:52AM -0500, Michael C . Wu wrote:
On Thu, Jun 21, 2001 at 11:02:02AM -0400, Omachonu Ogali scribbled:
| On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
| On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| | vnconfig has changed to mdconfig in -current, but the
| | picobsd build script still references vnconfig, also
| | CONFIG isn't defined anywhere in the script, resulting
| | in the process dying when it tries to configure the
| | kernel, a couple of punctuation mods here and there,
| | and dumped the vnode is... log.
|
| Hi Omachonu,
|
| Do you mind posting a URL with the above patch
| in unified form? (i.e. diff -u)
|
|
http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch
Attached is my questions about this.
The rest of it looks great. We shouldn't have any problem
with this patch at all. I will test this tonight or at USENIX.
--
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+
| --- src/release/picobsd/build/picobsd.orig Thu Jun 21 04:49:46 2001
| +++ src/release/picobsd/build/picobsd Thu Jun 21 10:08:00 2001
| @@ -2,3 +2,3 @@
| -gzip -9 etc/*
| +for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
| log --- Compressed files in etc/
Good idea!
| +newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
| +mount /dev/md${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
| +log `df /dev/md${VNUM}c`
| }
| @@ -527,3 +518,3 @@
| log --- Copy generic floppy_tree into MFS...
| - cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
| + cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
| +
| +du -k kernel.gz
| +df -k ${MFS_MOUNTPOINT}
| +cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
Why do you call du and df?
That can be removed, that was just for debugging sake, I wanted to see
how big the image is, and how much free space I had available on the
floppy, so I could say, 'the image overshoots the floppy by NNN kB'
and then work on the space problem from there...
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
PCM sound problems in -current ??
I'm having problems with both an internal VIA'686 and a PCI base ESS Solo1, both seem to loose interrupts. The interrupts doesn't even show up in a vmstat -i / systat so something is definitly wrong. BTW the exact same HW work just fine with -stable ? Cameron ? anyone ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: orm driver itches (vga1, sc1, pca[12], isic1)?
On 20 Jun, Warner Losh wrote: However, it is related to having both a hints line in your config file and a /boot/device.hints file. fdc1 is the giveaway here. Bug or feature? I like to have the hints compiled in (just in case /boot/device.hints disappears for whatever reason) and to have it in /boot/device.hints to be able to modify them whitout recompiling the kernel. Bye, Alexander. -- Secret hacker rule #11: hackers read manuals. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: broken world (kerberos5/lib/libasn1)
Date: Fri, 22 Jun 2001 01:00:53 +0900 From: Jun Kuriyama [EMAIL PROTECTED] Today's nightly build reports breakage of the world... /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/lex.l:65: `SEQUENCE' undeclared (first use in this function) /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/lex.l:66: `OF' undeclared (first use in this function) ... Stop in /usr/src/kerberos5/lib/libasn1. You may well have obtained your updates at an inopportune time: I'm still building today's -CURRENT, but have got beyond the buildworld (with no incident), and am in the process of building the new kernel. My CVSup was between 03:47 - 03:52 this morning, PDT (GMT-0700), from cvsup14. Cheers, david (of course, I haven't tried to *boot* it yet) -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: broken world (kerberos5/lib/libasn1)
At Thu, 21 Jun 2001 09:04:51 -0700 (PDT), David Wolfskill wrote: You may well have obtained your updates at an inopportune time: I'm still building today's -CURRENT, but have got beyond the buildworld (with no incident), and am in the process of building the new kernel. Thank you for your information. My script will retry building the world within one hour... -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
Hi, would you mind resubmitting a patch for the version of picobsd i committed this morning, also keeping in mind the following: * it would be better to define a variable, say MD, which holds the string vn or md, and is used in accessing the memory device, so we have mostly the same script working on both current and stable with just a one-line change. * you are recursively gzipping files in /etc now, so you should also modify the mfs_tree/etc/rc script which decompresses things; This might be annoying as gzip is unable to recurse in a directory tree. * re. the CONFIG variable... it does not seem to give problem with the version i committed this morning. I think there was a bug in the previous commit, but now it should be ok. * i am not sure the way you handle arguments is correct, from your patch it appears that you ignore THETYPE (first argument) if there are not two arguments. This is wrong, the second argument is optional. thanks luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . 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) Mobile +39-347-0373137 ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: orm driver itches (vga1, sc1, pca[12], isic1)?
In message [EMAIL PROTECTED] Alexander Leidinger writes: : On 20 Jun, Warner Losh wrote: : : However, it is related to having both a hints line in your config file : and a /boot/device.hints file. fdc1 is the giveaway here. : : Bug or feature? : : I like to have the hints compiled in (just in case /boot/device.hints : disappears for whatever reason) and to have it in /boot/device.hints to : be able to modify them whitout recompiling the kernel. I'd say it is a bug because the hints both say the same thing. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCM sound problems in -current ??
I'm having problems with both an internal VIA'686 and a PCI base ESS Solo1, both seem to loose interrupts. The interrupts doesn't even show up in a vmstat -i / systat so something is definitly wrong. BTW the exact same HW work just fine with -stable ? while i've not tested either of these chips for a while (lack of slots, anyone know of a motherboard with ~20 pci and ~10 isa slots?) i can't think of any changes that might cause this except possibly the introduction of INTR_TYPE_AV - and then only if you're using modules and your modules are built from newer source than your kernel. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
lock order reversal
Yet another... Jun 20 19:47:08 hades /boot/kernel/kernel: lock order reversal Jun 20 19:47:08 hades /boot/kernel/kernel: 1st 0xc04d91a0 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007 Jun 20 19:47:08 hades /boot/kernel/kernel: 2nd 0xc3f86b6c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016 The revision of the referenced file is: /usr/src/sys/ufs/ffs/ffs_vfsops.c: $FreeBSD: src/sys/ufs/ffs/ffs_vfsops.c,v 1.155 2001/05/29 21:21:49 phk Exp $ -giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCM sound problems in -current ??
It seems Cameron Grant wrote: I'm having problems with both an internal VIA'686 and a PCI base ESS Solo1, both seem to loose interrupts. The interrupts doesn't even show up in a vmstat -i / systat so something is definitly wrong. BTW the exact same HW work just fine with -stable ? while i've not tested either of these chips for a while (lack of slots, anyone know of a motherboard with ~20 pci and ~10 isa slots?) i can't think of any changes that might cause this except possibly the introduction of INTR_TYPE_AV - and then only if you're using modules and your modules are built from newer source than your kernel. Maybe you should test them now :) Anyhow, the VIA driver doesn't use INTR_TYPE_AV it uses 0, and a quick grep amongst the pci sound card drivers reveals that 0, .._AV, .._MPSAFE is used in a way that doesn't make sense to me at least... To make it short I tried playing with those, no effect i still get the dreaded channel dead message. An no I dont use modules, its all compiled into the kernel.. And yes, its still works in -stable... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo scribbled: | would you mind resubmitting a patch for the version of | picobsd i committed this morning, also keeping in mind the | following: | | * it would be better to define a variable, say MD, which holds | the string vn or md, and is used in accessing the memory | device, so we have mostly the same script working on both current | and stable with just a one-line change. | | * you are recursively gzipping files in /etc now, so you should | also modify the mfs_tree/etc/rc script which decompresses things; | This might be annoying as gzip is unable to recurse in a | directory tree. | | * re. the CONFIG variable... it does not seem to give problem with | the version i committed this morning. I think there was a bug | in the previous commit, but now it should be ok. | | * i am not sure the way you handle arguments is correct, from your | patch it appears that you ignore THETYPE (first argument) if there | are not two arguments. This is wrong, the second argument is optional. I have more questions regarding this: * Do we want NO_SWAPPING on or off in PicoBSD? I understand that many PicoBSD devices do not have swapspace. However, my understand of -current is that we do require swapping to work well. * Do we want SOFTUPDATES? * Statically compiling device.hints seems to be awkward. Perhaps we should be using a customized /boot/device.hints. This way, many devices can be disabled or enabled easily without recompiling PicoBSD/ version -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
* Do we want NO_SWAPPING on or off in PicoBSD? I understand that many PicoBSD devices do not have swapspace. However, my understand of -current is that we do require swapping to work well. given that in the vast majority of cases you don't have a choice... * Do we want SOFTUPDATES? same as above. who cares, the memory fs is mostly readonly, and secondary storage is generally unavailable. * Statically compiling device.hints seems to be awkward. if i am not mistaken, it is the bootloader which should read the hints, but in picobsd there is no bootloader, so we have no other choice. I doubt this is a big issue, anyways, most hardware is PnP these days. flexibility is good, but reality (with its constraints) comes first :) cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo wrote:
would you mind resubmitting a patch for the version of
picobsd i committed this morning, also keeping in mind the
following:
That patch was based off of your 8:49AM (revision 1.7) commit
this morning.
* it would be better to define a variable, say MD, which holds
the string vn or md, and is used in accessing the memory
device, so we have mostly the same script working on both current
and stable with just a one-line change.
The method of allocating and releasing a md and vn are
different, would it be too much to maintain two different
scripts (-stable and -current) until mdconfig replaces
its counterpart?
* you are recursively gzipping files in /etc now, so you should
also modify the mfs_tree/etc/rc script which decompresses things;
This might be annoying as gzip is unable to recurse in a
directory tree.
Good idea, I missed that.
* re. the CONFIG variable... it does not seem to give problem with
the version i committed this morning. I think there was a bug
in the previous commit, but now it should be ok.
On line 336 of the script, you export dead air, resulting in
no program being passed to Makefile.conf, my snippet of code
at the bottom should be removed and a more appropriate line
inserted after line 62 along the lines of:
CONFIG=${CONFIG:-config}
I missed that portion of that script when I was looking at it
this morning.
* i am not sure the way you handle arguments is correct, from your
patch it appears that you ignore THETYPE (first argument) if there
are not two arguments. This is wrong, the second argument is optional.
Yeah, that should be $1 not $2.
thanks
luigi
---+-
Luigi RIZZO, [EMAIL PROTECTED] . 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)
Mobile +39-347-0373137
---+-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Problems with ata probing twice.
On Thu, 21 Jun 2001, Makoto MATSUSHITA wrote: matusita I've just updated to 5-current as of yesterday (yeh!), but matusita no helps. 'ata' driver detects the second devices which is matusita _not_ on this machine. Since the kernel detects ata1 which eats IRQ 15, the kernel fail to attach the first fxp device (which is actually uses IRQ15). I want to use both fxp ethernet devices... See PR kern/21400. Sounds like the same problem I was (and still am) having. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: broken world (kerberos5/lib/libasn1)
Jun Kuriyama [EMAIL PROTECTED] writes:
Today's nightly build reports breakage of the world...
Please update to kerberos5/lib/libasn1/Makefile:1.9 or apply the
appended patch (relative to 1.8).
/assar
Index: Makefile
===
RCS file: /home/ncvs/src/kerberos5/lib/libasn1/Makefile,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -w -u -w -r1.8 -r1.9
--- Makefile2001/06/21 12:55:44 1.8
+++ Makefile2001/06/21 19:19:00 1.9
@@ -1,4 +1,4 @@
-# $FreeBSD: src/kerberos5/lib/libasn1/Makefile,v 1.8 2001/06/21 12:55:44 assar Exp $
+# $FreeBSD: src/kerberos5/lib/libasn1/Makefile,v 1.9 2001/06/21 19:19:00 assar Exp $
LIB= asn1
CFLAGS+=-I${KRB5DIR}/include \
@@ -70,7 +70,6 @@
.PATH: ${KRB5DIR}/lib/asn1
.PATH: ${KRB5DIR}/lib/vers
.PATH: ${KRB5DIR}/lib/roken
-.ORDER:parse.o lex.o
build-tools: make-print-version asn1_compile
@@ -115,7 +114,7 @@
mv y.tab.c parse.c
mv y.tab.h parse.h
-lex.o: lex.l
+lex.o: lex.l parse.h
print_version.o: print_version.h print_version.c roken.h
${CC} ${CFLAGS} -c -o ${.TARGET} ${KRB5DIR}/lib/vers/print_version.c
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: SCSI hangs w/SuperMicro 6010H
On 17-Jun-01 Dave Cornejo wrote: Please excuse me if you've seen this in questions, but I found a relevancy to current: If I drop back to 4.3 release, this system boots every time with no hangs observed in half a dozen tries in either UP or SMP mode. Anyone else seeing similar? Is this on -current or -stable? If it's on -current, why did you ask on -questions? :) It looks like an interrupt problem however. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversal
On 21-Jun-01 Jun Kuriyama wrote: Another message is reported: lock order reversal 1st 0xc043ad20 dev_pager create @ ../../vm/device_pager.c:142 2nd 0xc0459840 vm @ ../../vm/vm_kern.c:186 Thanks, I'll try and look at this in a bit. I have a big set of locking changes to the pagers that I might ask you to try to see if you can still reproduce this. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI hangs w/SuperMicro 6010H
John Baldwin wrote: Is this on -current or -stable? If it's on -current, why did you ask on -questions? :) It looks like an interrupt problem however. When I asked on questions, I was of the belief that I had a hardware problem and that it was not necessarily a -current issue. When I later went back and installed 4.3 and it worked I then realized that I had justification to post it on -current. Hey, at least I didn't cross-post to questions, stable, scsi, and current! :) I guess my next step is to try and trace through what's happening - can you suggest a good place to start (like a routine to start tracing), or is there anything I can do that might get more info for the people that know what is going on? thanks! dave c -- Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED]) There aren't any monkeys chasing us... - Xochi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: convert libgmp to a port?
On Tue, Jun 19, 2001 at 12:44:40PM -0700, Terry Lambert wrote: Giorgos Keramidas wrote: On Sun, Jun 17, 2001 at 01:51:56PM -0700, Kris Kennaway wrote: libbn is already part of OpenSSH; it's a trivial matter to make it ^^^ I meant to say OpenSSL here, of course. into a standalone library. In other words, we already include two functionally equivalent bignum libraries in FreeBSD, so one of them should go. I couldn't agree more :) I'm going to word this strongly, mostly because I feel strongly about the underlying issues. The SSL one is known to be very slow, and was written as a proof of concept by the author. Please read the release notes; it is seriously slow. Replacing it will increase your SSL performance significantly. I know of no-one who has developed patches to make OpenSSL work with an external math library (e.g. libgmp). The OpenSSL guys are very interested in cleaning up their legacy code; you should work with them if you are interested. In FreeBSD, the only use of the libgmp code is for non-speed-critical applications, so replacing it with a less efficient library doesn't cost anything. libgmp will still exist in ports for applications which want to make use of a more efficient library. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! S/Key is ancient, OPIE is new
On Thu, Jun 21, 2001 at 10:13:06PM +0400, Andrey A. Chernov wrote: On Thu, Jun 21, 2001 at 08:07:51 +0200, Mark Murray wrote: On Wed, Jun 20, 2001 at 21:03:21 +0200, Mark Murray wrote: I want to remove S/Key from CURRENT completely, and replace it with OPIE where necessary. For the most part, this means just using PAM, but in one-or-two places, it may still be necessary to use it directly (like temporarily in ftpd). Please don't forget to fix ports which use system Skey too, like wu-ftpd and popper. Good move. I think we need to make S/Key into a port for this. Why? Better way will be rewritting ports to use good-new OPIE. wi-ftpd already have OPIE hooks, but I not sure they works. Popper needs modifications. Doesn't know, if other ports using Skey exists. I think it's pretty trivial to convert things from S/Key to OPIE. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!! S/Key is ancient, OPIE is new
On Thu, Jun 21, 2001 at 11:52:52AM +0200, Dag-Erling Smorgrav wrote: Mark Murray [EMAIL PROTECTED] writes: I want to remove S/Key from CURRENT completely, and replace it with OPIE where necessary. How will this affect OpenSSH's SKeyAuthentication option, which is required for certain types of token-based authentication (like CryptoCard)? It already uses OPIE; AFAIK OpenBSD decided to call OPIE S/Key when they imported it to replace their old S/Key. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: convert libgmp to a port?
On Thu, Jun 21, 2001 at 01:15:12PM -0700, some SMTP stream spewed forth: On Tue, Jun 19, 2001 at 12:44:40PM -0700, Terry Lambert wrote: Giorgos Keramidas wrote: On Sun, Jun 17, 2001 at 01:51:56PM -0700, Kris Kennaway wrote: libbn is already part of OpenSSH; it's a trivial matter to make it ^^^ I meant to say OpenSSL here, of course. into a standalone library. In other words, we already include two functionally equivalent bignum libraries in FreeBSD, so one of them should go. I couldn't agree more :) I'm going to word this strongly, mostly because I feel strongly about the underlying issues. The SSL one is known to be very slow, and was written as a proof of concept by the author. Please read the release notes; it is seriously slow. Replacing it will increase your SSL performance significantly. I know of no-one who has developed patches to make OpenSSL work with an external math library (e.g. libgmp). The OpenSSL guys are very interested in cleaning up their legacy code; you should work with them if you are interested. In FreeBSD, the only use of the libgmp code is for non-speed-critical applications, so replacing it with a less efficient library doesn't cost anything. libgmp will still exist in ports for applications which want to make use of a more efficient library. Am I understanding this correctly? We currently have implemented a more efficient library than one you propose expending effort to plug in? You propose that people remove the currently implemented and more efficient library and replace it with a less-efficient library of non-native BSD origin? Really? This hardly seems like a good idea. gh Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI hangs w/SuperMicro 6010H
On 21-Jun-01 Dave Cornejo wrote: John Baldwin wrote: Is this on -current or -stable? If it's on -current, why did you ask on -questions? :) It looks like an interrupt problem however. When I asked on questions, I was of the belief that I had a hardware problem and that it was not necessarily a -current issue. When I later went back and installed 4.3 and it worked I then realized that I had justification to post it on -current. Hey, at least I didn't cross-post to questions, stable, scsi, and current! :) Ok, sounds good, just checking. :) Can you provide the output of mptable for this box? In the SMP case, -current does interrupt routing for PCI interrupts a bit differently, which might be a possible reason. Hmm, but you are getting interrupts eventually it seems. I guess my next step is to try and trace through what's happening - can you suggest a good place to start (like a routine to start tracing), or is there anything I can do that might get more info for the people that know what is going on? Actuually, KTR is your friend here. :) Read the ktr(4) manpage, then compile a kernel with KTR_MASK and KTR_COMPILE set to KTR_INTR|KTR_PROC. Then when it hangs, break into DDB and look at the longs via 'show ktr' to see if you can locate any interrutps coming in from ahc0 or ahc1. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI hangs w/SuperMicro 6010H
John Baldwin wrote: Ok, sounds good, just checking. :) Can you provide the output of mptable for this box? In the SMP case, -current does interrupt routing for PCI interrupts a bit differently, which might be a possible reason. Hmm, but you are getting interrupts eventually it seems. I can only get the thing past the hang maybe once in twenty+ tries. Below is the mptable output (I don't remember what version of FreeBSD I had installed when I did this, hope it doesn't matter). I'll try the KTR stuff later tonight. thanks! dave c === MPTable, version 2.0.15 --- MP Floating Pointer Structure: location: BIOS physical address: 0x000ff780 signature:'_MP_' length: 16 bytes version: 1.1 checksum: 0xb9 mode: Virtual Wire --- MP Config Table Header: physical address: 0x000f0bd0 signature:'PCMP' base table length:284 version: 1.1 checksum: 0x28 OEM ID: 'AMI ' Product ID: 'CNB20HE ' OEM table pointer:0x OEM table size: 0 entry count: 27 local APIC address: 0xfee0 extended table length:0 extended table checksum: 0 --- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model StepFlags 0 0x11BSP, usable 6 8 6 0x387fbff 1 0x11AP, usable 6 8 6 0x387fbff -- Bus:Bus ID Type 0 PCI 1 PCI 2 PCI 3 ISA -- I/O APICs: APIC ID Version State Address 4 0x11usable 0xfec0 5 0x11usable 0xfec01000 -- I/O Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# INT active-lo level1 0:A 5 14 INT active-lo level0 5:B 5 11 INT active-lo level0 15:A 4 10 INT active-lo level0 6:A 5 15 INT active-lo level0 5:A 5 10 INT active-lo level0 4:A 5 12 ExtINT active-hiedge3 0 40 INT active-hiedge3 1 41 INT active-hiedge3 0 42 INT active-hiedge3 3 43 INT active-hiedge3 4 44 INT active-hiedge3 6 46 INT active-hiedge3 8 48 INT active-hiedge312 4 12 INT active-hiedge313 4 13 INT active-hiedge314 4 14 INT active-hiedge315 4 15 -- Local Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# ExtINT active-hiedge3 02550 NMI active-hiedge0 0:A2551 === -- Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED]) There aren't any monkeys chasing us... - Xochi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problems with ata probing twice.
At 11:47 PM +0900 6/18/01, Makoto MATSUSHITA wrote: (from dmesg output) atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 This looks right to me. One main PIIX4 ATA controller with two independent IDE channels (usually referred to as a Primary and a Secondary IDE controller). Usually the PC BIOS will allow you to turn on/off these channels independently. Does your bios allow you to turn off the Secondary? I've tried to figure out what's going on with atacontrol(8), and got: ushi % sudo atacontrol info ata0 Master slot: ad0: IBM-DJSA-220/JS4OAC3A ATA/ATAPI rev 5 Slave slot: no device present ushi % sudo atacontrol info ata1 Master slot: ad0: IBM-DJSA-220/JS4OAC3A ATA/ATAPI rev 5 Slave slot: no device present Apparantly, the kernel attaches same bus/HDD _twice_. I don't think the HDD is being detected twice. Try this instead: % sudo atacontrol info 0 % sudo atacontrol info 1 Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: support Pentium3 SSE
Michael C . Wu wrote: On Thu, Jun 21, 2001 at 04:07:25PM +0100, David Malone scribbled: | On Wed, Jun 20, 2001 at 05:39:55PM -0400, Andrew Gallatin wrote: | While we're at it, I know that the AMD AthlonMP supports SSE, but I I think we already detect AthlonMP's SSE automatically. I recall reading Peter's dmesg of his Tyan board and seeing SSE in the config. CPU: AMD Athlon(tm) Processor (1194.43-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x661 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,\ MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc044b18,AMIE,DSP,3DNow! Note the FXSR (fast context save and restore) and the SSE flag are there. This is an AthlonMP system: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 and it works very nicely. :-) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: orm driver itches (vga1, sc1, pca[12], isic1)?
Warner Losh wrote: In message [EMAIL PROTECTED] Alexander Leidin ger writes: : On 20 Jun, Warner Losh wrote: : : However, it is related to having both a hints line in your config file : and a /boot/device.hints file. fdc1 is the giveaway here. : : Bug or feature? : : I like to have the hints compiled in (just in case /boot/device.hints : disappears for whatever reason) and to have it in /boot/device.hints to : be able to modify them whitout recompiling the kernel. I'd say it is a bug because the hints both say the same thing. Definately a bug. :-( The scanner is effectively concatenating the device.hints and the config hints together when enumerating them. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
From -current to -stable?
Hi, I followed the directions on the freebsd web site to grab the latest -stable sources, but it looks like somehow I got the -current sources, built and installed them (doh!). Everything is working ok, but this is my development laptop, and it would probably be wiser to track -stable so that things will still work. I have grabbed the RELENG_4 source, but it is dying at unctrl.h. Is there any way to go backward from an installed current build, to stable? Thanks.. -- T.J. Kniveton Communications Systems Lab Nokia Research Center To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: broken world (kerberos5/lib/libasn1)
At 21 Jun 2001 21:19:58 +0200, Assar Westerlund wrote: Please update to kerberos5/lib/libasn1/Makefile:1.9 or apply the appended patch (relative to 1.8). Fixed. Thanks! -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversal
kuriyama I got message below with WITNESS option. Is this safe to ignore? I've found another WITNESS message (5-current CVSuped Jun/18/2001): lock order reversal 1st 0xc5d2043c process lock @ ../../vm/vm_glue.c:487 2nd 0xc05a9ec0 lockmgr interlock @ ../../kern/kern_lock.c:239 *** Revision ID of these files are: % cd /usr/src/sys; grep FreeBSD: vm/vm_glue.c kern/kern_lock.c vm/vm_glue.c: * $FreeBSD: src/sys/vm/vm_glue.c,v 1.114 2001/05/23 22:35:45 jhb Exp $ kern/kern_lock.c: * $FreeBSD: src/sys/kern/kern_lock.c,v 1.46 2001/04/28 12:11:01 alfred Exp $ -- - Makoto MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCM sound problems in -current ??
In message 006501c0fa71$7fa71a40$0504020a@haveblue Cameron Grant writes: : while i've not tested either of these chips for a while (lack of slots, : anyone know of a motherboard with ~20 pci and ~10 isa slots?) i can't think : of any changes that might cause this except possibly the introduction of : INTR_TYPE_AV - and then only if you're using modules and your modules are : built from newer source than your kernel. We use 15 ISA slot passive backplanes at work. But we make them ourselves. I have seen these in industrial control catalogs in the past. The most PCI slots I've seen is 7. I take that back, I did once see a specialized motherboard with 4 or 5 PCI buses, each with 4 slots. But that was made my a different company for its own private use. Something to do with data gathering or signal replication. I'm not completely sure. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI hangs w/SuperMicro 6010H
John Baldwin wrote: Actuually, KTR is your friend here. :) Read the ktr(4) manpage, then compile a kernel with KTR_MASK and KTR_COMPILE set to KTR_INTR|KTR_PROC. Then when it hangs, break into DDB and look at the longs via 'show ktr' to see if you can locate any interrutps coming in from ahc0 or ahc1. Okay - fired up the box, built a kernel off of a 6/18 source snapshot, and it hangs in about the same place - however what I get that as soon as I touch a key to invoke the debugger from the console, it continues merrily booting and I can't break into DDB until way past the problem. In my mind this kind of confirms something is busted in the interrupts. Tried looking back through the show ktr output and I'm not 100% clear on what it all means - I guess I'm interested in the ithread stuff and the only thing I ever see is swi6: tty:sio+ in the trace buffer besides what appears to be normal process rescheduling (?) which is mostly idle task time... Do think there's any use to rolling my source tree back a ways and compiling a kernel? thanks, dave c -- Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED]) There aren't any monkeys chasing us... - Xochi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: convert libgmp to a port?
*snip* No. We are talking about removing a GPL infected library from the base tree that is used by a couple of utterly performance irrelevant utilities and making these couple of utilities (secure-rpc key generation tools) use the OpenSSL bignum API - where OpenSSL has a BSD-style license. This has absolutely no effect on openssl at all. Really? This hardly seems like a good idea. No. We can't plug libgmp into openssl anyway due to GPL infection and the resulting license conflicts. openssl *explicitly* may not be distributed under GPL. And building libgmp into openssl would require exactly that. *snip* Oh, I see. Nevermind then, sounds good. (Somehow I missed the libgmp-GPL relationship.) gh (Apologies to the CC's who didn't need this aside.) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
