[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hi dhbaird - sorry, the focal backport has languished in my queue for
quite a while now. I have not been able find time to focus on it.
Another developer, patviafore, has offered to take the task off my
hands, and I believe he is hoping to start looking into it at the start
of the new year. Happy holidays to you, too :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
Confirmed
Status in linux-azure source package in Focal:
Invalid
Status in livecd-rootfs source package in Focal:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hi dhbaird - this was fixed in v2.672, v2.674, and v2.678 of the livecd-
rootfs package in groovy; however, those changes have not been
backported to focal, yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
Confirmed
Status in linux-azure source package in Focal:
Invalid
Status in livecd-rootfs source package in Focal:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
@tmolloy, thank you for circling back around. I'm glad the patches worked for you :-) Note that there are other (unrelated) packages in @waveform's PPA that may get installed with an apt upgrade. I don't know what the state of those packages are. I disabled the PPA after installing bluez, just to be sure I didn't unintentionally install the other packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
On Ubuntu 20.10 MATE on a pi400, I ran through the following steps: * Boot the Ubuntu 20.10 MATE for Pi image on a Pi 400 (Was not a fresh installation) * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez # I noticed there were other packages in the PPA that I did not install * sudo nvi /etc/apt/sources.list.d/waveform-ubuntu-pi-bluetooth-groovy.list # Comment out PPA * sudo apt update && sudo apt upgrade -y * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Pair a set of AirPods * Ensure I can hear audio through the AirPods Everything seemed to work as expected. Thank you for the patches :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
@colin-king dmesg output: [0.00] Linux version 5.8.0-1008-gcp (buildd@lgw01-amd64-043) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #8-Ubuntu SMP Thu Oct 15 12:48:27 UTC 2020 (Ubuntu 5.8.0-1008.8-gcp 5.8.14) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-1008-gcp root=PARTUUID=506f6274-5923-4632-96d5-b96445cc673c ro console=ttyS0 panic=-1 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] reserved [0.00] BIOS-e820: [mem 0x1000-0x00054fff] usable [0.00] BIOS-e820: [mem 0x00055000-0x0005] reserved [0.00] BIOS-e820: [mem 0x0006-0x00097fff] usable [0.00] BIOS-e820: [mem 0x00098000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbe11dfff] usable [0.00] BIOS-e820: [mem 0xbe11e000-0xbe120fff] ACPI data [0.00] BIOS-e820: [mem 0xbe121000-0xbe121fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe122000-0xbe2d1fff] usable [0.00] BIOS-e820: [mem 0xbe2d2000-0xbe2d9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe2da000-0xbe31afff] reserved [0.00] BIOS-e820: [mem 0xbe31b000-0xbf39afff] usable [0.00] BIOS-e820: [mem 0xbf39b000-0xbf3f2fff] reserved [0.00] BIOS-e820: [mem 0xbf3f3000-0xbf3fafff] ACPI data [0.00] BIOS-e820: [mem 0xbf3fb000-0xbf3fefff] ACPI NVS [0.00] BIOS-e820: [mem 0xbf3ff000-0xbffd] usable [0.00] BIOS-e820: [mem 0xbffe-0xbfff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00013fff] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.70 by EDK II [0.00] efi: TPMFinalLog=0xbe2d2000 ACPI=0xbf3fa000 ACPI 2.0=0xbf3fa014 SMBIOS=0xbf3cd000 MEMATTR=0xbe6d3698 RNG=0xbf3cec98 TPMEventLog=0xbd8b6018 [0.00] efi: seeding entropy pool [0.00] random: fast init done [0.00] secureboot: Secure boot disabled [0.00] SMBIOS 2.4 present. [0.00] DMI: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 45401001, primary cpu clock [0.00] kvm-clock: using sched offset of 8055433513 cycles [0.03] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.05] tsc: Detected 2300.000 MHz processor [0.89] e820: update [mem 0x-0x0fff] usable ==> reserved [0.91] e820: remove [mem 0x000a-0x000f] usable [0.96] last_pfn = 0x14 max_arch_pfn = 0x4 [0.000131] MTRR default type: write-back [0.000131] MTRR fixed ranges enabled: [0.000132] 0-9 write-back [0.000133] A-F uncachable [0.000134] MTRR variable ranges enabled: [0.000135] 0 base C000 mask 3FFFC000 uncachable [0.000136] 1 base 0100 mask 3F00 uncachable [0.000137] 2 disabled [0.000137] 3 disabled [0.000138] 4 disabled [0.000138] 5 disabled [0.000139] 6 disabled [0.000139] 7 disabled [0.000147] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.000157] last_pfn = 0xbffe0 max_arch_pfn = 0x4 [0.017358] check: Scanning 1 areas for low memory corruption [0.017395] Using GB pages for direct mapping [0.018424] secureboot: Secure boot disabled [0.018442] ACPI: Early table checksum verification disabled [0.018447] ACPI: RSDP 0xBF3FA014 24 (v02 Google) [0.018451] ACPI: XSDT 0xBF3F90E8 5C (v01 Google GOOGFACP 0001 0113) [0.018458] ACPI: FACP 0xBF3F4000 F4 (v02 Google GOOGFACP 0001 GOOG 0001) [0.018465] ACPI: DSDT 0xBF3F5000 0018BA (v01 Google GOOGDSDT 0001 GOOG 0001) [0.018474] ACPI: FACS 0xBE121000 40 [0.018477] ACPI: SSDT 0xBF3F8000 000316 (v02 GOOGLE Tpm2Tabl 1000 INTL 20160527) [
[Kernel-packages] [Bug 1903543] [NEW] Block device scheduler should be multiqueue for spinning disks
Public bug reported: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: New Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+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
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Sorry, that was v2.672 and v2.678 of the livecd-rootfs package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Robert Jennings's proposal from comment #33 landed in groovy v2.672.
A mechanism was also added in groovy v2.678 to detect if we've booted
using the panic fallback behavior mentioned by Steve Langasek in comment
#21.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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
[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
This may not be a new problem. Running the test case against a bionic image from June shows similar behavior: $ multipass launch 'https://cloud-images.ubuntu.com/minimal/releases/bionic/release-20200610/ubuntu-18.04-minimal-cloudimg-amd64.img' Launched: main-gnu $ multipass exec main-gnu -- sudo systemctl list-units --failed --no-legend cloud-config.service loaded failed failed Apply the settings specified in cloud-config systemd-modules-load.service loaded failed failed Load Kernel Modules $ multipass exec main-gnu -- cat /etc/cloud/build.info build_name: minimal serial: 20200610 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Bug description: Overview --- This is *blocking* new minimal image promotion. Starting on or around 20200714, the Bionic and Xenial minimal cloud images reported they failed to load kernel modules. Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-bionic/ 2. multipass launch file:/// 3. multipass exec -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+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
[Kernel-packages] [Bug 1881346] [NEW] linux-kvm should support nftables
Public bug reported: LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1881346 Title: linux-kvm should support nftables Status in linux-kvm package in Ubuntu: New Bug description: LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1881346/+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
[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
@fginther, The touchscreen works great with the -proposed kernel, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1865836 Title: Touchscreen Unresponsive in Focal, but Works in Eoan Status in linux-5.4 package in Ubuntu: New Bug description: After upgrading my Surface Go to Focal from Eoan, the touchscreen has stopped working. A snippet from journalctl: 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18
[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
With kernel version 5.4.0, the touchscreen does not work. Attaching a dmesg with this kernel. ** Attachment added: "dmesg.5.4.0-14-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334326/+files/dmesg.5.4.0-14-generic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1865836 Title: Touchscreen Unresponsive in Focal, but Works in Eoan Status in linux-5.4 package in Ubuntu: New Bug description: After upgrading my Surface Go to Focal from Eoan, the touchscreen has stopped working. A snippet from journalctl: 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu
[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
With kernel version 5.3.0, the touchscreen works. Attaching a dmesg with this kernel. ** Attachment added: "dmesg.5.3.0-29-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334325/+files/dmesg.5.3.0-29-generic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1865836 Title: Touchscreen Unresponsive in Focal, but Works in Eoan Status in linux-5.4 package in Ubuntu: New Bug description: After upgrading my Surface Go to Focal from Eoan, the touchscreen has stopped working. A snippet from journalctl: 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04
[Kernel-packages] [Bug 1865836] [NEW] Touchscreen Unresponsive in Focal, but Works in Eoan
Public bug reported: After upgrading my Surface Go to Focal from Eoan, the touchscreen has stopped working. A snippet from journalctl: 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1694 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 02:27:15 2020 InstallationDate: Installed on 2020-01-29 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:096f Microsoft Corp. Surface Type
