Re: problems with perl
>> The perl upgrade seems to be having problems. I got this twice >> towday making buildworld from 4.5: > Please test the enclosed patch. That patch allows perl to compile. Unfortunatly, I'm still unable to make a 5.0 kernel from 4.5, so I cant test it. cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes - Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions - ansi -g -nostdinc -I- -I. -I/5.0/usr/src/sys -I/5.0/usr/src/sys/dev -I/5.0/usr /src/sys/contrib/dev/acpica -I/5.0/usr/src/sys/contrib/ipfilter -I/5.0/usr/src/ sys/../include -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -mpreferred-stack-boundary=2 -Werror /5.0/usr/src/sys/dev/amr/amr.c cc1: warnings being treated as errors /5.0/usr/src/sys/dev/amr/amr.c: In function `amr_bio_command': /5.0/usr/src/sys/dev/amr/amr.c:817: warning: unsigned int format, different typ e arg (arg 3) *** Error code 1 Stop in /scratch/obj/5.0/usr/src/sys/GENERIC. *** Error code 1 Stop in /5.0/usr/src. *** Error code 1 Stop in /5.0/usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problems with perl
The perl upgrade seems to be having problems. I got this twice towday making buildworld from 4.5: thanx, brad [...] cc -O -pipe -I/usr/obj/5.0/usr/src/gnu/usr.bin/perl/miniperl -I/5.0/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -DPERL_EXTERNAL_GLOB -DPERL_CORE -DAPPLLIB_EXP=\"/usr/libdata/perl/BSDPAN\" -L/usr/obj/5.0/usr/src/gnu/usr.bin/perl/miniperl/../libperl -static -o miniperl miniperlmain.o perl.o gv.o toke.o perly.o op.o regcomp.o dump.o util.o mg.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o universal.o xsutils.o globals.o perlio.o -lm -lcrypt -lutil pp_sys.o: In function `Perl_pp_fteread': pp_sys.o(.text+0x5f57): undefined reference to `eaccess' pp_sys.o: In function `Perl_pp_ftewrite': pp_sys.o(.text+0x6023): undefined reference to `eaccess' pp_sys.o: In function `Perl_pp_fteexec': pp_sys.o(.text+0x60ef): undefined reference to `eaccess' *** Error code 1 Stop in /5.0/usr/src/gnu/usr.bin/perl/miniperl. *** Error code 1 Stop in /5.0/usr/src. *** Error code 1 Stop in /5.0/usr/src. *** Error code 1 Stop in /5.0/usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.5->5.0 kldxref:No such file or directory
* Crist J. Clark ([EMAIL PROTECTED]) wrote: > > *** Error code 1 (ignored) > >^ > > Note. > > > Since there is no kldxref in 4.5, this should probably included in > > the bootstrap process somehow. > > A known issue. The install process deliberately ignores this as a > non-fatal error. Ok, but comming as it does at the _end_ of the kernel install process it's very deceptive. I think a note, or an "if [ -x ..." would be a good idea. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.5->5.0 kldxref:No such file or directory
"make DESTDIR=/5.0 world kernel" encountered the following problem: [...] -- >>> Kernel build for GENERIC completed on Tue Mar 12 20:26:10 GMT 2002 -- [...] -- >>> Kernel build for GENERIC completed on Tue Mar 12 20:26:10 GMT 2002 -- cd /usr/obj/5.0/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i3 [...] ===> xe install -c -o root -g wheel -m 555 if_xe.ko /5.0/boot/kernel/ kldxref /5.0/boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) Since there is no kldxref in 4.5, this should probably included in the bootstrap process somehow. As an asside, I've noticed in the past when upgrading from 4.0 to 5.0, I've had to forcebly reinstall the loader. I dont know why, but the loader shiped with (at least) 4.4 doesnt seem to like loading 5.0 kernel bits. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/lib/libcrypt crypt-md5.c crypt.c crypt.h misc.c src/secure/lib/libcrypt blowfish.c blowfish.h crypt-blowfish.c crypt-des.c
> This comment is false. On my -CURRENT system with > this commit in place 'passwd' and 'login'/'su' commands > loops forever computing MD5 password. > After reverting crypt-md5.c to rev. 1.8 all thouse > commands work as always. Same thing happened to me, but it appears to have been fixed. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fxp SCB timeout problems [FIX]
> From my perspective, negative functionality is being lost. There is a > nice comment in the source code explaining what it is... > * Enable workarounds for certain chip revision deficiencies. > * > * Systems based on the ICH2/ICH2-M chip from Intel have a defect > * where the chip can cause a PCI protocol violation if it receives > * a CU_RESUME command when it is entering the IDLE state. The > * workaround is to disable Dynamic Standby Mode, so the chip never > * deasserts CLKRUN#, and always remains in an active state. > * > * See Intel 82801BA/82801BAM Specification Update, Errata #30. Will the card be able to function in suspend mode and do Wake-on-LAN correctly after this? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown PNP hardware
> Then go look them up. I'm not about to stuff the entire PnP device > database into the kernel just to satisfy your curiosity. 8( I was going to ask where, but I see they are in /usr/src/sys/boot/common/pnpdata. thanx, brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown PNP hardware
>: unknown: can't assign resources >: unknown: can't assign resources >: unknown: can't assign resources >: unknown: can't assign resources >: unknown: can't assign resources >: unknown: can't assign resources > Shouldn't we just suppress the message? It just confuses users. I would be satisfied just knowing what devices these messages correspond to. I suspect this the sentiment of the original poster as well. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: is 'suspend' broken in CURRENT?
> I have sony vaio z505hs. I have latest cvs-tree. suspend worked > 1-2 weeks ago but now when I want to resume from suspend-mode I > see the same screen I saw before suspend but keyboard doesn't work > and harddisk doesn't spin. FYI: I see this on my z505(ls??) running 4.3-STABLE from a few months ago. Not only does the keyboard/mouse freeze, the whole machine is generally locked up and unpingable. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
Brad <[EMAIL PROTECTED]> writes: > Has anyone attempted to make a loadable module out of IPSEC yet? Kris <[EMAIL PROTECTED]> responds: > I doubt it would be possible: it has hooks all through the network > code. What about makeing the individual encription and authentication schemes loadable modules? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPSEC/IPSEC_ESP module(s)
> Have we come to a decision on when we're going to either drop floppy > support or consider a different version of GENERIC for the CDROM > installation? Along the lines of droping floppy support: I just managed to setup a DHCP/TFTP/NFS diskless boot server that boots the floppy install images. Unfortunatly, it did require nfs. So even if floppy install is discontinued, it would be very nice to have support for installing from PXE. If anyone wants details let me know off-line. brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPSEC/IPSEC_ESP module(s)
Has anyone attempted to make a loadable module out of IPSEC yet? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xl0 lock order reversal
My apologies for not looking into this more throughly before posting to the list, but I thought someone might be interested. The first time I run tcpdump after a reboot, I get this kernel message: xl0: promiscuous mode enabled lock order reversal 1st 0xc04f3fa0 bpf global lock @ ../../../net/bpf.c:365 2nd 0xc16beb9c xl0 @ ../../../pci/if_xl.c:2824 I'm running a mostly generic 5.0 kernel built from sources down loaded Jul 30 03:36 with a 1GHz Athlon system; the only difference from the GENERIC config is: device acpica options ACPI_DEBUG profile 1 On a related note, I've noticed that when doing compiles and other high load activities, my systems spends allot of time (nearly 50%) in witness_lock(), which not only has a nested loop in it, but also seems to do spin locking. Are spinlock's really a good idea on a single processor system (which is what I have)? thanx, brad ACPI debug layer 0x0 debug level 0x0 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 #0: Sat Jul 28 13:10:18 MDT 2001 [EMAIL PROTECTED]:/scratch/5.0/src/sys/i386/compile/ACPI Calibrating clock(s) ... TSC clock: 1010038034 Hz, i8254 clock: 1193295 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 CPU: AMD Athlon(tm) Processor (1009.95-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc044<,AMIE,DSP,3DNow!> Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 268369920 (262080K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00607000 - 0x0ffe7fff, 262017024 bytes (63969 pages) avail memory = 255184896 (249204K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fdb40 bios32: Entry = 0xfdb50 (c00fdb50) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xdb71 pnpbios: Found PnP BIOS data at 0xc00f7710 pnpbios: Entry = f:6604 Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc05e1000. Preloaded elf module "snd_sb16.ko" at 0xc05e109c. Preloaded elf module "snd_sbc.ko" at 0xc05e113c. Preloaded elf module "snd_pcm.ko" at 0xc05e11dc. Preloaded elf module "bktr.ko" at 0xc05e127c. Preloaded elf module "bktr_mem.ko" at 0xc05e1318. Preloaded elf module "joy.ko" at 0xc05e13b8. bktr_mem: memory holder loaded null: random: mem: Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Math emulator present apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. acpi0: sleep button is handled as a fixed feature programming model. Timecounter "ACPI" frequency 3579545 Hz acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: on acpi0 pci0: physical bus=0 map[10]: type 3, range 32, base e800, size 26, enabled map[14]: type 3, range 32, base eedfe000, size 12, enabled map[18]: type 4, range 32, base dc00, size 2, port disabled found-> vendor=0x1022, dev=0x7006, revid=0x25 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 found-> vendor=0x1022, dev=0x7007, revid=0x01 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 found-> vendor=0x1022, dev=0x7408, revid=0x01 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=0x1022, dev=0x7409, revid=0x07 bus=0, slot=7, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 found-> vendor=0x1022, dev=0x740b, revid=0x03 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 map[10]: type 1, range 32, base efffe000, size 12, enabled found-> vendor=0x1022, dev=0x740c, revid=0x06 bus=0, slot=7, func=4 class=0c-03-10, hdrtype=0x00, mfdev=0 intpin=d, irq=7 map[10]: type 3, range 32, base eedff000, size 12, enabled found-> vendor=0x109e, dev=0x0350, revid=0x12 bus=0, slot=10, func=0 class=04-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=9 map[10]: type 4, range 32, base de00, size 7, enabled map[14]: type 1, range 32, base ef80, size 7, enabled found-> vendor=0x10b7, dev=0x9055, revid=0x24 bus=0, slot=12, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10
Re: catching abrupt time changes
> The usual platform-independent way to do this is to have a thread > that monitors the system clock. It wakes up every, say, 2 seconds > and makes sure the clock is where it expects it. If the clock isn't > what it expects, it does whatever you need to do in that case. > I fear, however, that this is yet another technique that won't work > properly with user-space threading. I fear that the clock thread's > sleep function will be virtualize into something that won't sleep > for the right amount of time if the system clock is changed. Does > anyone know which sleep function to use to avoid this - or if there > is one? Unfortunately, this is exactly what I'm trying fix. I want cron to _stop_ waking up every 60 seconds. If cron has nothing to do for 5 days, it should sleep for 5 days. And if everything on the system is sleeping for 5 days and the kernel knows this, then mabey we can hibernate the system for 5 days. I know theres allot more to this than just cron (network stuff etc). brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
catching abrupt time changes
Suppose I'm a (root) process: I have an appointment in exactly one hour. I call select() and specify a timeout of 3600 seconds, trusting that the system will wake me up just in time. But unbeknownst to me someone sets the clock back 10 minutes while I'm asleep (using settimeofday(), not adjtime()). When select() returns I find that I'm 10 minutes late! My question is: How can I arrange to be notified when someone and makes a corse change to the system clock? One idea I had was to generate a klog message for each call to settimeofday(). This would put the information in syslog, and I could simply add /dev/klog to the list of file descriptors in it's select() call (there will be lots of false alarms, but that's probably not a problem for this application). Another idea was to add a new minor device to klog that just logs calls to settimeofday(). Could this be generalized? Alternately such a device file could be put in /proc (smells like a Linux solution). Or perhaps I could select() for "read" or "err" conditions on /kern/time (from kernfs). Any thoughts? brad P.S. The application in question is a new schedular for cron/at that can sleep between jobs. This would seem to be a good first step toward better laptop power management. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
user connection request data w/ recvmsg(2)/getsockopt(2)
The following jucy tidbit has been hiding in the accept(2) man page for several years, but has apparently never been implemented. One can obtain user connection request data without confirming the con- nection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non- zero msg_controllen, or by issuing a getsockopt(2) request. Similarly, one can provide user connection rejection information by issuing a sendmsg(2) call with providing only the control information, or by call- ing setsockopt(2). There is no mention of this feature in the man pages for getsockopt(2), recvmsg(2) or sendmsg(2). Rather than correct the accept(2), I'd really like to see this feature implemented in the kernel, and incorporated into tcp wrapper. I think it would really help limit limit the effectivness of portscanning. Who's idea was this origionally and do they have thoughts on why it should or should not be implemented? Any gottchas? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp -d dir patch for review (or 'xargs'?)
> Try: > > echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo > > Now consider what would happen with the above suggested construct with > a very long file list. > > I don't see a problem with adding an option to cp to treat the first > argument as the target instead of the last argument. It's a simple > solution, the code change is simple, and it produces the exact desired > result. What's the problem? Unfortunatly, cp is not alone in needing this feature. I think a more sensable approach would be to add an "append args" flag to xargs. For example "--", which could be used like so: xargs cp -- destdir <
Re: BTSpeedup evaluation copy
Could we perhaps "close" the freebsd-current list? brad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message