public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "C.Y.M." <syphir@syphir.sytes.net>
Cc: linux-kernel@vger.kernel.org, "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: Re: Changes to ide-probe.c in 2.6.9-rc2 causing improper detection
Date: Tue, 14 Sep 2004 09:06:50 +0200	[thread overview]
Message-ID: <20040914070649.GI2336@suse.de> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA9mKu6AlYok2efOpJ3sb3O+KAAAAQAAAA6P8AlyGHikORXOqFZ6fdPAEAAAAA@syphir.sytes.net>

On Tue, Sep 14 2004, C.Y.M. wrote:
> 
> > 
> > On Mon, Sep 13 2004, C.Y.M. wrote:
> > > After installing 2.6.9-rc2 on my PC today (x86 VIA Chipset 
> > motherboard and
> > > Athlon XP CPU), The IDE detection during boot in probing 
> > for ide2-5 and
> > > displaying errors, and the hard drives that it does find 
> > are telling me that
> > > "hda: cache flushes not supported" (when they are displayed 
> > as supported
> > > when using 2.6.9-rc1.
> > 
> > Your drive doesn't advertise FLUSH_CACHE support, the model 
> > for when we
> > use these commands changed between -rc1 and -rc2. This 
> > essentially means
> > that you have to turn off write back caching for safe operations on a
> > journalled drive.
> > 
> > Alan, I bet there are a lot of these. Maybe we should consider letting
> > the user manually flag support for FLUSH_CACHE, at least it 
> > is in their
> > hands then.
> > 
> > -- 
> > Jens Axboe
> > 
> 
> Thanks for the explanation.  I can understand that some of the older drives
> will not support FLUSH_CACHE which is acceptable. On another note, since

They do support it, they just don't flag the support in the capability
flags. And of course some don't support it at all, you can try this on
your drives if you want to know for sure.

> most computers only have IDE0 and IDE1 slots, is there a way to prevent the
> probe from returning errors on boot when looking for IDE2 to IDE5?  Perhaps
> a kernel configuration option asking how many IDE's are expected to probe
> (defaulting to two)?

It is very annoying, I agree, I don't see the need to confuse people
with this message as well. Until that is fixed, you should be able to
use ide2=noprobe etc on the boot command line.

-- 
Jens Axboe


  reply	other threads:[~2004-09-14  7:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14  2:26 Changes to ide-probe.c in 2.6.9-rc2 causing improper detection C.Y.M.
2004-09-14  6:06 ` Jens Axboe
2004-09-14  7:03   ` C.Y.M.
2004-09-14  7:06     ` Jens Axboe [this message]
2004-09-14  7:15       ` Jens Axboe
2004-09-14  8:20         ` C.Y.M.
2004-09-14  8:28           ` Jens Axboe
2004-09-14 10:09         ` Alan Cox
2004-09-14 11:12           ` Jens Axboe
2004-09-14 10:35             ` Alan Cox
2004-09-14 11:43               ` Jens Axboe
2004-09-14 11:19                 ` Alan Cox
2004-09-14 12:21                   ` Jens Axboe
2004-09-14 11:37         ` Gene Heskett
2004-09-14 10:07       ` Alan Cox
2004-09-14 11:11         ` Jens Axboe
2004-09-14 11:59     ` Bartlomiej Zolnierkiewicz
2004-09-14 13:15       ` Jens Axboe
2004-09-14 10:05   ` Alan Cox
2004-09-14 11:09     ` Jens Axboe
2004-09-14 12:07     ` Bartlomiej Zolnierkiewicz
2004-09-14 15:18     ` Jeff Garzik
2004-09-14 15:25       ` Jens Axboe
2004-09-14 15:05         ` Alan Cox
2004-09-14 15:33         ` Mark Lord
2004-09-14 15:39           ` Mark Lord
2004-09-14 15:51             ` Jeff Garzik
2004-09-14 15:06               ` Alan Cox
2004-09-14 15:45           ` Jeff Garzik
2004-09-14 15:31       ` Mark Lord

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=20040914070649.GI2336@suse.de \
    --to=axboe@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syphir@syphir.sytes.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox