mount -o union broken recently?
I have been experimenting with union mounts today with a recent -stable (cvsupped yesterday), and I haven't had much luck. Because cvsup likes to obliterate local changes, I thought it would be convenient to keep the altered files on a separate filesystem and use a union mount to overlay them on the upstream source when I compile things. So: # mount /dev/da0s1a on / (local, writes: sync 420 async 3185) procfs on /proc (local) /dev/da0s1e on /www (local, writes: sync 2 async 0) # mount /dev/da0s1f /srcdelta # ls -l /srcdelta total 1 drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys # umount /srcdelta # ls /usr/src COPYRIGHT UPDATING include share CVS bin kerberosIVsys Makefile contrib lib tools Makefile.inc0 cryptolibexec usr.bin Makefile.inc1 etc release usr.sbin Makefile.upgrade games sbin READMEgnu secure # mount -o union /dev/da0s1f /usr/src # ls -l /usr/src total 1 drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys # umount /usr/src # uname -a FreeBSD shirt.www.demon.net 3.1-STABLE FreeBSD 3.1-STABLE #6: Thu Feb 18 02:26:59 GMT 1999 r...@shirt.www.demon.net:/usr/src/sys/compile/SHIRT i386 # However, on another machine running 3.0-RELEASE mount -o union works as expected: # ls -l total 6 drwxr-xr-x 2 root wheel 512 Feb 18 16:36 da1 drwxr-xr-x 2 root wheel 512 Dec 11 11:06 da2 # mount /dev/da1s1e da1 # mount /dev/da2s1e da2 # ls -l da?/* -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da2/this_is_da2 # umount da2 # mount -o union /dev/da2s1e /www/da1 # ls -l da?/* -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da2 # Shirt's kernel configuration is below. Tony. -- f.a.n.finch d...@dotat.at f...@demon.net machine i386 cpu I686_CPU ident SHIRT maxusers64 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options MFS #Memory Filesystem #optionsMFS_ROOT#MFS usable as root device, MFS req'ed options NFS #Network Filesystem options NFS_NOSERVER #optionsNFS_ROOT#NFS usable as root device, NFS req'ed options MSDOSFS #MSDOS Filesystem #optionsCD9660#ISO 9660 Filesystem #optionsCD9660_ROOT #CD-ROM usable as root. CD9660 req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NETALIAS options NETBIND options SOFTUPDATES options MAXMEM=(64*1024) options PQ_MEDIUMCACHE options INCLUDE_CONFIG_FILE options PERFMON options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_DEFAULT_TO_ACCEPT options ICMP_BANDLIM options DUMMYNET config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0at isa? port IO_FD1 bio irq 6 drq 2 diskfd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 options CMD640# work around CMD640 chip deficiency controller wdc0at isa? port IO_WD1 bio irq 14 diskwd0 at wdc0 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC#Don't do it as an LKM device acd0#IDE CD-ROM controller ncr0 controller scbus0 device da0 device pass0 device cd0 #Only need one of these, the code dynamically grows # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0at isa? tty irq 12 device vga0at isa? port ? conflicts # splash screen/screen saver #pseudo-device splash #optionsVM86 #optionsVESA # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0at isa? port IO_NPX irq 13 # Laptop support (see LINT for more options) # device apm0at isa? disable flags 0x31 # Advanced Power Management # serial port device
HEADS UP: struct proc changing
While everyone is hob-nobbing at USENIX I thought I'd take the opportunity to make a gratuitous change to the proc structure. I'll be adding a pointer to the end of it which can be used by emulators for storing process-related emulator-specific information. It'll initially be used for storing information related to signal context state in the SysVR4 emulator, but there's no reason other emulators can't use it to hook into state data they need to store on a process-by-process base. I'll commit it tomorrow; You'll need to rebuild libkvm and any statically linked binaries which are linked against libkvm (or just do a make world). Cheers, - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Filesystem deadlock
Luoqi Chen said: Do you still have that piece of code? Does it handle the case involves more than one process? For example, process 1 mmaps file B and reads file A into the mmapped region, while process 2 mmaps file A and reads file B, this could also result in a deadlock. It used to be part of the tree, but I seem to remember that it was removed (by those who understand the code :-)) soon after I left. I will look for it, and see if it would help with the problem(s). -- John | Never try to teach a pig to sing, dy...@iquest.net | it makes one look stupid jdy...@nc.com | and it irritates the pig. I have some thoughts on how to solve this problem. A deadlock can occur when you read into a mmapped region or write from a mmapped region, a solution to this problem must be able to handle both cases. For the first case (read), (as originally suggested by Tor Egge), we could allow vm_fault's shared lock attempt to succeed even if there's already a process waiting for the exclusive lock. This is unlikely to create any starvation problem. For the second case (write), it's trickier if there're two processes involved. My solution is not to use exclusive lock for write, because in most cases we don't need to lock the vnode exclusively, except when disk block allocation is required. We could instead perform a lock upgrade before and a downgrade after the block allocation, so the process will only hold a shared lock when copying from the mmapped address, and thus deadlock can be avoided just as in the first case. Comments? -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kernel build failure at nfs_serv.c
On Tue, 23 Feb 1999, Nicolas Souchu wrote: Hi folks, Updating at Mar 23 f?v 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_serv.c ../../nfs/nfs_serv.c:103: `sysctl__vfs_nfs_children' undeclared here (not in a function) ../../nfs/nfs_serv.c:103: initializer element for `sysctl___vfs_nfs_async.oid_parent' is not constant *** Error code 1 Stop. Any clue? I think this is fixed - try updating nfs_serv.c -- 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: NFS Problems
On 23 Feb 1999, Joel Ray Holveck wrote: This reminds me; do we have a utility to reference wmesg strings back to the code that sets them, a la TAGS? Would this be useful? No, and yes respectively. I have the scanner mostly written; there is one bug yet to fix (This time for sure!). Presently, it creates a single file WTAGS which contains an easily-read (my man or machine) flat file index. I will presently be modifying it to generate Emacs's etags format, as well as ctags, and as soon as I learn it, GSYMS format. At the moment, the scanner scans tsleep, asleep, and ttysleep calls. What other sleep functions can have the wchan specified as a string literal? There being no robust manner to handle calls with a computed or dereferenced wchan, such as acquire(), I will allow for a notation of /* WCHAN: foo */ to cause the appropriate information to be added to the database. lockinit() takes a wmesg string which is used when a process sleeps on the lock. -- 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: sh(1) -- exec vs. fork
In 199902191644.laa08...@misha.cisco.com, Mikhail Teterin wrote:
I just finished going through a couple of crontabs prepending the
command-lines with ``exec'', when it hit me.
Can shell itself recognize, there will be no more commands and just
proceed to exec without forking? What would this break?
This should never, of course, happen in interactive mode...
The shell's source requires studying, but, may be, a knowledgeable
person can answer right away?
FreeBSD's /bin/sh does a forkless exec in some cases, which is why we
have the echo -n in /etc/rc:
(trap 'exit 1' 2 ; ${script} start ; echo -n)
The problem with not forking is that trap handling is being
broken. Currently, our /bin/sh eliminates one instance when subshells
are started with '(...)', the last command in the brackets is just
exec'ed without fork.
Example:
#! /bin/sh
echo $$
(
echo $$
cat
)
The subshell replaces the outer instances, the pids echoed are the
same.
But this will break asynchronous traps (which are not Posix, BTW),
hence it doesn't do this for the outermost shell of a shell script:
#! /bin/sh
echo $$
cat
The outer shell still exists when cat is exec'ed.
Obviously, while this inconsistent behaviour gets most cases right, it
isn't perfect, as seen in the /etc/rc hack above.
What is needed here is that the process elimination happens only when
no traps are set.
I looked into this in September (with help from Tor Egge), we need a
count of active traps and if traps are active, don't do subshell
elimination. The problem here is that counting active traps isn't that
easy. Also, this would only solve the lower half of the problem, that
too much elimination happens for subshells.
The upper half, that elimination could/should happen for toplevel
shells when the last command of a script is being exectued needs more
thought. I feel uncomfortable having a shellscript running without a
handle to the toplevel controlling shell process. For example, you
might want to use it get the whole process group of everything it
started.
Martin
--
%
Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/
BSD User Group Hamburg, Germany http://www.bsdhh.org/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Promise IDE board docs
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote: Søren Schmidt said: It should work, but the promise support in the old system is, well, hacky at best. I'm not sure if Promise supports more than one card at a time, but from looking at the chip specs, it should work just fine, and if the hardware works, at least the new driver will support it. I run with two (2) boards, but it appears that certain (all?) versions of the bios require that you remove the chip from all but one board. I did run such a setup as well, but the disks on the first controller with BIOS ran much faster than those on the BIOSless controller. Martin -- % Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Strange routing to www.freebsd.org ;)
I'm today discovered strange routing to www.freebsd.org sh$ traceroute www.freebsd.org [...] 15? T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)? 698.413 ms? 608.198 ms? 578.823 m s 16? R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)? 609.090 ms? 598.030 ms? 599.085 ms 17? T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)? 978.255 ms? 608.167 ms? 578.853 m s 18? R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)? 598.453 ms? 598.058 ms? 608.966 ms 19? T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)? 618.394 ms? 598.144 ms? 589.037 m s 20? R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)? 598.230 ms? 608.151 ms? 748.804 ms 21? T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)? 608.493 ms? 618.058 ms? 638.848 m s [etc to infinity] What the matter? Maxim Sobolev To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Promise IDE board docs
It seems Martin Cracauer wrote: In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote: Søren Schmidt said: It should work, but the promise support in the old system is, well, hacky at best. I'm not sure if Promise supports more than one card at a time, but from looking at the chip specs, it should work just fine, and if the hardware works, at least the new driver will support it. I run with two (2) boards, but it appears that certain (all?) versions of the bios require that you remove the chip from all but one board. I did run such a setup as well, but the disks on the first controller with BIOS ran much faster than those on the BIOSless controller. Hmm, which suggests that I need to leave the do it by hand code in there and recommend removing the BIOS :( -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Staroffice 5.01?
Has anyone gotten SO501 to run on -current? Thx To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: zone: entry not free
On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote: You could add -DINVARIANTS to CFLAGS in sys/module/msdosfs/Makefile. OK, did that, no more panics. Thanks! Dima Cheers, -- Jos Backus _/ _/_/_/Reliability means never _/ _/ _/ having to say you're sorry. _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ jos.bac...@nl.origin-it.com _/_/ _/_/_/use Std::Disclaimer; To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
IDE CDROM not found with PIIX4 chipset, -current kernel
I've been having problems with an IDE controller on my motherboard. I can't seem to be able to get it to recognize a CDROM drive (it's the only device plugged on the second IDE controller). The kernel seems to timeout on that second controller during the probe phase. Maybe that's one of the infamous PIIX 4 bugs... The machine is a Dell Optiplex. The first weird thing is that the CDROM drive is found if I plug another IDE drive as slave on the second controller. The second weird thing is that it's recognized perfectly correctly if I boot a Linux installation disk... So I assume they found a workaround, if that's a PIIX 4 bug. I've tried to change the device flags (with and without DMA), to no avail. I've followed every recent patch to the IDE code, none of these seems to help (the last kernel I tried is a 4.0-current from Monday). Here's my dmesg: ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 ... wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): Maxtor 90640D4, DMA, 32-bit, multi-block-16 wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): Maxtor 90640D4, DMA, 32-bit, multi-block-16 wd1: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa ... then nothing, it times out after a while and goes on with the boot, no CDROM is ever found. Here's an excerpt from my kernel config. Did I miss something obvious? controller wdc0at isa? port IO_WD1 bio irq 14 flags 0xa0ffa0ff vector wdintr diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 bio irq 15 flags 0xa0ffa0ff vector wdintr diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC#Don't do it as an LKM device acd0#IDE CD-ROM -- Pierre Beyssac p...@enst.fr To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE CDROM not found with PIIX4 chipset, -current kernel
On Wed, 24 Feb 1999 23:51:17 +0100, Pierre Beyssac wrote: Here's an excerpt from my kernel config. Did I miss something obvious? controller wdc0[...] diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 controller wdc1[...] diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC#Don't do it as an LKM device acd0#IDE CD-ROM Um... Do you really have 4 wd devices plugged in? If so, where on earth are you plugging the CDROM device in? :) Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM device on your primary IDE controller. So you'd do something like: controller wdc0 controller wdc1 diskwd0 at wdc0 drive 0 diskwd1 at wdc1 drive 0 diskwd2 at wdc1 drive 1 ...followed by your acd device, naturally. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CVS and Y2K
Does FreeBSD still ship with CVS version 1.9.26? If so it needs to be
upgraded within the next 9 months or so. 1.9.26 can't parse dates
past 1999-12-31.
Have you verified this?
from http://www.cyclic.com/cvs/info-y2k.html:
Do not plan to continue to use CVS 1.9 or older beyond the year 2000. Such
versions of CVS have known bugs in their ability to handle dates beyond 2000.
These bugs are fixed in CVS 1.10, and we recommend an upgrade to CVS 1.10 some
time before the year 2000.
( 4.0-current as of yesterday )
[15:36:04]1020 cvs -v
Concurrent Versions System (CVS) 1.9.26 (client/server)
bummer...
--
obfuscate v.t. darken; obscure; bewilder.
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: IDE CDROM not found with PIIX4 chipset, -current kernel
On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote: controller wdc1[...] diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 Um... Do you really have 4 wd devices plugged in? Uh, well, no, just 2 (on the first IDE controller). Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM device on your primary IDE controller. So you'd do something like: Wow. Thanks a million! I didn't even have to go so far, I just deleted wd2 and wd3 and acd0 now appears as if by magic. I can't tell you how extremely stupid I now feel... OTOH, I copied this from the GENERIC kernel config file, assuming it recognizes an ATAPI CDROM when it finds one. So my puzzled question is now: how can the GENERIC kernel work in that case, since it declares wd[0-3] ? -- Pierre Beyssac p...@enst.fr To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Promise IDE board docs
On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote: Hmm, which suggests that I need to leave the do it by hand code in there and recommend removing the BIOS :( Are there any plans to support the Promise Fast Trak IDE RAID controller ? ---Mike Mike Tancsa (mdtan...@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Staroffice 5.01?
On 24-Feb-99 Alok K. Dhir wrote: Has anyone gotten SO501 to run on -current? I have and its quite good, but it hangs occasionally.. The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..) What problems are you having? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Promise IDE board docs
Martin Cracauer said: In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote: Søren Schmidt said: It should work, but the promise support in the old system is, well, hacky at best. I'm not sure if Promise supports more than one card at a time, but from looking at the chip specs, it should work just fine, and if the hardware works, at least the new driver will support it. I run with two (2) boards, but it appears that certain (all?) versions of the bios require that you remove the chip from all but one board. I did run such a setup as well, but the disks on the first controller with BIOS ran much faster than those on the BIOSless controller. The order of the boards is critical, and which bios is installed. Of course, YMMV. Each drive on each controller in my case runs at full speed :-). On the bootup sequence, I get one BIOS display of eight drive slots, as if I am using one board, with 8 drive positions (even though I really have two boards.) Of course, the PCI bus probes the controllers as two controllers, but the BIOS kind of acts like one logical controller. -- John | Never try to teach a pig to sing, dy...@iquest.net | it makes one look stupid jdy...@nc.com | and it irritates the pig. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
panic: aha0 Invalid CCB or SG list
(Sorry for the crosspost, but I'd like to now if this is fixed in -current) Hi! I've seen three crashes in the last couple of weeks, with a server box that's been running stable as a rock for two years, at least. It has an adaptec 2940UW with six disks, and an adaptec 1542CP that's connected to a seagate travan tape driver. It's running STABLE-3.1 from Feb 19 1999, and since the last upgrade, I've seen three crashes, all related to dumping to tape. Since I got no info on what happened, I decided to sit down with the machine, run a backup sequence to tape, and wait for it to possibly crash. After 90 minutes, I was about to give up when suddenly, poof: panic: aha0 Invalid CCB or SG list. So, it's probably the 1540 driver (or hardware)? Can anybody shed some light on what to do? Is it software? That's my guess, since the machine never ONCE has crashed until the upgrade to 3.x. I had one crash when running current form beginning of January (soon after moving to 3.x), and now theese three in a week. The 1540 has been in the machine for about six months. Before starting the panicking backup, I spawned off a few logs: netstat -I de0 -w 5 and vmstat -p sa -p da -w 5 I'm not sure how to interpret them, but there's an excerpt at the end of this mail of the vmstat output (it stops in the middle of a row, when the crash occurred). The backups are made with amanda (see the ports collection), and uses gzip, hence the outbursts of cpu load. The netstat seems pretty uninteresting; quite normal. If there's anything I can do to help debug I'll do it, but device drivers are a little above my level of expertise. Thanks in advance! /Palle Here's a dmesg: 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.1-STABLE #0: Fri Feb 19 23:35:59 CET 1999 gir...@tb303.partitur.se:/usr/src/sys/compile/TRUMPET Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 198948269 Hz CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0x617 Stepping=7 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 201326592 (196608K bytes) avail memory = 192790528 (188272K bytes) Preloaded elf kernel kernel at 0xf02b5000. Probing for devices on PCI bus 0: Correcting Natoma config for non-SMP chip0: Intel 82440FX (Natoma) PCI and memory controller rev 0x02 on pci0.0.0 chip1: Intel 82371SB PCI to ISA bridge rev 0x00 on pci0.7.0 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 de0: Digital 21140A Fast Ethernet rev 0x20 int a irq 12 on pci0.11.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:27:eb:e9 vga0: S3 Trio graphics accelerator rev 0x54 int a irq 9 on pci0.12.0 ahc0: Adaptec 2940 Ultra SCSI adapter rev 0x00 int a irq 11 on pci0.13.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs 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 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdreset: error1: 0x0 wdreset: error1: 0x0 wdc0 not found at 0x1f0 aha0 at 0x330-0x333 irq 10 drq 7 on isa aha0: AHA-1542CP FW Rev. D.0 (ID=46) SCSI Host Adapter, SCSI ID 7, 16 CCBs vga0 at 0x3c0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 5 seconds for SCSI devices to settle de0: enabling 100baseTX port sa0 at aha0 bus 0 target 5 lun 0 sa0: CONNER CTT8000-S 1.07 Removable Sequential Access SCSI-2 device sa0: 3.333MB/s transfers (3.333MHz, offset 8) da4 at ahc0 bus 0 target 4 lun 0 da4: SEAGATE ST39102LW 0005 Fixed Direct Access SCSI-2 device da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST32155W 0528 Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) changing root device to da0s1a da3 at ahc0 bus 0 target 3 lun 0 da3: IBM DCAS-34330W S65A Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 2 lun 0 da2: IBM DCAS-34330W S65A Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DCAS-34330W S65A Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4134MB (8467200 512 byte sectors: 255H
Re: listproc problem?
From: Thomas T. Veldhouse ve...@visi.com Date: Tue, 23 Feb 1999 13:42:37 -0600 Content-Type: text/plain; charset=iso-8859-1 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-curr...@freebsd.org X-Loop: FreeBSD.ORG Precedence: bulk I have been seeing 5 hour delays from when the message was sent to the list and when the message arrives in my mailbox. It seems to be a problem with the following jump: looks like we had an issue while trying to reach mail2.sol.net. that one hop took about 3 hours (not five...gotta watch those timezone changes ;) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id NAA00902; Tue, 23 Feb 1999 13:26:13 -0600 (CST) Received: by hub.freebsd.org (Postfix, from userid 538) id AECC411D08; Tue, 23 Feb 1999 07:34:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 5DD8B11B6C; Tue, 23 Feb 1999 07:34:37 -0800 (PST) (envelope-from owner-freebsd-stable) Also, as a side note, how do I set up my box to use PostFix instead of sendmail? I heard that it was (or was considered) included in the 3.1-RELEASE, it just wasn't enabled by default. it was considered but not included in the endthe disucssion in the committers mailing list indicated that people were not ready to go that way yet. we will try again soon. jmb To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE CDROM not found with PIIX4 chipset, -current kernel
On Thursday, 25 February 1999 at 1:04:48 +0100, Pierre Beyssac wrote: On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote: controller wdc1[...] diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 Um... Do you really have 4 wd devices plugged in? Uh, well, no, just 2 (on the first IDE controller). Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM device on your primary IDE controller. So you'd do something like: Wow. Thanks a million! I didn't even have to go so far, I just deleted wd2 and wd3 and acd0 now appears as if by magic. I can't tell you how extremely stupid I now feel... You shouldn't do. What you did shouldn't have any effect on the problem. You may find that sometimes it gets recognized, other times it doesn't. FreeBSD still has difficulties with some ATAPI CD-ROM drives. If you continue to have trouble (and I suspect you will), you should enter a PR with send-pr or at http://www.freebsd.org/send-pr.html. Make sure to give exact details of your hardware and software configuration. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NFS Problems
This reminds me; do we have a utility to reference wmesg strings back to the code that sets them, a la TAGS? Would this be useful? No, and yes respectively. Okay, I've got an early version written. It's got some fairly substantial TODO's, and needs a fair bit of cleanup. I would appreciate any comments anybody has. -cut here- #! /usr/bin/perl -w # Copyright (c) 1999 Joel Ray Holveck. All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright #notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright #notice, this list of conditions and the following disclaimer in the #documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $Id$ # NAME # wtags - generate wchan tag file # # SYNOPSIS # wtags [-cegw] [-v] [path] # # DESCRIPTION # wtags scans a 4.4BSD kernel source tree and creates a database # listing all the wchan's which are explicitly specified to # tsleep(9) or similar functions. This is useful for identifying # where in the kernel a process may be hung. # # The source tree to be searched may be specified with path, or # the current directory is used. Subdirectories are always # scanned, and symbolic links are always followed. # # The options are as follows: # # -c Generate ctags(1)-compatible output. Output is appended # to the file tags in the current directory. This file # is typically used with vi(1). # # -e Generate etags(1)-compatible output. Output is appended # to the file TAGS in the current directory. This file # is typically used with Emacs(1). # # -g Generate gtags(1)-compatible output. Output is appended # to the file GSYMS in the current directory. This file # is typically used with the global(1) tags system by # Shigio Yamaguchi, which may be used with vi(1), Emacs(1), # or other systems. # # -w Generate a native file format (described below). This # format is designed to be easily read by humans or machines, # but no utilities currently use it. -w is the default if # no other output format is specified. # # -v Generate warnings for many cases when a possible call to # tsleep(9) or a related function is found, but a wchan # could not be isolated. There are normally many of these # in correct code; one version of wtags produced 83 such # diagnostics on the 4.4BSD-Lite kernel. See DIAGNOSTICS, # below. # # wtags will only recognize string literals for wchan arguments. # A function (such as lf_setlock) which uses a string constant # instead, or one (such as ttread) which uses one of a few known # possibilities selected via :? or another mechanism, may have a # comment such as /* WCHAN: lockf */ on the line in question. # wtags will then use the indicated channel, and ignore any tsleep # call on that line. # # FILES # /sysTraditional kernel source location # WTAGS Default output file, used with -w or if no other # tag file is specified # TAGSEmacs(1) tags output file, used with -e # tagsvi(1) tags file, used with -c # GSYMS global(1) tags file, used with -g # # DIAGNOSTICS # If the -v option is specified, then whenever tsleep (or another # function that uses wchan) is written in the source file, but no # wchan can be found, a diagnostic is printed. These diagnostics # do not always properly describe the issue. # # There is one exception to this: if the item appears to be a # reference to tsleep from within a comment (using a heuristic), # then no diagnostic is printed. # # SEE ALSO # ps(1), etags(1), ctags(1), global(1), tsleep(9), glimpse(1) # # NOTES # wtags was designed under FreeBSD. Any
Re: Missing files/directories
Hi Brian, It was a good thought, but we can't put the blame on bad hardware. These tests were done on the RELENG_3 system cvsup'd as of Feb 22 @ 20:00 EST. All tests were run internal to the same machine. So that I don't remain the only guy in the world to see these test results, Control files are included so you can test locally:-) ppp0 -direct on localhost is started by port 6671. I know (now) that setting up the test this way the ppp's were communicating via localhost rather than the tunnel, but this way was much cleaner as far as verifying exactly how close the results were to what I saw running the server under 2.2-stable. There were differences, but the main issues are demonstrated. You will recall our discussion about the server hanging around under 2.2-stable after the client is terminated? Required by the RFCs you said? Under RELENG_3 the server meekly goes away, which makes sense to me. Two tests were done. The first involved kill -KILL clientpid. The second was kill -TERM clientpid. In the first test, the server illegally removed the default route. In the second test, the server did the same - neither ppp actioned the second command in the linkdown scripts. I was surprised that the first test ended immediately - I thought the LQR packets would cause the server to terminate after 1 minute. Files: test1.netstat0 shows routing after boot test1.netstat1 shows routing after ppp -background testloop test1.psaxl show ps results for the executing processes. test1.netstat2 shows routing after killing the client. test1.tun0 ifconfig while active. test1.tun1 ifconfig while active. test2.netstat routing tables after terminating the client. Logs are supplied for both tests. I hope that this is very helpful to you. I really appreciate your efforts!! Cheers, Tom Hi, I don't claim to know a great deal about cache code etc, but I'm pretty sure that it's extremely unlikely that the file name has any chance of affecting the buffer cache. While NFS has its fair share of problems (with which Matt is dealing with admirably), I would think that the code that does the work there is equally unlikely to know anything about file names. Having said all that in as vague a way as possible, the reason I'm posting this is that you seem to be experiencing difficulties with ppp that are of a similar nature - that is, completely inexplicable and unseen by anyone else - disappearing default routes, ppp.linkdown not being processed, I'm beginning to suspect a hardware problem - perhaps with your disk controller or something. This wouldn't easily explain the default route problem, but may explain the failure to process ppp.linkdown Maybe you could try treating the other machine (your son's machine?) as the gateway, and see if things become more stable. If they do, the finger might be pointed more firmly at hardware. On the weekend I reported to hackers about problems experienced with 2.2-stable and RELENG-3 systems where I experienced files that disappeared from cache and Mail directories that disappeared. The RELENG-3 system had files affected with softupdates enabled. The 2.2-stable system had sub-directories missing from the same directories that I was writing to via nfsv2. By coincidence, I had cvsup'd and compiled new kernels and naturally made the assumption that there was causality there. Subsequently I have come to believe that the problem may have more to do with what I was doing, not changes to the code. For about 3-4 hours prior to noticing the problems, I had been repetitively editing dot files, then writing a kludge of dot files to the local system hard drive and to the nfs exported FS of the other computer, while occasionally checking mail on that computer. All files and directories missing were being updated for one reason or another by myself or by mail processes while I was doing this. It is speculation, but there is a good chance that there is a bug in the cache-handling code that causes problems with other files or directories being dropped from cache because of bad processing common to BOTH or ALL releases, when large numbers of dot files are being written. The dot files themselves did not disappear - other items to be written disappeared before their writes actually occurred. I know that this is a frustrating kind of message to receive, but I am not a developer not qualified to go into the code myself. Also no logs or hard output are available - files/directories simply disappeared without any error messages. I just did a scan of the entire /usr/src/sys tree for \\\.\ and \'\\.\' to see what code sections might be affected - mostly cache-handling. In quantity, not bad, really. Others have apparently reported missing files to do with nfs I believe. THis might or might not be a related problem. I guess that I am asking someone who is
RE: Staroffice 5.01?
I was unable to install it. It complains about not being able to copy 'setup.zip' to '/tmp/sv001.tmp' and keeps bombing out. This is after pointing LD_LIBRARY_PATH to a place with glibc2, etc. Did you have any trouble installing? Al On Wed, 24 Feb 1999, Daniel O'Connor wrote: On 24-Feb-99 Alok K. Dhir wrote: Has anyone gotten SO501 to run on -current? I have and its quite good, but it hangs occasionally.. The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..) What problems are you having? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: ad...@worldbank.org L_ The World Bank Group Washington, DC \/ | Unix _is_ user friendly - it just chooses friends selectively... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Missing files/directories
I forgot to mention to those following this thread, files and directories were definitely removed from /root that were not scheduled for writing under ANY circumstances, on the RELENG_3 machine. In fact, on the RELENG_3 machine all files and directories (except ALL the .x files) were removed from /root. I put a union on the /home directory nfsv2 exported from the 2.2-stable machine, which has been rock-solid ever since. THe problems that system had were when I was writing to its file system from RELENG_3. I am still very suspicious of those dot files even if I am the only one. All files and directories missing are ONLY missing from the directories to which I was writing the dot files! Cheers, Tom To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Staroffice 5.01?
On 25-Feb-99 Alok K. Dhir wrote: I was unable to install it. It complains about not being able to copy 'setup.zip' to '/tmp/sv001.tmp' and keeps bombing out. This is after pointing LD_LIBRARY_PATH to a place with glibc2, etc. Did you have any trouble installing? What I did was the following... Make this directory /usr/local/Office50/lib/ Unpack the glibc libs in there unzip -L the setup.zip file in the inst directory. cd into the inst directory and run setup --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE CDROM not found with PIIX4 chipset, -current kernel
I've been having problems with an IDE controller on my motherboard. I can't seem to be able to get it to recognize a CDROM drive (it's the only device plugged on the second IDE controller). The kernel seems to timeout on that second controller during the probe phase. Maybe that's one of the infamous PIIX 4 bugs... The machine is a Dell Optiplex. That's one of the infamous FreeBSD bugs :-). The wd probe has never really supported cdrom drives. It works best when there is an ordinary drive on the master and a cdrom drive on the slave. Then it essentially doesn't see the slave, and control passes to the atapi probe which does support cdrom drives. It works worst with a cdrom master and no slave. Then it at first sees the master as a broken ordinary drive and times out attempting to reset it. Then it does a quick subprobe for a cdrom drive, and if it sees a cdrom drive then it doesn't see an ordinary drive and control passes to the atapi probe ... The subprobe apparently doesn't work for new drives. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Staroffice 5.01?
Alok K. Dhir wrote: Has anyone gotten SO501 to run on -current? Yes, it runs fairly well out of the box, without the registration problems of the previous version. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
please don't check mail for root logins
I have a suggestion for the FreeBSD maintainers. In /bin/login, please don't check for mail when the user is root. And in the case that the mail filesystem is mounted via NFS from a non-responding server, it hangs root logins. Root logins on machine A should never ever ever require machine B to be up. Rahul P.S. Patch on request, but it's too trivial to submit as one. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: please don't check mail for root logins
:I have a suggestion for the FreeBSD maintainers. : :In /bin/login, please don't check for mail when the user is root. And :in the case that the mail filesystem is mounted via NFS from a :non-responding server, it hangs root logins. : :Root logins on machine A should never ever ever require machine B :to be up. : :Rahul You should be able to fix this trivially in /etc/login.conf. Look at the standard: entry's setenv for MAIL and do something similar for root's, pointing MAIL somewhere else. I haven't tried this myself, but it should work. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
