From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org ([63.228.1.57]:39010 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755651Ab3EVUpY (ORCPT ); Wed, 22 May 2013 16:45:24 -0400 Message-ID: <1369255489.3870.19.camel@pasglop> Subject: Re: Resource assignment oddities From: Benjamin Herrenschmidt To: Bjorn Helgaas Cc: Yinghai Lu , Gavin Shan , "linux-pci@vger.kernel.org" Date: Thu, 23 May 2013 06:44:49 +1000 In-Reply-To: References: <1367712653.11982.19.camel@pasglop> <1367712932.11982.20.camel@pasglop> <1367732090.11982.38.camel@pasglop> <1367740336.11982.41.camel@pasglop> <51871088.4594420a.0ccc.7300SMTPIN_ADDED_BROKEN@mx.google.com> <518786a7.64bbec0a.58a0.1f6bSMTPIN_ADDED_BROKEN@mx.google.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-pci-owner@vger.kernel.org List-ID: On Wed, 2013-05-22 at 11:21 -0600, Bjorn Helgaas wrote: > > looks like right fix for v3.9 should be as attached patch. > > it will keep must+optional for mmio, if only ioport fails.... > > I read all that before, but it didn't answer my questions. I assume > we're trying to fix a device that doesn't work. Which device is it? We have MMIO assignment failures due to the "retry" but so far it hasn't prevented the devices I have tested from working. It does make me very nervous however. Gavin, do you have more details about what actually happens ? Cheers, Ben.