odd behaviour using lagg on bridge
Hi List, I’m observing some odd behaviour after I decided to put the 2 interfaces in my system into a lagg failover bond - Can’t add the lagg to a bridge, it will say: $ sudo ifconfig vm-public addm lagg0 ifconfig: BRDGADD lagg0: Device busy I also witnessed that starting a vm after having it reconfigured to use a manual bridge (instead of the vm-bhyve managed one) where lagg0 is present all IPv6 addresses are being stripped from the lagg interface. A service netif/routing restart doesn’t restore ipv6 connectivity. I think I saw something similar with a (iocage managed) vnet jail too, as that uses bridges too Regards, Ruben signature.asc Description: Message signed with OpenPGP
Re: Deprecating base system ftpd?
> On 3 Apr 2021, at 22:39, Ed Maste wrote: > > I propose deprecating the ftpd currently included in the base system > before FreeBSD 14, and opened review D26447 > (https://reviews.freebsd.org/D26447) to add a notice to the man page. > I had originally planned to try to do this before 13.0, but it dropped > off my list. FTP is not nearly as relevant now as it once was, and it > had a security vulnerability that secteam had to address. > > I'm happy to make a port for it if anyone needs it. Comments? Make it a port It is time to deprecate ftp altogether, and any other protocols that embed protocol information in layer 7, thus hurting any #IPv6 migration and deployment technology (SIIT-DC e.g). Hopefully the IETF can put up a deprecation notice, just as was done for e.g. TLS 1.0. Then we move onward to the self regulating capacity of the community, warning each other on “you have ftp” running. ftp, a protocol not using TLS protection but by adding it a netadmin needs to manage the port range in their firewalls too because clients behind nat can’t use passive mode with TLS as NAT can’t map things around ¯\_(ツ)_/¯ It is not worth the time and the hassle. Keep FTP(s) for legacy and internal, serve anyone else with https Best Regards, Ruben signature.asc Description: Message signed with OpenPGP
Request: Mount zfs encrypted datasets at boot? Re: FreeBSD 13.0-RC2 Now Available
Hi, > On 13 Mar 2021, at 1:11, Glen Barber wrote: > > The second RC build of the 13.0-RELEASE release cycle is now available. Might it be interesting to change the zfs mount -a / zfs unmount -a in /etc/rc.d/zfs to zfs mount -al / zfs unmount -au so that filesystems using the openzfs encryption feature can be automatically mounted? given their keylocation is not “prompt" and accessible during boot. This would make it possible for me to move away from my current dual pool boot setup, in where the boot pool has the geli keys for my geli encrypted system pool, which seems to be incompatible with beadm/bectl handling of things these days… The single geli encrypted pool does not work for me as it doesn’t allow for unattended reboots. Best regards, Ruben signature.asc Description: Message signed with OpenPGP
Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusion
I’ve updated the installation to RC2, the behaviour has changed in vmware fusion to when I installed one of the BETA releases. The initial boot fails, the system will reboot again and then it succeeds, though more predictable than with the BETAs I’m trying to see the differences in screen recording I made, and I can only see the “Image base” is changed. Load path, load device, bootcurrent, bootinfo path, currdev (disk0p1, EFI)) has not changed. Either something in the loader(s) was changed, or the RC1 to RC2 update placed contents on more “favourable" places on disk that made it possible to boot again. But I do not understand how the loader interacts with the (Vmware) EFI firmware to make sense out of it. > On 10 Mar 2021, at 12:22, Ruben van Staveren wrote: > > To continue on the subject of UEFI booting weirdness > >> On 9 Mar 2021, at 16:57, Ruben van Staveren wrote: >> >> If I press escape and end up in VMWare’s UEFI setup screen I can boot from >> any ada*p1 drive and continue as normal. >> Is UEFI with OpenZFS too new, or is this an issue in VMWare? > > I got an off list tip to see whether this was also the case in bhyve, so I > also created the setup in there, using UEFI boot, and no problems even with > the special/log/cache NVMe vdevs attached to the pool. > > So I’m starting to wonder whether the loader / VMware UEFI firmware (??) > interaction is a bug in VMware or an edge case that needs to be supported too. > > Btw, bhyve is looking nice these days! > > Cheers, >Ruben > signature.asc Description: Message signed with OpenPGP
Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusion
To continue on the subject of UEFI booting weirdness > On 9 Mar 2021, at 16:57, Ruben van Staveren wrote: > > If I press escape and end up in VMWare’s UEFI setup screen I can boot from > any ada*p1 drive and continue as normal. > Is UEFI with OpenZFS too new, or is this an issue in VMWare? I got an off list tip to see whether this was also the case in bhyve, so I also created the setup in there, using UEFI boot, and no problems even with the special/log/cache NVMe vdevs attached to the pool. So I’m starting to wonder whether the loader / VMware UEFI firmware (??) interaction is a bug in VMware or an edge case that needs to be supported too. Btw, bhyve is looking nice these days! Cheers, Ruben ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusio
> Also, I’m missing /boot/*efifat* in FreeBSD13. What is the procedure for > updating EFI loaders? > > They have been removed because they are no longer needed (filesystem images > for boot blocks trouble me too). Agree, but I’ve felt I’ve missed the memo > > mount -t msdos /dev/da0pX /mnt > mv /mnt/efi/boot/bootx64.efi /mnt/efi/boot/bootx64-old.efi > cp /boot/loader.efi /mnt/efi/boot/bootx64.efi > > The ESP on UEFI systems is just a FAT filesystem. Yes. I think it it noteworthy to have this in the release notes somewhere. that is, if bootx64.efi needs updates every now and then > > One issue you may run into is the size of the partition. If it is tiny, > you'll likely have to create a new ESP. Using /boot/boot1.efi may help and > can be used in the last step instead of loader.efi, but it's much less > flexible than loader.efi. > > Warner Thanks, Ruben signature.asc Description: Message signed with OpenPGP
FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusio
Hi List, With FreeBSD 13 getting near release I was trying out a new hardware setup for a future upgrade, in where a zfs SATA RAID-10 array would be accelated by some NVME devices for cache, log, and special meta data. However, booting the setup under VMWare fusion gives me a lot of zio_read error: 5 / ZFS: i/o error - all block copies unavailable whereas in VirtualBox using the same VMDKs the setup boots without issue, both in UEFI mode I used the guided ZFS install, GPT UEFI only, and choose RAID-10 and zero swap as I want to use the NVME devices for that later on. when on the loader prompt lsdev / lszfs / ls works through latter two throw out zio_read error: 5 but show recognisable output (zfs filesystems, files) disk0 through 4 are the SATA disks with only an EFI and ZFS GPT partition each, disk4/5 is reserved for the special vdevs (but not in use yet) and swap If I press escape and end up in VMWare’s UEFI setup screen I can boot from any ada*p1 drive and continue as normal. Is UEFI with OpenZFS too new, or is this an issue in VMWare? Also, I’m missing /boot/*efifat* in FreeBSD13. What is the procedure for updating EFI loaders? signature.asc Description: Message signed with OpenPGP
Re: Waiting for FreeBSD 12.2-RELEASE
Hi Jack, > On 26 Oct 2020, at 22:31, Jack Raats wrote: > > > I bought a new a PC and now eager waiting for the new release to arrive!!! Don’t hold your horses, install now (unless your hardware is not listed as supported in https://www.freebsd.org/releases/12.1R/hardware.html) and use the excellent freebsd-update when it arrives! Good luck! > > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > signature.asc Description: Message signed with OpenPGP
ZFS arc behaviour different after upgrading to 10.4
Hi list, I noticed that the ZFS ARC is behaving differently with 10.4, giving me a much worser cache effeciency as with 10.3 The following grafana/telefraph graph illustrates this as follows. https://snapshot.raintank.io/dashboard/snapshot/X18wHgmqFnMccEYlnbwgQtYgLIZ4oQLU?panelId=65061&fullscreen&orgId=2 Left I'm still running 10.3, Started some maintenance (binary update with freebsd-update) at 12:36 and booted into 10.4 at 14:34. Since then the ARC hits/misses are much more irregular. Disabling compression (apparently also introduced in 10.4) didn't help that much with regards to the pattern although it did shave off some load of the system. Any thoughts on the changed behaviour? Cheers, Ruben signature.asc Description: OpenPGP digital signature
restore zfs pool using original devices?
Hi list, Recently I decided to grow my zfs pool from 1TB to 6TB by replacing my 1TB dell rebranded toshiba disk with an HGST Deskstar NAS 6 TB one. system was running 10.2 to make things easier, I decided to do a zpool replace on both the unencrypted boot and encrypted (as per https://www.dan.me.uk/blog/2012/05/06/full-disk-encryption-with-zfs-root-for-freebsd-9-x/) system pool zpool replace system gpt/boot diskid/DISK-NAHRVZDXp2 zpool replace system gpt/system.eli diskid/DISK-NAHRVZDXp3.eli The system ran fine for a while until I rebooted it: https://ruben.is.verweg.com/stuff/IMG_5734.jpg a panic during mounting root panic: solaris assert: nvlist_lookup_uint64(configs[i], ZPOOL_CONFIG_POOL_TXG, &txg) == 0: file src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:4040 I tried to recover diskid/DISK-NAHRVZDXp2 by creating a new boot pool on a rescue nanobsd image, so I could recover the encryption keys. No I didn’t make an off system backup of those with zpool create -R /path/to/temp/root-for-boot zboot /dev/diskid/DISK-NAHRVZDXp2. first it complained the disk was part of the original boot pool, so I used -f. upon inspection I found the disk to be empty, so it looks like that action destroyed some important metadata. should it do that actually? I wanted to restore that data so I used dd if=/dev/gpt/boot of=/dev/diskid/DISK-NAHRVZDXp2 bs=64k but the contents is not restored. a cat of /dev/gpt/boot show various data is still there, but not seen anymore by zfs. given zfs replace actually involves a temporarily mirror in where the old vdev is removed, it should be pretty much possible to re attach this vdev to any pool to see its contents again ? what are my chances to create a functional new pool using old devices? Best Regards, Ruben signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Stiil a regression with jails/IPv6/pf?
Hi, On 31 Aug 2013, at 21:49, Tim Bishop wrote: > Hi all, > > This is regarding kern/170070 and these two threads from last year: > > http://lists.freebsd.org/pipermail/freebsd-stable/2012-July/068987.html > http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069043.html > > I'm running stable/9 r255017 and I'm seeing the same issue, even with > the fix Bjoern committed in r238876. This is still with "modulate state" in some rules that also hit ipv6 traffic ? It almost looks like doing this kind of traffic alteration is considered harmful for IPv6 http://forums.freebsd.org/showthread.php?t=36595 If that is the case, then this should be applicable only to ipv4 traffic, without requiring specific knowledge from the user > > My setup is a dual stack one (IPv6 is done through an IPv4 tunnel) and > the problem is only with IPv6. I have jails with both IPv4 and IPv6 > addresses, and I use pf to rdr certain ports to certain jails. With IPv6 > I'm seeing failed checksums on the packets coming back out of my system, > both with UDP and TCP. > > If I connect over IPv6 to the jail host it works fine. If I connect over > IPv6 to a jail directly (they have routable addresses, but I prefer them > to all be masked behind the single jail host normally), it works fine. > So the only failure case is when it goes through a rdr rule in pf. > > This system replaces a previous one running stable/8 which worked fine > with the same pf config file. > > Has anyone got any suggestions on what I can do to fix this or to debug > it further? > > Thanks, > > Tim. > > -- > Tim Bishop > http://www.bishnet.net/tim/ > PGP Key: 0x6C226B37FDF38D55 > signature.asc Description: Message signed with OpenPGP using GPGMail
Re: 9-stable from i386 to amd64
Hi Randy, On 11 Feb 2012, at 10:58, Randy Bush wrote: > so do you have direct suggestion(s) on how to hack the system (while the > 32-bit kernel is running) so that i can boot the 64-bit kernel and get > the 64-bit world up? > > randy trying something nanobsd'ish in where you get a 64bit kernel to run with a mfsroot image which brings up networking so you can get in from remote and kick of from there ? mfsroot should hold enough stuff to buildworld etc. Just an idea. Cheers, Ruben ___ 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: FLAME - security advisories on the 23rd ? uncool idea is uncool
On 23 Dec 2011, at 17:07, Damien Fleuriot wrote: > Seriously, this is just irritating. Seriously, malevolent persons don't do engineering freeze times. I thank the FreeBSD security team for keeping vigilant on this, despite they have no official obligation as there is no SLA on the product and neither being backed by a commercial company. Best Regards, Ruben___ 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: unable to pwd in ZFS snapshot
On 26 Dec 2010, at 10:05, Daniel Braniss wrote: >> On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote: >>> this is still broken in 8.2-PRERELEASE, there seems to be a patch, but >>> it's almost a year old. >>> http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff >> >> Setting snapdir to visible should fix this right away: >> # zfs set snapdir=visible tank/foo >> > it did indeed! > any reason why this should not be the default behaviour? Personally, I want to have the snapshot, but not see the directory otherwise so that it doesn't get scooped up by rsync et al inadvertently > > thanks, > danny Cheers, Ruben___ 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: Updated py-zfs ? Re: New ZFSv28 patchset for 8-STABLE
Thanks, I'm going to check it out! On 23 Dec 2010, at 9:58, Martin Matuska wrote: > I have updated the py-zfs port right now so it should work with v28, > too. The problem was a non-existing solaris.misc module, I had to patch > and remove references to this module. > > Cheers, > mm > Regards, Ruben ___ 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"
Updated py-zfs ? Re: New ZFSv28 patchset for 8-STABLE
Hi, On 16 Dec 2010, at 13:44, Martin Matuska wrote: > Hi everyone, > > following the announcement of Pawel Jakub Dawidek (p...@freebsd.org) I am > providing a ZFSv28 testing patch for 8-STABLE. Where can I find an updated py-zfs so that zfs (un)allow/userspace/groupspace can be tested ? Regards, Ruben ___ 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 ZFSv28 patchset for 8-STABLE
Ok, On 16 Dec 2010, at 13:44, Martin Matuska wrote: > Please test, test, test. Chances are this is the last patchset before > v28 going to HEAD (finally) and after a reasonable testing period into > 8-STABLE. > Especially test new changes, like boot support and sendfile(2) support. > Also be sure to verify if you can import for existing ZFS pools > (v13-v15) when running v28 or boot from your existing pools. > > Please test the (v13-v15) compatibility layer as well: > Old usereland + new kernel / old kernel + new userland Using v28 kernel+userland seems to work on FreeBSD/amd64, I didn't dare to mix userland/kernel as that is ill advised by itself when there are major changes, like this one. I can't seem to use zfs allow/userspace/groupspace. old py-zfs just dumped core on those commands, recompiling gave my warnings about a missing solaris.misc module which persisted even after a upgrade to py26-zfs-1_1. Thanks for keeping up the good work on ZFS in FreeBSD! Best Regards, Ruben___ 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: SIGEPIPE after update to 8.1-RC2
On 20 Jul 2010, at 10:03, Jeremy Chadwick wrote: > On Tue, Jul 20, 2010 at 09:19:39AM +0200, Ruben van Staveren wrote: >> To me, this is a clear breakage and should be considered a show >> stopper issue for 8.1-RELEASE. > > Too late for that now… Oh well, errata when the culprit is found… I've filed this as misc/148781 > > ftp://ftp4.freebsd.org/pub/FreeBSD/releases/amd64/ > ftp://ftp4.freebsd.org/pub/FreeBSD/releases/i386/ Thanks! > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | Regards, Ruben___ 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: SIGEPIPE after update to 8.1-RC2
Hi, On 18 Jul 2010, at 4:20, Sean wrote: > On 18/07/2010 1:24 AM, Alex Kozlov wrote: >> Hi, stable >> >> After updating my buildbox from 26 April 8-STABLE >> to 8.1-RC2 I constantly getting SIGEPIPE >> > > > [snip] > > I'm getting the same thing; what shell are you using? I changed my shell on > one machine from /bin/tcsh to /usr/local/bin/bash and problem disappeared. Another occasion where this problem acts up: is marked as broken: does not build** Makefile possibly broken: mail/moztraybiff: grep: write error: Broken pipe moztraybiff-1.2.4_1 ---> Session ended at: Tue, 20 Jul 2010 09:04:41 +0200 (consumed 00:03:01)/usr/local/sbin/portupgrade:1473:in `get_pkgname': Makefile broken (MakefileBrok enError) from /usr/local/sbin/portupgrade:623 from /usr/local/sbin/portupgrade:614:in `each' from /usr/local/sbin/portupgrade:614 from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588 from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1248:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1241:in `order' from /usr/local/sbin/portupgrade:565:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2213 This happens during a "sudo portupgrade -va --batch" my shell is /bin/tcsh too. When I run "exec bash" after sudo -s and then do the portupgrade the problem doesn't show up. To me, this is a clear breakage and should be considered a show stopper issue for 8.1-RELEASE. All shells should be equally supported, especially when they reside in /bin. Is there already an open pr on this ? Thanks, Ruben ___ 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.0 kmem map too small
On 5 May 2010, at 15:33, Pawel Jakub Dawidek wrote: > Could you try to track down the commit that is causing your problems? > Could you try 8-STABLE kernel from before r206815? I do suspect something similar like that, and try to roll the kernel back too. I was just fine with 8.0 with zfs-on-root till the last update when my typical workload (portupgrade every now and then, make world) resulted in kmem map too small panics and more sluggish performance (spending most time in zio->io_cv) during pkgdb -F on a i386 system with 2gb memory. I have 1gb memory sized amd64 vmware fusion vm's that run without incident using the same workload. I had to bump KVA_PAGES to 512 and set vm.kmem_size=1024M to have this i386 system stable again. Prior to that I tried to lower the arc cache size but that resulted in a unresponsive system that I could not diagnose. Regards, Ruben ___ 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: kern/140661: [zfs] /boot/loader fails to work on a GPT/ZFS-only system on both 8.0-RC2 and RC3
> On Nov 18, 2009, at 21:57 , Scot Hetzel wrote: > > Make sure you have LOADER_ZFS_SUPPORT in your /etc/src.conf: > > > > dv8t01# cat /etc/src.conf > > LOADER_ZFS_SUPPORT=YES > > Ah! I also have LOADER_TFTP_SUPPORT=YES. Removing that, and everything works. > I don't know why I didn't think of that in the first place, but maybe this > is either a bug, or something that should be warned about when building > loader(8)? > > /Kenneth I had the same problem which went away after removing TFTP support and reinstalling the bootcode. For now I suggest to add the following patch: --- sys/boot/i386/loader/conf.c.orig2010-02-13 14:08:31.154391969 + +++ sys/boot/i386/loader/conf.c 2010-02-13 14:11:11.119255786 + @@ -46,6 +46,10 @@ #error "Cannot have both tftp and nfs support yet." #endif +#if defined(LOADER_ZFS_SUPPORT) && defined(LOADER_TFTP_SUPPORT) +#error "Cannot have both tftp and zfs support yet." +#endif + #if defined(LOADER_FIREWIRE_SUPPORT) extern struct devsw fwohci; #endif I think having both options corrupt each other's environment system: FreeBSD freebsd-master 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon Jan 18 16:14:24 UTC 2010 r...@freebsd-master:/usr/obj/usr/cvsup/8-stable/src/sys/VMWARE amd64 Regards, Ruben ___ 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: hald running 100%
On 13 Nov 2009, at 2:59, Dan Langille wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > After upgrading to 8.0-PRERELEASE today, I'm seeing hald at 100% on both > my laptop and my desktop: > > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND > 1500 haldaemon 1 1180 22944K 4904K CPU1 1 107:44 100.00% hald > > uptime was about 1:50 at this point. > > Seems to be relatively common from the posts I've seen. > Did you try to recompile the hald port ? Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: Open Vs Free BSD
On 19 Jun 2009, at 14:02, Timo Schoeler wrote: Sure, each one has its own merits over the others and vice versa. Above all, they contribute to the genetic diversity in the operating system pool. Which is a good thing. - Ruben ___ 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"
On the topic of network_interfaces, optional full automatic renaming of interfaces
Hi lists, Now the topic of network_interfaces has been mentioned, and the freeze for 8-stable is near I wonder if there is enough interest in the following feature to be included: http://ruben.is.verweg.com/stuff/freebsd/ifrename/ There is some dust there in that directory (It works, but is nowhere finished yet), but basically this early rc.d script takes the functionality of ifconfig_XXX_name a step further and enables optional automatic renaming of all ethernet capable interfaces, and enumerate them in the order probed by the kernel. A possible usage scenario is where you do massive imaging of a freebsd installation in where you don't know beforehand it will end up on hardware that has Broadcom or Intel NICs but it is for certain the cable will be connected to the first interface available and the same interface name can be referenced throughout all configuration files that need it (pf.conf, rc.conf(.local), /etc/rc.conf.d/network ) An other application usage is nailing down interface names using ethernet address, either because of correcting "mistakes" in the hardware (e.g. some Dell PowerEdges have the port labelled first to be probed as second and vice versa) or the necessity to only allow that interface to exist if it's MAC is the one that was configured (because of switch port ACL's) Regards, Ruben ___ 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: Do you use a value other than AUTO for network_interfaces?
On 2 Jun 2009, at 21:20, Doug Barton wrote: Up till Sunday in 8-current, and for a long time in general network.subr (part of the rc.d system) has emitted a warning that values of network_interfaces other than AUTO are deprecated. I removed that warning in HEAD Sunday, and there is no a discussion about whether or not it should be put back, and whether or not there is any need for the user to specify the list of network interfaces at all. Well, I do. I only want to configure only the interfaces that are connected and that I know about. especially in combination with IPv6 there is a nit that you'll get autoconfiguration for all interfaces unless they are all explicitly configured. e.g. bge0 connected, bge1 not, v6 autoconf on the lan. if I don't do a ipv6_ifconfig_bge1="down" and nail network_interfaces to bge0 bge1 lo0 only I'll get autoconfiguration of v6 where I don't want it to be. Being a bit of my own devils advocate here, network_interfaces="AUTO" is already true for ipv6. with network_interfaces="bge0 lo0" network.subr nevertheless sees bge1, and no configuration and takes the responsibility of starting ipv6 autoconfiguration for it. If you use a value of network_interfaces other than AUTO please speak up so that we can make an intelligent decision about this issue. you want to have a system where one still can control which interfaces are explicitly configured or skipped, with no side effects of default actions Thanks, Doug ___ 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 " Regards, Ruben ___ 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: I've borked my ZFS system upgrading to -STABLE
On 28 mei 2009, at 19:33, Niki Denev wrote: Just curious... doesn't a "zfs upgrade -a" do the same thing? The zpool upgrade is just for the pools, but the filesystems keep their original settings so we need to do that in a seperate move Regards, Niki Regards, Ruben ___ 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: I've borked my ZFS system upgrading to -STABLE
On 27 May 2009, at 22:44, Kevin Day wrote:
tries to do a chflags on it, fails because ZFS doesn't support flags
are the pools already upgraded to v13 ? if not please do so with zpool
upgrade -a
Then in single user mode do
zfs list -H | awk '{print $1}' | xargs -n 1 zfs set version=3
flags should work now
Regards,
Ruben
___
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: loader not working with GPT and LOADER_ZFS_SUPPORT
On 28 May 2009, at 9:40, Kip Macy wrote: MFC'd in 192969 Thanks for the explanation and all the hard work! Kind Regards, Ruben ___ 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: on 'btxld: zfsboot.ldr: Invalid argument' again
On 27 May 2009, at 16:11, Andriy Gapon wrote: So I have LOADER_ZFS_SUPPORT=yes in make.conf, building the most recent stable/7 and I am getting: ... btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/ zfsboot/../btx/btx/btx -l zfsboot.ldr -o zfsboot.ld -P 1 zfsboot.bin btxld: zfsboot.ldr: Invalid argument The problem seems to be that /usr/bin/btxld can not properly Shouldn't it be able to bootstrap itself using the btxld from the current build instead of what is installed ? Are we sure the btxld residing somewhere in /usr/obj is used during builds instead of the one in /usr/bin ? handle '-l zfsboot.ldr.' On the other hand, freshly built btxld in /usr/obj can handle it very well. So I worked around this by making a small temporary hack in zfsboot/ Makefile. But what is the proper solution for such source upgrade scenarios? -- Andriy Gapon ___ 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 " Regards, Ruben ___ 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: loader not working with GPT and LOADER_ZFS_SUPPORT
Hi all, On 26 May 2009, at 18:10, George Hartzell wrote: Artis Caune writes: 2009/5/26 Philipp Wuensche : Hi, I tried booting from a disk with GPT scheme, with a /boot/loader build with LOADER_ZFS_SUPPORT="yes" in make.conf. I get the following error: panic: free: guard1 fail @ 0x2fd4a6ac from /usr/src/sys/boot/i386/libi386/biosdisk.c:1053 Same problem for me. I also tried with MBR scheme, same problem. Updated kernel + world yesterday, setting LOADER_ZFS_SUPPORT="yes" in make.conf Same symptom, had to revert to the old loader for that. Prior to that I needed to do a cd /usr/src/usr.sbin/btxld && make install clean in order to work around the btxld: zfsboot.ldr: Invalid argument problem during building world+kernel Regards, Ruben ___ 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: cvsup.de.FreeBSD.org out of sync? (was: "make buildkernel KERNCONF=GENERIC fails")
On 26 May 2009, at 22:38, Christian Walther wrote: it finished successfully. From my point of view it appears that cvsup.de.freebsd.org is out of sync. cvsup.de.freebsd.org is definitely out of sync. I had build errors which only went away after switching to a different cvsup server Regards, Ruben ___ 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: RFT: ZFS MFC
On 20 May 2009, at 1:01, Kip Macy wrote: I would recommend that you use the ZFS_MFC branch - it is the same as what will be in RELENG_7 tomorrow afternoon. This is great news, and given the testing it should be no problem I feel... After setting vm.kmem_size to the recommended minimum I ran buildworld (which resides on a compressed zfs volume) while doing some ufs -> zfs and v.v. rsyncs. This was on FreeBSD/amd64 inside VMWare fusion using both v6 and v13 on the zpool (single device, no mirroring/raid) Thanks for all the hard work! Regards, Ruben ___ 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: LSI Logic raid status
On 24 Mar 2009, at 13:40, Peter Ankerstål wrote: Hi, I have a LSI Logic sata/sas raid running, is there a way to see the state of the volume, like optimal, degraded or resyncing? There is sysutils/linux-megacli Yes, looks like ports/130505 is still pending unfortunately I've tried several commands with camcontrol but I cant figure it out. -- Peter Ankerstål pe...@pean.org http://www.pean.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 " Regards, Ruben ___ 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: Panics involving ppp following routing fixes
Hi Robert, On 8 Mar 2009, at 12:24, Robert Watson wrote: On Sun, 8 Mar 2009, Ruben van Staveren wrote: Just a minor heads up: I've merged both Kip Macy's lock order fixes to the kernel routing code, and the route locking and reference counting fixes from kern/130652 to stable/7. These fixes should correct a number of reported network-related hangs. We might want to release a subset of these as an errata patch to 7.1 if they shake out well in 7-stable. Unfortunately these changes let my system panic during early boot, around the time when ppp/routing is started. Backing out these changes prevents the panic. I've filed this with some textdumps as: kern/132404: panic sleeping thread after 25th Feb src/sys/net commits http://www.freebsd.org/cgi/query-pr.cgi?pr=132404 Hi Ruben-- I've had a number of similar reports, but this one contained enough information for me to (hopefully) track it down. I've merged a fix from head as r189531 that corrects lock leak in error-handling in the routing socket code. Could you let me know if that helps with the problem? Yes, Using rev 1.143.2.9 of src/sys/net/rtsock.c indeed solves the problem, thanks! Robert N M Watson Computer Laboratory University of Cambridge Regards, Ruben ___ 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: Various route locking fixes merged to stable/7 (was: Re: Big problems with 7.1 locking up :-()
Hi, On 26 Feb 2009, at 2:28, Charles Sprickman wrote: On Wed, 25 Feb 2009, Robert Watson wrote: Just a minor heads up: I've merged both Kip Macy's lock order fixes to the kernel routing code, and the route locking and reference counting fixes from kern/130652 to stable/7. These fixes should correct a number of reported network-related hangs. We might want to release a subset of these as an errata patch to 7.1 if they shake out well in 7-stable. +1 Charles Unfortunately these changes let my system panic during early boot, around the time when ppp/routing is started. Backing out these changes prevents the panic. I've filed this with some textdumps as: kern/132404: panic sleeping thread after 25th Feb src/sys/net commits http://www.freebsd.org/cgi/query-pr.cgi?pr=132404 Regards, Ruben ___ 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: visibility of release process
On 9 Dec 2008, at 10:56, Aristedes Maniatis wrote: Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/ and see commit log per branch or any other way to see what is going on in a branch. Fisheye gives you that in a really clear way and it costs nothing to add another option for users. Though experimental, I'm greatly enjoying http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7 Maybe it is worth considering to team up and bring this under the freebsd.org umbrella ? Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: MFC ZFS: when?
Hi, On 22 Nov 2008, at 1:20, Zaphod Beeblebrox wrote: That's a pretty cop-out answer. Considering the the version of ZFS in 7.x has significant issues and the ZFS patches havn't shown any propensity to affect non-ZFS systems when ZFS is not running or loaded, the benefit of Please, give them some time zfs v13 has just ended up in -current after a long time and hard workmanship. I think everyone likes to see it up in RELENG_7 someday, but until that happens I'll be just patient. It definitely needs the time to settle before people can even think about mfc'ing it, which is not a trivial task either. Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: Request for testing: ata(4) MFC
Hi, On 17 Oct 2008, at 1:15, Steven Hartland wrote: You must be very careful with using less than 48bit addressing when both the drive and the controller supports it as some disks report errors at none standard crossover points. I saw this first hand with the highpoint driver where it totally trashed the RAID volumes. The solution was to "always" use 48bit addressing if the drive supports / requires it. Could this be the thing that is at stake ? The mirror, consisting out of ad4/ad6 got its ad4 trashed with the patch enabled. luckily it could be rebuild from the intact ad6. here is a atacontrol cap ad4 (0|chassis|ttyp0[-]) ~ > atacontrol cap ad4 Protocol Serial ATA II device model SEAGATE ST32500NSSUN250G 0825B824R1 serial number 9QE824R1 firmware revision 3AZQ cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 488390625 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management no no 0/0x00 254/0xFE PGP.sig Description: This is a digitally signed message part
Re: Request for testing: ata(4) MFC
I'm getting this on FreeBSD/amd64 with the ata patch. It also blew one part of the gmirror the system is running on. The machine is a Sun Fire X2100-M2 with 4gb memory, running from a RELENG_7 csup of a couple of hours ago. [...] atapci1: port 0xd480-0xd487,0xd400-0xd403,0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc0f mem 0xfcff9000-0xfcff9fff irq 23 at device 5.0 on pci0 ad4: 238471MB at ata2- master SATA300 ad6: 238471MB at ata3- master SATA300 [...] Trying to mount root from ufs:/dev/ufs/root ad4: FAILURE - load data ad4: setting up DMA failed ad4: FAILURE - load data ad4: setting up DMA failed GEOM_MIRROR: Request failed (error=5). ad4[READ(offset=1550114304, length=81920)] GEOM_MIRROR: Device gm0: provider ad4 disconnected. ad6: FAILURE - load data ad6: setting up DMA failed ad6: FAILURE - load data ad6: setting up DMA failed GEOM_MIRROR: Request failed (error=5). ad6[READ(offset=1550114304, length=81920)] GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). ad6: FAILURE - load data ad6: setting up DMA failed GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). ad6: FAILURE - load data ad6: setting up DMA failed ad6: FAILURE - load data ad6: setting up DMA failed ad6: FAILURE - load data ad6: setting up DMA failed GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). /libexec/ld-elf.so.1: /lib/libncurses.so.7: invalid file format ad6: FAILURE - load data ad6: setting up DMA failed GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). ad6: FAILURE - load data ad6: setting up DMA failed GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). ad6: FAILURE - load data ad6: setting up DMA failed GEOM_JOURNAL: Error while reading data from mirror/gm0s1a (error=5). Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: FreeBSD 7.1 and BIND exploit
On 23 Jul 2008, at 4:18, Paul Schmehl wrote: WRONG. You need to re-sign the zone an expire period before the signatures expire. You need to generate new keys periodically but no where near every 30 days. OK. I misspoke. I got the 30 days from Andrew Clegg's presentation and confused keys with signatures. But still, you have to resign *every* zone every 30 days. Don't forget to bump the zone serial too... as your secondaries will not catch up otherwise and start serving expired RRSIG's, leaving your zone dead in the water. - R PGP.sig Description: This is a digitally signed message part
Re: FreeBSD 7.1 and BIND exploit
On 22 Jul 2008, at 23:49, Kevin Oberman wrote: Someone needs to write a really good tutorial on dnssec. The bits and pieces are scattered about the web, but explanations of now to publish your keys, to whom they need to be published and what is involved in the ongoing maintenance are lacking. Especially a clear explanation of what is required to run both keyed and "legacy" dns at the same time. Another piece of text can be found at http://www.nlnetlabs.nl/dnssec_howto/ I can't imagine why anyone would want to run both. Resolvers which don't know how to check signatures simple don't do so and everything still works. A pretty good, though somewhat outdated tutorial can be found in NIST SP800-81. It's pretty readable and tells you how to generate keys and sign a zone properly. http://csrc.nist.gov/publications/nistpubs/800-81/SP800-81.pdf Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: Management interface for cards powered by the "mfi" driver?
On 20 Jun 2008, at 6:37, Karl Denninger wrote: The linux version sysctl is? Also I think you need to make sure mfi_linux.ko is loaded before linuxsys.ko mounts so you get the emulation hooks. Verify that via: head /compat/linux/sys/class/scsi_host/*/proc_name results in one saying: megaraid_sas or it won't think it is there. BINGO! That did it. The count is good to see if your file system & linux version sysctl stuff is in the right state. Once it detects it, then the ioctl should work. 6-stable, 7-stable and -current all have the latest stuff to support all of the ioctl stuff as Linux does for MegaCli. MegaCli does various things to try to find the card in Linux that is really strange IMHO. For FreeBSD it doesn't have to be that complicated. They unfortunately, have not released a FreeBSD MegaCli which they could ... It looks like I need to explicitly set those to load in the /boot/loader.conf instead of letting them autoload on demand... I'll make some changes in the port, for stressing out the load order and to let the wrapper work when compat.linux.osrelease is higher than 2.6.12 -- Karl Denninger [EMAIL PROTECTED] Regards, Ruben PGP.sig Description: This is a digitally signed message part
Re: Management interface for cards powered by the "mfi" driver?
On 18 Jun 2008, at 16:07, Stefan Lambrev wrote: Last time I checked it was still 2.6.12. it still is set to that value on our 2950's (running 6.2 and linux_base-fc-4_9) I never saw 2.6.12 in documentation, but you may be right. Tough in ports/UPDATING only 2.6.16 is mention. http://blogs.freebsdish.org/netchild/category/freebsd/linuxolator/ speaks also only for 2.6.16 :) I got this from reading the commit message of r1.5 of http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/mfi/mfi.c I don't know what the change set between 2.6.12 and 2.6.16 is regarding the linuxolator. As I see it the difference should only in more syscalls being supported. So if megacli has enough to get going on by setting it to just 2.6.12 it should not have a requirement for 2.6.16. Correct me if I am wrong (and I'll fix the instructions in the port) Of course, if you think mfi(4) should support your board csup up to the latest stable and see whether it works. Also run through /usr/ local/sbin/megacli instead of /usr/local/libexec/MegaCli as it will perform some sanity checks. People should only realise that they are running a linux binary under emulation in order to manage their mission critical servers. It is a thing you might not like. It has been always this way with lsi ? Actually the difference now is that we are forced to use tools under beta/experimental linuxolator ;) Sad but true. But I managed with ease to replace a hot spare not that long ago. You might want to have a peek at the cheat sheet hosted at http://tools.rapidsoft.de/perc/ Cheers, Ruben PGP.sig Description: This is a digitally signed message part
Re: Management interface for cards powered by the "mfi" driver?
Hi, On 18 Jun 2008, at 12:29, Stefan Lambrev wrote: Did you follow all steps from ports/sysutils/linux-megacli/pkg- message ? Though I think there is a small bug in the port (maintainer CCed) It wants compat.linux.osrelease=2.6.12, but I think it should be compat.linux.osrelease=2.6.16 ? Last time I checked it was still 2.6.12. it still is set to that value on our 2950's (running 6.2 and linux_base-fc-4_9) Just for reference I installed it with OVERRIDE_LINUX_BASE_PORT=f8 I think you are confusing mega-cli with megamgr (which is the one that work with amr driver) People should only realise that they are running a linux binary under emulation in order to manage their mission critical servers. It is a thing you might not like. Regards, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On 7 Jun 2008, at 22:54, Max Laier wrote: Here is a cluebat for you: Here is another one: Currently 176 messages, posted by 51 unique participants (25 % by Jo himself) Given the fact that at least these 51 persons are actually reading all the mails, and taking some 5 minutes for it you'll see that this thread already consumed a whole man month worth of time. The amount of passive readers might stretch up to a good portion of the subscriber base. I probably do not have to mention this time was better spent on other things. So far I have seen nothing else than the community at large addressing FUD of one poster, which was a genuine remark when it started, but became irrational as there was no room for compromise. I started with RELENG_7 when it was 4 days of age, and impressed by the stability from the start. Yet still we going to get our production servers up to 6.3 and go for 7.1 instead as we make use (by design) of MyISAM tables in MySQL, though I do believe I saw a fix in cvs for the issue mentioned here: http://jeffr-tech.livejournal.com/20425.html Overall, the days of RELENG_4 and RELENG_5 are over and the 15 years or so of cvs history contributes to the quality of development inside the FreeBSD project, which I was using since 2.2.4-stable. Thanks! - Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INET6 -- and why I don't use it
The interesting thing, to stay on topic, is that people are willing to explore a feature called "SCTP" which to my knowledge is younger than "IPv6". This makes the whole discussion sort of moot, right ? Speaking for the devil's advocate... The point of insecurity does not hold up if you look at RFC 5062. And we had TCP/UDP for many years and they are still serving their purpose well, so why change ? So give it a chance, only then there will be feedback and only then we can fix the problems. Otherwise it will stay just theoretical. - Ruben PGP.sig Description: This is a digitally signed message part
Re: INET6 required for SCTP in 7.0?
On 5 Mar 2008, at 15:32, Mark Andrews wrote: - IPv6 provides almost no technological upgrades beyond additional address space. DHCP addressed the auto configuration feature, VPNs addressed IPsec. That extra address space really is a big advantage. It really is so much better to be able to get to machines you need to without have to manually setup application relays because you couldn't get enough address space to be able to globally address everything want to. Please see http://www.youtube.com/watch?v=_y36fG2Oba0 This song exactly explains why you should care about IPv6 :) I don't get this "anti IPv6" behaviour. If people are not willing to adopt it, it will not get tested which in turn will make other people hesitating to jump on the bandwagon. Having it compiled in your system does not cause harm if you don't configure it and for everything else there are traffic filters. Just like IPv4. - Ruben PGP.sig Description: This is a digitally signed message part
Re: swap_pager: indefinite wait buffer
On 5 Mar 2008, at 10:06, Michael Grant wrote: My server just literally was brought to it's knees with this message spewing on the console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1203133, size: 4096 (blkno and size were varying) Some searching says that this is or was a bug. Has this been fixed yet? If so, what should I upgrade to? I'm currently running 6.3 You may consider partition backed swap instead of file backed swap if that is the case. Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED] " - Ruben PGP.sig Description: This is a digitally signed message part
Re: Manual/Wiki or other documentation for PXE install mainlyinstall.cfg?
On 21 Jan 2008, at 18:04, Drew Weaver wrote: Not specifically that I don’t know, more specifically that install.cfg doesn't know whether it’s a rl0, fxp0 or 3 or 4 others.. I have some stuff at http://ruben.is.verweg.com/stuff/freebsd/ ifrename/ that might help with this (and other cases, like the "swapped" ethernet ports of a Dell PE 2950) YMMV - Ruben PGP.sig Description: This is a digitally signed message part
Re: ifconfig options?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Krassimir, Krassimir Slavchev wrote: > Hi, > > 'ifconfig -l [address_family]' does not work correct on RELENG_7 If you suspect a regression in functionality, and you can reproduce it the best thing one can do is submit a problem report with send-pr http://www.freebsd.org/send-pr.html Having them reported on the list may seem nice but stands less chance the item is picked up. Regards, Ruben -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHb3/5Z88+mcQxRw0RCNdPAJ4rqsiLuVwr9QP2PAS3ALdqjNGy1QCfRu9q 65+69EzO6S2j4qyjApq7TBI= =ygDu -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: kldxref: file isn't dynamically-linked -- expected behaviour?
On 19 Oct 2007, at 8:04, Chris Chou wrote: I saw the same message when upgrading from RELENG_6 to RELENG_7, and it disappeared when I re-installed the RELENG_7 kernel. Was your user land already upgraded to RELENG_7 ? if concerned, find the version 7 kldxref from /usr/obj and rerun it. apart from that and a few other nits that aren't really worth mentioning as I reused my kernel config from six the upgrade was really smooth. Thanks to all who participated in getting RELENG_7 branched! - Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no glxgears with xorg 7.2?
On 22 May 2007, at 15:30, Iulian M wrote: running pkg_which(1) on "glxgears" on my not yet updated system, reveals xorg-clients as the origin of glxgears(1). If I'm not mistaken, xorg-clients was renamed to xorg-apps during the upgrade of xorg 6.9 to xorg 7.2. That's true, xorg-apps is a meta-package for a lot of small applications X11-related. ... but glxgears isn't included. Don't ask me why, I also was looking for it some time ago, but couldn't find it. I do believe glxgears has moved to graphics/mesa-demos And the much more useful "glxinfo" also. should it be added to the meta package too just out of "expectancy" ? - Ruben PGP.sig Description: This is a digitally signed message part
Re: NFS == lock && reboot
Chris H. wrote: > # uname -a > FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 > 16:27:14 PST 2007 > > Greetings, > Does anyone know when NFS and friends will be working again? I haven't > been able > to /safely/ use it from 4.8 on. I remember some talk on the list > sometime ago and > then it seemed to be resolved, as the discussion ended. So I thought > it was > fixed. Seems not. :( > > > # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ > > Fatal double fault > eis 0x0blah > eiblah blah0x > panic double fault > no dump device defined > rebooting in 15sec... You might want to try to configure a dump device, or as a last resort, take a picture of the crash and put that on your site > > Hmmm... that's not good. :( > > I can't remember all the "ei*" numbers between the Fatal and panic lines, > BUT I /can/ reproduce this at will - I simply need to copy a file larger > than a few k to a mounted host. Yes, this /does/ happen /every/ time. > > Any and all help with this will be /GREATLY/ appreciated. > > Thank you for all your time and consideration in this matter. > > --Chris Regards, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can we resurrect linux-firefox-1.5 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16 Jan 2007, at 20:09, Luigi Rizzo wrote: Additionally, i could not find a way to make the flash plugin work, which is a major annoyance given the amount of flash content that one finds in the services i use daily (some work related too). You might give the native firefox a try with linuxpluginwrapper, linux-flashplugin-7 and run firefox as env XLIB_SKIP_ARGB_VISUALS=1 firefox (or edit /usr/local/bin/firefox and insert a export XLIB_SKIP_ARGB_VISUALS=1) still not optimal but trivial flash stuff should be usable. - - Ruben -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFFsM+OZ88+mcQxRw0RAsJEAJ92iqOiBJaCJQOfoEzgxlRiH77UEwCfVbdR ZNj+vZj2iG+VswvvwEYDhTQ= =WmzW -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: When will the new BCE driver in HEAD be incorporated into RELENG_6?
On 26 Oct 2006, at 1:21, Sam Baskinger wrote: Adding to the excitement, our band of attack squirrels haven't been able to bring down our 2950 yet with this one. We are using the if_bce.c from the HEAD w/ a small chunk about vlans commented out (for any wondering). We're trying outbound UDP_STREAM tests w/ netperf of big and small payloads to a machine on the same 100Mb switch. Nothing fancy, but what we could once crash in seconds now hangs tough till the end of the test. Also adding, It survived multiple buildworld runs over NFS v3 udp hard mounts while inserting a 11gb compressed mysql dump over NFS into the database running on local disks. Both machines involved for the buildworld are 2950's running 6.2-PRERELEASE, identically configured. source for the mysqldump is a NetApp F810c, all connections over gig ethernet. this is with r 1.2.2.6 of if_bce.c - Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: When will the new BCE driver in HEAD be incorporated into RELENG_6?
On 23 Oct 2006, at 18:44, Brian A. Seklecki wrote:
So probably MFC/RFP into RELENG_6 after two weeks? Is there an
official FreeBSD PR on this to update?
Apparently it is already there ?
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bce/if_bce.c?
rev=1.2.2.6&content-type=text/x-cvsweb-markup
I just cvsupped and installed on our 2950's
a previous C++ project build did indeed trigger the bce watchdog, but
with the new version it is just fine.
Thing which is a bit odd though, is that copying +100 gig of data
from nfs to the 2950 which it was doing previously didn't lock things
up with the old driver.
My thanks to Scott Long and all others who worked on this!
Regards,
Ruben van Staveren
~BAS
On Mon, 23 Oct 2006, Bill Moran wrote:
In response to Jason Thomson <[EMAIL PROTECTED]>:
Scott Long wrote:
I'll cautiously say that the latest set of changes to bce might be
interesting for you. It now survives all of my ttcp and
netblast tests
in both UDP and TCP. Please let me know if it makes things better,
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-
[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Installing FreeBSD 6.0 on a Dell PE850 (Re: Dell PE850 and SC430 issue)
Lee,
On 25 Sep 2005, at 11:59, lee sheng wrote:
Then I decide to install pfsense, the project which is based on
FreeBSD 6
Beta, everything goes smoothly and I can install, it is really
annoying as I
wonder why it hangs on the sysinstall until I can't do anything. Is
there
any solution or workaround on these, I guess there might be someone
successfully installing freebsd on it.
Please see http://tinyurl.com/7rm94
"some assembly required, parts not included."
Thanks.
Regards,
geek00L
Cheers,
Ruben
--
= Ruben van Staveren -- http://ruben.is.verweg.com/
= An Apple a day keeps the cluepon away
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Logitech Cordless Internet Pro Desktop
On 18 May 2005, at 9:20, Paig Chong Woo wrote: It seems that FreeBSD already detect the mouse as ums0, and the keyboard as ukbd0, but my mouse didn't work. usbd already attach my mouse as ums0, and still nothing happens Anyone had the similar problem? Or even better, does anyone has any solution for this :-) Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=63837 for a fix. Works for my Logitech Cordless Desktop. Regards, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: I can not surf on Flash powered sites.
On Wed, Mar 02, 2005 at 12:23:42AM +0200, Ege Mukan wrote: > Nowavadays whenever I want to surf on websites which contains flash > things my firefox or mozilla shuts itself. > > Did you ever encounter this problem. And if you'd how did you eliminate ??? > Are you using Xorg6.8.1 and have enabled the Composite extension ? (as in Section "Extensions" Option "Composite" "Enable" EndSection ) Then add this line to /usr/X11R6/bin/firefox, just beneath the #! /bin/sh export XLIB_SKIP_ARGB_VISUALS=1 > Thanks in advance. > > Ege Mukan > [EMAIL PROTECTED] Kind Regards, Ruben van Staveren -- ,-_ .--------. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Ofcourse, in my dreams I have the money and all the girls too...| #> =/ () `' 4 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Shuttle ST61G4 hanging during boot with Hitachi 7K250 sata and Sil 3512.
Hi, I've currently lingering around here a shuttle ST61G4 bare bone, and decided to give the FreeBSD 5.3 beta6 iso a try. It is equipped with a NEC ND-3500A and a Hitachi Deskstar 7K250 (160 GB, SATA flavour). Kernel startup just goes fine up until it arrives at the sata disc. It just hangs there with the following line: ata2-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 What does this error message exactly mean ? The controller is probed as a atapci1: which is just right. I tried different combinations of ata and sata headers, but only when disconnecting the sata disc gets me to the install screen. (but of course no disc to install to then) I also made sure the drive cables are not to close to either the CPU and GPU. Cheers, Ruben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: BSD network stack virtualization
Isn't this something that can overcome the current shortcomings of jail(2) ? (the no other stacks/no raw sockets problem) - Ruben -- ,-_ .. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Men are from Mars. Women are from Venus. Computers are from hell| #> =/ () `' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PCM broken in 4.7RC
I have a stalling PCM since 4.4-RELEASE, using kernel modules from 4.3-RELEASE solves my problems for the moment. see PR #33986 http://www.freebsd.org/cgi/query-pr.cgi?pr=33986 We are talking about an AudioPCI ES1370 on an Asus P2B-DS Cheers, Ruben -- ,-_ .. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Men are from Mars. Women are from Venus. Computers are from hell| #> =/ () `' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
path MTU Re: I cannot access some websites
On Thu, May 02, 2002 at 06:23:23PM -0600, Korey Pelton wrote: > Hello, > > I apologize for cross-posting this, but I haven't recieved a reply from > -questions yet, and I need to get this fixed for my job or I will have to > switch to Windows. Not an exucse, because you are likely to have the same problem. It sounds like a MTU issue, consult your network administrator and ask them about path MTU and analyze your traffic with tcpdump/ethereal. You are sending ip traffic with a smaller MTU than the receiving host. These hosts respond to your traffic but sets the 'DF' bit (Don't Fragment) when sending a reply. That reply is discarded when it arrives at the network host (router or endpoint) which has a smaller MTU. Normally this would generate an IP fragment but is wasted due to the DF bit. The network host responds to you with an ICMP NeedFragment to notify you it went wrong. Kind regards, Ruben -- ,-_ .------------. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Men are from Mars. Women are from Venus. Computers are from hell| #> =/ () `' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Audio can hang machine. SMP related
On Mon, Jan 07, 2002 at 07:55:14PM +0100, Ruben van Staveren wrote: > These hangs seem very similar to what I am experiencing and wrote earlier > about in message id's <[EMAIL PROTECTED]> and > <[EMAIL PROTECTED]> > > I've recompiled almost everything on my system that possibly could interact > with kernel internals. I set my bios to MPS 1.4 specification (I still wonder > what it does, has something to do with interrupt assignment ?) but still > these lockups while running a SMP kernel. Uniprocessor is just fine. > > For the moment I have unloaded my audio device drivers from loader.conf > (FYI, it is an AudioPCI ES1370 card (SB 128 PCI)) System is running just fine ever since, putting back in the audio support makes it unstable again. Is there an open PR for this ? Kind regards, Ruben -- ,-_ .------------. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Men are from Mars. Women are from Venus. Computers are from hell| #> =/ () `' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
symmetric multiprocessing: MPS 1.4 recommended ?
On Sat, Nov 10, 2001 at 08:05:46PM +0100, Ruben van Staveren wrote: > > Same here, stability `improved' when stripping out USB and I2C support. > this all happend when I upgraded from RELENG_4_3 to RELENG_4 on last sunday. > I had resynced with RELENG_4 today, but no effect. > > dmesg and kernel config can be found on http://ruben.is.verweg.com/freebsd > > Motherboard is an ASUS P2B-DS. I've cvs'upped to 4.5-PRERELEASE recently to see if the problems went away. Stability seemed to have improved while running X but still those total lockups. There where no stability issues whatsoever when not running X. Now I did something completely different: I flashed my bios to version 1013 and turned on MPS 1.4 support. (It was bios rev# 1008B and MPS 1.1) has http://www.freebsd.org/cgi/getmsg.cgi?fetch=7960+0+/usr/local/www/db/text/2001/freebsd-smp/20010603.freebsd-smp anything to do with it ? The system hasn't hung ever since... If it is truly recommended, is it worth mentioning it in for example the LINT or GENERIC kernel config files ? > > The system can run fine for a day, serving as gateway and firewall and > providing email and proxy for the home network. When running an interactive X > logon it runs for about a couple of hours before freezing up. sometimes the > machine comes back after a couple of minutes, only to freeze again later on. > > Some of the freezes happened while just browsing with mozilla, a make > deinstall of a port, or after an rm -rf /usr/obj. It is not reproducable > however: the system did compile and install a whole userland and kernel while > running an interactive X session Regards, Ruben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [SOLVED] Broken sound with 4.4-RC
On Mon, Sep 17, 2001 at 09:24:46PM -0500, Mike Meyer wrote: > > I found the source of this jar. > > I'he installed 'gkrellm' from ports. > > It's installed as root:kmem with SUID bit (no SGID, however). > > Running gkrellm while audio playback produces sound breakage. > > The solution is removing SUID bit from gkrellm binary. > > All metallic effects have disappeared now. > > There have been multiple reports of gkrellm causing SMP systems to > freeze - more accurately, gkrellm plugins cause this to > happen. Which prompts me to ask if you are running SMP, and if you > have any gkrellm plugins running. > > FWIW, if you define WITHOUT_SENSOR when you install gkrellm, it will > not turn on the SUID bit on the binary. > > http://ruben.is.verweg.com |BSD is for unix lovers | #> =/ () `+---' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fxp drivers
On Mon, May 21, 2001 at 09:30:50AM -0400, Mike Tancsa wrote: > What type of fxp card is it ? I have some that are close to 4yrs old and > they work just fine. > What are the serial no's ? the NIC's chipset identifiers ? model series ? There are a few cards we call fxp at http://support.intel.com/support/network/adapter/pro100/21397.htm It is not just about fxp going mii, but whole companies using mostly Intel EtherExpress (Pro) cards and are dependant on a stable driver, so if it is possible, please include as much information as you can :) Kind regards, Ruben -- ,-_ .----. /() ) | Ruben van Staveren | Linux is for Microsoft Haters,|_o (__ ( | http://ruben.is.verweg.com | BSD is for Unix Lovers| #> =/ () `+---' 4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
