Re: build broken by usbdivar.h 1.40
--On Tuesday, July 15, 2003 22:31:38 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: === netgraph/bluetooth/ubt cc -O -pipe -mcpu=pentiumpro -g -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/blueto ot h/include -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/blueto ot h/drivers/ubt -Wall -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/blueto ot h/include -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/blueto ot h/drivers/ubt -I. -I@ -I@/dev -I@/../include -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c In file included from /usr/src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c:48: @/dev/usb/usbdivar.h:127: error: syntax error before bus_dma_tag_t *** Error code 1 After John-Mark's last commit I have a good kernel, for those keeping score. Thanks John-Mark for the quick fix(es). LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP page update
On Tue, Jul 15, 2003, Alp ATICI wrote: I was wondering whether the SMPng page at http://www.freebsd.org/smp is updated as those features are added. Because it seems like no feature update for long. For instance is the preemptible kernel going to be a part of 5.x series or going to be left to 6.x? The kernel has been preemptible for a long time. I don't know anything about the webpage. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Tue, Jul 15, 2003 at 10:16:01PM -0700, Kris Kennaway wrote: malloc, you say? I have build failures in XFree4-clients because rman coredumps and I have a backtrace full of free() frames... Coincidence? Some of the XFree86 utilities contain malloc bugs..rman in particular has been dumping core on certain ports for a couple of years. I tried to track it down once but couldn't find it. [cc [EMAIL PROTECTED] The attached patch fixes rman. The faulting case is \\\0. The '\0' was handled in the default case for escaped characters, which also incremented the pointer p beyond the terminating '\0'. Oh: this goes to devel/imake-4 of course. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] --- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003 +++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003 @@ -4104,6 +4104,9 @@ } } break; +case 0: + /* ignore */ + break; default: /* unknown escaped character */ sputchar(*p++); } ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on i386/i386
TB --- 2003-07-16 06:41:03 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-16 06:41:03 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-16 06:43:10 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. TB --- 2003-07-16 07:46:12 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Building an up-to-date make(1) Kernel build for GENERIC started on Wed Jul 16 07:46:12 GMT 2003 Kernel build for GENERIC completed on Wed Jul 16 08:00:37 GMT 2003 TB --- 2003-07-16 08:00:37 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2003-07-16 08:00:37 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT Building an up-to-date make(1) Kernel build for LINT started on Wed Jul 16 08:00:37 GMT 2003 [...] cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/usb/usb_mem.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/usb/usb_quirks.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/usb/usb_subr.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd
Re: Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Wed, Jul 16, 2003 at 12:43:37AM -0700, Marcel Moolenaar wrote: On Tue, Jul 15, 2003 at 10:16:01PM -0700, Kris Kennaway wrote: malloc, you say? I have build failures in XFree4-clients because rman coredumps and I have a backtrace full of free() frames... Coincidence? Some of the XFree86 utilities contain malloc bugs..rman in particular has been dumping core on certain ports for a couple of years. I tried to track it down once but couldn't find it. [cc [EMAIL PROTECTED] The attached patch fixes rman. The faulting case is \\\0. The '\0' was handled in the default case for escaped characters, which also incremented the pointer p beyond the terminating '\0'. Oh: this goes to devel/imake-4 of course. Hmm, I'm not sure this is the same bug I was seeing, because mine went away when I turned off malloc debugging. Kris pgp0.pgp Description: PGP signature
Re: Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Wed, Jul 16, 2003 at 12:43:37AM -0700, Marcel Moolenaar wrote: On Tue, Jul 15, 2003 at 10:16:01PM -0700, Kris Kennaway wrote: malloc, you say? I have build failures in XFree4-clients because rman coredumps and I have a backtrace full of free() frames... Coincidence? Some of the XFree86 utilities contain malloc bugs..rman in particular has been dumping core on certain ports for a couple of years. I tried to track it down once but couldn't find it. [cc [EMAIL PROTECTED] The attached patch fixes rman. The faulting case is \\\0. The '\0' was handled in the default case for escaped characters, which also incremented the pointer p beyond the terminating '\0'. Oh: this goes to devel/imake-4 of course. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] The print/gv port has patch-ad to work around another rman bug. This bug is only exposed by malloc debugging. Kris pgp0.pgp Description: PGP signature
Re: escalation stage 2 [was:RE: Big and ugly bug in 5.1-release]
On Wed, 16 Jul 2003, Harald Schmalzbauer wrote: Now after resetting the machine which was hung by sysinstall it claims that ad4 (one of two mirrored 30GB 2.5 disks was absent (see dmesg below) Now the controller warns me that one drive is bad (which in fact is definatley not) and allows me to select continue boot Did you try to replace that defective drive? That's what I do and after kernel probing the machine reboots with the folowing error (well, this takes some time to typewrite it from my monchrome screen): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code= supervisor read, page not present instruction pinter= 0x8:0xc014a0a6 stack pointer=0x10:0xcce65bd8 frame pointer=0x10:0xcce65c58 code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 4(g_down) trap number = 12 panic: page fault Then it reboots! Can you get a coredump and a backtrace? That would be very helpful in debugging. Now please give me a hint what to do. This is my brand new fileserver which collected all improtant data from the last decade and since it's brand new I didn't manage any backup. Funny, there's always an excuse why there are no backups. When testing the hardware (unplugging one drive while the machine was running) I had the same error but I thought that would never happen under normal circumstances. Well, if you did run tests and saw the errors, why did you think it wouldn't happen under normal circumstances? IMHO it would be better if you start over with a clean machine and two new disks. Sounds very much like you damaged the drive. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universität Wien http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on i386/pc98
TB --- 2003-07-16 08:08:16 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-07-16 08:08:16 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-16 08:13:30 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. TB --- 2003-07-16 09:12:37 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Building an up-to-date make(1) Kernel build for GENERIC started on Wed Jul 16 09:12:37 GMT 2003 Kernel build for GENERIC completed on Wed Jul 16 09:24:44 GMT 2003 TB --- 2003-07-16 09:24:44 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src/sys/pc98/conf TB --- /usr/bin/make -B LINT TB --- 2003-07-16 09:24:44 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=LINT Building an up-to-date make(1) Kernel build for LINT started on Wed Jul 16 09:24:45 GMT 2003 [...] cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/usb/usb_mem.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/usb/usb_quirks.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/usb/usb_subr.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd
Re: Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Wed, Jul 16, 2003 at 01:52:28AM -0700, Kris Kennaway wrote: On Wed, Jul 16, 2003 at 12:43:37AM -0700, Marcel Moolenaar wrote: On Tue, Jul 15, 2003 at 10:16:01PM -0700, Kris Kennaway wrote: malloc, you say? I have build failures in XFree4-clients because rman coredumps and I have a backtrace full of free() frames... Coincidence? Some of the XFree86 utilities contain malloc bugs..rman in particular has been dumping core on certain ports for a couple of years. I tried to track it down once but couldn't find it. [cc [EMAIL PROTECTED] The attached patch fixes rman. The faulting case is \\\0. The '\0' was handled in the default case for escaped characters, which also incremented the pointer p beyond the terminating '\0'. Oh: this goes to devel/imake-4 of course. Hmm, I'm not sure this is the same bug I was seeing, because mine went away when I turned off malloc debugging. Without malloc debugging the chance that the allocated memory has zeroes is large(r). Going past the terminating '\0' if it's followed by another one then hides the bug. With J, malloc() makes sure the allocated memory is not zero and thus exposes the bug. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Wed, Jul 16, 2003 at 01:59:44AM -0700, Kris Kennaway wrote: On Wed, Jul 16, 2003 at 12:43:37AM -0700, Marcel Moolenaar wrote: On Tue, Jul 15, 2003 at 10:16:01PM -0700, Kris Kennaway wrote: malloc, you say? I have build failures in XFree4-clients because rman coredumps and I have a backtrace full of free() frames... Coincidence? Some of the XFree86 utilities contain malloc bugs..rman in particular has been dumping core on certain ports for a couple of years. I tried to track it down once but couldn't find it. [cc [EMAIL PROTECTED] The attached patch fixes rman. The faulting case is \\\0. The '\0' was handled in the default case for escaped characters, which also incremented the pointer p beyond the terminating '\0'. Oh: this goes to devel/imake-4 of course. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] The print/gv port has patch-ad to work around another rman bug. This bug is only exposed by malloc debugging. Probably a different bug. The ^G is assumed to be a delimiter. The code will look for the closing delimiter, but will not find one. This too can result in runnaway pointers. I haven't analyzed the code that closely though. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Big and ugly bug in 5.1-release
Doug White wrote: On Wed, 16 Jul 2003, Harald Schmalzbauer wrote: I'm experimenting with 5.1-REL for some weeks and during that time I had some mysterious hangs which I didn't take serious because I modified /usr/src/sys/cam/scsi/scsi_da.c to support my CF-Card-Reader. But now I saw exactly the same problem on my brand new (and cosidered by hardware extremely different) fileserver. The machine freezes for about one minute and then reboots itself withut any error message. Sounds like its panicking and making a crashdump. Do you have console access? Can you perhaps compile with 'options DDB' and get on the console when it dies? If it worked right you should see the panic message and have a db prompt. I can do so on my workstation. More when my server is running again. It happens when I do a /stand/sysinstall or a sysctl -a If this is an i386 machine, I'd begin to suspect bad memory. Usually yes, but now exactly the same problem crashed my server so I'm quiet sure it's no hardware problem. -Harry -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: escalation stage 2 [was:RE: Big and ugly bug in 5.1-release]
Lukas Ertl wrote: On Wed, 16 Jul 2003, Harald Schmalzbauer wrote: Now after resetting the machine which was hung by sysinstall it claims that ad4 (one of two mirrored 30GB 2.5 disks was absent (see dmesg below) Now the controller warns me that one drive is bad (which in fact is definatley not) and allows me to select continue boot Did you try to replace that defective drive? If it was defect I'd replace it. But I'm very absolutely sure it isn't defective, it's a bug. That's what I do and after kernel probing the machine reboots with the folowing error (well, this takes some time to typewrite it from my monchrome screen): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code= supervisor read, page not present instruction pinter= 0x8:0xc014a0a6 stack pointer= 0x10:0xcce65bd8 frame pointer= 0x10:0xcce65c58 codesegment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 4(g_down) trap number = 12 panic: page fault Then it reboots! Can you get a coredump and a backtrace? That would be very helpful in debugging. Not on that machine since I can't install a new kernel. I can make a ddb kernel for finding out the initially crash but not for the consequences, named an inacessable RAID1 Now please give me a hint what to do. This is my brand new fileserver which collected all improtant data from the last decade and since it's brand new I didn't manage any backup. Funny, there's always an excuse why there are no backups. I really never had any backup when it was needed *grumpf* When testing the hardware (unplugging one drive while the machine was running) I had the same error but I thought that would never happen under normal circumstances. Well, if you did run tests and saw the errors, why did you think it wouldn't happen under normal circumstances? Because I accepted the risk that if one drive really fails I have to manually recover it, assuming I have a backup to be sure. But now it's definatly no hardware failure. IMHO it would be better if you start over with a clean machine and two new disks. Sounds very much like you damaged the drive. I'll now release the RAID1 and create a new one while duplicating data form ad6 with the controller's BIOS. I'm sure this will work but it's not the sense. The machine should boot with one drive detached! Perhaps Soren has an idea? Best regards, -Harry regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universität Wien http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
'Hard error reading fsbn' in 5.1 but not 5.0?
Just now, my 120GB western digital, immediately upon the mounting of all filesystems during startup, made a faint click, then my screen filled with errors of the form: ad6: hard error reading fsbn -# of -#--# error=10 That's not an exact quote, of course, since the messages scrolled by so fast I couldn't actually read parts of them. Those # signs are in place of large numbers (most were 12-18 digits). This was in 5.1-R, fresh install, in the first 15G of the disk, just after having booted into DOS to create some DOS partitions after the FreeBSD slice. I booted back into 5.0, and am presently writing across the entire disk with this command: fdisk -I /dev/ad6 dd if=/dev/zero of=/dev/ad6s1 bs=1m At more than 33 minutes into it at 24+MB/sec, there have been no such errors and the portion of the disk that was being mounted has already been covered by zeros. After dd completes/dies, I'm going to try to reproduce the error, but I figured I'd bring this up now in case I've tripped over something someone else already knows about. I did notice that when I used fdisk(8) to look at the partition table, the slice table showed the new DOS slice starting before the end of the FreeBSD slice. Assuming that was real overlap, and not harmless output screwiness as a result of using two very different fdisks, is it possible for such corruption to cause hard read errors? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS problem
I guess there is something wrong with exporting iso9660 CD's over NFS. I've added /cdrom -ro -mapall=root to /etc/exports, restarted mountd and after mounting the CD on Solaris 8. All the files are 0-sized, dates are set back to the epoch and directories are seen as files. Exporting ufs2 filesystems works as expected. Example listing looks like this: rohan:root ls -la total 5 dr-xr-xr-x 6 root root2048 Aug 28 2002 . dr-xr-xr-x 3 root root 3 Jul 16 12:42 .. -r-xr-xr-x 1 root root 0 Jan 1 1970 .install -r-xr-xr-x 1 root root 0 Jan 1 1970 .jvm -r-xr-xr-x 1 root root 0 Jan 1 1970 Copyright -r-xr-xr-x 1 root root 0 Jan 1 1970 autorun -r-xr-xr-x 1 root root 0 Jan 1 1970 autorun.inf -r-xr-xr-x 1 root root 0 Jan 1 1970 cd.info -r-xr-xr-x 1 root root 0 Jan 1 1970 image -r-xr-xr-x 1 root root 0 Jan 1 1970 installer -r-xr-xr-x 1 root root 0 Jan 1 1970 installing.pdf -r-xr-xr-x 1 root root 0 Jan 1 1970 release_notes.txt -r-xr-xr-x 1 root root 0 Jan 1 1970 rr_moved -r-xr-xr-x 1 root root 0 Jan 1 1970 setup.exe -r-xr-xr-x 1 root root 0 Jan 1 1970 volstart Any thoughts? I attach output file from tcpdump generated with: tcpdump -w /tmp/tcpdump-s-1500.out -s 1500 -ln host rohan and not port 22 /S tcpdump-s-1500.out Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fix for rman [was: Re: [-CURRENT tinderbox] ...]
On Wed, Jul 16, 2003 at 03:05:06AM -0700, Marcel Moolenaar wrote: Hmm, I'm not sure this is the same bug I was seeing, because mine went away when I turned off malloc debugging. Without malloc debugging the chance that the allocated memory has zeroes is large(r). Going past the terminating '\0' if it's followed by another one then hides the bug. With J, malloc() makes sure the allocated memory is not zero and thus exposes the bug. Sounds plausible. Good catch! Kris pgp0.pgp Description: PGP signature
Re: 'Hard error reading fsbn' in 5.1 but not 5.0?
Darren Pilgrim wrote: Just now, my 120GB western digital, immediately upon the mounting of all filesystems during startup, made a faint click, then my screen filled with errors of the form: ad6: hard error reading fsbn -# of -#--# error=10 That's not an exact quote, of course, since the messages scrolled by so fast I couldn't actually read parts of them. Those # signs are in place of large numbers (most were 12-18 digits). This was in 5.1-R, fresh install, in the first 15G of the disk, just after having booted into DOS to create some DOS partitions after the FreeBSD slice. I booted back into 5.0, and am presently writing across the entire disk with this command: fdisk -I /dev/ad6 dd if=/dev/zero of=/dev/ad6s1 bs=1m At more than 33 minutes into it at 24+MB/sec, there have been no such errors and the portion of the disk that was being mounted has already been covered by zeros. Darren - I've seen this before (actually, on western digital drives) a few times, and I'll tell you it's never good. Each time, I thought maybe it's a bug somewhere in the OS because I could rebuild the OS on the drive, and the error would seem to disappear - for awhile. Then the drive would get worse, and rapidly deteriorate into a door stop. I'm not sure if it's software or not, but I would double check your backups and start making plans to swap the drive. Eric -- -- Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
errors using wi driver in -CURRENT
I've just reinstalled a 'desktop server' from FreeBSD 4.8 to -CURRENT, and am finding quite a few problems with the 802.11b driver.I'm trying to use it as a access point, so I've tried setting the flag0,adhoc mediaopt, since ibss-master which I had used under 4.8 didn't work. This appeared to work, but other computers couldn't connect. Now, using just 'adhoc' other computers can connect, but whenever any use the network, the rate shown in 'ifconfig wi0' drops to 2MBit/s and I only get about 100KB/s bandwidth. Also, whenever I try to reset the media and/or mediaopt settings using eg 'ifconfig wi0 media DS/11Mbps mediaopt adhoc', the driver or card seems to go a bit buggy, with messages like: wi0: bad alloc 2f2 != 1f7, cur 0 nxt 0 wi0: device timeout wi0: device timeout wi0: timeout in wi_cmd 0x0021; event status 0x0008 when I run 'ifconfig' wi0 output stalls for a few seconds, locking the system, while another kernel error message appears. I'm using the card with a PCI converter card, and the card itself is: wi0: MELCO WLI-PCM-L11 at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: 802.11 address: 00:01:02:03:04:05 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.36.1) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps on initial configuration, the Media line of ifconfig is: media: IEEE 802.11 Wireless Ethernet DS/11Mbps adhoc (none) when I was recently getting ~35KB/s to the card, the 'OACTIVE' flag on the interface was set. I can provide more information which can help in diagnosing the problem, if required. -- Bruce Cran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: errors using wi driver in -CURRENT
It seems Bruce Cran wrote: Just to chime in here, I've spent 2 weeks of various trial and errors to get two Lucent Wavelan's (one 4.8, one -current) to talk to each other. Dispite my more or less futile experiments this would not work no matter what (even asking on -mobile and trying what came up there didn't help). Since I can use the cards perfectly between two 4.8 boxes (and have been for about 2 years), my take is that the wi driver in -current is borked useless, at least for some cards (It worked in 5.0 but broke on the way to 5.1 IIRC). just my .01 EUR... I've just reinstalled a 'desktop server' from FreeBSD 4.8 to -CURRENT, and am finding quite a few problems with the 802.11b driver.I'm trying to use it as a access point, so I've tried setting the flag0,adhoc mediaopt, since ibss-master which I had used under 4.8 didn't work. This appeared to work, but other computers couldn't connect. Now, using just 'adhoc' other computers can connect, but whenever any use the network, the rate shown in 'ifconfig wi0' drops to 2MBit/s and I only get about 100KB/s bandwidth. Also, whenever I try to reset the media and/or mediaopt settings using eg 'ifconfig wi0 media DS/11Mbps mediaopt adhoc', the driver or card seems to go a bit buggy, with messages like: wi0: bad alloc 2f2 != 1f7, cur 0 nxt 0 wi0: device timeout wi0: device timeout wi0: timeout in wi_cmd 0x0021; event status 0x0008 when I run 'ifconfig' wi0 output stalls for a few seconds, locking the system, while another kernel error message appears. I'm using the card with a PCI converter card, and the card itself is: wi0: MELCO WLI-PCM-L11 at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: 802.11 address: 00:01:02:03:04:05 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.36.1) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps on initial configuration, the Media line of ifconfig is: media: IEEE 802.11 Wireless Ethernet DS/11Mbps adhoc (none) when I was recently getting ~35KB/s to the card, the 'OACTIVE' flag on the interface was set. I can provide more information which can help in diagnosing the problem, if required. -- Bruce Cran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
gcc-3.3 issues
Hi !
Some port builds bail out with errors.
(Of course they do, that was expected.)
This is definitely gcc-3.3 related.
(They did build on 5.1-Release and
do build on 4.8-Stable.)
Would it be of interest for anyone to post them
or is it way too early for that ?
('Wait until 5.2-Release is out ?')
Cheers
Peter
--
[EMAIL PROTECTED]
Netzwerk- und Systemadministration
Campus der Max-Planck-Institute Tübingen
Tel: +49 7071 601598
Fax: +49 7071 601616
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
world breakage in pam_echo
--iIq+KTIB+xWY0FJy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, my world is broken with the following error message for some days now: =3D=3D=3D lib/libpam/modules/pam_echo cc -O2 -pipe -march=3Dpentium2 -I/usr/src/lib/libpam/modules/pam_echo/../..= /../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../..= /libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototy= pes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-= strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/= libpam/modules/pam_echo/pam_echo.c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: dereferencing = type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_echo. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Does anyone have some insight into this? - Christian --=20 Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --iIq+KTIB+xWY0FJy Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/FWYzbHYXjKDtmC0RAmikAKCcf+97hb8MYVmFkcB98FFaBgZ2zQCg59oY zt3LZ+pRTuf0O8ndWBklElI= =cQku -END PGP SIGNATURE- --iIq+KTIB+xWY0FJy--
Re: errors using wi driver in -CURRENT
I only seem to have problems when trying to connect to access points or devices with authmode set to shared, but when I set everything to OPEN, but still use a WEP key, I can make it work (as a client, not as an access point). I would agree something is seriously borked and really wish the authmode stuff would work. I'm willing to help in any way I can, but I'm not much of a C programmer or driver hacker to begin work on it myself.. Eric Soeren Schmidt wrote: It seems Bruce Cran wrote: Just to chime in here, I've spent 2 weeks of various trial and errors to get two Lucent Wavelan's (one 4.8, one -current) to talk to each other. Dispite my more or less futile experiments this would not work no matter what (even asking on -mobile and trying what came up there didn't help). Since I can use the cards perfectly between two 4.8 boxes (and have been for about 2 years), my take is that the wi driver in -current is borked useless, at least for some cards (It worked in 5.0 but broke on the way to 5.1 IIRC). just my .01 EUR... -- -- Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: errors using wi driver in -CURRENT
On Wed, Jul 16, 2003 at 03:01:15PM +0100, Bruce Cran wrote: wi0: bad alloc 2f2 != 1f7, cur 0 nxt 0 wi0: device timeout wi0: device timeout wi0: timeout in wi_cmd 0x0021; event status 0x0008 i get these too with a mini pci card and 5.1. so the problem is not related to the pci adapter. i also get the 'busy bit won't clear' errors, reports of that showed up on -mobile before i think. i did not have this problem with stable. i did not look into it, for i have other things to worry about right now. also, all i could do would be suppling bug reports, i do now have the knowledge for fixing this myself. cheers, t. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc-3.3 issues
s/gcc-3.3/ports/ issues and we are in agreement. Patches to fix broken ports are welcome. Kris is doing a fine job generating a list of what needs to be fixed with his cluster packabe building runs. -- Alexander Kabaev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Keyboard not working with XFree86
Hi Folks, I've recently upgraded my Notebook to 5.1-CURRENT. One of the main problems I ran into, is, that the keyboard is not working when using X. For the update from 4.8 to 5.1 I've followed the UPDATING procedure and was successful. After that I deleted all ports/packages and installed most of the ports fresh, including XFree86. Now I have XFree86-Server-4.3.0_8 installed. If I start up X, I cannot put in any key. The mouse works fine, though. I have to remote log into the box and kill xdm to get rid of the problem. The keyboard works perfectly on the console. I searched the mailing list archives and bug reports, but did not find anything. I also tried to create a fresh XF86Config file using xf86cfg (GUI based) and xf86config (text based). Both resulting config files had the same problem as the original config file, i.e. everything works except the keyboard. Now I've updated my 5.1-CURRENT to a snapshot from July 15, and tried to rebuild the XFree86-4-Server port. Now, the portbuild fails in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src/drv/radeon/ while trying to compile radeon_vtxtmp_x86.S error message are many lines of similar output, example: [..] radeon_vtxtmp_x86.S:400:34: pasting _x86_MultiTexCoord2fARB_2 and : does not give a valid preprocessing token. I don't think thats a problem, but due to the recent gcc import, since the portrevision has not changed, this probably wouldn't solve my problem anyway. But for the keyboard problem, any hints are appreciated. Best regards, Daniel -- IRCnet: Mr-Spock - signs of absurd developments in the net community: #42: - Wurstbrot gehoert m.E. zum Fruehstuecks-botnet von Cartoon - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Re: world breakage in pam_echo
On Wed, 16 Jul 2003, Christian Brueffer wrote: === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium2 -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 I was just about to report this myself. The breakage only occurs with optimization levels of -O2 (and maybe higher). Officially -O2 is not supported for world, but in my experience there are real problems with code (warnings in this case) that do not show up until the optimizer takes a closer look at them. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Tue, 15 Jul 2003, Static wrote: Just installed 5.1 yesterday, cvsuped using the . tag, and src-all /etc/make.conf untouched. I attempted to buildworld and I get the following ranlib libc_pic.a ranlib libc.a ranlib libc_p.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc.a /usr/obj/usr/sr c/i386/usr/lib sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc_p.a /usr/obj/usr/ src/i386/usr/lib sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libc.so.5 /usr/obj/u sr/src/i386/usr/lib ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so sh /usr/src/tools/install.sh -o root -g wheel -m 444 libc_pic.a /usr/obj/usr/s rc/i386/usr/lib 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Did not see an open pr or anything mentioned in mailing lists. Is this a known issue and should I file a pr, or is there a hack/workaround to fix this? Thanks rwz Static, My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: === usr.sbin/keyserv cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/keyserv.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 keyserv.8.gz cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/crypt_server.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc 1 error *** Error code 2 1 error *** Error code 2 1 error My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES DOC_LANG= en_US.ISO8859-1 PERL_VER= 5.8.0 PERL_VERSION= 5.8.0 PERL_ARCH= mach NOPERL= yo NO_PERL=yo NO_PERL_WRAPPER=yo My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. Anyway, I have not seen any mention on the lists of similar failures either. There must be something funky that we are doing. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: Mine has as well, though I thought the issue was specific to sparc64 (I'm on an Ultra 5). I cvsup'ed up again this morning and am trying again with -jX. It'll take a while to find out as this box takes a long time to compile recent -CURRENT. I'm currently 5 hours into buildworld and it's on contrib/ncurses. My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES Same compile options as me, though I don't have COMPAT or BOOTWAIT. My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. I'd be interested in seeing if that works for you - it'll be a few hours before my run is finished so you'll know before I will ;-) -T -- Do not consciously seek enlightenment. -Muso Kokushi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Tillman wrote: On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: Mine has as well, though I thought the issue was specific to sparc64 (I'm on an Ultra 5). I cvsup'ed up again this morning and am trying again with -jX. It'll take a while to find out as this box takes a long time to compile recent -CURRENT. I'm currently 5 hours into buildworld and it's on contrib/ncurses. My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES Same compile options as me, though I don't have COMPAT or BOOTWAIT. My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. I'd be interested in seeing if that works for you - it'll be a few hours before my run is finished so you'll know before I will ;-) -T Tillman, It takes 1 1/2 hours to hit the point of failure, so it will be a short while, but I will let you know. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
In the last episode (Jul 16), Matt Loschert said: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: === usr.sbin/keyserv cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/keyserv.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 keyserv.8.gz cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/crypt_server.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc 1 error *** Error code 2 1 error *** Error code 2 1 error My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. If you are using -j6, the real error could be many many lines above what you pasted. It's most likely in usr.sbin somewhere, but probably not keyserv. You'll have to capture the entire log and look at it to determine the first failure. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
USB Palm/Weird messages on hotsync....
Since I know there's been LOTS of USB commits in the last few days... I tried(!) my Tungsten T today and got the following: Jul 16 13:08:15 lerlaptop-red kernel: ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 2 Jul 16 13:08:15 lerlaptop-red kernel: ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 2 Jul 16 13:08:20 lerlaptop-red kernel: ucom0: init failed, TIMEOUT Jul 16 13:08:20 lerlaptop-red kernel: device_probe_and_attach: ucom0 attach returned 6 Jul 16 13:08:20 lerlaptop-red kernel: uhub1: port 1, set config at addr 2 failed Jul 16 13:08:20 lerlaptop-red kernel: uhub1: device problem, disabling port 1 Where do we go from here? How do I debug? 5.1-CURRENT from last night, with the ucom/uvisor module kldload(1)ed. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
Same here, remove the -j N. Right now there seem to be some dependencies which you fail against with a parallel build. Sorry for the top-posting. -Bosko On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: On Tue, 15 Jul 2003, Static wrote: Just installed 5.1 yesterday, cvsuped using the . tag, and src-all /etc/make.conf untouched. I attempted to buildworld and I get the following ranlib libc_pic.a ranlib libc.a ranlib libc_p.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc.a /usr/obj/usr/sr c/i386/usr/lib sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc_p.a /usr/obj/usr/ src/i386/usr/lib sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libc.so.5 /usr/obj/u sr/src/i386/usr/lib ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so sh /usr/src/tools/install.sh -o root -g wheel -m 444 libc_pic.a /usr/obj/usr/s rc/i386/usr/lib 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Did not see an open pr or anything mentioned in mailing lists. Is this a known issue and should I file a pr, or is there a hack/workaround to fix this? Thanks rwz Static, My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: === usr.sbin/keyserv cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/keyserv.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 keyserv.8.gz cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/crypt_server.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc 1 error *** Error code 2 1 error *** Error code 2 1 error My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES DOC_LANG= en_US.ISO8859-1 PERL_VER= 5.8.0 PERL_VERSION= 5.8.0 PERL_ARCH= mach NOPERL= yo NO_PERL=yo NO_PERL_WRAPPER=yo My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. Anyway, I have not seen any mention on the lists of similar failures either. There must be something funky that we are doing. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED] TECHNOkRATIS Consulting Services * http://www.technokratis.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: world breakage in pam_echo
Wesley Morgan [EMAIL PROTECTED] writes: On Wed, 16 Jul 2003, Christian Brueffer wrote: === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium2 -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 I was just about to report this myself. The breakage only occurs with optimization levels of -O2 (and maybe higher). Officially -O2 is not supported for world, but in my experience there are real problems with code (warnings in this case) that do not show up until the optimizer takes a closer look at them. [snip] It's my impression that these warnings mean the C code in question is undefined or implementation-defined according to the C standard, and the generated assembler may have unexpected behavior. I get this impression from reading the description of -fstrict-aliasing (enabled at -O2, -O3, -Os) at: http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Optimize-Options.html#Optimize%20Options (The relevant warning flag is -Wstrict-aliasing, see http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Warning-Options.html#Warning%20Options ) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'Hard error reading fsbn' in 5.1 but not 5.0?
Darren has dicovered the magic of automatic block remapping. On Wed, 16 Jul 2003, Darren Pilgrim wrote: Just now, my 120GB western digital, immediately upon the mounting of all filesystems during startup, made a faint click, then my screen filled with errors of the form: ad6: hard error reading fsbn -# of -#--# error=10 If you write this block again it should map it out of the way. Whatever's there is probably gone but you can keep it from annoying you any more. Of course mapping dd to a file gets kinda hard :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: world breakage in pam_echo
On Wed, 16 Jul 2003, Christian Brueffer wrote: my world is broken with the following error message for some days now: === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium2 -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c 1. Optimization levels above -O are not supported. 2. -Werror is NOT recommended post-gcc 3.3 upgrade unless you are fixing warnings. gcc3.3 is much more warn-happy. I'm not sure how you got -Werror in there since it was removed prior to the gcc3.3 import. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
msdof and fstab
I am having trouble mounting my windows partition from the fstab file. I have an entry in fstab that looks like this /dev/ad6s5 /mnt/disk2 msdosfs rw 0 0. When I try to mount the disk I get the following error mount: disk2: unknown special file or file system. What makes things even more strange is that I can mount the slice just fine when I issue mount_msdosfs from the command prompt. Does anyone have any ideas? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Dan Nelson wrote: In the last episode (Jul 16), Matt Loschert said: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: === usr.sbin/keyserv cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/keyserv.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 keyserv.8.gz cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/crypt_server.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc 1 error *** Error code 2 1 error *** Error code 2 1 error My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. If you are using -j6, the real error could be many many lines above what you pasted. It's most likely in usr.sbin somewhere, but probably not keyserv. You'll have to capture the entire log and look at it to determine the first failure. -- Dan Nelson [EMAIL PROTECTED] Thanks Dan. I have the output saved, but I can't see anything obviously wrong. Bosko Milekic just emailed me too and said that there is currently a make dependency problem causing -j builds to fail. Beyond my make-foo skills. :) Anyway, my non-j build just finished successfully, so I guess that was it. BTW, if my build logs would be useful to anyone, I still have them. Thanks, - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Bosko Milekic wrote: Same here, remove the -j N. Right now there seem to be some dependencies which you fail against with a parallel build. Sorry for the top-posting. -Bosko Bosko, That did the trick. Thanks so much. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Annoucning DragonFly BSD!
Announcing DragonFly BSD! http://www.dragonflybsd.org/ Hello everyone! For the last few months I have been investigating and then working on a new approach to the BSD kernel. This has snowballed into a far more ambitious project which is now ready for wider participation. It is the intent of this project to take over development of the 4.x tree, to move kernel development along an entirely new path towards SMP, and to completely rewrite the packaging and distribution system. We eventually intend to backport many FreeBSD-5 features into the new tree, but that is not where the initial focus will be. The preliminary 'proving' work I have done is now available on the new DragonFly site. You can access it through cvsup or browse it through ftp. This proving work involved implementing much of the earlier UP-SMP converstion work that was done when 5.x first branched, but under an entirely new mutex-free light weight kernel threading infrastructure. It includes the LWKT system, interrupt threads, and pure threads for system processes amoung other things. For obvious reasons the codebase will only run on i386 for now, and ports to other platforms will not happen until the MD infrastructure is cleaned up and finalized. I considered starting with a 5.x base but it is simply too heavily mutexed, it was actually faster to start with 4.x and move forward rather then to start with 5.x and move backwards. I have both UP and SMP builds working in the current codebase. I believe it proves out the core concepts quite nicely and there is much more work coming down the pipeline. The site is: http://www.dragonflybsd.org/ Hopefully my T1 can handle the cvsup load. Eventually I'll colocate some boxes to deal with that issue. For the next few months the project is going to concentrate on low level kernel development. There are still a number of big ticket items that have to be accomplished, primarily in converting the I/O path to using VM Object/range lists, before work can branch out into other areas. I expect the project to start fairly slowly but then for momentum to build. Anyone interested in working on or discussing the project is welcome! I have created a mailing list server and newsgroup forums and I am working on web-accessibility to same for passive listeners. I will be posting periodic updates to freebsd-hackers as well. Again, the site is below. It contains a great deal of documentation and other information. I even have a mascot! And, hopefully, it will all work from outside my LAN :-) http://www.dragonflybsd.org/ -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI / HP Omnibook 500
I committed a fix for AE_NO_HARDWARE_RESPONSE errors as acpi_ec.c:1.33. Please cvsup and report if your problems are still present. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problem?
Your asl seems bogus since there are a lot of unexpected values (i.e. for TZ and EC port values). Since it worked in 4.8R, follow the instructions for disabling ACPI. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi: iasl errors
Please see a common faq on patching your asl: http://www.cpqlinux.com/acpi-howto.html -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc-3.3 issues
On Wednesday 16 July 2003 17:07, Alexander Kabaev wrote: s/gcc-3.3/ports/ issues and we are in agreement. Patches to fix broken ports are welcome. Kris is doing a fine job generating a list of what needs to be fixed with his cluster packabe building runs. There was one report of kdelibs' configure failing because of the weirdness of the new cc (3.3), that leads to errors instead of warnings with certain combinations of -W* and -pedantic options. Is something like this expected, i.e., certain combinations of -W* and -pedantic to produce errors when they didn't before? -- Michael Nottebrock \KDE on FreeBSD\,ww \--- \ ,wWWCybaWW_) \ http://freebsd.kde.org \ `WSheepW'free \II II node pgp0.pgp Description: signature
Re: Annoucning DragonFly BSD!
: :Is it real or another troll? : :-Maxim I stupidly misspelled 'announcing' in the subject line, but it's very real. Check the site out: http://www.dragonflybsd.org/ It's basically the reason why I've been so quiet lately. I've been working 12 hours a day on proving the model out. -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoucning DragonFly BSD!
At 1:58 PM -0700 7/16/03, Matthew Dillon wrote: : :Is it real or another troll? : :-Maxim I stupidly misspelled 'announcing' in the subject line, Well, at least you didn't misspell your name... :-) but it's very real. Check the site out: http://www.dragonflybsd.org/ The site looks interesting. All the kernel-level stuff is pretty much over my head, but I will be interested in the package-level ideas (once work starts on that part). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Annoucning DragonFly BSD!
: : I stupidly misspelled 'announcing' in the subject line, : :Well, at least you didn't misspell your name... :-) : : but it's very real. Check the site out: : : http://www.dragonflybsd.org/ : :The site looks interesting. All the kernel-level stuff is :pretty much over my head, but I will be interested in the :package-level ideas (once work starts on that part). : :-- :Garance Alistair Drosehn= [EMAIL PROTECTED] I have the beginnings of an idea for how to do the packaging stuff properly... and how to automated it so one gets the dependancies correct. To realize the idea I will have to get to the point where a VFS layer can run in userland. Then it becomes trivial to build 'filtering VFS layers' that run in userland (i.e. don't take up kernel resources) which can be used to figure out *exactly* what a package references in the system and *exactly* what it effects. Once one is able to do that the dependancy and conflict information can not only be completely automated, but one can theoretically (and automatically) create 'environments' for each package to run in which resolve the conflicts (i.e. makes sure that the exact version of third party shared libraries and so forth used by a package are the ones that package sees even if multiple versions would normally install over each other). I'm guessing 6 months until the project gets to that point, oweing to the complexity of fixing VFS and, in particular, VFS_LOOKUP. But then, watch out! Infinite application... not only to the packaging system, but to the concept of how jails should work as well, and many other things. -Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Dan Nelson wrote: If you are using -j6, the real error could be many many lines above what you pasted. It's most likely in usr.sbin somewhere, but probably not keyserv. You'll have to capture the entire log and look at it to determine the first failure. Try using make -P to unmix the output. I don't know how well this works in practice. This flag seems to be quite broken -- it causes the (standard) output to be spammed with messages like Remaking (sic) foo.o and Results of making foo.o even when make is requested to be quiet (make -s) and the results are null. Using -P also has the side effect of accidentally avoiding the longstanding bug of waiting for a select timeout for up to 100 msec after each batch of jobs. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on sparc64/sparc64
TB --- 2003-07-16 23:05:24 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-07-16 23:05:24 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-16 23:07:56 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/sysconf.3 sysconf.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/sysctl.3 sysctl.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/syslog.3 syslog.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/tcgetpgrp.3 tcgetpgrp.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/tcsendbreak.3 tcsendbreak.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/tcsetattr.3 tcsetattr.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/tcsetpgrp.3 tcsetpgrp.3.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2003-07-16 23:45:48 - /usr/bin/make returned exit code 1 TB --- 2003-07-16 23:45:48 - ERROR: failed to build world TB --- 2003-07-16 23:45:48 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with fxp0 on T30 with 5.1-RELEASE
http://www.freebsdforums.org/forums/showthread.php?s=threadid=10676 This has more info confirming that it's not just me :) Anyways, I'm willing to try anything: I'm installing 5.1 from CD (BSD Mall! YAY!) and am VERY VERY VERY happy that acpi (appears to be) is working perfectly! (I had to retrograde to 4.x because it was so broken with 5.0 and this is my first return to 5.x land since then :) The problem : fxp0: device timeout appears continuously (about every 15 seconds) while interface is UP details : - IBM T30 laptop, Windows says it's an Intel Pro/100 VE - 5.1-RELEASE (can't cvsup, network doesn't work :) - only happens when device is UP (ifconfig down causes the error to go away) - mii appears to work correctly : ifconfig shows the link status correctly instantly (10/100/none, full/half duplex) and it updates when i remove the cable. Also, the mac address shows up correctly. I don't have anything added to the laptop, no cardbus devices, no usb devices, so i'm not sure what's causing the problem, but like I said, I'm willing to try anything out if you have any suggestions :) Dana Lacoste Ottawa, Canada ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help diagnosing NIS breakage ?
Hi Bill, I have a question.
On Tue, 15 Jul 2003 10:44:15 -0700 (PDT), [EMAIL PROTECTED] (Bill
Paul) said:
B I uploaded a new diff, please test this instead:
B http://www.freebsd.org/~wpaul/getpwent.diff
B Thanks for providing me access to this machine, it helped me realize
B where I'd gone wrong in my patch. If this works for you, and if nobody
B objects, I will check it in.
Is your patch getpwent.diff really for revision 1.82 ?
If so, nis_map() will be like this and I do not think this works.
-- -- -- -- --
static int
nis_map(char *domain, enum nss_lookup_type how, char *buffer, size_t bufsize,
int *master)
{
int rv;
char*outname;
*master = 0;
if (geteuid() == 0) {
if (snprintf(buffer, bufsize, master.passwd.by%s,
(how == nss_lt_id) ? uid : name) = bufsize)
return (NS_UNAVAIL);
rv = yp_order(domain, buffer, outname);
if (rv == 0)
*master = 1;
return (NS_UNAVAIL);
}
return (NS_SUCCESS);
}
-- -- -- -- --
In case of geteuid()==0, always NS_UNAVAIL returned
In case of geteuid()!=0, map name is not assigned to *buffer
I did not imagine my idea of yp_order() would break NIS with
ActiveDirectory, which I have never seen so far.
--
---
TOMITA Yoshinori
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broadcom NetXtreme BCM5705M support
Hi Bill, I tested the driver with the new patch and everything works fine now. Thank you for your quick response. If you need more testing of this NIC, I can always cooperate. Boris Georgiev - Original Message - From: william paul [EMAIL PROTECTED] To: Boris Georgiev [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:00 AM Subject: Re: Broadcom NetXtreme BCM5705M support Of all the gin joints in all the towns in all the world, Boris Georgiev had to walk into mine and say: Hi Bill, Sorry for the previous e-mail, but have in mind that I'm trying to cooperate by testing your drivers and I am not aware of the rules for declaring a hardware problem in the mailing lists. The only way I can send you the messages from the kernel is if I rewrite them from the console. I know that. But that's a small price to pay for free driver development. :) Here is the information that you requested: bge0: Broadcom BCM5705M Dual Gigabit Ethernet, ASIC rev. 0x3001 mem 0x9000-0x9000 irq 11 at device 14.0 on pci2 bge0: firmware handshake timed out bge0: RX CPU self-diagnostics failed! bge0: chip initialization failed device_probe_and_attach: bge0 attach returned 6 If you need more detailed information, I can send it to you on request. Ok, the firmware handshake does not really load any firmware. This just checks that the firmware on the NIC has responded to a reset and is back up and running. The error here is due to the fact that the firmware initialization seems to take longer on the 5705, so the timeout has to be increased. Thanks for a couple of other people, I have made changes to deal with this. Please download the latest driver code from the same URL (http://www.freebsd.org/~wpaul/Broadcom/5705). This should fix the problem with the timeout, as well as a few other things. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on alpha/alpha
TB --- 2003-07-17 04:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-17 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-17 04:02:51 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get.3 acl_get.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get_entry.3 acl_get_entry.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get_permset.3 acl_get_permset.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get_perm_np.3 acl_get_perm_np.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get_qualifier.3 acl_get_qualifier.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_get_tag_type.3 acl_get_tag_type.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libc/posix1e/acl_init.3 acl_init.3.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. TB --- 2003-07-17 04:43:59 - /usr/bin/make returned exit code 1 TB --- 2003-07-17 04:43:59 - ERROR: failed to build world TB --- 2003-07-17 04:43:59 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS problem
S³awek ¯ak wrote: I guess there is something wrong with exporting iso9660 CD's over NFS. I've added /cdrom -ro -mapall=root to /etc/exports, restarted mountd and after mounting the CD on Solaris 8. All the files are 0-sized, dates are set back to the epoch and directories are seen as files. Exporting ufs2 filesystems works as expected. [ ... ] Any thoughts? Yes. Exporting FS's is not as simple as simply doing it. The API in FreeBSD needs changed somewhat to support this at a higher layer. Even so, the hacked ISO9660 code is actually OK for the volume export. The problem comes in that the consumer of the FS is assumed to have the ability to translate certain attributes when the struct direct and stat structures are externalized to the NFS server code, which is a VFS client. You are certain you don't see these same attributes on /cdrom itself, form a shell when you cd to /cdrom? If your answer is no, then it's definitely the externalization of the stat structure and things like struct direct. Note that the NFS over-the-wire stat structure is *not* the same as the FFS version which it exports to the stat(2) and fstat(2) system calls. Probably the thing to do is to look at the differences in the code, and not assume that the VFS client is always the system call layer. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
