linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Alan <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Cable detection fixes
Date: Thu, 1 Mar 2007 23:35:07 -0700	[thread overview]
Message-ID: <20070302063507.GA8345@ellpspace.math.ualberta.ca> (raw)
In-Reply-To: <45E77EDD.3010205@garzik.org>

On Thu, Mar 01, 2007 at 08:33:17PM -0500, Jeff Garzik wrote:
> 
> That little change, buried in the middle of Alan's patch, changes the 
> probing order for a /lot/ of devices, possibly millions, when you 
> consider that it changes behavior of ata_piix (Intel SATA) as well as 
> all the not-yet-default PATA controllers.

Hm, I got recently hands on a hardware where 2.6.21-rc1 based
kernels from Fedora rawhide simply do not boot as there is no
way to get to disks.  I would not mind some change in behavior
although so far I can boot at least some earlier kernels.

This looks like ATIIXP issue and details are here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229621
Changelogs for kernels in question have this:

* Wed Feb 21 2007 Dave Jones <davej@redhat.com>
- 2.6.21-rc1

   Michal

  reply	other threads:[~2007-03-02  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 17:30 [PATCH] libata: Cable detection fixes Alan
2007-03-02  1:24 ` Linus Torvalds
2007-03-02  1:33   ` Jeff Garzik
2007-03-02  6:35     ` Michal Jaegermann [this message]
2007-03-02 12:52       ` Alan Cox
2007-03-02  1:26 ` Jeff Garzik
2007-03-02 12:45   ` Alan Cox
2007-03-02 22:50     ` Jeff Garzik
2007-03-02 22:48 ` Jeff Garzik
2007-03-03 19:35 ` Paul Rolland

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=20070302063507.GA8345@ellpspace.math.ualberta.ca \
    --to=michal@ellpspace.math.ualberta.ca \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@harddata.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).