nfs problems
Hi, starting about last week, I'm getting: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: write failed on /net/rnd/dist/tmp/local/amd64.FreeBSD_8.3-wip/compat/li nux/usr/lib/locale/locale-archive.tmpl: Permission denied (13) rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9] rsync: connection unexpectedly closed (21872 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] the server is running 8.2, but the client is very upto date, 8.3-stable as of this morning (local time). after runing rsync several times, it finaly gets synced. another item is that i'm using am-utils, but I don't see it causing the problem I will try using tcp (instead of udp) soon. any insights? cheers, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: nfs problems
Hi, starting about last week, I'm getting: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: write failed on /net/rnd/dist/tmp/local/amd64.FreeBSD_8.3-wip/compat/li nux/usr/lib/locale/locale-archive.tmpl: Permission denied (13) rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9] rsync: connection unexpectedly closed (21872 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] the server is running 8.2, but the client is very upto date, 8.3-stable as of this morning (local time). after runing rsync several times, it finaly gets synced. another item is that i'm using am-utils, but I don't see it causing the problem I will try using tcp (instead of udp) soon. any insights? cheers, danny the problem is most probably NFS/UDP related. I took am-utils out of the equation. mounted using TCP, and no problems mounted using UDP: Jun 29 12:38:14 pe-02 kernel: nfs server nrnfdn:sf/s ds isseterr:vve ernr o trrnn dd:r:e/s/pddoinisdsitt::n nngoo Jun 29 12:38:14 pe-02 kernel: tt Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: 66 rreessppoonnddiinngg Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: nfs server rnd:/dist: not responding Jun 29 12:38:14 pe-02 last message repeated 11 times Jun 29 12:38:27 pe-02 kernel: nfs server rnd:/dist: is alive again the above happens about every 15 seconds (you have to learn to read in between the bytes :-) cheers, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
Hello, I'm mostly using freebsd, but there are a few cases where it's impossible to do, and because of these, i'm not using fbsd there. These reasons are mostly are: - Lack of a working infiniband/OFED stack, with all its utils, mellanox connectX3 drivers, RDMA, iscsi-over-RDMA, nfs-over-RDMA, and such things. - Lack of proper support for a decent hypervisor for virtualisation. We can't make a hypervisor out of freebsd, if there are no such virtualisations available like XEN, kvm or something similar, that just works out of the box. - Lack of decent OCI support (oracle client lib). Sometimes we need OCI libs, for things like monitoring oracle databases. Without the client libs, this becomes kinda problematic. Usually these are the top reasons. Best regards, Gergely ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Hypervisor ( was Re: Why Are You NOT Using FreeBSD ? )
- Lack of proper support for a decent hypervisor for virtualisation. We can't make a hypervisor out of freebsd, if there are no such virtualisations available like XEN, kvm or something similar, that just works out of the box. What do you need that VirtualBox doesn't provide ? I used to bemoan the lack of a hypervisor too, but vince VBox arrived in FreeBSD I have had no complaints. I use it to run Windows instances both as desktop clients and also servers, and it works beautifully. Combined with a ZVOL underneath (and hence all the delights of ZFS snapshots) it';s a great solution. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Hypervisor ( was Re: Why Are You NOT Using FreeBSD ? )
On Fri, 29 Jun 2012 10:55:20 +0100 Pete French petefre...@ingresso.co.uk wrote: - Lack of proper support for a decent hypervisor for virtualisation. We can't make a hypervisor out of freebsd, if there are no such virtualisations available like XEN, kvm or something similar, that just works out of the box. What do you need that VirtualBox doesn't provide ? I used to bemoan the lack of a hypervisor too, but vince VBox arrived in FreeBSD I have had no complaints. I use it to run Windows instances both as desktop clients and also servers, and it works beautifully. Combined with a ZVOL underneath (and hence all the delights of ZFS snapshots) it';s a great solution. Yes, virtualbox is not that bad. However, to get some really nice features, you need the non-free version. Also, we can use citrix's xenserver's management tool to manage non-citrix xen clusters, because the API is same. With that we get a management tool for our clusters, which is really nice. Also I didn't know that virtualbox is capable of building clusters of nodes and bouncing VMs among nodes to balance load, and capable of doing such things, i might be lacking a bit here, sorry. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Hypervisor ( was Re: Why Are You NOT Using FreeBSD ? )
Yes, virtualbox is not that bad. However, to get some really nice features, you need the non-free version. Also, we can use citrix's xenserver's management tool to manage non-citrix xen clusters, because the API is same. With that we get a management tool for our clusters, which is really nice. OK, makes sennse. Also I didn't know that virtualbox is capable of building clusters of nodes and bouncing VMs among nodes to balance load, and capable of doing such things, i might be lacking a bit here, sorry. I belive if you have an iscsi storage backend for a runnign node it can be moved transparently to another physsical hardware node without stopping running, but I havent tried it myself I ahve to admit. cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Need help with nfsv4 and krb5 access denied
On 06/28/2012 10:01 PM, Ian Lepore wrote: When something in software works fine with one NIC but not another (nearly-) identical one, the first thing that comes to my mind is that the MAC address on the card is being used by the software as a sort of UUID. I had that happen with a commercial software once; when I changed NICs in the machine the software stopped working and said it wasn't registered on that machine. (I would have been annoyed except this sophisticed security system was circumvented by deleting a file that wasn't even hard to find, and it automatically re-authorized itself on the next run using the new MAC address.) That came to my mind, too. The thing is, I can set any MAC address I want on both NICs. The result is still the same. The first one is working, the second one not. Greetings, Herbert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-06-29 11:24:21 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-06-29 11:24:21 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-29 11:24:21 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-06-29 11:24:21 - cleaning the object tree TB --- 2012-06-29 11:24:21 - cvsupping the source tree TB --- 2012-06-29 11:24:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/sparc64/sparc64/supfile TB --- 2012-06-29 11:24:49 - building world TB --- 2012-06-29 11:24:49 - CROSS_BUILD_TESTING=YES TB --- 2012-06-29 11:24:49 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-29 11:24:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-29 11:24:49 - SRCCONF=/dev/null TB --- 2012-06-29 11:24:49 - TARGET=sparc64 TB --- 2012-06-29 11:24:49 - TARGET_ARCH=sparc64 TB --- 2012-06-29 11:24:49 - TZ=UTC TB --- 2012-06-29 11:24:49 - __MAKE_CONF=/dev/null TB --- 2012-06-29 11:24:49 - cd /src TB --- 2012-06-29 11:24:49 - /usr/bin/make -B buildworld World build started on Fri Jun 29 11:24:49 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_ZFS_SUPPORT -I/src/sys/boot/sparc64/zfsloader/../../zfs -I/src/sys/boot/sparc64/zfsloader/../../../cddl/boot/zfs -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT -DBOOT_FORTH -I/src/sys/boot/sparc64/zfsloader/../../ficl -I/src/sys/boot/sparc64/zfsloader/../../ficl/sparc64 -I/src/sys/boot/sparc64/zfsloader/../../common -I. -DNETIF_OPEN_CLOSE_ONCE -I/src/sys/boot/sparc64/zfsloader/../../ofw/libofw/ -I/src/sys/boot/sparc64/zfsloader/../../../../lib/libstand/ -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/zfsloader/../../common/misc.c cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_ZFS_SUPPORT -I/src/sys/boot/sparc64/zfsloader/../../zfs -I/src/sys/boot/sparc64/zfsloader/../../../cddl/boot/zfs -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT -DBOOT_FORTH -I/src/sys/boot/sparc64/zfsloader/../../ficl -I/src/sys/boot/sparc64/zfsloader/../../ficl/sparc64 -I/src/sys/boot/sparc64/zfsloader/../../common -I. -DNETIF_OPEN_CLOSE_ONCE -I/src/sys/boot/sparc64/zfsloader/../../ofw/libofw/ -I/src/sys/boot/sparc64/zfsloader/../../../../lib/libstand/ -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/zfsloader/../../common/module.c cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_ZFS_SUPPORT -I/src/sys/boot/sparc64/zfsloader/../../zfs -I/src/sys/boot/sparc64/zfsloader/../../../cddl/boot/zfs -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT -DBOOT_FORTH -I/src/sys/boot/sparc64/zfsloader/../../ficl -I/src/sys/boot/sparc64/zfsloader/../../ficl/sparc64 -I/src/sys/boot/sparc64/zfsloader/../../common -I. -DNETIF_OPEN_CLOSE_ONCE -I/src/sys/boot/sparc64/zfsloader/../../ofw/libofw/ -I/src/sys/boot/sparc64/zfsloader/../../../../lib/libstand/ -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/zfsloader/../../common/panic.c cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_ZFS_SUPPORT -I/src/sys/boot/sparc64/zfsloader/../../zfs -I/src/sys/boot/sparc64/zfsloader/../../../cddl/boot/zfs -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT -DBOOT_FORTH -I/src/sys/boot/sparc64/zfsloader/../../ficl -I/src/sys/boot/sparc64/zfsloader/../../ficl/sparc64 -I/src/sys/boot/sparc64/zfsloader/../../common -I. -DNETIF_OPEN_CLOSE_ONCE -I/src/sys/boot/sparc64/zfsloader/../../ofw/libofw/ -I/src/sys/boot/sparc64/zfsloader/../../../../lib/libstand/ -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/zfsloader/../../common/load_elf64.c cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_ZFS_SUPPORT -I/src/sys/boot/sparc64/zfsloader/../../zfs -I/src/sys/boot/sparc64/zfsloader/../../../cddl/boot/zfs -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT -DBOOT_FORTH -I/src/sys/boot/sparc64/zfsloader/../../ficl -I/src/sys/boot/sparc64/zfsloader/../../ficl/sparc64 -I/src/sys/boot/sparc64/zfsloader/../../common -I. -DNETIF_OPEN_CLOSE_ONCE -I/src/sys/boot/sparc64/zfsloader/../../ofw/libofw/ -I/src/sys/boot/sparc64/zfsloader/../../../../lib/libstand/ -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/zfsloader/../../common/reloc_elf64.c cc -O2 -pipe -DLOADER_DISK_SUPPORT
Re: nfs problems
On 29/06/2012 10:45, Daniel Braniss wrote: Hi, starting about last week, I'm getting: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: write failed on /net/rnd/dist/tmp/local/amd64.FreeBSD_8.3-wip/compat/li nux/usr/lib/locale/locale-archive.tmpl: Permission denied (13) rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9] rsync: connection unexpectedly closed (21872 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] the server is running 8.2, but the client is very upto date, 8.3-stable as of this morning (local time). after runing rsync several times, it finaly gets synced. another item is that i'm using am-utils, but I don't see it causing the problem I will try using tcp (instead of udp) soon. any insights? cheers, danny the problem is most probably NFS/UDP related. I took am-utils out of the equation. mounted using TCP, and no problems mounted using UDP: Jun 29 12:38:14 pe-02 kernel: nfs server nrnfdn:sf/s ds isseterr:vve ernr o trrnn dd:r:e/s/pddoinisdsitt::n nngoo Jun 29 12:38:14 pe-02 kernel: tt Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: 66 rreessppoonnddiinngg Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: nfs server rnd:/dist: not responding Jun 29 12:38:14 pe-02 last message repeated 11 times Jun 29 12:38:27 pe-02 kernel: nfs server rnd:/dist: is alive again the above happens about every 15 seconds (you have to learn to read in between the bytes :-) cheers, danny Its also possible you are hitting a bug I came across recently. See http://lists.freebsd.org/pipermail/freebsd-current/2012-June/034860.html basicly mountd may give incorrect permission denied errors when it is refreshing the exports list due to non-atomic operations. see kern/131342 kern/136865 also. Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: nfs problems
On 29/06/2012 10:45, Daniel Braniss wrote: Hi, starting about last week, I'm getting: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: write failed on /net/rnd/dist/tmp/local/amd64.FreeBSD_8.3-wip/compat/li nux/usr/lib/locale/locale-archive.tmpl: Permission denied (13) rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9] rsync: connection unexpectedly closed (21872 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] the server is running 8.2, but the client is very upto date, 8.3-stable as of this morning (local time). after runing rsync several times, it finaly gets synced. another item is that i'm using am-utils, but I don't see it causing the problem I will try using tcp (instead of udp) soon. any insights? cheers, danny the problem is most probably NFS/UDP related. I took am-utils out of the equation. mounted using TCP, and no problems mounted using UDP: Jun 29 12:38:14 pe-02 kernel: nfs server nrnfdn:sf/s ds isseterr:vve ernr o trrnn dd:r:e/s/pddoinisdsitt::n nngoo Jun 29 12:38:14 pe-02 kernel: tt Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: 66 rreessppoonnddiinngg Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: nfs server rnd:/dist: not responding Jun 29 12:38:14 pe-02 last message repeated 11 times Jun 29 12:38:27 pe-02 kernel: nfs server rnd:/dist: is alive again the above happens about every 15 seconds (you have to learn to read in between the bytes :-) cheers, danny Its also possible you are hitting a bug I came across recently. See http://lists.freebsd.org/pipermail/freebsd-current/2012-June/034860.html basicly mountd may give incorrect permission denied errors when it is refreshing the exports list due to non-atomic operations. see kern/131342 kern/136865 Hi Vince, I thought so too, there used to be a bug caused by am-utils umounting, succeding even if the mount was active, then re-mounting, which caused all kind of problems, the work around was to increase the timeout. But I don't think it's the case here, unless mountd has a life of its own. Furthermore, rsync works without a glitch when mounted nfs/tcp. thanks, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Possible r237738 libedit regression with xfce4 and other terminal programs
Some update between r237683 and r237740 has caused a regression with xfce4's Terminal program: An attempt to resize a window by dragging a corner results in the window immediately closing. I have reproduced this on a Pentium 4 machine with an old ati radeon 9000 era card and on newer machines with radeon 4 cards. There is one exception I have noted: a Terminal window with the results of svn log | less can be resized without closing. While I have not exactly bisected the problem to r237738, this regression is similar to one I have reported for DragonFly BSD after a bisection to an update to libedit. The identical symptoms lead me to believe the problem will be manifested beyond xfce4's Terminal and beyond the radeon cards tested. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Please post the output of pciconf -lvc for these devices. -Andrew On Jun 29, 2012, at 10:50 AM, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Andrew Boyerabo...@averesystems.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: new desktop box
I have a GT430 installed on my machine, but I think GT520 will use less power, from specification: http://www.geforce.com/hardware/desktop-gpus/geforce-gt-520/specifications It only needs 29W while GT430 needs 49W. NVIDIA also provides their native driver for FreeBSD. There is fanless GT520 card, not expensive. I hope it will work with nv. No real need for something more than basic graphics. What I still cannot decide is what cpu to get. I read reviews for bulldozer and find nothing thrilling. Guys are mostly gamers. On the other side, whatever i buy, gonna suffice. How about fx 8120 ? I like to have multicore (is there one core nowadays), but cold. Seems that I cannot wait for next generation to show up. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: new desktop box
Do not get a Radeon newer than the 4000-series, the drivers are not available in FreeBSD at present. The 4650 has worked well for me. I'm not picky. In old node I have/had geforce 6200, which is pretty old. Works fine for non-demanding user. It also has no fan. As I said, my only concern at the moment is what cpu I should choose. I found posts of non working amdtemp on bulldozer. Code from the head had to be compiled for it to work. Gamers overclock and get high temperatures. If someone has fx cpu (especially 8120), I'd like to hear how it behaves. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Hrmm, very interesting indeed. How do I identify if/when/where the source has been updated? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Be patient, a new version will hit HEAD soon with the ID added. Jack On Fri, Jun 29, 2012 at 9:35 AM, Rick Miller vmil...@hostileadmin.comwrote: On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Hrmm, very interesting indeed. How do I identify if/when/where the source has been updated? -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9-stabe: cd device gone, ATA_CAM panics
- Original Message - From: Oliver Fromme o...@lurza.secnetix.de I need a working DVD drive, so I'm now considering to downgrade to 8-stable. But then again, TMPFS didn't work a well for me as it does in 9-stable (which was the main reason for me to upgrade), so I'm kind of stuck in a difficult situation. Fortunately, 9-stable works with device atapicam, as I just found out. I thought I had already tried that and got errors during linking, but that was probably with the ATA_CAM option enabled at the same time which causes conflicts, obviously. So, everything's back to normal with device atapicam for now, and without ATA_CAM. Hi Oliver had a similar experience here might want to try the patch in the following PR:- http://www.freebsd.org/cgi/query-pr.cgi?pr=169495 This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem in sys/boot/i386/cdboot/cdboot.S with clang @237770
On 2012-06-29 15:34, David Wolfskill wrote: ... FreeBSD g1-227.catwhisker.org 9.0-STABLE FreeBSD 9.0-STABLE #201 237770M: Fri Jun 29 04:46:48 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 OK using gcc, but with clang (separate bootable slice), I get whines and a failure: clang -O2 -pipe -I/usr/src/sys/boot/i386/cdboot/../common -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -Qunused-arguments-c /usr/src/sys/boot/i386/cdboot/cdboot.S .code16 ^ /usr/src/sys/boot/i386/cdboot/cdboot.S:144:3: error: ambiguous instructions require an explicit suffix (could be 'orb', 'orw', 'orl', or 'orq') or $0x1,0x8(%bx) # kargs-bootflags |= ^ I had not merged r235281 from head to stable/9 yet. Please try again with r237812. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
NFSv3 + krb5 mysteries - need help tracking down
Hi, I have a FreeBSD 9-STABLE acting as a kerberized NFSv3 server. server# ktutil list FILE:/etc/krb5.keytab: Vno Type Principal 5 aes256-cts-hmac-sha1-96 nfs/server.linguamatics@linguamatics.com 5 des3-cbc-sha1 nfs/server.linguamatics@linguamatics.com 5 arcfour-hmac-md5 nfs/server.linguamatics@linguamatics.com ntp in sync everywhere The network is a lagg device composed of two bce interfaces (an add-in card). -- 8 [nfstest.sh] -- #!/bin/bash i=0 fail=0 while [ $i -lt 100 ] do i=$[i+1] echo RUN: $i umount -f /mnt sleep 1 mount -v -o sec=krb5i,vers=3,proto=tcp server:/export/share /mnt || fail =$[fail+1] done echo $fail times failed -- 8 -- centos62# ./nfstest.sh 54 times failed ubuntu1204# ./nfstest.sh 98 times failed ubuntu1104# ./nfstest.sh 0 times failed centos58# ./nfstest.sh 0 times failed I started rpc.gssd -v on all linux clients. The clients which did not fail are using gssapi v1 with DES. Jun 29 18:17:41 centos58 rpc.gssd[1452]: prepare_krb5_rfc1964_buffer: serializing keys with enctype 4 and length 8 Jun 29 18:04:36 ubuntu1104 rpc.gssd[911]: prepare_krb5_rfc1964_buffer: serializing keys with enctype 4 and length 8 The failing clients are using the newer gssapi v2 with AES256. Jun 29 17:59:37 ubuntu1204 rpc.gssd[756]: prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32 Jun 29 17:55:48 centos62 rpc.gssd[1183]: prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32 Note the different RFC being used. This is just a suspicion, this may not be realted to the problem. The cipher being used is different too. Then I changed my script to proto=udp. from ubuntu1104 fails 0 times. from centos62 fails 0 times. On centos58 and ubuntu1204 mount locks up all the time. Then I added to krb5.conf [libdefaults] default_tgs_enctypes = dec-cbc-crc and rebooted both centos58 and ubuntu1204. After rebooting centos56 and ubuntu1204: nfstest fails 0 times on centos58 with udp I get very long response times for ubuntu1204 mounts and always a permission denied. This is a mystery. I have not tested NFSv4 yet. I need some help to track down this problem. Attila PS: This may be the same problem as this thread: http://lists.freebsd.org/pipermail/freebsd-stable/2012-June/068619.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer gpal...@freebsd.org wrote: On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: network, ethernet at device 0.0 (no driver attached) pci4: network, ethernet at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. We removed an Intel branded equivalent from the DL360 and tried it in the R620. It detected it no problem. Only problem was we could not see it in the BIOS, not a huge deal to us. -- Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem in sys/boot/i386/cdboot/cdboot.S with clang @237770
On Fri, Jun 29, 2012 at 08:11:28PM +0200, Dimitry Andric wrote: ... I had not merged r235281 from head to stable/9 yet. Please try again with r237812. Much better (after patching with the change for r237812): FreeBSD d134.dwolf.juniper.net. 9.0-STABLE FreeBSD 9.0-STABLE #201 237770M: Fri Jun 29 11:39:57 PDT 2012 r...@d134.dwolf.juniper.net.:/usr/obj/usr/src/sys/CANARY i386 Thanks! I believe that PR i386/169550 may noe be closed. :-) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpv2NWUG0JvL.pgp Description: PGP signature
Re: new Heimdal version, was NFSv3 + krb5 mysteries - need help tracking down
Someone was/is recently working on a Heimdal upgrade, but I'm not sure if they are doing it as a port or part of the base system. Otherwise, the version of Kerberos in FreeBSD is quite old (around Heimdal 1.0.5 I think?) and it would be no surprise that the new gssapi wouldn't be supported. Maybe the person working on the newer Heimdal can comment? (I've changed the subject line so they might notice.) rick - Original Message - Hi, I have a FreeBSD 9-STABLE acting as a kerberized NFSv3 server. server# ktutil list FILE:/etc/krb5.keytab: Vno Type Principal 5 aes256-cts-hmac-sha1-96 nfs/server.linguamatics@linguamatics.com 5 des3-cbc-sha1 nfs/server.linguamatics@linguamatics.com 5 arcfour-hmac-md5 nfs/server.linguamatics@linguamatics.com ntp in sync everywhere The network is a lagg device composed of two bce interfaces (an add-in card). -- 8 [nfstest.sh] -- #!/bin/bash i=0 fail=0 while [ $i -lt 100 ] do i=$[i+1] echo RUN: $i umount -f /mnt sleep 1 mount -v -o sec=krb5i,vers=3,proto=tcp server:/export/share /mnt || fail =$[fail+1] done echo $fail times failed -- 8 -- centos62# ./nfstest.sh 54 times failed ubuntu1204# ./nfstest.sh 98 times failed ubuntu1104# ./nfstest.sh 0 times failed centos58# ./nfstest.sh 0 times failed I started rpc.gssd -v on all linux clients. The clients which did not fail are using gssapi v1 with DES. Jun 29 18:17:41 centos58 rpc.gssd[1452]: prepare_krb5_rfc1964_buffer: serializing keys with enctype 4 and length 8 Jun 29 18:04:36 ubuntu1104 rpc.gssd[911]: prepare_krb5_rfc1964_buffer: serializing keys with enctype 4 and length 8 The failing clients are using the newer gssapi v2 with AES256. Jun 29 17:59:37 ubuntu1204 rpc.gssd[756]: prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32 Jun 29 17:55:48 centos62 rpc.gssd[1183]: prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32 Note the different RFC being used. This is just a suspicion, this may not be realted to the problem. The cipher being used is different too. Then I changed my script to proto=udp. from ubuntu1104 fails 0 times. from centos62 fails 0 times. On centos58 and ubuntu1204 mount locks up all the time. Then I added to krb5.conf [libdefaults] default_tgs_enctypes = dec-cbc-crc and rebooted both centos58 and ubuntu1204. After rebooting centos56 and ubuntu1204: nfstest fails 0 times on centos58 with udp I get very long response times for ubuntu1204 mounts and always a permission denied. This is a mystery. I have not tested NFSv4 yet. I need some help to track down this problem. Attila PS: This may be the same problem as this thread: http://lists.freebsd.org/pipermail/freebsd-stable/2012-June/068619.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: new desktop box
Hi, On Thursday, June 28, 2012 09:00:56 PM Zoran Kolic wrote: Thanks all for reply! The real question is which video card do you want to use? Since I'm not gamer nor do 3d, some silent card will suffice. There are nvidia gp520 and radeon 6450, both with no fan. Also, I always enable powerd and dynamically lower freq to the least I could. More I read, less I know, regarding that future cpu. What about amd fx8120 ? Nex gen will come at Q3, maybe. I am currently also considering an eight core AMD. I have a Athlon X4 620 and I am perfectly happy with it. Next decision might be ssd, instead of hdd. Best reviews are for samsung 830 (of wich 64gb are fine in my case). I plan to install from usb stick and avoid dvd-cd. Also, cannot This is what I do since 8.0. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
