From owner-freebsd-current@freebsd.org Mon Aug 31 11:56:51 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09E7A9C2007 for ; Mon, 31 Aug 2015 11:56:51 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C43EAC9B for ; Mon, 31 Aug 2015 11:56:50 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from 141.7.19.93.rev.sfr.net ([93.19.7.141] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZWNhh-0001xi-1g; Mon, 31 Aug 2015 13:56:49 +0200 Subject: Re: panic: Stray timeout To: Oliver Pinter References: <55E2DA91.6080206@FreeBSD.org> <55E353E1.6050605@FreeBSD.org> <55E41522.7070409@FreeBSD.org> Cc: freebsd-current@freebsd.org From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= X-Enigmail-Draft-Status: N1110 Message-ID: <55E440EC.3070108@FreeBSD.org> Date: Mon, 31 Aug 2015 13:56:28 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KawJB387EumuCcMX1Ee4mauNoLT9ObpHu" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2015 11:56:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KawJB387EumuCcMX1Ee4mauNoLT9ObpHu Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 31.08.2015 12:58, Oliver Pinter wrote: > I got this panic, and I have somewhere a kernel and a coredump on my > other machine. I got this panic only when I put my machine under heavy > load and use X with randonkms driver. > When I didn't use X and start the build under vt, I newer got this pani= c. The function called by this taskqueue cleans up graphical buffer objects. vt(4) relies on a single buffer object which doesn't change for its entire life, that's why this TTM task is unused with vt(4). However, buffer objects are heavily used by the X server and Mesa. The task is executed several times a second on my laptop. --=20 Jean-S=C3=A9bastien P=C3=A9dron --KawJB387EumuCcMX1Ee4mauNoLT9ObpHu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJV5EDsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMxKkP/2ahYJ8jywKLm2R0Z+J2iU71 o1I+lv7bOApHWxYgh6JdaHSlPSG3Sy+d3UsRDBiSAWFqp8op9hIJh1yU8SH+o27K bzhfxYC98rjzwROfL9Ig7EgJqI7orVeNRH3tvanNHZ4jp18LhzBYneHLNhm1Wyfe 39ifzgRWTSsG7LLVaSMQJlfwm4zxhVJiYbWxEaWR2SuqEvLZeMNDHzQx+MxwAgJI uyBS254HVdZa1PtfeNw0N9JNExqYaTKn3N6vvoROwhe7QEkst6XqMG00bgI0pG0/ 1Ok/j2sjFf7l+wuCpO7BocQbxl0AVr4ZLxSH1vP5AxorDX+axyqfn7Q7PoWCQKxX CcmaWXavdYCiQk4vwSj8rCHzcYyrz9D+hi+8kHlw4Rh+QhhN/+/Azd784xwQaIj5 HXt1Kzgb1w+74ARbXdT7Pmz8FIy54Y771AqPG6veWfzFyfO3150Pc4FKYJFqxavV 7bdoH3HeUtFL8HLOswrBHOlqyDUwYxxFNV1Mxzv8sONQpBmA0PTKYan/xrU2PqDw X+0SBrTZJaAmAoror8V/VYXUBtb+mA3ls79hrKH7m1UcIiPmVb8LhmRd356WXt3O lX++fgnJM9CJ01+yAUlb5od4IvD8EDVCSAvdMmNPYpC5KtMaN1vK8TR29zsGEQ7n vC4IubW7aCdLMljWn/39 =BRW0 -----END PGP SIGNATURE----- --KawJB387EumuCcMX1Ee4mauNoLT9ObpHu--