linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Rob Allen <ra-kernel@hotmail.co.uk>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Clemens Ladisch <clemens@ladisch.de>,
	Ram Pai <linuxram@us.ibm.com>,
	linux1394-devel@lists.sourceforge.net, linux-pci@vger.kernel.org
Subject: Re: [Bug 43244] New: firewire_ohci prevents boot
Date: Mon, 4 Jun 2012 16:59:48 -0700	[thread overview]
Message-ID: <CAE9FiQUtJ_YZEd6kFydi=fwiGnDBkEABpM=FE1EiZwHu4NtwAA@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP129FFE755310932B1C36438B7000@phx.gbl>

On Thu, May 24, 2012 at 11:43 AM, Rob Allen <ra-kernel@hotmail.co.uk> wrote:
> On 24/05/12 19:26, Stefan Richter wrote:
>>
>> On May 24 bugzilla-daemon@bugzilla.kernel.org wrote:
>>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=43244
>>>
>>> --- Comment #3 from Rob Allen<ra-kernel@hotmail.co.uk>   2012-05-24
>>> 17:30:12 ---
>>> Created an attachment (id=73381)
>>>  -->  (https://bugzilla.kernel.org/attachment.cgi?id=73381)
>>> dmesg from v3.4 with CONFIG_PCI_DEBUG
>

it seems kernel assign new resource to the bridge

[    0.841285] pci 0000:00:1e.0: PCI bridge to [bus 0a-0b] (subtractive decode)
[    0.841340] pci 0000:00:1e.0:   bridge window [mem 0xd0400000-0xd04fffff]
[    0.841349] pci 0000:00:1e.0:   bridge window [io  0x0000-0xffff]
(subtractive decode)
[    0.841352] pci 0000:00:1e.0:   bridge window [mem
0x00000000-0xffffffff] (subtractive decode)

[    0.924562] pci 0000:00:1e.0: PCI bridge to [bus 0a-0b]
[    0.924611] pci 0000:00:1e.0:   bridge window [io  0x9000-0x9fff]
[    0.924663] pci 0000:00:1e.0:   bridge window [mem 0xd0400000-0xd04fffff]
[    0.924715] pci 0000:00:1e.0:   bridge window [mem
0x80000000-0x87ffffff pref]

can you post

lspci -vvxxx -s 0a:09.4

with working kernel and not working kernel?

Thanks

Yinghai

  reply	other threads:[~2012-06-04 23:59 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 [this message]
     [not found]                 ` <4FBE8146.1030803@hotmail.co.uk>
2012-06-04 11:00                   ` Rob Allen
2012-06-05  2:54                     ` Ram Pai
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='CAE9FiQUtJ_YZEd6kFydi=fwiGnDBkEABpM=FE1EiZwHu4NtwAA@mail.gmail.com' \
    --to=yinghai@kernel.org \
    --cc=clemens@ladisch.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxram@us.ibm.com \
    --cc=ra-kernel@hotmail.co.uk \
    --cc=stefanr@s5r6.in-berlin.de \
    /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).