From: Tony Battersby <tonyb@cybernetics.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Tejun Heo <tj@kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: AHCI problem with hotplug
Date: Tue, 20 Jan 2009 17:56:27 -0500 [thread overview]
Message-ID: <4976569B.9040206@cybernetics.com> (raw)
In-Reply-To: <496EBE98.4040103@shaw.ca>
Robert Hancock wrote:
> Tejun Heo wrote:
>
>> Hello,
>>
>> Tony Battersby wrote:
>>
>>> No luck. After "setpci -s 1f.2 92.b=7f" with the disk unplugged, lspci
>>> shows register 0x92 = 0x0f. After plugging in the disk, this changes to
>>> 0x92 = 0x1f, but still no interrupt, and still no hotplug event.
>>>
>> Aieee... I've run out of ideas then. :-(
>>
>>
>
> Tried reloading the ahci module after making that change? Maybe it needs
> an AHCI reset before it takes effect or something..
>
>
Still no luck.
boot with no drive attached
plug in drive
modprobe ahci
setpci
modprobe -r ahci
modprobe ahci
I get the following messages:
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: forcing PORTS_IMPL to 0xf
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part
ahci 0000:00:1f.2: setting latency timer to 64
scsi12 : ahci
scsi13 : ahci
scsi14 : ahci
scsi15 : ahci
ata13: SATA max UDMA/133 abar m1024@0xea000400 port 0xea000500 irq 506
ata14: SATA max UDMA/133 abar m1024@0xea000400 port 0xea000580 irq 506
ata15: SATA max UDMA/133 abar m1024@0xea000400 port 0xea000600 irq 506
ata16: SATA max UDMA/133 abar m1024@0xea000400 port 0xea000680 irq 506
ata13: SATA link down (SStatus 0 SControl 0)
ata14: SATA link down (SStatus 0 SControl 0)
ata15: SATA link down (SStatus 0 SControl 0)
ata16: SATA link down (SStatus 0 SControl 0)
Tony
next prev parent reply other threads:[~2009-01-20 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 20:32 AHCI problem with hotplug Tony Battersby
2008-12-12 16:03 ` Alan Cox
2008-12-29 8:17 ` Tejun Heo
2008-12-29 14:51 ` Tony Battersby
2008-12-29 18:29 ` Robert Hancock
2008-12-30 0:38 ` Tejun Heo
2009-01-02 3:12 ` Tejun Heo
2009-01-07 15:39 ` Tony Battersby
2009-01-08 2:06 ` Tejun Heo
2009-01-08 14:20 ` Tony Battersby
2009-01-09 0:13 ` Robert Hancock
2009-01-09 16:30 ` Tony Battersby
2009-01-14 6:33 ` Tejun Heo
2009-01-14 21:38 ` Tony Battersby
2009-01-15 1:31 ` Tejun Heo
2009-01-15 4:42 ` Robert Hancock
2009-01-20 22:56 ` Tony Battersby [this message]
2008-12-30 13:41 ` raz ben yehuda
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=4976569B.9040206@cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).