public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Sanath S <Sanath.S@amd.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Sanjay R Mehta <sanju.mehta@amd.com>, <linux-pci@vger.kernel.org>,
	<bhelgaas@google.com>, <linux-kernel@vger.kernel.org>,
	<mario.limonciello@amd.com>, Sanath S <Sanath.S@amd.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH] PCI: Allocate maximum available buses to help extending the daisy chain
Date: Wed, 23 Aug 2023 22:15:49 +0800	[thread overview]
Message-ID: <202308232106.50c8f492-oliver.sang@intel.com> (raw)
In-Reply-To: <20230816051923.2287912-1-Sanath.S@amd.com>



Hello,

kernel test robot noticed disk issues on:

commit: 4f0dbecaea6160d50d568fcaa4e09346052f7423 ("[PATCH] PCI: Allocate maximum available buses to help extending the daisy chain")
url: https://github.com/intel-lab-lkp/linux/commits/Sanath-S/PCI-Allocate-maximum-available-buses-to-help-extending-the-daisy-chain/20230816-132324
base: https://git.kernel.org/cgit/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/all/20230816051923.2287912-1-Sanath.S@amd.com/
patch subject: [PATCH] PCI: Allocate maximum available buses to help extending the daisy chain

in testcase: filebench
version: filebench-x86_64-22620e6-1_20221010
with following parameters:

	fs: xfs
	test: filemicro_statfile.f
	cpufreq_governor: performance



compiler: gcc-12
test machine: 96 threads 2 sockets Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz (Cascade Lake) with 128G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)




If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202308232106.50c8f492-oliver.sang@intel.com


[    6.738560][    T1] pci 0000:17:00.0: Bridge has subordinate 0x19 but max busn 0x39, reconfiguring
...
[  238.092454][ T1230] ls: cannot access '/dev/nvme1n1p1': No such file or directory
[  238.092457][ T1230]
[  238.526845][ T1230] disk number 2 mismatch with 1 real disks: /dev/nvme1n1p1 /dev/nvme0n1p1


before this commit, we have below two disks on server:

# ls -l /dev/disk/by-path/
lrwxrwxrwx 1 root root  13 Aug 23 23:00 pci-0000:83:00.0-nvme-1 -> ../../nvme0n1
lrwxrwxrwx 1 root root  15 Aug 23 23:00 pci-0000:83:00.0-nvme-1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root  13 Aug 23 23:00 pci-0000:84:00.0-nvme-1 -> ../../nvme1n1
lrwxrwxrwx 1 root root  15 Aug 23 23:00 pci-0000:84:00.0-nvme-1-part1 -> ../../nvme1n1p1

but after this commit, there is no nvme1n1p1 detected



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230823/202308232106.50c8f492-oliver.sang@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  parent reply	other threads:[~2023-08-23 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  5:19 [PATCH] PCI: Allocate maximum available buses to help extending the daisy chain Sanath S
2023-08-16 13:18 ` Sanath S
2023-08-17 10:24   ` Mika Westerberg
2023-08-18  3:31     ` Sanath S
2023-08-18  4:56       ` Mika Westerberg
2023-08-22 14:36         ` Maciej W. Rozycki
2023-08-23 14:15 ` kernel test robot [this message]
2023-12-08 22:24 ` Bjorn Helgaas
2023-12-08 22:29   ` Mario Limonciello
2023-12-08 22:44     ` Bjorn Helgaas
2023-12-11 21:48       ` Mario Limonciello
2023-12-12 20:54         ` 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=202308232106.50c8f492-oliver.sang@intel.com \
    --to=oliver.sang@intel.com \
    --cc=Sanath.S@amd.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mario.limonciello@amd.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=sanju.mehta@amd.com \
    /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