Ubuntu
linux package

libgnutls report "trap invalid opcode" when trying to install packages over https

Bug #2031093 reported by Po-Hsu Lin on 2023-08-11

This bug affects 3 people

	Status	Importance	Assigned to
ubuntu-kernel-tests	New	Undecided	Unassigned
gnutls28 (Ubuntu)	Confirmed	Undecided	Unassigned
Focal	Confirmed	High	Unassigned
Jammy	Confirmed	High	Unassigned
Lunar	Confirmed	High	Unassigned
linux (Ubuntu)	Confirmed	Undecided	Thadeu Lima de Souza Cascardo
Focal	Fix Released	Critical	Thadeu Lima de Souza Cascardo
Jammy	Fix Released	Critical	Thadeu Lima de Souza Cascardo
Lunar	Fix Released	Critical	Thadeu Lima de Souza Cascardo

Bug Description

[Impact]
When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git.

[Test case]
git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
Cloning into 'autotest-client-tests'...
error: git-remote-https died of signal 4

dmesg:
[ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000]

Works fine with the mitigation disabled by default.

[Potential regressions]
Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys.

-------------------------------------------------

When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with:
E: Method https has died unexpectedly!
E: Sub-process https received signal 4.

$ sudo apt install linux-libc-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
linux-libc-dev
0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded.
Need to get 1353 kB of archives.
After this operation, 6943 kB of additional disk space will be used.
E: Method https has died unexpectedly!
E: Sub-process https received signal 4.

From dmesg you will see:
[ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000]

Also, git clone is not working as well.

$ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
Cloning into 'autotest-client-tests'...
error: git-remote-https died of signal 4

dmesg:
[ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000]

libgnutls30 version:3.7.3-4ubuntu1.2

See original description

Tags:

Po-Hsu Lin (cypressyew) on 2023-08-11

description:

updated

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2023-08-11:

This issue does not exist with 5.15.0.78 nor 5.15.0-79

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2023-08-11:

This is also affecting the r5.metal on AWS cloud.

Revision history for this message

Stefan Bader (smb) wrote on 2023-08-11:

Would be worth checking 5.15.0-80.89 as well as soon as possible.

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2023-08-11:

Tested with 5.15.0-80-generic #89 on Oracle BM.Standard2.52, this issue originate from there:
$ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
Cloning into 'autotest-client-tests'...
error: git-remote-https died of signal 4
$ uname -a
Linux j-l-gen-5-15-bmstd252-u-zfs-smk-test-611299 5.15.0-80-generic #89-Ubuntu SMP Wed Aug 9 18:52:43 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

dmesg:
[ 200.266224] traps: git-remote-http[2617] trap invalid opcode ip:7f5e2521544a sp:7ffd7e197480 error:0 in libgnutls.so.30.31.0[7f5e250ee000+129000]
[ 203.425690] traps: https[2681] trap invalid opcode ip:7f056580b6be sp:7fffe68285c0 error:0 in libgnutls.so.30.31.0[7f05656e9000+129000]
[ 203.603751] traps: https[2691] trap invalid opcode ip:7f4b9c1d644a sp:7fff00312480 error:0 in libgnutls.so.30.31.0[7f4b9c0af000+129000]
[ 266.638059] traps: https[2906] trap invalid opcode ip:7f26cb07944a sp:7fffc1ab2c80 error:0 in libgnutls.so.30.31.0[7f26caf52000+129000]
[ 266.839155] traps: https[2896] trap invalid opcode ip:7f100f1346be sp:7ffd8453e9c0 error:0 in libgnutls.so.30.31.0[7f100f012000+129000]

Thadeu Lima de Souza Cascardo (cascardo) on 2023-08-11

Changed in linux (Ubuntu):
assignee:	nobody → Thadeu Lima de Souza Cascardo (cascardo)
Changed in linux (Ubuntu Focal):
assignee:	nobody → Thadeu Lima de Souza Cascardo (cascardo)
Changed in linux (Ubuntu Jammy):
assignee:	nobody → Thadeu Lima de Souza Cascardo (cascardo)
Changed in linux (Ubuntu Lunar):
assignee:	nobody → Thadeu Lima de Souza Cascardo (cascardo)
importance:	Undecided → High
Changed in linux (Ubuntu Jammy):
importance:	Undecided → Critical
Changed in linux (Ubuntu Lunar):
importance:	High → Critical
Changed in linux (Ubuntu Focal):
importance:	Undecided → Critical
status:	New → In Progress
Changed in linux (Ubuntu Jammy):
status:	New → In Progress
Changed in linux (Ubuntu Lunar):
status:	New → In Progress
Changed in gnutls28 (Ubuntu Jammy):
importance:	Undecided → High
description:	updated

Thadeu Lima de Souza Cascardo (cascardo) on 2023-08-11

summary:

- libgnutls report "trap invalid opcode" when trying to install linux-
- libc-dev on Oracle BM.Standard2.52 with Jammy
+ libgnutls report "trap invalid opcode" when trying to install packages
+ over https

Revision history for this message

Tobias Heider (tobhe) wrote on 2023-08-13:

Could that be https://gitlab.com/gnutls/gnutls/-/issues/1282?

Roxana Nicolescu (roxanan) on 2023-08-14

Changed in linux (Ubuntu Focal):
status:	In Progress → Fix Committed

Stefan Bader (smb) on 2023-08-14

Changed in gnutls28 (Ubuntu Focal):
importance:	Undecided → High
Changed in gnutls28 (Ubuntu Lunar):
importance:	Undecided → High
Changed in linux (Ubuntu Jammy):
status:	In Progress → Fix Committed
Changed in linux (Ubuntu Lunar):
status:	In Progress → Fix Committed

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-08-15:

This bug is awaiting verification that the linux/6.2.0-32.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar-linux' to 'verification-failed-lunar-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-08-16:

This bug is awaiting verification that the linux/5.4.0-162.179 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal-linux' to 'verification-failed-focal-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-08-16:

This bug is awaiting verification that the linux/5.15.0-83.92 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-08-18:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnutls28 (Ubuntu Focal):
status:	New → Confirmed
Changed in gnutls28 (Ubuntu Jammy):
status:	New → Confirmed
Changed in gnutls28 (Ubuntu Lunar):
status:	New → Confirmed
Changed in gnutls28 (Ubuntu):
status:	New → Confirmed
Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Birgit Edel (biredel) wrote on 2023-08-18 (last edit on 2023-10-13):

#14

Whether the automatic mitigation strategy or manual kernel command line configuration has decided to stop using AVX, outcome appears indistinguishable: GnuTLS break just the same.

Keywords:
clearcpuid=156 clearcpuid=avx (same, just more readable on 5.19+)
setup_clear_cpu_cap(X86_FEATURE_AVX)
CONFIG_GDS_FORCE_MITIGATION
GDS_MITIGATION_FORCE
/sys/devices/system/cpu/vulnerabilities/gather_data_sampling: Mitigation: AVX disabled, no microcode
dmesg: Microcode update needed! Disabling AVX as mitigation.

Workaround: The broken GnuTLS feature can be disabled by adding GNUTLS_CPUID_OVERRIDE=0x1 to the environment of the respective shell or service.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-08-28:

#15

This bug was fixed in the package linux - 5.4.0-159.176

---------------
linux (5.4.0-159.176) focal; urgency=medium

* focal/linux: 5.4.0-159.176 -proposed tracker (LP: #2031149)

  * libgnutls report "trap invalid opcode" when trying to install packages over
    https (LP: #2031093)
    - [Config]: disable CONFIG_GDS_FORCE_MITIGATION

  * Fix boot test warning for log_check "CPU: 0 PID: 0 at
    arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
    - x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to init_fpstate")

-- Thadeu Lima de Souza Cascardo <email address hidden> Mon, 14 Aug 2023 08:18:30 -0300

Changed in linux (Ubuntu Focal):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-08-28:

#16

This bug was fixed in the package linux - 5.15.0-82.91

---------------
linux (5.15.0-82.91) jammy; urgency=medium

* jammy/linux: 5.15.0-82.91 -proposed tracker (LP: #2031147)

  * libgnutls report "trap invalid opcode" when trying to install packages over
    https (LP: #2031093)
    - [Config]: disable CONFIG_GDS_FORCE_MITIGATION

-- Thadeu Lima de Souza Cascardo <email address hidden> Mon, 14 Aug 2023 10:31:08 -0300

Changed in linux (Ubuntu Jammy):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-08-28:

#17

This bug was fixed in the package linux - 6.2.0-31.31

---------------
linux (6.2.0-31.31) lunar; urgency=medium

* lunar/linux: 6.2.0-31.31 -proposed tracker (LP: #2031146)

  * libgnutls report "trap invalid opcode" when trying to install packages over
    https (LP: #2031093)
    - [Config]: disable CONFIG_GDS_FORCE_MITIGATION

-- Thadeu Lima de Souza Cascardo <email address hidden> Mon, 14 Aug 2023 08:29:52 -0300

Changed in linux (Ubuntu Lunar):
status:	Fix Committed → Fix Released

Revision history for this message

Birgit Edel (biredel) wrote on 2023-08-29:

#18

Is there a way to have either launchpad or snapd track the status in snap-managed library hardcopies?

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-08-30:

#19

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-6.2-v2 verification-needed-jammy-linux-nvidia-6.2

Roxana Nicolescu (roxanan) on 2023-09-01

tags:

added: verification-done-focal-linux
removed: verification-needed-focal-linux

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-05:

#20

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1017.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-06:

#21

This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done-lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed-lunar-linux-starfive'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-07:

#22

This bug is awaiting verification that the linux-azure/5.15.0-1047.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-linux-azure'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-08:

#23

This bug is awaiting verification that the linux-intel-iotg/5.15.0-1039.45 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-done-jammy-linux-intel-iotg'. If the problem still exists, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-failed-jammy-linux-intel-iotg'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-intel-iotg-v2 verification-needed-jammy-linux-intel-iotg

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-09:

#24

This bug is awaiting verification that the linux-aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-09:

#25

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-10:

#26

This bug is awaiting verification that the linux-riscv-5.15/5.15.0-1041.45~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-riscv-5.15' to 'verification-failed-focal-linux-riscv-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-riscv-5.15-v2 verification-needed-focal-linux-riscv-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-11:

#27

This bug is awaiting verification that the linux-raspi/5.15.0-1038.41 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-linux-raspi'. If the problem still exists, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-12:

#28

This bug is awaiting verification that the linux-azure/5.4.0-1117.124 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal-linux-azure'. If the problem still exists, change the tag 'verification-needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-12:

#29

This bug is awaiting verification that the linux-azure/6.2.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar-linux-azure'. If the problem still exists, change the tag 'verification-needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-13:

#30

This bug is awaiting verification that the linux-bluefield/5.4.0-1071.77 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-done-focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed-focal-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-15:

#31

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-09-15:

#32

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1017.17~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-tegra-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15

Revision history for this message

Bartlomiej Zolnierkiewicz (bzolnier) wrote on 2023-09-20:

#33

bluefield is arm64 only kernel and this bug is x86 specific.

tags:

added: verification-done-focal-linux-bluefield
removed: verification-needed-focal-linux-bluefield

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-10-03:

#34

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1024.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-10-05:

#35

This bug is awaiting verification that the linux-aws/5.15.0-1048.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy-linux-aws'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2023-10-09:

#36

This bug is awaiting verification that the linux-azure/4.15.0-1170.185~14.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty-linux-azure' to 'verification-done-trusty-linux-azure'. If the problem still exists, change the tag 'verification-needed-trusty-linux-azure' to 'verification-failed-trusty-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-trusty-linux-azure-v2 verification-needed-trusty-linux-azure

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2023-10-30:

#37

This issue has gone, repos can be cloned and packages can be installed now.

tags:	added: verification-done-jammy-linux-raspi verification-done-jammy-linux-xilinx-zynqmp verification-done-lunar-linux verification-done-lunar-linux-azure verification-done-lunar-linux-starfive verification-done-trusty-linux-azure removed: verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp verification-needed-lunar-linux verification-needed-lunar-linux-azure verification-needed-lunar-linux-starfive verification-needed-trusty-linux-azure
tags:	added: verification-done-focal-linux-riscv-5.15 verification-done-jammy-linux removed: verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux
tags:	added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-azure verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-6.2 verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-azure verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-6.2 verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

auto-gitlab.com-gnutls-gnutls-- #1282
[closed triaged::bug] Edit

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

libgnutls report "trap invalid opcode" when trying to install packages over https

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
linux package