Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Apr 2018 12:41:37 -0700
From:      Bryan Drewery <bdrewery@FreeBSD.org>
To:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: crash on process exit.. current at about r332467
Message-ID:  <da5f0963-03fe-dbd2-f271-3a44bb6f3049@FreeBSD.org>
In-Reply-To: <8644151e-7dce-1283-e804-93a4b1b7bb0b@FreeBSD.org>
References:  <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org> <8644151e-7dce-1283-e804-93a4b1b7bb0b@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--XrXTZQPqT7qonL4KyhQAbkofj9ZnNHGLl
Content-Type: multipart/mixed; boundary="q07P0RfWC0x9DqdfKOtoNi9gPYJFoA94D";
 protected-headers="v1"
From: Bryan Drewery <bdrewery@FreeBSD.org>
To: freebsd-current <freebsd-current@freebsd.org>
Message-ID: <da5f0963-03fe-dbd2-f271-3a44bb6f3049@FreeBSD.org>
Subject: Re: crash on process exit.. current at about r332467
References: <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org>
 <8644151e-7dce-1283-e804-93a4b1b7bb0b@FreeBSD.org>
In-Reply-To: <8644151e-7dce-1283-e804-93a4b1b7bb0b@FreeBSD.org>

--q07P0RfWC0x9DqdfKOtoNi9gPYJFoA94D
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 4/25/18 12:39 PM, Bryan Drewery wrote:
> On 4/23/18 7:50 AM, Julian Elischer wrote:
>> back trace at:=C2=A0 http://www.freebsd.org/~julian/bob-crash.png
>>
>> If anyone wants to take a look..
>>
>> In the exit syscall, while deallocating a vm object.
>>
>> I haven't see references to a similar crash in the last 10 days or so.=
=2E
>> But if it rings any bells...
>>
>=20
> I just hit this on r332455 and have a dump.
>=20
>> panic: Bad link elm 0xfffff811cd920e60 prev->next !=3D elm
>> cpuid =3D 10
>> time =3D 1524682939
>> KDB: stack backtrace:
>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe23=
f450c3b0
>> vpanic() at vpanic+0x18d/frame 0xfffffe23f450c410
>> panic() at panic+0x43/frame 0xfffffe23f450c470
>> vm_object_destroy() at vm_object_destroy/frame 0xfffffe23f450c4d0
>> vm_object_deallocate() at vm_object_deallocate+0x45c/frame 0xfffffe23f=
450c530
>> vm_map_process_deferred() at vm_map_process_deferred+0x99/frame 0xffff=
fe23f450c560
>> vm_map_remove() at vm_map_remove+0xc6/frame 0xfffffe23f450c590
>> exec_new_vmspace() at exec_new_vmspace+0x185/frame 0xfffffe23f450c5f0
>> exec_elf64_imgact() at exec_elf64_imgact+0x8fb/frame 0xfffffe23f450c6e=
0
>> kern_execve() at kern_execve+0x82c/frame 0xfffffe23f450ca40
>> sys_execve() at sys_execve+0x4c/frame 0xfffffe23f450cac0
>> amd64_syscall() at amd64_syscall+0x786/frame 0xfffffe23f450cbf0
>> fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe23f45=
0cbf0
>> --- syscall (59, FreeBSD ELF64, sys_execve), rip =3D 0x800d7af7a, rsp =
=3D 0x7fffffffbd28, rbp =3D 0x7fffffffbe70 ---
>=20
>=20
>=20

It's a different stack than Julian's but it seems like the same issue to =
me.

--=20
Regards,
Bryan Drewery


--q07P0RfWC0x9DqdfKOtoNi9gPYJFoA94D--

--XrXTZQPqT7qonL4KyhQAbkofj9ZnNHGLl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE+Rc8ssOq6npcih8JNddxu25Gl88FAlrg2fEACgkQNddxu25G
l89EZgf8Ca/haSUNmxU+Xq6cYacl19+4AFizBi6FcNw+QYWQ4EOEhNl0zSig5W4V
cCUwkXcx18ULMBWcax4rFMBDi8TPXYPNPFtB8Pr+DNUWycN4f68jpLqnRxo5htlt
QeKbS/uq2tPkon7ALBRRlUFRFoUZGtk/ptOCSocSMr6SCT6jkgF/FVcf7lR6GSSn
0q/mt9s8rZ9x4xN78/Atczvi01uLmDxSbLpJy/vUkGrrcYp+E6XdJPgKfne07BcF
d56AApE7KiSgL1ipP6YhmylL1jEmScG0jnfr43HGHYP+NcDyvKo2Ye8URs8WqaAo
RAOs658bQhF7EE4/WNt0KrLEbwB73Q==
=/3P0
-----END PGP SIGNATURE-----

--XrXTZQPqT7qonL4KyhQAbkofj9ZnNHGLl--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?da5f0963-03fe-dbd2-f271-3a44bb6f3049>