lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Apr 2012 11:13:45 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Martin Mokrejs <mmokrejs@...d.natur.cuni.cz>
Cc:	linux-pci@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 3.2.11: PCI Express card cannot be re-detected withing cca 60sec timeframe

On Thu, Apr 19, 2012 at 10:32 AM, Martin Mokrejs
<mmokrejs@...d.natur.cuni.cz> wrote:
>  this brought me to and issue with "Intel® 6 Series Express Chipset B2 stepping" chips
> having enabled SATA ports 2-5. This is my case:
>
> [    3.037832] ahci 0000:00:1f.2: version 3.0
> [    3.037880] ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
> [    3.037906] ahci: SSS flag set, parallel bus scan disabled
> [    3.048233] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x31 impl SATA mode
> [    3.048335] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ems sxs apst
> [    3.048371] ahci 0000:00:1f.2: setting latency timer to 64
> [    3.088902] scsi0 : ahci
> [    3.089010] scsi1 : ahci
> [    3.089098] scsi2 : ahci
> [    3.089185] scsi3 : ahci
> [    3.089272] scsi4 : ahci
> [    3.089361] scsi5 : ahci
> [    3.090528] ata1: SATA max UDMA/133 abar m2048@...7f06000 port 0xf7f06100 irq 44
> [    3.091400] ata2: DUMMY
> [    3.092262] ata3: DUMMY
> [    3.093112] ata4: DUMMY
> [    3.093952] ata5: SATA max UDMA/133 abar m2048@...7f06000 port 0xf7f06300 irq 44
> [    3.094803] ata6: SATA max UDMA/133 abar m2048@...7f06000 port 0xf7f06380 irq 44
>
>
> Is this bug anyhow related to this already known chipset issue?
>
> http://support.dell.com/support/topics/global.aspx/support/kcs/document?c=us&cs=04&docid=389728&l=en&s=bsd
> http://www.intel.com/support/chipsets/6/sb/CS-032521.htm
> http://www.intel.com/support/chipsets/6/sb/CS-032521.htm
>
>>
>
>
> So you found two issues, right?
>
> Issue 1:
>
> Yinghai Lu wrote:
>> for USB 3.0:
>>               SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
>>                       Changed: MRL- PresDet- LinkState+
>>
>> PresDet+: mean that card is still there. so no interrupt is generated
>> by chipset.
>>
>> that present bit is decide by by inband link or out of band.
>>
>> sometimes when out of band pres is no, present bit could be keep flip
>> around because in root port try to retrain to detect ...
>> but it is not the case.
>>
>> the pin "CPPE#  PCI Express interface presence detect" should get into
>> hotplug FPGA in motherboard.
>>
>> You may need to check with vendor about if there is any problem with
>> that hotplug FPGA.

Not sure about this one. could be that outofband signal is not used.



>
>
> Issue 2:
>>>> Can you try to use acpiphp instead of pciehp?
>>
>> looks your BIOS does not support acpiphp.
>>
>> Maybe you have to stay with
>>
>> echo 1  > .../pcie_link_disable
>> echo 0  > .../pcie_link_disable
>>
>> after removal every time.
>>
>
> Does it make sense to report this to Dell (that it does not support ACPI hotplug)?
> Can they fix it with BIOS or whatever? Thay will anyways replace my motherboard
> in the laptop if my system is really affected.

even there is intel silicon problem <user can not disable inband
present detecting, and that could report wrong status>
Dell should have good design to workaround it like add logic to check
CPPE and reset the link if needed.

>
> Can I just return the thing after 2.5 months completely?

You need to talk to dell about that.

How about those test on other shipped OS?

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ