From: Jens Axboe <jens.axboe@oracle.com>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sda] write cache: enabled, read cache:enabled: doesn't support DPO or FUA, sda:
Date: Tue, 28 Oct 2008 15:04:50 +0100 [thread overview]
Message-ID: <20081028140449.GN22217@kernel.dk> (raw)
In-Reply-To: <40a4ed590810280703q665ed37du3f8c25df0855dc5d@mail.gmail.com>
(don't top post)
> On Tue, Oct 28, 2008 at 2:57 PM, Jens Axboe <jens.axboe@oracle.com> wrote:
> > On Tue, Oct 28 2008, Zeno Davatz wrote:
> >> Dear List
> >>
> >> After my latest git pull from
> >>
> >> url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> >>
> >> I done
> >>
> >> make silentoldconfig
> >> make modules_install
> >>
> >> copied the bzImage to /boot and ran lilo.
> >>
> >> When I want to boot into 2.6.28-rc2 I get:
> >>
> >> [sda] write cache: enabled, read cache:enabled: doesn't support DPO or FUA, sda:
> >>
> >> Also see my screenshot:
> >>
> >> http://farm4.static.flickr.com/3213/2980651545_de81680bf9_o.jpg
> >
> > How recent is that pull? This looks like something fixed in-between -rc1
> > and -rc2. So I'd double check that you are after or on -rc2 and that you
> > are booting the right kernel.
>
> That Pull is from right after Linus released 2.6.28-rc2. I always pull
> after Linus releases an rc and notifys everyone through the list.
>
> I will pull again right now and try again.
Please do, and if it still breaks then use netconsole or a serial
console to capture all boot messages!
--
Jens Axboe
next prev parent reply other threads:[~2008-10-28 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 13:48 [sda] write cache: enabled, read cache:enabled: doesn't support DPO or FUA, sda: Zeno Davatz
2008-10-28 13:57 ` Jens Axboe
2008-10-28 14:03 ` Zeno Davatz
2008-10-28 14:04 ` Jens Axboe [this message]
2008-10-28 14:19 ` Zeno Davatz
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=20081028140449.GN22217@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zdavatz@gmail.com \
/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.