Message-ID: <422F5D0E.7020004@pobox.com>
Date: Wed, 09 Mar 2005 15:31:10 -0500
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922
MIME-Version: 1.0
To: Jon Smirl <jonsmirl@gmail.com>
CC: lkml <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: current linus bk, error mounting root
References: <9e47339105030909031486744f@mail.gmail.com>	 <422F2F7C.3010605@pobox.com> <9e4733910503091023474eb377@mail.gmail.com>
In-Reply-To: <9e4733910503091023474eb377@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1249
Lines: 44

Jon Smirl wrote:
> On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>Jon Smirl wrote:
>>
>>>Something in the last 24hrs in linus bk broke my ability to mount root:
>>>
>>>Creating root device
>>>Mounting root filesystem
>>>mount: error 6 mounting ext3
>>>mount: error 2 mounting none
>>>Switching to new root
>>>Switchroot: mount failed 22
>>>umount /initrd/dev failed: 2
>>>
>>>If I back off a day everything works again.
>>>
>>>Root is on Intel ICH5 SATA drive.
>>
>>dmesg output?
>>
>>Can you verify that -bk4 works, and -bk5 breaks?
> 
> 
> bk4 works. I don't have a serial port hooked up so there is no way to
> get dmesg, but I don't see anything obvious on the screen scrolling
> by.
> 
> I'll check bk5 next.
> 
> It would be much more convenient if the bkN releases were tagged in Linus bk.

Well, there are no changes in libata from bk4 to present.  The only 
thing I see in the -bk4-bk5 increment diff that's immediately noticeable 
is the barrier stuff.

	Jeff


-
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/