Re: Nullfs leaks i-nodes
--On Wednesday, 08 May, 2013 12:13 PM +0300 Konstantin Belousov
kostik...@gmail.com wrote:
On Tue, May 07, 2013 at 08:30:06AM +0200, G??ran L??wkrantz wrote:
I created a PR, kern/178238, on this but would like to know if anyone
has any ideas or patches?
Have updated the system where I see this to FreeBSD 9.1-STABLE #0
r250229 and still have the problem.
The patch below should fix the issue for you, at least it did so in my
limited testing.
What is does:
1. When inactivating a nullfs vnode, check if the lower vnode is
unlinked, and reclaim upper vnode if so. [This fixes your case].
2. Besides a callback to the upper filesystems for the lower vnode
reclaimation, it also calls the upper fs for lower vnode unlink.
This allows nullfs to purge cached vnodes for the unlinked lower.
[This fixes an opposite case, when the vnode is removed from the
lower mount, but upper aliases prevent the vnode from being
recycled].
3. Fix a wart which existed from the introduction of the nullfs caching,
do not unlock lower vnode in the nullfs_reclaim_lowervp(). It should
be completely innocent, but now it is also formally safe.
4. Fix vnode reference leak in nullfs_reclaim_lowervp().
Please note that the patch is basically not tested, I only verified your
scenario and a mirror of it as described in item 2.
diff --git a/sys/fs/nullfs/null.h b/sys/fs/nullfs/null.h
index 4f37020..a624be6 100644
--- a/sys/fs/nullfs/null.h
+++ b/sys/fs/nullfs/null.h
@@ -53,8 +53,11 @@ struct null_node {
LIST_ENTRY(null_node) null_hash; /* Hash list */
struct vnode*null_lowervp; /* VREFed once */
struct vnode*null_vnode;/* Back pointer */
+ u_int null_flags;
};
+#defineNULLV_NOUNLOCK 0x0001
+
#defineMOUNTTONULLMOUNT(mp) ((struct null_mount *)((mp)-mnt_data))
#defineVTONULL(vp) ((struct null_node *)(vp)-v_data)
#defineNULLTOV(xp) ((xp)-null_vnode)
diff --git a/sys/fs/nullfs/null_vfsops.c b/sys/fs/nullfs/null_vfsops.c
index 02932bd..544c358 100644
--- a/sys/fs/nullfs/null_vfsops.c
+++ b/sys/fs/nullfs/null_vfsops.c
@@ -65,7 +65,6 @@ static vfs_statfs_t nullfs_statfs;
static vfs_unmount_t nullfs_unmount;
static vfs_vget_t nullfs_vget;
static vfs_extattrctl_tnullfs_extattrctl;
-static vfs_reclaim_lowervp_t nullfs_reclaim_lowervp;
/*
* Mount null layer
@@ -391,8 +390,22 @@ nullfs_reclaim_lowervp(struct mount *mp, struct
vnode *lowervp) vp = null_hashget(mp, lowervp);
if (vp == NULL)
return;
+ VTONULL(vp)-null_flags |= NULLV_NOUNLOCK;
vgone(vp);
- vn_lock(lowervp, LK_EXCLUSIVE | LK_RETRY);
+ vput(vp);
+}
+
+static void
+nullfs_unlink_lowervp(struct mount *mp, struct vnode *lowervp)
+{
+ struct vnode *vp;
+
+ vp = null_hashget(mp, lowervp);
+ if (vp == NULL || vp-v_usecount 1)
+ return;
+ VTONULL(vp)-null_flags |= NULLV_NOUNLOCK;
+ vgone(vp);
+ vput(vp);
}
static struct vfsops null_vfsops = {
@@ -408,6 +421,7 @@ static struct vfsops null_vfsops = {
.vfs_unmount = nullfs_unmount,
.vfs_vget = nullfs_vget,
.vfs_reclaim_lowervp = nullfs_reclaim_lowervp,
+ .vfs_unlink_lowervp = nullfs_unlink_lowervp,
};
VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK | VFCF_JAIL);
diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c
index f59865f..3c41124 100644
--- a/sys/fs/nullfs/null_vnops.c
+++ b/sys/fs/nullfs/null_vnops.c
@@ -692,18 +692,21 @@ null_unlock(struct vop_unlock_args *ap)
static int
null_inactive(struct vop_inactive_args *ap __unused)
{
- struct vnode *vp;
+ struct vnode *vp, *lvp;
struct mount *mp;
struct null_mount *xmp;
vp = ap-a_vp;
+ lvp = NULLVPTOLOWERVP(vp);
mp = vp-v_mount;
xmp = MOUNTTONULLMOUNT(mp);
- if ((xmp-nullm_flags NULLM_CACHE) == 0) {
+ if ((xmp-nullm_flags NULLM_CACHE) == 0 ||
+ (lvp-v_vflag VV_NOSYNC) != 0) {
/*
* If this is the last reference and caching of the
-* nullfs vnodes is not enabled, then free up the
-* vnode so as not to tie up the lower vnodes.
+* nullfs vnodes is not enabled, or the lower vnode is
+* deleted, then free up the vnode so as not to tie up
+* the lower vnodes.
*/
vp-v_object = NULL;
vrecycle(vp);
@@ -748,7 +751,10 @@ null_reclaim(struct vop_reclaim_args *ap)
*/
if (vp-v_writecount 0)
VOP_ADD_WRITECOUNT(lowervp, -1);
- vput(lowervp);
+ if ((xp-null_flags NULLV_NOUNLOCK) != 0)
+ vunref(lowervp);
+ else
+ vput(lowervp);
free(xp, M_NULLFSNODE);
return (0);
diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c
index
Re: 32GB limit per swap device?
Hi Daniel, Just a stupid question, as I have done something different. Can't you use a different device or slice for the dump? In that case there is no limitation on the size of the dump device, as far as I know. My setup: 96GB, dump device local 160G disc, slice for swap, slice for dump, system boots from nanobsd usb-stick. All other disk ZFS filesystems using LSI HBA for NFS and Samba clients. MVH Göran --On August 9, 2011 17:26:46 +0300 Daniel Kalchev dan...@digsys.bg wrote: I am trying to set up 64GB partitions for swap for a system that has 64GB of RAM (with the idea to dump kernel core etc). But, on 8-stable as of today I get: WARNING: reducing size to maximum of 67108864 blocks per swap unit Is there workaround for this limitation? Daniel ___ 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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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: zfs hang in zio-io_cv) with dd read
--On October 7, 2010 17:50:42 +0200 John Hay j...@meraka.org.za wrote: On Thu, Oct 07, 2010 at 02:35:31PM +0200, Ivan Voras wrote: On 10/07/10 14:15, John Hay wrote: Hi, I got hold of a SunFire X4500 with 48 X 500G disks and thought to try FreeBSD 8-stable with zfs on it. I have setup the two boot disks in a zfs mirror and then the rest in a pool of 6 X raidz2 of 7 disks each. I have created a 10G file with dd in the second pool, but if I try to read it with dd, dd will hang in zio-io_cv) according to ^T. This happens everytime. The first time I saw messages about an interrupt storm, so I have put hw.intr_storm_threshold=1 in /etc/sysctl.conf. According to systat -vm 1 there is atapci for 2-3 seconds and then it is quiet. There are two things you could try: 1) use the AHCI driver (ahci_load=YES in /boot/loader.conf) and 2) disable superpages, they don't get along on a few models of Opterons (vm.pmap.pg_ps_enabled=0 in /boot/loader.conf). ahci does not grab them. According to the ahci man page, it can handle Marvell 88SX61xx, while these are MV88SX6081 according to pciconf -lcv: atap...@pci0:1:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 4 split transactions Then try mvs_load=YES m...@pci0:6:2:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI m...@pci0:5:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI I have also set vm.pmap.pg_ps_enabled=0 in loader.conf, but that did not make a difference either. :-( Once dd hang in that zio-io_cv) state the rest of the machine is ok and everything works as long as you stay away from the directory where the file is that you dd from. There are no messages in dmesg or /var/log/messages. John -- John Hay -- j...@meraka.csir.co.za / j...@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 /glz ___ 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 is NFSv4 so slow?
--On September 12, 2010 11:44:40 -0400 Rick Macklem rmack...@uoguelph.ca wrote: On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote: snip My results seems to confirm a factor of two (or 1.5) but it's stable: new nfs nfsv4 369792 bytes transferred in 71.932692 secs (55607119 bytes/sec) 369792 bytes transferred in 66.806218 secs (59874214 bytes/sec) 369792 bytes transferred in 65.127972 secs (61417079 bytes/sec) 369792 bytes transferred in 64.493585 secs (62021204 bytes/sec) old nfs nfsv3 369792 bytes transferred in 42.290365 secs (94583478 bytes/sec) 369792 bytes transferred in 42.135682 secs (94930700 bytes/sec) 369792 bytes transferred in 41.404841 secs (96606332 bytes/sec) 369792 bytes transferred in 41.461210 secs (96474989 bytes/sec) new nfs nfsv3 369792 bytes transferred in 63.172592 secs (63318121 bytes/sec) 369792 bytes transferred in 64.149324 secs (62354044 bytes/sec) 369792 bytes transferred in 62.447537 secs (64053284 bytes/sec) 369792 bytes transferred in 57.203868 secs (69924813 bytes/sec) Client: FreeBSD 8.1-STABLE #200: Sun Sep 12 12:03:25 CEST 2010 r...@skade.glz.hidden-powers.com:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ (2600.26-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Family = f Model = 6b Stepping = 2 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:1b:21:2e:7d:3c inet 10.255.253.3 netmask 0xff00 broadcast 10.255.253.255 media: Ethernet autoselect (1000baseT full-duplex) status: active Server: FreeBSD 8.1-STABLE #74: Sun Sep 5 18:47:12 CEST 2010 r...@midgard.glz.hidden-powers.com:/usr/obj/usr/src/sys/SERVER amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) 9550 Quad-Core Processor (2210.08-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x100f23 Family = 10 Model = 2 Stepping = 3 re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3898VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 00:1f:d0:59:d8:e2 inet 10.255.253.1 netmask 0xff00 broadcast 10.255.253.255 media: Ethernet autoselect (1000baseT full-duplex) status: active Network: Systems connected via two Netgear GS108T, one system to each switch, the switches connected via TP cable. Patchar: stable-8-v15.patch zfs_metaslab_v2.patch zfs_abe_stat_rrwlock.patch arc.c.9.patch r211970.patch Cheers, Göran --- There is hopeful symbolism in the fact that flags do not wave in a vacuum. -- Arthur C. Clarke ___ 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: top Segmentation faulting on 8.0p2 amd64 (nss_ldapd problem?)
I had exactly this problem. Removing an old /etc/localtime fixed the problem. /glz --On January 23, 2010 2:02:04 +0100 Harald Schmalzbauer h.schmalzba...@omnilan.de wrote: Mikolaj Golub schrieb am 22.01.2010 23:26 (localtime): On Wed, 20 Jan 2010 08:06:23 +0100 Harald Schmalzbauer wrote: Dear all, I have no idea why top crashes with segmentation fault on my amd64 machine running FreeBSD 8.0-RELEASE-p2. If someone wants to have a loot at the core dump: http://www.schmalzbauer.de/downloads/top.core core file is useless without binary and libraries. So it is better to run gdb on your host, produce backtrace and post here: gdb /usr/bin/top top.core bt And sure a backtrace from the top built with -g would be much better. cd /usr/src/usr.bin/top CFLAGS=-g make Unfortunately nss_ldap seems to be the culprit. gdb /usr/bin/top top.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 bt: # 0 0x000800d08403 in __nss_compat_gethostbyname () from # /usr/local/lib/nss_ldap.so.1 0 0x000800d08403 in # __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 1 # 0x000800d0606f in _nss_ldap_getpwent_r () from # /usr/local/lib/nss_ldap.so.1 2 0x0008009ffc54 in # __nss_compat_getpwent_r () from /lib/libc.so.7 3 0x000800a84a3d in # nsdispatch () from /lib/libc.so.7 # 4 0x000800a50976 in getpwent_r () from /lib/libc.so.7 # 5 0x000800a50596 in sysctlbyname () from /lib/libc.so.7 # 6 0x00406c6d in machine_init (statics=0x7fffea30, # do_unames=1 '\001') at /usr/src/usr.bin/top/machine.c:257 # 7 0x00407a10 in main (argc=1, argv=0x7fffeb08) at /usr/src/usr.bin/top/../../contrib/top/top.c:458 I'm using nss_ldapd-0.7.2 and there's no way to live without ldap... Any help highly appreciated! Thanks, -Harry ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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: top Segmentation faulting on 8.0p2 amd64 (nss_ldapd problem?)
Sorry, noise. Problem can back after a reboot. But now it only affects non super-users, it works just fine for root. When it first happened for me, even root cored. /glz --On January 23, 2010 13:57:41 +0100 Goran Lowkrantz goran.lowkra...@ismobile.com wrote: I had exactly this problem. Removing an old /etc/localtime fixed the problem. /glz --On January 23, 2010 2:02:04 +0100 Harald Schmalzbauer h.schmalzba...@omnilan.de wrote: Mikolaj Golub schrieb am 22.01.2010 23:26 (localtime): On Wed, 20 Jan 2010 08:06:23 +0100 Harald Schmalzbauer wrote: Dear all, I have no idea why top crashes with segmentation fault on my amd64 machine running FreeBSD 8.0-RELEASE-p2. If someone wants to have a loot at the core dump: http://www.schmalzbauer.de/downloads/top.core core file is useless without binary and libraries. So it is better to run gdb on your host, produce backtrace and post here: gdb /usr/bin/top top.core bt And sure a backtrace from the top built with -g would be much better. cd /usr/src/usr.bin/top CFLAGS=-g make Unfortunately nss_ldap seems to be the culprit. gdb /usr/bin/top top.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Core was generated by `top'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libncurses.so.8...done. Loaded symbols for /lib/libncurses.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libkvm.so.5...done. Loaded symbols for /lib/libkvm.so.5 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/nss_ldap.so.1...done. Loaded symbols for /usr/local/lib/nss_ldap.so.1 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 bt: # 0 0x000800d08403 in __nss_compat_gethostbyname () from # /usr/local/lib/nss_ldap.so.1 0 0x000800d08403 in # __nss_compat_gethostbyname () from /usr/local/lib/nss_ldap.so.1 1 # 0x000800d0606f in _nss_ldap_getpwent_r () from # /usr/local/lib/nss_ldap.so.1 2 0x0008009ffc54 in # __nss_compat_getpwent_r () from /lib/libc.so.7 3 0x000800a84a3d in # nsdispatch () from /lib/libc.so.7 # 4 0x000800a50976 in getpwent_r () from /lib/libc.so.7 # 5 0x000800a50596 in sysctlbyname () from /lib/libc.so.7 # 6 0x00406c6d in machine_init (statics=0x7fffea30, # do_unames=1 '\001') at /usr/src/usr.bin/top/machine.c:257 # 7 0x00407a10 in main (argc=1, argv=0x7fffeb08) at /usr/src/usr.bin/top/../../contrib/top/top.c:458 I'm using nss_ldapd-0.7.2 and there's no way to live without ldap... Any help highly appreciated! Thanks, -Harry ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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: Smartctl and ahci
Hi, Have installed 5.39-rc1 by hacking the port (remove all patches, don't use gmake) and it works just fine with ada devices. It also handles our HighPoint controllers, which I don't thing 5.38 did. /glz --On December 7, 2009 13:06:12 +0200 Andriy Gapon a...@icyb.net.ua wrote: on 07/12/2009 12:42 b. f. said the following: There is no support in smartmontools 5.38 for the new ahci(4) driver in FreeBSD 8.x and 9.x, or for the new ATA_CAM option that mav@ just introduced into FreeBSD 9.x. You need to wait for smartmontools 5.39 to be released, or build smartmontools from the latest svn sources. The smartmontools developers have made some changes beginning on Oct.6, and claim to support the new FreeBSD drivers in the latest sources. BTW, 5.39rc1 is available. -- 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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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
error building zfsboot
On a system cvsuped Tue May 26 08:30 CEST 2009 and only LOADER_ZFS_SUPPORT=yes in the make.conf, I get the following error: === sys/boot/i386/zfsboot (all) objcopy -S -O binary zfsldr.out zfsboot1 cp /dev/null zfsboot.ldr cc -Os -g -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DB OOT2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/zfsboot/../../zfs -I/usr/src/sys/boot/i386/zfsboot/../../../cddl/boot/zfs -I/u sr/src/sys/boot/i386/zfsboot/../btx/lib -I. -I/usr/src/sys/boot/i386/zfsboot/../boot2 -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferr ed-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -S -o zfsboot.s.tmp /usr/src/sys/boot/i386/zfsboot/zfsboot.c In file included from /usr/src/sys/boot/i386/zfsboot/zfsboot.c:276: /usr/src/sys/boot/i386/zfsboot/../../zfs/zfsimpl.c: In function 'vdev_init_from_nvlist': /usr/src/sys/boot/i386/zfsboot/../../zfs/zfsimpl.c:474: warning: assignment discards qualifiers from pointer target type /usr/src/sys/boot/i386/zfsboot/../../zfs/zfsimpl.c:476: warning: assignment discards qualifiers from pointer target type sed -e '/align/d' -e '/nop/d' zfsboot.s.tmp zfsboot.s rm -f zfsboot.s.tmp as --32 -o zfsboot.o zfsboot.s cc -Os -g -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DB OOT2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/zfsboot/../../zfs -I/usr/src/sys/boot/i386/zfsboot/../../../cddl/boot/zfs -I/u sr/src/sys/boot/i386/zfsboot/../btx/lib -I. -I/usr/src/sys/boot/i386/zfsboot/../boot2 -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferr ed-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -c /usr/src/sys/boot/i386/zfsboot/../boot2/sio.S ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o zfsboot.out /usr/obj/usr/src/sys/boot/i386/zfsboot/../btx/lib/crt0.o zfsboot.o sio.o /usr/obj/usr/ src/tmp/usr/lib/libstand.a objcopy -S -O binary zfsboot.out zfsboot.bin 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 *** Error code 2 Stop in /usr/src/sys/boot/i386/zfsboot. *** Error code 1 Looking in the directory, zfsboot.ldr is empty: # cd /usr/obj/usr/src/sys/boot/i386/zfsboot/ # ls .depend sio.o zfsboot.h zfsboot.o zfsboot.s zfsldr.o machine zfsboot.bin zfsboot.ldr zfsboot.out zfsboot1 zfsldr.out # 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 # file zfsboot.ldr zfsboot.ldr: empty Any pointers? Cheers, Göran ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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: error building zfsboot
--On May 26, 2009 11:28:17 +0200 Mickael MAILLOT mickael.mail...@gmail.com wrote: hi, Simply update btxld first: cd /usr/src/usr.sbin/btxld make install clean then you can buildworld Thanks, that worked. 2009/5/26 Dimitry Andric dimi...@andric.com: On 2009-05-26 10:20, Goran Lowkrantz wrote: On a system cvsuped Tue May 26 08:30 CEST 2009 and only LOADER_ZFS_SUPPORT=yes in the make.conf, I get the following error: ... btxld: zfsboot.ldr: Invalid argument ... Looking in the directory, zfsboot.ldr is empty: Your CVSup mirror may be out of date, this was fixed as of r192697. Since you are using CVS and not Subversion, make sure you have usr.sbin/btxld/btxld.c revision 1.10.2.1. ___ 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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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: ZFS MFC heads up
Ran into the same thing on -CURRENT when we went version 13. Some manual intervention fixed it. http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000508.html /glz --On Thursday, May 21, 2009 12:42 PM +0300 Pertti Kosunen pertti.kosu...@pp.nic.fi wrote: Kip Macy wrote: I will be MFC'ing the newer ZFS support some time this afternoon. Both world and kernel will need to be re-built. Existing pools will continue to work without upgrade. Mounting local file systems:. internal error: out of memory internal error: out of memory internal error: out of memory internal error: out of memory I get this in dmesg after make installkernel shutdown -r now, zfs pool is not mounted. /usr is on zfs so can't installworld. 2GB memory and 4x 1TB raid-z on amd64, / is 2x 2GB gmirror. ___ 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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.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 and iSCSI for disks.
Trying to build 2.1.1 on a CURRENT results in this: === iscsi/initiator (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c: In function 'iscsi_open': /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:120: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:122: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:126: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c: In function 'iscsi_close': /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:149: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:154: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c: In function 'iscsi_ioctl': /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:184: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:210: error: invalid operands to binary /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c: In function 'iscsi_read': /usr/src/sys/modules/iscsi/initiator/../../../dev/iscsi/initiator/iscsi.c:290: error: invalid operands to binary /glz --On April 9, 2009 10:43:06 +0300 Danny Braniss da...@cs.huji.ac.il wrote: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --enig90DADA8437A99D893FB775F8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Danny Braniss wrote: Garance A Drosihn wrote: Some friends of mine are looking at the new DroboPro, which makes a= lot of disk space available via iSCSI (in addition to firewire 800), and they were wondering how well iSCSI works with FreeBSD. I haven't= paid attention to iSCSI support. Is there anyone using it heavily for disk-storage under FreeBSD? Has there been much changed for iSCSI support in the 8.x branch, or is 7.x support working fine? I suppose you are interested in the client (initiator) side of iSCSI= support. It hasn't changed much between 7.x and 8.x but there are apparently some announcements of a newer version: http://lists.freebsd.org/pipermail/freebsd-scsi/2009-March/003834.htm l= I can't find any more information on it. the latest is in: http://www.cs.huji.ac.il/~danny/ftp/freebsd/iscsi-2.1.1.tar.gz Thanks! Is there anything in particular you'd like to get tested in the new version, any significant changes or improvements? mainly fixed some bugs, and some code cleanup. give it a spin, and let me know what target you are testing. btw, the default tag opening is a bit concervative (1), you might want to change it to somewhat larger, say 64 or 128. 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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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
Problems with samba and vista on 7.1-STABLE
)
select(24,{6 23},{},0x0,{21.288167 })= 0 (0x0)
gettimeofday({1234648099.279293 },0x0) = 0 (0x0)
gettimeofday({1234648099.279370 },0x0) = 0 (0x0)
gettimeofday({1234648099.279417 },0x0) = 0 (0x0)
select(24,{6 23},{},0x0,{59.989982 })= 1 (0x1)
gettimeofday({1234648102.286493 },0x0) = 0 (0x0)
read(23,\0\0\0r,4) = 4 (0x4)
read(23,\M^?SMB2\0\0\0\0\^X\a\M-H\0\0\0...,114) = 114 (0x72)
geteuid(0x3e8,0x3e8,0x2,0x800adf750,0x2,0x800adf750) = 0 (0x0)
getegid(0x3e8,0x3e8,0x2,0x801eadb8c,0xff006cf16a50,0x7fffd138) = 0
(0x0)
__sysctl(0x7fffd0a0,0x2,0x7fffd0bc,0x7fffd0b0,0x0,0x0) = 0 (0x0)
0.000u 0.001s 2:36.56 0.0%0+0k 0+0io 0pf+0w
# sockstat | grep 445
glz smbd 8307 23 tcp4 10.255.253.1:445 10.255.253.2:57438
root smbd 76917 19 tcp4 127.0.0.1:445 *:*
root smbd 76917 20 tcp4 10.255.253.1:445 *:*
# ps -awxl | grep 8307
1000 8307 8556 0 44 0 34672 7984 select IX??0:04.57
/usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf
0 8556 3273 0 8 0 4600 1204 wait I+p00:00.00 truss
-p 8307
# sockstat | grep 445
root smbd 8307 23 tcp4 10.255.253.1:445 10.255.253.2:57438
root smbd 76917 19 tcp4 127.0.0.1:445 *:*
root smbd 76917 20 tcp4 10.255.253.1:445 *:*
# ps -awxl | grep 8307
0 8307 8556 0 44 0 34672 7984 select SX??0:04.57
/usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf
0 8556 3273 0 8 0 4600 1204 wait I+p00:00.00 truss
-p 8307
I can recreate this at any time and the condition can be cleared in two
ways:
- killing the offending smbd process and the PC reconnects just fine
- attach and detach truss, as can bee seen in the logs below taken after
the truss session above:
# sockstat | grep 445
glz smbd 8307 23 tcp4 10.255.253.1:445 10.255.253.2:57438
root smbd 76917 19 tcp4 127.0.0.1:445 *:*
root smbd 76917 20 tcp4 10.255.253.1:445 *:*
# ps -awxl | grep 8307
1000 8307 76917 0 44 0 34672 7984 select S ??0:04.58
/usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf
/glz
... the future isMobile
Goran Lowkrantz goran.lowkra...@ismobile.com
System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden
Phone: +46(0)920-75559
Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82
http://www.ismobile.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: Upgrade from 32-bit to AMD-64?
Hi, When have done this, MySQL is OK but Berkley and PostgreSQL need dump/restore. /glz --On February 13, 2009 2:53:13 -0500 Mike Andrews mandr...@bit0.com wrote: Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karl Denninger wrote: [...] I guess I need to schedule the 2-3 hours of downtime. the reason for this, by the way, is that I have a dbms app on there that is getting too RAM hungry for its own good (its a Quadcore CPU) and I'm up against the RAM limit for 32-bit code. The board will support more but 32-bit code won't; ergo, the only way to get beyond this is to go to 64-bit. Oh wait! One thing you wanted to know is that, some database *can* have different on-disk format for 32-bit and 64-bit binaries. Be sure to have a dump handy. Last time I hit this on a MySQL upgrade between two servers, and I end up using its replication functionality. The operation took longer time than I expected at the beginning. For what it's worth, I did an in-place source upgrade on our MySQL server (for the same lack-of-memory reason) and didn't have any on-disk format problems. In fact later on when troubleshooting data corruption problems that turned out to be bad hardware, I switched between 32-bit and 64-bit mysqld binaries without rebooting or dumping/reimporting the database. BUT... there was no replication involved. It wouldn't surprise me if the binlog or relay logs were in an architecture specific format. InnoDB and MyISAM tables don't appear to be. This was over a year ago though, so test on a scratch box first and you may save yourself a bit of downtime. The upgrade is a pain, and does have a lot of potential foot-shooting, and you have to immediately recompile ALL of your installed ports (and anything else not built from ports) to avoid mixing 32-bit and 64-bit shared libraries... and that rebuilding ports time is where most of your downtime comes from if it's a production box. If you're feeling lucky, the procedure's in the list archives somewhere and the super-short version is you turn your swap partition into a temporary amd64 root filesystem, installworld/kernel into that, boot into that, then mount and installworld/kernel on top of the old i386 root filesystem from there, then boot into it and recompile all your ports (after reclaiming your swap partition for swap). Or, the way I did it last time was to boot into a PXE diskless FreeBSD/amd64 install and use that to mount/install over the i386 stuff. Definitely practice on a scratch system first. :) -- Mike Andrews Server Monkey Fark, Inc mandr...@fark.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 ... the future isMobile Goran Lowkrantz goran.lowkra...@ismobile.com System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.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
Regression in vr - not receiveing multicast
Hi, in July, vr had this problem and was fixed: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125010 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125024 but now it's back again! On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without any problems. Let me know what I can do to help fix this. /glz ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Regression in vr - not receiveing multicast
Hi, in July, vr had this problem and was fixed: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125010 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125024 but now it's back again! On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without any problems. Let me know what I can do to help fix this. /glz ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... --- There is hopeful symbolism in the fact that flags do not wave in a vacuum. -- Arthur C. Clarke ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression in vr - not receiveing multicast
--On December 9, 2008 20:47:23 +0900 Pyun YongHyeon [EMAIL PROTECTED] wrote: On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: Hi, in July, vr had this problem and was fixed: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125010 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125024 but now it's back again! There was just one bug fix since then and I guess the fix is not related with your issue. On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without anyproblems. There is fundamental differences between em(4) and vr(4). The vr(4) for VT6105M takes advantage of perfect multicast filtering feature which is not present on all em(4) interface. Perfect multicast filtering can reduce unwanted multicast traffics such that it could save a lot of CPU cycles. The downside is that vr(4) cannot accept multicast frames for a multicast group without joining the multicast group first. For multicast routing purpose I guess 'options MROUTING' kernel option should be enabled to accept all multicast frames. Does your kernel have that option? No it has not. I will create such a beast and return with stories. /glz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression in vr - not receiveing multicast
--On December 9, 2008 12:53:05 +0100 Goran Lowkrantz [EMAIL PROTECTED] wrote: --On December 9, 2008 20:47:23 +0900 Pyun YongHyeon [EMAIL PROTECTED] wrote: On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: Hi, in July, vr had this problem and was fixed: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125010 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125024 but now it's back again! There was just one bug fix since then and I guess the fix is not related with your issue. On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without anyproblems. There is fundamental differences between em(4) and vr(4). The vr(4) for VT6105M takes advantage of perfect multicast filtering feature which is not present on all em(4) interface. Perfect multicast filtering can reduce unwanted multicast traffics such that it could save a lot of CPU cycles. The downside is that vr(4) cannot accept multicast frames for a multicast group without joining the multicast group first. For multicast routing purpose I guess 'options MROUTING' kernel option should be enabled to accept all multicast frames. Does your kernel have that option? No it has not. I will create such a beast and return with stories. I have tried with 'options MROUTING' and it didn't work. Did I miss something? Do I have to install and run mrouted also? It seems like maybe the first two packages are accepted after registration as I don't lose the routes until after about 6 min uptime. But to get further updates, I need the interfaces in promisc. So, next step? /glz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression in vr - not receiveing multicast
--On December 10, 2008 16:19:33 +0900 Pyun YongHyeon [EMAIL PROTECTED] wrote: On Wed, Dec 10, 2008 at 08:06:16AM +0100, Goran Lowkrantz wrote: --On December 9, 2008 12:53:05 +0100 Goran Lowkrantz [EMAIL PROTECTED] wrote: --On December 9, 2008 20:47:23 +0900 Pyun YongHyeon [EMAIL PROTECTED] wrote: On Tue, Dec 09, 2008 at 10:40:17AM +0100, Goran Lowkrantz wrote: Hi, in July, vr had this problem and was fixed: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125010 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=125024 but now it's back again! There was just one bug fix since then and I guess the fix is not related with your issue. On a system with the following: 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Oct 16 12:31:04 UTC 2008 I have to set all vr interfaces in promisc to get routing info. Using Quagga # pkg_info -Ix uagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software on an inner network using RIPv2 # ifmcstat -i vr0 vr0: inet xxx.xxx.xxx.xxx group 224.0.0.9 igmpv2 mcast-macaddr 01:00:5e:00:00:09 refcnt 1 group 224.0.0.1 mcast-macaddr 01:00:5e:00:00:01 refcnt 1 On the same box, we have some em devices also and they work without anyproblems. There is fundamental differences between em(4) and vr(4). The vr(4) for VT6105M takes advantage of perfect multicast filtering feature which is not present on all em(4) interface. Perfect multicast filtering can reduce unwanted multicast traffics such that it could save a lot of CPU cycles. The downside is that vr(4) cannot accept multicast frames for a multicast group without joining the multicast group first. For multicast routing purpose I guess 'options MROUTING' kernel option should be enabled to accept all multicast frames. Does your kernel have that option? No it has not. I will create such a beast and return with stories. I have tried with 'options MROUTING' and it didn't work. Did I miss something? Do I have to install and run mrouted also? It seems like maybe the first two packages are accepted after registrationas I don't lose the routes until after about 6 min uptime. But to getfurther updates, I need the interfaces in promisc. So, next step? Can you see ALLMULTI flag from the output of ifconfig vr0? No - # ifconfig vr0 vr0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=284bRXCSUM,TXCSUM,VLAN_MTU,POLLING,WOL_UCAST,WOL_MAGIC ether 00:00:24:c8:e0:9c inet xxx.xxx.xxx.xxx netmask 0xfff8 broadcast xxx.xxx.xxx.yyy media: Ethernet autoselect (100baseTX full-duplex) status: active /glz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Request for testing: ata(4) MFC
It seems the attachment got eaten somewhere. Trying again with correct content type. /glz --On October 16, 2008 12:20:27 +0200 Goran Lowkrantz [EMAIL PROTECTED] wrote: Ok, I was not sure if this was a No news is good news request. Attached are the lspci:s of the MB and devices I have had the pleasure of testing. I have found nothing bad on these once but please remember that I had to hack the nVidia MCP67-A1 to have it accepted as a SATA and AHCI controller. All controllers have had large copy in/out, backups at file-system level via dump/zfs snapshot and tar and all have had bonny++ tests done. On AHCI controllers, I have at least remove and re-inserted one disk of a zpool. Cheers, Göran Best regards, Göran L --On October 16, 2008 13:15:46 +0400 Andrey V. Elsukov [EMAIL PROTECTED] wrote: Jeremy Chadwick wrote: - Could someone provide an explanation of the 48-bit LBA addressing changes (see lines 988-1003 in the patch)? I'd like to know what they do, and if further QA/testing is needed with this. I think this is for debug purposes. - Can we please see about adding the FreeNAS project's ata timeout sysctls? I see lots of delays/sleeps in numerous pieces of code that pertain to soft or hard resets of AHCI controllers, and I often worry about the implications of hard-coded timeouts. http://freenas.svn.sourceforge.net/viewvc/freenas/trunk/build/kernel-p atches/ata/files/patch-ata.diff?view=markup As i remember changes in FreeNAS don't change timeouts for resets. In any case, these changes can not be in 7.1-RELEASE. My patch targeted to move changes from CURRENT to 7.1. But it seems there are too few testers and patch can not be commited. -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ...=== MB: Intel D915GAV 00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corporation Unknown device [8086:4156] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 255 Region 0: I/O ports at unassigned Region 1: I/O ports at unassigned Region 2: I/O ports at unassigned Region 3: I/O ports at unassigned Region 4: I/O ports at ffa0 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Intel Corporation Unknown device [8086:4156] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 19 Region 0: I/O ports at e800 Region 1: I/O ports at e400 Region 2: I/O ports at e000 Region 3: I/O ports at dc00 Region 4: I/O ports at d800 Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 06:00.0 SCSI storage controller [0100]: Adaptec AHA-2940U/UW/D / AIC-7881U [9004:8178] (rev 01) Subsystem: Adaptec AHA-2940UW SCSI Host Adapter [9004:7881] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2000ns min, 2000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 21 Region 0: I/O ports at b800 Region 1: Memory at ff59 (32-bit, non-prefetchable) [disabled] Expansion ROM at ff58 [disabled] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1
Re: Request for testing: ata(4) MFC
--On Saturday, October 04, 2008 19:38 +0400 Andrey V. Elsukov
[EMAIL PROTECTED] wrote:
Hi, All.
I prepared patch to make MFC of ata(4) driver into RELENG_7
before 7.1-RELEASE. Depending on results of the testing patch
will be commited or not (if some regressions will be detected).
So if you want or just can test it, please try and report here.
Installed and tested with no ill effects on an ASUS M2N-VM DVI board. Still
need to manually apply the attached patch, picked up on the list a while
ago, to have the built-in SATA controller detected and recognized as AHCI
capable.
Cheers,
Goran
Attachments:
lspci output of controller under test.
original patch for controller.
updated patch against tested patchset.
---
There is hopeful symbolism in the fact that flags do not wave in a vacuum.
-- Arthur C. Clarke00:09.0 SATA controller [0106]: nVidia Corporation MCP67 AHCI Controller
[10de:0554] (rev a2) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82b3]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort-
MAbort- SERR- PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at c480
Region 1: I/O ports at c400
Region 2: I/O ports at c080
Region 3: I/O ports at c000
Region 4: I/O ports at bc00
Region 5: Memory at f9ef6000 (32-bit, non-prefetchable)
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [8c] SATA HBA ?
Index: src/sys/dev/ata/ata-chipset.c
===
RCS file: /ncvs/src/sys/dev/ata/ata-chipset.c,v
retrieving revision 1.225
diff -u -p -r1.225 ata-chipset.c
--- src/sys/dev/ata/ata-chipset.c 15 Aug 2008 10:55:11 - 1.225
+++ src/sys/dev/ata/ata-chipset.c 23 Sep 2008 05:06:28 -
@@ -3372,7 +3372,9 @@ ata_nvidia_ident(device_t dev)
{ ATA_NFORCE_MCP61_S3, 0, 0, NV4|NVQ, ATA_SA300, nForce MCP61 },
{ ATA_NFORCE_MCP65,0, AMDNVIDIA, NVIDIA, ATA_UDMA6, nForce MCP65 },
{ ATA_NFORCE_MCP67,0, AMDNVIDIA, NVIDIA, ATA_UDMA6, nForce MCP67 },
+ { ATA_NFORCE_MCP67_A1, 0, 0, NVAHCI, ATA_SA300, nForce MCP67 },
{ ATA_NFORCE_MCP73,0, AMDNVIDIA, NVIDIA, ATA_UDMA6, nForce MCP73 },
+ { ATA_NFORCE_MCP73_A1, 0, 0, NVAHCI, ATA_SA300, nForce MCP73 },
{ ATA_NFORCE_MCP77,0, AMDNVIDIA, NVIDIA, ATA_UDMA6, nForce MCP77 },
{ 0, 0, 0, 0, 0, 0}} ;
@@ -3380,7 +3382,12 @@ ata_nvidia_ident(device_t dev)
return ENXIO;
ata_set_desc(dev);
-ctlr-chipinit = ata_nvidia_chipinit;
+
+if (ctlr-chip-cfg2 == NVAHCI)
+ ctlr-chipinit = ata_ahci_chipinit;
+else
+ ctlr-chipinit = ata_nvidia_chipinit;
+
return 0;
}
Index: src/sys/dev/ata/ata-pci.h
===
RCS file: /ncvs/src/sys/dev/ata/ata-pci.h,v
retrieving revision 1.89
diff -u -p -r1.89 ata-pci.h
--- src/sys/dev/ata/ata-pci.h 10 Jul 2008 21:36:53 - 1.89
+++ src/sys/dev/ata/ata-pci.h 23 Sep 2008 05:06:28 -
@@ -243,8 +243,10 @@ struct ata_connect_task {
#define ATA_NFORCE_MCP61_S2 0x03f610de
#define ATA_NFORCE_MCP61_S3 0x03f710de
#define ATA_NFORCE_MCP650x044810de
+#define ATA_NFORCE_MCP67_A1 0x055010de
#define ATA_NFORCE_MCP670x056010de
#define ATA_NFORCE_MCP730x056c10de
+#define ATA_NFORCE_MCP73_A1 0x07f810de
#define ATA_NFORCE_MCP770x075910de
#define ATA_PROMISE_ID 0x105a
@@ -450,6 +452,7 @@ struct ata_connect_task {
#define NVIDIA 0x0004
#define NV4 0x0010
#define NVQ 0x0020
+#define NVAHCI 0x0040
#define VIACLK 0x0100
#define VIABUG 0x0200
#define VIABAR 0x0400
ata_nvidia_ahci-20081004.diff
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unsupported NVIDIA SATA controller
Hi, FYI, I have added your patch on an MCP67 of an ASUS M2N-VM DVI motherboard and it's been up for about a day, dmesg looks OK and it survived the backup of its managed disks. So, unless you hear more from me, it worked. FreeBSD midgard.glz.hidden-powers.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Tue Sep 23 19:57:47 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MIDGARD amd64 00:09.0 IDE interface [0101]: nVidia Corporation MCP67 AHCI Controller [10de:0550] (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:82b3] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 22 Region 0: I/O ports at c480 Region 1: I/O ports at c400 Region 2: I/O ports at c080 Region 3: I/O ports at c000 Region 4: I/O ports at bc00 Region 5: Memory at dfcfa000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [8c] SATA HBA ? Cheers, Goran --On Tuesday, September 23, 2008 09:11 +0400 Andrey V. Elsukov [EMAIL PROTECTED] wrote: Joseph Olatt wrote: [EMAIL PROTECTED]:0:14:0: class=0x010485 card=0x01371025 chip=0x07f810de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = mass storage subclass = RAID Do you still have this problem? It seems that your controller is AHCI-capable. I can make a patch if is it needed. Yes, I'm still have the above problem. And, yes, the controller appears to be ACHI-capable (at least according to Ubuntu. see [1]) I would greatly appreciate a patch if you can provide one. regards, joseph [1]: http://www.eskimo.com/~joji/nvidia_sata/ Hi, Joseph. Try attached patch. -- WBR, Andrey V. Elsukov ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unusually large directory - 2.0 peta bytes (SOLVED)
The initial fsck didn't clear it but using fsdb to remove the entry from the parent directory, an fsck -y /usr in singleuser cleard the problem. Thanks to Joseph Koshy for directing me to fsdb. Cheers, Göran --On Saturday, June 14, 2008 07:17 +0200 Goran Lowkrantz [EMAIL PROTECTED] wrote: While preparing to upgrade to latest stable, I ran some scripts to verify that the target was OK and found something that I think I need to fix but have no clue to how. This is the essence of what I found: # ls /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* autosplit.ix # ls -la /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* ls: : No such file or directory ls: autosplit.ix: No such file or directory total 8 drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO 163 5229427 drwxr-xr-x 2 root wheel 20894350 2251799813685760 Jun 14 07:07:43 2008 Jun 14 04:06:44 2008 Jun 14 04:06:44 2008 Mar 29 10:33:10 2008 4096 4 0 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO # stat # /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix stat: /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix: stat: No such file or directory # od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more 000s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t 040P e r l I O . s o \0 217 300 u 313 O \0 060 324 001 \b \t P e r l I O . b s \0 217 300 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0001020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0002000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0002020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0003000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0003020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0004000v 313 O \0 \f \0 004 001 . \0 \0 \0 335 312 O \0 0004020 \f \0 004 002 . . \0 \0 w 313 O \0 350 001 \b \f 0004040a u t o s p l i t . i x \0 231 - 351 0004060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0005000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0005020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0006000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0006020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0007000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0007020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 001 177 E L F 001 001 001 \t \0 \0 \0 \0 \0 \0 \0 \0 0010020 003 \0 003 \0 001 \0 \0 \0 240 \t \0 \0 4 \0 \0 \0 0010040 330 025 \0 \0 \0 \0 \0 \0 4 \0 \0 003 \0 ( \0 This does not look like a directory, it looks like a shared library, PerlIO.so, that somehow got the directory bit set. First, am I correct in my analysis? Second, how do I remove the directory bit so I can delete the file? Host info, dmesg.boot attached: # uname -a FreeBSD balder.glz.hidden-powers.com 6.3-STABLE FreeBSD 6.3-STABLE #1: Thu Feb 28 02:14:05 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BALDER i386 Cheers, Göran ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Unusually large directory - 2.0 peta bytes
While preparing to upgrade to latest stable, I ran some scripts to verify that the target was OK and found something that I think I need to fix but have no clue to how. This is the essence of what I found: # ls /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* autosplit.ix # ls -la /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* ls: : No such file or directory ls: autosplit.ix: No such file or directory total 8 drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO 163 5229427 drwxr-xr-x 2 root wheel 20894350 2251799813685760 Jun 14 07:07:43 2008 Jun 14 04:06:44 2008 Jun 14 04:06:44 2008 Mar 29 10:33:10 2008 4096 4 0 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix stat: /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix: stat: No such file or directory # od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more 000s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t 040P e r l I O . s o \0 217 300 u 313 O \0 060 324 001 \b \t P e r l I O . b s \0 217 300 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0001020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0002000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0002020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0003000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0003020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0004000v 313 O \0 \f \0 004 001 . \0 \0 \0 335 312 O \0 0004020 \f \0 004 002 . . \0 \0 w 313 O \0 350 001 \b \f 0004040a u t o s p l i t . i x \0 231 - 351 0004060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0005000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0005020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0006000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0006020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0007000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0007020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 001 177 E L F 001 001 001 \t \0 \0 \0 \0 \0 \0 \0 \0 0010020 003 \0 003 \0 001 \0 \0 \0 240 \t \0 \0 4 \0 \0 \0 0010040 330 025 \0 \0 \0 \0 \0 \0 4 \0 \0 003 \0 ( \0 This does not look like a directory, it looks like a shared library, PerlIO.so, that somehow got the directory bit set. First, am I correct in my analysis? Second, how do I remove the directory bit so I can delete the file? Host info, dmesg.boot attached: # uname -a FreeBSD balder.glz.hidden-powers.com 6.3-STABLE FreeBSD 6.3-STABLE #1: Thu Feb 28 02:14:05 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BALDER i386 Cheers, Göran ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em 6.6.6 - watchdog timeout
Hi Jack, --On Thursday, November 01, 2007 13:36 -0700 Jack Vogel [EMAIL PROTECTED] wrote: I should also note that this only applies to PCI-E NICs, 82571 and later. Jack Have tested - enable MSI with the original 6.6.6 driver - the new driver files you sent to -stable with and without MSI enabled In all cases I can run all tests and programs that previous gave watchdog problems without any problems. Thanks! /glz ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em watchdog problem
Hi Jack, In my case, yes but only under higher loads, specifically when Amanda started receive the backup data. At lower loads, like the check or sizing, no problems. Best regards, Göran L --On Tuesday, October 30, 2007 10:16 -0700 Jack Vogel [EMAIL PROTECTED] wrote: This morning I had an idea about what the source of the watchdog problem is. Also, we have repro'd at least one type of watchdog inhouse. One question, is this problem only happening for those running STABLE with the 6.6.6 merged driver? We found the problem does not seem to happen on 7.0. Right now my suspicion is that the FAST irq handling is again causing a problem. I am experimenting with variations to the code today to be sure whats going on, and hopefully fixing it. Cheers, Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MFC requests for 6.3
[EMAIL PROTECTED] wrote: On Sun, 28 Oct 2007, Brett Glass wrote: I would like to request that some useful work on networking be MFCed from -CURRENT to -STABLE in time for the release of FreeBSD 6.3. The thing that's worried me, following only [EMAIL PROTECTED] traffic, were the reports about the new em driver (6.6.6?) causing hangs and other problems with people who have been updating RELENG_6 - have those who had those problems seen their issues resolved? I've got remote boxes using em that I can't risk making inaccessible and can't test locally. All my problems with watchdog timeouts and em 6.6.6 occurred when em shared interrupt with USB but I don't know if it's MB, em or usb that's the problem. Removing USB from the kernel or switching to polling and the driver works just fine. The fact that one of my test machines didn't have any problems was because it had no USB in it's kernel. I had removed USB as I had problems with watchdog timeouts with the bge driver when I first upgraded to the D915GAV MB ages ago. The bge also shared interrupt with USB. /glz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MFC requests for 6.3
[EMAIL PROTECTED] wrote: On Mon, 29 Oct 2007, Goran Lowkrantz wrote: On Sun, 28 Oct 2007, Brett Glass wrote: I would like to request that some useful work on networking be MFCed from -CURRENT to -STABLE in time for the release of FreeBSD 6.3. The thing that's worried me, following only [EMAIL PROTECTED] traffic, were the reports about the new em driver (6.6.6?) causing hangs and other problems with people who have been updating RELENG_6 - have those who had those problems seen their issues resolved? I've got remote boxes using em that I can't risk making inaccessible and can't test locally. All my problems with watchdog timeouts and em 6.6.6 occurred when em shared interrupt with USB but I don't know if it's MB, em or usb that's the problem. Removing USB from the kernel or switching to polling and the driver works just fine. The fact that one of my test machines didn't have any problems was because it had no USB in it's kernel. I had removed USB as I had problems with watchdog timeouts with the bge driver when I first upgraded to the D915GAV MB ages ago. The bge also shared interrupt with USB. Thanks. /var/run/dmesg.boot says my em0 and em1 don't share an IRQ with USB or anyone else, so sounds like I'm in the clear, yay. But it still seems like something the vendor (Intel?) should be looking into before a another release on RELENG_6 is cut - even if USB is the culprit, it sounded like the problems started for em users when the driver was updated from 6.2.9 to 6.6.6. Yes, that's correct. But then 6.6.6 is faster, so it may be that we have a timing problem in any driver when they share interrupt with a Gigant locked driver. Isn't there a new non-Gigant USB driver that is waiting for testers? I have two workstations with em that needs usb that I could test the combination on. /glz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em 6.6.6 - watchdog timeout
[EMAIL PROTECTED] wrote: Hi, snip When running netstat between servers balder and midgard, server balder get watchdog timeouts and resets the connection for a few seconds. Oct 19 13:12:47 balder kernel: em0: watchdog timeout -- resetting s/netstat/netperf/ ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, iaMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
em 6.6.6 - watchdog timeout
- - lo0 16384 10.255.253.10 ca.glz.hidden-pow0 -0 - - lo0 16384 10.255.253.11 test 0 -0 - - lo0 16384 10.255.253.13 secure 0 -0 - - lo0 16384 10.255.253.18 rscds.hidden-powe7 -0 - - midgard# lspci 00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 04) 00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04) 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 SCSI storage controller: Triones Technologies, Inc. Unknown device 2310 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) 06:01.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 01) 06:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) When running netstat between servers balder and midgard, server balder get watchdog timeouts and resets the connection for a few seconds. Oct 19 13:12:47 balder kernel: em0: watchdog timeout -- resetting Oct 19 13:12:47 balder kernel: em0: link state changed to DOWN Oct 19 13:12:51 balder kernel: em0: link state changed to UP I have switched the cable between the two servers but get exactly the same problem. The switch is a Netgear GS108T with the latest firmware. The resp. dmesg.boot are attached. Please let me know if there is any other information I can supply to clear this. Best regards, Göran L ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, iaMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Luleå, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ... balder.dmesg.boot Description: Binary data midgard.dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em 6.6.6 - watchdog timeout
[EMAIL PROTECTED] wrote: Hi, After the update of em to 6.6.6 last, I experience watchdog timeouts on a server running 6-STABLE. I have two identical servers with Intel D915GAV boards. Both have Intel PRO/1000 PCI-Express network cards. Server balder: em0: Intel(R) PRO/1000 Network Connection Version - 6.6.6 port 0xac00-0xac1f mem 0xff60-0xff61,0xff62-0xff63 irq 16 at device 0.0 on pci5 em0: Ethernet address: 00:1b:21:00:48:c4 em0: [FAST] # vmstat -i interrupt total rate irq1: atkbd0 3 0 irq4: sio0 2 0 irq6: fdc012 0 irq14: ata0 68 0 irq16: em0 uhci3 219828879450 irq19: uhci1++ 4287947 8 irq22: ahc0232717293476 irq23: uhci0 ehci0 1 0 cpu0: timer976552804 2000 Total 1433387009 2935 # netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll em01500 Link#1 00:1b:21:00:48:c4 209880531 773 20622 84 0 em01500 10.255.253/24 balder215210996 - 212337968 - - plip0 1500 Link#2 0 00 0 0 lo0 16384 Link#312040055 0 12055326 0 0 lo0 16384 fe80:3::1 fe80:3::10 -0 - - lo0 16384 localhost ::1 6 -6 - - lo0 16384 your-net localhost 6249979 - 6249980 - - 00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 04) 00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04) 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 05:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) 06:01.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 01) Server midgard: em0: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port 0xac00-0xac1f mem 0xff50-0xff51,0xff52-0xff53 irq 16 at device 0.0 on pci5 em0: Ethernet address: 00:15:17:0e:05:f7 [EMAIL PROTECTED] vmstat -i interrupt total rate irq1: atkbd0 11 0 irq4: sio0 2142746 0 irq6: fdc014 0 irq14: ata0 252 0 irq16: em0+40101164 irq19: atapci1+ 7932757 1 irq22: ahc0 87074425 21 cpu0: timer 3807810138937 Total 4571600444 1125 [EMAIL PROTECTED] netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll em01500 Link#1 00:15:17:0e:05:f7 343771280 0 474609731 0 0 em01500 10.255.253/24 midgard 347467842 - 478700485 - - plip0 1500 Link#2 0 00 0 0 lo0 16384 Link#316821054 0 16947668 0 0 lo0 16384 fe80:3::1 fe80:3::10 -0 - - lo0 16384 localhost ::1 2610 - 2610 - - lo0 16384 your-net localhost 12616879 - 12616879 - - lo0 16384 10.255.253.12 appsrv1 0 -0 - - lo0 16384 10.255.253.10
Re: iwi, hidden SSID and wpa_supplicant problem
Hi, Reporting back after a few days with the patch. The connect and switching between accesspoints work but there are still a few down/up events, about once every two hours but that may have somthing to do with the dhcp cleint. At the moment, the number of lease renewals match the number of link down/up events. I leave this to the clever folks. When running from the em interface, I do not see any down/up at all and thet net uses the same DCHP server etc. iwi0: link state changed to DOWN iwi0: link state changed to UP iwi0: link state changed to DOWN iwi0: link state changed to UP iwi0: link state changed to DOWN iwi0: link state changed to UP iwi0: link state changed to DOWN iwi0: link state changed to UP iwi0: link state changed to DOWN iwi0: scan stuck iwi0: link state changed to UP /glz --On Tuesday, October 10, 2006 05:04:46 +0200 Max Laier [EMAIL PROTECTED] wrote: On Monday 09 October 2006 20:26, Max Laier wrote: On Monday 09 October 2006 19:53, Andrew N. Below wrote: Hi. [..] You can try using ap_scan=2 or whatever it is in the wpa_supplicant.conf file. This causes wpa_supplicant to use directed broadcasts msgs to each ap listed in the file. In my case setting ap_scan to 2 doesn't help. BTW, I got successfull connection some time ago when I start to use /etc/rc.d/netif start iwi0 instead of manual running of wpa_supplicant: defanbook# ifconfig iwi0 iwi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 213.189.198.75 netmask 0xfff0 broadcast 213.189.198.79 ether 00:12:f0:3d:cd:58 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid ZENON-RADIO channel 11 bssid 00:07:0e:b8:d8:ee authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpowmax 100 bmiss 10 protmode CTS roaming MANUAL bintval 100 I wrote bssid value to /etc/wpa_supplicant.conf and run /etc/rc.d/netif. Then I drop connection (netif stop iwi0) and tried to start it again. I got associated state in 5-6 minutes. In rc.conf I have: ifconfig_iwi0=ssid MY-SSID channel 11 WPA How can I get -dd output from wpa_supplicant started with netif? It could be interesting. No idea, but a bit more stress testing did reveal a similar problem here. After I associated with the AP w/ hidden SSID I changed the channel via webinterface. The disconnect resulted in the exact problem you were having. Only stopping and restarting wpa_supplicant fixed the issue and I got associated on the new channel. Not sure what happens there yet, but something seems to get stuck in an undefined state. Could you try the attached - untested - patch? It seems - from looking at the linux driver - that we have to remind the firmware of the ESSID before doing a directed scan. That explains why it would sometimes work (whenever we are coming straight from iwi_config) and sometimes not. Let me know if that improves things for you. Thanks. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News -- ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile, Aurorum 2, S-977 75 Lule￥, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi, hidden SSID and wpa_supplicant problem
entering state INITIALIZE Oct 09 18:24:41.271597: EAP: EAP entering state DISABLED Oct 09 18:24:41.271636: EAPOL: External notification - portEnabled=0 Oct 09 18:24:41.271657: EAPOL: External notification - portValid=0 Oct 09 18:24:41.271918: Own MAC address: 00:12:f0:3d:cd:58 Oct 09 18:24:41.271929: wpa_driver_bsd_set_wpa: enabled=1 Oct 09 18:24:41.271936: wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1 Oct 09 18:24:41.271946: wpa_driver_bsd_del_key: keyidx=0 Oct 09 18:24:41.271954: wpa_driver_bsd_del_key: keyidx=1 Oct 09 18:24:41.271962: wpa_driver_bsd_del_key: keyidx=2 Oct 09 18:24:41.271969: wpa_driver_bsd_del_key: keyidx=3 Oct 09 18:24:41.271977: wpa_driver_bsd_set_countermeasures: enabled=0 Oct 09 18:24:41.271984: wpa_driver_bsd_set_drop_unencrypted: enabled=1 Oct 09 18:24:41.271994: Setting scan request: 0 sec 10 usec Oct 09 18:24:41.272118: Added interface iwi0 Oct 09 18:24:41.372226: State: DISCONNECTED - SCANNING Oct 09 18:24:41.372235: Starting AP scan (specific SSID) Oct 09 18:24:41.372242: Scan SSID - hexdump_ascii(len=11): [MY-SSID] Oct 09 18:24:43.021948: Received 0 bytes of scan results (4 BSSes) Oct 09 18:24:43.021982: Scan results: 4 Oct 09 18:24:43.021992: Selecting BSS from priority group 0 Oct 09 18:24:43.021998: 0: 00:07:0e:b8:d8:ee ssid='' wpa_ie_len=26 rsn_ie_len=0 caps=0x31 Oct 09 18:24:43.022008:skip - SSID mismatch Oct 09 18:24:43.022014: 1: 02:3f:2d:21:0e:c2 ssid='ANY' wpa_ie_len=0 rsn_ie_len=0 caps=0x2 Oct 09 18:24:43.022023:skip - no WPA/RSN IE Oct 09 18:24:43.022029: 2: 00:60:b3:d4:0d:76 ssid='ADSL_Wireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x61 Oct 09 18:24:43.022038:skip - no WPA/RSN IE Oct 09 18:24:43.022044: 3: 00:14:6c:55:24:4a ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 Oct 09 18:24:43.022052:skip - no WPA/RSN IE Oct 09 18:24:43.022058: No suitable AP found. Oct 09 18:24:43.022066: Setting scan request: 5 sec 0 usec Oct 09 18:24:48.023226: Starting AP scan (broadcast SSID) Oct 09 18:24:49.501060: Received 0 bytes of scan results (2 BSSes) Oct 09 18:24:49.501070: Scan results: 2 Oct 09 18:24:49.501077: Selecting BSS from priority group 0 Oct 09 18:24:49.501083: 0: 00:07:0e:b8:d8:ee ssid='' wpa_ie_len=26 rsn_ie_len=0 caps=0x31 Oct 09 18:24:49.501092:skip - SSID mismatch Oct 09 18:24:49.501098: 1: 00:14:6c:55:24:4a ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 Oct 09 18:24:49.501106:skip - no WPA/RSN IE Oct 09 18:24:49.501112: No suitable AP found. Oct 09 18:24:49.501118: Setting scan request: 5 sec 0 usec ^COct 09 18:24:52.082178: CTRL-EVENT-TERMINATING - signal 2 received Oct 09 18:24:52.082190: Removing interface iwi0 Oct 09 18:24:52.082197: State: SCANNING - DISCONNECTED Oct 09 18:24:52.082204: No keys have been configured - skip key clearing Oct 09 18:24:52.082210: EAPOL: External notification - portEnabled=0 Oct 09 18:24:52.082282: EAPOL: External notification - portValid=0 Oct 09 18:24:52.082315: wpa_driver_bsd_set_wpa: enabled=0 Oct 09 18:24:52.082321: wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 Oct 09 18:24:52.082333: wpa_driver_bsd_set_drop_unencrypted: enabled=0 Oct 09 18:24:52.082341: wpa_driver_bsd_set_countermeasures: enabled=0 Oct 09 18:24:52.082348: No keys have been configured - skip key clearing Oct 09 18:24:52.082463: wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 Oct 09 18:24:52.082851: Cancelling scan request As we can see, it just repeats specific and broadcast SSID scan in cycle, but always says No suitable AP found and SSID mismatch. While this process is running I can see more and more Number of frames with a bad CRC receive with the iwicontrol utility. On another FreeBSD box with 6.1-release and same version of wpa_supplicant, but with another USB wireless device (ural) all works fine. Wireless connection in winxp on this laptop works fine too. Any ideas? -- Andrew N. Below Zenon N.S.P. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile, Aurorum 2, S-977 75 Lule￥, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... dmesg.boot Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi, hidden SSID and wpa_supplicant problem
Have attacehd my output from a connect attampt agains a hidden SSID where I
had BSSID in the config. And it didn't connect over the time I looked.
Here is the scan for the area:
SSIDBSSID CHAN RATE S:N INT CAPS
OPERAX 00:0f:cb:9f:de:ee1 54M 37:0 100 ES
0x0000:0f:b5:72:a6:563 54M 52:0 100 EPS WPA
0x0000:09:5b:b8:c4:4d3 54M 61:0 100 EP WPA
OPERAX 00:15:e9:60:e8:4c6 54M 53:0 100 ES
jonsson200:05:5d:f2:50:2a6 11M 78:0 100 EcP
and the wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=LCLSSID
key_mgmt=WPA-PSK
scan_ssid=1
psk=iM03x123
bssid=00:0f:b5:72:a6:56
}
/glz
--On Monday, October 09, 2006 17:12:48 +0200 Goran Lowkrantz
[EMAIL PROTECTED] wrote:
I have the same problem with an IBM R50 laptop and the iwi driver. From
dmesg
iwi0: Intel(R) PRO/Wireless 2915ABG mem 0xc0214000-0xc0214fff irq 9 at
device 2.0 on pci2
I have never been able to connect to a hidden SSID without giving the
BSSID. If I give the BSSID I can get connection but it takes a long time
and is not reliable as the driver looses connection and failes to
re-connect after a while.
When connected to an AP that broadcasts the SSID I still lose connection
after a couple of hours and have to stop and restart the connection.
Here is the sequiece from the console:
iwi0: link state changed to DOWN
iwi0: scan stuck
iwi0: link state changed to UP
iwi0: link state changed to DOWN
iwi0: link state changed to UP
iwi0: firmware error
iwi0: link state changed to DOWN
iwi0: scan stuck
iwi0: link state changed to UP
iwi0: link state changed to DOWN
iwi0: link state changed to UP
iwi0: firmware error
iwi0: link state changed to DOWN
iwi0: scan stuck
iwi0: could not allocate firmware DMA memory
# /etc/rc.d/netif stop iwi0
Stopping network:Stopping wpa_supplicant.
Waiting for PIDS: 324.
iwi0.
# /etc/rc.d/netif start iwi0
Starting wpa_supplicant.
DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 7
iwi0: link state changed to UP
DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 19
DHCPOFFER from 10.255.253.253
DHCPREQUEST on iwi0 to 255.255.255.255 port 67
DHCPACK from 10.255.253.253
bound to 10.255.253.200 -- renewal in 300 seconds.
iwi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::216:6fff:fe8b:a21%iwi0 prefixlen 64 scopeid 0x2
inet 10.255.253.200 netmask 0xff00 broadcast 10.255.253.255
ether 00:16:6f:8b:0a:21
media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps)
status: associated
ssid SSID channel 11 bssid xx:xx:xx:xx:xx:xx
authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 100
bmiss 10 protmode CTS roaming MANUAL bintval 100
The first couple of times it recovers on it self but after receiving
iwi0: could not allocate firmware DMA memory I always have to restart the
connection manually.
The kernel is built with option INVARIANTS and option INVARIANT_SUPPORT.
uname -a
FreeBSD viglaf 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #62: Thu Oct 5
10:35:57 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VIGLAF i386
pkg_info -Ix iwi
iwi-firmware-kmod-3.0_1 Intel PRO/Wireless 2200 Firmware Kernel Module
dmesg attached.
/glz
--On Monday, October 09, 2006 18:35:40 +0400 Andrew N. Below
[EMAIL PROTECTED] wrote:
Hi.
I have an Asus V6V (V6800) laptop with Intel wireless adapter:
iwi0: Intel(R) PRO/Wireless 2200BG
and FreeBSD installed:
defanbook# uname -v
FreeBSD 6.2-PRERELEASE #3: Mon Oct 9 17:40:59 UTC 2006
I want to connect to access point (cisco 350) with
hidden (not broadcasted) SSID using WPA/TKIP authentication
but still got no success.
Here is my wpa_supplicant.conf:
===
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid=MY-SSID
scan_ssid=1
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk=PASSPHRASE
phase2=auth=MSCHAPV2
}
===
Here is wpa_supplicant output:
defanbook# wpa_supplicant -ddKt -i iwi0 -c /etc/wpa_supplicant.conf
Oct 09 18:24:41.247941: Initializing interface 'iwi0' conf
'/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A'
Oct 09 18:24:41.248083: Configuration file '/etc/wpa_supplicant.conf' -
'/etc/wpa_supplicant.conf'
Oct 09 18:24:41.248094: Reading configuration file
'/etc/wpa_supplicant.conf'
Oct 09 18:24:41.248129: ctrl_interface='/var/run/wpa_supplicant'
Oct 09 18:24:41.248473: ctrl_interface_group=0
Oct 09 18:24:41.248490: eapol_version=1
Oct 09 18:24:41.248497: ap_scan=1
Oct 09 18:24:41.248503: fast_reauth=1
Oct 09 18:24:41.248510: Line: 7 - start of a new network block
Oct 09 18:24:41.248520: ssid - hexdump_ascii(len=11):
[..]
Oct 09 18:24:41.248535: scan_ssid=1
Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2
To add another twist to this: I added options POLLING to the kernel, moved the fireware and USB drivers from the kernel and loaded them as modules. I have NOT enabled polling on the em-interface but this new kernal, built on the same sources as the failing one works without a hitch. As before, let me know if there is anything I can do to help. Regards, Goran L --On Wednesday, September 27, 2006 13:24:15 +0200 glz [EMAIL PROTECTED] wrote: I have seen the watchdog and reset problem on a -STABLE laptop, both em and iwi. It only occur when I try to connect using Mulberry e-mail client so I thought it could be a problem with the linuxilator. The load on the box is normally low but both driver have shared interrupts, either with cbb or usb. Here is what I can see: uname -a: FreeBSD viglaf 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #55: Thu Sep 21 22:15:38 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VIGLAF i386 dmesg: em0: Intel(R) PRO/1000 Network Connection Version - 6.1.4 port 0x8000-0x803f mem 0xc022-0xc023,0xc020-0xc020 irq 11 at device 1.0 on pci2 em0: Ethernet address: 00:0d:60:89:36:e8 em0: [FAST] iwi0: Intel(R) PRO/Wireless 2915ABG mem 0xc0214000-0xc0214fff irq 9 at device 2.0 on pci2 iwi0: Ethernet address: 00:16:6f:8b:0a:21 vmstat -i interrupt total rate irq0: clk 11148090999 irq1: atkbd0 32271 2 irq5: pcm0 atapci+157115 14 irq6: fdc0 1 0 irq7: 1 0 stray irq7 1 0 irq8: rtc1426745127 irq9: cbb1 cbb2++* 26582 2 irq11: cbb0 em0++*762544 68 irq12: psm0 516858 46 irq14: ata043494 3 irq15: ata1 82 0 Total 14113784 1265 This is a development machine so I can debug and test patches as needed. Best regards, Goran L Patrick M. Hausen wrote: Hello! On -stable occasionally other people complained about very similar looking problems with bge and other drivers. My guess is, though I'm not a kernel developer, just an experienced admin, that em stands out as problematic just by coincidence. Certain onboard network components tend to come with certaiin chipsets and certain architectures. I forgot to mention: we do have systems with em interfaces that never showed this problem! Regards, Patrick -- ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile, Aurorum 2, S-977 75 Lule￥, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem restarting gvinum raid-5
Hi, We have a gvinum raid-5 volume that that we had to replace a disk on and after that we cant get the new subdisk starting. Here are the things we did: 1: Replace disk and boot singleuser to fdisk and lable new disk: gvinum - list 5 drives: D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0R5 State: up Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s0State: up D: disk1Size: 17 GB S imap.p0.s1State: up D: disk2Size: 17 GB S imap.p0.s2State: up D: disk3Size: 17 GB S imap.p0.s3State: up D: disk4Size: 17 GB S imap.p0.s4State: up D: disk5Size: 17 GB After fixing the new disk partition we did a saveconfig and reboot: gvinum - list 5 drives: D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0R5 State: up Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s4State: staleD: disk5Size: 17 GB S imap.p0.s3State: up D: disk4Size: 17 GB S imap.p0.s2State: up D: disk3Size: 17 GB S imap.p0.s1State: up D: disk2Size: 17 GB S imap.p0.s0State: up D: disk1Size: 17 GB Tried start on plex and subdisk, nnot working. Finally, to get plex into degraded mode we did a setstate down imap.p0.s4. gvinum - list 5 drives: D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0R5 State: degraded Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s4State: down D: disk5Size: 17 GB S imap.p0.s3State: up D: disk4Size: 17 GB S imap.p0.s2State: up D: disk3Size: 17 GB S imap.p0.s1State: up D: disk2Size: 17 GB S imap.p0.s0State: up D: disk1Size: 17 GB and here we are. Start on volume or plex give errno 16, start on subdisk gives can't start: cannot start 'imap.p0.s4' - not yet supported. Can't find any descriptions of the proper way to do disk replacement, so if this is wrong, I'd love to get updated. And how do we get the current situation upa nd running? Regards, Göran ... the future isMobile Goran Lowkrantz [EMAIL PROTECTED] System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
