Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161132AbaDJTu0 (ORCPT ); Thu, 10 Apr 2014 15:50:26 -0400 Received: from mail-ig0-f175.google.com ([209.85.213.175]:48770 "EHLO mail-ig0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030242AbaDJTuW (ORCPT ); Thu, 10 Apr 2014 15:50:22 -0400 MIME-Version: 1.0 In-Reply-To: References: <20140329171903.GA10551@google.com> From: Bjorn Helgaas Date: Thu, 10 Apr 2014 13:50:01 -0600 Message-ID: Subject: Re: BAR 14: can't assign mem (size 0x200000) To: Parag Warudkar Cc: Linus Torvalds , Yinghai Lu , LKML , "Rafael J. Wysocki" , "linux-pci@vger.kernel.org" , "linux-acpi@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? > ... > Not sure if Ubuntu includes any patches on top of 3.11 mainline that > make a difference to this issue - but in case they don't this might be > a regression. 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. Bjorn -- 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/