From: Tejun Heo <htejun@gmail.com>
To: "Matías Alejandro Torres" <torresmat@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA SB600 works in 2.6.20.4 but not in 2.6.21-rc5 with irqpoll parameter
Date: Tue, 27 Mar 2007 13:13:08 +0900 [thread overview]
Message-ID: <460899D4.6070708@gmail.com> (raw)
In-Reply-To: <460896D8.8040203@gmail.com>
Hello,
Matías Alejandro Torres wrote:
>
>> Can you try with kernel parameter 'acpi=noirq' or 'irqpoll'?
> I made a typo when passing the irqpoll parameter to the kernel. In
> kernel 2.6.20.4 with the irqpoll parameter passewd to kernel the SATA
> disk works:
>
> [ 1.320000] ide: Assuming 33MHz system bus speed for PIO modes;
> override with idebus=xx
> [ 1.320000] ahci 0000:00:12.0: version 2.0
> [ 1.320000] ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level,
> low) -> IRQ 16
> [ 2.324000] ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps
> 0xf impl SATA mode
> [ 2.324000] ahci 0000:00:12.0: flags: 64bit ncq ilck pm led clo pmp
> pio slum part
> [ 2.324000] ata1: SATA max UDMA/133 cmd 0xF8824D00 ctl 0x0 bmdma 0x0
> irq 222
> [ 2.324000] ata2: SATA max UDMA/133 cmd 0xF8824D80 ctl 0x0 bmdma 0x0
> irq 222
> [ 2.324000] ata3: SATA max UDMA/133 cmd 0xF8824E00 ctl 0x0 bmdma 0x0
> irq 222
> [ 2.324000] ata4: SATA max UDMA/133 cmd 0xF8824E80 ctl 0x0 bmdma 0x0
> irq 222
> [ 2.324000] scsi0 : ahci
> [ 2.636000] ata1: SATA link down (SStatus 0 SControl 300)
> [ 2.636000] scsi1 : ahci
> [ 3.120000] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 3.136000] ata2.00: ATA-7, max UDMA/133, 160836480 sectors: LBA48
> NCQ (depth 31/32)
> [ 3.136000] ata2.00: ata2: dev 0 multi count 16
> [ 3.144000] ata2.00: configured for UDMA/133
>
[--snip--]
>
> Nice isn't it? I'm happy.
Me happy too.
> In the 2.6.21-rc5 version this hasn't worked (the typo was here too,
> copy, paste & destroy :P). Here's is the output of dmesg:
That's weird. So, with irqpoll, 2.6.21-rc5 doesn't work while 2.6.20.4
does? I looked through the changelog but nothing looks suspicious at
the first glance.
Can you try 'pci=nomsi'? At first, I though you weren't using MSI. You
apparently are.
--
tejun
next prev parent reply other threads:[~2007-03-27 4:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 2:25 SATA SB600 Matías Alejandro Torres
2007-03-27 2:31 ` Tejun Heo
2007-03-27 2:36 ` Matías Alejandro Torres
2007-03-27 2:39 ` Tejun Heo
2007-03-27 4:00 ` SATA SB600 works in 2.6.20.4 but not in 2.6.21-rc5 with irqpoll parameter Matías Alejandro Torres
2007-03-27 4:13 ` Tejun Heo [this message]
2007-03-27 4:42 ` Matías Alejandro Torres
2007-05-04 9:49 ` Tejun Heo
2007-05-04 13:45 ` Matías Alejandro Torres
2007-05-04 17:48 ` Matías Alejandro Torres
2007-05-04 18:00 ` Tejun Heo
2007-05-04 19:30 ` Matías Alejandro Torres
2007-05-04 19:36 ` Tejun Heo
2007-05-05 17:43 ` Matías Alejandro Torres
2007-05-05 17:55 ` Tejun Heo
2007-05-07 10:03 ` Tejun Heo
2007-05-07 15:12 ` Matías Alejandro Torres
2007-05-07 15:35 ` Tejun Heo
2007-05-07 20:05 ` Matías Alejandro Torres
2007-05-08 8:07 ` Tejun Heo
[not found] ` <46089F28.8060803@gmail.com>
2007-03-27 5:02 ` Tejun Heo
2007-04-13 5:26 ` Tejun Heo
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=460899D4.6070708@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=torresmat@gmail.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;
as well as URLs for NNTP newsgroup(s).