6.3-RELEASE kernel panic
Hi, just another kernel panic: it may be due to a buggy IBM USB keyboard with integrated touchpad. I got random generation of ESC ^G characters. When unplugging this keyboard from the box for the second time, I got the following panic (admitting that it doesn't look like a keyboard related crash): [root@ /var/crash]# kgdb /boot/kernel/kernel ./vmcore.11 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde fined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. (no debugging symbols found)...Attempt to extract a component of a value that is not a structure pointer. (kgdb) bt #0 0xc06a46a6 in doadump () #1 0xc06a4b76 in boot () #2 0xc06a4e0c in panic () #3 0xc090d1b4 in trap_fatal () #4 0xc090cf1b in trap_pfault () #5 0xc090cb59 in trap () #6 0xc08f9fea in calltrap () #7 0xc07f8a7c in handle_written_filepage () #8 0xc07f7f60 in softdep_disk_write_complete () #9 0xc06ef5e4 in bufdone () #10 0xc066c057 in g_vfs_done () #11 0xc06ef2cb in biodone () #12 0xc0669fc2 in g_io_schedule_up () #13 0xc066a20e in g_up_procbody () #14 0xc068dd74 in fork_exit () #15 0xc08fa04c in fork_trampoline () (kgdb) bt full #0 0xc06a46a6 in doadump () No symbol table info available. #1 0xc06a4b76 in boot () No symbol table info available. #2 0xc06a4e0c in panic () No symbol table info available. #3 0xc090d1b4 in trap_fatal () No symbol table info available. #4 0xc090cf1b in trap_pfault () No symbol table info available. #5 0xc090cb59 in trap () No symbol table info available. #6 0xc08f9fea in calltrap () No symbol table info available. #7 0xc07f8a7c in handle_written_filepage () No symbol table info available. #8 0xc07f7f60 in softdep_disk_write_complete () No symbol table info available. #9 0xc06ef5e4 in bufdone () No symbol table info available. #10 0xc066c057 in g_vfs_done () No symbol table info available. #11 0xc06ef2cb in biodone () No symbol table info available. #12 0xc0669fc2 in g_io_schedule_up () No symbol table info available. #13 0xc066a20e in g_up_procbody () No symbol table info available. #14 0xc068dd74 in fork_exit () No symbol table info available. #15 0xc08fa04c in fork_trampoline () No symbol table info available. Alas, no debugging symbols kernel in default installation :( Petr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[PATCH] ng_nat(4) redirects and rc.d script
Hello! Please test: http://antigreen.org/vadim/freebsd/ng_nat/ (I've ran for a week on a production 6.2 router without any problems). This is a patched version of ng_nat(4) for FreeBSD 6.x, providing support for all libalias(3) features, especially port redirections (before this moment ng_nat(4) has supported only the basic functionality of the library). To compile kernel module: $ make To load it into the running kernel: $ kldload ./ng_nat.ko To view the man page documenting new messages: $ tbl ng_nat.4 | nroff -man | more There is also included a convenient rcNG-style boot script, ng_nat.sh, which allows to easily configure ng_nat(4) nodes and ipfw(8) from rc.conf(5). It is based on a Eugene Grosbein's version and heavily modified by me. Example for two nodes from /etc/rc.conf: ng_nat_nodes=simple full # list of node names # Simple example - all we need is only three lines ng_nat_simple_interface=em1# take IP addr from em1 ng_nat_simple_cookies=50 51# ipfw's netgraph arguments, in then out ng_nat_simple_ipfw_rules=80 90 # ipfw rule numbers to create, in then out # More complex example, in which we need custom ipfw(8) rules for several # selected networks (default rule will catch all) and setup some redirections. ng_nat_full_interface=1.2.3.4 # external alias address ng_nat_full_cookies=60 61 # for custom rules these numbers are used only for deletion on shutdown; # these can duplicate and be more than two ng_nat_full_ipfw_rules=172 172 182 # Actual custom rules - if not defined, rules are created automatically ng_nat_full_ipfw_rule0=172 netgraph 60 ip from 172.16.0.0/25 to any out xmit em0 ng_nat_full_ipfw_rule1=172 netgraph 60 ip from 172.16.0.128/27 to any out xmit em0 ng_nat_full_ipfw_rule2=182 netgraph 61 ip from any to 1.2.3.4 in recv em0 # Set natd(8)-like flags for node (if not specified, node uses same_ports) # Available flags are: log, deny_incoming, same_ports, unregistered_only, # proxy_only, reverse, reset_on_addr_change. The last is new and means that # after aliasing address change internal table should be cleared (breaks # current connections like node restart). ng_nat_full_set_mode=same_ports unregistered_only # Set target address for any unspecified incoming traffic, like natd -t ng_nat_full_set_target=172.16.0.100 # Set up several redirection rules, each can have an optional description # string of up to 63 chars in length. DNS hostnames are disallowed. # natd(8) -redirect_port ng_nat_full_redirect_port0=tcp 172.16.0.1:22 222 ng_nat_full_redirect_port1=udp 172.16.0.2:2300-2399 3300-3399 ng_nat_full_redirect_port1_description=For P2P and VoIP apps ng_nat_full_redirect_port2=tcp 172.16.0.101:80,172.16.0.102:80,172.16.0.103:80 1.2.3.4:80 # -redirect_proto and -redirect_address (including LSNAT) can be # specified the same way, if needed, as long as -proxy_rule. The script also supports additional command-line keywords, along with standard start and stop ones. They include redirect_port, redirect_proto and redirect_address, along with list_redirects. The format is: $ /path/to/ng_nat.sh keyword node_name [arguments] e.g. $ /etc/rc.d/ng_nat.sh redirect_port full tcp 172.16.0.8:80 8080 This allows to add redirections on the fly without need to restart entire node breaking current connections. The list_redirects keyword prints table of all redirects (no matter what type) in a pretty human-readable format. This can be used to obtain ID of specific redirection to make it dynamic or delete it on the fly: $ ngctl msg full: redirectdelete 3 # delete redirection with ID number 3 Enjoy! ;-) -- WBR, Vadim Goncharov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_7: interrupt eating whole cpu core
On Fri, 2008-02-08 at 19:35 +0100, Dominic Fandrey wrote: Tom Evans wrote: On Fri, 2008-02-08 at 17:14 +0100, Dominic Fandrey wrote: Tom Evans wrote: If I try to turn on DMA, I just get WDMA2, which just doesn't cut it: I think any DMA mode is fast enough to handle a DVD drive. There's just no necessity for more. WDMA is not UDMA. Any UDMA variant would be enough. WDMA2 provides a maximum of 16MiB/s, which will frequently lead to buffer underruns viewing a DVD. UDMA2 provides a maximum of 33MiB/s, which IS plenty. 16MB/s is exactly what is needed for 12x DVD access. I think this is the usual speed for a Notebook drive nowadays and it suffices for me. # atacontrol mode acd0 udma5 current mode = WDMA2 Same as for me. I'm satisfied with the speed of the drive. I'm rarely satisfied - I'm quite often not bothered enough to pursue :) Well, if 12x speed is not enough for you, you have to use an external drive. This is not a driver issue. It's just what your drive supports. The chipset supports UDMA6, the drive supports UDMA6, I should be happy with WDMA2 because 'thats what works'? Thanks for your 'help'. I'll continue on here from myself. signature.asc Description: This is a digitally signed message part
Re: Broadcom Netlink BCM5906M
On 2/11/08, Thomas Nyström [EMAIL PROTECTED] wrote: Some questions: Which version of FreeBSD are you running? How do you recover? For example: reboot ifconfig bge0 down; ifconfig bge0 up or what? I tested to ftp a file from my laptop and back again (around 400 MB) and couldn't see any problems, but I'm running at 6.3R. Excuse me this newbie fault... The version is a 7.0-RC2. -- Have a nice day ;-) TooManySecrets Dijo Confucio: Exígete mucho a ti mismo y espera poco de los demás. Así te ahorrarás disgustos. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount of ext2fs volume stuck in D+ state (disk uninterruptible wait)
Joe Peterson wrote: Kris Kennaway wrote: Joe Peterson wrote: I just tried (under FreeBSD 7.0-RC1) to mount an ext2fs volume - I've mounted it before with no trouble on this same FreeBSD version. This time, mount appeared to hang. I noticed that I can see the contents of the volume under the mount point, so the mount seemed to work, but the process is stuff. ps shows: root 1307 0.0 0.0 3156 792 p6 D+5:21PM 0:00.00 mount /mnt/linux-home The ps man page says that D means: Marks a process in disk (or other short term, uninterruptible) wait. Is there any way I can investigate what is going on? I cannot umount (device busy) or break out of the mount command... http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html But unfortunately I do not have KDB and DDB compiled into the kernel. And, obviously, if I reboot, I will lose this opportunity. I suspect this to be an intermittent thing. Is there anything I can extract while the system is running that would be useful? Thanks, Joe You can run kgdb on /dev/mem to obtain the backtrace. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_7: interrupt eating whole cpu core
Tom Evans wrote: On Fri, 2008-02-08 at 19:35 +0100, Dominic Fandrey wrote: Tom Evans wrote: On Fri, 2008-02-08 at 17:14 +0100, Dominic Fandrey wrote: Tom Evans wrote: If I try to turn on DMA, I just get WDMA2, which just doesn't cut it: I think any DMA mode is fast enough to handle a DVD drive. There's just no necessity for more. WDMA is not UDMA. Any UDMA variant would be enough. WDMA2 provides a maximum of 16MiB/s, which will frequently lead to buffer underruns viewing a DVD. UDMA2 provides a maximum of 33MiB/s, which IS plenty. 16MB/s is exactly what is needed for 12x DVD access. I think this is the usual speed for a Notebook drive nowadays and it suffices for me. # atacontrol mode acd0 udma5 current mode = WDMA2 Same as for me. I'm satisfied with the speed of the drive. I'm rarely satisfied - I'm quite often not bothered enough to pursue :) Well, if 12x speed is not enough for you, you have to use an external drive. This is not a driver issue. It's just what your drive supports. The chipset supports UDMA6, the drive supports UDMA6, I should be happy with WDMA2 because 'thats what works'? Thanks for your 'help'. I'll continue on here from myself. I don't know which drive you are using, but mine even only supports 8xDVD-reading so the highest transfer rate is 9.9606 MB/s. There's no way a faster mode would improve anything. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Formatting bug in C++ iostreams when running i386 binary on amd64
Hi list. I've encountered a strange bug deploying one of our C++ applications on amd64. We tend to build most of our applications on i386, even if the deployment box is amd64, as we aren't 100% sure that our code is 64 bit clean yet. The boxes in question both run 6.2-RELEASE, at various kernel release patchsets: FreeBSD dellboy.mintel.co.uk 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #0: Wed Dec 12 16:58:42 GMT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE2650 i386 FreeBSD animal.mintel.co.uk 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #35: Fri Jul 20 10:20:28 BST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE2950 amd64 With an i386 binary running on an amd64 host, when we write a small double, with value close to 0.1, to a C++ iostream, it is formatted incorrectly. I have derived a small test case, which generates the spurious value on the 18th iteration. Compiled on i386: $ g++ -o doubletest -Wall doubletest.cc Run on i386: $ ./doubletest -0.90 0.090.099 0.0999 0.0 0.090.099 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 ^^^ Run on amd64: $ ./doubletest -0.90 0.090.099 0.0999 0.0 0.090.099 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.0:0.1 0.1 If we compile with slightly different linkage (and run again on amd64): $ g++ -Wl,-Bstatic -o doubletest -Wall doubletest.cc -Wl,dy $ ./doubletest-halfstatic -0.90 0.090.099 0.0999 0.0 0.090.099 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.0:0.1 0.1 $ g++ -static -o doubletest -Wall doubletest.cc $ ./doubletest-static -0.90 0.090.099 0.0999 0.0 0.090.099 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 ^^^ This obviously produces unexpected results! Does anyone have any idea what may be triggering this? We currently have two workarounds, one is to compile completely statically (add -static to the compile command line), and compile the app natively 64bit. The former cannot be used on any application that dlopen()s any libraries, and we're not confident with the latter! Tom signature.asc Description: This is a digitally signed message part
Re: Rebuilding World Problems
Quoting Gavin Spomer [EMAIL PROTECTED]: Please forgive me if this is not the appropriate list to post this on. If this is a topic for another, more appropriate FreeBSD list, then would someone please kindly point this guy in the right direction? :) I'm on the security advisory list too and got 2 emails about patches about a month ago. They came with instructions to follow for patching... excellent! Then, the last step has a link to the FreeBSD Handbook's Rebuilding world. Yes, I admit, it's taken me almost a month to get the courage (and find the time) to do this. I'm usually pretty fearless when exploring computer things. I don't really have the best way to backup either. I finally just made tarballs of important directories and scp'd them to one of my Linux machines. I finally got to the point where I booted to single user mode (first time for me) and that's where my problems began. It might be useful to note on the instructions page that you don't have to type boot -s to go into single user mode; it's easier to to just select option #4. First, let me note that step one in rebuilding world should be cd /usr/src, not make buildworld. I guess I was supposed to know that for some reason. Having said that, I figured I would also have to be in /usr/src for the make installworld step. But I couldn't do that! Why? I could cd to /usr, but not /usr/src! So, I decided to go ahead and try the mergemaster -p step. I was given an error that was something like cannot find mergemaster. So I thought that maybe in single user mode my $PATH isn't set, so I thought about entering /sbin/mergemaster -p, but I didn't know if that was the path or not and I chickened out. :( Maybe the fact that I hit Return to choose /bin/sh while going into single user mode instead of my preferred bash had something to do with it? Here's a slightly dumb question: when I get this all figured out, do I have to start all over from make buildworld or can I just continue with booting in single user mode and mergemaster -p? I'm guessing I can just continue, but I thought it was important to ask. Here's a little more intelligent question or two. ;) Is there a way to do this while logged in via ssh? I don't mind making the trip to our computer room so I can select #4 at the FreeBSD prompt, but it's not all that convenient. Also, how long (in general) do the steps mergemaster -p through the final reboot take? I am running FreeBSD on a test server, but if I were to use it for my production servers (which I am considering), the down-time of being in single user mode would be a concern. Thanks to everyone who takes the time to read this. :) Greetings Gavin, Yes, you're quite correct on all accounts. The doc's are a bit terse in these areas. Which, as I read your email, reminds me why I _should_ send-pr a patch with some additional info in these areas. I guess I'm like so many others - once I figured it all out, I got so involved with it all, I completely forgot there was some issues with the docs. NOTE: I'm not the author of the documentation. :) OK I'm going to give you a cheat sheet that I hope you'll find helpful in the future - be aware, this is NOT an excuse to ignore the /usr/src/UPDATING file, as THAT document will QUITE likely contain more timely information regarding little, but important changes, that can make all the difference. That said, here goes: * On an initial install ALWAYS buildworld BEFORE buildkernel * Unless having troubles building a kernel, it is usually best to ensure /etc/make.conf is empty * If REbuilding world/kernel it is usually a good idea to perform the following: cd /usr/obj chflags -R noschg * rm -rf * (see chflags(1) for more information) OK here we go: cd /usr/src/sys/ARCH/conf cp ./GENERIC ./YOUR_CHOSEN_NAME edit ./YOUR_CHOSEN_NAME and adjust as necessary cd /usr/src make buildworld * * * * OPTIONAL * * * * NOTE: SINGLE CPU: make -j4 buildworld NOTE: MULTI CPU: make -j(6 through 10) buildworld * * * * * * * * * * * * make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user mode) fsck -p (optional, but a good idea) mount -u / mount -a -t ufs swapon -a (most cases; optional) cd /usr/src mergemaster -p make installworld mergemaster reboot That was simply a QUICK cheat sheet, and does not replace good research. But I hope it helps. :) --Chris - Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding World Problems
Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]: On 12/02/2008, Chris H. [EMAIL PROTECTED] wrote: Quoting Gavin Spomer [EMAIL PROTECTED]: . . . for some reason. Having said that, I figured I would also have to be in /usr/src for the make installworld step. But I couldn't do that! Why? I could cd to /usr, but not /usr/src! . . . reboot (in single user mode) fsck -p (optional, but a good idea) mount -u / mount -a -t ufs ^^^- this is why you couldn't cd into /usr/src swapon -a (most cases; optional) from note 3 near the end of /usr/src/UPDATING: [3] From the bootblocks, boot -s, and then do fsck -p mount -u / mount -a cd src adjkerntz -i# if CMOS is wall time Also, when doing a major release upgrade, it is required that you boot into single user mode to do the installworld. 2 things I feel worth mentioning - well, 3; I just performed a 5.2 -- 7b4 upgrading using the cheat sheet I provided. All went w/o error/troubles. It (cheat sheet) has also served me well many yrs. w/o issues. I /did/ mention that the cheat sheet I provided was not a replacement for /usr/src/UPDATING. But you /strategically/ removed that part of the post. Context is also lost. -- -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Three interface NAT box
Hi Again. I have a FreeBSD 6.3 box that runs IPNAT and IPFILTER. xl0 is the external NIC and is a dhcp client on a cable network. Naturally, it does IPFILTER. fxp0 is the internal NIC that hands out dhcp leases to clients inside the NAT net. It has the address 192.168.0.1. I also run a caching named on this IPF/IPNAT gateway box. This setup has worked great for years. Recently I added a third NIC ( em0 ) to this gateway box and gave it a static IP 192.168.1.1. I connected em0 to a server via xover cable. I assigned the server on the other end of the xover cable a static address of 192.168.1.5. I reconfigured BIND to listen on em0 and fxp0 both. Connectivity from 192.168.1.1 --- 192.168.1.5 works great. Both machines can talk to each other. All that's missing now is for 192.168.1.5 to be able to reach the Internet through 192.168.1.1. The server with 192.168.1.5 needs to be able to download updates, patches, etc. I can resolve Internet hosts from 192.168.1.5 but that's all. No other protocols seem to reach the www. I am thinking it could be an IPNAT issue or a routing issue; perhaps both. Here's my /etc/ipnat.conf file: map xl0 192.168.0.0/24 - 0.0.0.0/32 portmap tcp/udp auto map xl0 192.168.0.0/24 - 0.0.0.0/32 Here is netstat -r on the gateway machine: defaultL100.VFTTP-18.BSTN UGS 0 6747766xl0 71.173.55/24 link#1 UC 00xl0 L100.VSTTP-18.BSTN 00:90:1a:a0:3d:c4 UHLW2 46xl0653 pool-71-173-55-4.b 00:50:da:11:95:97 UHLW10lo0 localhost localhost UH 00lo0 192.168.0 link#3 UC 00 fxp0 192.168.0.38 00:16:01:70:38:94 UHLW1 420937 fxp0605 192.168.0.39 00:17:f2:49:d5:23 UHLW1 6430 fxp0909 192.168.0.53 00:11:24:21:49:36 UHLW142014 fxp0391 192.168.1 link#2 UC 00em0 Traffic, except for dns queries, is not being passed out from em0 to xl0. Here is netstat -rn on the 192.168.01.5 host: Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG0 0 0 eth0 Here are the first few lines of my ipf.conf file. There are no other rules for em0 anywhere in the file. pass in quick on fxp0 all pass out quick on fxp0 all pass in quick on em0 all pass out quick on em0 all pass in quick on lo0 all pass out quick on lo0 all pass out quick on xl0 all keep state I am thinking of adding these lines to /etc/rc.conf : static_routes=emzero route_emzero=-net 192.168.1.0/24 192.168.0.1 Can anyone tell me if that might work before I potentially hose my network? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on sparc64/sparc64
TB --- 2008-02-13 03:50:06 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 03:50:06 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-02-13 03:50:06 - cleaning the object tree TB --- 2008-02-13 03:50:20 - cvsupping the source tree TB --- 2008-02-13 03:50:21 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2008-02-13 03:50:28 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 03:50:28 - cd /src TB --- 2008-02-13 03:50:28 - /usr/bin/make -B buildworld World build started on Wed Feb 13 03:50:29 UTC 2008 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 [...] cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 04:37:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 04:37:59 - ERROR: failed to build world TB --- 2008-02-13 04:37:59 - tinderbox aborted TB --- 2494.12 user 266.70 system 2873.27 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: another: supervisor read, page not present
What workload, if any, was running at the time?
Have you run memtest on the machine to confirm that there are no memory issues?
-Kip
2008/2/12 Mikhail T. [EMAIL PROTECTED]:
The kernel is from:
FreeBSD 6.3-STABLE #0: Thu Feb 7 ... amd64
The crash:
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0xffe3ffe3e010
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x80414d98
stack pointer = 0x10:0xd62714d0
frame pointer = 0x10:0xff016e6ce9e0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 10919 (kdeinit)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 19h29m22s
Dumping 4095 MB (3 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903
1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 (CTRL-C to abort)
(CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort)
1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487
1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247
1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007
991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703
687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399
383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79
63 47 31 15 ... ok
chunk 2: 2048MB (524288 pages) 2033 2017 2001 1985 1969 1953 1937 1921 1905
1889 1873 1857 1841 1825 1809 1793 1777 1761 1745 1729 1713 1697 1681 1665
1649 1633 1617 1601 1585 1569 1553 1537 1521 1505 1489 1473 1457 1441 1425
1409 1393 1377 1361 1345 1329 1313 1297 1281 1265 1249 1233 1217 1201 1185
1169 1153 1137 1121 1105 1089 1073 1057 1041 1025 1009 993 977 961 945 929
913 897 881 865 849 833 817 801 785 769 753 737 721 705 689 673 657 641 625
609 593 577 561 545 529 513 497 481 465 449 433 417 401 385 369 353 337 321
305 289 273 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
(kgdb) #0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x802ba757 in boot (howto=260)
at ../../../kern/kern_shutdown.c:409
#3 0x802badf1 in panic (
fmt=0xff013c235be0 X\223і[EMAIL PROTECTED])
at ../../../kern/kern_shutdown.c:565
#4 0x8041e31f in trap_fatal (frame=0xff013c235be0,
eva=18446742979543995224) at ../../../amd64/amd64/trap.c:669
#5 0x8041e69c in trap_pfault (frame=0xd6271420, usermode=0)
at ../../../amd64/amd64/trap.c:580
#6 0x8041e953 in trap (frame=
{tf_rdi = -1099511627776, tf_rsi = 16386, tf_rdx = -120260927488,
tf_rcx = 4503599627366400, tf_r8 = 0, tf_r9 = 5, tf_rax = -120260927472,
tf_rbx = 0, tf_rbp = -1093364028960, tf_r10 = 0, tf_r11 = 1, tf_r12 =
34365251584, tf_r13 = -1093364028960, tf_r14 = -1093237757744, tf_r15 = 5,
tf_trapno = 12, tf_addr = -120260927472, tf_flags = 0, tf_err = 0, tf_rip =
-2143203944, tf_cs = 8, tf_rflags = 66178, tf_rsp = -702081824, tf_ss = 0})
at ../../../amd64/amd64/trap.c:353
#7 0x8040456b in calltrap () at ../../../amd64/amd64/exception.S:168
#8 0x80414d98 in pmap_enter_quick_locked (pmap=0xff016e6ce9e0,
va=34365251584, m=0xff0175f3a8d0, prot=5 '\005', mpte=0x0)
at ../../../amd64/amd64/pmap.c:2298
#9 0x80414fdf in pmap_enter_object (pmap=0xff016e6ce9e0,
start=34365251584, end=18446743953448624128, m_start=0xff0175f3a8d0,
prot=5 '\005') at ../../../amd64/amd64/pmap.c:2235
#10 0x803ee67d in vm_map_pmap_enter (map=0xff016e6ce880,
addr=34365251584, prot=5 '\005', object=0xff0174b899a0,
pindex=18446742980345522304, size=18446742980472635672, flags=0)
at ../../../vm/vm_map.c:1539
#11 0x803ee9e4 in vm_map_insert (map=0xff016e6ce880,
object=0xff0174b899a0, offset=0, start=34365251584, end=34365411328,
prot=5 '\005', max=7 '\a', cow=0) at ../../../vm/vm_map.c:1069
#12 0x8027f646 in elf64_map_insert (map=0xff016e6ce880,
object=0xff0174b899a0, offset=0, start=34365251584, end=34365411328,
prot=5 '\005', cow=-1843184) at ../../../kern/imgact_elf.c:327
#13 0x8027f74f in
another: supervisor read, page not present
The kernel is from:
FreeBSD 6.3-STABLE #0: Thu Feb 7 ... amd64
The crash:
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0xffe3ffe3e010
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x80414d98
stack pointer = 0x10:0xd62714d0
frame pointer = 0x10:0xff016e6ce9e0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 10919 (kdeinit)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 19h29m22s
Dumping 4095 MB (3 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903
1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 (CTRL-C to abort)
(CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort)
1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471
1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215
1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959
943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639
623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319
303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok
chunk 2: 2048MB (524288 pages) 2033 2017 2001 1985 1969 1953 1937 1921 1905
1889 1873 1857 1841 1825 1809 1793 1777 1761 1745 1729 1713 1697 1681 1665 1649
1633 1617 1601 1585 1569 1553 1537 1521 1505 1489 1473 1457 1441 1425 1409 1393
1377 1361 1345 1329 1313 1297 1281 1265 1249 1233 1217 1201 1185 1169 1153 1137
1121 1105 1089 1073 1057 1041 1025 1009 993 977 961 945 929 913 897 881 865 849
833 817 801 785 769 753 737 721 705 689 673 657 641 625 609 593 577 561 545 529
513 497 481 465 449 433 417 401 385 369 353 337 321 305 289 273 257 241 225 209
193 177 161 145 129 113 97 81 65 49 33 17 1
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
(kgdb) #0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x802ba757 in boot (howto=260)
at ../../../kern/kern_shutdown.c:409
#3 0x802badf1 in panic (
fmt=0xff013c235be0 X\223і[EMAIL PROTECTED])
at ../../../kern/kern_shutdown.c:565
#4 0x8041e31f in trap_fatal (frame=0xff013c235be0,
eva=18446742979543995224) at ../../../amd64/amd64/trap.c:669
#5 0x8041e69c in trap_pfault (frame=0xd6271420, usermode=0)
at ../../../amd64/amd64/trap.c:580
#6 0x8041e953 in trap (frame=
{tf_rdi = -1099511627776, tf_rsi = 16386, tf_rdx = -120260927488, tf_rcx
= 4503599627366400, tf_r8 = 0, tf_r9 = 5, tf_rax = -120260927472, tf_rbx = 0,
tf_rbp = -1093364028960, tf_r10 = 0, tf_r11 = 1, tf_r12 = 34365251584, tf_r13 =
-1093364028960, tf_r14 = -1093237757744, tf_r15 = 5, tf_trapno = 12, tf_addr =
-120260927472, tf_flags = 0, tf_err = 0, tf_rip = -2143203944, tf_cs = 8,
tf_rflags = 66178, tf_rsp = -702081824, tf_ss = 0})
at ../../../amd64/amd64/trap.c:353
#7 0x8040456b in calltrap () at ../../../amd64/amd64/exception.S:168
#8 0x80414d98 in pmap_enter_quick_locked (pmap=0xff016e6ce9e0,
va=34365251584, m=0xff0175f3a8d0, prot=5 '\005', mpte=0x0)
at ../../../amd64/amd64/pmap.c:2298
#9 0x80414fdf in pmap_enter_object (pmap=0xff016e6ce9e0,
start=34365251584, end=18446743953448624128, m_start=0xff0175f3a8d0,
prot=5 '\005') at ../../../amd64/amd64/pmap.c:2235
#10 0x803ee67d in vm_map_pmap_enter (map=0xff016e6ce880,
addr=34365251584, prot=5 '\005', object=0xff0174b899a0,
pindex=18446742980345522304, size=18446742980472635672, flags=0)
at ../../../vm/vm_map.c:1539
#11 0x803ee9e4 in vm_map_insert (map=0xff016e6ce880,
object=0xff0174b899a0, offset=0, start=34365251584, end=34365411328,
prot=5 '\005', max=7 '\a', cow=0) at ../../../vm/vm_map.c:1069
#12 0x8027f646 in elf64_map_insert (map=0xff016e6ce880,
object=0xff0174b899a0, offset=0, start=34365251584, end=34365411328,
prot=5 '\005', cow=-1843184) at ../../../kern/imgact_elf.c:327
#13 0x8027f74f in elf64_load_section (vmspace=0xff016e6ce880,
object=0xff0174b899a0, offset=16386,
vmaddr=0x800542000 Address 0x800542000 out of bounds, memsz=158641,
filsz=158641, prot=5 '\005', pagesize=4096)
at ../../../kern/imgact_elf.c:386
[releng_7 tinderbox] failure on powerpc/powerpc
TB --- 2008-02-13 02:57:21 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 02:57:21 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2008-02-13 02:57:21 - cleaning the object tree TB --- 2008-02-13 02:57:40 - cvsupping the source tree TB --- 2008-02-13 02:57:40 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2008-02-13 02:57:47 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 02:57:47 - cd /src TB --- 2008-02-13 02:57:47 - /usr/bin/make -B buildworld World build started on Wed Feb 13 02:57:47 UTC 2008 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 [...] cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 03:50:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 03:50:06 - ERROR: failed to build world TB --- 2008-02-13 03:50:06 - tinderbox aborted TB --- 2697.34 user 278.08 system 3164.60 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on i386/i386
TB --- 2008-02-13 02:02:35 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 02:02:35 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2008-02-13 02:02:36 - cleaning the object tree TB --- 2008-02-13 02:02:57 - cvsupping the source tree TB --- 2008-02-13 02:02:57 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2008-02-13 02:03:05 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 02:03:05 - cd /src TB --- 2008-02-13 02:03:05 - /usr/bin/make -B buildworld World build started on Wed Feb 13 02:03:06 UTC 2008 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 [...] cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 02:53:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 02:53:51 - ERROR: failed to build world TB --- 2008-02-13 02:53:51 - tinderbox aborted TB --- 2601.27 user 279.55 system 3075.30 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding World Problems
On 12/02/2008, Chris H. [EMAIL PROTECTED] wrote: Quoting Gavin Spomer [EMAIL PROTECTED]: . . . for some reason. Having said that, I figured I would also have to be in /usr/src for the make installworld step. But I couldn't do that! Why? I could cd to /usr, but not /usr/src! . . . reboot (in single user mode) fsck -p (optional, but a good idea) mount -u / mount -a -t ufs ^^^- this is why you couldn't cd into /usr/src swapon -a (most cases; optional) from note 3 near the end of /usr/src/UPDATING: [3] From the bootblocks, boot -s, and then do fsck -p mount -u / mount -a cd src adjkerntz -i# if CMOS is wall time Also, when doing a major release upgrade, it is required that you boot into single user mode to do the installworld. -- -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RC2 Available
Abdullah Ibn Hamad Al-Marri wrote: How about RELENG_7? will we still get PRERELEASE? Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ I imagine RELENG_7 will stay at PRERELEASE until 7.0-RELEASE is out of the door, at which point it will become 7.0-STABLE. Rgds, Jase. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RC2 Available
On Tue, 2008-02-12 at 10:54 -0800, Abdullah Ibn Hamad Al-Marri wrote: How about RELENG_7? will we still get PRERELEASE? We leave the development branch a release is coming from named PRERELEASE until the release is completed. No matter what we do with the development branches during this phase of a release process it's wrong. Some people think it's strange leaving it name PRERELEASE that long (and this release has dragged on so long it's been in this state for longer than normal...). Other people do an update to a machine, see it named -STABLE, and assume that means the release has happened and wonder why they can't find it. Since that second set of people are typically less in tune with what's going on (don't follow mailing lists, often times less technically oriented, etc.) we've decided to cater to them. I'll shift RELENG_7 to -STABLE as soon as the release is completed. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Rebuilding World Problems
Please forgive me if this is not the appropriate list to post this on. If this is a topic for another, more appropriate FreeBSD list, then would someone please kindly point this guy in the right direction? :) I'm on the security advisory list too and got 2 emails about patches about a month ago. They came with instructions to follow for patching... excellent! Then, the last step has a link to the FreeBSD Handbook's Rebuilding world. Yes, I admit, it's taken me almost a month to get the courage (and find the time) to do this. I'm usually pretty fearless when exploring computer things. I don't really have the best way to backup either. I finally just made tarballs of important directories and scp'd them to one of my Linux machines. I finally got to the point where I booted to single user mode (first time for me) and that's where my problems began. It might be useful to note on the instructions page that you don't have to type boot -s to go into single user mode; it's easier to to just select option #4. First, let me note that step one in rebuilding world should be cd /usr/src, not make buildworld. I guess I was supposed to know that for some reason. Having said that, I figured I would also have to be in /usr/src for the make installworld step. But I couldn't do that! Why? I could cd to /usr, but not /usr/src! So, I decided to go ahead and try the mergemaster -p step. I was given an error that was something like cannot find mergemaster. So I thought that maybe in single user mode my $PATH isn't set, so I thought about entering /sbin/mergemaster -p, but I didn't know if that was the path or not and I chickened out. :( Maybe the fact that I hit Return to choose /bin/sh while going into single user mode instead of my preferred bash had something to do with it? Here's a slightly dumb question: when I get this all figured out, do I have to start all over from make buildworld or can I just continue with booting in single user mode and mergemaster -p? I'm guessing I can just continue, but I thought it was important to ask. Here's a little more intelligent question or two. ;) Is there a way to do this while logged in via ssh? I don't mind making the trip to our computer room so I can select #4 at the FreeBSD prompt, but it's not all that convenient. Also, how long (in general) do the steps mergemaster -p through the final reboot take? I am running FreeBSD on a test server, but if I were to use it for my production servers (which I am considering), the down-time of being in single user mode would be a concern. Thanks to everyone who takes the time to read this. :) - Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0-RC2 Available
How about RELENG_7? will we still get PRERELEASE? Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Formatting bug in C++ iostreams when running i386 binary on amd64
On Tue, Feb 12, 2008 at 06:23:18PM +, Tom Evans wrote: I've encountered a strange bug deploying one of our C++ applications on amd64. We tend to build most of our applications on i386, even if the deployment box is amd64, as we aren't 100% sure that our code is 64 bit clean yet. The boxes in question both run 6.2-RELEASE, at various kernel release patchsets: ... With an i386 binary running on an amd64 host, when we write a small double, with value close to 0.1, to a C++ iostream, it is formatted incorrectly. See kern/102424 and amd64/11. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpMnmcrAJB0I.pgp Description: PGP signature
Re: FreeBSD 7.0-RC2 Available
On Tue, 2008-02-12 at 13:31 -0500, Ken Smith wrote: The second Release Candidate for FreeBSD 7.0 is now available on most of the FTP mirror sites ... Sorry - forgot to include ... The MD5/SHA256 sums for the ISOs are: MD5 (7.0-RC2-amd64-bootonly.iso) = bc37934ad5c29d081738e244ba5d2b3b MD5 (7.0-RC2-amd64-disc1.iso) = 4b4165573f4aa9a3c20b0cfd17509a1d MD5 (7.0-RC2-amd64-disc2.iso) = cb243fe6e3102817fd3d925cbd6d2faf MD5 (7.0-RC2-amd64-disc3.iso) = 87f27c787ff9e19539c38b8c5a6b8214 MD5 (7.0-RC2-amd64-docs.iso) = e66f5067c6c745525fa9f5b2760975c3 MD5 (7.0-RC2-amd64-livefs.iso) = 769771310c3481b13e350ce1213a09c5 MD5 (7.0-RC2-i386-bootonly.iso) = 0a4daf90fc9926b2abe5f0538a6aee95 MD5 (7.0-RC2-i386-disc1.iso) = 7ec7c631f46c891da0da23f4cd4b35e0 MD5 (7.0-RC2-i386-disc2.iso) = 9ddbf85aa9d9a1f135810dd862e0fe34 MD5 (7.0-RC2-i386-disc3.iso) = 9191f36f26aee38680714beb891f8474 MD5 (7.0-RC2-i386-docs.iso) = c23f49125a556971c8a83886ab1f40b7 MD5 (7.0-RC2-i386-livefs.iso) = 5380cf66d547fff489e7fed162b2bdb6 MD5 (7.0-RC2-ia64-bootonly.iso) = a3543488eb2b9ea53196ad5401a52308 MD5 (7.0-RC2-ia64-disc1.iso) = 0e8529042a8192580cb5247e7c1f38e1 MD5 (7.0-RC2-ia64-disc2.iso) = 070cd2fd22ba45ea2d56d82e70c08cfc MD5 (7.0-RC2-ia64-disc3.iso) = 69a14d857bbea6e0e6a7f122fabcc33d MD5 (7.0-RC2-ia64-docs.iso) = 48ee3e3553f23de072f680b175cb52f8 MD5 (7.0-RC2-ia64-livefs.iso) = dbe3cda1ca14cba1aa688e7f13acb7c0 MD5 (7.0-RC2-pc98-bootonly.iso) = 247840a9068aac3c792a60903c1ab3a2 MD5 (7.0-RC2-pc98-disc1.iso) = d28f0985faa62b7e07529ee4383428ae MD5 (7.0-RC2-pc98-livefs.iso) = e71e71b1ae89503c47893392c0c3ba4c MD5 (7.0-RC2-powerpc-bootonly.iso) = a6eec2c87b89158b3e8dae55000b3fb6 MD5 (7.0-RC2-powerpc-disc1.iso) = fb5feb4c0b1c7a9e4feb4c3e3041316e MD5 (7.0-RC2-powerpc-disc2.iso) = ba4f67be13808fa59c8975b753070b86 MD5 (7.0-RC2-powerpc-disc3.iso) = ccc20adb5d95011e069f60490cce94fd MD5 (7.0-RC2-powerpc-docs.iso) = 8a590d2e20d0d8b36e0657a9ab9faca8 MD5 (7.0-RC2-sparc64-bootonly.iso) = febfc56b1101af60bb9a6fbfea149d28 MD5 (7.0-RC2-sparc64-disc1.iso) = 5aead743fecf3a75829238ca619ee6f3 MD5 (7.0-RC2-sparc64-disc2.iso) = c18507722b8cc50d91e0a4050642adeb MD5 (7.0-RC2-sparc64-disc3.iso) = 8545dfaeacdc453d77b8f013714f7730 MD5 (7.0-RC2-sparc64-docs.iso) = a00c2b51c1f3c96533ee26d51c413941 SHA256 (7.0-RC2-amd64-bootonly.iso) = 8d6e5135ef420e224281f55635d11c12880882c83f0946aba3fc93cfba2303f8 SHA256 (7.0-RC2-amd64-disc1.iso) = c67a037a8c5019887f7fb0608cec8cd7ed511df3179746fa108fe35d8bc3feba SHA256 (7.0-RC2-amd64-disc2.iso) = 795e2ba7db32dc4abed226c6920361764ff464055039299c39989c14113765e5 SHA256 (7.0-RC2-amd64-disc3.iso) = e049c47507d215f46c7d81119ed0cb06a6353d9e4d94c4a70c2b90467519ce87 SHA256 (7.0-RC2-amd64-docs.iso) = 4e4c646f6b903421ac0dea3a359a05e4bc216316df5ebdf07c7d3befe45dafd7 SHA256 (7.0-RC2-amd64-livefs.iso) = 1461a11761059e9abb5c7ff5014052b6260b2a048c60f680e23709f3db19a35b SHA256 (7.0-RC2-i386-bootonly.iso) = 9a6f7eef7c6cbef30abaf5c12d1e31830106ccd6a8811d9ed66b46914cb88b79 SHA256 (7.0-RC2-i386-disc1.iso) = eb43bff9e22795aae154fda4db6be52cbd2de92d1ad1702d76714dc99c085edf SHA256 (7.0-RC2-i386-disc2.iso) = 20a1346932ed23607c151c262304fccf79a7722d29efd71090b1972f937a8d45 SHA256 (7.0-RC2-i386-disc3.iso) = 78a5b1f6a56eed23c5a9a2ad209e517f4c52b9769ace8b5d871ccec7dc96edea SHA256 (7.0-RC2-i386-docs.iso) = b29b436c99c3696b25e8a51d39644b96419367a915b6d172eae531e7b66aa16f SHA256 (7.0-RC2-i386-livefs.iso) = 603d8ed6a899e047b23c976b650d6c3a268da3798d9316c97318f53fefe7fa97 SHA256 (7.0-RC2-ia64-bootonly.iso) = 8884b506e3a41115840e123f6ff840218e010d029d42d1a127a19ce4953bb52c SHA256 (7.0-RC2-ia64-disc1.iso) = ce57f3acb8dbada5056b395b371b47f9882d0f7beed35807f5676fbdd4e724aa SHA256 (7.0-RC2-ia64-disc2.iso) = dbcae30b93fc60358f4292c4aab7d77bcd2302eadec8bb8aa1a8adc287fa895a SHA256 (7.0-RC2-ia64-disc3.iso) = ccef862acfafb24a9687107f45cee48e7414c9fb8e212567c8a01e99c8273b16 SHA256 (7.0-RC2-ia64-docs.iso) = 974b43ba60441838ca51ccefe5ffe02af3f166eae51d829124a756f7ee3b16e8 SHA256 (7.0-RC2-ia64-livefs.iso) = 81fa04ef18fee2f34c3e6e4f70ba3605dd81e4cb73db82c2606d2f641c9745e6 SHA256 (7.0-RC2-pc98-bootonly.iso) = f43d981afbb226c49739be98c4d67a3c36d9c8ce5f52496ea4a08082c153b657 SHA256 (7.0-RC2-pc98-disc1.iso) = 8efb77a44430b1ec51bf3887cd2c381637272ca33f69ee66ab035e9439270788 SHA256 (7.0-RC2-pc98-livefs.iso) = 71e2f9cda6a8e9ea210c3cf41f281544fe443e5f1a9f4939b388e6f0e178bc3e SHA256 (7.0-RC2-powerpc-bootonly.iso) = 736606cdbcf5b3357c3092c53f249f71f99efe6e9bd6cf6c803d5f997b9184af SHA256 (7.0-RC2-powerpc-disc1.iso) = e38735b1a7200235d40b51aabcbad52948784ea5177b3fff0684d79e28199366 SHA256 (7.0-RC2-powerpc-disc2.iso) = 0d1d3aa3a3287b9335a7e8f64a4a13d1b351fce7a4873618d4e1bcf91bf742b2 SHA256 (7.0-RC2-powerpc-disc3.iso) = d45b42a21e4866bedaa0773e4a6ef374dd260ea794cdff28af3785a04fcbf683 SHA256 (7.0-RC2-powerpc-docs.iso) = 0e583e9b6a9ebf90dd50035d02d9450527fd35c90af38429edb0280889d48a6e SHA256 (7.0-RC2-sparc64-bootonly.iso) =
FreeBSD 7.0-RC2 Available
The second Release Candidate for FreeBSD 7.0 is now available on most of
the FTP mirror sites, for example
ftp://ftp.freebsd.org/pub/FreeBSD/releases/{$arch}/ISO-IMAGES/7.0/
(where ${arch} is your machine's architecture, e.g. amd64, i386, etc).
If you can please try a local mirror please.
Users of i386 or amd64 systems running FreeBSD 6.2-RELEASE, 6.3-BETA*,
6.3-RC*, 6.3-RELEASE, 7.0-BETA*, or 7.0-RC1 may wish to perform a binary
upgrade to 7.0-RC2 using code recently added to the freebsd-update
utility. On systems running 7.0-BETA4 or 7.0-RC1, the instructions for
minor upgrades at:
http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html
should be followed for this purpose; on systems running older releases
or BETAs (including 7.0 BETAs prior to BETA4) the lengthier instructions
for major upgrades at:
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
(which include rebuilding all software installed from the ports tree)
should be followed.
There is one known issue with a very recently MFCed portion of the
ciss(4) driver that was discovered a little too late for -RC2 but will
be fixed for the release. Some though not all machines have a problem
with a feature added to solve other machines' problems with Adapter
Heartbeat Failed so that portion will be turned into a tunable with the
default disabling it. If you update an already running machine and the
new driver causes you problems you can boot the older kernel, and see
v1.87 of sys/dev/ciss/ciss.c in HEAD for how to fix it (that is what
will be MFCed before the release).
We sincerely hope this will be the last of the public tests for 7.0 and
that the -RELEASE builds will start in about a week and a half. If
bug(s) considered big enough to be show-stoppers are found we will of
course reconsider but hopefully we're in good enough shape now to
proceed with the release.
Thanks for all the help/testing.
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
signature.asc
Description: This is a digitally signed message part
[releng_7 tinderbox] failure on ia64/ia64
TB --- 2008-02-13 02:53:51 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 02:53:51 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-02-13 02:53:51 - cleaning the object tree TB --- 2008-02-13 02:54:06 - cvsupping the source tree TB --- 2008-02-13 02:54:06 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-02-13 02:54:14 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 02:54:14 - cd /src TB --- 2008-02-13 02:54:14 - /usr/bin/make -B buildworld World build started on Wed Feb 13 02:54:17 UTC 2008 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 [...] cc -O2 -pipe -DRESCUE -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -DRESCUE -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -DRESCUE -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -DRESCUE -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /obj/ia64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 03:56:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 03:56:36 - ERROR: failed to build world TB --- 2008-02-13 03:56:36 - tinderbox aborted TB --- 3287.61 user 281.84 system 3765.13 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on i386/pc98
TB --- 2008-02-13 02:05:43 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 02:05:43 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2008-02-13 02:05:43 - cleaning the object tree TB --- 2008-02-13 02:06:04 - cvsupping the source tree TB --- 2008-02-13 02:06:04 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/pc98/supfile TB --- 2008-02-13 02:06:12 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 02:06:12 - cd /src TB --- 2008-02-13 02:06:12 - /usr/bin/make -B buildworld World build started on Wed Feb 13 02:06:12 UTC 2008 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 [...] cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 02:57:21 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 02:57:21 - ERROR: failed to build world TB --- 2008-02-13 02:57:21 - tinderbox aborted TB --- 2600.10 user 288.62 system 3098.07 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expresscard Wireless
Michael Lankton wrote: I bought a laptop with no PCMCIA slot, just expresscard. Instead of using a usb dongle for wireless, I would like to use an expresscard if possible. Ubiquiti makes one that uses atheros chip. Has anyone successfully used an expresscard wifi card in FreeBSD? Any info? It's just another form factor; it'll work fine. For newer Atheros cards you're likely to need the hal at http://www.freebsd.org/~sam. I've not tried the Ubiquiti expresscard so don't know what part is in it. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding World Problems
Date: Tue, 12 Feb 2008 16:34:57 -0800 From: Chris H. [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Quoting Gavin Spomer [EMAIL PROTECTED]: Please forgive me if this is not the appropriate list to post this on. If this is a topic for another, more appropriate FreeBSD list, then would someone please kindly point this guy in the right direction? :) I'm on the security advisory list too and got 2 emails about patches about a month ago. They came with instructions to follow for patching... excellent! Then, the last step has a link to the FreeBSD Handbook's Rebuilding world. Yes, I admit, it's taken me almost a month to get the courage (and find the time) to do this. I'm usually pretty fearless when exploring computer things. I don't really have the best way to backup either. I finally just made tarballs of important directories and scp'd them to one of my Linux machines. I finally got to the point where I booted to single user mode (first time for me) and that's where my problems began. It might be useful to note on the instructions page that you don't have to type boot -s to go into single user mode; it's easier to to just select option #4. First, let me note that step one in rebuilding world should be cd /usr/src, not make buildworld. I guess I was supposed to know that for some reason. Having said that, I figured I would also have to be in /usr/src for the make installworld step. But I couldn't do that! Why? I could cd to /usr, but not /usr/src! So, I decided to go ahead and try the mergemaster -p step. I was given an error that was something like cannot find mergemaster. So I thought that maybe in single user mode my $PATH isn't set, so I thought about entering /sbin/mergemaster -p, but I didn't know if that was the path or not and I chickened out. :( Maybe the fact that I hit Return to choose /bin/sh while going into single user mode instead of my preferred bash had something to do with it? Here's a slightly dumb question: when I get this all figured out, do I have to start all over from make buildworld or can I just continue with booting in single user mode and mergemaster -p? I'm guessing I can just continue, but I thought it was important to ask. Here's a little more intelligent question or two. ;) Is there a way to do this while logged in via ssh? I don't mind making the trip to our computer room so I can select #4 at the FreeBSD prompt, but it's not all that convenient. Also, how long (in general) do the steps mergemaster -p through the final reboot take? I am running FreeBSD on a test server, but if I were to use it for my production servers (which I am considering), the down-time of being in single user mode would be a concern. Thanks to everyone who takes the time to read this. :) Gavin and Chris, It's clearly time to fix this and this is a pretty good start. While it is not the most readable document, the procedure in src/UPDATING is what I always recommend to people as it is going to be rebuilding a system and the handbook is always be bit behind the times. There are also possible differences between , for example, V6.3 vs. V7.0. Comments are interspersed in the document (which I like). Greetings Gavin, Yes, you're quite correct on all accounts. The doc's are a bit terse in these areas. Which, as I read your email, reminds me why I _should_ send-pr a patch with some additional info in these areas. I guess I'm like so many others - once I figured it all out, I got so involved with it all, I completely forgot there was some issues with the docs. NOTE: I'm not the author of the documentation. :) OK I'm going to give you a cheat sheet that I hope you'll find helpful in the future - be aware, this is NOT an excuse to ignore the /usr/src/UPDATING file, as THAT document will QUITE likely contain more timely information regarding little, but important changes, that can make all the difference. That said, here goes: * On an initial install ALWAYS buildworld BEFORE buildkernel And, if you think this does not apply to you, look up ALWAYS in your favorite dictionary! * Unless having troubles building a kernel, it is usually best to ensure /etc/make.conf is empty Note that, once Perl is installed, you need to have the three lines it adds in make.conf. I also believe defining KERNCONF in make.conf is a good idea. * If REbuilding world/kernel it is usually a good idea to perform the following: cd /usr/obj chflags -R noschg * rm -rf * Should never be needed on an initial install, but I don't know of a reason not to. (see chflags(1) for more information) OK here we go: cd /usr/src/sys/ARCH/conf cp ./GENERIC ./YOUR_CHOSEN_NAME edit ./YOUR_CHOSEN_NAME and adjust as necessary I would recommend adding
[releng_7 tinderbox] failure on amd64/amd64
TB --- 2008-02-13 01:12:39 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-13 01:12:39 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-02-13 01:12:39 - cleaning the object tree TB --- 2008-02-13 01:13:13 - cvsupping the source tree TB --- 2008-02-13 01:13:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-02-13 01:13:21 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-13 01:13:21 - cd /src TB --- 2008-02-13 01:13:21 - /usr/bin/make -B buildworld World build started on Wed Feb 13 01:13:23 UTC 2008 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 [...] cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/gpt.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/label.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/map.c cc -O2 -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/sbin/gpt/migrate.c /src/sbin/gpt/migrate.c: In function 'migrate_disklabel': /src/sbin/gpt/migrate.c:121: error: 'FS_ZFS' undeclared (first use in this function) /src/sbin/gpt/migrate.c:121: error: (Each undeclared identifier is reported only once /src/sbin/gpt/migrate.c:121: error: for each function it appears in.) *** Error code 1 Stop in /src/sbin/gpt. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-13 02:05:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-13 02:05:43 - ERROR: failed to build world TB --- 2008-02-13 02:05:43 - tinderbox aborted TB --- 2648.09 user 289.57 system 3183.74 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig fxp0 link0 from rc.conf?
Matthew Herzog wrote: What is the proper way to turn on the checksum offloading for an Intel fxp card? Yes, it's obvious I can do it by hand with ifconfig. That works fine. How do enable it in rc.conf so that it happens upon each reboot? I searched the www for an hour and found no examples. Here's a working example from one of my FreeBSD 6.2 machines: ifconfig_fxp0=inet 10.0.0.1 netmask 255.0.0.0 media 100BaseTX mediaopt full-duplex link0 -- Toomas Aas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UFS snapshot weirdness
Eirik Øverby wrote: I use the snapshots to get a consistent file-backup with history. This one puzzles me to no end. Did you try running fsck on the original file system and on the snapshot? signature.asc Description: OpenPGP digital signature
Re: UFS snapshot weirdness
On Feb 12, 2008, at 1:41 PM, Daniel O'Connor wrote: On Tue, 12 Feb 2008, Eirik Øverby wrote: I am at a total loss here. Is it re-using the first snapshot I ever made of this filesystem, even though I've removed it? Didn't I understand how to create/remove snapshots? Is this a bug? Sure the old md isn't hanging around by mistake or some such? Yes, I am absolutely sure of this. I considered using the snapshot tool, however I need to reduce dependencies to an absolute minimum (as one target environment is very strict on allowing additional software installs).. I use the snapshots to get a consistent file-backup with history. This one puzzles me to no end. /Eirik I have had people recover many files using the snapshot tool in ports (plus a small symlink maker for samba access) and haven't noticed issues like this. On the otherhand I find it can take a long time to make a snapshot (during which time no FS access is allowed). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm when disconnecting sata drives in 7.0-RC2 and 6.3
I've tested both 6.3 and 7.0-RC2, amd64 architecture, and have found the occurrence of an interrupt storm using an ASUS A8N-SLI Premium (nForce 4) motherboard with an AMD Opteron 175. Relevant dmesg output: atapci0: nVidia nForce CK804 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 atapci1: nVidia nForce CK804 SATA300 controller port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd3002000-0xd3002fff irq 21 at device 7.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 atapci2: nVidia nForce CK804 SATA300 controller port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd3001000-0xd3001fff irq 22 at device 8.0 on pci0 ata4: ATA channel 0 on atapci2 ata5: ATA channel 1 on atapci2 atapci3: SiI SiI 3114 SATA150 controller port 0x9000-0x9007,0x9400-0x9403,0x9800-0x9807,0x9c00-0x9c03,0xa000-0xa00f mem 0xd200-0xd20003ff irq 19 at device 10.0 on pci5 ata6: ATA channel 0 on atapci3 ata7: ATA channel 1 on atapci3 ata8: ATA channel 2 on atapci3 ata9: ATA channel 3 on atapci3 Also, there are lines of the form ata0: [ITHREAD] for all of ata0, ata1, atapci1, ata2, ata3, atapci2, ata4, ata5, atapci3, ata6, ata7, ata8, and ata9. There is not such a line for atapci0, I assume by design. Using a Kingwin KF-1000-BK SATA hot swap rack, I can connect and reconnect an SATA hard drive without powering down. This is technically equivalent to using esata. I start with a hard drive in the rack on bootup, and here what I see: [EMAIL PROTECTED] ~]$ atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: ad8 WDC WD800JD-00LSA0/06.01D06 Serial ATA II Slave: no device present ATA channel 5: Master: ad10 ST3250620NS/3.AEG Serial ATA II Slave: no device present ATA channel 6: Master: ad12 ST380815AS/3.AAA Serial ATA v1.0 Slave: no device present ATA channel 7: Master: no device present Slave: no device present ATA channel 8: Master: no device present Slave: no device present ATA channel 9: Master: no device present Slave: no device present [EMAIL PROTECTED] ~]$ vmstat -i interrupt total rate irq19: atapci376 2 irq22: atapci2 1234 35 irq23: nfe0 250 7 cpu0: timer68395 1954 cpu1: timer68177 1947 Total 138132 3946 The system is on ad8, a data drive is connected as ad10, and the removable drive is ad12. ad8 is the nForce sata1 (why it isn't ad4 is ASUS's fault for labelling their sata ports weird), ad10 is the nForce sata2, and ad12 is the SiI 3114 sata1. I haven't cropped anything from the vmstat output, which is to say that yes, I've disabled USB, firewire, and the second ethernet adapter so that I can isolate what's going on. Now I disconnect ad12 (edited output for vmstat): [EMAIL PROTECTED] ~]$ atacontrol detach ata6 [EMAIL PROTECTED] ~]$ vmstat -i irq19: atapci376 0 Next I actually eject the drive: [EMAIL PROTECTED] ~]$ vmstat -i ; sleep 10 ; vmstat -i irq19: atapci3 7266334 24548 irq19: atapci3 8912703 29126 So interrupts are coming at roughly 160,000 per second. The storm continues even after the drive is re-inserted. It stops after reconnecting with atacontrol attach ata6. Some variations on this theme: 1) If I do the above but do not re-insert the drive and try atacontrol attach ata6, I get a ATA_IDENTIFY timeout, and then a kernel panic Fatal trap 12: page fault while in kernel mode. 2) If I try using the nForce sata3 ports, I always get some kind of kernel panic on attaching a drive and atacontrol attach ata4. The NVRAID settings in the BIOS don't matter. I don't know if anything is AHCI here. 3) If I try instead with a Dell Optiplex 330, which uses an Intel ICH7 for sata and which is configured as AHCI in the BIOS (and fbsd shows as AHCI in dmesg), I get exactly the same as I did with the SiI 3114, except that the atacontrol attach when no device is attached simply detects no devices (no kernel panic), and actually stops the interrupt storm. When it is storming, the rate is more like 190,000 per second. 4) I've tried using a JMicron JMB363 sata port on an add-in PCIex1 card (with most recent firmware), but the attached drive is never detected, on either computer. No interrupt storm occurs through any of atacontrol attach or
Re: RELENG_7: interrupt eating whole cpu core
Tom Evans wrote: The chipset supports UDMA6, the drive supports UDMA6, Are you sure about that? What brand/model is that? I don't think I've ever seen an atapi CD/DVD drive that supported more than UDMA3. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UFS snapshot weirdness
On Tue, 12 Feb 2008, Eirik Øverby wrote: I am at a total loss here. Is it re-using the first snapshot I ever made of this filesystem, even though I've removed it? Didn't I understand how to create/remove snapshots? Is this a bug? Sure the old md isn't hanging around by mistake or some such? I have had people recover many files using the snapshot tool in ports (plus a small symlink maker for samba access) and haven't noticed issues like this. On the otherhand I find it can take a long time to make a snapshot (during which time no FS access is allowed). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
UFS snapshot weirdness
Hi all, I've been making a wrapper script for the backup tool 'duplicity', allowing me to create config files for each resource, wherein I define whether a snapshot should be made prior to backing up the resource or not. Now I find that my snapshots never change The script creates a snapshot, creates md device, mounts it, runs backup against the mounted snapshot, dismounts, removes md device, and rm -f's the snapshot file. The problem is .. Whenever I look into the mounted snapshot, a given directory looks like so: drwxr-xr-x 3 root wheel 512 Jan 29 15:25 . drwxr-xr-x 18 root wheel 512 Jan 29 13:49 .. -rw--- 1 root wheel 1281 Jan 31 17:12 .bash_history -rw-r--r-- 2 root wheel 786 Jan 29 13:00 .cshrc -rw-r--r-- 1 root wheel 143 Jan 29 13:00 .k5login -rw-r--r-- 1 root wheel 293 Jan 29 13:00 .login -rw-r--r-- 2 root wheel 253 Jan 29 13:00 .profile drwxr-xr-x 2 root wheel 512 Jan 29 13:00 .ssh However, when looking into the same directory outside the snapshot, it looks like so: -rw--- 1 root wheel 2961 Feb 12 00:39 .bash_history -rw-r--r-- 2 root wheel786 Jan 29 13:00 .cshrc -rw-r--r-- 1 root wheel143 Jan 29 13:00 .k5login drwx-- 2 root wheel512 Feb 11 16:23 .links -rw-r--r-- 1 root wheel293 Jan 29 13:00 .login -rw-r--r-- 2 root wheel253 Jan 29 13:00 .profile drwxr-xr-x 2 root wheel512 Jan 29 13:00 .ssh -rw-r--r-- 1 root wheel 948424 Feb 11 13:14 bsd-jdk16- patches-3.tar.bz2 -rw-r--r-- 1 root wheel 46938731 Feb 11 16:23 diablo-jdk- freebsd6.amd64.1.5.0.07.01.tbz -rw-r--r-- 1 root wheel2116124 Feb 11 13:11 jdk-6u3-fcs-bin-b05- jrl-24_sep_2007.jar -rw-r--r-- 1 root wheel8608204 Feb 11 13:11 jdk-6u3-fcs- mozilla_headers-b05-unix-24_sep_2007.jar -rw-r--r-- 1 root wheel 116791442 Feb 11 13:15 jdk-6u3-fcs-src-b05- jrl-24_sep_2007.jar The snapshot was made just now, long after those additional files were placed in the snapshot. I am at a total loss here. Is it re-using the first snapshot I ever made of this filesystem, even though I've removed it? Didn't I understand how to create/remove snapshots? Is this a bug? Any input is appreciated. Thanks, /Eirik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Expresscard Wireless
I bought a laptop with no PCMCIA slot, just expresscard. Instead of using a usb dongle for wireless, I would like to use an expresscard if possible. Ubiquiti makes one that uses atheros chip. Has anyone successfully used an expresscard wifi card in FreeBSD? Any info? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
