Re: Cannot cross compile 9.1-RELEASE to i386
On 06/12/2012 22:26, David Demelier wrote: Hello, I'm trying to make as small as possible a FreeBSD installation for my Alix 2D2, I did it with 8.1-RELEASE so, a lot of changes appeared I think. I'm trying to make TARGET_ARCH=i386 buildworld and it fails at: ===> sys/boot/i386/gptboot (all) Warning: Object directory not changed from original /usr/src/sys/boot/i386/gptboot cc -DBOOTPROG=\"gptboot\" -O1 -DGPT -DUFS1_AND_UFS2 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/gptboot/../../common -I/usr/src/sys/boot/i386/gptboot/../common -I/usr/src/sys/boot/i386/gptboot/../btx/lib -I. -I/usr/src/sys/boot/i386/gptboot/../boot2 -I/usr/src/sys/boot/i386/gptboot/../../.. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -c gptldr.S ld -static -N --gc-sections -nostdlib -e start -Ttext 0x7c00 -o gptldr.out gptldr.o objcopy -S -O binary gptldr.out gptldr.bin make: don't know how to make /usr/src/sys/boot/i386/gptboot/../btx/lib/crt0.o. Stop *** [all] Error code 2 Stop in /usr/src/sys/boot/i386. *** [all] Error code 1 Stop in /usr/src/sys/boot. *** [all] Error code 1 Stop in /usr/src/sys. *** [sys.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. My src.conf is like that: WITHOUT_JAIL=yes WITHOUT_ACPI=yes WITHOUT_AMD=yes WITHOUT_APM=yes WITHOUT_ATM=yes WITHOUT_AUDIT=yes WITHOUT_AUTHPF=yes WITHOUT_BIND=yes WITHOUT_BLUETOOTH=yes WITHOUT_BSNMP=yes WITHOUT_CALENDAR=yes WITHOUT_CDDL=yes WITHOUT_CLANG=yes WITHOUT_CTM=yes WITHOUT_CVS=yes WITHOUT_CXX=yes WITHOUT_DICT=yes WITHOUT_EXAMPLES=yes WITHOUT_FDT=yes WITHOUT_FLOPPY=yes WITHOUT_FREEBSD_UPDATE=yes WITHOUT_GAMES=yes WITHOUT_GCOV=yes WITHOUT_GDB=yes WITHOUT_HTML=yes WITHOUT_INFO=yes WITHOUT_IPFILTER=yes WITHOUT_IPFW=yes WITHOUT_IPX=yes WITHOUT_JAIL=yes WITHOUT_KERBEROS=yes WITHOUT_KERNEL_SYMBOLS=yes WITHOUT_LOCATE=yes WITHOUT_MAKE=yes WITHOUT_NDIS=yes WITHOUT_NIS=yes WITHOUT_NLS=yes WITHOUT_OBJC=yes WITHOUT_PAM=yes WITHOUT_PORTSNAP=yes WITHOUT_PPP=yes WITHOUT_RCMDS=yes WITHOUT_SHAREDOCS=yes WITHOUT_SYSINSTALL=yes Did I added a WITHOUT_ that could break or is it a cross-compile issue? (Host version is amd64). Cheers, The problem was an old CPUTYPE defined in the make.conf, working now :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ipv6_addrs_IF aliases in rc.conf(5)
Hello, I wrote a small patch for /etc/network.subr to add support for ipv6_addrs_IF aliases in rc.conf(5) to match the already existing ipv4_addrs_IF aliases for ipv4 addresses. With this patch the ipv6 aliases can be written like: ipv6_addrs_re0="2001:db8::::1/64 2001:db8::::2/64" Only this syntax is supported, it's not possible to use the "prefixlen nn" syntax in the list. The patch is against a recent 9-STABLE, last changed rev of network.subr on my SVN checkout is r242187. I don't have a CURRENT system to test if it applies to CURRENT as well. The patch can be found attached to a PR I sent: http://www.freebsd.org/cgi/query-pr.cgi?pr=174225 I wrote this patch inspired by a question on the FreeBSD forums: http://forums.freebsd.org/showthread.php?t=36136 Please test and report if it works for you :) Regards, Kimmo Paasiala ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Using dhclient on WAN if on a box serving DHCP to LAN if
Hi all Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare for 9.1, but I think it should be largely irrelevant of version. I have a freebsd router that provides all the things a soho router should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface connects to a ADSL modem operating in bridge mode. My ISP has recently forced a change on to me, in order to get service I have to connect via DHCP, in order for them to give me my static IP. Apparently this makes their lives a lot easier. Even knowing the IP, netmask, broadcast and router is not enough, no service will flow unless a DHCP request has been registered. Relevant rc.conf, ale0 is the WAN, em0 is the LAN ifconfig_ale0="DHCP" ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" gateway_enable="YES" dhcpd_enable="YES" dhcpd_flags="-q" dhcpd_ifaces="em0" dhcpd_conf="/usr/local/etc/dhcpd.conf" With this configuration, the default route is over the LAN iface. This causes the dhclient for ale0 to get a response from the local dhcpd server, not the ISP dhcpd server. This drove me potty! Can anyone explain why dhcpd, having been told only to listen for DHCP on em0, responds to ale0? Could this be related to my pf rules, or is it down to the default route being incorrect? Changing rc.conf to this allows the network to come up correctly: ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast xx.xx.110.255 DHCP" defaultrouter="xx.xx.110.1" This relies on me knowing that these are the values that dhclient on the WAN iface will receive from my ISP's DHCP server. How would I achieve this setup if this information was dynamic or otherwise unknowable? My ISP could easily change my gateway IP, the only guarantee I have is that my allocated IP is static. So: 1) Why does the LAN dhcpd respond to the WAN dhclient? 2) Is there a better way of specifying this setup, so that it does not have hard coded addresses in there? Thanks in advance for any pointers. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
On Fri, 07 Dec 2012 12:38:45 +0100, Tom Evans wrote: Hi all Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare for 9.1, but I think it should be largely irrelevant of version. I have a freebsd router that provides all the things a soho router should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface connects to a ADSL modem operating in bridge mode. My ISP has recently forced a change on to me, in order to get service I have to connect via DHCP, in order for them to give me my static IP. Apparently this makes their lives a lot easier. Even knowing the IP, netmask, broadcast and router is not enough, no service will flow unless a DHCP request has been registered. Relevant rc.conf, ale0 is the WAN, em0 is the LAN ifconfig_ale0="DHCP" ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" gateway_enable="YES" dhcpd_enable="YES" dhcpd_flags="-q" dhcpd_ifaces="em0" dhcpd_conf="/usr/local/etc/dhcpd.conf" What is in dhcpd.conf? Ronald. With this configuration, the default route is over the LAN iface. This causes the dhclient for ale0 to get a response from the local dhcpd server, not the ISP dhcpd server. This drove me potty! Can anyone explain why dhcpd, having been told only to listen for DHCP on em0, responds to ale0? Could this be related to my pf rules, or is it down to the default route being incorrect? Changing rc.conf to this allows the network to come up correctly: ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast xx.xx.110.255 DHCP" defaultrouter="xx.xx.110.1" This relies on me knowing that these are the values that dhclient on the WAN iface will receive from my ISP's DHCP server. How would I achieve this setup if this information was dynamic or otherwise unknowable? My ISP could easily change my gateway IP, the only guarantee I have is that my allocated IP is static. So: 1) Why does the LAN dhcpd respond to the WAN dhclient? 2) Is there a better way of specifying this setup, so that it does not have hard coded addresses in there? Thanks in advance for any pointers. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
Hi, On 7 Dec 2012, at 11:38, Tom Evans wrote: > Hi all > > Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare > for 9.1, but I think it should be largely irrelevant of version. > > I have a freebsd router that provides all the things a soho router > should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface > connects to a ADSL modem operating in bridge mode. > > My ISP has recently forced a change on to me, in order to get service > I have to connect via DHCP, in order for them to give me my static IP. > Apparently this makes their lives a lot easier. Even knowing the IP, > netmask, broadcast and router is not enough, no service will flow > unless a DHCP request has been registered. > > Relevant rc.conf, ale0 is the WAN, em0 is the LAN > > ifconfig_ale0="DHCP" > ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" > gateway_enable="YES" > > dhcpd_enable="YES" > dhcpd_flags="-q" > dhcpd_ifaces="em0" > dhcpd_conf="/usr/local/etc/dhcpd.conf" > > With this configuration, the default route is over the LAN iface. This > causes the dhclient for ale0 to get a response from the local dhcpd > server, not the ISP dhcpd server. This drove me potty! Can anyone > explain why dhcpd, having been told only to listen for DHCP on em0, > responds to ale0? Could this be related to my pf rules, or is it down > to the default route being incorrect? > > Changing rc.conf to this allows the network to come up correctly: > > ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast > xx.xx.110.255 DHCP" > defaultrouter="xx.xx.110.1" > > This relies on me knowing that these are the values that dhclient on > the WAN iface will receive from my ISP's DHCP server. How would I > achieve this setup if this information was dynamic or otherwise > unknowable? My ISP could easily change my gateway IP, the only > guarantee I have is that my allocated IP is static. > > So: > > 1) Why does the LAN dhcpd respond to the WAN dhclient? Maybe DHCP requests are getting passed across the gateway. Try setting gateway_enable="NO" temporarily, if that stops the unwanted behaviour then configure pf to block DHCP requests crossing the gateway. > 2) Is there a better way of specifying this setup, so that it does not > have hard coded addresses in there? > > Thanks in advance for any pointers. > > Tom > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
On Fri, 2012-12-07 at 11:38 +, Tom Evans wrote:
> Hi all
>
> Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare
> for 9.1, but I think it should be largely irrelevant of version.
>
> I have a freebsd router that provides all the things a soho router
> should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface
> connects to a ADSL modem operating in bridge mode.
>
> My ISP has recently forced a change on to me, in order to get service
> I have to connect via DHCP, in order for them to give me my static IP.
> Apparently this makes their lives a lot easier. Even knowing the IP,
> netmask, broadcast and router is not enough, no service will flow
> unless a DHCP request has been registered.
>
> Relevant rc.conf, ale0 is the WAN, em0 is the LAN
>
> ifconfig_ale0="DHCP"
> ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0"
> gateway_enable="YES"
>
> dhcpd_enable="YES"
> dhcpd_flags="-q"
> dhcpd_ifaces="em0"
> dhcpd_conf="/usr/local/etc/dhcpd.conf"
>
> With this configuration, the default route is over the LAN iface. This
> causes the dhclient for ale0 to get a response from the local dhcpd
> server, not the ISP dhcpd server. This drove me potty! Can anyone
> explain why dhcpd, having been told only to listen for DHCP on em0,
> responds to ale0? Could this be related to my pf rules, or is it down
> to the default route being incorrect?
>
> Changing rc.conf to this allows the network to come up correctly:
>
> ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast
> xx.xx.110.255 DHCP"
> defaultrouter="xx.xx.110.1"
>
> This relies on me knowing that these are the values that dhclient on
> the WAN iface will receive from my ISP's DHCP server. How would I
> achieve this setup if this information was dynamic or otherwise
> unknowable? My ISP could easily change my gateway IP, the only
> guarantee I have is that my allocated IP is static.
>
> So:
>
> 1) Why does the LAN dhcpd respond to the WAN dhclient?dhcpd_ifaces="sk0"
> 2) Is there a better way of specifying this setup, so that it does not
> have hard coded addresses in there?
>
> Thanks in advance for any pointers.
>
> Tom
I've been running this exact setup for years (although it's still
running on freebsd 7.x because I've been too lazy to update a setup that
works so well).
Make sure you're telling dhcpd to only listen for broadcasts on the lan
interface. You can do this in rc.conf with
dhcpd_ifaces="sk0"
Also, I found that dhcpd (at least the old version I'm running) whines
if you don't have a subnet statement for the wan interface in the config
even if it's not serving on that interface, so my dhcpd.conf has this
# The subnet that should be active via the cable modem.
# We don't serve it (no range statement).
# I don't remember why I need the broadcast-address thing here.
# It might be to match what comcast sets via their dhcp.
subnet 24.6.2.0 netmask 255.255.254.0 {
not authoritative;
option routers 24.6.2.1;
option broadcast-address255.255.255.255;
}
-- Ian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
On Fri, Dec 7, 2012 at 12:25 PM, Ronald Klop
wrote:
> On Fri, 07 Dec 2012 12:38:45 +0100, Tom Evans
>
> What is in dhcpd.conf?
>
> Ronald.
>
dhcpd.conf is straightforward:
option domain-name "x.com";
option subnet-mask 255.255.255.0;
default-lease-time 3600;
max-lease-time 86400;
ddns-update-style none;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.200 192.168.1.253;
option domain-name-servers 192.168.1.1;
option routers 192.168.1.1;
}
Ian: I had already specified dhcpd_ifaces to be just the internal
interface, which is why it had confused me! I haven't yet got any
complaints from dhcpd about the subnet on the extif, so far as I can
see.
For clarity, this is my pf.conf, which again is very simple:
ext_if="ale0"
int_if="{ em0 }"
antispoof_if="{ lo0 em0 }"
tcp_services="{ 22 443 }"
icmp_types="{ echoreq echorep unreach }"
# options
set block-policy return
set loginterface $ext_if
set skip on lo0
# tables
table persist
# scrub
#match in all scrub (no-df)
# nat/rdr
nat on $ext_if from !($ext_if) -> ($ext_if:0)
nat-anchor "ftp-proxy/*"
rdr-anchor "ftp-proxy/*"
# filter rules
block in
pass out keep state
anchor "ftp-proxy/*"
antispoof quick for $antispoof_if
block in quick on $ext_if from label "ssh bruteforce"
pass in on $ext_if inet proto tcp from any to ($ext_if) port
$tcp_services flags S/SA keep state
pass in inet proto icmp all icmp-type $icmp_types keep state
pass in quick on $int_if
Ideally, I would like the configuration to not specify the details of
the configuration. Eg, if I instead had a dynamic IP, how could I
configure that, as I would not know IP, netmask, broadcast and router
addresses beforehand.
Cheers
Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Using dhclient on WAN if on a box serving DHCP to LAN if
On Fri, Dec 7, 2012 at 5:38 AM, Tom Evans wrote: > Hi all > > Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare > for 9.1, but I think it should be largely irrelevant of version. > > I have a freebsd router that provides all the things a soho router > should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface > connects to a ADSL modem operating in bridge mode. > > My ISP has recently forced a change on to me, in order to get service > I have to connect via DHCP, in order for them to give me my static IP. > Apparently this makes their lives a lot easier. Even knowing the IP, > netmask, broadcast and router is not enough, no service will flow > unless a DHCP request has been registered. > > Relevant rc.conf, ale0 is the WAN, em0 is the LAN > > ifconfig_ale0="DHCP" > ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" > gateway_enable="YES" > > dhcpd_enable="YES" > dhcpd_flags="-q" > dhcpd_ifaces="em0" > dhcpd_conf="/usr/local/etc/dhcpd.conf" > > With this configuration, the default route is over the LAN iface. This > causes the dhclient for ale0 to get a response from the local dhcpd > server, not the ISP dhcpd server. This drove me potty! Can anyone > explain why dhcpd, having been told only to listen for DHCP on em0, > responds to ale0? Could this be related to my pf rules, or is it down > to the default route being incorrect? > I have seen some modems that were configured to bridge mode or use public IPs that would also hand out the private IPs. Try changing your LAN IP address to not be on the 192.168.1.0/24 network (i.e. 192.168.2.0/24). Then see if you pull a 192.168.1.x or the LAN IP address. -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Help review the FAQ
While it's very, very minute detail, I think that in #officesuite there should be "Apache OpenOffice" not "Apache Open Office" as they were very careful even bureaucratic [*] if I reckon correctly, when choosing new branding. [*] They have "branding initiative guidelines" and held vote- https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767462.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
machine can reboot again
Hi, After an update of 9-stable from 14 Nov. to 6 Dec. my machine does not hang on reboot and shutdown anymore. I don't know what broke it (a while ago) and I don't know what fixed it, but is very nice! Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Help review the FAQ
On 12/07/12 21:36, Jakub Lach wrote: While it's very, very minute detail, I think that in #officesuite there should be "Apache OpenOffice" not "Apache Open Office" as they were very careful even bureaucratic [*] if I reckon correctly, when choosing new branding. [*] They have "branding initiative guidelines" and held vote- https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache Hi Jakub You can file a patch for it Index: en_US.ISO8859-1/books/faq/book.xml === --- en_US.ISO8859-1/books/faq/book.xml(revision 40304) +++ en_US.ISO8859-1/books/faq/book.xml(working copy) @@ -3523,7 +3523,7 @@ The open-source - url="http://www.openoffice.org";>Apache Open Office + url="http://www.openoffice.org";>Apache OpenOffice and http://www.libreoffice.org";>LibreOffice office suites work natively on &os;. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Help review the FAQ
On 7 December 2012 16:11, Bas Smeelen wrote: > On 12/07/12 21:36, Jakub Lach wrote: >> >> While it's very, very minute detail, I think that in #officesuite >> there should be "Apache OpenOffice" not "Apache Open Office" >> as they were very careful even bureaucratic [*] if I reckon correctly, >> when choosing new branding. >> >> [*] They have "branding initiative guidelines" and held vote- >> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache Patch sent to mentor for approval. Thanks! -- Eitan Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.1-RC3 reproducible kernel panic in ffs_valloc?
Hello :-) After days of problem with my system storage (?) I think I have located the issue, or at least I am able to reproduce it, please take a look at attached picture (photo of a crash). http://i45.tinypic.com/23qtcx.jpg At first I thought that was the Ext2 filesystem issue, but then I have replaced the filesystem to UFS2-SU+J (which increased transfer efficiency and dramatically reduced filesystem check time compared to Ext2) but the issue persisted. This problem occurs also when only / is mounted (no additional storage locations only the OS). Right now I am not sure if this is storage related anymore... but there are some remarks about ffs. Crash occurs after I start Xorg (Kde3 WM, all packages installed from binary packages with portinstall). Please let me know if you need additional information/tests :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.1-RC3 LiveCD missing features
Hello :-) I have tried to chceck for badblocks on my / but I did not find badblocks program on LiveCD and there is no option to install it. This is very useful utility, please add it as part of LiveCD :-) Also there is a problem with DHCP based workstations using LiveCD -although interface gets configured it is impossible to update /etc/resolv.conf (by dhclient and by hand) and so this workstation pretty useless for IPv4 (is it more usable on IPv6?). Please update :-) Thank you :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Cannot build kernel since subr_devstat.c commit
Relevant bit is- /usr/src/sys/kern/subr_devstat.c:295:2: error: implicit declaration of function 'DTRACE_DEVSTAT_BIO_START' is invalid in C99 [-Werror,-Wimplicit-function-declaration] DTRACE_DEVSTAT_BIO_START(); ^ /usr/src/sys/kern/subr_devstat.c:390:2: error: implicit declaration of function 'DTRACE_DEVSTAT_BIO_DONE' is invalid in C99 [-Werror,-Wimplicit-function-declaration] DTRACE_DEVSTAT_BIO_DONE(); ^ /usr/src/sys/kern/subr_devstat.c:390:2: note: did you mean 'DTRACE_DEVSTAT_BIO_START'? DTRACE_DEVSTAT_BIO_DONE(); ^~~ DTRACE_DEVSTAT_BIO_START /usr/src/sys/kern/subr_devstat.c:295:2: note: 'DTRACE_DEVSTAT_BIO_START' declared here DTRACE_DEVSTAT_BIO_START(); ^ 2 errors generated. *** [subr_devstat.o] Error code 1 http://svnweb.freebsd.org/base/stable/9/sys/kern/subr_devstat.c?view=log -- View this message in context: http://freebsd.1045724.n5.nabble.com/Cannot-build-kernel-since-subr-devstat-c-commit-tp5767503.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_9 tinderbox] failure on arm/arm
TB --- 2012-12-07 23:42:21 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-12-07 23:42:21 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-12-07 23:42:21 - starting RELENG_9 tinderbox run for arm/arm TB --- 2012-12-07 23:42:21 - cleaning the object tree TB --- 2012-12-07 23:42:21 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-12-07 23:42:21 - cd /tinderbox/RELENG_9/arm/arm TB --- 2012-12-07 23:42:21 - /usr/local/bin/svn cleanup /src TB --- 2012-12-07 23:43:08 - /usr/local/bin/svn update /src TB --- 2012-12-07 23:43:17 - At svn revision 244000 TB --- 2012-12-07 23:43:18 - building world TB --- 2012-12-07 23:43:18 - CROSS_BUILD_TESTING=YES TB --- 2012-12-07 23:43:18 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-07 23:43:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-07 23:43:18 - SRCCONF=/dev/null TB --- 2012-12-07 23:43:18 - TARGET=arm TB --- 2012-12-07 23:43:18 - TARGET_ARCH=arm TB --- 2012-12-07 23:43:18 - TZ=UTC TB --- 2012-12-07 23:43:18 - __MAKE_CONF=/dev/null TB --- 2012-12-07 23:43:18 - cd /src TB --- 2012-12-07 23:43:18 - /usr/bin/make -B buildworld >>> World build started on Fri Dec 7 23:43:19 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Dec 8 00:40:04 UTC 2012 TB --- 2012-12-08 00:40:04 - cd /src/sys/arm/conf TB --- 2012-12-08 00:40:04 - /usr/sbin/config -m AVILA TB --- 2012-12-08 00:40:04 - building AVILA kernel TB --- 2012-12-08 00:40:04 - CROSS_BUILD_TESTING=YES TB --- 2012-12-08 00:40:04 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-08 00:40:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-08 00:40:04 - SRCCONF=/dev/null TB --- 2012-12-08 00:40:04 - TARGET=arm TB --- 2012-12-08 00:40:04 - TARGET_ARCH=arm TB --- 2012-12-08 00:40:04 - TZ=UTC TB --- 2012-12-08 00:40:04 - __MAKE_CONF=/dev/null TB --- 2012-12-08 00:40:04 - cd /src TB --- 2012-12-08 00:40:04 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Sat Dec 8 00:40:04 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/kern/subr_devstat.c cc1: warnings being treated as errors /src/sys/kern/subr_devstat.c: In function 'devstat_start_transaction_bio': /src/sys/kern/subr_devstat.c:295: warning: implicit declaration of function 'DTRACE_DEVSTAT_BIO_START' /src/sys/kern/subr_devstat.c:295: warning: nested extern declaration of 'DTRACE_DEVSTAT_BIO_START' [-Wnested-externs] /src/sys/kern/subr_devstat.c: In function 'devstat_end_transaction_bio': /src/sys/kern/subr_devstat.c:390: warning: implicit declaration of function 'DTRACE_DEVSTAT_BIO_DONE' /src/sys/kern/subr_devstat.c:390: warning: nested extern declaration of 'DTRACE_DEVSTAT_BIO_DONE' [-Wnested-externs] *** Error code 1 Stop in /obj/arm.arm/src/sys/AVILA. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-12-08 00:41:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-12-08 00:41:35 - ERROR: failed to build AVILA kernel TB --- 2012-12-08 00:41:35 - 2521.42 user 519.58 system 3554.69 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-arm-arm.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
nullfs changes MFC
Hi, I am going to merge latest batch of the nullfs improvements into stable/9. This will bring up significant performance enchancements due to use of the shared locks for lookups if the lower layer supports it, much better caching on the nullfs layer, and proper handling of the text segments on the nullfs. Also, it should improve the error recovery and some corner cases with locking. Unfortunately, the merge would break KBI for VFS, since it needs 5 new VOP slots, and only three spares are left. We already are very liberal with the VFS KBI, so I do not feel that the merge is not acceptable, due to the benefits it brings to the nullfs. The merge is available at http://people.freebsd.org/~kib/misc/nullfs_9.1.patch pgpHMMlThCzYf.pgp Description: PGP signature
Re: 9.1-RC3 LiveCD missing features
Quoth CeDeROM : > > I have tried to chceck for badblocks on my / but I did not find badblocks > program on LiveCD and there is no option to install it. This is very useful > utility, please add it as part of LiveCD :-) There is no badblocks utility in the FreeBSD base system. It wouldn't be much use with modern disks in any case, since they do automatic bad-block mapping internally and once any bad blocks become visible the disk is failing and you will likely see lots more very soon. The Linux utility is available as part of the sysutils/e2fsprogs port. If you just want to test a disk there are examples in the dd(1) manpage. Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: nullfs changes MFC
On Sat, Dec 08, 2012 at 03:01:09AM +0200, Konstantin Belousov wrote: > Hi, > I am going to merge latest batch of the nullfs improvements into > stable/9. This will bring up significant performance enchancements due > to use of the shared locks for lookups if the lower layer supports it, > much better caching on the nullfs layer, and proper handling of the text > segments on the nullfs. Also, it should improve the error recovery and > some corner cases with locking. > > Unfortunately, the merge would break KBI for VFS, since it needs 5 new > VOP slots, and only three spares are left. We already are very liberal > with the VFS KBI, so I do not feel that the merge is not acceptable, due > to the benefits it brings to the nullfs. > > The merge is available at > http://people.freebsd.org/~kib/misc/nullfs_9.1.patch Sorry I haven't checked the latest zfs related MFC, but for some time there was an issue with nullfs improvements and zfs, will this mfc be synchronize with the mfc of the related zfs fixes? regards, Bapt pgpZ7YTsbpo9F.pgp Description: PGP signature
Re: nullfs changes MFC
On Sat, Dec 08, 2012 at 03:58:16AM +0100, Baptiste Daroussin wrote: > On Sat, Dec 08, 2012 at 03:01:09AM +0200, Konstantin Belousov wrote: ... > > The merge is available at > > http://people.freebsd.org/~kib/misc/nullfs_9.1.patch > > > Sorry I haven't checked the latest zfs related MFC, but for some time > there was an issue with nullfs improvements and zfs, will this mfc be > synchronize with the mfc of the related zfs fixes? Corresponding zfs fixes were already merged to stable/9, as I was told. Cc:ed Andrey to confirm it once more. pgp5JWVCeKD4r.pgp Description: PGP signature
[releng_9 tinderbox] failure on amd64/amd64
TB --- 2012-12-07 23:01:30 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-12-07 23:01:30 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-12-07 23:01:30 - starting RELENG_9 tinderbox run for amd64/amd64 TB --- 2012-12-07 23:01:30 - cleaning the object tree TB --- 2012-12-07 23:01:30 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-12-07 23:01:30 - cd /tinderbox/RELENG_9/amd64/amd64 TB --- 2012-12-07 23:01:30 - /usr/local/bin/svn cleanup /src TB --- 2012-12-07 23:02:37 - /usr/local/bin/svn update /src TB --- 2012-12-07 23:02:53 - At svn revision 243999 TB --- 2012-12-07 23:02:54 - building world TB --- 2012-12-07 23:02:54 - CROSS_BUILD_TESTING=YES TB --- 2012-12-07 23:02:54 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-07 23:02:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-07 23:02:54 - SRCCONF=/dev/null TB --- 2012-12-07 23:02:54 - TARGET=amd64 TB --- 2012-12-07 23:02:54 - TARGET_ARCH=amd64 TB --- 2012-12-07 23:02:54 - TZ=UTC TB --- 2012-12-07 23:02:54 - __MAKE_CONF=/dev/null TB --- 2012-12-07 23:02:54 - cd /src TB --- 2012-12-07 23:02:54 - /usr/bin/make -B buildworld >>> World build started on Fri Dec 7 23:02:55 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sat Dec 8 01:55:34 UTC 2012 TB --- 2012-12-08 01:55:34 - generating LINT kernel config TB --- 2012-12-08 01:55:34 - cd /src/sys/amd64/conf TB --- 2012-12-08 01:55:34 - /usr/bin/make -B LINT TB --- 2012-12-08 01:55:34 - cd /src/sys/amd64/conf TB --- 2012-12-08 01:55:34 - /usr/sbin/config -m LINT TB --- 2012-12-08 01:55:34 - building LINT kernel TB --- 2012-12-08 01:55:34 - CROSS_BUILD_TESTING=YES TB --- 2012-12-08 01:55:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-08 01:55:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-08 01:55:34 - SRCCONF=/dev/null TB --- 2012-12-08 01:55:34 - TARGET=amd64 TB --- 2012-12-08 01:55:34 - TARGET_ARCH=amd64 TB --- 2012-12-08 01:55:34 - TZ=UTC TB --- 2012-12-08 01:55:34 - __MAKE_CONF=/dev/null TB --- 2012-12-08 01:55:34 - cd /src TB --- 2012-12-08 01:55:34 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 8 01:55:34 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sat Dec 8 02:26:37 UTC 2012 TB --- 2012-12-08 02:26:37 - cd /src/sys/amd64/conf TB --- 2012-12-08 02:26:37 - /usr/sbin/config -m LINT-NOINET TB --- 2012-12-08 02:26:37 - building LINT-NOINET kernel TB --- 2012-12-08 02:26:37 - CROSS_BUILD_TESTING=YES TB --- 2012-12-08 02:26:37 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-08 02:26:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-08 02:26:37 - SRCCONF=/dev/null TB --- 2012-12-08 02:26:37 - TARGET=amd64 TB --- 2012-12-08 02:26:37 - TARGET_ARCH=amd64 TB --- 2012-12-08 02:26:37 - TZ=UTC TB --- 2012-12-08 02:26:37 - __MAKE_CONF=/dev/null TB --- 2012-12-08 02:26:37 - cd /src TB --- 2012-12-08 02:26:37 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET >>> Kernel build for LINT-NOINET started on Sat Dec 8 02:26:37 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT-NOINET completed on Sat Dec 8 02:56:25 UTC 2012 TB --- 2012-12-08 02:56:25 - cd /src/sys/amd64/conf TB --- 2012-12-08 02:56:25 - /usr/sbin/config -m LINT-NOINET6 TB --- 2012-12-08 02:56:25 - building LINT-NOINET6 kernel TB --- 2012-12-08 02:56:25 - CROSS_BUILD_TESTING=YES TB --- 2012-12-08 02:56:25 - MAKEOBJDIRPREFIX=/obj TB --- 2012-12-08 02:56:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-12-08 02:56:25 - SRCCONF=/dev/null TB --- 2012-12-08 02:56:25 - TARGET=amd64 TB --- 2012-12-08 02:56:25 - TARGET_ARCH=amd64 TB --- 2012-12-08 02:56:25 - TZ=UTC TB --- 2012-12-08 02:56:25 - __MAKE_CONF=/dev/null TB --- 2012-12-08 02:56:25 - cd /src TB --- 2012-12-08 02:56:25 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET6 >>> Kernel build for LINT-NOINET6 started on Sat Dec 8 02:56:26 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everyth
Re: 9.1-RC3 reproducible kernel panic in ffs_valloc?
This problem was caused by corrupted UFS2-SU+J (9.x default) filesystem marked as clean where journal showed no issues, running fsck -t ufs -fy solved the issue! http://i47.tinypic.com/35m1qxk.jpg I guess filesystem related kernel panic should enforce full filesystem chceck (some filesystem flag or journal date modification to enforce full check). Maybe it is possible to stop the OS in that case, perform some sort of fsck running from memory, and then continue the OS with no crash? :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
