linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: `VL <vl.homutov@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: pci->pcie bridge issue: kernel unable to find a free I/O port range.
Date: Thu, 09 Jan 2014 09:14:06 +0400	[thread overview]
Message-ID: <52CE301E.60108@gmail.com> (raw)
In-Reply-To: <CAE9FiQV5r-c4ufd2SqLJk-KcoJhucmr6RszUb0LyUFtgq_a5sg@mail.gmail.com>

I've put all logs here: http://inspert.ru/pci/

On 09.01.2014 00:28, Yinghai Lu wrote:
> On Wed, Jan 8, 2014 at 2:08 AM, `VL <vl.homutov@gmail.com> wrote:
>> I've enabled netconsole and got some output.
>> Here it is: http://dpaste.com/1542030/
> It does include any realloc message.
not sure I understood you.
The message I was talking about is:

Jan  8 12:51:52 10 Some PCI device resources are unassigned, try booting 
with pci=realloc

and you can see it in this log: 
http://inspert.ru/pci/netconsole-norealloc.txt

The kernel hangs if I add this option.
>
>> Note that since the hang occurs on the module load, netconsole was 
>> unable
>> to send latest messages and the log looks clear
>>
>> I've rebuilt kernel with sound driver compiled in, and the hang occured
>> during
>> kernel load, userspace was not reached (but in this case, netconsole was
>> useless at
>> all) and I've made a photo of screen (attached). Note there is ACPI 
>> warning
>> about
>> system IO conflict.
> Can you enable
>
> CONFIG_PCI_DEBUG=y
>
> and boot with "debug ignore_loglevel initcall_debug"?

Here it is: http://inspert.ru/pci/netconsole-pcidebug.txt

(problem is when snd_ice17 is loaded; this is for the card installed 
into adapter)
>
> Thanks
>
> Yinghai


  reply	other threads:[~2014-01-09  5:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07  9:11 pci->pcie bridge issue: kernel unable to find a free I/O port range `VL
2014-01-07 18:27 ` Bjorn Helgaas
     [not found]   ` <52CD2387.2030403@gmail.com>
2014-01-08 20:28     ` Yinghai Lu
2014-01-09  5:14       ` `VL [this message]
2014-01-09 20:17         ` Yinghai Lu
2014-01-10  4:41           ` `VL
2014-01-10  5:19             ` Yinghai Lu
2014-01-11  8:38               ` `VL
2014-01-14 19:31                 ` Yinghai Lu
2014-01-15  9:10                   ` `VL
     [not found]                     ` <52D6CEC6.2000901@gmail.com>
2014-01-30  5:31                       ` `VL
2014-01-30 18:56                         ` Yinghai Lu
2014-02-01 10:30                           ` `VL
2014-10-13 20:48                             ` Bjorn Helgaas

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=52CE301E.60108@gmail.com \
    --to=vl.homutov@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --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).