From: maurilio.longo@libero.it
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Tue, 20 Feb 2024 03:58:59 -0500 [thread overview]
Message-ID: <17084195390.7Be2F8Bc.38165@composer.illumos.topicbox-beta.com> (raw)
In-Reply-To: <17083772470.e500A6BA.762619@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
After googling around about my problems I've made two changes, the first one was to upgrade the controller firmware from 52.16.3-3913, dated April 2021, to the lastest one, 52.26.3-5250_A, dated December 2023.
Then, given several reports of HPE Gen10 units rebooting unexpectedly all suggesting to change the workload profile to max performance, I did this change to the BIOS, loosing SpeedStep, as it appears from /var/adm/messages.
Feb 20 09:20:33 pg-1 unix: [ID 950921 kern.info] cpu1: x86 (chipid 0x0 GenuineIntel A0671 family 6 model 167 step 1 clock 2807 MHz)
Feb 20 09:20:33 pg-1 unix: [ID 950921 kern.info] cpu1: Intel(r) Xeon(r) E-2314 CPU @ 2.80GHz
Feb 20 09:20:33 pg-1 unix: [ID 557947 kern.info] cpu1 initialization complete - online
Feb 20 09:20:33 pg-1 unix: [ID 977644 kern.info] NOTICE: cpu_acpi: _TSS package bad count 1 for CPU 2.
Feb 20 09:20:33 pg-1 unix: [ID 340435 kern.info] NOTICE: Support for CPU throttling is being disabled due to errors parsing ACPI T-state objects exported by BIOS.
Feb 20 09:20:33 pg-1 unix: [ID 950921 kern.info] cpu2: x86 (chipid 0x0 GenuineIntel A0671 family 6 model 167 step 1 clock 2807 MHz)
Feb 20 09:20:33 pg-1 unix: [ID 950921 kern.info] cpu2: Intel(r) Xeon(r) E-2314 CPU @ 2.80GHz
Feb 20 09:20:33 pg-1 unix: [ID 557947 kern.info] cpu2 initialization complete - online
Feb 20 09:20:33 pg-1 unix: [ID 977644 kern.info] NOTICE: cpu_acpi: _TSS package bad count 1 for CPU 3.
Feb 20 09:20:33 pg-1 unix: [ID 340435 kern.info] NOTICE: Support for CPU throttling is being disabled due to errors parsing ACPI T-state objects exported by BIOS.
Restarted iozone, let's see if something improves or not.
Regards.
Maurilio.
[-- Attachment #2: Type: text/html, Size: 4554 bytes --]
next prev parent reply other threads:[~2024-02-20 8:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:31 maurilio.longo
2024-02-07 11:14 ` [developer] " Peter Tribble
2024-02-07 11:16 ` Hans Rosenfeld
2024-02-07 11:46 ` maurilio.longo
2024-02-07 12:04 ` maurilio.longo
2024-02-07 12:29 ` Hans Rosenfeld
2024-02-07 13:01 ` maurilio.longo
2024-02-07 16:47 ` maurilio.longo
2024-02-07 17:01 ` Hans Rosenfeld
2024-02-07 21:35 ` Hans Rosenfeld
2024-02-08 7:59 ` maurilio.longo
2024-02-08 10:42 ` Hans Rosenfeld
2024-02-08 11:01 ` maurilio.longo
2024-02-09 8:06 ` maurilio.longo
2024-02-09 19:55 ` Hans Rosenfeld
2024-02-09 20:36 ` maurilio.longo
2024-02-12 8:11 ` maurilio.longo
2024-02-13 19:32 ` Hans Rosenfeld
2024-02-13 20:55 ` maurilio.longo
2024-02-13 21:03 ` maurilio.longo
2024-02-15 6:50 ` maurilio.longo
2024-02-15 7:38 ` Carsten Grzemba
2024-02-15 8:11 ` Toomas Soome
2024-02-15 9:44 ` maurilio.longo
2024-02-16 14:36 ` maurilio.longo
2024-02-16 15:20 ` maurilio.longo
2024-02-16 15:27 ` maurilio.longo
2024-02-16 15:42 ` Robert Mustacchi
2024-02-16 20:41 ` maurilio.longo
2024-02-19 21:14 ` maurilio.longo
2024-02-20 8:58 ` maurilio.longo [this message]
2024-02-22 17:44 ` maurilio.longo
2024-02-26 8:59 ` maurilio.longo
2024-02-26 9:30 ` Carsten Grzemba
2024-08-26 12:30 ` manipm
2024-08-26 15:23 ` Hans Rosenfeld
2024-02-13 19:23 ` Hans Rosenfeld
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=17084195390.7Be2F8Bc.38165@composer.illumos.topicbox-beta.com \
--to=maurilio.longo@libero.it \
--cc=developer@lists.illumos.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;
as well as URLs for NNTP newsgroup(s).