Dear Dell people,
To my surprise, the firmware (2.3.4) of the Dell PowerEdge R730 doesn’t
seem to support Suspend to RAM (STR).
```
$ more /proc/version
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2
Dear Dell PowerEdge users,
Installing Debian 9 with Linux 4.9.x and CentOS 7 with Linux 3.10.x on a
Dell PowerEdge R730.
In both versions the Linux kernel reports the errors below.
```
[…]
kernel: ipmi message handler version 39.2 kernel: IPMI System Interface
driver.
kernel: ipmi_si:
Dear Mike,
Thank you very much for your answer. (Sorry for formatting my pastes as
citations. It’s because otherwise Mozilla Thunderbird will wrap around
the lines.
On 02/16/17 18:18, Hanby, Mike wrote:
> This is from one of our R730's:
> $ omreport chassis info | egrep -i
Dear Sven,
On 08/22/16 14:16, Sven Ulland wrote:
On 08/22/2016 12:17 PM, Paul Menzel wrote:
My current suspicion is, that just a PCI ID is missing in the driver.
What is the PCI ID of your memory controller? The lspci output above
seems to have been cut before the memory controllers were
Dear Dell list administrators,
Although I have set the option *Avoid duplicate copies of messages?* to
*no* [1], I only received John’s replies once, and not twice as expected.
Could you please look into it, and fix the Mailman setup if needed?
Best regards,
Paul Menzel
[1] https
Dear John,
On 08/22/16 12:29, John Hodrien wrote:
> On Mon, 22 Aug 2016, Paul Menzel wrote:
>
>>> BMC supports all it needs to support, so fault reports will be reported
>>> via DRAC / esmlog, no?
>>
>> That’s the first time I hear about esmlog. How do
out of the
box, and it’s Dell’s job to verify that, and, if they can’t fix it,
contact Intel to fix it.
Do I need to open a separate ticket for this issue, or are Dell
employees reading this, who can bring it up with the right people?
Best regards,
Paul Menzel
PS: I am sorry
Dear John,
Thank you for your reply.
On 08/22/16 12:21, John Hodrien wrote:
> On Mon, 22 Aug 2016, Paul Menzel wrote:
>
>> That’s unacceptable for that kind of money that system costs.
>>
>> My current suspicion is, that just a PCI ID is missing in the driver.
>>
/show_bug.cgi?id=153881
Reported-by: Paul Menzel <pmen...@molgen.mpg.de>
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
---
arch/x86/pci/fixup.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
i
Dear list administrators,
Neither my reply to Sven, nor his reply made it to the list yesterday.
Other messages are delivered though. Could you please look into it?
The Message-ID header field of my undelivered message is
`3307b804-c0ee-a0a1-0520-90dd0fb9c...@molgen.mpg.de`.
Best regards,
Dear Matt,
On 04/26/18 22:55, Matt Vander Werf wrote:
I noticed that Dell released BIOS updates for R815 systems to address the
Spectre vulnerability (variant #2, CVE-2017-5715) at [1]. The new version
is 3.4.0 and the previous latest version is 3.2.2. We have quite a few R815
systems running
Dear lejeczek,
On 04/27/18 15:18, lejeczek wrote:
more importantly !! why dsu does not find this new BIOS versions - @dell
guys?
Why is your issue more important?
And, please be more polite, and do not hijack threads, and follow the
netiquette – [1] is one example.
Anyway, from the
Dear Matt,
Am 24.05.2018 um 18:22 schrieb Matt Vander Werf:
To update everyone, it appears that Dell has released a new 3.4.1 BIOS
update for R815 as of today.
It hasn't been added to the Meltdown/Spectre status page (also of course
not in DSU yet), but it can be found here:
Dear Matt,
On 04/30/18 16:44, Matt Vander Werf wrote:
I did actually test also on an R815 running Opteron 6234 as well, and
got the same result. Microcode version is different (0x600063d) but
also did not change with the update.
Thank you for sharing the information.
Systems running
14 matches
Mail list logo
