[-CURRENT tinderbox] failure on alpha/alpha
TB --- 2003-06-15 04:00:16 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-06-15 04:00:16 - 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-06-15 04:02:40 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> 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 [...] cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_proc.c:129: `P_THREADED' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_proc.c:129: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm/kvm_proc.c:129: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/lib/libkvm. *** 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. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. TB --- 2003-06-15 04:18:46 - /usr/bin/make returned exit code 1 TB --- 2003-06-15 04:18:46 - ERROR: failed to build world TB --- 2003-06-15 04:18:46 - tinderbox aborted ___ [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-06-15 04:22:57 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-06-15 04:22:57 - 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-06-15 04:25:47 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> 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 [...] cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_proc.c:129: `P_THREADED' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_proc.c:129: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm/kvm_proc.c:129: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/lib/libkvm. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-06-15 04:40:32 - /usr/bin/make returned exit code 1 TB --- 2003-06-15 04:40:32 - ERROR: failed to build world TB --- 2003-06-15 04:40:32 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-06-15 05:03:22 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-06-15 05:03:22 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-06-15 05:07:26 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld >>> 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/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include >>> stage 4: building libraries [...] cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_proc.c:129: `P_THREADED' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_proc.c:129: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm/kvm_proc.c:129: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libkvm. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-06-15 05:23:22 - /usr/bin/make returned exit code 1 TB --- 2003-06-15 05:23:22 - ERROR: failed to build world TB --- 2003-06-15 05:23:22 - tinderbox aborted ___ [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-06-15 04:44:43 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-06-15 04:44:43 - 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-06-15 04:46:33 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> 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 [...] cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_proc.c:129: `P_THREADED' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_proc.c:129: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm/kvm_proc.c:129: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/libkvm. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-06-15 05:01:04 - /usr/bin/make returned exit code 1 TB --- 2003-06-15 05:01:04 - ERROR: failed to build world TB --- 2003-06-15 05:01:04 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: O(/E)HCI detach support patch
Below is a preliminary patch that seems to at least keep the machine from
panicing when detaching USB cards :)
It's still highly experimental, so use at your own risk. It works well enough
for me to plug in / unplug my cardbus card repeatedly (even with devices
attached to it). Theoretically this should also make the usb kernel module
unloadable, however that is untested.
WARNING: There may still be edge conditions or memory leaks lurking about, and
users of this patch are likely to be eaten by a grue.
Unplugging it while one of the devices is actively being used is probably a
very bad idea. I tried not to make the code too divergant from the NetBSD
path but probably wasn't 100% successful.
If the formatting gets mangled in the mail and anyone wants to try this patch,
mail me and I'll send it as a file. Feedback / comments / advice are much
appreciated.
Index: ehci_pci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ehci_pci.c,v
retrieving revision 1.2
diff -u -r1.2 ehci_pci.c
--- ehci_pci.c 12 Jun 2003 05:29:15 - 1.2
+++ ehci_pci.c 14 Jun 2003 21:48:26 -
@@ -263,9 +263,7 @@
if (err) {
device_printf(self, "USB init failed err=%d\n", err);
-#if 0 /* TODO */
ehci_pci_detach(self);
-#endif
return EIO;
}
return 0;
@@ -317,6 +315,7 @@
/* Device interface */
DEVMETHOD(device_probe, ehci_pci_probe),
DEVMETHOD(device_attach, ehci_pci_attach),
+ DEVMETHOD(device_detach, ehci_pci_detach),
DEVMETHOD(device_shutdown, bus_generic_shutdown),
/* Bus interface */
Index: ohci_pci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci_pci.c,v
retrieving revision 1.31
diff -u -r1.31 ohci_pci.c
--- ohci_pci.c 12 Jun 2003 05:29:15 - 1.31
+++ ohci_pci.c 15 Jun 2003 04:25:32 -
@@ -299,6 +299,7 @@
/* Device interface */
DEVMETHOD(device_probe, ohci_pci_probe),
DEVMETHOD(device_attach, ohci_pci_attach),
+ DEVMETHOD(device_detach, ohci_pci_detach),
DEVMETHOD(device_shutdown, bus_generic_shutdown),
/* Bus interface */
Index: uhci_pci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/uhci_pci.c,v
retrieving revision 1.47
diff -u -r1.47 uhci_pci.c
--- uhci_pci.c 12 Jun 2003 05:29:15 - 1.47
+++ uhci_pci.c 15 Jun 2003 05:18:25 -
@@ -392,6 +392,7 @@
/* Device interface */
DEVMETHOD(device_probe, uhci_pci_probe),
DEVMETHOD(device_attach, uhci_pci_attach),
+ DEVMETHOD(device_detach, uhci_pci_detach),
DEVMETHOD(device_suspend, uhci_pci_suspend),
DEVMETHOD(device_resume, uhci_pci_resume),
DEVMETHOD(device_shutdown, bus_generic_shutdown),
Index: uhub.c
===
RCS file: /home/ncvs/src/sys/dev/usb/uhub.c,v
retrieving revision 1.47
diff -u -r1.47 uhub.c
--- uhub.c 8 Aug 2002 12:05:50 - 1.47
+++ uhub.c 15 Jun 2003 04:39:13 -
@@ -87,6 +87,7 @@
Static usbd_status uhub_explore(usbd_device_handle hub);
Static void uhub_intr(usbd_xfer_handle, usbd_private_handle,usbd_status);
+Static int uhub_dummy_detach(device_t);
#if defined(__FreeBSD__)
Static bus_driver_added_t uhub_driver_added;
@@ -123,8 +124,7 @@
Static device_method_t uhubroot_methods[] = {
DEVMETHOD(device_probe, uhub_match),
DEVMETHOD(device_attach, uhub_attach),
-
- /* detach is not allowed for a root hub */
+ DEVMETHOD(device_detach, uhub_dummy_detach),
DEVMETHOD(device_suspend, bus_generic_suspend),
DEVMETHOD(device_resume, bus_generic_resume),
DEVMETHOD(device_shutdown, bus_generic_shutdown),
@@ -535,6 +535,16 @@
return (0);
}
#endif
+
+/*
+ * Dummy detach for root hub when devices are being torn down
+ * Don't need to detach child devices since they're already gone
+ */
+Static int
+uhub_dummy_detach(device_t dev)
+{
+ return 0;
+}
/*
* Called from process context when the hub is gone.
Index: usb.c
===
RCS file: /home/ncvs/src/sys/dev/usb/usb.c,v
retrieving revision 1.87
diff -u -r1.87 usb.c
--- usb.c 14 Apr 2003 14:04:07 - 1.87
+++ usb.c 15 Jun 2003 05:20:58 -
@@ -121,6 +121,10 @@
struct proc *sc_event_thread;
+#if defined(__FreeBSD__)
+ dev_t dev;
+#endif
+
charsc_dying;
};
@@ -175,7 +179,8 @@
USB_DECLARE_DRIVER_INIT(usb,
DEVMETHOD(device_suspend, bus_generic_suspend),
DEVMETHOD(device_resume, bus_generic_resume),
- DEVMETHOD(device_shutdown, bus_generic_shutdown)
+ DEVMETHOD(device_shutdown, bus_generic_shutdown),
+
[-CURRENT tinderbox] failure on sparc64/sparc64
TB --- 2003-06-15 05:26:51 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-06-15 05:26:51 - 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-06-15 05:30:20 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> 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 [...] cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -DLIBC_SCCS -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_proc.c:129: `P_THREADED' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_proc.c:129: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm/kvm_proc.c:129: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libkvm. *** 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. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2003-06-15 05:44:57 - /usr/bin/make returned exit code 1 TB --- 2003-06-15 05:44:57 - ERROR: failed to build world TB --- 2003-06-15 05:44:57 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: O(/E)HCI detach support
Okay, sorry for the reply-to-self, but I think I've nailed down the detach
problem and it looks like it will require some more work. In short, the OHCI
driver may be ready for hot-plugging but the USB subsystem isn't. Here's a
play-by-play of what's happening:
1. On card removal, cardbus_detach_card dispatches ohci_pci_detach
2. ohci_pci_detach calls device_delete_child on itself
3. device_delete_child calls itself recursively for the children of ohci
4. When device_delete_child tries to dispatch device_detach for the first uhub
it finds, it gets ENXIO because uhub doesn't define a detach method
5. The ENXIO error filters up to the top level device_delete_child and it
exits without detaching any of the other devices
6. ohci_pci_detach ignores the error result and removes all its resources
(about all it can do at this point)
7. cardbus_detach_card removes the PCI configuration data from memory
This leaves some nonexistent devices as children of the cardbus device. The
next time any card is inserted, it calls cardbus_detach_card to remove the
old entries, which removes the already-removed PCI config, and BOOM. I think
the only way this can be resolved is to make sure all of the USB-related
devices (including the root hub) have a device_detach method implemented.
uhub is easy enough to fix -- like OHCI and EHCI it has a detach function
written but it's just not referenced in the device_method_t.
The usb device is a whole can of worms though. It has a detach method that
just spits out "unload prevented" and returns EINVAL. Of course since the
usb bus has physically been removed it doesn't have much of a choice :). I
put in a null function that just returns 0 as a test, but it either panics
immediately because the event thread is still polling the device or panics
when you put the card back in and it tries to make_dev something that already
exists ("panic: don't do that").
It looks like the NetBSD and OpenBSD cases do have detach code, so it may just
be a matter of modifying that remove the device entry. If I get some free
time tomorrow I'll take a crack at it and see how many times I can panic this
poor laptop :D
Craig
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
O(/E)HCI detach support (was CardBus USB 2.0 Controller)
On Thursday 12 June 2003 07:15 am, Bernd Walter wrote: > I'm not shure if the code would work, but it was also ported into ehci > and therefor ehci should be in a similar state. > Well loosing memory is better than panic. > I have no cardbus - can this be tested with a module? Well, the card no longer complains when it is removed, but unfortunately re-inserting it results in a panic in pci_freecfg. At least the panic always seems to happen in the same place now: #0 0xc01b2a82 in pci_freecfg (dinfo=0xc1cc8f00) at /mnt/compile/src/sys/dev/pci/pci.c:456 #1 0xc017f9c0 in cardbus_detach_card (cbdev=0xc0c68580) at /mnt/compile/src/sys/dev/cardbus/cardbus.c:238 #2 0xc017f6d8 in cardbus_attach_card (cbdev=0xc0c68580) at /mnt/compile/src/sys/dev/cardbus/cardbus.c:158 #3 0xc01b1658 in CARD_ATTACH_CARD (dev=0xc0c68580) at card_if.h:67 #4 0xc01af345 in cbb_insert (sc=0xc0c68580) at /mnt/compile/src/sys/dev/pccbb/pccbb.c:936 #5 0xc01af0d8 in cbb_event_thread (arg=0xc1bd2a00) at /mnt/compile/src/sys/dev/pccbb/pccbb.c:883 at the line: pci.c:456 STAILQ_REMOVE(devlist_head, dinfo, pci_devinfo, pci_links); I went through devlist_head list manually and didn't see dinfo in there. dinfo is ID 1003 0035 (NEC OHCI) and it has the other OHCI and the EHCI dangling off of it -- neither of which are in the actual devlist. It looks like something somewhere isn't getting freed. There is also still trouble when it's combined with other PCMCIA devices -- it works with 16-bit PCcard stuff if and only if it's the FIRST card inserted, and completely blows up if combined with another Cardbus device either way. Of course putting two Cardbus 3com NICs in doesn't work either, so I think there may be some unresolved issues with this controller. I've got serial gdb setup at home now (from a Linux box, oh the horror! :) and it makes troubleshooting a lot easier. It seems that the cc: list has grown a bit, if anybody is getting copied and couldn't care less about this please let me know :) I'm also thinking that at this point hackers@ may be a more appropriate venue for discussion. Comments? Craig ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pedantic again
On Sat, 14 Jun 2003, Pete Carah wrote: > Someone added "-std=gnu89 -pedantic" to libcrypto's make; given that > stdlib.h and several other places contain "long long", this results in > several thousands of warnings about C89. We need to either go modern > or not but not try both at once :-) -std=c89 works fine for slightly wrong reasons, but not gnu89, mainly because of spelling differences. std=c89 prevents definition of FreeBSD's __LONG_LONG_SUPPORTED in , while std=gnu99 gives a definition of _LONGLONG by the compiler itself. stdlib.h etc. only understands the former. > Also usr.bin/window generates LOTS of warnings; I didn't spot just what > kind. Someone added -std=mumble which causes lots of warnings in nonstandard code. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -pedantic yet again, this time with Werror
H, when I build, I get: ===> libexec/tcpd cc -O -pipe -mcpu=pentiumpro -DREAL_DAEMON_DIR=\"/usr/libexec\" -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10 -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DFACILITY=LOG_DAEMON -DINET6 -Wformat=2 -Wno-format-extra-args -Werror -c /paco/imp/FreeBSD/src/contrib/tcp_wrappers/tcpd.c cc -O -pipe -mcpu=pentiumpro -DREAL_DAEMON_DIR=\"/usr/libexec\" -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10 -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DFACILITY=LOG_DAEMON -DINET6 -Wformat=2 -Wno-format-extra-args -Werror -o tcpd tcpd.o -lwrap gzip -cn /paco/imp/FreeBSD/src/libexec/tcpd/../../contrib/tcp_wrappers/tcpd.8 > tcpd.8.gz ===> What version of src/Makefile.inc and src/share/mk/bsd.sys.mk do you have? I have 1.367 and 1.32 respectively. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI: Error: Method execution failed
On Sat, 14 Jun 2003, Doug White wrote: Hi, > This might be fixable ... its overrunning a region definition which could > be a simple bug that could be fixed by extracting the DSDT, convert to > ASL, fix, recompile, and override. Of course you have to know ASL :) No I don't really know but remember to have downloaded an acpi pdf once... perhaps I should have read it ... > > It is a MSI-6210 w/o SCSI onboard but MP. It's the latest BIOS > > revision available for this board - I can check the version > > on request but I do not really like rebooting again ;-) > > You should probably pester MSI and claim Linux has the same issue. The > magic L word might wake them up. With that "magic" L that I almost entirely dropped beginning of this year in favour of FreeBSD 5 a lot of more things didn't work up to 2.5.xx that worked out of the box with a 5.x CD :-))) Just for the archive link to the board's BIOS: http://www.msi-computer.de/produkte/produkt.php?Prod_id=15&Seite=BIOS > If you want to be extra neat, use acpidump to extract the dsdt and in > bundle that with your dmesg into a tarball I can download. http://www.zabbadoz.net/zabbadoz-network/megablast/freebsd-testing/msi-6120n-acpi.tbz containing msi-6120n-acpi.dmesg msi-6120n-acpi.asl msi-6120n-acpi.dsdt [1] (extracted according to the instruction from acpidump manpage). -- Thanks Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ ___ [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-06-14 19:26:05 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-06-14 19:26:05 - 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-06-14 19:28:35 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] cc -O -pipe -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/xlint/../lint1 -DPREFIX=\"\" -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/xlint/../arch/sparc64 -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/xlint/../common -o xlint xlint.o mem.o gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/xlint/lint.1 > lint.1.gz ===> usr.bin/xlint/llib lint -cghapbx -Cposix /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/llib/llib-lposix llib-lposix: In file included from /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include/sys/types.h:45, from /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/llib/llib-lposix:39: /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include/sys/cdefs.h:148:2: #error FreeBSD alloca support needed for this compiler *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint/llib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin/xlint. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/usr.bin. *** 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-06-14 20:16:30 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 20:16:30 - ERROR: failed to build world TB --- 2003-06-14 20:16:30 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Build breakage in the "en" module
With this morning's sources, my kernel build is failing in the "en" module: /a/src/sys/dev/en/midway.c: In function `en_get_vccs': /a/src/sys/dev/en/midway.c:1474: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1474: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1479: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1480: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1488: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1492: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1493: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1493: `ATMIO_FLAG_PVC' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1493: (Each undeclared identifier is reported only once /a/src/sys/dev/en/midway.c:1493: for each function it appears in.) /a/src/sys/dev/en/midway.c:1494: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1495: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1497: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1497: `ATMIO_AAL_5' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1499: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1499: `ATMIO_AAL_0' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1500: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1500: `ATMIO_TRAFFIC_UBR' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1501: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1502: increment of pointer to unknown structure /a/src/sys/dev/en/midway.c:1502: arithmetic on pointer to an incomplete type /a/src/sys/dev/en/midway.c: In function `en_ioctl': /a/src/sys/dev/en/midway.c:1591: `SIOCATMGETVCCS' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1600: `SIOCATMGVCCS' undeclared (first use in this function) /a/src/sys/dev/en/midway.c:1606: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type /a/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type *** Error code 1 At line 1474, the incomplete type is "struct atmio_vcctable". I grepped all of the *.h files under src/sys, but none of them contained "atmio_vcctable". Perhaps a new header file was omitted from the commit? John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-pedantic yet again, this time with Werror
This one stops the build: Same cvsup (of about an hour ago) as for my previous note. -- Pete - ===> libexec/tcpd cc -O -pipe -march=pentium3 -DREAL_DAEMON_DIR=\"/usr/libexec\" -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10 -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DFACILITY=LOG_DAEMON -DINET6 -std=iso9899:1990 -pedantic -Wformat=2 -Wno-format-extra-args -Werror -c /usr/src/contrib/tcp_wrappers/tcpd.c cc1: warnings being treated as errors In file included from /usr/obj/usr/src/i386/usr/include/sys/stat.h:100, from /usr/src/contrib/tcp_wrappers/tcpd.c:23: /usr/obj/usr/src/i386/usr/include/sys/time.h: In function `timespec2bintime': /usr/obj/usr/src/i386/usr/include/sys/time.h:125: warning: ISO C89 forbids long long integer constants /usr/obj/usr/src/i386/usr/include/sys/time.h: In function `timeval2bintime': /usr/obj/usr/src/i386/usr/include/sys/time.h:142: warning: ISO C89 forbids long long integer constants /usr/src/contrib/tcp_wrappers/tcpd.c: In function `main': /usr/src/contrib/tcp_wrappers/tcpd.c:133: warning: ISO C does not support the `%m' printf format *** Error code 1 Stop in /usr/src/libexec/tcpd. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-06-14 18:30:27 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-06-14 18:30:27 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-06-14 18:33:01 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld >>> 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/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. [...] In file included from /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include/sys/stat.h:100, from /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/contrib/tcp_wrappers/tcpd.c:23: /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include/sys/time.h: In function `timespec2bintime': /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include/sys/time.h:125: warning: ISO C89 forbids long long integer constants /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include/sys/time.h: In function `timeval2bintime': /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include/sys/time.h:142: warning: ISO C89 forbids long long integer constants /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/contrib/tcp_wrappers/tcpd.c: In function `main': /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/contrib/tcp_wrappers/tcpd.c:133: warning: ISO C does not support the `%m' printf format *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/libexec/tcpd. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/libexec. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-06-14 19:25:32 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 19:25:32 - ERROR: failed to build world TB --- 2003-06-14 19:25:32 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CVSUP
On Sat, 14 Jun 2003, Blaise Takoudjou wrote:
> hello,
> i make my cvsup last week und cannot install my ports again.
> I do cvsup today again but the problem still there. Wenn i "make install
> clean" the error says:
>
> u-2.05b# make install clean
> /usr/bin/sed: 1: Syntax error: "(" unexpected
> "/usr/ports/Mk/bsd.port.mk", line 801: warning: "/usr/bin/uname -r |
> /usr/bin/sed -e 's/[-(].*//'" returned non-zero status
> /usr/bin/sed: 1: Syntax error: "(" unexpected
Try rebuilding and reinstalling only sed. You may have hit the window
where it was broken last week.
I believe there is an UPDATING entry if you need more details.
--
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: ACPI: Error: Method execution failed
On Sat, 14 Jun 2003, Bjoern A. Zeeb wrote: > already had this with 5.0 as I do with 5.1 and I suspect it's > a broken BIOS ? Or something that the MS interpreter allows and the stringent Intel one does not. This might be fixable ... its overrunning a region definition which could be a simple bug that could be fixed by extracting the DSDT, convert to ASL, fix, recompile, and override. Of course you have to know ASL :) > It is a MSI-6210 w/o SCSI onboard but MP. It's the latest BIOS > revision available for this board - I can check the version > on request but I do not really like rebooting again ;-) You should probably pester MSI and claim Linux has the same issue. The magic L word might wake them up. If you want to be extra neat, use acpidump to extract the dsdt and in bundle that with your dmesg into a tarball I can download. -- 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]"
CVSUP
hello,
i make my cvsup last week und cannot install my ports again.
I do cvsup today again but the problem still there. Wenn i "make install
clean" the error says:
u-2.05b# make install clean
/usr/bin/sed: 1: Syntax error: "(" unexpected
"/usr/ports/Mk/bsd.port.mk", line 801: warning: "/usr/bin/uname -r |
/usr/bin/sed -e 's/[-(].*//'" returned non-zero status
/usr/bin/sed: 1: Syntax error: "(" unexpected
"/usr/ports/Mk/bsd.port.mk", line 1607: warning: "/usr/sbin/pkg_info -P
2>/dev/null | /usr/bin/sed -e 's/.*: //'" returned non-zero status
/usr/bin/sed: 1: Syntax error: "(" unexpected
*** Error code
what i supose to do ?
Thanks;
blaise
"Ich verschicke mich mit der Post an Dich."
Woody guthrie, Mail Myself to you
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compiling under 5.x for 4.x releases?
In message: <[EMAIL PROTECTED]> Karl Denninger <[EMAIL PROTECTED]> writes: : Thanks; I guess that means that for now I keep the production build machine : is 4.8-STABLE, and I keep 5.x as a "play" environment until people move : over. I think, but am not positive, that 4.8-stable boxes can build tip of current again. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pedantic again
Someone added "-std=gnu89 -pedantic" to libcrypto's make; given that stdlib.h and several other places contain "long long", this results in several thousands of warnings about C89. We need to either go modern or not but not try both at once :-) Also usr.bin/window generates LOTS of warnings; I didn't spot just what kind. -- Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compiling under 5.x for 4.x releases?
Thanks; I guess that means that for now I keep the production build machine is 4.8-STABLE, and I keep 5.x as a "play" environment until people move over. The fun will begin when migration begins in significant numbers, but I still need to support both! -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netTired of spam at your company? LOOK HERE! http://childrens-justice.orgWorking for family and children's rights http://diversunion.org LOG IN AND GET YOUR TANK STICKERS TODAY! On Sat, Jun 14, 2003 at 12:28:11PM -0500, Dan Nelson wrote: > In the last episode (Jun 14), Karl Denninger said: > > On Sat, Jun 14, 2003 at 09:43:01AM -0700, Doug White wrote: > > > On Sat, 14 Jun 2003, Karl Denninger wrote: > > > > > > > Can it be done with a command-line switch to the compiler or gcc, > > > > or am I consigned to dual-booting? > > > > > > You mean building apps linked against 4.X libs vs. 5.X? With some > > > creative -L flags you might be able to get it to not use > > > /usr/lib/libc* and use /usr/lib/compat/libc* instead, which has > > > copies of certain 4.X libs in it. > > > > > > Let us know if you get it working :) > > > > Will play with that one > > That won't work. The reason shared libraries get their versions bumped > and the old ones move into compat is that the ABI changes. Unless you > kept the headers for those old shlibs laying around someplace, gcc will > compile programs using the ABI for the libs in /usr/lib. > > > The problem is that I have a lot of users on the 4.x release(s) of > > the OS, and have binary apps that I'm supporting for them. Linking > > static is an option, but does ugly things to the file sizes. > > That will break the first time a 5.0-compiled library decides to use a > syscall not in 4.x. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [-CURRENT tinderbox] failure on i386/pc98
TB --- 2003-06-14 17:43:41 - starting CURRENT tinderbox run for i386/pc98 It looks like we were racing here. I committed my changes at 17:41:59, which is well within the margin of error depending on when the local repo was updated. Warner ___ [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-06-14 17:43:41 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-06-14 17:43:41 - 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-06-14 17:45:52 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] In file included from /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include/sys/stat.h:100, from /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/contrib/tcp_wrappers/tcpd.c:23: /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include/sys/time.h: In function `timespec2bintime': /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include/sys/time.h:125: warning: ISO C89 forbids long long integer constants /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include/sys/time.h: In function `timeval2bintime': /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include/sys/time.h:142: warning: ISO C89 forbids long long integer constants /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/contrib/tcp_wrappers/tcpd.c: In function `main': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/contrib/tcp_wrappers/tcpd.c:133: warning: ISO C does not support the `%m' printf format *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/libexec/tcpd. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/libexec. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-06-14 18:30:13 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 18:30:13 - ERROR: failed to build world TB --- 2003-06-14 18:30:13 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: build flags for a 386DX (5.1)
On Saturday 14 June 2003 10:32, Doug White wrote: > On Fri, 13 Jun 2003, John Nielsen wrote: > > As I indicated, my only hangup is that I'm not familiar enough with the > > new GCC 3 build procedures to know where to put the -march and/or -mcpu > > flags for a buildworld on a separate (newer) machine. > > CPUTYPE=yatta in make.conf. See /etc/defaults/make.conf :) Thank you (and thanks DES!), that's what I needed. I actually looked for /etc/defaults/make.conf, but it doesn't exist on any of my 5.1 systems that were installed from scratch. Now that I look around, though, I see that there is an extensive make.conf(5) manpage, as well as share/examples/etc/make.conf. Live and learn, I guess. Thanks again, JN ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI: Error: Method execution failed
Hi, already had this with 5.0 as I do with 5.1 and I suspect it's a broken BIOS ? It is a MSI-6210 w/o SCSI onboard but MP. It's the latest BIOS revision available for this board - I can check the version on request but I do not really like rebooting again ;-) --- boot messages --- ... acpi0: on motherboard ACPI-1287: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc150e2c0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc150e2c0), AE_AML_REGION_LIMIT ... ACPI-1287: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc150e2c0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc150e2c0), AE_AML_REGION_LIMIT ... + another 30 times --- /boot messages --- -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ ___ [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-06-14 16:57:09 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-06-14 16:57:09 - 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-06-14 16:59:18 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] In file included from /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include/sys/stat.h:100, from /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/contrib/tcp_wrappers/tcpd.c:23: /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include/sys/time.h: In function `timespec2bintime': /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include/sys/time.h:125: warning: ISO C89 forbids long long integer constants /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include/sys/time.h: In function `timeval2bintime': /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include/sys/time.h:142: warning: ISO C89 forbids long long integer constants /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/contrib/tcp_wrappers/tcpd.c: In function `main': /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/contrib/tcp_wrappers/tcpd.c:133: warning: ISO C does not support the `%m' printf format *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/libexec/tcpd. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/libexec. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-06-14 17:43:35 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 17:43:35 - ERROR: failed to build world TB --- 2003-06-14 17:43:35 - tinderbox aborted ___ [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-06-14 16:00:15 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-06-14 16:00:15 - 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-06-14 16:02:57 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] In file included from /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include/sys/stat.h:100, from /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/contrib/tcp_wrappers/tcpd.c:23: /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include/sys/time.h: In function `timespec2bintime': /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include/sys/time.h:125: warning: ISO C89 forbids long long integer constants /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include/sys/time.h: In function `timeval2bintime': /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include/sys/time.h:142: warning: ISO C89 forbids long long integer constants /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/contrib/tcp_wrappers/tcpd.c: In function `main': /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/contrib/tcp_wrappers/tcpd.c:133: warning: ISO C does not support the `%m' printf format *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/libexec/tcpd. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/libexec. *** 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-06-14 16:52:09 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 16:52:09 - ERROR: failed to build world TB --- 2003-06-14 16:52:09 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compiling under 5.x for 4.x releases?
In the last episode (Jun 14), Karl Denninger said: > On Sat, Jun 14, 2003 at 09:43:01AM -0700, Doug White wrote: > > On Sat, 14 Jun 2003, Karl Denninger wrote: > > > > > Can it be done with a command-line switch to the compiler or gcc, > > > or am I consigned to dual-booting? > > > > You mean building apps linked against 4.X libs vs. 5.X? With some > > creative -L flags you might be able to get it to not use > > /usr/lib/libc* and use /usr/lib/compat/libc* instead, which has > > copies of certain 4.X libs in it. > > > > Let us know if you get it working :) > > Will play with that one That won't work. The reason shared libraries get their versions bumped and the old ones move into compat is that the ABI changes. Unless you kept the headers for those old shlibs laying around someplace, gcc will compile programs using the ABI for the libs in /usr/lib. > The problem is that I have a lot of users on the 4.x release(s) of > the OS, and have binary apps that I'm supporting for them. Linking > static is an option, but does ugly things to the file sizes. That will break the first time a 5.0-compiled library decides to use a syscall not in 4.x. > Thus, wondering if I can link the other way and still have it run on > a 4.x box. I guess it depends on what the application is and what > dependancies there are. You will need to keep a 4.x box around (or possibly build a chrooted 4.x environment) to build older binaries. I believe until last month the Linux Mozilla binaries were built on a RedHat 6.2 system, to maximize the number of machines it would run on. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: *IT WORKS* Re: CardBus USB 2.0 Controller (NEC uPD)
In message: <[EMAIL PROTECTED]> Craig Boston <[EMAIL PROTECTED]> writes: : On Fri, 2003-06-13 at 14:17, Tony Naggs wrote: : > Yes, I think you should also do this for Uhci. There are probably not : > many straight Uhci USB 1.1 Cardbus cards, but it is likely some of the : > USB 2.0 cards have an UHCI controller rather than OHCI for USB 1.x : > support. : : Never mind, it seems Warner was one step ahead of us and committed a : similar change to uhci_pci.c two days ago :) Usually I'm about 3 weeks behind people, so it is good to catch up for a change :-) Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.1R + mdconfig -t malloc + cp = Panic!?
Good Morning,
I believe I have stumbled onto a bug in 5.1R.
Here is the problem. If you have a 5.1-R system with, say, 256M of ram
and you mdconfig one or several malloc md-devices totalling around 100M,
if you attempt to use them to capacity, the machine will panic. The
message given is:
panic: kmem_malloc(4096): kmem_map too small: 108347392 total allocated
I have taken some time to track down how to repeat the problem at will...
so perhaps someone can figure it out. The problem does not occur if you
have more memory, I tried it on the exact same configuration, only with 4G
of ram, and there is no panic. I have also tried it on several machines,
with the same results. I would guess that it has something to do with
caching/buffering of the copied files, but that's just a guess.
I have attached a shell script that will trigger the error. I've run this
several times, usually in single-user mode, and without fail on a 256M
machine it will panic. set 'cache_dirs' to any set of directories that
will total 100M or more. On my specific config I have a default 5.1R
install with a minimal install+catman, the dirs listed in the script total
around 110M.
anyone have any ideas? The script that got me started on this whole thing
worked fine on 5.0-Current (Apr 30), but panic'd the machine as of
5.1R. (it's a different script than the one below, but I removed the
non-essential parts of the script to make it less confusing) I should
also mention that the kernel is identical to 'GENERIC' except that
'options POLLING' was included.
Below is the script, and a log of what occurs on a 4G machine, then a 256M
machine...
Any help would be appreciated,
Jay Kuri
- shell script -
#!/bin/sh
## quick script to show the mdconfig -t malloc + fill = panic bug on 5.1-R
PATH=/bin:/sbin:/usr/bin:/usr/sbin
# on a machine with 256M of ram, this is enough to crash it. 112M roughly on
# my machine. Use any combination of directories that will push the limit
# up over 100M
cache_dirs="/bin /sbin /usr/bin /usr/sbin /usr/lib"
# say we have 100M less than we actually have, to make sure we don't
# try to use more memory than we have
space_in_k=`sysctl hw.physmem|awk '{print int($2 / 1024) - 10}'`
echo Ram available to us: $space_in_k
totaldirsize=0
type="malloc"
## This gives us a writable directory so that we can run this off of the 5.1
## install or live cd.
mddev=`/sbin/mdconfig -a -t malloc -s 1M`
/sbin/newfs /dev/${mddev}
/sbin/mount /dev/${mddev} /mnt
mkdir /mnt/copy
/bin/cp /bin/cp /mnt/
for dir in ${cache_dirs}
do
dirsize=`/usr/bin/du -sk ${dir}|/usr/bin/awk '{print int(1024 + ($1 * 1.20))}'`
totaldirsize=`/bin/expr ${totaldirsize} + ${dirsize}`
if [ ${totaldirsize} -le ${space_in_k} ]; then
dirs_mirrored=`echo ${dirs_mirrored} $dir`
mddevice=`/sbin/mdconfig -a -t ${type} -s ${dirsize}k`
/sbin/newfs -i 1024 -U /dev/${mddevice} >/dev/null
/sbin/tunefs -m 2 /dev/${mddevice}
/sbin/mount /dev/${mddevice} /mnt/copy >/dev/null
/mnt/cp -Rp ${dir}/ /mnt/copy
/sbin/umount /mnt/copy >/dev/null
/bin/mkdir -p /mnt${dir}
/sbin/mount /dev/${mddevice} /mnt${dir} >/dev/null
fi
done
- fin -
- 4G log -
# df -k
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/acd0 345120 345120 0 100%/
devfs 1 1 0 100%/dev
/dev/da0s1253888 84416 16947233%/opt
# sh -x test.sh
+ PATH=/bin:/sbin:/usr/bin:/usr/sbin
+ cache_dirs=/bin /sbin /usr/bin /usr/sbin /usr/lib
+ sysctl+ awk {print int($2 / 1024) - 10}
hw.physmem
+ space_in_k=3928684
+ echo Ram available to us: 3928684
Ram available to us: 3928684
+ totaldirsize=0
+ type=malloc
+ /sbin/mdconfig -a -t malloc -s 1M
+ mddev=md0
+ /sbin/newfs /dev/md0
/dev/md0: 1.0MB (2048 sectors) block size 16384, fragment size 2048
using 2 cylinder groups of 0.50MB, 32 blks, 64 inodes.
super-block backups (for fsck -b #) at:
160, 1184
+ /sbin/mount /dev/md0 /mnt
+ mkdir /mnt/copy
+ /bin/cp /bin/cp /mnt/
+ /usr/bin/du+ /usr/bin/awk {print int(1024 + ($1 * 1.20))}
-sk /bin
+ dirsize=12050
+ /bin/expr 0 + 12050
+ totaldirsize=12050
+ [ 12050 -le 3928684 ]
+ echo /bin
+ dirs_mirrored=/bin
+ /sbin/mdconfig -a -t malloc -s 12050k
+ mddevice=md1
+ /sbin/newfs -i 1024 -U /dev/md1
+ /sbin/tunefs -m 2 /dev/md1
tunefs: minimum percentage of free space changes from 8% to 2%
tunefs: should optimize for space with minfree < 8%
+ /sbin/mount /dev/md1 /mnt/copy
+ /mnt/cp -Rp /bin/ /mnt/copy
+ /sbin/umount /mnt/copy
+ /bin/mkdir -p /mnt/bin
+ /sbin/mount /dev/md1 /mnt/bin
+ /usr/bin/du -sk /sbin
+ /usr/bin/awk {print int(1024 + ($1 * 1.20))}
+ dirsize=33913
+ /bin/expr 12050 + 33913
+ totaldirsize=45963
+ [ 45963 -le 3928684 ]
+ echo /bin /sbin
+ dirs_mirrored=/bin /sbin
+ /sbin/mdconfig -a -t malloc -s 33913k
+ mddevice=md2
+ /sbin/newfs -i 1024 -U /dev/md2
+ /sbin/tunefs -m 2 /dev/md2
tunefs: minimu
Re: Compiling under 5.x for 4.x releases?
On Sat, Jun 14, 2003 at 09:43:01AM -0700, Doug White wrote: > On Sat, 14 Jun 2003, Karl Denninger wrote: > > > Can it be done with a command-line switch to the compiler or gcc, or am I > > consigned to dual-booting? > > You mean building apps linked against 4.X libs vs. 5.X? With some creative > -L flags you might be able to get it to not use /usr/lib/libc* and use > /usr/lib/compat/libc* instead, which has copies of certain 4.X libs in it. > > Let us know if you get it working :) Will play with that one > > I know the libraries are there for runtime, but can you build executables > > for them? > > The executables are the exact same format. The problem is that I have a lot of users on the 4.x release(s) of the OS, and have binary apps that I'm supporting for them. Linking static is an option, but does ugly things to the file sizes. Thus, wondering if I can link the other way and still have it run on a 4.x box. I guess it depends on what the application is and what dependancies there are. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netTired of spam at your company? LOOK HERE! http://childrens-justice.orgWorking for family and children's rights http://diversunion.org LOG IN AND GET YOUR TANK STICKERS TODAY! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bluetooth 20030604 and 5.1 release
Hello, --- User Toyboy <[EMAIL PROTECTED]> wrote: > Thanks for the information, I can now surf the internet from my laptop via > bluetooth. I will put up a page on how to do it, even though there are i'm very glad it works for you :) > already a few pages on it already. The problem with my setup was using my > laptop's address instead of the FreeBSd box address. Also, I needed to > clean up my ppp file a little.Thanks for all the help!! please do not forget to send us link to your page. thank you very much for your time and help, max __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compiling under 5.x for 4.x releases?
On Sat, 14 Jun 2003, Karl Denninger wrote: > Can it be done with a command-line switch to the compiler or gcc, or am I > consigned to dual-booting? You mean building apps linked against 4.X libs vs. 5.X? With some creative -L flags you might be able to get it to not use /usr/lib/libc* and use /usr/lib/compat/libc* instead, which has copies of certain 4.X libs in it. Let us know if you get it working :) > I know the libraries are there for runtime, but can you build executables > for them? The executables are the exact same format. -- 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]"
Compiling under 5.x for 4.x releases?
Can it be done with a command-line switch to the compiler or gcc, or am I consigned to dual-booting? I know the libraries are there for runtime, but can you build executables for them? -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netTired of spam at your company? LOOK HERE! http://childrens-justice.orgWorking for family and children's rights http://diversunion.org LOG IN AND GET YOUR TANK STICKERS TODAY! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: build flags for a 386DX (5.1)
On Fri, 13 Jun 2003, John Nielsen wrote: > As I indicated, my only hangup is that I'm not familiar enough with the new > GCC 3 build procedures to know where to put the -march and/or -mcpu flags > for a buildworld on a separate (newer) machine. CPUTYPE=yatta in make.conf. See /etc/defaults/make.conf :) -- 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: build flags for a 386DX (5.1)
On Fri, 13 Jun 2003, Kris Kennaway wrote: > On Fri, Jun 13, 2003 at 12:44:06PM -0700, Doug White wrote: > > On Thu, 12 Jun 2003, John Nielsen wrote: > > > > > [escalated from -questions] > > > > > > Hi folks- > > > > > > I am setting up FreeBSD 5.1-RELEASE on a 386DX. > > > > That works? 386 is not a supported CPU on 5.X. It is missing atomic > > operations that is necesary for proper operation of threading. > > It is if you compile your own kernel, it's just not supported by > default. Ah, ok. I stand corrected. -- 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: bluetooth 20030604 and 5.1 release
Thanks for the information, I can now surf the internet from my laptop via bluetooth. I will put up a page on how to do it, even though there are already a few pages on it already. The problem with my setup was using my laptop's address instead of the FreeBSd box address. Also, I needed to clean up my ppp file a little.Thanks for all the help!! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Shared object not found - library / buildworld issue
I muck my system badly now I can´t even do "vi" or anything really. It won't boot either, only to single mode. I was the one who tried to upgrade from freebsd 4.7-release to 5.1-release. Got the source through cvs did a make buildworld and it failed. tried it a couples of times again and somehow blew my libraries (it happen right after i went to /usr/src/lib/compat/compat4x.i386 and did a make all install, of course it failed)and now is saying /usr/libexec/ld-elf.so.1: Shared object not found. Anytime i try to run a prog, like I said even vi is giving me that error. Seems to me like all libraries are gone since i try to do a make all install in the compat directory. I know I'm a newbie, but I did read the src/UPDATING before doing a make buildworld and couldnt find out anything that explain why the errors were happening. The first time the errors were about the libpthread, then the error happen during the geting an up-to-date make. And now is the library issue. Is there a way to rebuild the libraries? from single mode. Alex _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 Buildworld Failure alloca cdefs.h
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: > The #error line he added is incorrect as it breaks compliant > applications which do not use the nonstandard and nonportable > alloca(3). The attached patch *may* fix this. It is currently undergoing testing. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] Index: sys/sys/cdefs.h === RCS file: /home/ncvs/src/sys/sys/cdefs.h,v retrieving revision 1.70 diff -u -r1.70 cdefs.h --- sys/sys/cdefs.h 14 Jun 2003 06:01:35 - 1.70 +++ sys/sys/cdefs.h 14 Jun 2003 15:04:29 - @@ -142,11 +142,6 @@ #define __section(x) __attribute__((__section__(x))) #endif #endif -#ifdef __GNUC__ -#define alloca(sz) __builtin_alloca(sz) -#else -#error FreeBSD alloca support needed for this compiler -#endif /* XXX: should use `#if __STDC_VERSION__ < 199901'. */ #if !(__GNUC__ == 2 && __GNUC_MINOR__ >= 7 || __GNUC__ >= 3) Index: include/stdlib.h === RCS file: /home/ncvs/src/include/stdlib.h,v retrieving revision 1.48 diff -u -r1.48 stdlib.h --- include/stdlib.h 12 Mar 2003 20:29:58 - 1.48 +++ include/stdlib.h 14 Jun 2003 15:06:02 - @@ -222,7 +222,12 @@ extern void (*_malloc_message)(const char *, const char *, const char *, const char *); -void *alloca(size_t); /* built-in for gcc */ +#ifdef __GNUC__ +#define alloca(sz) __builtin_alloca(sz) +#else +void *alloca(size_t); +#endif + __uint32_t arc4random(void); void arc4random_addrandom(unsigned char *dat, int datlen); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lmc driver in 5.1-release
Hi, I noticed that the lmc driver for T1/T3/HSSI/V.35 cards is now in 5.1-Release. I cvsup'ed from 5.0-Release to 5.1-Release, brought the system up to 5.1 via buildworld/installworld, including the GENERIC kernel. When I try to build a modified kernel with "device lmc", the build fails. The failure is in /usr/src/sys/dev/lmc/if_lmc_fbsd3.c:40:2 "The lmc device requires the old pci compatibility shims" The error states that this driver needs "options COMPAT_OLDPCI", but this doesn't seem to be a valid kernel option in 5.1. Also, /usr/src/UPDATING leads me to believe that devices needing COMPAT_OLDPCI wouldn't be included in 5.x in the future. Yet, this driver never shipped at all until 5.1. The man page gives no indication as to what is needed to get support for this card enabled other than "device lmc". Does anyone know if this card is really supported? Thanks, MikeC ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 Buildworld Failure alloca cdefs.h
"Matt" <[EMAIL PROTECTED]> writes: > Got this on a buildworld from current sources just now, is this possibly > related to the commit to sys/cdefs.h from DES ? I did not touch cdefs.h, David did. The commit message was inaccurate; while it claims that I submitted the patch, I'm only responsible for one line of it: #definealloca(sz) __builtin_alloca(sz) The #error line he added is incorrect as it breaks compliant applications which do not use the nonstandard and nonportable alloca(3). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-RELEASE panic, trace included
On Sat, Jun 14, 2003 at 04:36:28PM +0200, Maxime Henrion wrote: > Pawel Jakub Dawidek wrote: > > On Sat, Jun 14, 2003 at 02:28:33AM -0400, Robert Watson wrote: > > +> If you have the kernel.debug for this kernel, could you send the gdb -k > > +> output of: > > +> > > +> l *in6_pcbbind+0x2a7 > > > > I've looked at objdump -d kernel, and it looks like this is somewhere here: > > > > 214:t = in_pcblookup_local(pcbinfo, > > 215:sin.sin_addr, lport, > > 216:INPLOOKUP_WILDCARD); > > 217:if (t && > > 218:(so->so_cred->cr_uid != > > 219: t->inp_socket->so_cred->cr_uid) && > > 220:(ntohl(t->inp_laddr.s_addr) != > > 221: INADDR_ANY || > > 222: INP_SOCKAF(so) == > > 223: INP_SOCKAF(t->inp_socket))) > > 224:return (EADDRINUSE); > > > > We're talking about this line: > > > > test%eax,%eax > > je c03ac9c7 > > mov 0x64(%eax),%eax > > mov %eax,0xffd0(%ebp) > > => mov 0xc4(%eax),%edx > > mov 0xc4(%esi),%eax > > mov 0x4(%eax),%eax > > cmp 0x4(%edx),%eax > > je c03ac9c7 > > > > We're loading inp_socket->so_cred to edx here. > > So it looks like inp_socket is NULL. Hmm, it is possible? > > Yes, since jlemon's reduced TCP state work. Olivier > ([EMAIL PROTECTED]) has a fix for this, so I added him to the Cc: line. Hi, I believe this patch : http://people.FreeBSD.org/~cognet/in6_pcb.c.diff fixes this issue. Unfortunately, I haven't been able to get it properly reviewed before 5.1-RELEASE. Cheers, Olivier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-RELEASE panic, trace included
Pawel Jakub Dawidek wrote: > On Sat, Jun 14, 2003 at 02:28:33AM -0400, Robert Watson wrote: > +> If you have the kernel.debug for this kernel, could you send the gdb -k > +> output of: > +> > +> l *in6_pcbbind+0x2a7 > > I've looked at objdump -d kernel, and it looks like this is somewhere here: > > 214: t = in_pcblookup_local(pcbinfo, > 215: sin.sin_addr, lport, > 216: INPLOOKUP_WILDCARD); > 217: if (t && > 218: (so->so_cred->cr_uid != > 219: t->inp_socket->so_cred->cr_uid) && > 220: (ntohl(t->inp_laddr.s_addr) != > 221: INADDR_ANY || > 222: INP_SOCKAF(so) == > 223: INP_SOCKAF(t->inp_socket))) > 224: return (EADDRINUSE); > > We're talking about this line: > > test%eax,%eax > je c03ac9c7 > mov 0x64(%eax),%eax > mov %eax,0xffd0(%ebp) > =>mov 0xc4(%eax),%edx > mov 0xc4(%esi),%eax > mov 0x4(%eax),%eax > cmp 0x4(%edx),%eax > je c03ac9c7 > > We're loading inp_socket->so_cred to edx here. > So it looks like inp_socket is NULL. Hmm, it is possible? Yes, since jlemon's reduced TCP state work. Olivier ([EMAIL PROTECTED]) has a fix for this, so I added him to the Cc: line. Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-RELEASE panic, trace included
On Sat, Jun 14, 2003 at 02:28:33AM -0400, Robert Watson wrote: +> If you have the kernel.debug for this kernel, could you send the gdb -k +> output of: +> +> l *in6_pcbbind+0x2a7 I've looked at objdump -d kernel, and it looks like this is somewhere here: 214:t = in_pcblookup_local(pcbinfo, 215:sin.sin_addr, lport, 216:INPLOOKUP_WILDCARD); 217:if (t && 218:(so->so_cred->cr_uid != 219: t->inp_socket->so_cred->cr_uid) && 220:(ntohl(t->inp_laddr.s_addr) != 221: INADDR_ANY || 222: INP_SOCKAF(so) == 223: INP_SOCKAF(t->inp_socket))) 224:return (EADDRINUSE); We're talking about this line: test%eax,%eax je c03ac9c7 mov 0x64(%eax),%eax mov %eax,0xffd0(%ebp) => mov 0xc4(%eax),%edx mov 0xc4(%esi),%eax mov 0x4(%eax),%eax cmp 0x4(%edx),%eax je c03ac9c7 We're loading inp_socket->so_cred to edx here. So it looks like inp_socket is NULL. Hmm, it is possible? -- Pawel Jakub Dawidek [EMAIL PROTECTED] UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net pgp0.pgp Description: PGP signature
i386 Buildworld Failure alloca cdefs.h
Got this on a buildworld from current sources just now, is this possibly related to the commit to sys/cdefs.h from DES ? ===> usr.bin/xlint/llib lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix llib-lposix: In file included from /usr/obj/usr/src/i386/usr/include/sys/types.h:45, from /usr/src/usr.bin/xlint/llib/llib-lposix:39: /usr/obj/usr/src/i386/usr/include/sys/cdefs.h:148:2: #error FreeBSD alloca support needed for this compiler *** Error code 1 Stop in /usr/src/usr.bin/xlint/llib. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [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-06-14 08:44:14 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-06-14 08:44:14 - 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-06-14 08:49:13 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2003-06-14 09:41:14 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Jun 14 09:41:14 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1502: increment of pointer to unknown structure /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1502: arithmetic on pointer to an incomplete type /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c: In function `en_ioctl': /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1591: `SIOCATMGETVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1600: `SIOCATMGVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1606: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/modules/en. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/modules. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC. *** 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-06-14 09:46:59 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 09:46:59 - ERROR: failed to build generic kernel TB --- 2003-06-14 09:46:59 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-06-14 07:19:21 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-06-14 07:19:21 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-06-14 07:24:45 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld >>> 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/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-06-14 08:32:09 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Jun 14 08:32:09 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1502: increment of pointer to unknown structure /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1502: arithmetic on pointer to an incomplete type /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c: In function `en_ioctl': /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1591: `SIOCATMGETVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1600: `SIOCATMGVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1606: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/modules/en. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/modules. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-06-14 08:41:46 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 08:41:46 - ERROR: failed to build generic kernel TB --- 2003-06-14 08:41:46 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rc.firewall not executed?
I just noticed that my ipfw rules were not loaded the last time I rebooted. My rc.conf is included below - has something changed recently so that these settings are not enough? I didn't see anything relevant in UPDATING. My /etc/firewall.conf exists and is readable (and unchanged since 2002). Kris # $FreeBSD: src/etc/defaults/rc.conf,v 1.156 2002/08/30 13:01:42 hm Exp $ hostname="citusc17.usc.edu" # Set this! nisdomainname="cituscdomain"# Set to NIS domain if using NIS (or NO). firewall_enable="YES" # Set to YES to enable firewall functionality firewall_type="/etc/firewall.conf" # Firewall type (see /etc/rc.firewall) sshd_enable="YES" # Enable sshd nfs_client_enable="YES" # This host is an NFS client (or NO). rpc_lockd_enable="YES" # Run NFS rpc.lockd needed for client/server. rpc_statd_enable="YES" # Run NFS rpc.statd needed for client/server. rpcbind_enable="YES"# Run the portmapper service (YES/NO). ntpd_enable="YES" # Run ntpd Network Time Protocol (or NO). nis_client_enable="YES" # We're an NIS client (or NO). defaultrouter="128.125.38.254" # Set to default gateway (or NO). keyrate="fast" # keyboard rate to: slow, normal, fast (or NO). moused_enable="yes" # Run the mouse daemon. moused_type="ps/2" # See man page for rc.conf(5) for available settings. lpd_enable="YES"# Run the line printer daemon. dumpdev="/dev/ad0s1b" # Device name to crashdump to (or NO). network_interfaces="lo0 xl0" ifconfig_xl0="inet 128.125.38.177 netmask 0x" named_enable="YES" # Run named, the DNS server (or NO). named_program="/usr/sbin/named" # path to named, if you want a different one. named_flags="-u bind -g bind" # Flags for named named_chrootdir="/var/chroot/named" # Chroot directory (or "" not to auto-chroot it) named_chroot_autoupdate="YES" # Automatically install/update chrooted # components of named. See /etc/rc.d/named. named_symlink_enable="YES" # Symlink /var/run/named.pid and /var/run/ndc # to their chrooted counterparts. sendmail_enable="YES" sendmail_flags="-bd" sendmail_outbound_enable="NO" sendmail_submit_enable="NO" sendmail_msp_queue_enable="NO" pgp0.pgp Description: PGP signature
[-CURRENT tinderbox] failure on i386/pc98
TB --- 2003-06-14 06:12:47 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-06-14 06:12:47 - 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-06-14 06:16:23 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> 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-06-14 07:12:41 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Jun 14 07:12:42 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1502: increment of pointer to unknown structure /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1502: arithmetic on pointer to an incomplete type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c: In function `en_ioctl': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1591: `SIOCATMGETVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1600: `SIOCATMGVCCS' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1606: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/modules/en. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/modules. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-06-14 07:19:10 - /usr/bin/make returned exit code 1 TB --- 2003-06-14 07:19:10 - ERROR: failed to build generic kernel TB --- 2003-06-14 07:19:10 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
