Hi Can someone please help me to debug this issue? Regards Nehal -----Original Message----- From: Shah, Nehal-bakulchandra Sent: Monday, September 26, 2016 3:45 PM To: 'Bharat Kumar Gogada' <bharat.kumar.gogada@xxxxxxxxxx> Cc: Deucher, Alexander <Alexander.Deucher@xxxxxxx>; linux-pci@xxxxxxxxxxxxxxx; holler@xxxxxxxxxxxxx; tj@xxxxxxxxxx; linux-ide@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx Subject: RE: ATA failure regression Hi Bharat Thanks for the reply. I have observed following thing If IOMMU is enabled in BIOS and I use following option FCH SATA Debug Options --> Unused SATA Port Auto Shut Down Disabled. Issue is not happening. I have attached dmesg and lspci output with this option Also I have attached lspci log with IOMMU disabled. When issue is happening I am not able to take lspci logs as it stops in initramfs itself. I will try to get. Thanks Nehal -----Original Message----- From: Bharat Kumar Gogada [mailto:bharat.kumar.gogada@xxxxxxxxxx] Sent: Friday, September 23, 2016 3:40 PM To: Shah, Nehal-bakulchandra <Nehal-bakulchandra.Shah@xxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; linux-pci@xxxxxxxxxxxxxxx; holler@xxxxxxxxxxxxx; tj@xxxxxxxxxx; linux-ide@xxxxxxxxxxxxxxx Cc: Deucher, Alexander <Alexander.Deucher@xxxxxxx> Subject: RE: ATA failure regression > Hi All, > > Resending this wider audience > > Currently I am working on AMD future platform. I am hitting the same > bug of ATA Failure Regression reported in past. > (https://patchwork.kernel.org/patch/6875661/) or > http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html > > I am newbie to this and because of this Ubuntu 16.04 is not booting. > If disable IOMMU and MSI obviously it works but that is not solution. > Even when I bisected it boiled to same place which was mentioned in past discussion. > So here when you are disabling MSI, it is working with legacy interrupts or MSI-X. Can you post the end sata device lscpi -xxx -vvv content. Bharat -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
