From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [git patches] libata ACPI support
Date: Wed, 21 Feb 2007 18:56:33 +0100 [thread overview]
Message-ID: <20070221175633.GE5143@mail.muni.cz> (raw)
In-Reply-To: <45DB88FD.5020509@garzik.org>
On Tue, Feb 20, 2007 at 06:49:17PM -0500, Jeff Garzik wrote:
> Can you narrow down the -gitX release further? i.e. does 2.6.20-git13
> perform at full speed? -git13 includes several libata changes, but does
> not include the ACPI additions.
>
> Since this is an ACPI execution error in the bug, that would tend to
> point to bad BIOS tables. But since there is a performance drop that
> does not disappear with acpi=off, there might also be another factor,
> unrelated to ACPI, at play here.
I've noticed on lkm another bug report which has pointed me to this:
ata_piix 0000:00:1f.1: version 2.00ac7
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001ffa8 irq 15
scsi0 : ata_piix
ata1.00: ATA-6: ST9100824A, 3.04, max UDMA/100
ata1.00: 195371568 sectors, multi 16: LBA48
ata1.01: ATAPI, max UDMA/33
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
Both ports are for some reason configured as UDMA/33.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2007-02-21 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 21:47 Lukas Hejtmanek
2007-02-20 22:23 ` Jeff Garzik
2007-02-20 23:26 ` Lukas Hejtmanek
2007-02-20 23:49 ` Jeff Garzik
2007-02-21 11:39 ` Lukas Hejtmanek
2007-02-21 17:56 ` Lukas Hejtmanek [this message]
2007-02-20 22:23 ` Jeff Garzik
2007-02-20 23:15 ` Lukas Hejtmanek
2007-02-21 1:20 ` Alan
-- strict thread matches above, loose matches on Subject: below --
2007-02-17 22:12 Jeff Garzik
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=20070221175633.GE5143@mail.muni.cz \
--to=xhejtman@mail.muni.cz \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®