mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Chiang <achiang@hp.com>
Cc: matthew@wil.cx, justin.chen@hp.com, linux-kernel@vger.kernel.org
Subject: Re: PCI BAR mem resource allocation "regression"
Date: Sat, 13 Dec 2008 09:16:29 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0812130901370.3340@localhost.localdomain> (raw)
In-Reply-To: <20081213000538.GC9947@ldl.fc.hp.com>



On Fri, 12 Dec 2008, Alex Chiang wrote:
> 
> I've been chasing a bug for the past week or so that I can't seem
> to figure out, and was hoping to get your eyes on it.
> 
> The basic summary is, we can't allocate a memory resource for our
> BAR after a PCI hotplug operation. We've been able to bisect it
> down to d33b6fba2c4350651f3f61ff2ab858a2f116e9a4 (Resources:
> insert identical resources above existing resources).

I'm missing some pieces I'd like to see: /proc/iomem before and after, and 
lspci output before and after (you do give lspci output, but only one, and 
I can't tell if it's before or after).

Also, is it just the error message, or does it actually affect 
functionality?

			Linus

  reply	other threads:[~2008-12-13 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13  0:05 Alex Chiang
2008-12-13 17:16 ` Linus Torvalds [this message]
2008-12-13 17:41   ` Linus Torvalds
2008-12-14  1:12     ` Alex Chiang
2008-12-17  4:05     ` Matthew Wilcox
2008-12-14  1:05   ` Alex Chiang
2008-12-14  1:37     ` Linus Torvalds
2008-12-15 20:04       ` Jesse Barnes
2008-12-16  0:25         ` Linus Torvalds
2008-12-16  0:53           ` Jesse Barnes
2008-12-15 18:26     ` Chen, Justin
2008-12-15 22:29     ` Chen, Justin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0812130901370.3340@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=achiang@hp.com \
    --cc=justin.chen@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®