NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-amd64/46833: NetBSD 6.0_BETA2 shutdowns under load
The following reply was made to PR port-amd64/46833; it has been noted by GNATS.
From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: port-amd64/46833: NetBSD 6.0_BETA2 shutdowns under load
Date: Mon, 27 Aug 2012 23:31:36 +0000 (UTC)
bouyer%antioche.eu.org@localhost (Manuel Bouyer) writes:
>On Mon, Aug 27, 2012 at 08:59:45AM +0200, Francois Tigeot wrote:
>> On Mon, Aug 27, 2012 at 01:25:02AM +0000, Mark Davies wrote:
>> >
>> > Not sure if this helps at all but all my poweredge r610's have
>> > complained from boot
>> > ipmi0: critical over limit on 'Temp6'
>> > since I've had them (a full envstat is below)
>> > I've never worried about it as it didn't seem to actually be an issue,
>> > over several years of running, and when you look at temperatures in
>> > the DRAC it doesn't even list Temp6 so assumed it was a bogus sensor.
>>
>> What makes me think the most the reports are bogus in my case is the
>> actual hardware doesn't give a damn:
>Another option is that the limits reported by hardware are bogus,
>and the BIOS/firmware doesn't take care about them.
When you query a poweredge r610 with IPMI, it reports 7 sensors
named 'Temp', all are in the state 'Disabled' and ipmitool says that
no readout is available (but some thresholds are).
The only temperature sensor reporting something is one of the three
'Ambient Temp' sensors.
Temp | na | degrees C | na | na | na |
na | 85.000 | 90.000 | na
Temp | na | degrees C | na | na | na |
na | 85.000 | 90.000 | na
Temp | na | degrees C | na | 64.000 | na |
-128.000 | -128.000 | na | na
Ambient Temp | na | degrees C | na | 64.000 | na |
-128.000 | -128.000 | na | na
Temp | na | degrees C | na | 64.000 | na |
-128.000 | -128.000 | na | na
Ambient Temp | na | degrees C | na | 64.000 | na |
-128.000 | -128.000 | na | na
Ambient Temp | 21.000 | degrees C | ok | na | 3.000 |
8.000 | 42.000 | 47.000 | na
Planar Temp | na | degrees C | na | na | 3.000 |
8.000 | 92.000 | 97.000 | na
Temp | na | degrees C | na | na | na |
na | na | na | na
Temp | na | degrees C | na | na | 3.000 |
8.000 | 42.000 | 47.000 | na
Temp | na | degrees C | na | na | 3.000 |
8.000 | 42.000 | 47.000 | na
Temp | 01h | ns | 3.1 | Disabled
Temp | 02h | ns | 3.2 | Disabled
Temp | 05h | ns | 10.1 | Disabled
Ambient Temp | 07h | ns | 10.1 | Disabled
Temp | 06h | ns | 10.2 | Disabled
Ambient Temp | 08h | ns | 10.2 | Disabled
Ambient Temp | 0Eh | ok | 7.1 | 21 degrees C
Planar Temp | 0Fh | ns | 7.1 | Disabled
CPU Temp Interf | 76h | ns | 7.1 | Disabled
Temp | 0Ah | ns | 8.1 | Disabled
Temp | 0Bh | ns | 8.1 | Disabled
Temp | 0Ch | ns | 8.1 | Disabled
Entities 3.1/3.2 are the CPUs
Entities 10.1/10.2 are the Riser cards
Entity 7.1 is the system board
Entity 8.1 is unspecified
So it looks like our driver doesn't ignore the disabled state correctly.
--
--
Michael van Elst
Internet: mlelstv%serpens.de@localhost
"A potential Snark may lurk in every tree."
Home |
Main Index |
Thread Index |
Old Index