Tejun Heo wrote:
Hmm... this is difficult. The problem is that everything looks normal
until command is issued. My primary suspect still is ahci powering down
phy during initialization. Can you please test the attached patch again?
No significant difference that I can tell. I've attached t
Testing the new libata ICH PATA drivers. There's one PATA port on this
chip, and I've got two optical drives connected to it. The master drive
fails to detect. The slave detects and works properly.
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
Controller (rev 01) (prog-if 8
Tejun Heo wrote:
> Berck E. Nash wrote:
>> [ 68.242305] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> [ 98.221334] ata2.00: qc timeout (cmd 0xec)
>> [ 98.225467] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
>> [ 108.063137] ata2: port is
Tejun Heo wrote:
> Berck E. Nash wrote:
>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>> chip, and I've got two optical drives connected to it. The master drive
>> fails to detect. The slave detects and works properly.
>
> Can
Tejun Heo wrote:
> Hello, Berck.
>
> Berck E. Nash wrote:
>> Tejun Heo wrote:
>>> Berck E. Nash wrote:
>>>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>>>> chip, and I've got two optical drives connected
Tejun Heo wrote:
>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>> chip, and I've got two optical drives connected to it. The master drive
>> fails to detect. The slave detects and works properly.
> Can you test 2.6.20.1 and post full dmesg?
Here's
Tejun Heo wrote:
> Hello, Berck.
>
> Berck E. Nash wrote:
>> Tejun Heo wrote:
>>> Berck E. Nash wrote:
>>>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>>>> chip, and I've got two optical drives connected
Tejun Heo wrote:
> Please test this one instead. Thanks.
Yup, the second patch fixes it.
-Berck
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Tejun Heo wrote:
>>>>> Berck E. Nash wrote:
>>>>>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>>>>>> chip, and I've got two optical drives connected to it. The master drive
>>>>>> fails to
Tejun Heo wrote:
> Hmmm... Once properly initialized, ahci is highly unlikely to cause
> runaway IRQs which results in nobody cared. It has proper IRQ mask and
> pending bits allowing the driver to reliably detect when and why the
> controller is raising interrupt and disable it if necessary. Ca
Jeff Garzik wrote:
> The first step would be to clone the "upstream" branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> and see if the problem is reproducible there. If yes, then you have
> narrowed down the problem to something my ATA devel tree has introduced
Jens Axboe wrote:
> On Tue, Sep 25 2007, Berck E. Nash wrote:
>> Jeff Garzik wrote:
>>
>>> The first step would be to clone the "upstream" branch of
>>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>>>
>>> and see
Jeff Garzik wrote:
> Once the blame has been squared fixed upon me :) you can use git-bisect
> to locate the precise change that broke your setup.
Okay, here's the problem:
268fe6f9f15551be9abedd44a237392675d529d5 is first bad commit
commit 268fe6f9f15551be9abedd44a237392675d529d5
Author: Jeff Ga
Jeff Garzik wrote:
> Can you tell me something about this device?
>
> [ 49.045635] ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133
> [ 49.051677] ata2.00: 640 sectors, multi 1: LBA
> [ 49.056321] ata2.00: configured for UDMA/133
>
> It seems like it does not support the 'check power mo
Berck E. Nash wrote:
> hdparm output attached.
Whoops, it really is this time.
/dev/sde:
427a 3fff 0010 e100 0258 003f
000e 5744 2d57 4d41 4b48 3131 3235
3131 3700 0003 4000 004a 3331
2e30 3846 3331 5744 4320 5744 3336 3047
442d 3030 464c 4132 2020 2020 2020 2020
2
Jeff Garzik wrote:
> Would it also be possible for you to send along 'hdparm --Istdout'
> output for your config disk thingy, /dev/sdd ?
Sure, just don't ask me what it is! (I've generally assumed that
writing to it would be a bad idea.)
Berck
/dev/sdd:
0040 3fff c837 0010 003f
0
Bernd Schmidt wrote:
> One of these appears in my system as well (ASUS P5W-DH Deluxe
> mainboard). Here's the hdparm output:
Yup, same mainboard here.
> Since about 2.6.17 or 2.6.18, it has been causing long delays while
> booting:
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.
17 matches
Mail list logo
