LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg Trounson <gregt@maths.otago.ac.nz>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AHCI - remove probing of ata2
Date: Thu, 15 Feb 2007 10:43:56 +1300	[thread overview]
Message-ID: <45D3829C.8050302@maths.otago.ac.nz> (raw)
In-Reply-To: <45D34B47.5090005@tmr.com>

Bill Davidsen wrote:
> Greg Trounson wrote:
>> At the risk of sounding like a "me too" post:
>>
>> I also have an Asus P5W-DH, with the following drives connected:
>>
>> SATA: ST3250820AS, connected to sata1
>> PATA: HL-DT-ST GSA-H12N, ATAPI DVD Writer, Primary master
>>
>> On bootup of 2.6.19 and 2.6.20, the kernel stalls for 1 minute when 
>> probing sata2, eventually giving up and continuing the boot process.  
>> There is no physical sata2 connector on the Motherboard, just solder 
>> lugs between sata1 and sata3.  From other users I understand this is 
>> really a Silicon Image SIL4723 SATA to 2-Port SATA splitter.  It is 
>> detected by the kernel as a disk, as below.
>>
>> The relevant part of the boot process looks like:
>> ...
>> libata version 2.00 loaded.
>> ahci 0000:00:1f.2: version 2.0
>> ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 23 (level, low) -> IRQ 22
>> PCI: Setting latency timer of device 0000:00:1f.2 to 64
>> 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 led clo pio slum part
>> ata1: SATA max UDMA/133 cmd 0xF882A900 ctl 0x0 bmdma 0x0 irq 219
>> ata2: SATA max UDMA/133 cmd 0xF882A980 ctl 0x0 bmdma 0x0 irq 219
>> ata3: SATA max UDMA/133 cmd 0xF882AA00 ctl 0x0 bmdma 0x0 irq 219
>> ata4: SATA max UDMA/133 cmd 0xF882AA80 ctl 0x0 bmdma 0x0 irq 219
>> scsi0 : ahci
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 31/32)
>> ata1.00: ata1: dev 0 multi count 16
>> ata1.00: configured for UDMA/133
>> scsi1 : ahci
>> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>
>> ...waits 20 seconds...
>>
>> ata2.00: qc timeout (cmd 0xec)
>> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
>>
>> ...waits 5 seconds...
>>
>> ata2: port is slow to respond, please be patient (Status 0x80)
>>
>> ...waits 30 seconds...
>>
>> ata2: port failed to respond (30 secs, Status 0x80)
>> ata2: COMRESET failed (device not ready)
>> ata2: hardreset failed, retrying in 5 secs
>>
>> ...waits 5 seconds...
>>
>> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
>> ata2.00: ata2: dev 0 multi count 1
>> ata2.00: configured for UDMA/133
>> scsi2 : ahci
>> ata3: SATA link down (SStatus 0 SControl 300)
>> ...
>>
>> A bit of poking about shows:
>>
>> fdisk -l /dev/sdb
>> Disk /dev/sdb: 0 MB, 327680 bytes
>> 255 heads, 63 sectors/track, 0 cylinders
>> Units = cylinders of 16065 * 512 = 8225280 bytes
>> Disk /dev/sdb doesn't contain a valid partition table
>>
>> So it presents itself as a 320k disk, filled with zeroes as below:
>>
>> dd if=/dev/sdb |hexdump
>> 0000000 0000 0000 0000 0000 0000 0000 0000 0000
>> *
>> 0050000
>>
>> 640+0 records in
>> 640+0 records out
>> 327680 bytes (328 kB) copied, 0.0106662 seconds, 30.7 MB/s
>>
...
> Is this 320k of cache memory, or in any way some actual storage on the 
> system? Have you tried to write to it out of curiosity? Seems odd that 
> it would be detected if there were nothing at all present, although 
> obviously it could be artifact.

According to the product outline at 
http://www.siliconimage.com/products/product.aspx?id=64, the Silicon Image port multiplier 
has an EEPROM of unspecified size.

With the drive appearing as precisely 320K I wouldn't be surprised if this EEPROM is what 
it was seeing.  Even though it's currently filled with zeros I dare not write to it 
through fear of bricking the controller.

Greg




  reply	other threads:[~2007-02-14 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  0:56 Greg Trounson
2007-02-14 17:47 ` Bill Davidsen
2007-02-14 21:43   ` Greg Trounson [this message]
2007-04-01 14:19 ` Håkan Lindqvist
     [not found] <fa.R5BFxVmVJj5OnAPGQI7410dt/fA@ifi.uio.no>
2007-02-10 17:20 ` Robert Hancock
2007-02-10 17:32   ` Paul Rolland
2007-02-10 18:39     ` Paul Rolland
2007-02-10 19:06       ` Alan
2007-02-10 20:01         ` Paul Rolland
2007-02-10 20:36           ` Alan
2007-02-10 21:59             ` Paul Rolland
2007-02-11 10:17               ` Paul Rolland
2007-02-12  0:53                 ` Tejun Heo
2007-02-12 11:19                   ` Paul Rolland
2007-02-13  7:33                     ` Paul Rolland
2007-02-13 20:20                       ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2007-02-10 14:24 Paul Rolland

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=45D3829C.8050302@maths.otago.ac.nz \
    --to=gregt@maths.otago.ac.nz \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: AHCI - remove probing of ata2' \
    /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

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).