Date: Fri, 6 Jul 2007 18:42:47 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Alex Keda <admin@lissyara.su> Cc: freebsd-net@freebsd.org Subject: Re: Fatal double fault while copy to NFS filesystems Message-ID: <20070706154247.GH2200@deviant.kiev.zoral.com.ua> In-Reply-To: <468E5A94.3030509@lissyara.su> References: <468E5A94.3030509@lissyara.su>
next in thread | previous in thread | raw e-mail | index | archive | help
--MEatx1zidE5asLAI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 06, 2007 at 07:07:00PM +0400, Alex Keda wrote: > When I copy files to NFS on another host kernel crash: > Fatal double fault: > eip =3D 0xc07e9e29 > esp =3D 0xe31a3000 > ebp =3D 0xe31a3000 > cpuid =3D 1; apic id =3D 01 > panic: double fault > cpuid =3D 1 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > before this, I see on /var/log/messages > nve0: device timeout > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > how repeat problem: > ussr# df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1a 72G 6.1G 60G 9% / > devfs 1.0K 1.0K 0B 100% /dev > ussr# dd if=3D/dev/zero of=3Dfile_20mb bs=3D1m count=3D20 > ussr# mount 192.168.254.254:/shares /mnt/ > ussr# df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1a 72G 6.1G 60G 9% / > devfs 1.0K 1.0K 0B 100% /dev > 192.168.254.254:/shares 271G 179G 89G 67% /mnt > ussr# cp file_20mb /mnt/ > then, after 3-5 second I see "device timeout", and later, after 5-7=20 > seconds - system crash > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > another information - this problem appearance after I upgrade remote=20 > machine (6.2-RELEASE-p5), I change CPU from Celeron 466 to PIII 800. > interface on remote machine - 3com509b > if I slow copy to remote machine (~100kb/s - 10% interface usage) - all= =20 > good. System not crash... > if I copy from remote machine - all good - system not crash... > on logs on remote machine - all clean. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 3 days ago I upgrade my system to 6.2-RELEASE-p5, but - problem exists... Double fault issue might be the problem that is fixed in CURRENT/RELENG_6. To confirm this, ddb backtrace after the panic will be helpful. You will need to compile DDB into the kernel, obtain DDB prompt after the panic and issue "bt" command. --MEatx1zidE5asLAI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGjmL2C3+MBN1Mb4gRAk2BAJwN8S4SMw5MWkkai3Uow2AC9qo17QCgoEUI Y3VVDfnqJRVc8c3Yy/O6JHc= =C44m -----END PGP SIGNATURE----- --MEatx1zidE5asLAI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070706154247.GH2200>