Unknown SATA PIIX PCI device ID 0x29b6

Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

Hi

just found out that the eSATA connector on my Intel DQ35JO motherboard 
doesn't work... because it is connected to the controller with product ID 
29b6... And this ID is not yet handled by the driver. Can I have a patch, 
please?:-) I think the correct entry would be

{ 0x8086, 0x29b6, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_2port_sata },

just because it also has two ports. Am I right? I would rather not test 
blindly.

BTW, why are these 2920, 2926, and 29b6 IDs not handled by the ahci 
driver? The board-manual does say ICH9...

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Alan Cox]

On Thu, 28 Feb 2008 23:37:36 +0100 (CET)
Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:

> Hi
> 
> just found out that the eSATA connector on my Intel DQ35JO motherboard 
> doesn't work... because it is connected to the controller with product ID 
> 29b6... And this ID is not yet handled by the driver. Can I have a patch, 
> please?:-) I think the correct entry would be

If the device is in AHCI mode it should match the ahci class entry - is
the device in AHCI mode or PIIX mode ?

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Thu, 28 Feb 2008, Alan Cox wrote:

> On Thu, 28 Feb 2008 23:37:36 +0100 (CET)
> Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> 
> > Hi
> > 
> > just found out that the eSATA connector on my Intel DQ35JO motherboard 
> > doesn't work... because it is connected to the controller with product ID 
> > 29b6... And this ID is not yet handled by the driver. Can I have a patch, 
> > please?:-) I think the correct entry would be
> 
> If the device is in AHCI mode it should match the ahci class entry - is
> the device in AHCI mode or PIIX mode ?

Indeed! It was in "IDE" mode, and 2 out of the 3 chips were handled by the 
piix driver (btw, why did Intel put 3 different SATA controllers on one 
board?). I switched it to AHCI mode (the third possibility is RAID) and 
indeed a kernel with (only) ahci driver managed to bring them up! 
Although, the eSATA link was "slow to respond":

ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
ata4.00: 312581808 sectors, multi 16: LBA48
ata4.00: applying bridge limits
ata4.00: configured for UDMA/100

but then it did manage it. Is such a delay normal?

One more question, what do UDMA numbers mean in SATA context? The internal 
SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Guennadi Liakhovetski wrote:
> Indeed! It was in "IDE" mode, and 2 out of the 3 chips were handled by the 
> piix driver (btw, why did Intel put 3 different SATA controllers on one 
> board?). I switched it to AHCI mode (the third possibility is RAID) and 
> indeed a kernel with (only) ahci driver managed to bring them up! 
> Although, the eSATA link was "slow to respond":
> 
> ata4: port is slow to respond, please be patient (Status 0x80)
> ata4: softreset failed (device not ready)
> ata4: port is slow to respond, please be patient (Status 0x80)
> ata4: softreset failed (device not ready)
> ata4: port is slow to respond, please be patient (Status 0x80)
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
> ata4.00: 312581808 sectors, multi 16: LBA48
> ata4.00: applying bridge limits
> ata4.00: configured for UDMA/100
> 
> but then it did manage it. Is such a delay normal?

If you hotplugged it, sometimes drives don't respond too well and takes
a few retries to talk to it.  How long did the whole thing take?  And is
it always like that?

> One more question, what do UDMA numbers mean in SATA context? The internal 
> SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.

1.00 is port 1 device 00 and UDMA numbers don't mean much to SATA devices.

Thanks.

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Thu, 6 Mar 2008, Tejun Heo wrote:

> Guennadi Liakhovetski wrote:
> > Indeed! It was in "IDE" mode, and 2 out of the 3 chips were handled by the 
> > piix driver (btw, why did Intel put 3 different SATA controllers on one 
> > board?). I switched it to AHCI mode (the third possibility is RAID) and 
> > indeed a kernel with (only) ahci driver managed to bring them up! 
> > Although, the eSATA link was "slow to respond":
> > 
> > ata4: port is slow to respond, please be patient (Status 0x80)
> > ata4: softreset failed (device not ready)
> > ata4: port is slow to respond, please be patient (Status 0x80)
> > ata4: softreset failed (device not ready)
> > ata4: port is slow to respond, please be patient (Status 0x80)
> > ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> > ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
> > ata4.00: 312581808 sectors, multi 16: LBA48
> > ata4.00: applying bridge limits
> > ata4.00: configured for UDMA/100
> > 
> > but then it did manage it. Is such a delay normal?
> 
> If you hotplugged it, sometimes drives don't respond too well and takes
> a few retries to talk to it.

I've seen this messages both on cold- and hot-plug.

> How long did the whole thing take?

Here's a hot-plug log:

Mar  4 15:04:28 6a kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xa frozen
Mar  4 15:04:28 6a kernel: ata4: irq_stat 0x00000040, connection status changed
Mar  4 15:04:28 6a kernel: ata4: SError: { PHYRdyChg CommWake DevExch }Mar  4 15:04:28 6a kernel: ata4: hard resetting link
Mar  4 15:04:38 6a kernel: ata4: softreset failed (device not ready)
Mar  4 15:04:38 6a kernel: ata4: hard resetting link
Mar  4 15:04:48 6a kernel: ata4: softreset failed (device not ready)
Mar  4 15:04:48 6a kernel: ata4: hard resetting link
Mar  4 15:04:55 6a kernel: ata4: port is slow to respond, please be patient (Status 0x80)
Mar  4 15:05:20 6a kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar  4 15:05:20 6a kernel: ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
Mar  4 15:05:20 6a kernel: ata4.00: 312581808 sectors, multi 0: LBA48
Mar  4 15:05:20 6a kernel: ata4.00: applying bridge limits
Mar  4 15:05:20 6a kernel: ata4.00: configured for UDMA/100
Mar  4 15:05:20 6a kernel: ata4: EH complete
Mar  4 15:05:20 6a kernel: scsi 3:0:0:0: Direct-Access     ATA      WDC WD1600BB-00R 20.0 PQ: 0 ANSI: 5
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  4 15:05:20 6a kernel:  sdb: sdb1 sdb2
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
Mar  4 15:05:20 6a kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0

Looks like almost a minute to me? On another occurence I see about 1.5 
minutes, then "port is slow to respond, please be patient (Status 0x80)" 
has been repeated 3 times. On cold-plug also 3 times, I think, about the 
same time then (time is not updated in the log).

> And is it always like that?

So far - yes.

> > One more question, what do UDMA numbers mean in SATA context? The internal 
> > SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.
> 
> 1.00 is port 1 device 00 and UDMA numbers don't mean much to SATA devices.

Sorry, I actually meant to ask what "UDMA/133" means for a SATA link?

Thanks
Guennadi
---
Guennadi Liakhovetski

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

 

>-----Original Message-----
>From: linux-ide-owner@vger.kernel.org 
>[mailto:linux-ide-owner@vger.kernel.org] On Behalf Of Guennadi 
>Liakhovetski
>Sent: Thursday, March 06, 2008 3:58 AM
>To: Tejun Heo
>Cc: Alan Cox; linux-kernel@vger.kernel.org; Jeff Garzik; 
>linux-ide@vger.kernel.org
>Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
>
>On Thu, 6 Mar 2008, Tejun Heo wrote:
>
>> Guennadi Liakhovetski wrote:
>> > Indeed! It was in "IDE" mode, and 2 out of the 3 chips 
>were handled by the 
>> > piix driver (btw, why did Intel put 3 different SATA 
>controllers on one 
>> > board?). I switched it to AHCI mode (the third possibility 
>is RAID) and 
>> > indeed a kernel with (only) ahci driver managed to bring them up! 
>> > Although, the eSATA link was "slow to respond":
>> > 
>> > ata4: port is slow to respond, please be patient (Status 0x80)
>> > ata4: softreset failed (device not ready)
>> > ata4: port is slow to respond, please be patient (Status 0x80)
>> > ata4: softreset failed (device not ready)
>> > ata4: port is slow to respond, please be patient (Status 0x80)
>> > ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> > ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
>> > ata4.00: 312581808 sectors, multi 16: LBA48
>> > ata4.00: applying bridge limits
>> > ata4.00: configured for UDMA/100
>> > 
>> > but then it did manage it. Is such a delay normal?
>> 
>> If you hotplugged it, sometimes drives don't respond too 
>well and takes
>> a few retries to talk to it.
>
>I've seen this messages both on cold- and hot-plug.
>
>> How long did the whole thing take?
>
>Here's a hot-plug log:
>
>Mar  4 15:04:28 6a kernel: ata4: exception Emask 0x10 SAct 0x0 
>SErr 0x4050000 action 0xa frozen
>Mar  4 15:04:28 6a kernel: ata4: irq_stat 0x00000040, 
>connection status changed
>Mar  4 15:04:28 6a kernel: ata4: SError: { PHYRdyChg CommWake 
>DevExch }Mar  4 15:04:28 6a kernel: ata4: hard resetting link
>Mar  4 15:04:38 6a kernel: ata4: softreset failed (device not ready)
>Mar  4 15:04:38 6a kernel: ata4: hard resetting link
>Mar  4 15:04:48 6a kernel: ata4: softreset failed (device not ready)
>Mar  4 15:04:48 6a kernel: ata4: hard resetting link
>Mar  4 15:04:55 6a kernel: ata4: port is slow to respond, 
>please be patient (Status 0x80)
>Mar  4 15:05:20 6a kernel: ata4: SATA link up 3.0 Gbps 
>(SStatus 123 SControl 300)
>Mar  4 15:05:20 6a kernel: ata4.00: ATA-7: WDC 
>WD1600BB-00RDA0, 20.00K20, max UDMA/100
>Mar  4 15:05:20 6a kernel: ata4.00: 312581808 sectors, multi 0: LBA48
>Mar  4 15:05:20 6a kernel: ata4.00: applying bridge limits
>Mar  4 15:05:20 6a kernel: ata4.00: configured for UDMA/100
>Mar  4 15:05:20 6a kernel: ata4: EH complete
>Mar  4 15:05:20 6a kernel: scsi 3:0:0:0: Direct-Access     ATA 
>     WDC WD1600BB-00R 20.0 PQ: 0 ANSI: 5
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 
>512-byte hardware sectors (160042 MB)
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: 
>enabled, read cache: enabled, doesn't support DPO or FUA
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 
>512-byte hardware sectors (160042 MB)
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: 
>enabled, read cache: enabled, doesn't support DPO or FUA
>Mar  4 15:05:20 6a kernel:  sdb: sdb1 sdb2
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
>Mar  4 15:05:20 6a kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
>
>Looks like almost a minute to me? On another occurence I see about 1.5 
>minutes, then "port is slow to respond, please be patient 
>(Status 0x80)" 
>has been repeated 3 times. On cold-plug also 3 times, I think, 
>about the 
>same time then (time is not updated in the log).
>
>> And is it always like that?
>
>So far - yes.
>
>> > One more question, what do UDMA numbers mean in SATA 
>context? The internal 
>> > SATA disk is "ata1.00: configured for UDMA/133", but 
>should be SATA-2.
>> 
>> 1.00 is port 1 device 00 and UDMA numbers don't mean much to 
>SATA devices.
>
>Sorry, I actually meant to ask what "UDMA/133" means for a SATA link?
>
>Thanks
>Guennadi
>---
>Guennadi Liakhovetski
>--
>To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

If you disable the IDE Redirection in BIOS on that system, the 0x29b6
controller should not appear.  If you are not using this, it would be
interesting to see if this effects what you are seeing.

Jason

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Jeff Garzik]

Gaston, Jason D wrote:
> If you disable the IDE Redirection in BIOS on that system, the 0x29b6
> controller should not appear.  If you are not using this, it would be
> interesting to see if this effects what you are seeing.


I think its fair to say that a certain amount of Linux users will 
inevitably have this option enabled in their BIOS.  We should have a 
plan to deal with this sanely...?

	Jeff

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Thu, 6 Mar 2008, Jeff Garzik wrote:

> Gaston, Jason D wrote:
> > If you disable the IDE Redirection in BIOS on that system, the 0x29b6
> > controller should not appear.  If you are not using this, it would be
> > interesting to see if this effects what you are seeing.
> 
> I think its fair to say that a certain amount of Linux users will inevitably
> have this option enabled in their BIOS.  We should have a plan to deal with
> this sanely...?

Sorry, I am afraid, I caused a bit of confusion here. 0x29b6 I had when 
BIOS configuration was set to "IDE". Then I couldn't use the 0x29b6 at 
all, and therefore couldn't access the external eSATA disk at all. Then I 
switched to AHCI, now all SATA hosts are on PCI ID 0x2922 and 0x29b6 is 
also there as an IDE host unused...

So, now BIOS is set to "AHCI", all SATA hosts - internal and external are 
on PCI ID 0x2922, and external needs a minute to start up, but then it 
works fine.

Thanks
Guennadi
---
Guennadi Liakhovetski

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

>Gaston, Jason D wrote:
>> If you disable the IDE Redirection in BIOS on that system, the 0x29b6
>> controller should not appear.  If you are not using this, it would be
>> interesting to see if this effects what you are seeing.
>
>
>I think its fair to say that a certain amount of Linux users will 
>inevitably have this option enabled in their BIOS.  We should have a 
>plan to deal with this sanely...?
>
>	Jeff

I was able to add the IDER Contoller DeviceID to ata_generic.c and it
seemed to work fine.  I was also able to add it to ata_piix.c as a SATA
Controler and it seemed to work ok as well.  However, when I tried to
add it to ata_piix.c as a PATA Controller if failed cable detection.  I
guess this would be expected as it is a Virtual IDE contoller.

Where is the correct place to add support for IDE Redirection
Contollers?

Thanks,

Jason

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Gaston, Jason D wrote:
>> Gaston, Jason D wrote:
>>> If you disable the IDE Redirection in BIOS on that system, the 0x29b6
>>> controller should not appear.  If you are not using this, it would be
>>> interesting to see if this effects what you are seeing.
>>
>> I think its fair to say that a certain amount of Linux users will 
>> inevitably have this option enabled in their BIOS.  We should have a 
>> plan to deal with this sanely...?
> 
> I was able to add the IDER Contoller DeviceID to ata_generic.c and it
> seemed to work fine.  I was also able to add it to ata_piix.c as a SATA
> Controler and it seemed to work ok as well.  However, when I tried to
> add it to ata_piix.c as a PATA Controller if failed cable detection.  I
> guess this would be expected as it is a Virtual IDE contoller.
> 
> Where is the correct place to add support for IDE Redirection
> Contollers?

What's IDE redirection?  SATA appearing as IDE?

-- 
tejun

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

>>> Gaston, Jason D wrote:
>>>> If you disable the IDE Redirection in BIOS on that system, 
>the 0x29b6
>>>> controller should not appear.  If you are not using this, 
>it would be
>>>> interesting to see if this effects what you are seeing.
>>>
>>> I think its fair to say that a certain amount of Linux users will 
>>> inevitably have this option enabled in their BIOS.  We 
>should have a 
>>> plan to deal with this sanely...?
>> 
>> I was able to add the IDER Contoller DeviceID to ata_generic.c and it
>> seemed to work fine.  I was also able to add it to 
>ata_piix.c as a SATA
>> Controler and it seemed to work ok as well.  However, when I tried to
>> add it to ata_piix.c as a PATA Controller if failed cable 
>detection.  I
>> guess this would be expected as it is a Virtual IDE contoller.
>> 
>> Where is the correct place to add support for IDE Redirection
>> Contollers?
>
>What's IDE redirection?  SATA appearing as IDE?
>
>-- 
>tejun

IDER is a controller, in this case, in the MCH/Northbridge that
redirects a virtual drive across the LAN and presents it as a local IDE
drive.  This is part of the Intel AMT managability engine.  You can
point it to a physical drive, .iso or a .img file on the remote system.

Thanks,

Jason

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Gaston, Jason D wrote:
> IDER is a controller, in this case, in the MCH/Northbridge that
> redirects a virtual drive across the LAN and presents it as a local IDE
> drive.  This is part of the Intel AMT managability engine.  You can
> point it to a physical drive, .iso or a .img file on the remote system.

Ah... fancy.  You can just make it PATA if doesn't have SCR access and 
supports slave device and use ata_cable_unknown() for ->cbl_detect.

-- 
tejun

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

>> IDER is a controller, in this case, in the MCH/Northbridge that
>> redirects a virtual drive across the LAN and presents it as 
>a local IDE
>> drive.  This is part of the Intel AMT manageability engine.  You can
>> point it to a physical drive, .iso or a .img file on the 
>remote system.
>
>Ah... fancy.  You can just make it PATA if doesn't have SCR access and 
>supports slave device and use ata_cable_unknown() for ->cbl_detect.
>
>-- 
>tejun
>

After messing around for a bit, what I came up with that worked, was
very similar to what it set for ich8_sata_ahci.  So, I tried just adding
the new DeviceID as an ich8_sata_ahci and it seems to work fine.  Do you
see anything wrong with just doing this?  I'm not sure that the port map
is relevant for a virtual device?  I have attached the dmesg output for
your review.

Thanks,

Jason

[-- Attachment #2: ider_as_ich8sata_dmesg.txt --]
[-- Type: text/plain, Size: 36578 bytes --]

Linux version 2.6.25-rc8_ider_ata_piix (root@localhost.localdomain) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #12 SMP Fri Apr 18 17:32:51 PDT 2008
Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007bf90000 (usable)
 BIOS-e820: 000000007bf90000 - 000000007c003000 (ACPI NVS)
 BIOS-e820: 000000007c003000 - 000000007d1ca000 (usable)
 BIOS-e820: 000000007d1ca000 - 000000007d1cc000 (reserved)
 BIOS-e820: 000000007d1cc000 - 000000007d27b000 (usable)
 BIOS-e820: 000000007d27b000 - 000000007d2ce000 (ACPI NVS)
 BIOS-e820: 000000007d2ce000 - 000000007d2de000 (usable)
 BIOS-e820: 000000007d2de000 - 000000007d2e5000 (ACPI NVS)
 BIOS-e820: 000000007d2e5000 - 000000007d2e8000 (usable)
 BIOS-e820: 000000007d2e8000 - 000000007d2f3000 (ACPI data)
 BIOS-e820: 000000007d2f3000 - 000000007d2f4000 (usable)
 BIOS-e820: 000000007d2f4000 - 000000007d2ff000 (ACPI data)
 BIOS-e820: 000000007d2ff000 - 000000007d300000 (usable)
 BIOS-e820: 000000007d300000 - 000000007e000000 (reserved)
 BIOS-e820: 00000000f0000000 - 00000000f8000000 (reserved)
 BIOS-e820: 00000000ffc00000 - 0000000100000000 (reserved)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 507792) 1 entries of 3200 used
Entering add_active_range(0, 507907, 512458) 2 entries of 3200 used
Entering add_active_range(0, 512460, 512635) 3 entries of 3200 used
Entering add_active_range(0, 512718, 512734) 4 entries of 3200 used
Entering add_active_range(0, 512741, 512744) 5 entries of 3200 used
Entering add_active_range(0, 512755, 512756) 6 entries of 3200 used
Entering add_active_range(0, 512767, 512768) 7 entries of 3200 used
end_pfn_map = 1048576
DMI 2.4 present.
ACPI: RSDP 000FE020, 0014 (r0 INTEL )
ACPI: RSDT 7D2FD038, 0068 (r1 INTEL  DQ3510J       33F       1000013)
ACPI: FACP 7D2FC000, 0074 (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: DSDT 7D2F8000, 3D3A (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: FACS 7D287000, 0040
ACPI: APIC 7D2F7000, 0078 (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: WDDT 7D2F6000, 0040 (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: MCFG 7D2F5000, 003C (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: ASF! 7D2F4000, 00A6 (r32 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: ASPT 7D2F2000, 002C (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: WDTT 7D2F1000, 02CC (r1 INTEL  DQ3510J       33F MSFT  1000013)
ACPI: SSDT 7D2F0000, 0204 (r1 INTEL     CpuPm      33F MSFT  1000013)
ACPI: SSDT 7D2EF000, 01F9 (r1 INTEL   Cpu0Ist      33F MSFT  1000013)
ACPI: SSDT 7D2EE000, 01F9 (r1 INTEL   Cpu1Ist      33F MSFT  1000013)
ACPI: SSDT 7D2ED000, 01F9 (r1 INTEL   Cpu2Ist      33F MSFT  1000013)
ACPI: SSDT 7D2EC000, 01F9 (r1 INTEL   Cpu3Ist      33F MSFT  1000013)
ACPI: SSDT 7D2EB000, 00DD (r1 INTEL   Cpu0Cst      33F MSFT  1000013)
ACPI: SSDT 7D2EA000, 00DD (r1 INTEL   Cpu1Cst      33F MSFT  1000013)
ACPI: SSDT 7D2E9000, 00DD (r1 INTEL   Cpu2Cst      33F MSFT  1000013)
ACPI: SSDT 7D2E8000, 00DD (r1 INTEL   Cpu3Cst      33F MSFT  1000013)
ACPI: TCPA 7D27B000, 0032 (r2 INTEL  TIANO           2 MSFT  1000013)
No NUMA configuration found
Faking a node at 0000000000000000-000000007d300000
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 507792) 1 entries of 3200 used
Entering add_active_range(0, 507907, 512458) 2 entries of 3200 used
Entering add_active_range(0, 512460, 512635) 3 entries of 3200 used
Entering add_active_range(0, 512718, 512734) 4 entries of 3200 used
Entering add_active_range(0, 512741, 512744) 5 entries of 3200 used
Entering add_active_range(0, 512755, 512756) 6 entries of 3200 used
Entering add_active_range(0, 512767, 512768) 7 entries of 3200 used
Bootmem setup node 0 0000000000000000-000000007d300000
  NODE_DATA [000000000000c000 - 0000000000013fff]
  bootmap [0000000000014000 -  0000000000023a5f] pages 10
early res: 0 [0-fff] BIOS data page
early res: 1 [6000-7fff] SMP_TRAMPOLINE
early res: 2 [200000-719deb] TEXT DATA BSS
early res: 3 [37c25000-37fefaf9] RAMDISK
early res: 4 [9f800-a07ff] EBDA
early res: 5 [8000-bfff] PGTABLE
 [ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
 [ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
 [ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
 [ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
 [ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
 [ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
 [ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
 [ffffe20000e00000-ffffe20000ffffff] PMD ->ffff810002e00000 on node 0
 [ffffe20001000000-ffffe200011fffff] PMD ->ffff810003200000 on node 0
 [ffffe20001200000-ffffe200013fffff] PMD ->ffff810003600000 on node 0
 [ffffe20001400000-ffffe200015fffff] PMD ->ffff810003a00000 on node 0
 [ffffe20001600000-ffffe200017fffff] PMD ->ffff810003e00000 on node 0
 [ffffe20001800000-ffffe200019fffff] PMD ->ffff810004200000 on node 0
 [ffffe20001a00000-ffffe20001bfffff] PMD ->ffff810004600000 on node 0
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1048576
Movable zone start PFN for each node
early_node_map[8] active PFN ranges
    0:        0 ->      159
    0:      256 ->   507792
    0:   507907 ->   512458
    0:   512460 ->   512635
    0:   512718 ->   512734
    0:   512741 ->   512744
    0:   512755 ->   512756
    0:   512767 ->   512768
On node 0 totalpages: 512442
  DMA zone: 56 pages used for memmap
  DMA zone: 1315 pages reserved
  DMA zone: 2628 pages, LIFO batch:0
  DMA32 zone: 6954 pages used for memmap
  DMA32 zone: 501489 pages, LIFO batch:31
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
PM: Registered nosave memory: 000000007bf90000 - 000000007c003000
PM: Registered nosave memory: 000000007d1ca000 - 000000007d1cc000
PM: Registered nosave memory: 000000007d27b000 - 000000007d2ce000
PM: Registered nosave memory: 000000007d2de000 - 000000007d2e5000
PM: Registered nosave memory: 000000007d2e8000 - 000000007d2f3000
PM: Registered nosave memory: 000000007d2f4000 - 000000007d2ff000
Allocating PCI resources starting at 80000000 (gap: 7e000000:72000000)
SMP: Allowing 4 CPUs, 2 hotplug CPUs
PERCPU: Allocating 43760 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 504117
Policy zone: DMA32
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
time.c: Detected 2989.490 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Checking aperture...
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 2011512k/2051072k available (2453k kernel code, 38256k reserved, 1376k data, 336k init)
CPA: page pool initialized 1 of 1 pages preallocated
SLUB: Genslabs=13, HWalign=64, Order=0-1, MinObjects=4, CPUs=4, Nodes=1
Calibrating delay using timer specific routine.. 5981.27 BogoMIPS (lpj=2990638)
Security Framework initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
ACPI: Core revision 20070126
Using local APIC timer interrupts.
APIC timer calibration result 20760337
Detected 20.760 MHz APIC timer.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 6098.51 BogoMIPS (lpj=3049256)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz stepping 0b
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
CPU0 attaching sched-domain:
 domain 0: span 00000000,00000003
  groups: 00000000,00000001 00000000,00000002
  domain 1: span 00000000,00000003
   groups: 00000000,00000003
CPU1 attaching sched-domain:
 domain 0: span 00000000,00000003
  groups: 00000000,00000002 00000000,00000001
  domain 1: span 00000000,00000003
   groups: 00000000,00000003
net_namespace: 1016 bytes
NET: Registered protocol family 16
No dock devices found.
ACPI: bus type pci registered
PCI: Using MMCONFIG at f0000000 - f7ffffff
PCI: Using configuration type 1
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:1f.0: quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
PCI-GART: No AMD northbridge found.
system 00:01: iomem range 0xf0000000-0xf7ffffff could not be reserved
system 00:01: iomem range 0xfeb00000-0xfeb03fff has been reserved
system 00:01: iomem range 0xfed13000-0xfed13fff has been reserved
system 00:01: iomem range 0xfed14000-0xfed17fff has been reserved
system 00:01: iomem range 0xfed18000-0xfed18fff has been reserved
system 00:01: iomem range 0xfed19000-0xfed19fff has been reserved
system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:01: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:01: iomem range 0xfed45000-0xfed99fff has been reserved
system 00:01: iomem range 0xc0000-0xdffff has been reserved
system 00:01: iomem range 0xe0000-0xfffff could not be reserved
system 00:01: iomem range 0xffc00000-0xffffffff could not be reserved
system 00:06: ioport range 0x500-0x53f has been reserved
system 00:06: ioport range 0x400-0x47f has been reserved
system 00:06: ioport range 0x680-0x6ff has been reserved
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: 1000-1fff
  MEM window: 0x90100000-0x901fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.3
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.4
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: 0x90000000-0x900fffff
  PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1c.1 to 64
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1c.2 to 64
ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1c.3 to 64
ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.4 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 3882k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1208540314.392:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:02.0: Boot video device
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
Allocate Port Service[0000:00:1c.0:pcie03]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
Allocate Port Service[0000:00:1c.1:pcie03]
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.2:pcie00]
Allocate Port Service[0000:00:1c.2:pcie02]
Allocate Port Service[0000:00:1c.2:pcie03]
PCI: Setting latency timer of device 0000:00:1c.3 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.3:pcie00]
Allocate Port Service[0000:00:1c.3:pcie02]
Allocate Port Service[0000:00:1c.3:pcie03]
PCI: Setting latency timer of device 0000:00:1c.4 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.4:pcie00]
Allocate Port Service[0000:00:1c.4:pcie02]
Allocate Port Service[0000:00:1c.4:pcie03]
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Monitor-Mwait will be used to enter C-1 state
ACPI: ACPI0007:00 is registered as cooling_device0
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: ACPI0007:01 is registered as cooling_device1
ACPI: Processor [CPU1] (supports 8 throttling states)
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.103
agpgart: Detected an Intel Q35 Chipset.
agpgart: Detected 7164K stolen memory.
agpgart: AGP aperture is 256M @ 0x80000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt 0000:00:03.3[B] -> GSI 17 (level, low) -> IRQ 17
0000:00:03.3: ttyS1 at I/O 0x2470 (irq = 17) is a 16550A
isa bounce pool size: 16 pages
brd: module loaded
input: Macintosh mouse button emulation as /class/input/input0
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
registered taskstats version 1
Freeing unused kernel memory: 336k freed
Write protecting the kernel read-only data: 1112k
ACPI: PCI Interrupt 0000:00:1a.7[C] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1a.7 to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1a.7
ehci_hcd 0000:00:1a.7: irq 17, io mem 0x90426400
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 23, io mem 0x90426000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1a.0 to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 18, io base 0x000020c0
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1a.1 to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x000020a0
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1a.2[C] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1a.2 to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 17, io base 0x00002080
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00002060
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00002040
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00002020
usb usb8: configuration #1 chosen from 1 choice
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
SCSI subsystem initialized
Driver 'sd' needs updating - please use bus_type methods
libata version 3.00 loaded.
ata_piix 0000:00:03.2: version 2.12
ACPI: PCI Interrupt 0000:00:03.2[C] -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:03.2: MAP [ P0 P2 P1 P3 ]
usb 7-2: new low speed USB device using uhci_hcd and address 2
PCI: Setting latency timer of device 0000:00:03.2 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x2480 ctl 0x24a4 bmdma 0x2440 irq 18
ata2: SATA max UDMA/133 cmd 0x2478 ctl 0x24a0 bmdma 0x2448 irq 18
usb 7-2: configuration #1 chosen from 1 choice
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /class/input/input1
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.1-2
usb 8-2: new low speed USB device using uhci_hcd and address 2
ata1.00: ATAPI: Intel Virtual LS-120 Floppy   UHD Floppy, 1.00, max UDMA/100
ata1.00: applying bridge limits
ata1.01: ATAPI: Intel Virtual CD, 1.00, max UDMA/100
ata1.01: applying bridge limits
usb 8-2: configuration #1 chosen from 1 choice
input: NOVATEK ORTEK USB Keyboard as /class/input/input2
input: USB HID v1.00 Keyboard [NOVATEK ORTEK USB Keyboard] on usb-0000:00:1d.2-2
input: NOVATEK ORTEK USB Keyboard as /class/input/input3
input: USB HID v1.00 Mouse [NOVATEK ORTEK USB Keyboard] on usb-0000:00:1d.2-2
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
scsi 0:0:0:0: Direct-Access     Intel    Virtual Floppy   1.00 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 2880 512-byte hardware sectors (1 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 5c 24 00
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 2880 512-byte hardware sectors (1 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 5c 24 00
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI removable disk
scsi 0:0:1:0: CD-ROM            Intel    Virtual CD       1.00 PQ: 0 ANSI: 5
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 21 (level, low) -> IRQ 21
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0x2468 ctl 0x249c bmdma 0x2430 irq 21
ata4: SATA max UDMA/133 cmd 0x2460 ctl 0x2498 bmdma 0x2438 irq 21
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
ata4: SATA link down (SStatus 0 SControl 300)
scsi 2:0:0:0: Direct-Access     ATA      ST3320620AS      3.AA PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2
sd 2:0:0:0: [sdb] Attached SCSI disk
ACPI: PCI Interrupt 0000:00:1f.5[A] -> GSI 21 (level, low) -> IRQ 21
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
PCI: Setting latency timer of device 0000:00:1f.5 to 64
scsi4 : ata_piix
scsi5 : ata_piix
ata5: SATA max UDMA/133 cmd 0x2458 ctl 0x2494 bmdma 0x2410 irq 21
ata6: SATA max UDMA/133 cmd 0x2450 ctl 0x2490 bmdma 0x2418 irq 21
ata5: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
type=1404 audit(1208540324.472:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
SELinux:8192 avtab hash slots allocated. Num of rules:207815
SELinux:8192 avtab hash slots allocated. Num of rules:207815
security:  8 users, 11 roles, 2317 types, 112 bools, 1 sens, 1024 cats
security:  67 classes, 207815 rules
security:  class peer not defined in policy
security:  class capability2 not defined in policy
security:  permission recvfrom in class node not defined in policy
security:  permission sendto in class node not defined in policy
security:  permission ingress in class netif not defined in policy
security:  permission egress in class netif not defined in policy
security:  permission setfcap in class capability not defined in policy
security:  permission forward_in in class packet not defined in policy
security:  permission forward_out in class packet not defined in policy
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
SELinux: policy loaded with handle_unknown=allow
type=1403 audit(1208540324.815:3): policy loaded auid=4294967295 ses=4294967295
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:1:0: Attached scsi generic sg1 type 5
sd 2:0:0:0: Attached scsi generic sg2 type 0
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:19.0 to 64
0000:00:19.0: PHY reset is blocked due to SOL/IDER session.
eth0: (PCI Express:2.5GB/s:Width x1) 00:19:d1:ad:8d:1d
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 5, PHY: 6, PBA No: ffffff-0ff
udev: renamed network interface eth0 to eth2
ACPI: PCI Interrupt 0000:06:03.0[A] -> GSI 19 (level, low) -> IRQ 19
input: PC Speaker as /class/input/input4
firewire_ohci: Added fw-ohci device 0000:06:03.0, OHCI version 1.0
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:03:00.0 to 64
scsi6 : pata_marvell
scsi7 : pata_marvell
ata7: PATA max UDMA/100 cmd 0x1018 ctl 0x1024 bmdma 0x1000 irq 18
ata8: DUMMY
BAR5:00:00 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00 0B:00 0C:01 0D:00 0E:00 0F:00 
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 18 (level, low) -> IRQ 18
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 0x/0x tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:1:0: Attached scsi CD-ROM sr0
input: Power Button (FF) as /class/input/input5
ACPI: Power Button (FF) [PWRF]
input: Sleep Button (CM) as /class/input/input6
ACPI: Sleep Button (CM) [SLPB]
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.01: BMDMA stat 0xe5
ata1.01: cmd a0/01:00:00:fe:00/00:00:00:00:00/b0 tag 0 dma 16640 in
         cdb 12 01 00 00 fe 00 00 00  00 00 00 00 00 00 00 00
         res 78/00:02:00:00:00/00:00:00:00:00/b0 Emask 0x2 (HSM violation)
ata1.01: status: { DRDY DF DRQ }
ata1: soft resetting link
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda_codec: Unknown model for ALC268, trying auto-probe from BIOS...
firewire_core: created device fw0: GUID 0090270001e8ed76, S400
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: BMDMA stat 0xe5
ata1.00: cmd a0/01:00:00:fe:00/00:00:00:00:00/a0 tag 0 dma 16640 in
         cdb 12 01 00 00 fe 00 00 00  00 00 00 00 00 00 00 00
         res 78/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DF DRQ }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
ata1: EH complete
sd 0:0:0:0: [sda] 2880 512-byte hardware sectors (1 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 5c 24 00
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 2880 512-byte hardware sectors (1 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 5c 24 00
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
device-mapper: multipath: version 1.0.5 loaded
loop: module loaded
EXT3 FS on dm-0, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sdb1, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2031608k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
warning: process `kudzu' used the deprecated sysctl system call with 1.23.
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
ADDRCONF(NETDEV_UP): eth2: link is not ready
eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: None
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
type=1400 audit(1208565540.640:4): avc:  denied  { read write } for  pid=1837 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.640:5): avc:  denied  { read write } for  pid=1837 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.643:6): avc:  denied  { read write } for  pid=1839 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.643:7): avc:  denied  { read write } for  pid=1839 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.651:8): avc:  denied  { read write } for  pid=1841 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.651:9): avc:  denied  { read write } for  pid=1841 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.701:10): avc:  denied  { read write } for  pid=1872 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.701:11): avc:  denied  { read write } for  pid=1872 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.704:12): avc:  denied  { read write } for  pid=1874 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
type=1400 audit(1208565540.704:13): avc:  denied  { read write } for  pid=1874 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:rhgb_devpts_t:s0 tclass=chr_file
eth2: no IPv6 routers present
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
warning: `dbus-daemon' uses 32-bit capabilities (legacy support in use)
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
[drm] Initialized drm 1.1.0 20060810
PCI: Setting latency timer of device 0000:00:02.0 to 64
[drm] Initialized i915 1.6.0 20060119 on minor 0
set status page addr 0x00033000
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SELinux: initialized (dev sda, type ext2), uses xattr
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts
usb 2-5: new high speed USB device using ehci_hcd and address 4
usb 2-5: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi8 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 8:0:0:0: Direct-Access     SanDisk  U3 Titanium      2.18 PQ: 0 ANSI: 2
sd 8:0:0:0: [sdc] 4013713 512-byte hardware sectors (2055 MB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sd 8:0:0:0: [sdc] 4013713 512-byte hardware sectors (2055 MB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 8:0:0:0: [sdc] Assuming drive cache: write through
 sdc: unknown partition table
sd 8:0:0:0: [sdc] Attached SCSI removable disk
sd 8:0:0:0: Attached scsi generic sg3 type 0
SELinux: initialized (dev sdc, type vfat), uses genfs_contexts

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Gaston, Jason D wrote:
>>> IDER is a controller, in this case, in the MCH/Northbridge that
>>> redirects a virtual drive across the LAN and presents it as 
>> a local IDE
>>> drive.  This is part of the Intel AMT manageability engine.  You can
>>> point it to a physical drive, .iso or a .img file on the 
>> remote system.
>>
>> Ah... fancy.  You can just make it PATA if doesn't have SCR access and 
>> supports slave device and use ata_cable_unknown() for ->cbl_detect.
>>
>> -- 
>> tejun
>>
> 
> After messing around for a bit, what I came up with that worked, was
> very similar to what it set for ich8_sata_ahci.  So, I tried just adding
> the new DeviceID as an ich8_sata_ahci and it seems to work fine.  Do you
> see anything wrong with just doing this?  I'm not sure that the port map
> is relevant for a virtual device?  I have attached the dmesg output for
> your review.

Things look fine to me but I think it's probably best to create a 
separate port info entry for it.  Is SIDPR available for IDER too?

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Jeff Garzik]

Gaston, Jason D wrote:
> IDER is a controller, in this case, in the MCH/Northbridge that
> redirects a virtual drive across the LAN and presents it as a local IDE
> drive.  This is part of the Intel AMT managability engine.  You can
> point it to a physical drive, .iso or a .img file on the remote system.


Since this is a new, non-PATA, non-SATA controller/device setup, there 
are a few general questions,

- what to do about cable detection?  unless it matters, we could simply 
assume a fixed cable type, since its a virtual link.

- what is the proper reset method?  to kick a device (and controller) 
into action, we will COMRESET via the SATA phy, or at the very least SRST.

- is set-xfer-mode properly emulated?  normally we look at the ATA 
device's IDENTIFY DEVICE page, and choose a transfer xfer from that info.

	Jeff

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

>Gaston, Jason D wrote:
>> IDER is a controller, in this case, in the MCH/Northbridge that
>> redirects a virtual drive across the LAN and presents it as 
>a local IDE
>> drive.  This is part of the Intel AMT managability engine.  You can
>> point it to a physical drive, .iso or a .img file on the 
>remote system.
>
>
>Since this is a new, non-PATA, non-SATA controller/device setup, there 
>are a few general questions,
>
>- what to do about cable detection?  unless it matters, we 
>could simply 
>assume a fixed cable type, since its a virtual link.
>
>- what is the proper reset method?  to kick a device (and controller) 
>into action, we will COMRESET via the SATA phy, or at the very 
>least SRST.
>
>- is set-xfer-mode properly emulated?  normally we look at the ATA 
>device's IDENTIFY DEVICE page, and choose a transfer xfer from 
>that info.
>
>	Jeff

The datasheet for the Intel(3) 3 Series Chipset Family is up on
intel.com.  
Here is a direct link:
http://download.intel.com/design/chipsets/datashts/31696602.pdf  
It looks like section 9.3 has the details for the IDER.  This is
somewhat over my head, can you help me with this?

Thanks,

Jason

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]

Guennadi Liakhovetski wrote:
> Mar  4 15:04:28 6a kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xa frozen
> Mar  4 15:04:28 6a kernel: ata4: irq_stat 0x00000040, connection status changed
> Mar  4 15:04:28 6a kernel: ata4: SError: { PHYRdyChg CommWake DevExch }Mar  4 15:04:28 6a kernel: ata4: hard resetting link
> Mar  4 15:04:38 6a kernel: ata4: softreset failed (device not ready)
> Mar  4 15:04:38 6a kernel: ata4: hard resetting link
> Mar  4 15:04:48 6a kernel: ata4: softreset failed (device not ready)
> Mar  4 15:04:48 6a kernel: ata4: hard resetting link
> Mar  4 15:04:55 6a kernel: ata4: port is slow to respond, please be patient (Status 0x80)
> Mar  4 15:05:20 6a kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

That's unusually long but if you look at the last reset try.  It began
at @48 and the device comes up after 32secs without the driver taking
further action, which might indicate that the device actually took that
long.  Hmmm.. maybe it's having problem establishing link at 3Gbps.

> Looks like almost a minute to me? On another occurence I see about 1.5 
> minutes, then "port is slow to respond, please be patient (Status 0x80)" 
> has been repeated 3 times. On cold-plug also 3 times, I think, about the 
> same time then (time is not updated in the log).

I see.  Does the attached patch make any difference?

>> And is it always like that?
> 
> So far - yes.
> 
>>> One more question, what do UDMA numbers mean in SATA context? The internal 
>>> SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.
>> 1.00 is port 1 device 00 and UDMA numbers don't mean much to SATA devices.
> 
> Sorry, I actually meant to ask what "UDMA/133" means for a SATA link?

That doesn't really mean much to native SATA devices.  That's just
something we're carrying over from PATA days.

Thanks.

-- 
tejun

[-- Attachment #2: force-1.5.patch --]
[-- Type: text/x-patch, Size: 381 bytes --]

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 4fbcce7..abebdcc 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
 	spd = (scontrol >> 4) & 0xf;
 	if (spd)
 		link->hw_sata_spd_limit &= (1 << spd) - 1;
+	link->hw_sata_spd_limit = 1;
 
 	ata_force_spd_limit(link);
 

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Fri, 7 Mar 2008, Tejun Heo wrote:

> > Looks like almost a minute to me? On another occurence I see about 1.5 
> > minutes, then "port is slow to respond, please be patient (Status 0x80)" 
> > has been repeated 3 times. On cold-plug also 3 times, I think, about the 
> > same time then (time is not updated in the log).
> 
> I see.  Does the attached patch make any difference?

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 4fbcce7..abebdcc 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
 	spd = (scontrol >> 4) & 0xf;
 	if (spd)
 		link->hw_sata_spd_limit &= (1 << spd) - 1;
+	link->hw_sata_spd_limit = 1;
 
 	ata_force_spd_limit(link);
 
Hm, this would force 1.5Gbps on all ports and devices, right? Cannot I 
just boot with "libata.force=4:1.5Gbps"?

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Guennadi Liakhovetski wrote:
> On Fri, 7 Mar 2008, Tejun Heo wrote:
> 
>>> Looks like almost a minute to me? On another occurence I see about 1.5 
>>> minutes, then "port is slow to respond, please be patient (Status 0x80)" 
>>> has been repeated 3 times. On cold-plug also 3 times, I think, about the 
>>> same time then (time is not updated in the log).
>> I see.  Does the attached patch make any difference?
> 
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 4fbcce7..abebdcc 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
>  	spd = (scontrol >> 4) & 0xf;
>  	if (spd)
>  		link->hw_sata_spd_limit &= (1 << spd) - 1;
> +	link->hw_sata_spd_limit = 1;
>  
>  	ata_force_spd_limit(link);
>  
> Hm, this would force 1.5Gbps on all ports and devices, right? Cannot I 
> just boot with "libata.force=4:1.5Gbps"?

Yeap, you can do that.  Wasn't sure you were using .25-rc or .24.

Thanks.

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Sun, 9 Mar 2008, Tejun Heo wrote:

> Guennadi Liakhovetski wrote:
> > On Fri, 7 Mar 2008, Tejun Heo wrote:
> > 
> >>> Looks like almost a minute to me? On another occurence I see about 1.5 
> >>> minutes, then "port is slow to respond, please be patient (Status 0x80)" 
> >>> has been repeated 3 times. On cold-plug also 3 times, I think, about the 
> >>> same time then (time is not updated in the log).
> >> I see.  Does the attached patch make any difference?
> > 
> > diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> > index 4fbcce7..abebdcc 100644
> > --- a/drivers/ata/libata-core.c
> > +++ b/drivers/ata/libata-core.c
> > @@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
> >  	spd = (scontrol >> 4) & 0xf;
> >  	if (spd)
> >  		link->hw_sata_spd_limit &= (1 << spd) - 1;
> > +	link->hw_sata_spd_limit = 1;
> >  
> >  	ata_force_spd_limit(link);
> >  
> > Hm, this would force 1.5Gbps on all ports and devices, right? Cannot I 
> > just boot with "libata.force=4:1.5Gbps"?
> 
> Yeap, you can do that.  Wasn't sure you were using .25-rc or .24.

Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did 
say:

ata4: FORCE: PHY spd limit set to 1.5Gbps

but hot-plugging the drive still took 50 seconds to recover.

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Guennadi Liakhovetski wrote:
> On Sun, 9 Mar 2008, Tejun Heo wrote:
> 
>> Guennadi Liakhovetski wrote:
>>> On Fri, 7 Mar 2008, Tejun Heo wrote:
>>>
>>>>> Looks like almost a minute to me? On another occurence I see about 1.5 
>>>>> minutes, then "port is slow to respond, please be patient (Status 0x80)" 
>>>>> has been repeated 3 times. On cold-plug also 3 times, I think, about the 
>>>>> same time then (time is not updated in the log).
>>>> I see.  Does the attached patch make any difference?
>>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>>> index 4fbcce7..abebdcc 100644
>>> --- a/drivers/ata/libata-core.c
>>> +++ b/drivers/ata/libata-core.c
>>> @@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
>>>  	spd = (scontrol >> 4) & 0xf;
>>>  	if (spd)
>>>  		link->hw_sata_spd_limit &= (1 << spd) - 1;
>>> +	link->hw_sata_spd_limit = 1;
>>>  
>>>  	ata_force_spd_limit(link);
>>>  
>>> Hm, this would force 1.5Gbps on all ports and devices, right? Cannot I 
>>> just boot with "libata.force=4:1.5Gbps"?
>> Yeap, you can do that.  Wasn't sure you were using .25-rc or .24.
> 
> Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did 
> say:
> 
> ata4: FORCE: PHY spd limit set to 1.5Gbps
> 
> but hot-plugging the drive still took 50 seconds to recover.

How about cold plugging?

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Mon, 10 Mar 2008, Tejun Heo wrote:

> > Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did 
> > say:
> > 
> > ata4: FORCE: PHY spd limit set to 1.5Gbps
> > 
> > but hot-plugging the drive still took 50 seconds to recover.
> 
> How about cold plugging?

Same.

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Guennadi Liakhovetski wrote:
> On Mon, 10 Mar 2008, Tejun Heo wrote:
> 
>>> Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did 
>>> say:
>>>
>>> ata4: FORCE: PHY spd limit set to 1.5Gbps
>>>
>>> but hot-plugging the drive still took 50 seconds to recover.
>> How about cold plugging?
> 
> Same.

Does the attached patch help?

-- 
tejun

[-- Attachment #2: debug --]
[-- Type: text/plain, Size: 506 bytes --]

---
 drivers/ata/ahci.c |    1 +
 1 file changed, 1 insertion(+)

Index: tree2/drivers/ata/ahci.c
===================================================================
--- tree2.orig/drivers/ata/ahci.c
+++ tree2/drivers/ata/ahci.c
@@ -397,6 +397,7 @@ static const struct ata_port_operations 
 static const struct ata_port_info ahci_port_info[] = {
 	/* board_ahci */
 	{
+		AHCI_HFLAGS	(AHCI_HFLAG_NO_PMP),
 		.flags		= AHCI_FLAG_COMMON,
 		.link_flags	= AHCI_LFLAG_COMMON,
 		.pio_mask	= 0x1f, /* pio0-4 */

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Mon, 10 Mar 2008, Tejun Heo wrote:

> Guennadi Liakhovetski wrote:
> > On Mon, 10 Mar 2008, Tejun Heo wrote:
> > 
> >>> Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did 
> >>> say:
> >>>
> >>> ata4: FORCE: PHY spd limit set to 1.5Gbps
> >>>
> >>> but hot-plugging the drive still took 50 seconds to recover.
> >> How about cold plugging?
> > 
> > Same.
> 
> Does the attached patch help?

Well, I am not sure, whether it helps, tried booting with both 1.5Gbps and 
this patch, it recovers now within 30 sec in both cold- and hot-plug 
cases. To really state, that it has improved from about 55 sec down to 30 
sec one would need more testing. Is this the kind of improvement you 
expected? Can it be, that with this hardware it just cannot get better? 
Remember, the disk is an external eSATA enclosure with a (relatively new) 
PATA disk inside.

Well, at least the hotplug case did recover faster this time. Not sure 
about coldplug, because in the logs all kernel messages come with the 
same time and I don't have printk timestamp on.

Thanks
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Hello,

Guennadi Liakhovetski wrote:
> Well, I am not sure, whether it helps, tried booting with both 1.5Gbps and 
> this patch, it recovers now within 30 sec in both cold- and hot-plug 
> cases. To really state, that it has improved from about 55 sec down to 30 
> sec one would need more testing. Is this the kind of improvement you 
> expected?

Not really.  :-P

> Can it be, that with this hardware it just cannot get better? 
> Remember, the disk is an external eSATA enclosure with a (relatively new) 
> PATA disk inside.

Can you try out a shorter cable?  I had a lot of troubles with eSATA +
long cable + PMP combinations.  Using shorter cable usually solves the
problem for me.

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Guennadi Liakhovetski]

On Tue, 11 Mar 2008, Tejun Heo wrote:

> Hello,
> 
> Guennadi Liakhovetski wrote:
> > Well, I am not sure, whether it helps, tried booting with both 1.5Gbps and 
> > this patch, it recovers now within 30 sec in both cold- and hot-plug 
> > cases. To really state, that it has improved from about 55 sec down to 30 
> > sec one would need more testing. Is this the kind of improvement you 
> > expected?
> 
> Not really.  :-P
> 
> > Can it be, that with this hardware it just cannot get better? 
> > Remember, the disk is an external eSATA enclosure with a (relatively new) 
> > PATA disk inside.
> 
> Can you try out a shorter cable?  I had a lot of troubles with eSATA +
> long cable + PMP combinations.  Using shorter cable usually solves the
> problem for me.

Well, this cable is only about 50cm long, or even shorter, and using a 
shorter one would be difficult there, even if I manage to get hold of one. 
But, in principle, if this is not a generic ahci problem that needs to be 
solved, I personally can somehow live with it. Having to wait 1 minute is 
not very nice, but so far not critical.

Thanks for your help
Guennadi
---
Guennadi Liakhovetski

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Tejun Heo]

Hello,

Guennadi Liakhovetski wrote:
>> Guennadi Liakhovetski wrote:
>>> Well, I am not sure, whether it helps, tried booting with both 1.5Gbps and 
>>> this patch, it recovers now within 30 sec in both cold- and hot-plug 
>>> cases. To really state, that it has improved from about 55 sec down to 30 
>>> sec one would need more testing. Is this the kind of improvement you 
>>> expected?
>> Not really.  :-P
>>
>>> Can it be, that with this hardware it just cannot get better? 
>>> Remember, the disk is an external eSATA enclosure with a (relatively new) 
>>> PATA disk inside.
>> Can you try out a shorter cable?  I had a lot of troubles with eSATA +
>> long cable + PMP combinations.  Using shorter cable usually solves the
>> problem for me.
> 
> Well, this cable is only about 50cm long, or even shorter, and using a 
> shorter one would be difficult there, even if I manage to get hold of one. 
> But, in principle, if this is not a generic ahci problem that needs to be 
> solved, I personally can somehow live with it. Having to wait 1 minute is 
> not very nice, but so far not critical.

50cm gotta be short enough.  For intel ahci, it definitely isn't a
general problem but it would still be nice if we can find out what's
going on but I don't have much idea what to do next.  I'll keep your
problem in mind and see whether any pattern emerges.  If you find out
something new, please let us know.

Thanks.

-- 
tejun

Re: Unknown SATA PIIX PCI device ID 0x29b6

[Felix Miata]

On 2008/02/28 22:56 (GMT) Alan Cox apparently typed:

> is the device in AHCI mode or PIIX mode ?

How does one tell for sure? BIOS typically only say things like "compatible"
or "enhanced".
-- 
"For God so loved the world that he gave his one
and only Son, that whoever believes in him shall
not perish but have eternal life." John 3:16 NIV

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://mrmazda.no-ip.com/

RE: Unknown SATA PIIX PCI device ID 0x29b6

[Gaston, Jason D]

>> is the device in AHCI mode or PIIX mode ?
>
>How does one tell for sure? BIOS typically only say things 
>like "compatible"
>or "enhanced".

29b6 is the IDER, IDE Redirection, network device.  There there will not
be anything "locally" attached to that network device.  I have not been
adding the IDER Management devices to the ata_piix driver, perhaps I
should?   

When in doubt, about an unknown device, check the latest pci.ids file on
http://pciids.sf.net.  We try to keep it up to date.

Thanks,

Jason