public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Lee Jones <lee.jones@linaro.org>,
	linux-kernel@vger.kernel.org,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] x86, lpc, Allow only one load of lpc_ich
Date: Wed, 03 Sep 2014 14:13:55 -0500	[thread overview]
Message-ID: <2934553.BlOlR0jvHm@petert> (raw)
In-Reply-To: <54075663.8090204@redhat.com>

> > Can you give more background on your hardware and firmware setup?
> 
> Unfortunately I cannot :(  The system isn't "mine" per se.  It is (as the
> dumps show) IBM's.

Can you look at the IBM manual and see info about which chipsets are used, and 
how they are connected?

> Are there
> 
> > physically two ICH bridges, or just one that is showing up two times due
> > to a firmware bug?
> 
> I can answer that.  There are two physical ICH bridges, and according to
> Intel one should be masked off.  We shouldn't run with two.

Interesting.  The "normal" setup I'm familiar with is multiple CPUs wired up 
to one IOH, and that IOH would be wired up to the ICH10.  There'd only be one 
ICH10 in this configuration though.  An example is on page 30 of 
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/5520-5500-chipset-ioh-datasheet.pdf  I'm not sure how it'd be possible to wire up 2 
ICH10s to one CPU?

How are you determining the number of ICH10s?  You could try running "lspci -
v" and comparing the PCI BARs on the duplicate devices.  If the duplicate PCI 
devices have the same BAR values, it would indicate that there is only one 
ICH10.  Could you send the output of "lspci -v"?

Regards,
Peter

  reply	other threads:[~2014-09-03 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 21:58 [PATCH] x86, lpc, Allow only one load of lpc_ich Prarit Bhargava
2014-09-03  7:43 ` Lee Jones
2014-09-03 10:13   ` Prarit Bhargava
2014-09-03 11:35     ` Lee Jones
2014-09-03 11:55       ` Prarit Bhargava
2014-09-03 12:19         ` Lee Jones
2014-09-03 12:23           ` Prarit Bhargava
2014-09-03 12:36             ` Lee Jones
2014-09-03 15:57             ` Guenter Roeck
2014-09-03 17:29               ` Peter Tyser
2014-09-03 17:56                 ` Prarit Bhargava
2014-09-03 19:13                   ` Peter Tyser [this message]
2014-09-03 20:08                     ` Guenter Roeck
2014-09-03 19:22                   ` Guenter Roeck

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=2934553.BlOlR0jvHm@petert \
    --to=ptyser@xes-inc.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=prarit@redhat.com \
    --cc=sameo@linux.intel.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