From: "Alan J. Wylie" <alan@wylie.me.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, EC <wingman@waika9.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: 2.4.29-pre1 OOPS early in boot with Intel ICH5 SATA controller
Date: Sun, 12 Dec 2004 15:40:52 +0000 [thread overview]
Message-ID: <16828.26244.409792.573084@devnull.wylie.me.uk> (raw)
In-Reply-To: <41BB41DC.6020808@pobox.com>
On Sat, 11 Dec 2004 13:52:12 -0500, Jeff Garzik <jgarzik@pobox.com> said:
> If you are getting an oops there, it looks like your ata_piix driver
> is mismatched from the libata core. Did you compile them both at
> the same time, from the same source kernel?
Yes. Clean build, everything compiled into the kernel, no modules.
> The assembly code above is where function ata_host_add in
> libata-core.c calls "ap->ops->port_start", which definitely exists
> in ata_piix.c.
As I noted in my follow-up e-mail, and EC has confirmed, changing the
BIOS settings from Native Mode: Auto to Native Mode: Both works around
this problem.
--
Alan J. Wylie http://www.wylie.me.uk/
"Perfection [in design] is achieved not when there is nothing left to add,
but rather when there is nothing left to take away."
-- Antoine de Saint-Exupery
next prev parent reply other threads:[~2004-12-12 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 9:49 2.4.29-pre1 OOPS early in boot with Intel ICH5 SATA controller Alan J. Wylie
2004-12-10 16:04 ` Alan J. Wylie
2004-12-11 18:52 ` Jeff Garzik
2004-12-11 20:24 ` EC
2004-12-11 20:37 ` Jeff Garzik
2004-12-11 20:59 ` EC
2004-12-12 15:40 ` Alan J. Wylie [this message]
2004-12-13 10:50 ` Alan J. Wylie
2004-12-13 11:09 ` Jeff Garzik
2004-12-13 12:11 ` Alan J. Wylie
2005-02-19 17:33 ` Jeff Garzik
2005-02-19 17:41 ` Alan J. Wylie
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=16828.26244.409792.573084@devnull.wylie.me.uk \
--to=alan@wylie.me.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=wingman@waika9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox