Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759250AbaDJWvY (ORCPT ); Thu, 10 Apr 2014 18:51:24 -0400 Received: from mail-qc0-f170.google.com ([209.85.216.170]:42638 "EHLO mail-qc0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753896AbaDJWvU (ORCPT ); Thu, 10 Apr 2014 18:51:20 -0400 Date: Thu, 10 Apr 2014 18:51:18 -0400 (EDT) From: Parag Warudkar X-X-Sender: parag@parag-Z230 To: Bjorn Helgaas cc: Parag Warudkar , Linus Torvalds , Yinghai Lu , LKML , "Rafael J. Wysocki" , "linux-pci@vger.kernel.org" , "linux-acpi@vger.kernel.org" Subject: Re: BAR 14: can't assign mem (size 0x200000) In-Reply-To: Message-ID: References: <20140329171903.GA10551@google.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 10 Apr 2014, Bjorn Helgaas wrote: > On Sat, Mar 29, 2014 at 6:14 PM, Parag Warudkar wrote: > >> On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote: > > > >>> Parag, can you add a WARN_ON_ONCE() to that message, so that we see > >>> what the call chain is for it. > > Parag, did you ever try this? No I haven't so far - I assumed the call chain you posted initially was the only possibility. I will give it a try. > I doubt that Ubuntu includes any patches relevant to this issue. > > Even though it doesn't seem to cause any problems, we're going to get > a lot of complaints about these scary-looking messages when resuming, > so I think we should figure this out and fix it. Sure, since the resource assignments aren't an issue during fresh boot, it might just be something worth fixing in the resume path. Thanks, Parag -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/