From: Ram Pai <linuxram@us.ibm.com>
To: Rob Allen <ra-kernel@hotmail.co.uk>
Cc: Ram Pai <linuxram@us.ibm.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Clemens Ladisch <clemens@ladisch.de>,
Yinghai Lu <yinghai@kernel.org>,
linux1394-devel@lists.sourceforge.net, linux-pci@vger.kernel.org
Subject: Re: [Bug 43244] New: firewire_ohci prevents boot
Date: Tue, 5 Jun 2012 10:54:22 +0800 [thread overview]
Message-ID: <20120605025422.GB6637@ram-ThinkPad-T61> (raw)
In-Reply-To: <BLU0-SMTP435F81F04D60963F0755BA9B70F0@phx.gbl>
On Mon, Jun 04, 2012 at 12:00:10PM +0100, Rob Allen wrote:
> Ram Pai,
>
> I've found the change that introduced the failure I'm seeing, and it
> seems you are the author. Please can you offer some help?
>
> commit 0a2daa1cf35004f5adbf4138555cc5669abf3a3e
> Author: Ram Pai <linuxram@us.ibm.com>
> Date: Mon Jul 25 13:08:41 2011 -0700
>
> PCI: make cardbus-bridge resources optional
>
> Allocate resources to cardbus bridge only after all other genuine
> resources requests are satisfied. Dont retry if resource allocation
> for cardbus-bridges fail.
>
> Signed-off-by: Ram Pai <linuxram@us.ibm.com>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Yes looking into it. The resource assignment for one of the BARs of the
firewire ohci device at 0a:09.4 has got reassigned a valid address
AFAICT. I think that device does not like the OS to reassign any resources.
We need to determine whether the ohci device behaves abnormally if it gets
assigned a address other than what is assigned by the BIOS.
To do that; as Yinghai suggested, lets see the contents of the
register with and without the patch.
output of the following command on a working kernel and a non-working
kernel will shed some light.
lspci -vvxxx -s 0a:09.4
also boot messages on a working kernel will also be helpful.
RP
next prev parent reply other threads:[~2012-06-05 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43244-4803@https.bugzilla.kernel.org/>
[not found] ` <20120513221357.7574ae79@stein>
2012-05-14 6:32 ` [Bug 43244] New: firewire_ohci prevents boot Clemens Ladisch
2012-05-14 6:39 ` Yinghai Lu
2012-05-16 13:12 ` Rob Allen
2012-05-16 13:53 ` Clemens Ladisch
2012-05-21 19:33 ` Rob Allen
2012-05-21 20:08 ` Stefan Richter
2012-05-21 20:20 ` Clemens Ladisch
2012-05-24 18:26 ` Stefan Richter
2012-05-24 18:43 ` Rob Allen
2012-06-04 23:59 ` Yinghai Lu
[not found] ` <4FBE8146.1030803@hotmail.co.uk>
2012-06-04 11:00 ` Rob Allen
2012-06-05 2:54 ` Ram Pai [this message]
2012-06-19 21:11 ` Rob Allen
[not found] ` <BAY153-W382DF41517C8EA770817E4B7EB0@phx.gbl>
2012-07-01 20:56 ` Yinghai Lu
2012-07-05 19:53 ` Rob Allen
[not found] ` <4FF5F09C.5020507@hotmail.co.uk>
2012-07-21 11:31 ` Rob Allen
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=20120605025422.GB6637@ram-ThinkPad-T61 \
--to=linuxram@us.ibm.com \
--cc=clemens@ladisch.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=ra-kernel@hotmail.co.uk \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yinghai@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).