The update_excuses page for jammy is currently outdated (Dec. 4th)
and I'm asking for it to be looked at by the responsible team.
Considering what is already there and in the pending-sru page,
plus other checks, only autopkgtests still need to be verified.
I did that manually with the autopkgtests database, as below.
All triggered tests have an interpreted result of NEUTRAL/8,
and manually checking the logs confirm they all PASS.
Thanks!
Steps:
wget https://autopkgtest.ubuntu.com/static/autopkgtest.db
wget https://autopkgtest.ubuntu.com/static/autopkgtest.db.sha256
$ sha256sum autopkgtest.db
a5ca4032ec1304bd0b3dd2357b1ad37e4f36a0e3141a27b5749c77e42234d1a8
autopkgtest.db
$ cat autopkgtest.db.sha256
a5ca4032ec1304bd0b3dd2357b1ad37e4f36a0e3141a27b5749c77e42234d1a8
RELEASE=jammy
TRIGGER=dmidecode/3.3-3ubuntu0.2
sqlite3 autopkgtest.db -column -header \
"SELECT test.release, test.arch, test.package, "\
" result.version, result.exitcode, "\
" result.triggers, result.requester "\
"FROM test, result "\
"WHERE test.id = result.test_id "\
"AND test.release = '${RELEASE}' "\
"AND result.triggers LIKE '%${TRIGGER}%' "\
"ORDER BY test.release, test.package, test.arch"
Output:
release arch package version exitcode triggers
requester
------- ------- --------- ------- --------
------------------------ ---------
jammy amd64 virt-what 1.21-1 8 dmidecode/3.3-3ubuntu0.2
jammy arm64 virt-what 1.21-1 8 dmidecode/3.3-3ubuntu0.2
jammy armhf virt-what 1.21-1 8 dmidecode/3.3-3ubuntu0.2
jammy ppc64el virt-what 1.21-1 8 dmidecode/3.3-3ubuntu0.2
jammy s390x virt-what 1.21-1 8 dmidecode/3.3-3ubuntu0.2
Looking at the results page for virt-what [1], the exit code 8 means
"NEUTRAL".
Looking at the results page for each architecture, and the test logs,
all are "PASS".
virt-what [jammy/amd64]
1.21-1 dmidecode/3.3-3ubuntu0.2 2024-11-25
23:07:04 UTC 0h 01m 16s - neutral
08935e5d-4610-4b4a-a224-3493d42dc600 log artifacts ♻
63s autopkgtest [23:06:51]: @@@@@@@@@@@@@@@@@@@@ summary
63s command1 PASS (superficial)
virt-what [jammy/arm64]
1.21-1 dmidecode/3.3-3ubuntu0.2 2024-11-25
23:07:28 UTC 0h 01m 40s - neutral
8f363069-2253-4541-9646-40647f718084 log artifacts ♻
88s autopkgtest [23:07:16]: @@@@@@@@@@@@@@@@@@@@ summary
88s command1 PASS (superficial)
virt-what [jammy/armhf]
1.21-1 dmidecode/3.3-3ubuntu0.2 2024-11-25
23:09:06 UTC 0h 03m 18s - neutral 7d787447-b38c-43db-
ab30-201731b26638 log artifacts ♻
194s autopkgtest [23:09:02]: @@@@@@@@@@@@@@@@@@@@ summary
194s command1 PASS (superficial)
virt-what [jammy/ppc64el]
1.21-1 dmidecode/3.3-3ubuntu0.2 2024-11-25
23:18:04 UTC 0h 12m 15s - neutral
7cb956f1-7837-4784-9b55-0cdadcb78941 log artifacts ♻
724s autopkgtest [23:17:52]: @@@@@@@@@@@@@@@@@@@@ summary
724s command1 PASS (superficial)
virt-what [jammy/s390x]
1.21-1 dmidecode/3.3-3ubuntu0.2 2024-11-25
23:07:09 UTC 0h 01m 20s - neutral
709ba438-635d-4601-ac07-db30e6e2d3d5 log artifacts ♻
69s autopkgtest [23:06:57]: @@@@@@@@@@@@@@@@@@@@ summary
69s command1 PASS (superficial)
[1] https://autopkgtest.ubuntu.com/packages/virt-what
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/2081611
Title:
Add processor support from SMBIOS 3.6.0 in Jammy and Noble
Status in dmidecode package in Ubuntu:
Fix Released
Status in dmidecode source package in Jammy:
Fix Released
Status in dmidecode source package in Noble:
Fix Released
Bug description:
[Impact]
* Add processor support from SMBIOS 3.6.0 in Jammy and Noble
to enable new hardware in LTS release per SRU policy [1].
* Backport of 1 relatively simple patch from dmidecode 3.6
in Oracular to dmidecode 3.3 in Jammy and dmidecode 3.5 in Noble
[Test Plan]
* Check no regressions on current systems with SMBIOS < 3.6,
i.e., no output changes in text and binary form.
$ sudo dmidecode > old.txt 2>&1
$ sudo dmidecode --dump-bin old.bin
$ apt install dmidecode # modified package
$ sudo dmidecode > new.txt 2>&1
$ sudo dmidecode --dump-bin new.bin
$ cmp old.txt new.txt; echo $?
0
$ cmp old.bin new.bin; echo $?
0
* Check for expected output on new systems with SMBIOS >= 3.6.
$ diff old.txt new.txt
1) Run "sudo dmidecode -t4"
2) Observe that the "Thread Enabled" field is being reported
[1] https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/requirements/#other-safe-cases
[Where problems could occur]
* The patch adds support for new bits/codes/strings,
so there are no changes expected for the old spec support.
* The new field (Thread Enabled) is added in a specific condition
and should not impact systems without support to it.
* If the current dmidecode is being used on systems that support
the new bits, users will see a different output, and this might
break some text parsers if they are strictly programmed. Using the
binary output is recommended in these cases.
[Patch Details]
https://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=ac65cf23af7cccecb4175d3c13460928e8e2f51d
Commit ac65cf23af7cccecb4175d3c13460928e8e2f51d
Author: Jean Delvare <jdelv...@suse.de>
Date: Fri May 26 17:41:51 2023 +0200
dmidecode: Add processor support from SMBIOS 3.6.0
SMBIOS 3.6.0 adds the following to the Processor Information
structure (type 4):
* 9 socket types
* 1 processor family
* 1 field (Thread Enabled)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2081611/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
