Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751662Ab0LWEbT (ORCPT ); Wed, 22 Dec 2010 23:31:19 -0500 Received: from cantor.suse.de ([195.135.220.2]:43795 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764Ab0LWEbS (ORCPT ); Wed, 22 Dec 2010 23:31:18 -0500 Subject: Re: Boot failure with block/for-next From: James Bottomley To: Jens Axboe Cc: Tejun Heo , linux-scsi , linux-kernel In-Reply-To: <1293038823.3019.89.camel@mulgrave.site> References: <1293038823.3019.89.camel@mulgrave.site> Content-Type: text/plain; charset="UTF-8" Date: Wed, 22 Dec 2010 22:31:13 -0600 Message-ID: <1293078673.3019.765.camel@mulgrave.site> Mime-Version: 1.0 X-Mailer: Evolution 2.30.1.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 915 Lines: 30 On Wed, 2010-12-22 at 11:27 -0600, James Bottomley wrote: > Trying to test out the SCSI post merge tree, I've found it won't boot on > my SCSI test system. The reason is a failure to read the partition > table of the root disc. It just gives > > sda: unable to read partition table > > The other four discs in the system seem to read their partition tables > OK. > > The obvious candidate is the partition code rework in block/for-next. > Simply reverting Actually, surprisingly, bisection confirms it's this patch: Author: Tejun Heo Date: Wed Dec 8 20:57:42 2010 +0100 sd: implement sd_check_events() I can't quite see how yet. James -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/