From: Helge Deller <deller@gmx.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-parisc@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] parisc/PCI: lba: fix: convert to pci_create_root_bus() for correct root bus resources
Date: Sun, 02 Jun 2013 00:03:16 +0200 [thread overview]
Message-ID: <51AA6FA4.3000900@gmx.de> (raw)
In-Reply-To: <CAErSpo6oX4ADT39_ya_PbHhkQ=i_TaT+hwfrh6qXDn2xCEnx7w@mail.gmail.com>
On 05/31/2013 11:25 PM, Bjorn Helgaas wrote:
>>>> Maybe it has devices that aren't
>>>> officially supported and the firmware did the wrong thing? (Though it'd
>>>> still be nice if Linux did something more sensible than this.)
>>
>> Ok, I removed all unnecessary cards, incl. 100MBit NIC, 1000MBit NIC, Matrox G200 and a Visualize FX.
>>
>> Now it works nicely and as expected.
>> Even the Visualize EG graphics card and the Voodo2 work (which were my main problem) :-)
>
> Good, glad that works. We *ought* to be able to do better, e.g., by
> just ignoring cards that we can't use.
>
> If you have a chance, you might collect the complete dmesg log from
> both the working configuration and the broken one, and attach them to
> a new kernel.org PCI bugzilla.
I opened bugzilla #59191
https://bugzilla.kernel.org/show_bug.cgi?id=59191
(Someone needs to reassign this bug to Driver/PCI component - I can't.)
Thanks!
Helge
prev parent reply other threads:[~2013-06-01 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130530141033.GA3665@ls3530.box>
[not found] ` <CAErSpo69AxKgz8Dg8+T7n5jsuOzdSoCUstqrX+uUh8TZ08ayqg@mail.gmail.com>
[not found] ` <51A7ACBF.4030601@gmx.de>
2013-05-30 21:12 ` [PATCH] parisc/PCI: lba: fix: convert to pci_create_root_bus() for correct root bus resources Bjorn Helgaas
2013-05-30 21:40 ` Helge Deller
2013-05-31 20:46 ` Helge Deller
2013-05-31 21:25 ` Bjorn Helgaas
2013-06-01 22:03 ` Helge Deller [this message]
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=51AA6FA4.3000900@gmx.de \
--to=deller@gmx.de \
--cc=bhelgaas@google.com \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).