Re: umass causes panic on 7 amd64
On Mon, May 12, 2008 at 04:19:27PM -0700, Steve Franks wrote: On Mon, May 12, 2008 at 3:50 PM, Roland Smith [EMAIL PROTECTED] wrote: On Mon, May 12, 2008 at 01:38:51PM -0700, Steve Franks wrote: I have added options USB DEBUG to my kernconf file (DYSTANT). Here is the backtrace: Steve [EMAIL PROTECTED] /usr/obj/usr/src/sys/DYSTANT]$ sudo kgdb kernel.debug /var/crash/vmcore.6 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined 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 amd64-marcel-freebsd. Unread portion of the kernel message buffer: umass0: OLYMPUS C-700 Ultra Zoom, class 0/0, rev 1.10/1.00, addr 3 on uhub2 umass0: SCSI over (unknown 0x00); quirks = 0x0100 panic: /usr/src/sys/dev/usb/umass.c:1453: Unknown proto 0x100 It looks like the camera is not returning a wire protocol. You definitely need to take this to the -usb list. Still shouldn't cause a panic, should it? Yes it should. It calls the 'panic' function. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOY3iUqfsIc.pgp Description: PGP signature
Re: Status of ZFS in -stable?
Hello Pierre-Luc, Tuesday, May 13, 2008, 6:26:49 AM, you wrote: Hi, I would like to know if the memory allocation problem with zfs has been fixed in -stable? Is zfs considered to be more stable now? It's still an experimental feature in FreeBSD, though the memory allocation issues might have been already fixed (I don't know personally). Many people have reported success stories when using ZFS on FreeBSD, however there's also plenty of them who are reporting substantial issues when using ZFS. It's up to your own decision whether ZFS will be feasible for you; you might want to test it before deploying it to the production environment. -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Status of ZFS in -stable?
Daniel Gerzo wrote: Hello Pierre-Luc, Tuesday, May 13, 2008, 6:26:49 AM, you wrote: Hi, I would like to know if the memory allocation problem with zfs has been fixed in -stable? Is zfs considered to be more stable now? It's still an experimental feature in FreeBSD, though the memory allocation issues might have been already fixed (I don't know personally). Many people have reported success stories when using ZFS on FreeBSD, however there's also plenty of them who are reporting substantial issues when using ZFS. It's up to your own decision whether ZFS will be feasible for you; you might want to test it before deploying it to the production environment. FWIW, I've been using ZFS on two jail servers for months without any visible issues. 7.0-RELEASE/amd64. Hugo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Changing an installed system from i386 to amd64
I have a box currently running i386 which I want to change over to run amd64. I have installed a second drive into the machine on which I have put a basic install of amd64, and have compiled up the world and kertnel from source. Can I simply switch the original partition over by mounting it up and doin a 'make installworld' with an approrpiate DESTDIR set ? I guess what I am asking is if anything else is different between the two versions aside from the actual binaries themselves (i.e. directory layout and the like). -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Status of ZFS in -stable?
Hugo Silva wrote: Daniel Gerzo wrote: Hello Pierre-Luc, Tuesday, May 13, 2008, 6:26:49 AM, you wrote: Hi, I would like to know if the memory allocation problem with zfs has been fixed in -stable? Is zfs considered to be more stable now? I am using ZFS on my laptop as a typical, heavily used desktop system. I experience some concurrency issues (the machine locks up for a moment while the system is doing some work). I am doing some heavy tasks like compiling OpenOffice in my free time. I experience very strange behaviour when running out of space (one of the applications dumped a huge core file that could not be rm(1)'ed because of Not enough space!). In my personal opinion, the stability of FreeBSD 7.0-stable with ZFS (and maybe other features are at fault, e.g. wpi driver, my ACPI) is not very good. I experience strange hangs and hick-ups, sometimes panics. The good thing about ZFS is that no matter how hard it dies it usually comes up good (once I had to wait a while to let it recover after reboot and reboot the system again cleanly since some files were missing and just re-appeared later). I am bound to use ZFS because it saves me a lot of space (no need for partition split), but as soon as I setup some more external disk space for my laptop I may consider not using it anymore. --Marcin signature.asc Description: OpenPGP digital signature
Re: Changing an installed system from i386 to amd64
I did roughly the same but slightly different method: ah, and did it work o.k. ? -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete French wrote: | I did roughly the same but slightly different method: | | ah, and did it work o.k. ? | | -pete. | Yes and I have been using the system for almost 8 months now as my primary desktop -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgps78ACgkQk8GFzCrQm4DjkwCgg6MUz2w73LZwKV2RorIyxeT7 sjAAn1Wh9NBQsBuR1Ftm2ashZEtc5SEk =W4Z2 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete French wrote: | I have a box currently running i386 which I want to change over to | run amd64. I have installed a second drive into the machine on which | I have put a basic install of amd64, and have compiled up the world | and kertnel from source. | | Can I simply switch the original partition over by mounting it up | and doin a 'make installworld' with an approrpiate DESTDIR set ? | I guess what I am asking is if anything else is different between | the two versions aside from the actual binaries themselves (i.e. | directory layout and the like). I did roughly the same but slightly different method: 0. Deinstall all ports but record what they are 1. FTP the enitre kernel and base system from what ever version you want 2. Install the kernel with (this assumes 7/8-current): ~ ./install.sh generic 3. Install the base system ~ ./install.sh 4. Reboot (optional) 4a. Get the most recent sources and remake the system with those (optional) 4b. Get and install any other sysinstall distfiles you wish (optional) 4c. Run make delete-old and make delete-old-libs 5. Reinstall all your ports Note: ./install.sh done from what ever dir you put the distfiles in (*DO NOT* intermix kernel and base) 4c is almost not optional -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgprqUACgkQk8GFzCrQm4CtVACeJg9f0SnPG1I1nix/948kHJit GCkAoO8U2D/WCvPJ1Mz3icCCQaQD6180 =o5mP -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
On Tue, 13 May 2008 15:18:36 BST Pete French [EMAIL PROTECTED] wrote:
I have a box currently running i386 which I want to change over to
run amd64. I have installed a second drive into the machine on which
I have put a basic install of amd64, and have compiled up the world
and kertnel from source.
Can I simply switch the original partition over by mounting it up
and doin a 'make installworld' with an approrpiate DESTDIR set ?
I guess what I am asking is if anything else is different between
the two versions aside from the actual binaries themselves (i.e.
directory layout and the like).
In the 64 bit FreeBSD world, /usr/lib32 contains libraries
for the x86 binaries and /lib, /usr/lib contain 64 bit
libraries so a straight install may mess things up. At the
very least you should backup your 32 bit root partition --
but I have a feeling my advice is already too late :-)
Ideally a simple perl script can automate most of this job.
May be all you have to do is something like this:
for a in lib usr/lib usr/local/lib
do
mv $DESTDIR/$a $DESTDIR/${a}32
done
echo 'ldconfig32_paths=/usr/lib32 /usr/local/lib32' $DESTIDIR/etc/rc.conf
Most all old 32 bit ports should work but upgrading them can
mess things up. All the new compiles will generate 64 bit
binaries but any port dependencies on a shared library will
be wrong. Also, not all 32 bit ports work on 64 bit. May be
the trick is to save port directory names for all installed
ports (e.g. shell/zsh), then blow them all away (after saving
a copy somewhere) and then install them again.
This really needs to be part of sysinstall.
PS: the following may come in handy. Save it in ~/bin/ldd32.
#!/bin/sh
# ldd for i386 binaries
for i in ${1+$@}
do
echo $i:
env LD_32_TRACE_LOADED_OBJECTS=1 $i
done
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
In the 64 bit FreeBSD world, /usr/lib32 contains libraries for the x86 binaries and /lib, /usr/lib contain 64 bit libraries so a straight install may mess things up. At the very least you should backup your 32 bit root partition -- but I have a feeling my advice is already too late :-) heh, not too late, am not *that* impulsive - but I don't see why this will mess things up ? Surely thats exactly what I want to happen, for /usr/lib to become 64 bit to go with the binaries which will aalso become 64 bit. This isn't a running system bear in mind - it a disc from another system which is mounted on a separte machine running 64 bitA, so theres no issue with the binaries needing to run during the changeover. Most all old 32 bit ports should work but upgrading them can mess things up. All the new compiles will generate 64 bit binaries but any port dependencies on a shared library will there are no ports on the amchine so this shouldnt be an issue. PS: the following may come in handy. Save it in ~/bin/ldd32. thats useful, thanks! -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
On Tue, 13 May 2008 16:59:11 BST Pete French [EMAIL PROTECTED] wrote: In the 64 bit FreeBSD world, /usr/lib32 contains libraries for the x86 binaries and /lib, /usr/lib contain 64 bit libraries so a straight install may mess things up. At the very least you should backup your 32 bit root partition -- but I have a feeling my advice is already too late :-) heh, not too late, am not *that* impulsive - but I don't see why this will mess things up ? Surely thats exactly what I want to happen, for /usr/lib to become 64 bit to go with the binaries which will aalso become 64 bit. If you run only the latest standard binaries you are right but typically one acquires useful things over time and it is not always possible to recompile them and also, why bother. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
good/best practices for gmirror and gjournal on a pair of disks?
I've been running many of my systems for some time now using gmirror on a pair of identical disks, as described by Ralf at: http://people.freebsd.org/~rse/mirror/ Each disk has single slice that covers almost all of the disk. These slices are combined into the gmirror device (gm0), which is then carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e (/tmp), and gm0f (/usr). My latest machine is using Seagate 1TB disks so I thought I should add gjournal to the mix to avoid ugly fsck's if/when the machine doesn't shut down cleanly. I ended up just creating a gm0f.journal and using it for /usr, which basically seems to be working. I'm left with a couple of questions though: - I've read in the gjournal man page that when it is ... configured on top of gmirror(8) or graid3(8) providers, it also keeps them in a consistent state... I've been trying to figure out if this simply falls out of how gjournal works or if there's explicity collusion with gmirror/graid3 but can't come up with a satisfactory explanation. Can someone walk me through it? Since I'm only gjournal'ing a portion of the underlying gmirror device I assume that I don't get this benefit? - I've also read in the gjournal man page ... that sync(2) and fsync(2) system calls do not work as expected anymore. Does this invalidate any of the assumptions made by various database packages such as postgresql, sqlite, berkeley db, etc about if/when/whether their data is safely on the disk? - What's the cleanest gjournal adaptation of rse's two-disk-mirror-everything setup that would be able to avoid tedious gmirror sync's. The best I've come up with is to do two slices per disk, combine the slices into a pair of gmirror devices, bsdlabel the first into gm0a (/), gm0b (swap), gm0d (/var) and gm0e (/tmp) and bsdlabel the second into a gm1f which gets a gjournal device. Alternatively, would it work and/or make sense to give each disk a single slice, combine them into a gmirror, put a gjournal on top of that, then use bsdlabel to slice it up into partitions? Is anyone using gjournal and gmirror for all of the system on a pair of disks in some other configuration? Thanks, g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 issues fixed? upgrade timing?
Hi all, I only just now subscribed, so my apologies if this has been covered and my cursory search missed it. I am seeing a similar issue to the one described in the email below (pasted from a web listing of this list). That is, my ssh connection will occasionally be dropped with the message Disconnecting: Bad packet length 3190815048. (the number is not always the same). I can reliably reproduce this with `cat /dev/urandom | od -c` from a FreeBSD-current box (a few weeks old, actually, since the build was broken when I last tried to update) as well as from a mac running OS X 10.4 . The system that is killing my connections is: FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Mar 25 14:53:51 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERIPHRASIS amd64 Any thoughts would be appreciated. -Ben Kaduk -- random message from this thread, for some context - * From: Jeremy Chadwick [EMAIL PROTECTED] * Date: Mon, 12 May 2008 05:32:07 -0700 On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: On Mon, 12 May 2008 11:37:53 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: FWIW, I had major troubles with re(4) around 7.0-release, and a while later (I had to use patches). After upgrading to 7-stable on 2008-04-12, re(4) is working for me without patches. (sigh).. it seems that I spoke to soon. Murphy just showed up. I still get ssh disconnects (see below) on connections _to_ the machine when transferring largish amounts of data (like when upgrading a port). Here is one example (portupgrading the jdk port): /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='amd64' -DRELEASE='1.6.0_03-p4' -DFULL_VERSION='1.6.0_03-p4-root_12_may_2008_13_25-b00' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c Disconnecting: Bad packet length 3601161525. The machine is running: [EMAIL PROTECTED] uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 and has been up for about 14 days: [EMAIL PROTECTED] uptime 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. Is this machine using pf(4) at all? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote: Alexandre Sunny Kovalenko wrote: I seem to be able to lock my machine by going into wpa_cli and asking it to 'reassoc'. The reason for question mark after hard is that debug information (caused by wlandebug and athdebug) is being printed on the console. The only way to get machine's attention is to hold power button for 8 seconds. So this is just livelock due to console debug msgs. I am not sure, I have parsed this well enough, so I will try to clarify: machine becomes unresponsive *without* any debugging turned on, to an extent that pressing the power button twice *does not* generate ACPI console message (something to the tune of going into S5 already -- gimme a break). If I turn ath debugging on, I do see those messages, and only them, scrolling on the console. Note: manual reassociation is just the handy way to reproduce the problem -- I have had machine locking up on me the whole day long completely on its own. Below are, what I think, relevant pieces of information. If anything is missing, please, chastise me appropriately and will do my best to provide. I have rigged firewire console, but am unable to break into the debugger locally or remotely. I see no log msgs. I am sorry -- mailman must have eaten it up -- I have posted them here now: http://members.verizon.net/~akovalenko/Misc/reassoc.log.gz While I am on the subject, I would appreciate couple of the troubleshooting suggestions: * is there any way to get sysctl dev.ath.0.debug to appear, other then defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h? options ATH_DEBUG That does not seem to work for if_ath built as the module, sorry for not being clear in that respect. * is there minimal, but still usable mask for athdebug and wlandebug? I have started with 0x and kept trimming likely high-volume settings until output slowed down to the reasonable pace. Why do you want debug msgs from ath? The debug msgs from wlandebug depend on what you're trying to debug. Because neither wpa_supplicant (quoted below), nor wlandebug (in the URL above) gave me the answer -- it looks like we are going into the scan with the specific SSID in mind and never come back, so I went for the next level. However, could you, please, clarify that I understood you correctly -- you *do not* want to see mix of wlandebug and athdebug messages in the report, and I should turn wlandebug off before turning athdebug on, right? I suggest that when debugging you start from the highest layer and move downward. If you can't find what you need in a wpa_supplicant log then turn on msgs in net80211 with wlandebug. If that doesn't tell you what you need then move to the driver. Blindly turning everything on can easily livelock your system. That's what I did -- what I have posted is the end result of the walking down that chain, and I assumed, possibly incorrectly, that you would want result of all three to put things in context. I do apologize for the misunderstanding. For high volume msgs I often do something like: athdebug +intr; sleep 1; athdebug -intr or athdebug +intr; read x; athdebug -intr so a carriage return will disable msgs. Thank you for the suggestion. * what facility does wpa_supplicant use, when forced to syslog by -s switch? trouble% cd /data/freebsd/head/contrib/wpa_supplicant/ trouble% grep openlog *.c common.c: openlog(wpa_supplicant, LOG_PID | LOG_NDELAY, LOG_DAEMON); Thank you, should have done this myself, sorry. -- Alexandre Sunny Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
If you run only the latest standard binaries you are right but typically one acquires useful things over time and it is not always possible to recompile them and also, why bother. true, but in this case I want to change a more or less vanilla 7-STABLE/i386 to a more or less vanilla 7-STABLE/amd74, just preserving all my user data and config files. It sounds like it should work then, and I'll give it a shot, thanks. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA APM and NCQ support in FreeBSD atacontrol
On Mon, 2008-05-12 at 14:52 +1000, Ian Smith wrote: On Sun, 11 May 2008 [EMAIL PROTECTED] wrote: Has any work been done recently towards adding SATA Native Command Queueing as well as ATA APM and acoustic management to FreeBSD? I found this PR (with patch) to add APM and acoustic management control to atacontrol. The PR was opened in May 2005 has not been changed since December 2006 and is still open. http://www.freebsd.org/cgi/query-pr.cgi?pr=81692cat= I have not been able to find much of anything on SATA NCQ in FreeBSD newer than 2005 or 2006 does anyone know anything newer? Jeremy has addressed the NCQ issue, about which I know nothing. As for APM and AAM, that functionality is handled by sysutils/ataidle, which that PR appears - on a quick glance - to pretty well duplicate. I see phk@ recently added an 'atacontrol spindown' command to HEAD and RELENG_7 that appears to offer similar functionality to 'ataidle -S standby_mins' or 'ataidle -I idle_mins', though specified in seconds instead. However this doesn't address acoustic management. Or is ataidle broken for SATA disks? Does not look broken here (RELENG_7): RabbitsDen# ataidle /dev/ad4 Device Info: Model: HTS541010G9SA00 Serial: MP2ZM4X0JWY6WH Firmware Rev: MBZIC60H ATA revision: ATA-7 LBA 48: yes Geometry: 16383 cyls, 16 heads, 63 spt Capacity: 93GB SMART Supported:yes SMART Enabled: yes APM Supported: yes APM Enabled:yes AAM Supported: yes AAM Enabled:yes Current AAM:1 Vendor Recommends AAM: 1 APM Value: 16638 RabbitsDen# 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: ad4 HTS541010G9SA00/MBZIC60H Serial ATA v1.0 Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present atacontrol: ioctl(IOCATADEVICES): Device not configured RabbitsDen# uname -a FreeBSD RabbitsDen.RabbitsLawn.verizon.net 7.0-STABLE FreeBSD 7.0-STABLE #1: Sun May 11 20:31:21 EDT 2008 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TPX60 i386 RabbitsDen# cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Alexandre Sunny Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kqemu support: not compiled
On Mon, 12 May 2008 20:56:20 -0400 bazzoola wrote: I just cant get kqemu to work on my AMD64 SMP! I setenv WITH_KQEMU I compiled the port with make -DWITH_KQEMU I edited src.conf and added WITH_KQEMU=yes I make config and checked KQEMU ALPHA support I am running #uname -a FreeBSD Aa.bsd 7.0-STABLE FreeBSD 7.0-STABLE #3: Mon Apr 21 05:56:16 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 #pkg_info | grep qemu kqemu-kmod-1.3.0.p11_6 qemu-devel-0.9.1s.20080302_6 latest as you as see ^^^ any ideas? You didn't show the actual command and an error message. -- WBR, bsam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kqemu support: not compiled
In article [EMAIL PROTECTED] you write: On Tue, 13 May 2008 00:18:32 EDT bazzoola [EMAIL PROTECTED] wrote: On May 12, 2008, at 10:20 PM, Bakul Shah wrote: I just cant get kqemu to work on my AMD64 SMP! echo kqemu_enable=YES /etc/rc.conf /usr/local/etc/rc.d/kqemu start This should probably be described in pkg-message. I looked at the rc script and all it does is kldload aio and kqemu. I already have them loaded by default. You didn't provide information so I had to guess. This still does not help me with my problem. I press Ctrl + Alt + 2 then I type info kqemu I get kqemu support: not compiled Are you running qemu? It is an i386 emulator and won't use kqemu on amd64. You need to run qemu-system-x86_64. I know, this is a bit confusing. I just added notes about these two things to the pkg-message(s)... Juergen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing an installed system from i386 to amd64
On 2008-May-13 08:33:03 -0700, Bakul Shah [EMAIL PROTECTED] wrote: Most all old 32 bit ports should work but upgrading them can mess things up. All the new compiles will generate 64 bit binaries but any port dependencies on a shared library will be wrong. It's actually somewhat worse than this: When compiling a new port with dependencies, the internal foo_DEPENDS logic will detect the i386 .so but the port's own configuration tools or build process will normally die in interesting ways when they can't actually use that .so. -- 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. pgppfg3C7wegl.pgp Description: PGP signature
Panic after hung rsync, probably zfs related
Hi, While doing an rsync from a zfs filesystem to an external usb hd (also zfs), the rsync processes hung in zfs state. I could not kill these processes, although the rest of the server seemingly continued to run fine. The reboot command did not work. Next I tried a shutdown now command. This caused a panic: ... Stopping dhcpd. Shutting down local daemons:. Stopping named. Waiting for PIDS: 106830 second watchdog timeout expired. Shutdown terminated. Tue May 13 21:02:50 CEST 2008 May 13 21:02:50 auth.alert mars init: /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user mode panic: vrele: negative ref cnt cpuid = 6 Uptime: 8d3h8m21s Physical memory: 8178 MB Dumping 3679 MB: 3664 3648 3632 3616 3600 3584 3568 3552 3536 3520 3504 3488 3472 3456 3440 3424 3408 3392 3376 3360 3344 3328 3312 3296 3280 3264 3248 atl trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fau =Fta tvailr tduoaulb laed dfraeuslst = r0ixp8 v f0axuflftf fcfofdfef 8 0=6 esbuap9e3r girssopr =r e0axdf fifnfsftfrfufcftbi5o4n8,f fp0a er bnpo t= p0rxe1s0e0n0t xipnusitdr u=c t0i;o na ppioci nitde r= =0 00 8:0x8 stack pointer = 0x10:0xf8c50a50 frame pointer = 0x10:0xfb54c450 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 = 44 (irq19: uhci1+) trap number = 12 Yes, it printed all that gibberish. (double fault I think it says?) At this point, the server completely hung, and I could not do a bt unfortunately. I had to reset the server. After reboot, savecore did not find a kernel dump. I ran the rsync again and could not reproduce the problem. Although I've had zfs related problems before, this one was new to me. Any idea what happened here? Other info on this machine follows below. Thanks, Ben [mars:~]133: uname -a FreeBSD mars.altus-escon.com 7.0-STABLE FreeBSD 7.0-STABLE #2: Mon Apr 21 08:45:56 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/ sys/MARS amd64 [mars:~]134: cat /boot/loader.conf console=comconsole zfs_load=YES vfs.root.mountfrom=zfs:tank vfs.zfs.prefetch_disable=1 vm.kmem_size=1536M vm.kmem_size_max=1536M vfs.zfs.arc_max=768M [mars:~]135: dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #2: Mon Apr 21 08:45:56 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MARS Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5335 @ 2.00GHz (2000.08-MHz K8- class CPU) Origin = GenuineIntel Id = 0x6f7 Stepping = 7 Features = 0xbfebfbff FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2 =0x4e33dSSE3,RSVD2,MON,DS_CPL,VMX,TM2,SSSE3,CX16,xTPR,PDCM,DCA AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 8575598592 (8178 MB) avail memory = 8285937664 (7902 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 p4tcc0: CPU Frequency Thermal Control on cpu0 cpu1: ACPI CPU on acpi0 p4tcc1: CPU Frequency Thermal Control on cpu1 cpu2: ACPI CPU on acpi0 p4tcc2: CPU Frequency Thermal Control on cpu2 cpu3: ACPI CPU on acpi0 p4tcc3: CPU Frequency Thermal Control on cpu3 cpu4: ACPI CPU on acpi0 p4tcc4: CPU Frequency Thermal Control on cpu4 cpu5: ACPI CPU on acpi0 p4tcc5: CPU Frequency Thermal Control on cpu5 cpu6: ACPI CPU on acpi0 p4tcc6: CPU Frequency Thermal Control on cpu6 cpu7: ACPI CPU on acpi0 p4tcc7: CPU Frequency Thermal Control on cpu7 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 0.0 on pci3 pci4:
Re: Panic after hung rsync, probably zfs related
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben Stuyts wrote: | Hi, | | While doing an rsync from a zfs filesystem to an external usb hd (also | zfs), the rsync processes hung in zfs state. I could not kill these | processes, although the rest of the server seemingly continued to run | fine. The reboot command did not work. Next I tried a shutdown now | command. This caused a panic: Sound like you somehow run out of memory, there is an known issue with ZFS which causes livelock when there is memory pressure. Which rsync version are you using? With rsync 3.x the memory usage would drop drastically which would help to prevent this from happening. Cheers, - -- ** Help China's quake relief at http://www.redcross.org.cn/ | Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgp8bcACgkQi+vbBBjt66DQQgCfSObZqsQNCteT9SsjDTIqAa2E xfgAnAs9reRKfjaJdS9RAco0cnD7JZp0 =J4+1 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: good/best practices for gmirror and gjournal on a pair of disks?
George Hartzell wrote: I've been running many of my systems for some time now using gmirror on a pair of identical disks, as described by Ralf at: http://people.freebsd.org/~rse/mirror/ Each disk has single slice that covers almost all of the disk. These slices are combined into the gmirror device (gm0), which is then carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e (/tmp), and gm0f (/usr). My latest machine is using Seagate 1TB disks so I thought I should add gjournal to the mix to avoid ugly fsck's if/when the machine doesn't shut down cleanly. I ended up just creating a gm0f.journal and using it for /usr, which basically seems to be working. I'm left with a couple of questions though: - I've read in the gjournal man page that when it is ... configured on top of gmirror(8) or graid3(8) providers, it also keeps them in a consistent state... I've been trying to figure out if this simply falls out of how gjournal works or if there's explicity collusion with gmirror/graid3 but can't come up with a satisfactory explanation. Can someone walk me through it? Since I'm only gjournal'ing a portion of the underlying gmirror device I assume that I don't get this benefit? - I've also read in the gjournal man page ... that sync(2) and fsync(2) system calls do not work as expected anymore. Does this invalidate any of the assumptions made by various database packages such as postgresql, sqlite, berkeley db, etc about if/when/whether their data is safely on the disk? - What's the cleanest gjournal adaptation of rse's two-disk-mirror-everything setup that would be able to avoid tedious gmirror sync's. The best I've come up with is to do two slices per disk, combine the slices into a pair of gmirror devices, bsdlabel the first into gm0a (/), gm0b (swap), gm0d (/var) and gm0e (/tmp) and bsdlabel the second into a gm1f which gets a gjournal device. Alternatively, would it work and/or make sense to give each disk a single slice, combine them into a gmirror, put a gjournal on top of that, then use bsdlabel to slice it up into partitions? Is anyone using gjournal and gmirror for all of the system on a pair of disks in some other configuration? Thanks, g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] I am pasting below the instructions I would use to convert a recently installed system with only / (root) and swap to be using gmirror+gjournal. It is in mediawiki markup format so it could be pasted into one if desired. I based my gmirror steps on the instructions from http://people.freebsd.org/~rse/mirror/ so thats why some of the words sound familiar. I also have similar instructions for setting up a gmirrored da0s1a and da0s1b alongside a zfs mirror containing the rest. I decided to journal /usr /var /tmp and leave / as a standard UFS partition because it is so small, fsck doesn't take long anyway and hopefully doesn't get written to enough to cause damage by an abrupt reboot. Because I'm not journaling the root partition, I chose to ignore the possibility of gjournal marking the mirror clean. Sudden reboots don't happen enough on servers for me to care. And all my servers got abruptly rebooted this sunday and they all came up fine :) I believe gjournal uses 1G for journal (2x512) which seemed to be sufficient on all of the systems where I have used the default, but I quickly found that using a smaller journal is a bad idea and leads to panics that I was unable to avoid with tuning. Considering 1G was such a close value, I chose to go several times above the default journal size (disk is cheap and I want to be sure) but I ran into problems using gjournal label -s (size) rejecting my sizes or wrapping the value around to something too low. As a workaround I chose to use a separate partition for each journal. I quickly ran out of partitions in a bsd disklabel so I decided to partition each disk into two slices; the first for data and the second for journals. This also made it easier to line up disk devices so they made more sense as a pair, for example: gm0s1d(data) + gm0s2d(journal) = /usr. I will note that if you accidentally put a gjournal label in the 'wrong' spot on your disk, you might make a tough situation for yourself getting rid of it. I have had plenty of times where I applied a gjournal label, discovered something unideal with it, but every time I did 'gjournal stop foo' the label would automatically get detected as a child of a different part of the disk because it could be seen and I could not unload it. That is part of why I use -h for gjournal label, and use slices+partitions, and the first partition is at offset 16, some of which may have been for gmirror's sake too. ==Software
Re: good/best practices for gmirror and gjournal on a pair of disks?
Adam McDougall writes: [...] I believe gjournal uses 1G for journal (2x512) which seemed to be sufficient on all of the systems where I have used the default, but I quickly found that using a smaller journal is a bad idea and leads to panics that I was unable to avoid with tuning. Considering 1G was such a close value, I chose to go several times above the default journal size (disk is cheap and I want to be sure) but I ran into problems using gjournal label -s (size) rejecting my sizes or wrapping the value around to something too low. [...] I also stumbled on this and was unable to find any mention of it in the pr database. One of my todo items is to make sure I'm not messing up somehow, dig further into the PR db for an existing report, and file one if I can't find one? I tried -s 2147483648 and it was found to be too small. A quick read of the source led me to find that jsize is an intmax_t and that gctl_get_intmax() should be returning an intmax_t and that intmax_ ought to be an __int64_t (I'm on amd64), which left me confused. Has anyone else seen/reported a problem with gjournal -s and values 1G? g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: good/best practices for gmirror and gjournal on a pair of disks?
Adam McDougall writes: George Hartzell wrote: [...] - I've read in the gjournal man page that when it is ... configured on top of gmirror(8) or graid3(8) providers, it also keeps them in a consistent state... I've been trying to figure out if this simply falls out of how gjournal works or if there's explicity collusion with gmirror/graid3 but can't come up with a satisfactory explanation. Can someone walk me through it? Since I'm only gjournal'ing a portion of the underlying gmirror device I assume that I don't get this benefit? [...] [...] I decided to journal /usr /var /tmp and leave / as a standard UFS partition because it is so small, fsck doesn't take long anyway and hopefully doesn't get written to enough to cause damage by an abrupt reboot. Because I'm not journaling the root partition, I chose to ignore the possibility of gjournal marking the mirror clean. Sudden reboots don't happen enough on servers for me to care. And all my servers got abruptly rebooted this sunday and they all came up fine :) [...] So you're confirming my belief that setting up gjournal on a bsdlabel'ed partition of a gmirror does *not* provide the consistency guarantee and that I should leave autosynchronization enabled. Right? g. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with ia64
Hello, I'm trying to download the ia64 distribution CDs from ftp://ftp.freebsd.org/pub/FreeBSD/releases/ia64/ISO-IMAGES/7.0/ and the list is [FILE] 7.0-RELEASE-ia64-bootonly.iso. . Feb 25 18:10 62M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc1.iso . . . Feb 25 18:11429M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc2.iso . . . Feb 25 18:11364K [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-disc3.iso . . . Feb 25 18:11364K [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-docs.iso. . . . Feb 25 18:11238M [VIEW] [DOWNLOAD] [FILE] 7.0-RELEASE-ia64-livefs.iso. . . Feb 25 18:12371M [VIEW] [DOWNLOAD] [FILE] CHECKSUM.MD5 . . . . . . . . . . Feb 25 18:10411 [VIEW] [DOWNLOAD] [FILE] CHECKSUM.SHA256. . . . . . . . . Feb 25 18:10621 [VIEW] [DOWNLOAD] if you look at the disc 2 and 3, the size is 364K is it ok?. I'd like to install freebsd in a intel core 2 duo. Should I instal this ia64? Thanks for your help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
: Re: Socket leak (Was: Re: What triggers No BufferSpace), ?Available
Hello All This issue goes back some time, but I do not see a solution. Sorry about the cross post not sure where this belongs. Here is an overview of my issue which is similar and I hope someone can point me in the direction of a solution. I have experiencing an odd socket related issue on a few servers i manage. They are fairly large ftp servers for popular north american news agency. They handle 1000's of ftp transactions per hour. Currently they are running FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD 6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit installs and in both SMP an UP kernels. Oddly this issue did not happen on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime running FreeBSD 4.x-Release. The issue is after 7 to 14 days the servers lock up and will not create any new tcp sockets. The system used proftp with mysql for authentication of the ftp accounts. The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 1.5 for Resin Appserver and daemontools . The only sysctls that seem to help are kern.ipc.maxsockets and kern.maxusers . Currently they are set to 65535 and 1024 . Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this up to 2Meg, In any case I started work on logging everything we could think of to see what was happening. I started logging the values of kern.ipc.numopensockets and I noticed that something is leaking sockets. Here is a sample of the log 2008-04-29--15:04.10 kern.ipc.numopensockets: 1501 2008-04-29--16:04.01 kern.ipc.numopensockets: 1535 2008-04-29--17:04.00 kern.ipc.numopensockets: 1617 2008-04-29--18:04.00 kern.ipc.numopensockets: 1710 This continues until kern.ipc.maxsockets its reached or the box is rebooted. The other thing we looked at was the output from vmstat -z The first thing was the high amount of malloc 128 bucket failures 128 Bucket:524,0, 2489, 80, 8364, 23055239 I also logged the mbuf clusters, we never reached the max mbuf clusters Its almost like there are stale sockets. Here is a snapshot of the server now ewr# sockstat -4u |wc -l 139 ewr# sysctl kern.ipc.numopensockets kern.ipc.numopensockets: 13935 ewr# uptime 7:30PM up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17 My questions. 1. If I can not identify who / what is consuming all my tcp sockets what will happen if I double or triple the value of kern.ipc.maxsockets ? 2. Could this be an issue with a low kern.maxusers . Its currently set to 1024 . Also at times when I can not create a new socket I am not pinned on mbuf clusters . I was able to verify this in the past. 3. I installed a debugging kernel, which I built on the server. I was able to get a coredump of the server at the point in time we last had an issue. But I am not sure what I can do with this, kernel debugging is way beyond what I am capable of doing . Do I want to even pursue this ? 4. Does anyone have any system tunings you could recommend for a high volume ftp site ? What does ftp.freebsd.org have ? -- Mark Saad [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
: Re: Socket leak (Was: Re: What triggers No BufferSpace), ?Available
Hello All This issue goes back some time, but I do not see a solution. Sorry about the cross post not sure where this belongs. Here is an overview of my issue which is similar and I hope someone can point me in the direction of a solution. I have experiencing an odd socket related issue on a few servers i manage. They are fairly large ftp servers for popular north american news agency. They handle 1000's of ftp transactions per hour. Currently they are running FreeBSD 6.3-Release-p1 . I have verified this happened on FreeBSD 6.1-Release 6.1-Stable 6.2-Release 6.2-Stable and 7.0-Release all 32bit installs and in both SMP an UP kernels. Oddly this issue did not happen on FreeBSD 4.x . I have a similar setup that has a 1400+ Day uptime running FreeBSD 4.x-Release. The issue is after 7 to 14 days the servers lock up and will not create any new tcp sockets. The system used proftp with mysql for authentication of the ftp accounts. The system is also running Apache 2.2.x , Postfix, Cyrus, clam-av, Diablo JDK 1.5 for Resin Appserver and daemontools . The only sysctls that seem to help are kern.ipc.maxsockets and kern.maxusers . Currently they are set to 65535 and 1024 . Changing kern.ipc.maxsockbuf did not have any effect I tried bumping this up to 2Meg, In any case I started work on logging everything we could think of to see what was happening. I started logging the values of kern.ipc.numopensockets and I noticed that something is leaking sockets. Here is a sample of the log 2008-04-29--15:04.10 kern.ipc.numopensockets: 1501 2008-04-29--16:04.01 kern.ipc.numopensockets: 1535 2008-04-29--17:04.00 kern.ipc.numopensockets: 1617 2008-04-29--18:04.00 kern.ipc.numopensockets: 1710 This continues until kern.ipc.maxsockets its reached or the box is rebooted. The other thing we looked at was the output from vmstat -z The first thing was the high amount of malloc 128 bucket failures 128 Bucket:524,0, 2489, 80, 8364, 23055239 I also logged the mbuf clusters, we never reached the max mbuf clusters Its almost like there are stale sockets. Here is a snapshot of the server now ewr# sockstat -4u |wc -l 139 ewr# sysctl kern.ipc.numopensockets kern.ipc.numopensockets: 13935 ewr# uptime 7:30PM up 6 days, 26 mins, 3 users, load averages: 0.18, 0.25, 0.17 My questions. 1. If I can not identify who / what is consuming all my tcp sockets what will happen if I double or triple the value of kern.ipc.maxsockets ? 2. Could this be an issue with a low kern.maxusers . Its currently set to 1024 . Also at times when I can not create a new socket I am not pinned on mbuf clusters . I was able to verify this in the past. 3. I installed a debugging kernel, which I built on the server. I was able to get a coredump of the server at the point in time we last had an issue. But I am not sure what I can do with this, kernel debugging is way beyond what I am capable of doing . Do I want to even pursue this ? 4. Does anyone have any system tunings you could recommend for a high volume ftp site ? What does ftp.freebsd.org have ? -- Mark Saad [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 issues fixed? upgrade timing?
On Tue, May 13, 2008 at 12:22:10PM -0400, Ben Kaduk wrote: Hi all, I only just now subscribed, so my apologies if this has been covered and my cursory search missed it. I am seeing a similar issue to the one described in the email below (pasted from a web listing of this list). That is, my ssh connection will occasionally be dropped with the message Disconnecting: Bad packet length 3190815048. (the number is not always the same). I can reliably reproduce this with `cat /dev/urandom | od -c` from a FreeBSD-current box (a few weeks old, actually, since the build was broken when I last tried to update) as well as from a mac running OS X 10.4 . The system that is killing my connections is: FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Mar 25 14:53:51 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PERIPHRASIS amd64 Any thoughts would be appreciated. There had been large changes to enhance re(4) stablility and many users reported positive results. But it still seems to have issues for certain models. See kern/123202, kern/123563. If you encounter issues on latest re(4), please try patch in kern/123563 and let me know how it goes. -Ben Kaduk -- random message from this thread, for some context - * From: Jeremy Chadwick [EMAIL PROTECTED] * Date: Mon, 12 May 2008 05:32:07 -0700 On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: On Mon, 12 May 2008 11:37:53 +0200 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: FWIW, I had major troubles with re(4) around 7.0-release, and a while later (I had to use patches). After upgrading to 7-stable on 2008-04-12, re(4) is working for me without patches. (sigh).. it seems that I spoke to soon. Murphy just showed up. I still get ssh disconnects (see below) on connections _to_ the machine when transferring largish amounts of data (like when upgrading a port). Here is one example (portupgrading the jdk port): /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='amd64' -DRELEASE='1.6.0_03-p4' -DFULL_VERSION='1.6.0_03-p4-root_12_may_2008_13_25-b00' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c Disconnecting: Bad packet length 3601161525. The machine is running: [EMAIL PROTECTED] uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 and has been up for about 14 days: [EMAIL PROTECTED] uptime 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. Is this machine using pf(4) at all? -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with ia64
On May 13, 2008, at 4:04 PM, Christian J. Wong Cruz wrote: Hello, I'm trying to download the ia64 distribution CDs from ftp://ftp.freebsd.org/pub/FreeBSD/releases/ia64/ISO-IMAGES/7.0/ and the list is [ ... ] if you look at the disc 2 and 3, the size is 364K is it ok?. I'd like to install freebsd in a intel core 2 duo. Should I instal this ia64? Why, no. ia64 is for the Itanium processor line which uses a different architecture and is not compatible with the standard x86 32- bit or 64-bit platforms. What you want instead is the amd64 platform, which is known as EM64T for the Intel Xeon/P4/Core/Core2 chips: http://www.FreeBSD.org/releases/7.0R/hardware.html#PROC-AMD64 ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.0/ Regards, -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: good/best practices for gmirror and gjournal on a pair of disks?
George Hartzell wrote: Adam McDougall writes: George Hartzell wrote: [...] - I've read in the gjournal man page that when it is ... configured on top of gmirror(8) or graid3(8) providers, it also keeps them in a consistent state... I've been trying to figure out if this simply falls out of how gjournal works or if there's explicity collusion with gmirror/graid3 but can't come up with a satisfactory explanation. Can someone walk me through it? Since I'm only gjournal'ing a portion of the underlying gmirror device I assume that I don't get this benefit? [...] [...] I decided to journal /usr /var /tmp and leave / as a standard UFS partition because it is so small, fsck doesn't take long anyway and hopefully doesn't get written to enough to cause damage by an abrupt reboot. Because I'm not journaling the root partition, I chose to ignore the possibility of gjournal marking the mirror clean. Sudden reboots don't happen enough on servers for me to care. And all my servers got abruptly rebooted this sunday and they all came up fine :) [...] So you're confirming my belief that setting up gjournal on a bsdlabel'ed partition of a gmirror does *not* provide the consistency guarantee and that I should leave autosynchronization enabled. Right? g. I forgot to address that. I think to gain that, you have to (re)label the mirror using -F (see man gmirror). I believe without using -F, the mirrors will still be synced (but probably don't need to). Otherwise, look for initial mail list announcements (freebsd-current?) of gjournal which may explain. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 issues fixed? upgrade timing?
On 5/13/08, Pyun YongHyeon [EMAIL PROTECTED] wrote: There had been large changes to enhance re(4) stablility and many users reported positive results. But it still seems to have issues for certain models. See kern/123202, kern/123563. If you encounter issues on latest re(4), please try patch in kern/123563 and let me know how it goes. -Ben Kaduk Pyun, Thanks for the reminder -- I saw the changes go in, but forgot that this box was using re(4). Attempting to csup while running the March 25 driver made me sad, but a kernel.old from February worked well. I'm now running with if_re.c v 1.95.2.18 and I'm not seeing any packet loss or terminated ssh sessions. Thanks for all the good work! -Ben Kaduk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA APM and NCQ support in FreeBSD atacontrol
On Tue, 13 May 2008, Alexandre Sunny Kovalenko wrote: On Mon, 2008-05-12 at 14:52 +1000, Ian Smith wrote: On Sun, 11 May 2008 [EMAIL PROTECTED] wrote: Has any work been done recently towards adding SATA Native Command Queueing as well as ATA APM and acoustic management to FreeBSD? I found this PR (with patch) to add APM and acoustic management control to atacontrol. The PR was opened in May 2005 has not been changed since December 2006 and is still open. http://www.freebsd.org/cgi/query-pr.cgi?pr=81692cat= I have not been able to find much of anything on SATA NCQ in FreeBSD newer than 2005 or 2006 does anyone know anything newer? Jeremy has addressed the NCQ issue, about which I know nothing. As for APM and AAM, that functionality is handled by sysutils/ataidle, which that PR appears - on a quick glance - to pretty well duplicate. I see phk@ recently added an 'atacontrol spindown' command to HEAD and RELENG_7 that appears to offer similar functionality to 'ataidle -S standby_mins' or 'ataidle -I idle_mins', though specified in seconds instead. However this doesn't address acoustic management. Or is ataidle broken for SATA disks? Does not look broken here (RELENG_7): RabbitsDen# ataidle /dev/ad4 Device Info: Model: HTS541010G9SA00 Serial: MP2ZM4X0JWY6WH Firmware Rev:MBZIC60H ATA revision:ATA-7 LBA 48: yes Geometry:16383 cyls, 16 heads, 63 spt Capacity:93GB SMART Supported: yes SMART Enabled: yes APM Supported: yes APM Enabled: yes AAM Supported: yes AAM Enabled: yes Current AAM: 1 Vendor Recommends AAM: 1 APM Value: 16638 Thanks for the confirmation Alexandre. I take Jonathan's point that it would be nice to have this functionality in atacontrol, though perhaps the BUGS section in ataidle(8) precludes merging that? cc'ing Bruce Cran in case he wants to add something .. RabbitsDen# atacontrol list [..] ATA channel 2: Master: ad4 HTS541010G9SA00/MBZIC60H Serial ATA v1.0 Slave: no device present Regarding the spindown thing, I always used to use APM (set in BIOS) to do that on this old laptop, until I found that I'd already consumed 25% of a new 40GB drive's 2 million Load_Cycle_Count in a year, following a thread warning about that last year, so now I run ataidle from rc.conf: ataidle_enable=YES ataidle_device=ad0 ataidle_ad0=-P 0 0 0 but then found it necessary to again disable disk APM in rc.resume: /usr/local/sbin/ataidle -P 0 0 0 cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
