Project

General

Profile

Bug #4911

AES-NI hardware crypto not always displayed in information widget

Added by Denny Page over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Web Interface
Target version:
Start date:
07/30/2015
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

The /var/log/dmesg.boot snapshot file appears to be created too early in the boot process resulting in hardware crypto information being missing from the snapshot.

Attached are the /var/log/dmesg.boot file and the output of dmesg from my SG-4860.

dmesg.boot (8.46 KB) dmesg.boot /var/log/dmesg.boot Denny Page, 07/30/2015 08:32 PM
dmesg.out (9.09 KB) dmesg.out Output of /sbin/dmesg Denny Page, 07/30/2015 08:32 PM

History

#1 Updated by Kill Bill over 4 years ago

Guys, this "method" is really pathetic. Not having things like /proc/cpuinfo does not help here, but what's exactly wrong with dmidecode at least as fallback method?

#2 Updated by Chris Buechler over 4 years ago

  • Subject changed from Hardware crypto not displayed in information widget to AES-NI hardware crypto not always displayed in information widget
  • Category set to Web Interface
  • Status changed from New to Confirmed
  • Priority changed from Normal to Low
  • Affected Version changed from 2.2.4 to All

It's definitely less than ideal, especially given it doesn't reliably work. dmidecode is not an alternative though, as it doesn't show AES-NI capability. Even if it did, it wouldn't tell whether or not it's enabled.

#3 Updated by Luiz Souza about 4 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

Fixed in 2.3 (at least for AESNI - other types of hardware accelerators may need similar changes).

#4 Updated by Chris Buechler about 4 years ago

  • Status changed from Feedback to Resolved
  • Target version set to 2.3

fixed

Also available in: Atom PDF