linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ruud <netwerkforens@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PCIe bus (re-)numbering
Date: Tue, 29 Sep 2015 16:04:07 +0200	[thread overview]
Message-ID: <CAKsTQnkBPEiUtpaVxyDm--BLnHvUCtVMhEUQ5-FQryp-X9HBUg@mail.gmail.com> (raw)
In-Reply-To: <CAE9FiQWxBWaJh0CbbEfeBUJK+54NDrTW6r0v-6itXEyTkmzkhQ@mail.gmail.com>

>>
>> Thus the procedure that works is:
>> 1) Chassis off
>> 2) Boot linux
>> 3) Chassis on
>> 4) setpci busnrs to 0
>> 5) remove switch
>> 6) rescan
>
> 4, 5 is reversed?

I can not setpci on a removed device, afaik.... for that reason I
reset the busses before removing the switch (not physically remove but
echo 1 >../remove).

For the kernel crash issue I will try to explain better, and try to
get a kernel crash dump to post some logging. It seems that the switch
will still fire hotplug events even after being removed (see lspci -tv
below). I zero-ed the busnumber for bus 04 (02.0-[04-17])  without
removing the underlying bus 05 device 00.0 and switches below.

(for illustration, lspci -tv from a 3.2 kernel, hand edited as the
original picture has already discovered the subordinate busses)
            +-02.0-[04-17]----00.0-[05-17]--+-04.0-[06-16]----00.0-[07-16]---
             |                               |
      \-08.0-[11-16]----

Sorry for the delay, but I didn't manage to create a crashdump yet :(
and the BMC is not cooperative in getting the serial console kernel
working either.
Will not go into details on my attempts for the kernel crash logging
to work as it is out of scope for the discussion..

Bet regards, Ruud

  reply	other threads:[~2015-09-29 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-19  8:20 PCIe bus (re-)numbering Ruud
2015-09-19 21:35 ` Yinghai Lu
2015-09-20  9:17   ` Ruud
2015-09-20 17:03     ` Yinghai Lu
2015-09-21  7:49       ` Ruud
2015-09-21 14:06         ` Ruud
2015-09-21 21:22           ` Yinghai Lu
2015-09-29 14:04             ` Ruud [this message]
2015-09-29 15:36               ` Yinghai Lu
2015-09-21 21:22         ` Yinghai Lu

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=CAKsTQnkBPEiUtpaVxyDm--BLnHvUCtVMhEUQ5-FQryp-X9HBUg@mail.gmail.com \
    --to=netwerkforens@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).