From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Brown, Len" <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VIA PCI routing problem
Date: Fri, 29 Jul 2005 08:28:35 +1000 [thread overview]
Message-ID: <42E95C13.5080509@yahoo.com.au> (raw)
In-Reply-To: <200507280937.33971.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
>
> Can you try this:
>
[...]
>
>
> If that doesn't help, remove it and see if this does:
>
[...]
>
> Can you also include "lspci" output?
>
Neither worked. I'll open a bugzilla and include lspci and dmesg there.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-07-28 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 12:10 VIA PCI routing problem Nick Piggin
2005-07-28 15:37 ` Bjorn Helgaas
2005-07-28 22:28 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-28 18:36 Brown, Len
2005-07-28 22:43 ` Nick Piggin
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=42E95C13.5080509@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@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