From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Reading SPD on Intel Patsburg on Supermicro X9SRG-F board
Date: Thu, 30 Jan 2014 04:31:19 +0000 [thread overview]
Message-ID: <52E9D597.4000201@roeck-us.net> (raw)
In-Reply-To: <87E51E09-C340-4A00-9DF2-1673EDF47F45@badgerous.net>
On 01/29/2014 07:39 PM, Alun Evans wrote:
>
> On 29 Jan 2014, at 17:42, Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On Wed, Jan 29, 2014 at 05:30:14PM -0800, Guenter Roeck wrote:
>>> On Wed, Jan 29, 2014 at 05:12:48PM -0800, Alun Evans wrote:
>>>>
>>>> On 29 Jan 2014, at 11:48, Alun Evans <alun@badgerous.net> wrote:
>>>>
>>>>> Thanks for the responses everyone, inline,
>>>>>
>>>>> On 29 Jan 2014, at 10:25, Guenter Roeck <linux@roeck-us.net> wrote:
>>>>>
>>>>>> On Wed, Jan 29, 2014 at 05:42:24PM +0100, Jean Delvare wrote:
>>>>>>> Hi Alun,
>>>>>>> <snip>
>>>>>>
>>>>>>> Please ask Supermicro about it.
>>>>>
>>>>> I have put a request in… We’ll see if I get a response.
>>>>>
>>>>>>> If the memory slots are behind an I2C
>>>>>>> multiplexer, ask them if the multiplexer is I2C-based or GPIO-based. If
>>>>>>> I2C-based, ask for the multiplexer type and address. If GPIO-based, ask
>>>>>>> for the chip name and pin numbers for the GPIOs. In both case, please
>>>>>>> ask which GPIO combinations map to which memory slots.
>>>>
>>>> I inlined the above hunk with my question, and the first response was:
>>>>
>>>>> Received feedback; The memory address does not use mux. It is hardware defined by Intel.
>>>>
>>>> So I went and clarified I was not talking about the DDR physical address setup by the memory reference code, and I got:
>>>>
>>>>> Per our engineer; There is no hardware connecting to DIMM.
>>>>
>>>> I’m not sure I’ve found the right help here...
>>>>
>>> Actually you might have. On some HW the DIMMs are connceted to a separate
>>> SMBus channel which is not visible to SW.
>>>
>> I had a quick glance into the Patsburg (c600) datasheet. The chip has
>> up to four SMBus channels, depending on chip variant. Are you sure
>> that you are talking to the correct one ? What do you see with lspci ?
>
> I am talking to that one:
>
> $ sudo lspci -v -v -v -s 0000:00:1f.3
> 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 05)
> Subsystem: Super Micro Computer Inc Device 0661
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Interrupt: pin C routed to IRQ 18
> Region 0: Memory at fba20000 (64-bit, non-prefetchable) [size=256]
> Region 4: I/O ports at 1180 [size=32]
> Kernel driver in use: i801_smbus
> Kernel modules: i2c-i801
>
Anything else that looks like an SMBus controller ? The datasheet says that "SRV/WS SKUs Only"
would have additional SMBus controllers.
> Whether or not the DIMMs are connected to it is a good question.
>
> It’s a C602:
> http://www.supermicro.com/products/motherboard/xeon/c600/x9srg-f.cfm
>
>
> Thinking about it, this Xeon has an integrated memory controller with 4 DDR3 channels, each of which can have 3 DIMMs per channel. That’s potentially 12 DIMMs on a board, which exceeds the 8 addressable SPDs given the 3 pins for addressing (SA{0-2}). While this board only has 8 DIMMs, it would make some sense if they were split in half with a mux somewhere.
>
Presumably there must be a means for the BIOS to read the SPD data to be able to
program the DRAM controller correctly. No idea how that works in detail, though.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2014-01-30 4:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 4:57 [lm-sensors] Reading SPD on Intel Patsburg on Supermicro X9SRG-F board Alun Evans
2014-01-29 16:42 ` Jean Delvare
2014-01-29 18:25 ` Guenter Roeck
2014-01-29 19:48 ` Alun Evans
2014-01-29 19:55 ` Jean Delvare
2014-01-29 22:21 ` Alun Evans
2014-01-30 1:12 ` Alun Evans
2014-01-30 1:30 ` Guenter Roeck
2014-01-30 1:42 ` Guenter Roeck
2014-01-30 3:23 ` Alun Evans
2014-01-30 3:39 ` Alun Evans
2014-01-30 4:14 ` Alun Evans
2014-01-30 4:31 ` Guenter Roeck [this message]
2014-01-30 17:01 ` Jean Delvare
2014-01-30 18:52 ` Alun Evans
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=52E9D597.4000201@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lm-sensors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.