Re: building -current on -stable broken?
On Sun, Apr 28, 2002 at 10:27:10PM -0600, Kenneth D. Merry wrote: I'm trying to build -current from today (4/28/2002) on a -stable box with a kernel/world from April 25th. It blows up in xlint: == cc -O -pipe -I. -I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1 -I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../arch/i386 -I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../common-D__FBSDID=__RCSID -static -o lint1 cgram.o scan.o mem1.o mem.o err.o main1.o decl.o tree.o func.o init.o emit.o emit1.o inittyp.o -ll -lm cgram.o: In function `yyparse': cgram.o(.text+0x10b8): undefined reference to `xcalloc' cgram.o(.text+0x10f0): undefined reference to `xcalloc' scan.o: In function `ccon': scan.o(.text+0x23f7): undefined reference to `xcalloc' func.o: In function `label': func.o(.text+0x6a8): undefined reference to `xcalloc' init.o: In function `prepinit': init.o(.text+0x78): undefined reference to `xcalloc' init.o(.text+0x214): more undefined references to `xcalloc' follow emit.o: In function `outopen': emit.o(.text+0x4f): undefined reference to `xmalloc' emit.o: In function `outxbuf': emit.o(.text+0xd4): undefined reference to `xrealloc' emit1.o: In function `ttos': emit1.o(.text+0x2d5): undefined reference to `xmalloc' *** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1. *** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src. *** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src. *** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src. == Am I doing something wrong here or is building -current on -stable broken? Seems to work OK here; xcalloc() and xmalloc() are defined in mem.c. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37842/pgp0.pgp Description: PGP signature
Re: 3com 3cxfe575bt
In message: [EMAIL PROTECTED] David Hill [EMAIL PROTECTED] writes: : Does -CURRENT currently support the 3com 3cxfe575bt cardbus pc card? Yes. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[no subject]
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Je considère cela comme.
Warning Unable to process data: multipart/mixed;boundary==_NextPart_000_00DD_016503AE.1403AE10
new french calendar(1) breaks installword
The commit was done abot 11 hours ago, but it was incomplete: the directory calendars/fr_FR.ISO_8859-1 does not exist. Here is the error message: === usr.bin/calendar install -c -o root -g wheel -m 444 /usr/src/usr.bin/calendar/calendars/calendar.* /usr/share/calendar install -c -o root -g wheel -m 444 /usr/src/usr.bin/calendar/calendars/de_DE.ISO8859-1/calendar.* /usr/share/calendar/de_DE.ISO8859-1; install -c -o root -g wheel -m 444 /usr/src/usr.bin/calendar/calendars/fr_FR.ISO_8859-1/calendar.* /usr/share/calendar/fr_FR.ISO_8859-1; install: /usr/src/usr.bin/calendar/calendars/fr_FR.ISO_8859-1/calendar.*: No such file or directory *** Error code 71 Just FYI. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: new french calendar(1) breaks installword
The commit was done abot 11 hours ago, but it was incomplete: the directory calendars/fr_FR.ISO_8859-1 does not exist. Here is the error message: Sorry about that - I think I've fixed the problem now. (Two breaks in one day - that will teach me to commit stuff late at night!) David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: page fault in _mtx_lock_flags
On 29-Apr-2002 Robert Watson wrote: If I apply the attached diff to the kern_malloc.c, backing out a portion of kern_malloc.c:1.99, the rate of panics plummets. Previously, I could have a box panic within five minutes of getting the crash boxes spinning. Now I've been going for about 40 minutes without any perceived failures (i.e., no panics). I have no idea why this fixes the problem, but David Wolfskill pointed me at that particular revision as being a source of related problems for him. I'm going to leave the boxes running overnight and see what I bump into. It would be nice to know if this is masking the problem, or fixing the problem, and if so, why. You have memory corruption it looks like. I think the patch adds new buckets of larger sizes. Perhaps the problem is a bug in uma where someone allocates something bigger than the largest bucket, and the chunk they get back is only the size of an item in the largest bucket, thus when the code writes to the end of the structure it is overwriting other memory. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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: xdm broken on current
On 27-Apr-2002 Dag-Erling Smorgrav wrote: John Baldwin [EMAIL PROTECTED] writes: Please back out revision 1.3 of src/etc/pam.d/xdm since it breaks xdm. xdm core dumps with a signal 6 if there is no session management configured for it in PAM. Obviously this commmit wasn't actually tested with xdm (at least not on X 4). Yes, it was. Please show me the output of 'ldd /usr/X11R6/bin/xdm'. ldd `which xdm` /usr/X11R6/bin/xdm: libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x2807e000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x2808c000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x280a1000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x280ec000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x280f5000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x2810b000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x28119000) librpcsvc.so.2 = /usr/lib/librpcsvc.so.2 (0x281f5000) libpam.so.1 = /usr/lib/libpam.so.1 (0x281fd000) libcrypt.so.2 = /usr/lib/libcrypt.so.2 (0x28207000) libutil.so.3 = /usr/lib/libutil.so.3 (0x2822) libc.so.5 = /usr/lib/libc.so.5 (0x28229000) libXThrStub.so.6 = /usr/X11R6/lib/libXThrStub.so.6 (0x282db000) It may be that my version of X is too old (a week or so before 4.2.0). -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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: xdm broken on current
John Baldwin [EMAIL PROTECTED] writes: ldd `which xdm` /usr/X11R6/bin/xdm: libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x2807e000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x2808c000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x280a1000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x280ec000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x280f5000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x2810b000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x28119000) librpcsvc.so.2 = /usr/lib/librpcsvc.so.2 (0x281f5000) libpam.so.1 = /usr/lib/libpam.so.1 (0x281fd000) libcrypt.so.2 = /usr/lib/libcrypt.so.2 (0x28207000) libutil.so.3 = /usr/lib/libutil.so.3 (0x2822) libc.so.5 = /usr/lib/libc.so.5 (0x28229000) libXThrStub.so.6 = /usr/X11R6/lib/libXThrStub.so.6 (0x282db000) It may be that my version of X is too old (a week or so before 4.2.0). It's linked against Linux-PAM (libpam.so.1 rather than libpam.so.2). A bug (misfeature?) in xdm's conversation function makes it crash when it tries to run pam_lastlog. Changing pam_lastlog to pam_permit in /etc/pam.d/other, or adding no_warn to the pam_lastlog entry, should hide the bug. Linux-PAM uses the session chain from the other policy because the xdm policy does not have one, while OpenPAM would only use the other policy if there was no xdm policy at all. The former is traditional, but surprising if you're not familiar with PAM. I have patches that make OpenPAM do this, but I'm not entirely certain if tradition should win over simplicity in this case. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: page fault in _mtx_lock_flags
On Mon, 29 Apr 2002, John Baldwin wrote: On 29-Apr-2002 Robert Watson wrote: If I apply the attached diff to the kern_malloc.c, backing out a portion of kern_malloc.c:1.99, the rate of panics plummets. Previously, I could have a box panic within five minutes of getting the crash boxes spinning. Now I've been going for about 40 minutes without any perceived failures (i.e., no panics). I have no idea why this fixes the problem, but David Wolfskill pointed me at that particular revision as being a source of related problems for him. I'm going to leave the boxes running overnight and see what I bump into. It would be nice to know if this is masking the problem, or fixing the problem, and if so, why. You have memory corruption it looks like. I think the patch adds new buckets of larger sizes. Perhaps the problem is a bug in uma where someone allocates something bigger than the largest bucket, and the chunk they get back is only the size of an item in the largest bucket, thus when the code writes to the end of the structure it is overwriting other memory. That was what I was theorizing when I made the change, but I haven't really had much time lately to read the UMA code, so it's greek to me. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
4.x boxes can now build 5.0 releases!
With these two fixes (now committed), my 4.5-STABLE dual-CPU i386 SMP box has just successfully built 5.0-CURRENT release: : # pwd : /data/ru/src-4 : # cat mkrel.sh : #!/bin/sh : exec mkrel.log 21 : export MAKEOBJDIRPREFIX=/data/ru/obj : cd release || exit 1 : make -f ../../src-5/release/Makefile \ : CHROOTDIR=/data/ru/R \ : CVSROOT=/home/ncvs \ : WORLD_FLAGS=-j8 KERNEL_FLAGS=-j8 \ : -DNODOC -DNOPORTS -DRELEASENOUPDATE \ : release \ : LOCAL_PATCHES=/home/ru/p : # grep '^ make release ' mkrel.log : make release started on Mon Apr 29 14:08:08 GMT 2002 : make release finished on Mon Apr 29 15:12:12 GMT 2002 Note that we need to -f /path/to/-CURRENT/usr/src/release/Makefile for now. On Mon, Apr 29, 2002 at 08:22:01AM -0700, Ruslan Ermilov wrote: ru 2002/04/29 08:22:01 PDT Modified files: .Makefile Makefile.inc1 Log: Parallel make release fixes. Revision ChangesPath 1.252 +13 -1 src/Makefile 1.262 +0 -7 src/Makefile.inc1 On Mon, Apr 29, 2002 at 08:26:37AM -0700, Ruslan Ermilov wrote: ru 2002/04/29 08:26:37 PDT Modified files: release Makefile Log: Some components of the crunched binaries may use build-tools that are to be run on the building host. (Currently, bin/sh and usr.sbin/sysinstall use them.) Make sure we build them in the correct environment, like we do it in the buildworld. Revision ChangesPath 1.675 +15 -12src/release/Makefile -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37852/pgp0.pgp Description: PGP signature
Re: xdm broken on current
On 29-Apr-2002 Dag-Erling Smorgrav wrote: John Baldwin [EMAIL PROTECTED] writes: ldd `which xdm` /usr/X11R6/bin/xdm: libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x2807e000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x2808c000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x280a1000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x280ec000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x280f5000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x2810b000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x28119000) librpcsvc.so.2 = /usr/lib/librpcsvc.so.2 (0x281f5000) libpam.so.1 = /usr/lib/libpam.so.1 (0x281fd000) libcrypt.so.2 = /usr/lib/libcrypt.so.2 (0x28207000) libutil.so.3 = /usr/lib/libutil.so.3 (0x2822) libc.so.5 = /usr/lib/libc.so.5 (0x28229000) libXThrStub.so.6 = /usr/X11R6/lib/libXThrStub.so.6 (0x282db000) It may be that my version of X is too old (a week or so before 4.2.0). It's linked against Linux-PAM (libpam.so.1 rather than libpam.so.2). A bug (misfeature?) in xdm's conversation function makes it crash when it tries to run pam_lastlog. Changing pam_lastlog to pam_permit in /etc/pam.d/other, or adding no_warn to the pam_lastlog entry, should hide the bug. Ah, so the bug is my binary is too old and is linked against the wrong PAM. Ok, my bad then. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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: xdm broken on current
John Baldwin [EMAIL PROTECTED] writes: Ah, so the bug is my binary is too old and is linked against the wrong PAM. Ok, my bad then. Well, yes and no. There is a bug in xdm which is exposed by the combination of Linux-PAM and FreeBSD's stock PAM configuration. A slightly different configuration would not trigger it, nor would the current version of OpenPAM. I'd say the blame is evenly spread. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfilter not broken for me
On Sat, Apr 27, 2002 at 04:01:28PM +1000, Darren Reed wrote: In some email I received from Doug Barton, sie wrote: On Fri, 26 Apr 2002, Ruslan Ermilov wrote: =20 I tested this on i386 only with 2 days old -CURRENT (today's is broken due to the import of latest IPFilter suite) =20 I updated to the latest and greatest last night around midnight and built/installed -current just fine. What about the ipfilter import = is broken, and have you let Darren know? I haven't seen anything on the li= sts about it... =20 I have not received any email about it. I tested building all the ipfilt= er binaries and kernel after the import and came up clean. if ref5 was a bit quicker =20 That was probably a local problem on one of the Brian's fast machines where I initially attempted to finally test my patch (unsynched cvsup update?). Sorry for the false alarm, I can't check it right now anyway. Yes... I've had periods where the compiler drops cores all over the place, and other periods where things work fine. It's on a P4-1.7Ghz and has behaved like this since about last August. The only variable is the kernel - some kernels work and some don't. I've spent many 10s of hours trying to track it down, and I still have no idea what causes it - except that some kernels ``just work'' and some don't. Maybe it depends on the humidity in the room when a kernel is built or something - and I'm only half joking here ! FWIW ru, /boot/kernel/kernel seems ok now. /boot/kernel.sig/kernel isn't. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: page fault in _mtx_lock_flags
John Baldwin [EMAIL PROTECTED] writes: On 28-Apr-2002 Robert Watson wrote: db trace _mtx_lock_flags(79747473,0,c03cb862,e3) at _mtx_lock_flags+0x42 Same here. See the first arg which is supposed to be a mutex pointer. ytts stty, actually, since the i386 is little-endian. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfilter not broken for me
On Mon, Apr 29, 2002 at 17:45:05 +0100, Brian Somers wrote: On Sat, Apr 27, 2002 at 04:01:28PM +1000, Darren Reed wrote: In some email I received from Doug Barton, sie wrote: On Fri, 26 Apr 2002, Ruslan Ermilov wrote: =20 I tested this on i386 only with 2 days old -CURRENT (today's is broken due to the import of latest IPFilter suite) =20 I updated to the latest and greatest last night around midnight and built/installed -current just fine. What about the ipfilter import = is broken, and have you let Darren know? I haven't seen anything on the li= sts about it... =20 I have not received any email about it. I tested building all the ipfilt= er binaries and kernel after the import and came up clean. if ref5 was a bit quicker =20 That was probably a local problem on one of the Brian's fast machines where I initially attempted to finally test my patch (unsynched cvsup update?). Sorry for the false alarm, I can't check it right now anyway. Yes... I've had periods where the compiler drops cores all over the place, and other periods where things work fine. It's on a P4-1.7Ghz and has behaved like this since about last August. The only variable is the kernel - some kernels work and some don't. I've spent many 10s of hours trying to track it down, and I still have no idea what causes it - except that some kernels ``just work'' and some don't. Maybe it depends on the humidity in the room when a kernel is built or something - and I'm only half joking here ! FWIW ru, /boot/kernel/kernel seems ok now. /boot/kernel.sig/kernel isn't. I discovered the same problem here for a P4-1.7Ghz with -stable. First thing I discovered: this only happens if you have -pipe in your CFLAGS in /etc/make.conf. It seems something with pipe handling is broken on these fast machines, which makes cc fail. Currently I'm trying to figure out which commit brought that in. Probabilty is high that it has to do with ipfilter, but I'm not quite sure. Definitively it is not a problem local to Brian. Best regards Udo Schweigert -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
3Com 3c905C-TX
sorry for the cross posting, but this is true for both, stable and current. the onboard ethernet (the motherboard is a tyan tiger dual MPX) xl0: 3Com 3c905C-TX Fast Etherlink XL port 0x3000-0x307f mem 0xfa001000-0xfa00107f irq 5 at device 8.0 on pci2 at 100baseTX full-duplex is slower than 10Mgb :-( it's not the cable/switch, because i can connect the same cable to another host, and it works as expected - fast. btw, the PXE is also extreamly slow - still looking for a flash upgrade. thanks, danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3Com 3c905C-TX
On Mon, 29 Apr 2002 20:08:02 +0300 Danny Braniss [EMAIL PROTECTED] wrote: xl0: 3Com 3c905C-TX Fast Etherlink XL port 0x3000-0x307f mem 0xfa001000-0xfa00107f irq 5 at device 8.0 on pci2 at 100baseTX full-duplex is slower than 10Mgb :-( I recently had a similar problem. My switch (Netgear FS105) needs the adaptor to *announce* itself as full duplex. Try turning OFF full-duplex in your ifconfig and see if there is a speed-up. -- Cogeco ergo sum msg37860/pgp0.pgp Description: PGP signature
Re: xdm broken on current
Is there any chance that this can be fixed in such a way that 3rd party binaries, like the xdm which comes with X as distributed by xfree86.org will work OOB? Breaking binary compat will be a fairly big obstacle for adoption of 5.x we have a hard enough time getting vendors to support us as it is. Doug On 29 Apr 2002, Dag-Erling Smorgrav wrote: John Baldwin [EMAIL PROTECTED] writes: Ah, so the bug is my binary is too old and is linked against the wrong PAM. Ok, my bad then. Well, yes and no. There is a bug in xdm which is exposed by the combination of Linux-PAM and FreeBSD's stock PAM configuration. A slightly different configuration would not trigger it, nor would the current version of OpenPAM. I'd say the blame is evenly spread. DES -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum out of commission?
In message [EMAIL PROTECTED], Greg 'groggy' Lehey w rites: This is a non-GEOM kernel - GEOM wouldn't even let me disklabel the drives. That doesn't surprise me. You might ask phk how he proposes to address that issue. This is ongoing work in GEOM. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: xdm broken on current
Doug Barton [EMAIL PROTECTED] writes: Is there any chance that this can be fixed in such a way that 3rd party binaries, like the xdm which comes with X as distributed by xfree86.org will work OOB? Yes, please see my last commit to etc/pam.d/other. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: xdm broken on current
On 30 Apr 2002, Dag-Erling Smorgrav wrote: Doug Barton [EMAIL PROTECTED] writes: Is there any chance that this can be fixed in such a way that 3rd party binaries, like the xdm which comes with X as distributed by xfree86.org will work OOB? Yes, please see my last commit to etc/pam.d/other. I saw that actually... but (not coredumping) != (lets users log in). :) Should I update and try again? -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
