Date: Wed, 6 Nov 2013 04:29:32 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Matt Magoffin <matt@msqr.us> Cc: freebsd-stable@freebsd.org Subject: Re: 9.2-RELEASE amd64 panic: vn_open_cred Message-ID: <20131106022932.GY59496@kib.kiev.ua> In-Reply-To: <DF88429C-058E-4756-AFC4-F97249FF54AA@msqr.us> References: <DF88429C-058E-4756-AFC4-F97249FF54AA@msqr.us>
next in thread | previous in thread | raw e-mail | index | archive | help
--m9Vkydzf3ccYCnyC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 06, 2013 at 07:26:17AM +1300, Matt Magoffin wrote: > Hello, >=20 > I have been running a generic 9.1 kernel for some time, and tried to upgr= ade to 9.2. The upgrade itself goes smoothly, but after running a few minut= es I get a panic like this: >=20 > panic: vm_fault: fault on nofault entry, addr: ffffff836e0fc000 > cpuid =3D 0 > KDB: stack backtrace: > n0 0xffffffff80947986 at kdb_backtrace+0x66 > n1 0xffffffff8090d9ae at panic+0x1ce > nz 0xffffffff80b79eca at vm_fault_hold+0x1f8a > n3 0xffffffff80b7a663 at vm_fault+0x73 > n4 0xffffffff80cf260f at trap_pfault+0x3~f > ns 0xffffffff80cf29e4 at trap+0x344 > n6 0xffffffff80cdbd13 at calltrap+0x8 > n? 0xffffffff80d96898 at VOP_ADD_WRITECOUNT_APV+0x78 > na 0xffffffff809bad48 at vn_open_cred+0x5d8 > n9 0xffffffff809b676a at kern_openat+0x20a > n10 0xffffffff80cf187a at amd64_syscall+0x5ea > n11 0xffffffff80cdbff7 at Xfast_syscall+0xf7 > Uptime: 5m24s >=20 > This is a production system for which I don't have a similar setup to tes= t changes on, so I rolled back (via a zfs snapshot) to 9.1 after the panic = consistently happened after rebooting. I can't say with certainty what was = causing the crash: after booting I performed my usual system tasks which in= volved mounting some pefs filesystems (and thus loading the pefs kernel mod= ule) and starting up a Postgres server. >=20 > After rolling back to 9.1 I did repeat the upgrade process and ended up w= ith the same panic, so I have since left it in 9.1. >=20 > I'm afraid I'm relatively new to FreeBSD, so I don't have any crash dumps= =2E I wondered if anyone had any ideas on what might be causing this type o= f panic? I do not see how you being new to freebsd prevents the system from dumping core. At least, look up the source line number for the VOP_ADD_WRITECOUNT_APV+0x7= 8, by loading the kernel.debug into kgdb and doing list *VOP_ADD_WRITECOUNT_APV+0x78 The lines should be from the build-time generated file vnode_if.c, so please provide the excerpt from the source file around the reported line. Just in case, do you have out-of-tree kernel modules installed on your system ? If yes, did you recompiled them after the upgrade ? --m9Vkydzf3ccYCnyC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSeamLAAoJEJDCuSvBvK1BrPIP/RxZ5qnYtBeZQT/Zp4zPk+Y7 pkmg7kDzQs1iKmHN+bZ6mtd9DaO7Yv3RAtN6FwbkYtzVaDrR5bd6+K1c7VT9uumJ XZSt0RoLB7rdN+Iai0kJ7RRdYmPvEKRrkfT3xwF0ENixkLBMjll/10PYvZp0mVEO HCEAR/UaMlCpQeuePA3jhJnBXqaGI+pCimCEZMUrTPR/AD6kz9Ecsm3qnrE2Isty 7CcAEhqqcS4K2E0nzttc0wUXOoU/hFsl9fjyKZgUFQ7+ue0eNErUbXwn3oYUYq1y Vso+unGrKl48qvuXBCOoy1Zn3q5L4AcWmy+LCEfTNR2N2Ntzpl2KpDryQX9suBsU pzijZ1mUgz4iXeWLj1HhPL0XwVolnfb8dJcnYlPPTxI9usGIGXsuv6qPppglckOx weuDefNEwj0w4WqZTNhbkwAeNXd/1EY5TNRPJGwlulTrNgnOxDlg7MAI9MhI1qTy pjh0tJTMDL5owwuw9MuuaEpNXJlmre4DQGdkPEtR6oswEAzSZuwOZIKOGfjpROfo HJ2r6vRE5/K4DDQcDu5GoS3U5oVWieQWhCg5glQzySQqNJm3yggYC1NmPdPvHfMx F45I0hv70uzURdfFHlWJtnvkqQfjTToh70FOFX6MwC2rXqWxzbDhnfVmKImdbvzd BRGD51uHkOJLFVx4PDR6 =ZrfX -----END PGP SIGNATURE----- --m9Vkydzf3ccYCnyC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131106022932.GY59496>