From: Jeff Garzik <jgarzik@pobox.com>
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
Date: Wed, 09 Mar 2005 15:31:10 -0500 [thread overview]
Message-ID: <422F5D0E.7020004@pobox.com> (raw)
In-Reply-To: <9e4733910503091023474eb377@mail.gmail.com>
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
next prev parent reply other threads:[~2005-03-09 20:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:03 current linus bk, error mounting root Jon Smirl
2005-03-09 17:16 ` Jeff Garzik
2005-03-09 18:23 ` Jon Smirl
2005-03-09 20:28 ` Jeff Garzik
2005-03-09 20:31 ` Jeff Garzik [this message]
2005-03-09 20:51 ` Jon Smirl
2005-03-09 21:09 ` Jens Axboe
2005-03-10 1:16 ` Jon Smirl
2005-03-10 7:50 ` Jens Axboe
2005-03-10 14:58 ` Jon Smirl
2005-03-10 15:31 ` Jens Axboe
2005-03-10 15:45 ` Jon Smirl
2005-03-10 15:48 ` Jens Axboe
2005-03-10 15:59 ` Jon Smirl
2005-03-10 16:01 ` Jens Axboe
2005-03-10 16:18 ` Jon Smirl
2005-03-10 16:29 ` Jens Axboe
2005-03-10 18:40 ` Jon Smirl
2005-03-10 18:52 ` Jon Smirl
2005-03-11 3:11 ` Matt Mackall
2005-03-11 3:18 ` Jon Smirl
2005-03-15 15:39 ` Jon Smirl
2005-03-15 15:47 ` Jens Axboe
2005-03-09 20:34 ` Steven Cole
[not found] ` <20050321154131.30616ed0.akpm@osdl.org>
[not found] ` <9e473391050321155735fc506d@mail.gmail.com>
2005-03-22 0:19 ` Andrew Morton
2005-03-22 0:38 ` Greg KH
2005-03-22 0:43 ` Andrew Morton
2005-03-22 0:49 ` Greg KH
2005-03-22 0:57 ` Jon Smirl
2005-03-22 4:02 ` Greg KH
2005-03-22 1:13 ` Jon Smirl
2005-03-22 0:53 ` Jon Smirl
2005-03-22 4:03 ` Greg KH
2005-03-22 0:47 ` Jon Smirl
2005-03-22 1:14 ` Kyle Moffett
2005-03-22 4:02 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 13:15 Alexander E. Patrakov
2005-03-12 19:56 ` Jon Smirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422F5D0E.7020004@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.