From: Christian Lamparter <chunkeey@googlemail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: dhlii@dlasys.net, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: 2.6.34-rc6 pci bridge problems
Date: Fri, 7 May 2010 20:44:07 +0200 [thread overview]
Message-ID: <201005072044.07682.chunkeey@googlemail.com> (raw)
In-Reply-To: <201005070946.41857.bjorn.helgaas@hp.com>
On Friday 07 May 2010 17:46:41 Bjorn Helgaas wrote:
> 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?
Pong! Unfortunately, I haven't heard any news about this pci bridge issue
from "David H. Lynch Jr.". But as you say: "Time for patching 2.6.34-rcX
regressions is running out". Therefore, David: please hurry up and post
what you are seeing. Most of oopses, can be easily captured with a serial
console (a setup is described in Documentation/serial-console.txt )
Regards,
Chr
next prev parent reply other threads:[~2010-05-07 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 10:19 ar9170-fw II David H. Lynch Jr.
2010-05-01 17:19 ` Christian Lamparter
2010-05-01 18:23 ` David H. Lynch Jr.
2010-05-01 20:45 ` Christian Lamparter
2010-05-02 7:47 ` Benoit Papillault
2010-05-02 11:14 ` David H. Lynch Jr.
2010-05-02 12:52 ` Christian Lamparter
2010-05-02 13:47 ` David H. Lynch Jr.
2010-05-05 18:41 ` carl9170 1.0.5.1 David H. Lynch Jr.
2010-05-05 19:59 ` 2.6.34-rc6 pci bridge problems Christian Lamparter
2010-05-06 15:09 ` Bjorn Helgaas
2010-05-07 15:46 ` Bjorn Helgaas
2010-05-07 18:44 ` Christian Lamparter [this message]
2010-05-06 0:11 ` carl9170 1.0.5.1 Luis R. Rodriguez
2010-05-11 22:02 ` ar9170-fw II David H. Lynch Jr.
2010-05-11 23:27 ` Christian Lamparter
2010-05-21 7:50 ` carl9170 1.0.6 David H. Lynch Jr.
2010-05-21 21:35 ` carl9170 1.0.6 carl9170_tx_superdesc David H. Lynch Jr.
2010-05-21 22:55 ` Christian Lamparter
2010-05-22 1:09 ` David H. Lynch Jr.
2010-05-22 19:13 ` carl9170 1.0.9 David H. Lynch Jr.
2010-05-23 1:34 ` Christian Lamparter
2010-05-23 5:30 ` David H. Lynch Jr.
2010-05-23 6:30 ` carl9170 1.0.9.1 David H. Lynch Jr.
2010-05-03 21:39 ` ar9170-fw II Luis R. Rodriguez
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=201005072044.07682.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=bjorn.helgaas@hp.com \
--cc=dhlii@dlasys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.