Date: Wed, 20 Mar 2013 09:14:30 -0400 From: Mark Saad <nonesuch@longcount.org> To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Core Dump / panic sleeping thread Message-ID: <20F03334-E1AA-4FEA-B45F-33547D7E454D@longcount.org> In-Reply-To: <0A794600-0D7C-4982-9665-1C39FEFCF8C1@freebsd.org> References: <A6D4A877-2DBA-4E9D-996D-2E34834BF60E@freebsd.org> <20130319173530.GA72669@icarus.home.lan> <0A794600-0D7C-4982-9665-1C39FEFCF8C1@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Comments in line . --- On Mar 19, 2013, at 1:45 PM, Michael Landin Hostbaek <mich@freebsd.org> wrot= e: >=20 > On Mar 19, 2013, at 6:35 PM, Jeremy Chadwick <jdc@koitsu.org> wrote: >=20 >> On Tue, Mar 19, 2013 at 06:18:06PM +0100, Michael Landin Hostbaek wrote: >> The kernel panic is happening in NFS-related code. Rick Macklem (and/or >> John Baldwin) should be able to help with this; I've CC'd both here. >=20 > OK, thanks.=20 >=20 >=20 >>=20 >> You're going to need to provide the following details: >>=20 >> 1. Contents of /etc/rc.conf >=20 > sshd_enable=3D"YES" > ntpdate_enable=3D"YES" > ntpdate_hosts=3D"xx.xx.xx.xx" > fsck_y_enable=3D"YES" > named_enable=3D"YES" > dumpdev=3D"AUTO" > nfs_client_enable=3D"YES" > rpc_lockd_enable=3D"YES" > rpc_statd_enable=3D"YES" > ifconfig_em0=3D"inet xx.xx.xx.xx netmask 255.255.255.0 broadcast xx.xx.xx.= xx" > defaultrouter=3D"xx.xx.xx.xx" > hostname=3D"xxxxxxxx" > cloned_interfaces=3D"vlanXXXX" > ifconfig_vlanXXXX=3D"inet xx.xx.xx.xx netmask 255.240.0.0 broadcast xx.xx.= xx.xx vlan XXXX vlandev em0" > apache22_enable=3D"YES" > pureftpd_enable=3D"YES" > revealcloud_enable=3DYES >=20 >=20 >> 2. Contents of /etc/sysctl.conf (if modified) >=20 > vm.pmap.shpgperproc=3D250 >=20 Small side note. This sysctl is no longer valid . It's had no effect after 7= .2 iirc .=20 >> 3. Contents of /etc/fstab >=20 > # Device Mountpoint FStype Options Dump Pa= ss# > /dev/mirror/gm0s1a / ufs rw 1 1 > /dev/mirror/gm0s1b none swap sw 0 0 > /dev/mirror/gm0s1d /var ufs rw 2 2 > /dev/mirror/gm0s1e /logs ufs rw 2 2 > /dev/mirror/gm0s1f /extra ufs rw 2 2 > /dev/mirror/gm0s1g /usr ufs rw 2 2 > proc /proc procfs rw 0 0 > xx.xx.xx.xx:/zpool-000xxx/www /mnt/www nfs rw 0 0 > xx.xx.xx.xx:/zpool-000xxx/data /mnt/data nfs rw,tcp 0 0= > linproc /compat/linux/proc linprocfs rw 0 0 >=20 >=20 >> 4. ifconfig -a >=20 > em0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 150= 0 > options=3D4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,= WOL_MAGIC,VLAN_HWTSO> > ether 00:25:90:79:a5:ac > inet xx.xx.xx.xx netmask 0xffffff00 broadcast xx.xx.xx.xx > inet6 xxxxxx::a5ac%em0 prefixlen 64 scopeid 0x1=20 > nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > em1: flags=3D8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=3D4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,= WOL_MAGIC,VLAN_HWTSO> > ether 00:25:90:79:a5:ad > nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect > status: no carrier > lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > options=3D600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> > inet6 ::1 prefixlen 128=20 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xb=20 > inet 127.0.0.1 netmask 0xff000000=20 > nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL> > vlanXXXX: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mt= u 1500 > options=3D103<RXCSUM,TXCSUM,TSO4> > ether 00:25:90:79:a5:ac > inet xx.xx.xx.xx netmask 0xfff00000 broadcast xx.xx.xx.xx > inet6 xxxxx:::5ac%vlanXXXX prefixlen 64 scopeid 0xc=20 > nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > vlan: XXXX parent interface: em0 >=20 >=20 >> 5. OS used by the NFS server, and all configuration details pertaining >> to that system >=20 > This is a hosted service, so I do not have access to this - though I belie= ve this is a ZFS fs. > Here's more info about the product: http://help.ovh.co.uk/Nas >=20 >=20 >>=20 >> You may also be asked to upgrade to 9.1-STABLE, as there may be fixes >> for whatever this is in base/stable/9 that are not in -RELEASE, but this >> is speculative on my part. >=20 > That is not a problem. I would simply like to confirm the issue, before up= grading.=20 >=20 >=20 > Thanks,=20 >=20 > /mich >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Mark saad | mark.saad@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20F03334-E1AA-4FEA-B45F-33547D7E454D>