[Kernel-packages] [Bug 1940332] Re: hci0: Failed to send firmware data (-38)
Still affects jammy on a ThinkPad X260 with kernel 6.8.0-40-generic. I haven't tried the workaround yet but a `rmmod btusb; modprobe btsub` makes Bluetooth work on this notebook. Actually, I am pretty sure it worked before and this is a more recent regression, maybe when the LTS kernel was updated from 6.5 (?) to 6.8. -- 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/1940332 Title: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: This report is related to a problem reported in IRC #ubuntu whereby (Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot time but can later. Appears to be a race condition between the wifi chipset setting up the device and enabling the attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem. The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() and/or https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 as the result of the calls: err = wait_event_interruptible_timeout(...) since only these are followed by calls to net/bluetooth/lib.c::bt_to_errno() and that is the only function that can return -ENOSYS (-38) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 default: return ENOSYS; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+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 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
** Also affects: linux (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557 Importance: Unknown Status: Unknown -- 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/1494350 Title: QEMU: causes vCPU steal time overflow on live migration Status in Linux: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Released Status in linux package in Debian: Unknown Bug description: [Impact] It is possible to have vcpu->arch.st.last_steal initialized from a thread other than vcpu thread, say the main thread, via KVM_SET_MSRS. That can cause steal_time overflow later (when subtracting from vcpu threads sched_info.run_delay). [Test Case] Testing Steps with patched trusty kernel: Using savemv & loadvm to simulate the migration process. In guest: 1. check steal_time data location rdmsr 0x4b564d03 <- returns the start address 0x7fc0d000 2. exam the steal time before savevm in qemu monitor (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:144139048 < steal time value before savevm (qemu) savevm mytestvm7 savevm mytestvm7 (qemu) quit quit 3. give some load to the host system, e.g. stress --cpu 4. start the guest with "-loadvm mytestvm7" to restore the state of the VM, thus the steal_time MSR 5. exam the steal time value again (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:147428917 < with high cpu load after loadvm, steal time still shows a linear increase The steal_time value would go backward (because of the overflow) after the restoration of the VM state without the fix. - I'm pasting in text from Debian Bug 785557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557 b/c I couldn't find this issue reported. It is present in QEMU 2.3, but I haven't tested later versions. Perhaps someone else will find this bug and confirm for later versions. (Or I will when I have time!) Hi, I'm trying to debug an issue we're having with some debian.org machines running in QEMU 2.1.2 instances (see [1] for more background). In short, after a live migration guests running Debian Jessie (linux 3.16) stop accounting CPU time properly. /proc/stat in the guest shows no increase in user and system time anymore (regardless of workload) and what stands out are extremely large values for steal time: % cat /proc/stat cpu 2400 0 1842 650879168 2579640 0 25 136562317270 0 0 cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0 cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0 cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0 cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0 intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 837862829 btime 1431642967 processes 8529939 procs_running 1 procs_blocked 0 softirq 225193331 2 77532878 172 7250024 819289 0 54 33739135 176552 105675225 Reading the memory pointed to by the steal time MSRs pre- and post-migration, I
[Kernel-packages] [Bug 1180649] Re: Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: file-aligned section .text extends beyond end of file
I asked around and this is an overly verbose sbsigntool which should probably not a warning but a debug message: https://twitter.com/mjg59/status/689745355202691073 ** Package changed: linux-signed (Ubuntu) => sbsigntool (Ubuntu) ** Summary changed: - Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: file-aligned section .text extends beyond end of file + sbsigntool warning: file-aligned section .text extends beyond end of file; checksum areas are greater than image size. Invalid section table? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1180649 Title: sbsigntool warning: file-aligned section .text extends beyond end of file; checksum areas are greater than image size. Invalid section table? Status in sbsigntool package in Ubuntu: Confirmed Bug description: Error in dist-upgrade to 3.8.0-21 for x86_64 SMP: Setting up linux-signed-image-3.8.0-21-generic (3.8.0-21.32) ... warning: file-aligned section .text extends beyond end of file warning: checksum areas are greater than image size. Invalid section table? The dist-upgrade completed without further errors and system is running with new kernel without any further error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1180649/+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 1276740] Re: [Acer C720] Touchpad not recognized since kernel upgrade
For testing I installed the utopic kernel (3.16.0.6.7) on trusty and the touchpad is still not recognized. -- 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/1276740 Title: [Acer C720] Touchpad not recognized since kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: This is on Ubuntu 13.10, kernel 3.11.0-15 on an Acer C720 Chromebook with a Synaptics touchpad. A USB or bluetooth mouse works fine. The trackpad is no longer in the list of devices in xinput as it had been before. $ apt-cache policy xserver-xorg-input-synaptics xserver-xorg-input-synaptics: Installed: 1.7.1-0ubuntu1 Candidate: 1.7.1-0ubuntu1 Version table: *** 1.7.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.25 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fredlaxton 1532 F pulseaudio /dev/snd/controlC0: fredlaxton 1532 F pulseaudio Date: Wed Feb 5 13:16:57 2014 MachineType: Acer Peppy MarkForUpload: True ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=b9c60669-34d9-460f-ac3e-35db5665dfeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd10/29/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276740/+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 1303342] Re: [Acer C720] Touchpad not working after kernel upgrade
*** This bug is a duplicate of bug 1276740 *** https://bugs.launchpad.net/bugs/1276740 ** This bug has been marked a duplicate of bug 1276740 [Acer C720] Touchpad not recognized since kernel upgrade -- 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/1303342 Title: [Acer C720] Touchpad not working after kernel upgrade Status in “linux” package in Ubuntu: Expired Bug description: After update touchpad stopped working. System does not see it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-19-generic 3.11.0-19.33 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1305 F pulseaudio /dev/snd/controlC0: user 1305 F pulseaudio Date: Sun Apr 6 15:16:34 2014 MachineType: Acer Peppy MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=4819d259-3230-4604-abd0-791f3aa07325 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd10/29/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303342/+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 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in “linux-meta” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1308264/+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 951736] Re: Cannot change brightness on laptop with ATI Radeon 6470M
Sorry, I don't have the hardware anymore. -- 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/951736 Title: Cannot change brightness on laptop with ATI Radeon 6470M Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: "When I press Fn+F9 or F10 which are the keyboard buttons to decrease/increase the screen brightness of my HP Probook 6560b laptop, nothing happens." This was quoted from the following bug from the kernel.org bugtracker which has some more infos: https://bugzilla.kernel.org/show_bug.cgi?id=40862 I manually installed the precise kernel on my oneiric install to see if it is fixed with a newer kernel, didn't help. WORKAROUND: Use fglrx. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-radeon 1:6.14.99~git20110811.g93fc084-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Mar 10 20:02:31 2012 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/951736/+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
