From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40166) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rapso-00020X-Sh for qemu-devel@nongnu.org; Wed, 14 Dec 2011 09:32:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rapsn-0004eh-6b for qemu-devel@nongnu.org; Wed, 14 Dec 2011 09:32:34 -0500 Received: from mail-ww0-f53.google.com ([74.125.82.53]:50277) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rapsn-0004as-0w for qemu-devel@nongnu.org; Wed, 14 Dec 2011 09:32:33 -0500 Received: by mail-ww0-f53.google.com with SMTP id ds1so1654548wgb.10 for ; Wed, 14 Dec 2011 06:32:32 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4EE8A6FA.8090305@labri.fr> References: <20111202125742.13621.362.malonedeb@soybean.canonical.com> <20111202131025.12679.91449.launchpad@wampee.canonical.com> <4ED8E449.1010409@labri.fr> <4EDB98B2.6070408@labri.fr> <20111205082617.GA20569@stefanha-thinkpad.localdomain> <4EDCA13E.3080508@labri.fr> <4EE8A6FA.8090305@labri.fr> Date: Wed, 14 Dec 2011 14:32:31 +0000 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [Bug 899140] Re: Problem with Linux Kernel Traffic Control List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bug 899140 <899140@bugs.launchpad.net> Cc: qemu-devel@nongnu.org On Wed, Dec 14, 2011 at 1:36 PM, Vincent Autefage <899140@bugs.launchpad.net> wrote: > I have checked differences between the GIT repository (V0.14.0) and the > Ubuntu version (V0.14.0) and generated patch diff file. > The patch contains about 5000 lines... > > What's the next step ? Okay, so when you rebuild the Ubuntu package from source the bug is not present and the largish diff suggests they have added patches on top of vanilla 0.14.0. If the Ubuntu source ships with a number of .diff/.patch files that get applied during the build then you could manually bisect this. That means rerunning the Ubuntu build but with only the first half of the list of patches applied. If that has the bug then split the untested patches in half too and continue the test cycle. If the bug is not present then split the patches in half and continue testing until you reach the point where the bug goes from present to fixed. Stefan