[Kernel-packages] [Bug 2077266] Re: Blank screen hang on bootup with Ryzen 7840U iGPU with Noble
If I look here: *'/boot/config-6.10.0-15-generic' * "CONFIG_DRM_RADEON=m # CONFIG_DRM_RADEON_USERPTR is not set CONFIG_DRM_AMDGPU=m CONFIG_DRM_AMDGPU_SI=y CONFIG_DRM_AMDGPU_CIK=y CONFIG_DRM_AMDGPU_USERPTR=y # CONFIG_DRM_AMDGPU_WERROR is not set" Or */boot/config-6.8.0-31-generic' * Is the same as above -- 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/2077266 Title: Blank screen hang on bootup with Ryzen 7840U iGPU with Noble Status in linux package in Ubuntu: Confirmed Bug description: TLDR - Looks like the amdgpu module is included in the Jammy kernel images but not in Noble. Hello! I have a laptop with the AMD Ryzen 7840U CPU which has a 780M iGPU running both Jammy-based and Noble-based distro elementary OS releases. This issue occurs only with the Noble and not Jammy edition. Upon bootup with the "quiet splash" params there is just a blank screen and apparent hang which is prevented if I remove the "splash" option and then I get the expected login screen just fine. Note that I ran the following command on both Jammy and Noble: sudo lsinitramfs /boot/initrd-6.8x | grep amdgpu And I see the amdgpu module is present in the Jammy image but not the Noble image. So I appended "amdgpu" to the /etc/initramfs-tools/modules file and did: sudo update-initramfs -uk all Which resolves the issue for me with Noble as well. Note both my Jammy and Noble installs are on the same kernel version currently 6.8-xxx-40 although the amdgpu module is included in the Jammy image but not the Noble one. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077266/+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 2063254] Re: firewire_ohci stops under moderate load
Update: this is strangely related to nouveau On a machine with a "NVIDIA MCP89 [GeForce 320M]" the nvidia drivers have been removed from 22.04. nouveau when run normally now causes a hang [see other reports if curious] The described "firewire_ohci quits when using firefox" happens when kernel launched with kernel flag nomodeset When launched, instead, with nouveau.noaccel=1 ...normal usage does not affect firewire_ohci, as expected and desired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063254 Title: firewire_ohci stops under moderate load Status in linux-hwe-6.5 package in Ubuntu: New Bug description: This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28 Using snd_dice to playback audio, doing anything else, even just scrolling in firefox or launching this bug report, causes the firewire driver to quit: Apr 23 12:48:53 Konnekt kernel: firewire_ohci :01:00.0: DMA context IT0 has stopped, error code: evt_timeout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 23 13:08:53 2024 Dependencies: linux-modules-6.5.0-28-generic 6.5.0-28.29~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+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 2063254] [NEW] firewire_ohci stops under moderate load
Public bug reported: This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28 Using snd_dice to playback audio, doing anything else, even just scrolling in firefox or launching this bug report, causes the firewire driver to quit: Apr 23 12:48:53 Konnekt kernel: firewire_ohci :01:00.0: DMA context IT0 has stopped, error code: evt_timeout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 23 13:08:53 2024 Dependencies: linux-modules-6.5.0-28-generic 6.5.0-28.29~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063254 Title: firewire_ohci stops under moderate load Status in linux-hwe-6.5 package in Ubuntu: New Bug description: This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28 Using snd_dice to playback audio, doing anything else, even just scrolling in firefox or launching this bug report, causes the firewire driver to quit: Apr 23 12:48:53 Konnekt kernel: firewire_ohci :01:00.0: DMA context IT0 has stopped, error code: evt_timeout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 23 13:08:53 2024 Dependencies: linux-modules-6.5.0-28-generic 6.5.0-28.29~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+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 1788044] Re: task kworker blocked for more than 120 seconds nouveau
I have found a fix. First I tried adding "nouveau.modeset=0" to bootflags, which got me to boot but no greeter. sddm appeared to be happily running but it failed to start the display server restarting it did not help "startx" worked, which gave me hope It appeared the session "seat" had been determined by systemd to have "CanGraphical" false Then I found this: https://github.com/mikhailnov/systemd/commit/c00bf275fdfbad3a9db8934b5e266b6abbdb8443 There's a heuristic hack which sets CanGraphical when the kernel starts w/o graphics, but only if this is done via "nomodeset" rather than the driver-specific ".modeset" flags So I just added "nomodeset" to boot flags, and now not only does 6.5.0-28 boot and land at a working greeter again, but all the weird sddm graphics bugs i'd been encountering since 6.5 are gone. Hope this helps someone else... And maybe this kernel issue will get fixed, some day -- 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/1788044 Title: task kworker blocked for more than 120 seconds nouveau Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet
[Kernel-packages] [Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
This is the closest, most recent report I could find with something which also appears kernel related Kernel 6.5.0-27 -- works fine Kernel 6.5.0-28 -- graphics hard-hangs - sddm never displays, vtty can't be activated shh works, sddm and x11 processes can not be killed, reboot hangs, hard power cycle required I see reports like this literally for years, yet seemingly no resolution. Now I'm bit, in a way suspiciously kernel version related Common internet "use nvidia drivers" wisdom is unworkable as old nvidia hardware is not supported on 22.04 04:00.0 VGA compatible controller: NVIDIA Corporation MCP89 [GeForce 320M] (rev a2) Again, for me, this is with 22.04, kernel 6.5.0-28 All the various combinations of nouveau flags to kernel boot which have helped reduce garbage or sddm troubles don't help. Here's a relevant boot log: Apr 20 21:06:29 Konnekt sddm-greeter[922]: Adding view for "LVDS-1" QRect(0,0 1280x800) Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 216004 put 216088 ib_get 0007 ib_put 0007 state 800081a4 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21608c put 217b7c ib_get 0009 ib_put 000a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 218ff0 put 21932c ib_get 000d ib_put 0012 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a48 put 219a64 ib_get 001f ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a64 put 219a7c ib_get 0021 ib_put 0024 state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a7c put 219a8c ib_get 0023 ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a8c put 219ccc ib_get 0025 ib_put 002a state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219de8 put 219df8 ib_get 002f ib_put 0030 state 4004 (err: INVALID_MTHD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: CACHE_ERROR - ch 3 [sddm-greeter[922]] subc 0 mthd data 2000 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219ef0 put 21a2f0 ib_get 0033 ib_put 0038 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 0020b10960 put 0020b10ac8 ib_get 0042 ib_put 0044 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21aff8 put 21bdf4 ib_get 004b ib_put 004c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21c248 put 21c620 ib_get 004d ib_put 004e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417a40 put 417a4c ib_get 0056 ib_put 0058 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417b54 put 417b5c ib_get 005c ib_put 005e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3370 put 4d33f4 ib_get 0062 ib_put 0064 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4db3c0 put 4db450 ib_get 0068 ib_put 006a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21d000 put 21d150 ib_get 006b ib_put 006c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417c50 put 417c5c ib_get 006e ib_put 0070 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3630 put 4d3684 ib_get 007a
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Mike and I have posted Disclaimers to the users on Jammy **Warning of potential breakage with the added PPA Mike has also included some very straight forward work-around's with The *Warning* to users on 22.04 until the fix is pushed to the users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397&highlight=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
It worked: The grub issue with a PPA solved it for NNoble Code: apt policy grub-common grub-common: Installed: 2.12-1ubuntu1~ppa1 Candidate: 2.12-1ubuntu1~ppa1 Version table: *** 2.12-1ubuntu1~ppa1 500 500 https://ppa.launchpadcontent.net/ubuntu-uefi-team/build/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 2.12~rc1-12ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages zfs list -r -t snapshot -o name,creation bpool NAME CREATION bpool/BOOT/ubuntu_l7y21m@autozsys_bk6cdb Fri Feb 2 10:41 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_sin22d Sat Feb 3 17:22 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_41kebx Sat Feb 3 17:23 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_25r5is Sun Feb 4 13:55 2024 bpool/BOOT/ubuntu_l7y21m@autozsys_1n6o7d Sun Feb 4 14:07 2024 bpool/BOOT/ubuntu_l7y21m@2-4-2024test Sun Feb 4 14:09 2024 As seen by the bottom "bpool/BOOT/ubuntu_l7y21m@2-4-2024test Sun Feb 4 14:09 2024" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397&highlight=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
I've added the PPA for Noble just now, will report after a manual bpool snapshot **The following packages will be upgraded: automake autopoint ayatana-indicator-common bind9-dnsutils bind9-host bind9-libs cpio gcc-14-base gcc-14-base:i386 gettext gettext-base grub-common grub-efi-amd64-bin grub-efi-amd64-signed grub-pc grub-pc-bin grub2-common language-pack-gnome-en libasan8 libatomic1 libatomic1:i386 libcc1-0 libgcc-s1 libgcc-s1:i386 libgfortran5 libgnutls30 libgomp1 libhwasan0 libitm1 liblsan0 libneon27 libp11-kit0 libpcap0.8 libquadmath0 libstdc++6 libstdc++6:i386 libtsan2 libubsan1 linux-firmware openssh-client p11-kit p11-kit-modules python3-mako ufw 44 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397&highlight=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2044657] Re: Multiple data corruption issues in zfs
All good hear, but curious about: *apt show zfsutils-linux |grep -e "Breaks" WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>> 2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1) Both live nicely here for me: * apt policy zfsutils-linux zfs-dkms zfsutils-linux: Installed: 2.2.2-0ubuntu1 Candidate: 2.2.2-0ubuntu1 Version table: *** 2.2.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status zfs-dkms: Installed: 2.2.2-0ubuntu1 Candidate: 2.2.2-0ubuntu1 Version table: *** 2.2.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages 100 /var/lib/dpkg/status Seems solid today with multiple boots, reboots and cold boots -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Committed Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
This affects me as well. All though this seems to be working apt policy zfs-dkms zfs-dkms: Installed: 2.2.0-0ubuntu3 Candidate: 2.2.0-0ubuntu3 Version table: 2.2.1-0ubuntu1 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages *** 2.2.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble/universe i386 Packages 100 /var/lib/dpkg/status Please also follow the Link Mike provided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044969 Title: Upstream bug: ZFS feature@block_cloning causes data corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: Noble DAILY ISO 2023.11.27 & Current Mantic Installers. some copied files are corrupted (chunks replaced by zeros) ISSUE #15526 RE:https://github.com/openzfs/zfs/issues/15526 zpool feature@block_cloning came out with version 2.2.0 of zfs-linux, this is not the root of that bug, but exacerbates the underlying bug. The bug was reported, and version 2.2.1 was released with that feature turned off by default, so that would be a problem out of the gate. There is a patch out which got approved, merged and built tonight that, after testing, seems to correct that: dnode_is_dirty: check dnode and its data for dirtiness #15571 https://github.com/openzfs/zfs/pull/15571 Unfortunately, Mantic was released with version 2.2.0. Current DEV Noble also has 2.2.0. This feature in the default ZFS install scripts for both Mantic and Noble, with the current default, In bpool, feature@block_cloning is disable, but for rpool, the same feature is enabled, so "at risk". This feature is set at pool creation time. You cannot set this feature to disable without destroying the pool and recreating it fresh. Have good backups, via rsync. cp is affected, but not rsync. Version 2.2.1 has this feature disabled by default. It was released Nov 21, 2023. I am proposing that the patched build from tonight get pushed through for Mantic when it hits from upstream... And possibly pushing 2.2.1 through for Noble, where we can thoroughly test it in this current DEV Cycle. Also, this was filed because of Security as it relates to data integrity concerns: CVE-2023-49298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: zfsutils-linux 2.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 27 19:58:32 2023 InstallationDate: Installed on 2023-11-23 (4 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
I have no logs, it blew my kernel out of boot. "you need to load the kernel first" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Attachment added: "Capture d’écran du 2023-09-24 15-44-45.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704098/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-45.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Attachment added: "Capture d’écran du 2023-09-24 15-44-18.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704097/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-18.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
I got it working on a 2015 MacBook Air 7.2 From a 23.04 fresh installation it didin't work neither with a 22.04 fresh installation. I tried all the tricks I found over internet and nothing worked. I then had first to install an old Ubuntu 20.04 and block the version of the following packages bcmwl-kernel-source linux-headers-5-10.0.84 linux-headers-5-10.0.84-generic linux-modules-5-10.0.84-generic. Now I have a fresh 23.04 version with Wifi on a Broadcom BCM 4360 14e4:43a0. It seems defintely to be a bug since it worked perfectly out-of-the-box with other distros such as Fedora or Arch. ** Attachment added: "Capture d’écran du 2023-09-24 15-43-57.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704096/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-43-57.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 1970056] Re: Ubuntu 22.04 unable to mount root partition
I tried Ubuntu 22.04 with kernel 5.13 on Acer Spin 5 SP513-54N. Touchpad, touchscreen, and stylus all work, but Wi-Fi does not work. -- 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/1970056 Title: Ubuntu 22.04 unable to mount root partition Status in linux package in Ubuntu: Confirmed Bug description: After updating from Kubuntu 21.10 to Kubuntu 22.04, boot drops to a (initramfs) prompt/busybox. When I type "exit" I get the "Gave up waiting for root file system device" error message and "ALERT! UUID=[nvme drive UUID] does not exist. Dropping to a shell!" I can still boot into KDE when selecting the older kernel version 5.13.0-40-lowlatency. I have tried the newer kernel versions 5.15.025-generic, 5.15.0.24-lowlatency, 5.17.4-051421-generic and 5.14.21-051421-lowlatency and all have produced the same problem. When removing the the "pci=nocrs" kernel paramater in Grub for these newer versions, the system boots into KDE but the touchpad does not work. Kernel version 5.13.0-40-lowlatency boots into KDE without removing the "pci=nocrs" parameter and everything works as expected, including the touchpad. My hardware is a Lenovo ideapad lenovo ideapad 3 15IIL05, Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz, Memory: 7,3 GiB of RAM, Graphics Processor: Mesa Intel® Iris® Plus Graphics. I have upgraded the hard drive that came with the machine to a Kingston SA2000M8500G 465,8GiB nvme drive. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 2376 F jackdbus /dev/snd/pcmC0D0c: nick 2376 F...m jackdbus /dev/snd/pcmC0D0p: nick 2376 F...m jackdbus /dev/snd/seq:nick 2801 F a2jmidid CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-27 (483 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=5a0515ea-30d8-4412-ad65-8abbd8be949f ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirt lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:br1.40:efr1.40:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05:skuLENOVO_MT_81WE_BU_idea_FM_IdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Is this Linux patch series back-ported to older kernels, like the 5.13 kernel that came with my Ubuntu 20.04 installation, or any LTS kernel? I'm not fully familiar with the Linux kernel release behaviour. I'm asking this because I'm looking for the best way to apply this patch on an older kernel without building the kernel from source? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I just verified the patch in Ubuntu 20.04 under kernel version 5.13. All of my components now show up in open RGB. I compiled the kernel myself using the steps provided in https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651. As mentioned above, I was not able to verify the PPA provided by @vicamo. **System info:** PCPartPicker Part List: https://nl.pcpartpicker.com/list/7HW8Y9 - CPU: AMD Ryzen 5 5600G 3.9 GHz 6-Core Processor (€228.95 @ Amazon Netherlands) - Motherboard: Asus ROG STRIX B550-E GAMING ATX AM4 Motherboard (€226.81 @ Amazon Netherlands) - Memory: Crucial Ballistix RGB 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory (€83.85 @ Megekko) - Memory: *Crucial Ballistix RGB 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory (€83.85 @ Megekko) - Video Card: NVIDIA GeForce GTX 1070 8 GB Video Card (2-Way SLI) - Video Card: NVIDIA GeForce GTX 1070 8 GB Video Card (2-Way SLI) - Case: Fractal Design Meshify 2 Compact TG Light Tint ATX Mid Tower Case (€159.00 @ Amazon Netherlands) - Power Supply: Corsair HXi 750 W 80+ Platinum Certified Fully Modular ATX Power Supply (€197.99 @ Amazon Netherlands) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I am now building the kernel from source using the following steps https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651 to verify whether the patch solves my problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Ah yea, that's a type. I used `sudo reboot now`. For me, after those steps the ram still didn't show up, so there might be another problem on my system. I also tried manually building the kernel with the patch, but I run into some unrelated issues. I think I will wait till the patch hits the upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I tried the PPA from @vicamo on Ubuntu 20.04 with kernel 5.14, but It does not seem to work for me. I installed the PPA using the following commands: sudo add-apt-repository ppa:vicamo/ppa-1950062 sudo update` sudo install linux-oem-5.14-headers-5.14.0-2023 linux-oem-5.14-tools-5.14.0-2023 linux-oem-5.14-tools-host. sudo apt reboot. sudo openrgb Maybe I am doing something wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I am affected by this issue on my Ubuntu 20.04 system that is running kernel a 5.13 kernel. I have a ASUS rog stix b550-E gaming motherboard, an AMD 5600G CPU and use crucial ballistix ram. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+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 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
I'm not sure what's needed to bisect the kernel? What would I need to do? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P conditional, RSB filling Vulnerability
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)
rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt:
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name:long_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us:27983872
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw:0
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name:short_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw:5875
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us:2440
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/device: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/enabled:0
/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj:5242172615
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:0: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:1: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj:262143328850
/sys/class/powercap/intel-rapl/intel-rapl:0/name:package-0
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/power: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem: Is a directory
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$ sudo rdmsr -c -p0 0x64F
rdmsr: CPU 0 cannot read MSR 0x064f
rt@sys76:~$ sudo strace rdmsr 0x64F
execve("/usr/sbin/rdmsr", ["rdmsr", "0x64F"], 0x7ffe9486b188 /* 16 vars */) = 0
brk(NULL) = 0x5633b869a000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe398f8370) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=79034, ...}) = 0
mmap(NULL, 79034, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc1f8b19000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc1f8b17000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fc1f8925000
mprotect(0x7fc1f894a000, 1847296, PROT_NONE) = 0
mmap(0x7fc1f894a000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fc1f894a000
mmap(0x7fc1f8ac2000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fc1f8ac2000
mmap(0x7fc1f8b0d000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fc1f8b0d000
mmap(0x7fc1f8b13000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc1f8b13000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fc1f8b18580) = 0
mprotect(0x7fc1f8b0d000, 12288, PROT_READ) = 0
mprotect(0x5633b7d85000, 4096, PROT_READ) = 0
mprotect(0x7fc1f8b5a000, 4096, PROT_READ) = 0
munmap(0x7fc1f8b19000, 79034) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, 0x7ffe398f8288, 8, 1615) = -1 EIO (Input/output error)
write(2, "rdmsr: CPU 0 cannot read MSR 0x0"..., 40rdmsr: CPU 0 cannot read MSR
0x064f
) = 40
exit_group(4) = ?
+++ exited with 4 +++
rt@sys76:~$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Status in thermald package in Ubuntu:
In Progress
Bug description:
I would really like to find out why my cpu's keep reverting back to a cpu
powersave mode after I get a kernel update then reboot.
I cleaned my laptops vent but this seems to happen whenever a new
kernel is updated and installed.
https://askubuntu.com/questions/1366090/
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@koba issue still occurs.
@Doug
rt@sys76:~$ sudo rdmsr -c -p0 0x1b2
0x3
rt@sys76:~$ sudo strace rdmsr 0x1b2
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1b2"], 0x7fff4f90a298 /* 17 vars */) = 0
brk(NULL) = 0x56510cc31000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe42320b10) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fec4390
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fec438fe000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fec4370c000
mprotect(0x7fec43731000, 1847296, PROT_NONE) = 0
mmap(0x7fec43731000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fec43731000
mmap(0x7fec438a9000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fec438a9000
mmap(0x7fec438f4000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fec438f4000
mmap(0x7fec438fa000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fec438fa000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fec438ff580) = 0
mprotect(0x7fec438f4000, 12288, PROT_READ) = 0
mprotect(0x56510cbb5000, 4096, PROT_READ) = 0
mprotect(0x7fec4396b000, 4096, PROT_READ) = 0
munmap(0x7fec4390, 253505) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\3\0\0\0\0\0\0\0", 8, 434) = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0), ...}) = 0
brk(NULL) = 0x56510cc31000
brk(0x56510cc52000) = 0x56510cc52000
write(1, "3\n", 23
) = 2
exit_group(0) = ?
+++ exited with 0 +++
rt@sys76:~$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Status in thermald package in Ubuntu:
In Progress
Bug description:
I would really like to find out why my cpu's keep reverting back to a cpu
powersave mode after I get a kernel update then reboot.
I cleaned my laptops vent but this seems to happen whenever a new
kernel is updated and installed.
https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts-
significant-throttling-of-
intel-i7-processor?noredirect=1#comment2345549_1366090
Description:Ubuntu 20.04.3 LTS
Release:20.04
Computer
Summary
Computer
Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Memory 16315MB (4407MB used)
Machine TypeLaptop
Operating SystemUbuntu 20.04.3 LTS
User Name rt (rt)
Date/Time Mon 30 Aug 2021 02:33:09 PM EDT
Display
Resolution 1920x1080 pixels
OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2)
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel HDMI
Audio Adapter HDA-Intel - HDA Intel PCH
Audio Adapter USB-Audio - USB Audio Device
Input Devices
Power Button
Sleep Button
Lid Switch
Power Button
AT Translated Set 2 keyboard
USB Audio Device
ETPS/2 Elantech Touchpad
Logitech Anywhere MX
Video Bus
HDA Intel PCH Mic
HDA Intel PCH Front Headphone
HDA Intel HDMI HDMI/DP,pcm:3
HDA Intel HDMI HDMI/DP,pcm:7
HDA Intel HDMI HDMI/DP,pcm:8
HDA Intel HDMI HDMI/DP,pcm:9
HDA Intel HDMI HDMI/DP,pcm:10
Printers (CUPS)
OfficeJet_Pro_6978 Default
SCSI Disks
TSSTcorp CDDVDW SN-208DB
ATA INTEL SSDMCEAC12
ATA ST1000LM014-1EJ1
Operating System
Version
Kernel Linux 5.4.0-81-generic (x86_64)
Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021
C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31
DistributionUbuntu 20.04.3
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
ok
rt@sys76:~$ sudo rdmsr -c -p0 0x19c
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x1aa
0x40
rt@sys76:~$ sudo rdmsr -c -p0 0x1b1
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x16f
rdmsr: CPU 0 cannot read MSR 0x016f
rt@sys76:~$ sudo rdmsr -c -p0 0x1fc
0x4005d
rt@sys76:~$ sudo strace rdmsr 0x19C
execve("/usr/sbin/rdmsr", ["rdmsr", "0x19C"], 0x7ffdaa2d1488 /* 17 vars */) = 0
brk(NULL) = 0x55b45cb84000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffc77c46f80) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35e41bf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35e41bd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f35e3fcb000
mprotect(0x7f35e3ff, 1847296, PROT_NONE) = 0
mmap(0x7f35e3ff, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7f35e3ff
mmap(0x7f35e4168000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7f35e4168000
mmap(0x7f35e41b3000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f35e41b3000
mmap(0x7f35e41b9000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f35e41b9000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7f35e41be580) = 0
mprotect(0x7f35e41b3000, 12288, PROT_READ) = 0
mprotect(0x55b45c8b1000, 4096, PROT_READ) = 0
mprotect(0x7f35e422a000, 4096, PROT_READ) = 0
munmap(0x7f35e41bf000, 253505) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\f\109\210\0\0\0\0", 8, 412) = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x3), ...}) = 0
brk(NULL) = 0x55b45cb84000
brk(0x55b45cba5000) = 0x55b45cba5000
write(1, "8839080c\n", 98839080c
) = 9
exit_group(0) = ?
+++ exited with 0 +++
rt@sys76:~$ sudo strace rdmsr 0x1aa
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1aa"], 0x7fffde650548 /* 17 vars */) = 0
brk(NULL) = 0x555d67d9f000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd9bfd56d0) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd5f63ff000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd5f63fd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fd5f620b000
mprotect(0x7fd5f623, 1847296, PROT_NONE) = 0
mmap(0x7fd5f623, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fd5f623
mmap(0x7fd5f63a8000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fd5f63a8000
mmap(0x7fd5f63f3000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Ok One terminal was running rt@sys76:~$ taskset -c 2 yes > /dev/null 2nd terminal data: rt@sys76:~$ grep . /sys/devices/system/cpu/intel_pstate/* /sys/devices/system/cpu/intel_pstate/max_perf_pct:100 /sys/devices/system/cpu/intel_pstate/min_perf_pct:50 /sys/devices/system/cpu/intel_pstate/no_turbo:0 /sys/devices/system/cpu/intel_pstate/num_pstates:27 /sys/devices/system/cpu/intel_pstate/status:active /sys/devices/system/cpu/intel_pstate/turbo_pct:38 rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ grep . /sys/devices/system/cpu/cpu2/cpufreq/* /sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:2 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_max_freq:340 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_min_freq:80 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_transition_latency:0 /sys/devices/system/cpu/cpu2/cpufreq/related_cpus:2 /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors:performance powersave /sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:798228 /sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_pstate /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor:powersave /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq:340 /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:80 /sys/devices/system/cpu/cpu2/cpufreq/scaling_setspeed: rt@sys76:~$ rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x198 [sudo] password for rt: 8 8 8 8 8 8 8 8 rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x199 17 17 34 17 17 34 17 17 rt@sys76:~$ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID:
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Now after another reboot the speed is stuck at 800mhz again and doesn't move rt@sys76:~$ uname -r 5.15.5-76051505-generic rt@sys76:~$ grep CONFIG_CPU_FREQ_DEFAULT /boot/config-5.15.5-76051505-generic # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,IRQ,PkgWatt,PkgTmp,RAMWatt,GFXWatt,CorWatt --interval 10 [sudo] password for rt: Busy% Bzy_MHz IRQ PkgTmp PkgWatt CorWatt GFXWatt 2.42800 555043 1.590.050.02 15.37 800 17228 44 2.990.420.17 19.79 800 25124 44 3.500.510.15 31.52 800 42876 46 5.060.880.44 9.73800 14967 46 2.610.250.15 3.60800 735846 1.660.070.04 4.63800 852946 1.870.100.04 3.29800 724346 1.680.070.03 7.49800 12913 47 2.290.190.07 rt@sys76:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 4: driver: intel_pstate CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 5: driver: intel_pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 799 MHz. analyzing CPU 6: driver: intel_pstate CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 7: driver: intel_pstate CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 4
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Yes I can get it to boot into active mode thanks to Doug, but after several minutes the cpu drops to 798-800mhz and won't increase no matter if I try and change it. I did notice that the scaling_governor always boots to powersave mode. When I change it to performance after several minutes the cpu drops to 798-800mhz again. I did find a similar problem "Linux kernel 5.8 defaults to passive mode for intel_pstate driver for cpu before skylake" but it always boots to the powersave governor and changing it doesn't fix the issue. https://www.reddit.com/r/linux/comments/ihdozd/linux_kernel_58_defaults_to_passive_mode_for/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds:
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Here's a list I can't remember the last time it worked, if you do a google search on "ubuntu cpu lowest freq" seems to be a very common problem but none of the fixes work for me. I can't change the speed of my CPU's in my bios (a system76 linux machine). What do you want me to check in the bios? Here's the kernel versions rt@sys76:~$ uname --all Linux sys76 5.15.5-76051505-generic #202111250933~1638201579~20.04~09f1aa7~dev-Ubuntu SMP Tue Nov 30 x86_64 x86_64 x86_64 GNU/Linux rt@sys76:~$ rt@sys76:~$ dpkg --list | grep linux-image rc linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-28-generic 4.10.0-28.32~16.04.2 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 amd64Linux kernel image for version 4.13.0 on 64 bit x86 SMP rc linux-image-4.15.0-101-generic 4.15.0-101.102 amd64Signed kernel image generic rc linux-image-4.15.0-106-generic 4.15.0-106.107 amd64Signed kernel image generic rc linux-image-4.15.0-108-generic 4.15.0-108.109 amd64Signed kernel image generic rc linux-image-4.15.0-109-generic 4.15.0-109.110 amd64Signed kernel image generic rc linux-image-4.15.0-111-generic 4.15.0-111.112 amd64Signed kernel image generic rc linux-image-4.15.0-112-generic 4.15.0-112.113 amd64Signed kernel image generic rc linux-image-4.15.0-115-generic 4.15.0-115.116 amd64Signed kernel image generic rc linux-image-4.15.0-117-generic 4.15.0-117.118 amd64Signed kernel image generic rc linux-image-4.15.0-118-generic 4.15.0-118.119 amd64Signed kernel image generic rc linux-image-4.15.0-20-generic 4.15.0-20.21 amd64Signed kernel image generic rc linux-image-4.15.0-22-generic 4.15.0-22.24 amd64Signed kernel image generic rc linux-image-4.15.0-23-generic 4.15.0-23.25 amd64Signed kernel image generic rc linux-image-4.15.0-24-generic 4.15.0-24.26 amd64Signed kernel image generic rc linux-image-4.15.0-29-generic 4.15.0-29.31 amd64Signed kernel image generic rc linux-image-4.15.0-30-generic 4.15.0-30.32 amd64Signed kernel image generic rc linux-image-4.15.0-32-generic 4.15.0-32.35 amd64Signed kernel image generic rc linux-image-4.15.0-33-generic 4.15.0-33.36 amd64Signed kernel image generic rc linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic rc linux-image-4.15.0-38-generic 4.15.0-38.41 amd6
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
ok... rt@sys76:~$ sudo cpupower -c all frequency-info [sudo] password for rt: analyzing CPU 0: driver: intel_cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 1: driver: intel_cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 2: driver: intel_cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 3: driver: intel_cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 4: driver: intel_cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 5: driver: intel_cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 6: driver: intel_cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 7: driver: intel_cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 ma
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
rt@sys76:~$ sudo systemctl status thermald.service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enabl> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:s> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; ven> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable > Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:ste> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor pre> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adapt> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0x6:> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive (code=exited, status=0/> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:mod
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
I'm not sure if this is the right package ** Package changed: ubuntu => thermald (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: New Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P conditional, RSB filling Vulne
[Kernel-packages] [Bug 1938050] [NEW] package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuratio
Public bug reported: Initial 16.04 esm installation went without a hitch. Soon after, software update reported no new updates. Today, updater tried to do updates but discovered some could not be installed without doing a "partial upgrade" first. This error occured during the "partial upgrade", and reported that "package linux-modules- extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed')" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 ProcVersionSignature: Ubuntu 4.4.0-211.243-generic 4.4.262 Uname: Linux 4.4.0-211-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rick 2218 F.... pulseaudio /dev/snd/controlC0: rick 2218 F pulseaudio Date: Mon Jul 26 10:44:38 2021 DuplicateSignature: package:linux-modules-extra-4.4.0-204-generic:4.4.0-204.236 Processing triggers for systemd (229-4ubuntu21.31+esm1) ... dpkg: error processing package linux-modules-extra-4.4.0-204-generic (--configure): package linux-modules-extra-4.4.0-204-generic is not ready for configuration ErrorMessage: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=d04e18df-5384-4207-9dbd-71d59bfc4150 InstallationDate: Installed on 2016-06-24 (1857 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-211-generic root=UUID=f2fbe206-5d00-4b50-92e9-72f30cc9b61e ro acpi=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.32 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: SOX5820J.86A.0603.2010.1117.1506 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DX58OG dmi.board.vendor: Intel Corporation dmi.board.version: AAG10926-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5820J.86A.0603.2010.1117.1506:bd11/17/2010:svn:pn:pvr:rvnIntelCorporation:rnDX58OG:rvrAAG10926-203:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1938050 Title: package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: Initial 16.04 esm installation went without a hitch. Soon after, software update reported no new updates. Today, updater tried to do updates but discovered some could not be installed without doing a "partial upgrade" first. This error occured during the "partial upgrade", and reported that "package linux-modules- extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed')" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 ProcVersionSignature: Ubuntu 4.4.0-211.243-generic 4.4.262 Uname: Linux 4.4.0-211-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rick 2218 F pulseaudio /dev/snd/controlC0: rick 2218 F pulseaudio Date: Mon Jul 26 10:44:38 2021 DuplicateSignature: package:linux-modules-extra-4.4.0-204-generic:4.4.0-204.236 Processing triggers for systemd (229-4ubuntu21.31+esm1) ... dpkg: error processing package linux-modules-extra-4.4.0-204-generic (--configure): package linux-modules-extra-4.4.0-204-generic is not ready for configuration ErrorMessage: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=d04e18df-5384-4207-9dbd-71d59bfc4150 InstallationDate: Installed on 2016-06-24 (1857 days ago) InstallationMedia: Ubuntu-Serv
[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04
Dell Latitude-9520 has the same issue. -- 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/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+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 1924717] Re: Internal speaker doesn't work after plug in a headset
** Description changed: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. + CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 1512 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware 1.197 + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. -- 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/1924717 Title: Internal speaker doesn't work after plug in a headset Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubsc
[Kernel-packages] [Bug 1924717] [NEW] Internal speaker doesn't work after plug in a headset
Public bug reported: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1924717 Title: Internal speaker doesn't work after plug in a headset Status in linux package in Ubuntu: New Bug description: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924717/+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
Re: [Kernel-packages] [Bug 1891764] Re: USB port no longer "seen" and therefor cannot mount flash drive
Yes, I sent the report when I noticed the problem: I put a thumb drive in the port and got nothing; I tried a mouse, a mic, and USB headphones, all nothing. It's as if the port no longer exists. ᐧ On Tue, Sep 1, 2020 at 8:10 PM Kai-Heng Feng <1891...@bugs.launchpad.net> wrote: > Was the log uploaded when the issue happened? Not seeing anything > relevant in dmesg. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891764 > > Title: > USB port no longer "seen" and therefor cannot mount flash drive > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > This USB port had been working; filled USB Lexar flashdrive was then > removed and new flash drive inserted. That one was also immediately > recognized and mounted and then suddenly it disappeared from view. Now > the drive itself is not found and nothing is mounted or installed when > inserted into that port (neither flash drive nor an external mouse). > > Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3 > > Rick Feldman > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-42-generic 5.4.0-42.46 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: owner 1173 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Aug 15 13:07:00 2020 > GvfsMonitorError: >This tool has been deprecated, use 'gio mount' instead. >See 'gio help mount' for more info. > GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. > HotplugNewDevices: > > HotplugNewMounts: > > InstallationDate: Installed on 2019-01-28 (564 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > MachineType: ASUSTeK Computer Inc. U56E > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=8071e842-b8c0-41c4-8950-6964dd47ced3 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-42-generic N/A >linux-backports-modules-5.4.0-42-generic N/A >linux-firmware1.187.2 > SourcePackage: linux > Symptom: storage > UdevMonitorLog: >monitor will print the received events for: >UDEV - the event which udev sends out after rule processing > UdisksMonitorLog: >Monitoring the udisks daemon. Press Ctrl+C to exit. >13:07:30.351: The udisks-daemon is running (name-owner :1.11). > UpgradeStatus: Upgraded to focal on 2020-05-10 (96 days ago) > dmi.bios.date: 12/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: U56E.213 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: U56E > dmi.board.vendor: ASUSTeK Computer Inc. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK Computer Inc. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: > dmi.product.family: U > dmi.product.name: U56E > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK Computer Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891764/+subscriptions > -- *Rick Feldman* *Lecturer in Economics & Entrepreneurship* *Committee Chair and Coordinator * * Entrepreneurship, Organizations, and Society (EOS)* *Office 124, Skinner Hall* *Mount Holyoke College* *feld...@mtholyoke.edu * *CELL: 413-537-7059* *CAMPUS PHONE: 538-2518* -- 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/1891764 Title: USB port no longer "seen" and therefor cannot mount flash drive Status in linux package in Ubuntu: Incomplete Bug description: This USB port had been working; filled USB Lexar flashdrive was then removed and new flash drive inserted. That one was also immediately recognized and mounted and then suddenly it disappeared from view. Now the drive itself is not found and nothing is mounte
[Kernel-packages] [Bug 1891764] [NEW] USB port no longer "seen" and therefor cannot mount flash drive
Public bug reported: This USB port had been working; filled USB Lexar flashdrive was then removed and new flash drive inserted. That one was also immediately recognized and mounted and then suddenly it disappeared from view. Now the drive itself is not found and nothing is mounted or installed when inserted into that port (neither flash drive nor an external mouse). Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3 Rick Feldman ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 1173 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 13:07:00 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-01-28 (564 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK Computer Inc. U56E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8071e842-b8c0-41c4-8950-6964dd47ced3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:07:30.351: The udisks-daemon is running (name-owner :1.11). UpgradeStatus: Upgraded to focal on 2020-05-10 (96 days ago) dmi.bios.date: 12/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U56E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U56E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U56E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1891764 Title: USB port no longer "seen" and therefor cannot mount flash drive Status in linux package in Ubuntu: New Bug description: This USB port had been working; filled USB Lexar flashdrive was then removed and new flash drive inserted. That one was also immediately recognized and mounted and then suddenly it disappeared from view. Now the drive itself is not found and nothing is mounted or installed when inserted into that port (neither flash drive nor an external mouse). Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3 Rick Feldman ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 1173 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 13:07:00 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-01-28 (564 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK Computer Inc. U56E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8071e842-b8c0-41c4-8950-6964dd47ced3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the rec
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
20.04 beta still has this issue for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@albertomilone: That does not work. I still cannot auto-login after adding needs_root_rights = yes in /etc/X11/Xwrapper.config -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://he
[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
In addition to above commit 255095fa7f62ff09b6f61393414535c59c6b4cb0 media: dvb-usb-v2: Fix incorrect use of transfer_flags URB_FREE_BUFFER -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
Kernel 4.21.1 and 4.19.14 have all the fixes. -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
Sorry I meant 4.20.1 ** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-fixed-upstream -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
4.18 EOL now anyway The only way out is to revert the above commit this patch isn't yet upstream https://patchwork.linuxtv.org/patch/53155/ Also this patch which has made into kernel 4.18 commit 7d95fb746c4eece67308f1642a666ea1ebdbd2cc Revert "media: dvbsky: use just one mutex for serializing device R/W ops" -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
** Tags added: kernel-bug-exists-upstream -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Incomplete Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
I think this is caused by commit 1a0c10ed7bb191bccf6f1e2d16203886a5ce76c8 media: dvb-usb-v2: stop using coherent memory for URBs Reverting this should restore normal operation. -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Incomplete Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1696422] Re: Sudden Read Only File System
The same problem also appears for me with 4.18.0-10-generic. -- 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/1696422 Title: Sudden Read Only File System Status in linux package in Ubuntu: Fix Released Bug description: Hello. I've got a critical problem with my computer, and i don't know why. The file system suddenly becomes read-only. All application (chrome, firefox and idea) that i use turn off and i can't even reboot. This trouble happens 3, 4 or 5 times a day (from 9 am to 18 pm) Ubuntu 16.04 LTS is installed. Kernel : 4.8.0-52-generic My Hard drive has been changed and i still got this trouble. My hard drive is an SSD. My partition is /dev/nvmeOn1 Here is the dmesg output after I got the error : [ 1995.052507] nvme :04:00.0: Failed status: 0x, reset controller. [ 1995.070353] nvme :04:00.0: enabling device ( -> 0002) [ 1995.070504] nvme nvme0: Removing after probe failure status: -19 [ 1995.070520] nvme0n1: detected capacity change from 512110190592 to 0 [ 1995.070971] blk_update_request: I/O error, dev nvme0n1, sector 0 [ 1998.122783] Aborting journal on device dm-1-8. [ 1998.122858] Buffer I/O error on dev dm-1, logical block 60325888, lost sync page write [ 1998.122877] JBD2: Error -5 detected when updating journal superblock for dm-1-8. [ 1998.126663] Buffer I/O error on dev dm-1, logical block 0, lost sync page write [ 1998.126688] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal [ 1998.126701] EXT4-fs (dm-1): Remounting filesystem read-only [ 1998.126711] EXT4-fs (dm-1): previous I/O error to superblock detected [ 1998.126770] Buffer I/O error on dev dm-1, logical block 0, lost sync page write [ 2016.894677] Buffer I/O error on dev dm-1, logical block 77070475, lost async page write [ 2016.894689] Buffer I/O error on dev dm-1, logical block 77070852, lost async page write [ 2016.894694] Buffer I/O error on dev dm-1, logical block 77070853, lost async page write [ 2016.894698] Buffer I/O error on dev dm-1, logical block 77071711, lost async page write [ 2016.894703] Buffer I/O error on dev dm-1, logical block 109051905, lost async page write [ 2016.894709] Buffer I/O error on dev dm-1, logical block 2, lost async page write [ 2016.894714] Buffer I/O error on dev dm-1, logical block 27, lost async page write [ 2016.894719] Buffer I/O error on dev dm-1, logical block 5242882, lost async page write [ 2069.041447] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 2071.156404] compiz[2087]: segfault at 0 ip 7fe4a0c854e9 sp 7ffda4be21b0 error 4 in libunityshell.so[7fe4a0851000+5e] Sorry for my bad english --- ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivier2175 F...m pulseaudio /dev/snd/controlC0: olivier2175 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3375b138-fc2d-43c5-85bf-0492f97eb4a0 InstallationDate: Installed on 2017-05-31 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-54-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-54-generic N/A linux-backports-modules-4.8.0-54-generic N/A linux-firmware1.157.10 Tags: xenial Uname: Linux 4.8.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.25 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.25:bd05/07/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696422/+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 1777010] Re: ip token set, results in: Invalid argument
Daniel Borkmann's contact information seems to be available at http://borkmann.ch . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1777010 Title: ip token set, results in: Invalid argument Status in iproute2 package in Ubuntu: Confirmed Bug description: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+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 1759836] Re: systemd-udevd consumes 100% of CPU
As per https://patchwork.kernel.org/patch/10384111/ message from Bluez mailing list, editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 -ACTION=="remove", GOTO="hid2hci_end" +ACTION!="add", GOTO="hid2hci_end" Bluetooth now works with kernels above and below 4.14. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836 -- 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/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel Status in linux package in Ubuntu: Incomplete Bug description: I can confirm the following bug in kernel version 4.15 in bionic, https://bugzilla.kernel.org/show_bug.cgi?id=199035 WORKAROUND: Boot into kernel 4.13. WORKAROUND: Disable bluetooth in BIOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+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 1759836] Re: systemd-udevd consumes 100% of CPU
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14, so sticking with the old kernel that works for now. Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail. systemd-udevd has always consumed 100% whenever a udev rule fails (could be argued that's also a bug but at least you become immediately aware there's a problem). Possibly no coincidence that the break was introduced at the same time kernel tree commits were made to btusb.c wrt. Dell 'features' being addded. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1743094] Re: hibernation broken (freezes with resume) in kernel linux-image-4.13.0-26-generic
I can also confirm that with 4.13.0-30, hibernate did not work, but installing 4.14.13-041413-generic works perfectly. -- 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/1743094 Title: hibernation broken (freezes with resume) in kernel linux- image-4.13.0-26-generic Status in linux package in Ubuntu: Incomplete Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1692144] [NEW] package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Trying to update Ubuntu Gnome 17.04 from Software Center. It just hangs. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1236 F pulseaudio rick 1704 F pulseaudio Date: Fri May 19 19:59:57 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=1dad3eb5-5b2e-4534-9f4d-c71983851766 InstallationDate: Installed on 2017-05-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/11/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1692144 Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: Trying to update Ubuntu Gnome 17.04 from Software Center. It just hangs. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1236 F pulseaudio rick 1704 F pulseaudio Date: Fri May 19 19:59:57 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=1dad3eb5-5b2e-4534-9f4d-c71983851766 InstallationDate: Installed on 2017-05-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/11/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692144/+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 1673344] [NEW] Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager
Public bug reported: My wireless connection completely disappears and isn't recognized along with my NIC card and doesn't come back until I reboot even if I restart network manager. I've attached the required files showing what my wifi information looks like connected and what it looks like when the problem occurs hopefully a fix or workaround can be found this happens several times a day. Steps: 1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power management) 2) $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. wlp3s0IEEE 802.11 ESSID:"2.4ghz" Mode:Managed Frequency:2.437 GHz Access Point: E0:3F:29:93:3F:20 Bit Rate=144.4 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=60/70 Signal level=-50 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:55 Missed beacon:0 3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time 4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi 5) sudo systemctl restart network-manager.service I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11 ESSID:"2.4ghz"** $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. I have to reboot to get my wifi back and for ubunutu to recognize my wifi card back how can I prevent this. $ uname -a Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep iwlwifi 876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 876.891602] iwlwifi :03:00.0: Scan failed! ret -5 [ 877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 877.909397] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 877.909409] iwlwifi :03:00.0: Scan failed! ret -5 [ 878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 878.928364] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 878.928366] iwlwifi :03:00.0: Scan failed! ret -5 [ 879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 879.947170] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 879.947172] iwlwifi :03:00.0: Scan failed! ret -5 $ sudo lshw -C network [sudo] password for rt: *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 73 serial: 0c:8b:fd:2e:64:8e width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:31 memory:f7d0-f7d01fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.2 bus info: pci@:04:00.2 logical name: enp4s0f2 version: 0a serial: 00:90:f5:f9:d4:f8 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff memory:f000-f0003fff $ ethtool -i wlp3s0 | grep driver driver: iwlwifi $ dmesg | grep iwlwifi [3.183972] iwlwifi :03:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [3.214247] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [3.216284] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [3.216508] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [3.733932] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 [4.369906] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [4.370133] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [4.590402] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [4.590625] iwlwifi :03:00.0: L1 Disabled - LTR Enabled [ 2613.473520] iwlwifi 000
[Kernel-packages] [Bug 1591075] [NEW] package linux-image-4.4.0-24-generic 4.4.0-24.43 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet
Public bug reported: The bug came when I've started the computer. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1728 F pulseaudio Date: Fri Jun 10 07:20:02 2016 DpkgTerminalLog: Uitpakken van .../firefox_47.0+build3-0ubuntu0.16.04.1_amd64.deb wordt voorbereid... Bezig met uitpakken van firefox (47.0+build3-0ubuntu0.16.04.1) over (46.0.1+build1-0ubuntu0.16.04.2) ... dpkg: fout bij verwerken van archief /var/cache/apt/archives/firefox-locale-en_47.0+build3-0ubuntu0.16.04.1_amd64.deb (--unpack): krijg geen toegang tot archief: Bestand of map bestaat niet ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet HibernationDevice: RESUME=UUID=48b92713-6bc2-435f-ad62-ce59474039c8 InstallationDate: Installed on 2016-04-23 (47 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. OptiPlex 760 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=a1ef524a-bdb1-417c-9c84-8835da6abba0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-24-generic 4.4.0-24.43 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0F373D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0F373D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- 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/1591075 Title: package linux-image-4.4.0-24-generic 4.4.0-24.43 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet Status in linux package in Ubuntu: Confirmed Bug description: The bug came when I've started the computer. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1728 F pulseaudio Date: Fri Jun 10 07:20:02 2016 DpkgTerminalLog: Uitpakken van .../firefox_47.0+build3-0ubuntu0.16.04.1_amd64.deb wordt voorbereid... Bezig met uitpakken van firefox (47.0+build3-0ubuntu0.16.04.1) over (46.0.1+build1-0ubuntu0.16.04.2) ... dpkg: fout bij verwerken van archief /var/cache/apt/archives/firefox-locale-en_47.0+build3-0ubuntu0.16.04.1_amd64.deb (--unpack): krijg geen toegang tot archief: Bestand of map bestaat niet ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet HibernationDevice: RESUME=UUID=48b92713-6bc2-435f-ad62-ce59474039c8 InstallationDate: Installed on 2016-04-23 (47 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. OptiPlex 760 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=a1ef524a-bdb1-417c-9c84-8835da6abba0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-24-generic 4.4.0-24.43 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0F373D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0F373D:rvrA00:cvnDellInc.:ct15
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
Aquaris M10, running first update after purchase. Screen comes on to lock prompt, stays on and even pressing power button it goes off for 1 second then back on again. -- 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/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+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 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
This is a real show stopper for hybrid graphic laptop. I had to reinstall 15.10. I will be interested to see the fix for this one. -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1546092] Re: computer freezes frequently
I can easily grab more kernel.log files if it helps. Just let me know. -- 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/1546092 Title: computer freezes frequently Status in linux package in Ubuntu: Confirmed Bug description: Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have not been able to create any repro steps, it feels quite random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1780 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 08:26:12 2016 HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8 InstallationDate: Installed on 2016-02-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: TOSHIBA Satellite L15W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.00 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 0670 dmi.board.vendor: FF40 dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L15W-B dmi.product.version: PSKVUU-00S01U dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546092/+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 1546092] [NEW] computer freezes frequently
Public bug reported: Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have not been able to create any repro steps, it feels quite random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1780 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 08:26:12 2016 HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8 InstallationDate: Installed on 2016-02-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: TOSHIBA Satellite L15W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.00 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 0670 dmi.board.vendor: FF40 dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L15W-B dmi.product.version: PSKVUU-00S01U dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1546092 Title: computer freezes frequently Status in linux package in Ubuntu: Confirmed Bug description: Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have not been able to create any repro steps, it feels quite random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1780 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 08:26:12 2016 HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8 InstallationDate: Installed on 2016-02-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: TOSHIBA Satellite L15W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.00 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 0670 dmi.board.vendor: FF40 dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L15W-B dmi.product.version: PSKVUU-00S01U dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546092/+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 1514976] [NEW] package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: not sure what other information would be useful ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Tue Nov 10 07:56:50 2015 DpkgTerminalLog: Log started: 2015-11-10 07:54:30 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2015-09-22 (49 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1514976 Title: package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux-lts-vivid package in Ubuntu: New Bug description: not sure what other information would be useful ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Tue Nov 10 07:56:50 2015 DpkgTerminalLog: Log started: 2015-11-10 07:54:30 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2015-09-22 (49 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1514976/+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 1390604] Re: Outbound TCP Throughput drops to zero for several drivers
This bug was not discovered by me. Instead, this is a tracking bug for
getting an upstream fix included in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1390604
Title:
Outbound TCP Throughput drops to zero for several drivers
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
There is a bug with TCP in kernel 3.16+ described as:
"Some drivers are unable to perform TX completions in a bound time.
They instead call skb_orphan()
Problem is skb_fclone_busy() has to detect this case, otherwise
we block TCP retransmits and can freeze unlucky tcp sessions on
mostly idle hosts."
A patch for this has been submitted upstream:
https://patchwork.ozlabs.org/patch/405110/
The Google engineer that submitted that patch also adds the following:
Backported patch for 3.16 or 3.17 kernel is much simpler :
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 4e4932b5079b..a8794367cd20 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2082,7 +2082,8 @@ static bool skb_still_in_host_queue(const struct sock
*sk,
const struct sk_buff *fclone = skb + 1;
if (unlikely(skb->fclone == SKB_FCLONE_ORIG &&
-fclone->fclone == SKB_FCLONE_CLONE)) {
+fclone->fclone == SKB_FCLONE_CLONE &&
+fclone->sk == sk)) {
NET_INC_STATS_BH(sock_net(sk),
LINUX_MIB_TCPSPURIOUS_RTX_HOSTQUEUES);
return true;
I do not believe that this problem affects any release prior to 14.10, and I
don't know which version of the patch you may need, but have included both.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390604/+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 1390604] [NEW] Outbound TCP Throughput drops to zero for several drivers
Public bug reported:
There is a bug with TCP in kernel 3.16+ described as:
"Some drivers are unable to perform TX completions in a bound time.
They instead call skb_orphan()
Problem is skb_fclone_busy() has to detect this case, otherwise
we block TCP retransmits and can freeze unlucky tcp sessions on
mostly idle hosts."
A patch for this has been submitted upstream:
https://patchwork.ozlabs.org/patch/405110/
The Google engineer that submitted that patch also adds the following:
Backported patch for 3.16 or 3.17 kernel is much simpler :
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 4e4932b5079b..a8794367cd20 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2082,7 +2082,8 @@ static bool skb_still_in_host_queue(const struct sock *sk,
const struct sk_buff *fclone = skb + 1;
if (unlikely(skb->fclone == SKB_FCLONE_ORIG &&
-fclone->fclone == SKB_FCLONE_CLONE)) {
+fclone->fclone == SKB_FCLONE_CLONE &&
+fclone->sk == sk)) {
NET_INC_STATS_BH(sock_net(sk),
LINUX_MIB_TCPSPURIOUS_RTX_HOSTQUEUES);
return true;
I do not believe that this problem affects any release prior to 14.10, and I
don't know which version of the patch you may need, but have included both.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1390604
Title:
Outbound TCP Throughput drops to zero for several drivers
Status in “linux” package in Ubuntu:
New
Bug description:
There is a bug with TCP in kernel 3.16+ described as:
"Some drivers are unable to perform TX completions in a bound time.
They instead call skb_orphan()
Problem is skb_fclone_busy() has to detect this case, otherwise
we block TCP retransmits and can freeze unlucky tcp sessions on
mostly idle hosts."
A patch for this has been submitted upstream:
https://patchwork.ozlabs.org/patch/405110/
The Google engineer that submitted that patch also adds the following:
Backported patch for 3.16 or 3.17 kernel is much simpler :
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 4e4932b5079b..a8794367cd20 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2082,7 +2082,8 @@ static bool skb_still_in_host_queue(const struct sock
*sk,
const struct sk_buff *fclone = skb + 1;
if (unlikely(skb->fclone == SKB_FCLONE_ORIG &&
-fclone->fclone == SKB_FCLONE_CLONE)) {
+fclone->fclone == SKB_FCLONE_CLONE &&
+fclone->sk == sk)) {
NET_INC_STATS_BH(sock_net(sk),
LINUX_MIB_TCPSPURIOUS_RTX_HOSTQUEUES);
return true;
I do not believe that this problem affects any release prior to 14.10, and I
don't know which version of the patch you may need, but have included both.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390604/+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 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
Solution to my problem - (Thank you Rick Forberg!) Linux Mint 17 Qiana won't install - keeps rebooting. It doesn't matter if the installation medium is a flash drive or CD. Once the live version loads it immediately reboots. There isn't enough time to install it. Once I managed to actually install it after dozens of tries. The result was it would get to the login, accept my credentials then reboot before actually loading. Thankfully after reading several of the posts on this page I was able to work out a procedure to install the OS, then fix the issue for my MSI desktops. Most of the Desktops at work running Linux Mint are custom built MSI boards with the following configurations: Motherboard: MSI A78M-E45 BIOS: AMI BIOS 25.1 (2013-12-09) & 25.3 (2014-03-19) APU: AMD A10-5800K (quad core) Trinity 3.8 GHz RAM: Patriot Viper DDR3 2133 (PC3 17000) 4x4GB and Motherboard: MSI FM2-A55M-E33 BIOS: E7721AMS v11.4 (2013-10-23) APU: AMD A8-5600K (quad core) 3.60GHz RAM: HyperX DDR3 1600 (PC3 12800) 2x4GB Both desktop configurations had the same problem. They were running Linux Mint 15 and 16. I have now replaced some of them with Qiana 17. Installing Linux Mint 17 on them had been a problem. Here is what I did to fix it: Once the live version started to load I kept the mouse constantly moving with one hand. With the other hand, using the keyboard, I started the installation utility and answered all the questions for the installation (I kept the mouse moving the entire time). Once the installation was finished the utility requested a restart. When the OS restarted I kept the mouse moving again, put in my login credentials and when Mint loaded I launched the terminal with ++t. In the terminal I updated the advanced packaging tool: apt-get update && apt-get upgrade (This takes quite a while, but it is important to keep the mouse moving the entire time) Then, I updated the display drivers: apt-get install fglrx-updates (you will need to prepend these commands with sudo if you are not root when you run them) After the the two commands (above) finished. I restarted the desktop and installation on the desktop has been stable ever since. This is true of all the desktops (configurations above). I hope this post will be helpful to anyone having problems with MSI motherboards. They are my systemboards of choice and I am very grateful to all the contributors of this forum. Your posts and insights have made this fix possible. -- 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/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in “linux” package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the "Ubuntu installer" application and click "Continue" button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 14.04.1 upcoming July release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/+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 1309578] Re: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
Same problem! Here’s the workaround I found. Hopefully my efforts will assist someone else, and point to a permanent fix. Hardware: Mobo: MSI A78-E35 BIOS: E77221AMS V30.2 Build Date: 02/21/2014 CPU:AMD A8-5600K APU with Radeon HD Graphics Mem:ADATA XPG V1.0 DDR3 1600, 8GB PS: 680W (Installing Ubuntu 14.04 server from CD but assume the results would be the same via USB load) After reading a post somewhere where the writer thought that the issue might be related to an “inactivity” timer and said he had some level of success with continuously moving his mouse during boot, I tried some combinations of this and have been able to boot and make a stable environment to work in. Being a complete Noob to all of this, I am not sure exactly why this works, but it is repeatable and might help lead to something that would help sort this out. I was able to run through the entire server load process by continuously moving my mouse during the entire process. Yes you need to type and make selections to configure your server while constantly moving the mouse, and no I didn’t try stopping because I wanted to get it loaded. It went flawlessly! A real PITA, but it worked. Next I found that I was able to boot by holding one of the keys the entire time the system is booting, but I get varying results. Seems like about 4 out of 5 times through the boot process, I am presented with a small font login prompt to my server. As soon as I release the key the system reloads and it’s time to hold the shift key again. About the 5th time through, I get a text menu that looks like this: *Ubuntu Advanced options for Ubuntu Memory test (memtest86+) Memory test (memtest86+, serial console 115200) When this text menu appears, you can release the shift key and work without holding it throughout the rest of the process. Now, if I just select Ubuntu, I go back into the boot loop. Hold the shift again! In the Advanced Options menu, I get two options; *Ubuntu with Linux 3.13.0-24-generic Ubuntu with Linux 3.13.0-24-generic (recovery mode) Selecting the Non-Recovery option takes me back to the boot loop, but selecting the Recovery Mode option gives me a colored text Recovery menu with eight options, all of which seem work with no problem. At this point I select the first option, , and on the following screen that warns that “graphic drivers require a full graphical boot and so will fail when resuming from recovery”. Now my server (RIX-ubuntu1) boots to a large font prompt: Ubuntu 14.04 LTS RIX-ubuntu1 tty1 RIX-ubuntu1 login: At this point I am able to login normally and the server will run without issue until it loses power, needs to be reloaded for maintenance, or any other reason you might have. This looks like a work–around, not a fix but it has allowed me to work in 14.04 without any other issues. I would love to know if this is repeatable for anyone else, and if some of you smarter more experienced users can use this to further refine the quest for a fix. Enjoy! -- 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/1309578 Title: Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k Status in “linux” package in Ubuntu: Incomplete Bug description: I have a custom built AMD System with the following hardware currently running on Linux Mint 16 : AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the "Ubuntu installer" application and click "Continue" button then the system restarts after 2-3 seconds. I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me. The BIOS version is the latest one downloaded from MSI official website which is version 11.5. Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version. I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong. This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04 -pc-restarts-after-i-click-continue-button-in I hope this gets fixed soon or with the 1
[Kernel-packages] [Bug 1319149] [NEW] HP Pavillion x360 boots very unreliably
Public bug reported: and the touch screen doesn't work ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1911 F pulseaudio CurrentDesktop: Unity Date: Tue May 13 14:47:04 2014 HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08 InstallationDate: Installed on 2014-05-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 097512405F00010420180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug kernel-key trusty -- 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/1319149 Title: HP Pavillion x360 boots very unreliably Status in “linux” package in Ubuntu: Confirmed Bug description: and the touch screen doesn't work ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1911 F pulseaudio CurrentDesktop: Unity Date: Tue May 13 14:47:04 2014 HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08 InstallationDate: Installed on 2014-05-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 097512405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319149/+subscriptions -- Mailing list: https://launchpad.net/~kernel
[Kernel-packages] [Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
I saw that 3.11.0-15 included a couple of backported fixes for shm races, including one (8380e1f50d3640498a3fec272ce32199de788a2d) that described my bug nearly exactly. I've been testing this kernel for the last couple of days, and have been unable to reproduce the kernel oops, so I think we can call this bug closed. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
The 3.11.5-031105.201311251400_amd64 (6b8fe6d417f93fa628779b1afd9e7717bbcb0572) kernel is bad, I was able to trigger the oops. However, the oops was only triggered after several days of usage, making me uneasy that the cause of the oops might be present in earlier kernels and I simply failed to trigger it. In the meantime until I get a new kernel to test, I'll go back to some previous kernels and test them a bit more to see if I can trigger anything. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
The 3.11.5-031105.201311211301_amd64 (1104f1b038765d0e31262eecdea6010907194226) kernel seems to be good, no oops. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 870934] Re: USB sound card not detected
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- 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/870934 Title: USB sound card not detected Status in “linux” package in Ubuntu: Fix Released Bug description: usb logitech wireless headset not detected after latest update. The hardware works in other os's Description: Ubuntu oneiric (development branch) Release: 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1498 F pulseaudio /dev/snd/controlC1: rick 1498 F pulseaudio Card0.Amixer.info: Card hw:0 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 Card1.Amixer.info: Card hw:1 'Audigy2'/'SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0x9000, irq 19' Mixer name : 'SigmaTel STAC9750,51' Components : 'AC97a:83847650' Controls : 211 Simple ctrls : 46 Date: Sat Oct 8 13:02:54 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2006 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-K8N Pro-SLI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd02/10/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NPro-SLI:rvrx.x: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/870934/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
http://kernel.ubuntu.com/~jsalisbury/lp1249719 seems to be empty. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
Will do, though the new specified commit (8bacb5ad41da1fde1c05165515c50e2911f16899) is actually before the previous commit (dbb563ec7b143323dd31520ab08c08394bc13381), which usually happens if "bad" is reported to the bisection, whereas all the results to date have been "good". -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
The 3.11.5-031105.201311181306_amd64 (dbb563ec7b143323dd31520ab08c08394bc13381) kernel is good, no oops. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
The 3.11.5-031105.201311151139_amd64 (b340404549c872099aec7554439a1821c0708878) kernel is good, no oops. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
Hello, I tested the three specified kernels, and v3.11.6 was the first one in which I could trigger the oops. -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+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 1249719] [NEW] Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [] touch_atime+0x17/0x140
Public bug reported: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-oops saucy ** Attachment added: "Oops message" https://bugs.launchpad.net/bugs/1249719/+attachment/3904209/+files/oops-dmesg -- 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: New Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True
[Kernel-packages] [Bug 1133054] Re: Bluetooth devices won't reconnect after suspend/resume
Andreas, Unfortunately, I have not been able to resolve this. I just switched back to using an external bluetooth keyboard after several months of using the mouse only + my laptop's internal keyboard, in which time I did not experience this issue at all. I am trying to figure out a scenario in which I can reproduce this reliably, but unfortunately I have not yet been able to do so. Sometimes when I resume, one or both of my bluetooth devices won't reconnect until I log out. Sometimes they both work fine when I resume. BTW, I'm using an Apple keyboard (model A1314) and a Gigabyte mouse (model GM-M7700B). -- 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/1133054 Title: Bluetooth devices won't reconnect after suspend/resume Status in “bluez” package in Ubuntu: Confirmed Bug description: I use a bluetooth keyboard and a bluetooth mouse. After I suspend/resume the system, I have issues using them. Sometimes one will work normally and not the other; sometimes neither will work. Toggling bluetooth off and on doesn't help. I have even gone so far as to delete the offending device from the Bluetooth settings and re-pair it. When I do this, the pairing always fails--it will see the device but the pairing will error out when I try to pair it. The only workaround I have found is to log out. As soon as I get back to the login screen, both devices immediately start working again. HCI log attached, per instructions given by apport-bug. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: bluetooth 4.101-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Feb 25 18:31:59 2013 InstallationDate: Installed on 2012-09-22 (156 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: TOSHIBA Satellite A305 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=dcedb5c2-7281-4ce4-9463-6fdf34bc89c5 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to quantal on 2012-10-24 (124 days ago) dmi.bios.date: 02/13/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd02/13/2009:svnTOSHIBA:pnSatelliteA305:pvrPSAG0U-02701V:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Satellite A305 dmi.product.version: PSAG0U-02701V dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:1B:DC:0F:A6:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:73345 acl:4132 sco:0 events:246 errors:0 TX bytes:1723 acl:55 sco:0 commands:55 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1133054/+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 1216492] Re: No Wireless
This issue is on a new computer with a new install of 13.04. I know how to install the latest upstream kernel, but how do I get it back to what it was before as I'll need the security updates as it is my son's computer. -- 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/1216492 Title: No Wireless Status in “linux” package in Ubuntu: Incomplete Bug description: Wireless for the Realtek device does not work. Seems to be no workaround. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: conor 1852 F pulseaudio CurrentDmesg: [ 15.456455] alx :03:00.0: irq 46 for MSI/MSI-X [ 15.456458] alx :03:00.0: irq 47 for MSI/MSI-X [ 15.456461] alx :03:00.0: irq 48 for MSI/MSI-X [ 15.456464] alx :03:00.0: irq 49 for MSI/MSI-X [ 15.457672] alx :03:00.0 eth0: NIC Link Up: 100 Mbps Full Date: Sat Aug 24 23:12:45 2013 HibernationDevice: RESUME=UUID=e68d891f-507c-4b9a-ad88-30d81ad0808f InstallationDate: Installed on 2013-08-25 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L75-A MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=3a5cea6c-85f8-44b9-b74c-e4819cc185a5 ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd04/30/2013:svnTOSHIBA:pnSatelliteL75-A:pvrPSKN2U-00V00C:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L75-A dmi.product.version: PSKN2U-00V00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1216492/+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 1216492] [NEW] No Wireless
Public bug reported: Wireless for the Realtek device does not work. Seems to be no workaround. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: conor 1852 F pulseaudio CurrentDmesg: [ 15.456455] alx :03:00.0: irq 46 for MSI/MSI-X [ 15.456458] alx :03:00.0: irq 47 for MSI/MSI-X [ 15.456461] alx :03:00.0: irq 48 for MSI/MSI-X [ 15.456464] alx :03:00.0: irq 49 for MSI/MSI-X [ 15.457672] alx :03:00.0 eth0: NIC Link Up: 100 Mbps Full Date: Sat Aug 24 23:12:45 2013 HibernationDevice: RESUME=UUID=e68d891f-507c-4b9a-ad88-30d81ad0808f InstallationDate: Installed on 2013-08-25 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L75-A MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=3a5cea6c-85f8-44b9-b74c-e4819cc185a5 ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd04/30/2013:svnTOSHIBA:pnSatelliteL75-A:pvrPSKN2U-00V00C:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L75-A dmi.product.version: PSKN2U-00V00C dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1216492 Title: No Wireless Status in “linux” package in Ubuntu: New Bug description: Wireless for the Realtek device does not work. Seems to be no workaround. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: conor 1852 F pulseaudio CurrentDmesg: [ 15.456455] alx :03:00.0: irq 46 for MSI/MSI-X [ 15.456458] alx :03:00.0: irq 47 for MSI/MSI-X [ 15.456461] alx :03:00.0: irq 48 for MSI/MSI-X [ 15.456464] alx :03:00.0: irq 49 for MSI/MSI-X [ 15.457672] alx :03:00.0 eth0: NIC Link Up: 100 Mbps Full Date: Sat Aug 24 23:12:45 2013 HibernationDevice: RESUME=UUID=e68d891f-507c-4b9a-ad88-30d81ad0808f InstallationDate: Installed on 2013-08-25 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L75-A MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=3a5cea6c-85f8-44b9-b74c-e4819cc185a5 ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd04/30/2013:svnTOSHIBA:pnSatelli
[Kernel-packages] [Bug 1096989] Re: 10ec:8179 No wireless support for Lenovo IdeaCentre Q190 (RTL8188E)
Is there anything I can do to help? I just brought a brand new Toshiba Satellite L75 and it's a bummer I can't put Ubuntu on it thanks to this little bug. -- 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/1096989 Title: 10ec:8179 No wireless support for Lenovo IdeaCentre Q190 (RTL8188E) Status in HWE Next Project: New Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Bug description: I'm on 12.10. The wifi adapter doesn't seem to be recognized at all: doesn't show up in NetworkManager, no adapter listed by iwconfig. The wifi card seems to be a RTL8188E (lspci -nn tells me it's 10ec:8179). I've tried to: - install the Realtek driver for the RTL8188CE (seemed close enough...) - install the driver from https://github.com/tianon/linux-rtlwifi-8188ce - install linux-backports-modules-cw - upgrade to kernel 3.7 None of those worked. --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cat1782 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=b597ccff-c6a0-4caf-8d7a-86b5885c2e71 InstallationDate: Installed on 2013-01-07 (29 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 10115 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=181643fb-824f-49b7-bad9-b8a31c74a430 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.95 RfKill: Tags: quantal running-unity Uname: Linux 3.5.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EZKT12AUS dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvrEZKT12AUS:bd09/21/2012:svnLENOVO:pn10115:pvrIdeaCentreQ190:rvnLENOVO:rnINVALID:rvrWin8STDMMDPKIPG:cvnLENOVO:ct3:cvrChassisVersion: dmi.product.name: 10115 dmi.product.version: IdeaCentre Q190 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1096989/+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
