Skip to contentSkip to conversation

FYI: SATA on x86-64

DISCUSSION Jeff Garzik 2 participants 3 messages Mar 19, 2004 libata

lore
Share & tools
lore
#0 lore raw

There appear to be a variety of platform problems that lead to trouble with libata (and also with the IDE driver to some extent), with the default x86-64 kernel + some buggy BIOSes + some iommu weirdness.

Here are some boot options to mix and match:
nomce, iommu=off, noapic, acpi=off

And also try using an SMP kernel (CONFIG_SMP) rather than a uniprocessor one.

Jeff

#1 lore raw
Quoted 7 lines · Jeff Garzik

There appear to be a variety of platform problems that lead to trouble with libata (and also with the IDE driver to some extent), with the default x86-64 kernel + some buggy BIOSes + some iommu weirdness.

Here are some boot options to mix and match:
nomce, iommu=off, noapic, acpi=off

And also try using an SMP kernel (CONFIG_SMP) rather than a uniprocessor one.

You have any special place where one or several options might be useful?

I stressed the promise sata on my ASUS K8V with a Maxtor disk yesterday and it worked just fine. Under 2.4 that is. And yes, running an x86_64 kernel.

// Stefan

#2 lore raw
Quoted 8 lines · Stefan Smietanowski
Quoted 6 lines · Jeff Garzik

There appear to be a variety of platform problems that lead to trouble with libata (and also with the IDE driver to some extent), with the default x86-64 kernel + some buggy BIOSes + some iommu weirdness.

Here are some boot options to mix and match:
nomce, iommu=off, noapic, acpi=off

Quoted 8 lines
Quoted 1 line

And also try using an SMP kernel (CONFIG_SMP) rather than a uniprocessor one.

You have any special place where one or several options might be useful?

I stressed the promise sata on my ASUS K8V with a Maxtor disk yesterday and it worked just fine. Under 2.4 that is. And yes, running an x86_64 kernel.

If you don't need any of those options, then no worries. You are fine as-is.

Jeff