From: Meelis Roos <mroos@linux.ee>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: 4.3-rc3 BAR allocation problems on multiple machines
Date: Wed, 7 Oct 2015 12:25:19 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510071147520.8345@math.ut.ee> (raw)
First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation
was failing for qla1280 scsi driver. Reading dmesg uncovered "can't
claim BAR" errors. Looking for this in my other test machines I see more
of them - on many sparc64 machines and some on x86.
In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu
asked for full dmesg to solve another similar case. So to help
understanding this one, here are the dmesgs of my machines:
sparc64 machines:
http://kodu.ut.ee/~mroos/dm/dm.t1-105
http://kodu.ut.ee/~mroos/dm/dm.t1-200
http://kodu.ut.ee/~mroos/dm/dm.v120
http://kodu.ut.ee/~mroos/dm/dm.v210
http://kodu.ut.ee/~mroos/dm/dm.v240
http://kodu.ut.ee/~mroos/dm/dm.sb100
amd64 machine:
http://kodu.ut.ee/~mroos/dm/dm.x2100
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2015-10-07 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 9:25 Meelis Roos [this message]
2015-10-07 22:49 ` 4.3-rc3 BAR allocation problems on multiple machines Yinghai Lu
2015-10-12 13:04 ` Meelis Roos
2015-10-12 22:55 ` Yinghai Lu
2015-10-13 5:06 ` Meelis Roos
2015-10-13 5:43 ` Yinghai Lu
2015-10-13 6:21 ` Yinghai Lu
2015-10-13 7:32 ` Meelis Roos
2015-10-13 19:30 ` Yinghai Lu
2015-10-13 19:43 ` Yinghai Lu
2015-10-13 20:39 ` Meelis Roos
2015-10-14 0:43 ` Yinghai Lu
2015-10-14 7:34 ` Meelis Roos
2015-10-14 21:45 ` Yinghai Lu
2015-10-13 6:19 ` Yinghai Lu
2015-10-07 23:16 ` Yinghai Lu
2015-10-08 14:47 ` Bjorn Helgaas
2016-10-26 21:50 ` Bjorn Helgaas
2016-10-27 15:35 ` Meelis Roos
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=alpine.LRH.2.20.1510071147520.8345@math.ut.ee \
--to=mroos@linux.ee \
--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