From owner-freebsd-stable@FreeBSD.ORG Mon Feb 28 00:55:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D3F16A4CE for ; Mon, 28 Feb 2005 00:55:48 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37B1743D2D for ; Mon, 28 Feb 2005 00:55:48 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j1S0tgX4012715; Sun, 27 Feb 2005 19:55:42 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <4222556B.5010805@root.org> References: <42439.1109545793@critter.freebsd.dk> <4222556B.5010805@root.org> Date: Sun, 27 Feb 2005 19:55:41 -0500 To: Nate Lawson , Poul-Henning Kamp From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: stable@freebsd.org cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: patch: fix 30 second hang while resuming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 00:55:48 -0000 At 3:19 PM -0800 2/27/05, Nate Lawson wrote: >Poul-Henning Kamp wrote: >> >>Have you tried sos@ new ATAng mk III patches ? As far as I know >>he plans to commit those shortly. One minor point: S=F8ren is on vacation right now. I *think* he will be getting back around March 5th (assuming I understand what he said in a recent message). So, *if* this is something we want to get in before the code-freeze, we may have to act without his input. >Not yet. In any case, I'd prefer these problems be fixed before >the import since the patches are minor and data corruption is >generally a bad thing for a little while even if a large, new >something is coming sometime soon. Your original message only mentioned a long-delay when resuming. Is this bug also causing data-corruption in some circumstances? (I don't have the slightest idea what this area of code does, I just want to make sure we understand how serious the issue is...). Is this something which only comes up in 6.x? Or is the same thing happening in 5.x too? -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu