public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata: 2.6.7-bk6,12 hang with ata_piix in combined mode; -bk5 ok
Date: Sun, 04 Jul 2004 14:03:23 -0400	[thread overview]
Message-ID: <40E8466B.9000702@pobox.com> (raw)
In-Reply-To: <20040630005420.GA4163@ti64.telemetry-investments.com>

Bill Rugolsky Jr. wrote:
> Jeff,
> 
> I have a Dell Poweredge 750 with a pair of Maxtor 250GB SATA drives
> running Fedora Core 1 + upgrades to support 2.6.
> 
> The Dell BIOS configures the controller in combined mode.
> Kernel 2.6.7-bk5 boots, while 2.6.7-bk6,bk12 generate the following
> timeout (copied by hand):
> 
> ata_piix: combined mode detected
> ACPI: PCI interrupt 0000:1f.2[A]: no GSI
> ata: 0x1f0 IDE port busy
> ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFEA8 irq 15
> ata1: dev 0 ATA, max UDMA/133 488281250 sectors: lba48
> ata1: dev 1 ATA, max UDMA/133 488281250 sectors: lba48
> ata1: dev0 configured for UDMA/133
> ata1: dev1 configured for UDMA/133
> scsi0: ata_piix
>   Vendor: ATA      Model: Maxtor 7Y250M0    Rev: YAR5
>   Type: Direct Access                       ANSI SCSI revision: 05
> SCSI device sda: 488281250 512-byte hdwr sectors (250000MB)
> SCSI device sda: drive cache: write back
>  sda:<3>ata1: command 0x25 timeout, stat 0xd0 host_stat 0x64


If "acpi=off" does not fix this, please test the patch I posted recently
	[PATCH,RFT] SATA interrupt handling



  parent reply	other threads:[~2004-07-04 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30  0:54 libata: 2.6.7-bk6,12 hang with ata_piix in combined mode; -bk5 ok Bill Rugolsky Jr.
2004-06-30  1:20 ` Jeff Garzik
2004-06-30 15:56   ` Bill Rugolsky Jr.
2004-06-30 18:02     ` Jeff Garzik
2004-07-04 18:03 ` Jeff Garzik [this message]
2004-07-05  1:34   ` Bill Rugolsky Jr.
     [not found] <A6974D8E5F98D511BB910002A50A6647615FF44B@hdsmsx403.hd.intel.com>
2004-07-05 20:39 ` Len Brown

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=40E8466B.9000702@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=brugolsky@telemetry-investments.com \
    --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