From: Jesse Barnes <jesse.barnes@intel.com>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ata_piix hang in 2.6.13-rc5
Date: Mon, 8 Aug 2005 10:20:48 -0700 [thread overview]
Message-ID: <200508081020.48945.jesse.barnes@intel.com> (raw)
I recently tried to upgrade an ICH5 based box I have to see if a PCI
resource allocation bug went away, but was stymied by the fact that
recent kernels (2.6.12 from Fedora and 2.6.13-rc5) hang when ata_piix
probes for drives. The last messages I get are these:
Loading ata_piix.ko module
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 177
ata1: SATA max UDMA/133 cmd 0xC800 ctl 0xC482 bmdma 0xC000 irq 177
ata2: SATA max UDMA/133 cmd 0xC400 ctl 0xC082 bmdma 0xC008 irq 177
ata1: SATA port has no device.
scsi0: ata_piix
ata2: dev 0 ata, max UDMA/133, 312581808 sectors, lba48
<hang>
Is this a known problem? Is there anything in particular I should try?
Thanks,
Jesse
next reply other threads:[~2005-08-08 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 17:20 Jesse Barnes [this message]
2005-08-08 18:03 ` ata_piix hang in 2.6.13-rc5 Martin Murray
2005-08-08 18:10 ` Jesse Barnes
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=200508081020.48945.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).