From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Hounschell Subject: Re: Can't boot new 4.4 kernel with IOMMU enabled Date: Fri, 18 Mar 2016 13:24:27 -0400 Message-ID: <56EC39CB.2010909@compro.net> References: <569FCFC8.2000606@compro.net> <20160120182602.GJ18805@8bytes.org> <56A0F03C.8010109@compro.net> <56A0F221.10502@compro.net> <20160121223958.GL18805@8bytes.org> <56B0CFF7.80907@compro.net> <20160216162455.GX18805@8bytes.org> <56C35D1A.9080307@compro.net> <20160226162319.GH22747@8bytes.org> <56D0A565.8080406@compro.net> <20160229174252.GN22747@8bytes.org> <56D48560.4010904@compro.net> Reply-To: markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56D48560.4010904-n2QNKt385d+sTnJN9+BGXg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Joerg Roedel Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: iommu@lists.linux-foundation.org On 02/29/2016 12:52 PM, Mark Hounschell wrote: > On 02/29/2016 12:42 PM, Joerg Roedel wrote: >> Hi Mark, >> >> On Fri, Feb 26, 2016 at 02:20:05PM -0500, Mark Hounschell wrote: >>> On 02/26/2016 11:23 AM, Joerg Roedel wrote: >>>> Can you please boot a v4.5-rc5 kernel with iommu enabled and >>>> 'amd_iommu_dump' on the kernel command line and send me dmesg after >>>> boot again? >>>> >>>> >>> >>> Here ya go Joerg, >>> >>> See ata7 and ata8 failure messages. These are the 2 disks that don't >>> come up. They are hanging off one of these two Marvell chips. >>> >>> 07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA >>> 6Gb/s Controller (rev 12) >>> 13:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA >>> 6Gb/s Controller (rev 12) >> >> Thanks for the dmesg. It does not contain IO_PAGE_FAULTs anymore, did it >> in the past? If yes, which device-ids were the faults reported against? >> > > The original report from me at the top of this thread was that the > machine would not come up at all. Many IO_PAGE_FAULTs. > > The patch by Baoquan He > > iommu/amd: Correct the wrong setting of alias DTE in do_attach > commit 9b1a12d29109234d2b9718d04d4d404b7da4e794 upstream > > fixed that issue but left me with these 2 disk not coming up. If I > disable the iommu in the BIOS, all the disks work fine. > > >> I can't really say yet why it does not work on your system. The IOMMU >> core groups the devices 00:15.0-2 and 11-13:00.0 together. This means >> that they all end up in the same iommu group. >> >> But according to the IVRS ACPI table on your system none of these >> devices has an alias defined. So this doesn't explain why the commit >> you bisected it down to causes the problem, because the commit is about >> alias handling (which the devices in question don't need). >> >> Maybe I send you some debug patches to try out, but I stare at the code >> a little bit more first. >> > > OK Should I submit a kernel bug report on this? Mark