From: Pat LaVarre Subject: Re: diff "lk 2.4 udf.ko" "lk 2.6 udf.ko" Date: 02 Dec 2003 18:17:40 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1070414259.2253.20.camel@patibmrh9> References: <1070323536.8454.8.camel@patibmrh9> <1070394858.4338.12.camel@patibmrh9> <1070397983.7531.4.camel@patibmrh9> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:39165 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S264478AbTLCBSa (ORCPT ); Tue, 2 Dec 2003 20:18:30 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 9FFE61EE9 for ; Tue, 2 Dec 2003 18:18:29 -0700 (MST) To: linux-fsdevel@vger.kernel.org In-Reply-To: <1070397983.7531.4.camel@patibmrh9> List-Id: linux-fsdevel.vger.kernel.org > > > > 2.6.0-test11 [fails] > > > ... > > > 2.4.23 [ok] > > ... > > From: http://lxr.linux.no/source/Documentation/BUG-HUNTING > > ... > > My apologies to Linus and the other kernel hackers > > for describing this brute force approach, it's > > hardly what a kernel hacker would do. However, it > > does work and it lets non-hackers help fix bugs. > ... > The binary-ish search begins ... The window narrows. Somewhere between 2.5.26 and 2.5.56, we changed udf.ko from ok to fail. More specifically, captured and sorted today, my results were: 2.4.23 udf ok 2.5.1 no defconfig 2.5.15 no defconfig 2.5.26 no gui, udf ok 2.5.37 does not boot 2.5.47 does not loop and complains much of hdc 2.5.51 does not boot 2.5.56 fails 2.6.0-test11 fails My next try may be 2.5.41, chosen by way of dc -e '26 56 + 2 / p' Pat LaVarre