From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: dhlii@dlasys.net, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: 2.6.34-rc6 pci bridge problems
Date: Fri, 7 May 2010 09:46:41 -0600 [thread overview]
Message-ID: <201005070946.41857.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <201005060909.58503.bjorn.helgaas@hp.com>
On Thursday, May 06, 2010 09:09:58 am Bjorn Helgaas wrote:
> On Wednesday, May 05, 2010 01:59:55 pm Christian Lamparter wrote:
> > On Wednesday 05 May 2010 20:41:26 David H. Lynch Jr. wrote:
> > > When I build out of the wireless-testing git tree (puled today)
> > > 2.6.34-rc6 using my current systems .config I get a very quick error
> > > on boot about PCI bridge windows.
> > > googling the error indicates this is a know 2.6.34 problem and that
> > > there are fixes in other 2.6.34 trees.
> > > I have been unable to find the actual patches or I would just apply
> > > them to wireless-testing.
>
> I made significant changes in the way we handle PCI bridge windows,
> and I'm eager to fix any issues in that area. But "very quick error
> on boot" doesn't give me any information to work with.
>
> Please attach your complete dmesg output, serial console log (with
> "ignore_loglevel"), digital photo of the error, or other specific
> details.
Ping! If there's a problem here, I want to fix it as soon as possible.
Do you have any more details? What error message did you google?
Thanks,
Bjorn
next prev parent reply other threads:[~2010-05-07 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BDC001F.9050202@dlasys.net>
[not found] ` <201005021452.01101.chunkeey@googlemail.com>
[not found] ` <4BE1BBD6.3030505@dlasys.net>
2010-05-05 19:59 ` Christian Lamparter
2010-05-06 15:09 ` Bjorn Helgaas
2010-05-07 15:46 ` Bjorn Helgaas [this message]
2010-05-07 18:44 ` Christian Lamparter
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=201005070946.41857.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=chunkeey@googlemail.com \
--cc=dhlii@dlasys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®