[Kernel-packages] [Bug 1810488] [NEW] Dummy bug for testing (please ignore)
Public bug reported: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. ** Affects: linux (Ubuntu) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Have you tested 4.5.7 and 4.6 to see if this was the transition where the bug started? -- 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/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1799388] Comment bridged from LTC Bugzilla
--- Comment From mainam...@in.ibm.com 2019-01-04 01:24 EDT---
Michael,
Can you please verify above test kernel and update your comments ASAP
--
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/1799388
Title:
TM (Hardware Transactional Memory) instructions halt application on
baremetal POWER9 DD2.1
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Cosmic:
Incomplete
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-10-15
08:55:55 ==
+++ This bug was initially created as a clone of Bug #167756 +++
---Problem Description---
TM (Hardware Transactional Memory) instructions halt application on baremetal
POWER9 DD2.1
Contact Information = grom...@br.ibm.com
---Additional Hardware Info---
POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon.
Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested
with the same result) and running Linux from Linus' upstream tree [3] or
powerpc/next branch [4] is not working as expected. Once a TM instruction is
executed in a process (any instruction), the process halts completely and has
to be killed.
A simple test case is to execute a 'tend.' which accordingly to POWER8
behaviour and the ISA v3.00 if executed "in Non-transactional state is
treated as a no-op." [5]. It means that the instruction in the test
case below should be treated simply as a 'nop' instruction and the
process would terminate normally but instead it halts and the process
never terminates:
root@io83:~/gromero# cat t.c
int main() { asm ("tend.;"); }
root@io83:~/gromero# make t
make: 't' is up to date.
root@io83:~/gromero# ./t
^C
Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
result.
I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
contain all the TM fixes we have at the moment.
Thus, that issue affects any application that uses TM on a baremetal
POWER9 DD2.1 (pvr 004e 1201).
[1]
IBM-witherspoon-ibm-OP9_v1.19_1.160
op-build-v1.21.2-255-g6ad1636-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.5-op910-1
hostboot-ed53939
linux-4.14.24-openpower1-paed97e8
petitboot-v1.6.6-p41a158a
machine-xml-4af
occ-ef5d466
hostboot-binaries-6a92b6d
capp-ucode-p9-dd2-v3
sbe-7e02c23
[2]
open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920
[3] https://github.com/torvalds/linux.git (master)
[4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next)
[5] Power ISA - Book II, p. 894
Stack trace output:
no
Oops output:
no
Userspace tool common name: any tool using TM instruction set
Userspace rpm: not relevant
The userspace tool has the following bit modes: 64-bit
System Dump Info:
The system is not configured to capture a system dump.
Userspace tool obtained from project website: na
*Additional Instructions for grom...@br.ibm.com:
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.
The following patch fixes this issue:
http://patchwork.ozlabs.org/patch/968375/
Author: Michael Neuling
Date: Tue Sep 11 13:07:56 2018 +1000
powerpc/tm: Fix HFSCR bit for no suspend case
Currently on P9N DD2.1 we end up taking infinite TM facility
unavailable exceptions on the first TM usage by userspace.
In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
off via CPU dt-ftrs but told to (partially) use it via
OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from
dt-ftrs but we need to turn it on for the no suspend case.
This patch fixes this by enabling HFSCR TM in this case.
Cc: sta...@vger.kernel.org # 4.15+
Signed-off-by: Michael Neuling
== Comment: #2 - Michael Ranweiler - 2018-10-15
13:52:13 ==
This is in the powerpc -next branch:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd9a8c5a87395b6f05552c3b44e42fdc95760552
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I have this problem with Intel Xeon CPU E5-2620 v4. I do not think it is CPU related. -- 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/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1796839] Comment bridged from LTC Bugzilla
--- Comment From mainam...@in.ibm.com 2019-01-04 00:33 EDT--- (In reply to comment #5) > I believe the "uname -a" output shows that this issue was observed with a > custom, i.e. a non-Ubuntu, kernel. Could you confirm that the issue is seen > with an unmodified Ubuntu kernel? > > Also, do you have a proposed (kernel?) patch that resolves this issue? > > Thanks. Hariharan Any updates on this? Do you observe this issue on released kernel version of ubuntu? -- 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/1796839 Title: Only 64 Memory regions or dimms supported for Hotplug. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1796839/+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 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Yeah, they all seem to be similar CPU. Have you tried to see if you get the same results as above when you try to run 4.5.7 and 4.6? It's sad because, apart from that, the computers run just fine. -- 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/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1800901] Re: Updating breaks wifi on Intel Compute Stick
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1800901 Title: Updating breaks wifi on Intel Compute Stick Status in linux package in Ubuntu: Expired Bug description: On an Intel Compute Stick model STCK1A8LFC the stock install works fine. The default kernel: uname -a Linux joe-STCK1A8LFC 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux When an apt-get update/upgrade is run all network connectivity is lost. Run wpa_cli scan shows no networks at all. A return to the factory default returns connectivity. Any help would be greatly appreciated. Cheers,-Joe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800901/+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 1801564] Re: Can't connect second monitor on NVidia over adapter DVI->VGA
[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Expired -- 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/1801564 Title: Can't connect second monitor on NVidia over adapter DVI->VGA Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835] MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: STRIX B250F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Nov 4 07:41:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1801564/+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 1801564] Re: Can't connect second monitor on NVidia over adapter DVI->VGA
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1801564 Title: Can't connect second monitor on NVidia over adapter DVI->VGA Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: NVidia GF108 (10de:0df8) Quadro 600 xserver-xorg-video-nouveau,nvidia-graphics-drivers : DisplayPort=Samsung 27" DVI->VGA=Acer V193HQ INTEL : DVI=BenQ FP93G X ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 07:43:17 2018 DistUpgraded: 2018-10-29 18:00:47,682 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108GL [Quadro 600] [10de:0835] MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=bc343c51-118f-49ba-a3a5-283e6bbd0290 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-29 (5 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: STRIX B250F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXB250FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Nov 4 07:41:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1801564/+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 1810390] Re: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1810390 Title: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: The test failed with file attribute not match, for "file", we're expecting: "c--- a/file", but lsattr shows: "c- a/file" for "file2", we're expecting: " a/file2", but lsattr shows: "-- a/file2" for "directory", we're expecting: " a", but lsattr shows: "-- a" This patch could be found in the Bionic tree. https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e So this might be a test case issue. fix 78a017a2c92df9b571db0a55a016280f9019c65e Btrfs: add missing compression property remove in btrfs_ioctl_setflags The behaviour of a 'chattr -c' consists of getting the current flags, clearing the FS_COMPR_FL bit and then sending the result to the set flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags passed to the ioctl. This results in the compression property not being cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL was set in the received flags. Incorrect attributes on file, got: c- a/file Incorrect attributes on file2, got: -- a/file2 Incorrect attributes on directory, got: -- a ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 3 08:42 seq crw-rw 1 root audio 116, 33 Jan 3 08:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 08:47:04 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810390/+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 1796553] Re: BT mouse getting reset during operation
Sorry for the belated response.
Please test if this kernel works for you, without using
"btusb.enable_autosuspend=0":
https://people.canonical.com/~khfeng/lp1796553/
--
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/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
(note: It's unclear to me if that's a kernel regression or an issue with
bluez)
I've been using this particular combination of Bluetooth mouse ("TECKNET
BM306") & laptop ("Dell Latitude E7240") for over a year now.
It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
a strange disconnect behaviour:
1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again.
when this happens, dmesg reports:
[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
ehci-pci
Disabling bluetooth and enabling it again results in:
[57833.455866] usb 1-1.3: USB disconnect, device number 18
[57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
[57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
[57837.016248] usb 1-1.3: New USB device found, idVendor=8087,
idProduct=07dc, bcdDevice= 0.01
[57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
[57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
[57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
[57841.724587] input: TECKNET BM306 Mouse as
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
[57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05
$ bluetoothctl --version
bluetoothctl: 5.50
$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: FC:F8:AE:45:3C:05 ACL MTU: 1021:5 SCO MTU: 96:5
UP RUNNING PSCAN
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6) Revision: 0x500
LMP Version: 4.0 (0x6) Subversion: 0x500
Manufacturer: Intel Corp. (2)
$ bluetoothctl
Agent registered
[TECKNET BM306]# show
Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[TECKNET BM306]# devices
Device 20:9B:A5:68:AE:67 SoundBuds Flow
Device DC:2C:26:01:24:23 TECKNET BM306
Device 88:71:E5:0E:6B:99 Echo-HPT
Device 00:0B:E4:A0:A2:14 Nokia BH-103
Device A8:96:75:8B:4F:49 Moto G5S Plus
Device 00:02:5B:20:75:3C Trust SPK-02
Device 88:75:98:F2:5C:9E NS9+
Device 00:E0:4C:D5:E0:F5 SoundCore mini
[TECKNET BM306]# info DC:2C:26:01:24:23
Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129
$ rfkill list
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
[Kernel-packages] [Bug 1810345] Re: kernel: general protection fault: 0000 [#1] SMP PTI
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/ -- 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/1810345 Title: kernel: general protection fault: [#1] SMP PTI Status in linux package in Ubuntu: Confirmed Bug description: using 18.10, all updates included. Desktop (gnome on wayland) is crashing from time to time at idle, or on reactivating from screensaver or while working(mostly while playing videos in browsers) where only sysreq gets to reboot. Running kernel 4.18.0-13-generic #14-Ubuntu Looking at the logs i found: Jan 2 23:29:07 ThinkPad kernel: [44709.167257] general protection fault: [#1] SMP PTI Jan 2 23:29:07 ThinkPad kernel: [44709.167284] CPU: 0 PID: 22311 Comm: kworker/u17:0 Not tainted 4.18.0-13-generic #14-Ubuntu Jan 2 23:29:07 ThinkPad kernel: [44709.167286] Hardware name: LENOVO 2325TZX/2325TZX, BIOS G2ETB3WW (2.73 ) 06/19/2018 Jan 2 23:29:07 ThinkPad kernel: [44709.167315] Workqueue: hci0 hci_rx_work [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167325] RIP: 0010:__wake_up_common+0xb4/0x140 Jan 2 23:29:07 ThinkPad kernel: [44709.167327] Code: 4d 85 ed 74 25 41 83 c4 01 41 83 fc 40 7e 1b 49 8d 46 18 48 39 c3 75 70 8b 45 c4 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <49> 8b 56 18 49 8d 46 18 4c 89 f7 4c 8d 72 e8 48 39 c3 75 94 eb d8 Jan 2 23:29:07 ThinkPad kernel: [44709.167376] RSP: 0018:a941c3c0fbd8 EFLAGS: 00010083 Jan 2 23:29:07 ThinkPad kernel: [44709.167379] RAX: RBX: 9c5d5ef42008 RCX: Jan 2 23:29:07 ThinkPad kernel: [44709.167381] RDX: 0001 RSI: 0082 RDI: 0082 Jan 2 23:29:07 ThinkPad kernel: [44709.167384] RBP: a941c3c0fc18 R08: R09: a941c3c0fb50 Jan 2 23:29:07 ThinkPad kernel: [44709.167386] R10: 9c5e03920400 R11: 0a00 R12: 0002 Jan 2 23:29:07 ThinkPad kernel: [44709.167389] R13: a941c3c0fc30 R14: dead00e8 R15: Jan 2 23:29:07 ThinkPad kernel: [44709.167392] FS: () GS:9c5f1e20() knlGS: Jan 2 23:29:07 ThinkPad kernel: [44709.167395] CS: 0010 DS: ES: CR0: 80050033 Jan 2 23:29:07 ThinkPad kernel: [44709.167397] CR2: 7f741dc0 CR3: 0001cd20a005 CR4: 001606f0 Jan 2 23:29:07 ThinkPad kernel: [44709.167399] Call Trace: Jan 2 23:29:07 ThinkPad kernel: [44709.167407] __wake_up_common_lock+0x80/0xc0 Jan 2 23:29:07 ThinkPad kernel: [44709.167412] __wake_up+0x13/0x20 Jan 2 23:29:07 ThinkPad kernel: [44709.167418] sock_def_wakeup+0x36/0x40 Jan 2 23:29:07 ThinkPad kernel: [44709.167440] l2cap_sock_teardown_cb+0x192/0x1f0 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167460] l2cap_chan_del+0x4a/0x2f0 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167481] l2cap_sig_channel+0xb55/0x1270 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167486] ? __switch_to_asm+0x34/0x70 Jan 2 23:29:07 ThinkPad kernel: [44709.167490] ? __switch_to_asm+0x40/0x70 Jan 2 23:29:07 ThinkPad kernel: [44709.167493] ? __switch_to_asm+0x34/0x70 Jan 2 23:29:07 ThinkPad kernel: [44709.167513] l2cap_recv_frame+0x280/0xc80 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167517] ? __switch_to_asm+0x40/0x70 Jan 2 23:29:07 ThinkPad kernel: [44709.167519] ? __switch_to_asm+0x34/0x70 Jan 2 23:29:07 ThinkPad kernel: [44709.167542] l2cap_recv_acldata+0x2f6/0x300 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167558] hci_rx_work+0x28f/0x380 [bluetooth] Jan 2 23:29:07 ThinkPad kernel: [44709.167565] process_one_work+0x20f/0x3c0 Jan 2 23:29:07 ThinkPad kernel: [44709.167570] worker_thread+0x34/0x400 Jan 2 23:29:07 ThinkPad kernel: [44709.167575] kthread+0x120/0x140 Jan 2 23:29:07 ThinkPad kernel: [44709.167579] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 2 23:29:07 ThinkPad kernel: [44709.167583] ? kthread_bind+0x40/0x40 Jan 2 23:29:07 ThinkPad kernel: [44709.167586] ret_from_fork+0x35/0x40 Jan 2 23:29:07 ThinkPad kernel: [44709.167589] Modules linked in: rfcomm hidp rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm cmac bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic wmi_bmof intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel kvm irqbypass
[Kernel-packages] [Bug 1563110]
(In reply to Jacek Jagosz from comment #105) > (In reply to marcin19883 from comment #104) > > https://github.com/conexant/codec_drivers/commits/rpi-4.4.y > > > > Autor adding support linux kernel 4.18. > > Sorry for bothering, but did he try to merge it to the main kernel? Or do we > have to compile it ourselves from this branch? I have no idea. I'm a beginning linux user. I am currently using Arch Linux and the cx2072x kernel from AUR. It works great. Everything works, even better than on ubuntu 18.04. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1810457] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1810457 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream periodically. [Test Case] [Fix] Various upstream patches. [Regression Risk] The number of changes here obviously comes with regression risk. However, these drivers are only used for two HiSilicon SoCs and their corresponding development platforms - D05 and D06. We are therefore able to mitigate the risk by directly testing these changes on the impacted devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+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 1810457] [NEW] Update hisilicon SoC-specific drivers
Public bug reported: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream periodically. [Test Case] [Fix] Various upstream patches. [Regression Risk] The number of changes here obviously comes with regression risk. However, these drivers are only used for two HiSilicon SoCs and their corresponding development platforms - D05 and D06. We are therefore able to mitigate the risk by directly testing these changes on the impacted devices. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream periodically. [Test Case] [Fix] Various upstream patches. [Regression Risk] The number of changes here obviously comes with regression risk. However, these drivers are only used for two HiSilicon SoCs and their corresponding development platforms - D05 and D06. We are therefore able to mitigate the risk by directly testing these changes on the impacted devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+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 1801540]
Actually this workaround adds another problem, in games the sound is delayed... -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
A partial workaround which doesn't completely fix the issue but improves things is the following: Adding to /etc/pulse/default.pa, use_ucm=0 tsched=0 right after module- udev-detect and /etc/pulse/daemon resample-method = src-sinc-best-quality default-sample-format = s16le default-fragment-size-msec=80 default-sample-rate = 48000 Don't know which what specific parameter improved this, because when I test each one of those singularly doesn't totally fix the problem. The best results I can obtain are with all those combined -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
** Attachment added: "Output of cat /sys/bus/serio/devices/serio1/firmware_id" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5226759/+files/output.txt -- 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/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Hi, I still have this issue. Using Ubuntu 18.04 on Dell XPS 9570. Any way to get a workaround for that? -- 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/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in linux package in Ubuntu: Confirmed Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/847001/+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 1810407] Re: boot-hanger
** 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226752/+files/ProcEnviron.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226758/+files/WifiSyslog.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226756/+files/RfKill.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226751/+files/ProcCpuinfoMinimal.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226747/+files/IwConfig.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226755/+files/PulseList.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226745/+files/CRDA.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226746/+files/CurrentDmesg.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226748/+files/Lspci.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226753/+files/ProcInterrupts.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226754/+files/ProcModules.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226757/+files/UdevDb.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226749/+files/Lsusb.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226750/+files/ProcCpuinfo.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] Re: boot-hanger
apport information ** Tags added: apport-collected sylvia ** Description changed: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: peter 1740 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Linux 18.3 + HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 + InstallationDate: Installed on 2018-11-01 (63 days ago) + InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 + MachineType: Dell Inc. Inspiron 15-3552 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset + ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.157.21 + Tags: sylvia + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 4.4.0 + dmi.board.name: 079W3P + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 15-3552 + dmi.product.version: 4.4.0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1810407/+attachment/5226744/+files/AlsaInfo.txt -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Confirmed Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1740 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=e70c1188-343e-45c4-a61d-0fbffb3c9fc8 InstallationDate: Installed on 2018-11-01 (63 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171213 MachineType: Dell Inc. Inspiron 15-3552 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=06c86e11-8588-49b6-a40b-b214dba0c0a5 ro quiet splash nomedeset ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810430] Re: tpm_crb MSFT0101:00: can't request region for resource
Hi, tested with upstream 4.20 as requested and still the same symptoms... $ uname -a Linux blackserver 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.783454] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.783475] tpm_crb: probe of MSFT0101:00 failed with error -16 [0.937933] ima: No TPM chip found, activating TPM-bypass! $ ls -l /dev/tmp ls: cannot access '/dev/tmp': No such file or directory I've added the tag but it looks like a bot changed the status of this bug to confirmed before you first replied? Or have I missed a further confirmation that's needed? ** Description changed: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: kelvin 3554 F pulseaudio - /dev/snd/controlC0: kelvin 3554 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: kelvin 3554 F pulseaudio + /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: - linux-restricted-modules-4.15.0-43-generic N/A - linux-backports-modules-4.15.0-43-generic N/A - linux-firmware 1.173.2 + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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. ** 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/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: Confirmed Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
My latest posting on this bug issue posted in AMD communities copied here FYI: https://community.amd.com/thread/225795?start=90=0 102. Re: Ryzen linux kernel bug 196683 - Random Soft Lockup uncle yap uncle yap Jan 4, 2019 3:29 AM (in response to imshalla) Dear All, Some good news and discovery. My crisis is greatly improved so far after 1st 5 hours running without lockup now. All I did essentially was changing my Linux Kernel from 4.18.0-11-generic to 4.15.0-43-generic I had previously also tried 4.18.0-13-generic and found it equally bad. My highest suspicion is 4.18.0-X kernel's thread scheduler is/are buggy with a same bug that would freeze up some threads randomly and up to 12hours long and later randomly unfreeze them. I call that random because I can not find any consistent pattern on how it freeze / unfreeze. These hardly require a hard reset unless it is left frozen for very long time. If I discovered soon enough and gave soft reset by SSH command sudo systemctl restart sddm it will be recovered. It would be gdm instead of sddm if you are in ubuntu instead of kubuntu. My guess for this difference (between requiring a motherboard reset switch vs soft reset command) is that TOO MANY REPEATED THREAD FROZEN OVER LONGER TIME UNATTENDED. It is a guess only because I cannot afford the time to test and prove that. My faithful logical analysis and derivation is so, because this kernel thread scheduler bug will freeze more & more threads than it unfreeze over longer unattended time, and that critical kernel or driver module threads or ssh or bash itself could have been frozen, hence you have no more chance to soft reset / recover. I have proven that when only 1 or 2 threads frozen, servers, ssh, bash, and even ksysguard (CPUs usage / load percentage graphs) will still be running and I never found any single CPU core nor logical CPU (hyperthread) completely stuck in ZERO% usage. 265px-Ksysguard1.png When my X.org console freezes, mouse will freeze and CPU usage graph will all freeze, but usually still a good chance if I quickly ssh my favorite reset command sudo systemctl restart sddm it will be recovered. If I wasn't checking and left it frozen for long time, there had been a high chance of it completely not recoverable via ssh command, and reset switch became the only way to get system back rebooted up. Today, when I checked my CPU Pstate via kernel, it is not running any C6, but I mt BIOS setting neither DISABLED C6 nor use TYPICAL CURRENT IDLE, nor I am using kernel boot idle=nowait , but I think my F4E version BIOS by Gigabyte X470 had DISABLED C6 power state & forced TYPICAL CURRENT IDLE: ~$ cat /sys/devices/system/cpu/cpu*/cpuidle/state*/name POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL C1 C2 POLL >From existing state of stability I am optimistic to expect no further debugging on my system for now. My proposal for Kubuntu/Ubuntu users is to check kernel version to be other than version 4.18.0-X , and try older 4.15.x 1st, and newer version when they released, if your stability improved with alternate kernels than stay with them and await for improved kernels and try them when they became available. Thanks & regards uy -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. 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: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on
[Kernel-packages] [Bug 1810064] Re: UI hangs When booting Live version of Ubuntu 18.04
Due to the nature of this bug (a completely frozen screen, it isn't possible to get a log. ** 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/1810064 Title: UI hangs When booting Live version of Ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My system: Graphics: Card: Advanced Micro Devices [AMD/ATI] Device 98e4 bus-ID: 00:01.0 chip-ID: 1002:98e4 Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: fbdev,vesa,radeon) Resolution: 1366x768@60.03hz GLX Renderer: Gallium 0.4 on AMD STONEY (DRM 3.1.0, LLVM 3.8.0) GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes description: Notebook product: Inspiron 15-3565 (078E) vendor: Dell Inc. version: 1.7.0 serial: 9LWJ6L2 width: 64 bits capabilities: smbios-3.0 dmi-3.0 smp vsyscall32 configuration: boot=normal chassis=notebook family=Inspiron sku=078E uuid=44454C4C-4C00-1057-804A-B9C04F364C32 *-core description: Motherboard product: Inspiron 15-3565 vendor: Dell Inc. physical id: 0 version: A00 serial: .9LWJ6L2.CNWSC0083900Q7. slot: Default string *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 1.7.0 date: 10/23/2017 size: 64KiB capacity: 8128KiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial int17printer acpi usb biosbootspecification netboot uefi *-cache:0 description: L1 cache physical id: 17 slot: L1 CACHE size: 160KiB capacity: 160KiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 18 slot: L2 CACHE size: 1MiB capacity: 1MiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=2 *-memory description: System Memory physical id: 25 slot: System board or motherboard size: 4GiB *-bank:0 description: SODIMM DDR4 [empty] product: A1_PartNum0 vendor: physical id: 0 serial: A1_SerialNum0 slot: DIMM 0 width: 64 bits *-bank:1 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) product: 4ATF51264HZ-2G3E1 vendor: 009C360B physical id: 1 serial: 1B0B3BB5 slot: DIMM 1 size: 4GiB width: 64 bits clock: 2400MHz (0.4ns) *-cpu description: CPU product: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G vendor: Advanced Micro Devices [AMD] physical id: 2c bus info: cpu@0 version: AMD A6-9200 RADEON R4, 5 COMPUTE CORES 2C+3G slot: P0 size: 1620MHz capacity: 2GHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov cpufreq configuration: cores=2 enabledcores=2 threads=2 *-pci:0 description: Host bridge product: Advanced Micro Devices, Inc. [AMD] vendor: Advanced Micro Devices, Inc. [AMD] physical id: 100 bus info: pci@:00:00.0 version: 00 width: 32 bits clock: 33MHz *-generic:0 UNCLAIMED description: IOMMU product: Advanced Micro Devices, Inc. [AMD] vendor: Advanced Micro Devices, Inc. [AMD] physical id: 0.2 bus info: pci@:00:00.2
[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288
** Attachment added: "Ungespeichertes Dokument 1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+attachment/5226716/+files/Ungespeichertes%20Dokument%201 -- 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/1810130 Title: ic2-HTIX5288 Status in linux package in Ubuntu: Confirmed Bug description: touchpad not working Ubuntu Disco Dingo (development branch) WINBOOK 13 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: docmint2172 F pulseaudio /dev/snd/controlC1: docmint2172 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 00:55:26 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230) MachineType: AXDIA International GmbH WINBOOK 13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2017 dmi.bios.vendor: WINBOOK 13 dmi.bios.version: 1.6 dmi.board.asset.tag: Default string dmi.board.name: K132 dmi.board.vendor: AXDIA International GmbH dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: WINBOOK 13 dmi.product.sku: WINBOOK13-K132-02 dmi.product.version: Default string dmi.sys.vendor: AXDIA International GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/ -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1810407] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1810407 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: Incomplete Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Seems like this laptop has thunderbolt? Try plugging a USB or PCI device
into the port, unplug it, and see if it helps.
--
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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
New
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+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 1810407] Re: boot-hanger
** Package changed: plymouth (Ubuntu) => linux (Ubuntu) -- 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/1810407 Title: boot-hanger Status in linux package in Ubuntu: New Bug description: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810407/+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 1810407] [NEW] boot-hanger
You have been subscribed to a public bug: Hello, my Dell Inspiron-15-3552 with Linux version 4.15.0-43-generic has sometimes a boot-hanger. Then Linux does not come up. The very first lines of syslog gives the advice to investigate the WLAN named wlp1s0 (-> Attachment). Sincerely Peter ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: wlan -- boot-hanger https://bugs.launchpad.net/bugs/1810407 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/ -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1810430] Re: tpm_crb MSFT0101:00: can't request region for resource
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/ -- 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/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: Confirmed Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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/ubuntu/+source/linux/+bug/1810430/+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 1797753] Re: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)
No upstream support yet. Please refer to LP: #1740231 for more information. -- 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/1797753 Title: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput) Status in linux package in Ubuntu: Confirmed Bug description: I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after installation there is no wifi adapter and also touchpad not working firstly id lspci and in that the output i found of chip : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter secondly id did xinput but there was not device dected as touchpad after that i dual boot centos 7 along side ubunt in that touchpad is working but again wifi adapter not found please solve this issue for both ubuntu (wifi adapter not found and touchpad not detected) and centos (wifi adapter not found) i searched and read regarding this issue and tried all of the but didn't find any solution so at last i have hopes only on u all Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797753/+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 1810430] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: Confirmed Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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/ubuntu/+source/linux/+bug/1810430/+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 1810183] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1810183/+attachment/5226711/+files/ProcEnviron.txt -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
apport information ** Description changed: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-12-30 (4 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: linux (not installed) + Tags: cosmic + Uname: Linux 4.18.10-041810-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1810183/+attachment/5226710/+files/ProcCpuinfoMinimal.txt -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1810430] [NEW] tpm_crb MSFT0101:00: can't request region for resource
Public bug reported: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: New Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018
[Kernel-packages] [Bug 1810183] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1810183/+attachment/5226692/+files/ProcEnviron.txt -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
apport information ** Tags added: apport-collected cosmic ** Description changed: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-12-30 (4 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: linux (not installed) + Tags: cosmic + Uname: Linux 4.19.11-041911-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1810183/+attachment/5226691/+files/ProcCpuinfoMinimal.txt -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1790181] Re: /proc/diskstats shows weird values
After rebooting, the values are < 2^31 and utilization is reporting fine. I feel this is a 31/32 bit overflow 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
Hi Andy, As original author of the quirk, I don't think you need to copy the commit message as is, simply states the quirk can solve your issue should be suffice. Also, please send the patch to upstream so we can backport it. -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
Fixed patch - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/5 -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
FIXED PATCH 2c-hid: Add a small delay for Synaptics/Elan touchpanel Synaptics/Elan touchpanel sometimes does not work in desktop session although it works in display manager. During user logging, the display manager exits, close the HID device, then the device gets runtime suspended and powered off. The desktop session begins shortly after, opens the HID device, then the device gets runtime resumed and powered on. If the trasition from display manager to desktop sesesion is fast, the touchpanel cannot switch from powered off to powered on in short timeframe. So add a small delay to workaround the issue. ** Patch added: "i2c_hid_fixed.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/+attachment/5226680/+files/i2c_hid_fixed.patch -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
** Tags added: patch -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1810029] Re: Setting up linux-headers-4.18.0-13-generic causes a crash
This bug is recurring, it happened before and it's still there Setting up linux-headers-4.15.0-43-generic (4.15.0-43.46) ... Progress: [ 86%] [#.] Very annoying as you have to kill the process and deal with the consequences! -- 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/1810029 Title: Setting up linux-headers-4.18.0-13-generic causes a crash Status in linux package in Ubuntu: Confirmed Bug description: When running apt-update the install freezes at "Setting up linux- headers-4.18.0-13-generic (4.18.0-13.14) ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810029/+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 1690085]
My understanding is that idle=nomwait disables the use of the MWAIT instruction in the kernel implementation of the CPU idle state. I also *think* that, under the hood, disabling C6 and the "Typical Power idle" option also have a similar (or perhaps the same?) effect of reducing the use of MWAIT. E.g., since I started enabling the "Typical Power idle" option in my BIOS, at every boot I have the following message showing up in the kernel logs: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) However, because the MWAIT instruction is part of SSE3 [1], it might end up being executed by any software which was compiled with support for SSE3. So I believe that disabling MWAIT for idle states greatly reduces the risk of getting these MWAIT hangs (simply because the instruction will end up being executed much less), but it will not completely eliminate them. Thus, it seems like the only bulletproof solution is either to upgrade to Ryzen+/Ryzen2, or to disable hypterthreading. [1] https://en.wikipedia.org/wiki/SSE3 -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general
[Kernel-packages] [Bug 1690085]
(In reply to Michael from comment #459) > I think this bug is mostly about the official AMD Errata 1109 "MWAIT > Instruction May Hang a Thread". > > This is described here ( > https://developer.amd.com/wp-content/resources/55449_1.12.pdf ) as: > > "Under a highly specific and detailed set of internal timing conditions, the > MWAIT instruction may cause a > thread to hang in SMT (Simultaneous Multithreading) Mode." > > Since this is a nofix for AMD, this must be fixed by the OS. The AMD > document states: > > "Suggested Workaround > System software may contain the workaround for this erratum." > > So, unfortunately AMD will never solve that hardware error. I suggest they > change the first two letters of their company name ;) > > This in fact leaves every linux system with a Ryzen CPU instable, so this > should be considered serious. > > I didn't read a comment from any kernel developer in the history of this bug > report. Did I overlook something? > > Question: Will the Linux kernel ever implement a workaround (as suggested by > AMD?? idle=nomwait kernel option fixed all hangs for me -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core
[Kernel-packages] [Bug 1690085]
(In reply to Bráulio Bhavamitra from comment #460) > (In reply to Michael from comment #459) > > I think this bug is mostly about the official AMD Errata 1109 "MWAIT > > (...) > > > > Question: Will the Linux kernel ever implement a workaround (as suggested > by > > AMD?? > > idle=nomwait kernel option fixed all hangs for me True, same for me. But, is every future ZEN user doomed to go through a valley of pain and possibly find this workaround themselves or is it going to be default at any time? -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom,
[Kernel-packages] [Bug 1690085]
I think this bug is mostly about the official AMD Errata 1109 "MWAIT Instruction May Hang a Thread". This is described here ( https://developer.amd.com/wp- content/resources/55449_1.12.pdf ) as: "Under a highly specific and detailed set of internal timing conditions, the MWAIT instruction may cause a thread to hang in SMT (Simultaneous Multithreading) Mode." Since this is a nofix for AMD, this must be fixed by the OS. The AMD document states: "Suggested Workaround System software may contain the workaround for this erratum." So, unfortunately AMD will never solve that hardware error. I suggest they change the first two letters of their company name ;) This in fact leaves every linux system with a Ryzen CPU instable, so this should be considered serious. I didn't read a comment from any kernel developer in the history of this bug report. Did I overlook something? Question: Will the Linux kernel ever implement a workaround (as suggested by AMD?? -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Just preliminary results. Done 2 cycles of sleep-wake. No signs of missing wifi+bluetooth. It seems encouraging. -- 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/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 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 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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 1810416] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Try making a Live USB with some distro, for example 18.04, run it and see if it suspends properly. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1810416] [NEW] SD card error mmc0: error -110 whilst initialising SD card
Public bug reported: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: New Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I'm on 2nd gen, and the issue is the same. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
tazesimit, do you have issues on 2nd gen? I had this laptop or many years, and it never had any issues with Ubuntu 16.04. Not sure if any of the solutions in this thread will help you, since they are specific for 6th gen and 18.04. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version:
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi all, Before I try these on my 2ND GEN x1c, do you know if it would work? I have ubuntu 16.04 installed and I do not want to change it since it should be very hard to restore some of the software I use on this system. I got this laptop 6 months ago and I do not like(and cannot) spend much money on electronics. Also do you think pushing lenovo hard on this would make them solve this for linux as well? A few of us sending some requests would be helpful I hope. Thanks for the effort from more experienced users so far! -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1
[Kernel-packages] [Bug 1810406] [NEW] Whiptail stucks during kernel upgrade
Public bug reported: While upgrading kernel, whiptail process stucks and the update process hangs forever nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build root 25534 0.0 0.0 63712 4316 pts/0S+ 13:02 0:00 | \_ sudo dpkg --configure -a root 25535 0.0 0.0 26600 10952 pts/0S+ 13:02 0:00 | \_ dpkg --configure -a root 25570 0.0 0.0 4628 784 pts/0S+ 13:02 0:00 | \_ /bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-43-generic.postinst configure root 25571 0.0 0.0 4520 768 pts/0S+ 13:02 0:00 | \_ run-parts --report --exit-on-error --arg=4.15.0-43-generic /etc/kernel/header_postinst.d root 25572 0.0 0.0 4628 1896 pts/0S+ 13:02 0:00 | \_ /bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-43-generic root 25582 0.0 0.0 15896 6452 pts/0S+ 13:02 0:00 | \_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-43-generic root 26396 0.0 0.0 16016 5724 pts/0S+ 13:02 0:00 | \_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-43-generic root 1718 0.1 0.1 104160 22504 pts/0S+ 13:02 0:00 | \_ /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key root 1750 0.0 0.0 4628 1864 pts/0S+ 13:02 0:00 | \_ /bin/sh /usr/sbin/update-secureboot-policy --enroll-key root 1897 0.0 0.0 24924 4320 pts/0S+ 13:03 0:00 | \_ whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --inputbox -- teo 22242 0.0 0.0 26560 8896 pts/2Ss 13:00 0:00 \_ /bin/bash teo 2054 0.0 0.0 37528 3596 pts/2R+ 13:03 0:00 \_ ps ufax ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DKMSKernelVersion: 4.15.0-43-generic Date: Thu Jan 3 13:02:14 2019 InstallationDate: Installed on 2017-04-06 (637 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1810406 Title: Whiptail stucks during kernel upgrade Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: While upgrading kernel, whiptail process stucks and the update process hangs forever nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build root 25534 0.0 0.0 63712 4316 pts/0S+ 13:02 0:00 | \_ sudo dpkg --configure -a root 25535 0.0 0.0 26600 10952 pts/0S+ 13:02 0:00 | \_ dpkg --configure -a root 25570 0.0 0.0 4628 784 pts/0S+ 13:02 0:00 | \_ /bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-43-generic.postinst configure root 25571 0.0 0.0 4520 768 pts/0S+ 13:02 0:00 | \_ run-parts --report --exit-on-error --arg=4.15.0-43-generic /etc/kernel/header_postinst.d root 25572 0.0 0.0 4628 1896 pts/0S+ 13:02 0:00 | \_ /bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-43-generic root 25582 0.0 0.0 15896 6452 pts/0S+ 13:02 0:00 | \_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-43-generic root 26396 0.0 0.0 16016 5724 pts/0S+ 13:02 0:00 | \_ /bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-43-generic root 1718 0.1 0.1 104160 22504 pts/0S+ 13:02 0:00 | \_ /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key root 1750 0.0 0.0 4628 1864 pts/0S+ 13:02 0:00 | \_ /bin/sh /usr/sbin/update-secureboot-policy --enroll-key root 1897 0.0 0.0 24924 4320 pts/0S+ 13:03 0:00 | \_ whiptail --backtitle
Re: [Kernel-packages] [Bug 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible
How can it see the 2.4GHz if it's a 5GHz adapter? Is there some way I can get it to connect to 2.4GHz signals as well? On Wed, Jan 2, 2019, 7:30 PM Robert weaver I can confirm that after upgrading to Kernel 4.18.0-13 , and moving up to > ubuntu 18.10 > BCM4360 802.11ac Wireless Network Adaptor (rev 03) > Still not able to view 5Ghz networks . > Wifi Radar only see's G Networks. > > iwlist freq shows available frequencies > wlp2s032 channels in total; available frequencies : > Channel 01 : 2.412 GHz > Channel 02 : 2.417 GHz > Channel 03 : 2.422 GHz > Channel 04 : 2.427 GHz > Channel 05 : 2.432 GHz > Channel 06 : 2.437 GHz > Channel 07 : 2.442 GHz > Channel 08 : 2.447 GHz > Channel 09 : 2.452 GHz > Channel 10 : 2.457 GHz > Channel 11 : 2.462 GHz > Channel 12 : 2.467 GHz > Channel 13 : 2.472 GHz > Channel 36 : 5.18 GHz > Channel 38 : 5.19 GHz > Channel 40 : 5.2 GHz > Channel 42 : 5.21 GHz > Channel 44 : 5.22 GHz > Channel 46 : 5.23 GHz > Channel 48 : 5.24 GHz > Channel 52 : 5.26 GHz > Channel 54 : 5.27 GHz > Channel 56 : 5.28 GHz > Channel 58 : 5.29 GHz > Channel 60 : 5.3 GHz > Channel 62 : 5.31 GHz > Channel 64 : 5.32 GHz > Channel 100 : 5.5 GHz > Channel 102 : 5.51 GHz > Channel 104 : 5.52 GHz > Channel 106 : 5.53 GHz > Channel 108 : 5.54 GHz > Current Frequency:2.462 GHz (Channel 11) > > I can confirm that when I run iwlist scan i can see skqbox on 5GHz > 8166- Cell 05 - Address: 0C:F9:C0:24:19:3B > 8213-Channel:36 > 8244:Frequency:5.18 GHz (Channel 36) > 8296-Quality=28/70 Signal level=-82 dBm > 8354-Encryption key:on > 8392-ESSID:"SKY2D188" > > So Changing my wifi AP , to use 5Ghz on Channel 36 , im now able to see > the AP > > 10209- Cell 06 - Address: 7C:FF:4D:EE:D3:A8 > 10256-Channel:36 > 10287:Frequency:5.18 GHz (Channel 36) > 10339-Quality=34/70 Signal level=-76 dBm > 10397-Encryption key:on > 10435-ESSID:"FRITZ!Box 3490" > 10478-Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 > Mb/s > 10550- 36 Mb/s; 48 Mb/s; 54 Mb/s > 10606-Mode:Master > 10638-Extra:tsf= > 10685-Extra: Last beacon: 80ms ago > 10734-IE: Unknown: 000E465249545A21426F782033343930 > > But connection Manager still wont use the the above network > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1787742 > > Title: > TP-Link Archer T1U 5GHz WiFi adapter not compatible > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being > recognized by the system settings and WiFi setup wizards, likely due to a > compatibility issue with the Linux kernel. > The device is functional in Windows and recognized by my motherboard, > but unfortunately it is a mere waste of a USB port with Ubuntu and other > Linux distributions. > > - > Terminal output when running 'lsusb' cmd: > jeb@A880G:~$ lsusb > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser > Mouse] > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader > Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish > RF-FLBTAD Bluetooth Adapter > Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface > Subclass) > Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface > Subclass) > Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub > (part of BCM2046 Bluetooth) > Bus 001 Device 009: ID 2357:0105 > Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 > Wireless Adapter > Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > - > > 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
[Kernel-packages] [Bug 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T
** Description changed: - Test failed with "ERROR: rmdir o259-6-0 failed. No such file or - directory" on Trusty. + == Justification == + When doing an incremental send on a Btrfs filesystem, if we delete a directory that has N > 1 hardlinks for the same file and that file has the highest inode number inside the directory contents, an incremental send would send N times rmdir operation against the directory. This made the btrfs receive command fail on the second rmdir instruction, as the target directory didn't exist anymore. + + This issue can be triggered with 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 + test in ubuntu_btrfs_kernel_fixes test suite. - Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 - - fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 - - Btrfs: send, don't send rmdir for same target multiple times - - When doing an incremental send, if we delete a directory that has N > 1 - hardlinks for the same file and that file has the highest inode number - inside the directory contents, an incremental send would send N times an - rmdir operation against the directory. This made the btrfs receive command - fail on the second rmdir instruction, as the target directory didn't exist - anymore. + The test will failed with "ERROR: rmdir o259-6-0 failed. No such file or directory" with Trusty kernel: Performing full device TRIM (1.00GiB) ... Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 WARNING! - Btrfs v3.12 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/loop0 - nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB + nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB Btrfs v3.12 Create a readonly snapshot of '/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in '/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1' At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1 Create a readonly snapshot of '/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in '/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2' At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2 Performing full device TRIM (1.00GiB) ... Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 WARNING! - Btrfs v3.12 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/loop0 - nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB + nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB Btrfs v3.12 At subvol snap1 At snapshot snap2 ERROR: rmdir o259-6-0 failed. No such file or directory incremental receive failed - It seems that commit 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 does not - exist in Trusty tree. + + == Fix == + 29d6d30f5 (Btrfs: send, don't send rmdir for same target multiple times) + This patch needs to be backported to Trusty for a variable difference in the process_recorded_refs function. + + In Trusty tree: + static int process_recorded_refs(struct send_ctx *sctx) + + In the patch: + static int process_recorded_refs(struct send_ctx *sctx, int *pending_move) + + As the new *pending_move is unrelated here, we can just backport the + patch with the same logic in this function. + + A test kernel could be found here: + http://people.canonical.com/~phlin/kernel/lp-1809868-btrfs-2nd-rmdir/ + This test will pass with this kernel. + + + == Regression potential == + Low, + this patch just adds an extra check to make it skip unnecessary rmdir operations. + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-164-generic 3.13.0-164.214 ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39 Uname: Linux 3.13.0-164-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Dec 27 03:14 seq - crw-rw 1 root audio 116, 33 Dec 27 03:14 timer + total 0 + crw-rw 1 root audio 116, 1 Dec 27 03:14 seq + crw-rw 1 root audio 116, 33 Dec 27 03:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 1 transid 4 /dev/loop0 - [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 1 transid 4 /dev/loop0 - [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 1 transid 4 /dev/loop0 - [13958.106099] btrfs: disk space caching is enabled - [13958.107771] btrfs: creating UUID tree + [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 1 transid 4 /dev/loop0 + [13958.102670] btrfs: device fsid
[Kernel-packages] [Bug 1810183] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1810183 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1797753] Re: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)
** Package changed: ubuntu => linux (Ubuntu) -- 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/1797753 Title: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput) Status in linux package in Ubuntu: Confirmed Bug description: I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after installation there is no wifi adapter and also touchpad not working firstly id lspci and in that the output i found of chip : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter secondly id did xinput but there was not device dected as touchpad after that i dual boot centos 7 along side ubunt in that touchpad is working but again wifi adapter not found please solve this issue for both ubuntu (wifi adapter not found and touchpad not detected) and centos (wifi adapter not found) i searched and read regarding this issue and tried all of the but didn't find any solution so at last i have hopes only on u all Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797753/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
** Package changed: ubuntu => linux (Ubuntu) -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Incomplete Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1797753] [NEW] I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)
You have been subscribed to a public bug: I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after installation there is no wifi adapter and also touchpad not working firstly id lspci and in that the output i found of chip : 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter secondly id did xinput but there was not device dected as touchpad after that i dual boot centos 7 along side ubunt in that touchpad is working but again wifi adapter not found please solve this issue for both ubuntu (wifi adapter not found and touchpad not detected) and centos (wifi adapter not found) i searched and read regarding this issue and tried all of the but didn't find any solution so at last i have hopes only on u all Thank you ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput) https://bugs.launchpad.net/bugs/1797753 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
Fix - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/3 -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1810183] [NEW] numpad on touchpad doesn't work in ASUS Zenbook 14
You have been subscribed to a public bug: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- numpad on touchpad doesn't work in ASUS Zenbook 14 https://bugs.launchpad.net/bugs/1810183 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.
i2c-hid: Add a small delay for Synaptics/Elan touchpanel Synaptics/Elan touchpanel sometimes does not work in desktop session although it works in display manager. During user logging, the display manager exits, close the HID device, then the device gets runtime suspended and powered off. The desktop session begins shortly after, opens the HID device, then the device gets runtime resumed and powered on. If the trasition from display manager to desktop sesesion is fast, the touchpanel cannot switch from powered off to powered on in short timeframe. So add a small delay to workaround the issue. ** Patch added: "i2c_hid.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/+attachment/5226618/+files/i2c_hid.patch -- 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/1807377 Title: i2c_hid i2c-ELAN2514:00: failed to change power setting. Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 08:35:57 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807377/+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 1810390] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810390 Title: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The test failed with file attribute not match, for "file", we're expecting: "c--- a/file", but lsattr shows: "c- a/file" for "file2", we're expecting: " a/file2", but lsattr shows: "-- a/file2" for "directory", we're expecting: " a", but lsattr shows: "-- a" This patch could be found in the Bionic tree. https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e So this might be a test case issue. fix 78a017a2c92df9b571db0a55a016280f9019c65e Btrfs: add missing compression property remove in btrfs_ioctl_setflags The behaviour of a 'chattr -c' consists of getting the current flags, clearing the FS_COMPR_FL bit and then sending the result to the set flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags passed to the ioctl. This results in the compression property not being cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL was set in the received flags. Incorrect attributes on file, got: c- a/file Incorrect attributes on file2, got: -- a/file2 Incorrect attributes on directory, got: -- a ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 3 08:42 seq crw-rw 1 root audio 116, 33 Jan 3 08:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 08:47:04 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810390/+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 1810390] Re: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B
The output length for lsattr is different between Xenial and Bionic For T/X, there 16 chars. For B, there are 18 of them. -- 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/1810390 Title: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: The test failed with file attribute not match, for "file", we're expecting: "c--- a/file", but lsattr shows: "c- a/file" for "file2", we're expecting: " a/file2", but lsattr shows: "-- a/file2" for "directory", we're expecting: " a", but lsattr shows: "-- a" This patch could be found in the Bionic tree. https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e So this might be a test case issue. fix 78a017a2c92df9b571db0a55a016280f9019c65e Btrfs: add missing compression property remove in btrfs_ioctl_setflags The behaviour of a 'chattr -c' consists of getting the current flags, clearing the FS_COMPR_FL bit and then sending the result to the set flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags passed to the ioctl. This results in the compression property not being cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL was set in the received flags. Incorrect attributes on file, got: c- a/file Incorrect attributes on file2, got: -- a/file2 Incorrect attributes on directory, got: -- a ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 3 08:42 seq crw-rw 1 root audio 116, 33 Jan 3 08:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 08:47:04 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810390/+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 1810390] [NEW] 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B
Public bug reported: The test failed with file attribute not match, for "file", we're expecting: "c--- a/file", but lsattr shows: "c- a/file" for "file2", we're expecting: " a/file2", but lsattr shows: "-- a/file2" for "directory", we're expecting: " a", but lsattr shows: "-- a" This patch could be found in the Bionic tree. https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e So this might be a test case issue. fix 78a017a2c92df9b571db0a55a016280f9019c65e Btrfs: add missing compression property remove in btrfs_ioctl_setflags The behaviour of a 'chattr -c' consists of getting the current flags, clearing the FS_COMPR_FL bit and then sending the result to the set flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags passed to the ioctl. This results in the compression property not being cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL was set in the received flags. Incorrect attributes on file, got: c- a/file Incorrect attributes on file2, got: -- a/file2 Incorrect attributes on directory, got: -- a ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 3 08:42 seq crw-rw 1 root audio 116, 33 Jan 3 08:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 08:47:04 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests 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/1810390 Title: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: The test failed with file attribute not match, for "file", we're expecting: "c--- a/file", but lsattr shows: "c- a/file" for "file2", we're expecting: " a/file2", but lsattr shows: "-- a/file2" for "directory", we're expecting: " a", but lsattr shows: "-- a" This patch could be found in the Bionic tree. https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e So this might be a test case issue. fix 78a017a2c92df9b571db0a55a016280f9019c65e Btrfs: add missing compression property remove in btrfs_ioctl_setflags The behaviour of a 'chattr -c' consists of getting the current flags, clearing the FS_COMPR_FL bit and then sending the result to the set flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags passed to the ioctl. This results in the compression property not being cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL was set in the received flags. Incorrect attributes on file, got: c- a/file Incorrect attributes on file2, got: -- a/file2 Incorrect
[Kernel-packages] [Bug 1810384] Re: 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B
This issue could be found on a SUT with 1TB disk space. ** Summary changed: - 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on T + 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B ** Description changed: Test failed with disk quota exceeded when trying to create subvolume, - and error traces could be found in the kernel log: + and error traces could be found in the kernel log. + + This patch exists in the Bionic kernel tree: + https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=6113077cd319e747875ec71227d2b5cb54e08c76 Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 fix 6113077cd319e747875ec71227d2b5cb54e08c76 - Btrfs: fix missing qgroup reservation before fallocating + Btrfs: fix missing qgroup reservation before fallocating - Steps to reproduce: - mkfs.btrfs - mount - btrfs quota enable - btrfs sub create /subv - btrfs qgroup limit 10M /subv - fallocate --length 20M /subv/data + Steps to reproduce: + mkfs.btrfs + mount + btrfs quota enable + btrfs sub create /subv + btrfs qgroup limit 10M /subv + fallocate --length 20M /subv/data - For the above example, fallocating will return successfully which - is not expected, we try to fix it by doing qgroup reservation before - fallocating. + For the above example, fallocating will return successfully which + is not expected, we try to fix it by doing qgroup reservation before + fallocating. Create subvolume '/tmp/mnt-6113077cd319e747875ec71227d2b5cb54e08c76/subv' fallocate: fallocate failed: Disk quota exceeded Found kernel issue: [ 829.940603] Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 [ 830.001738] BTRFS: device fsid 134f6701-7984-42bc-affc-e423f4e6c750 devid 1 transid 5 /dev/loop0 [ 830.005573] BTRFS info (device loop0): disk space caching is enabled [ 830.005574] BTRFS info (device loop0): has skinny extents [ 830.005575] BTRFS info (device loop0): flagging fs with big metadata feature [ 830.006375] BTRFS info (device loop0): creating UUID tree [ 830.038054] BTRFS info (device loop0): qgroup scan completed (inconsistency flag cleared) [ 830.042133] WARNING: CPU: 1 PID: 15933 at /build/linux-oem-RkS9Vy/linux-oem-4.15.0/fs/btrfs/extent-tree.c:4433 btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042133] Modules linked in: btrfs zstd_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ppdev input_leds intel_cstate joydev intel_rapl_perf intel_pch_thermal parport_pc ipmi_si parport lpc_ich mac_hid ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 mgag200 crct10dif_pclmul crc32_pclmul ttm ghash_clmulni_intel pcbc igb drm_kms_helper hid_generic aesni_intel dca syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd ptp ahci usbhid glue_helper cryptd drm libahci hid pps_core video [last unloaded: zstd_compress] [ 830.042166] CPU: 1 PID: 15933 Comm: fallocate Not tainted 4.15.0-1030-oem #35-Ubuntu [ 830.042167] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [ 830.042176] RIP: 0010:btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042177] RSP: 0018:aa474a647d88 EFLAGS: 00010287 [ 830.042178] RAX: RBX: 0140 RCX: 0140 [ 830.042178] RDX: 0001 RSI: RDI: 8febd2814200 [ 830.042179] RBP: aa474a647db0 R08: 00027fc0 R09: c0877688 [ 830.042180] R10: 8feb877f R11: 0001 R12: 8febd2814200 [ 830.042180] R13: 8feb877f R14: 8feb1ff25f40 R15: 0140 [ 830.042181] FS: 7f7b7a10c540() GS:8febe084() knlGS: [ 830.042182] CS: 0010 DS: ES: CR0: 80050033 [ 830.042183] CR2: 7f7b79f4baa0 CR3: 00045a996004 CR4: 003606e0 [ 830.042184] DR0: DR1: DR2: [ 830.042184] DR3: DR6: fffe0ff0 DR7: 0400 [ 830.042185] Call Trace: [ 830.042194] btrfs_free_reserved_data_space+0x50/0x70 [btrfs] [ 830.042205] btrfs_fallocate+0x3f8/0x750 [btrfs] [ 830.042208] vfs_fallocate+0x144/0x260 [ 830.042209] SyS_fallocate+0x48/0x80 [ 830.042211] do_syscall_64+0x73/0x130 [ 830.042214] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 830.042215] RIP: 0033:0x7f7b79c13857 [ 830.042215] RSP: 002b:7ffc1ad01498 EFLAGS: 0246 ORIG_RAX: 011d [
[Kernel-packages] [Bug 1810383] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810383 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: System report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tzdata: Install linux-headers-4.4.0-96: Configure tzdata: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnyreb 2230 F pulseaudio Date: Thu Jan 3 07:29:24 2019 DpkgHistoryLog: Start-Date: 2019-01-03 07:29:16 Commandline: /usr/bin/unattended-upgrade Upgrade: tzdata:i386 (2018g-0ubuntu0.16.04, 2018i-0ubuntu0.16.04) DpkgTerminalLog: Preparing to unpack .../tzdata_2018i-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 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.20 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810383/+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 1810384] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810384 Title: 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with disk quota exceeded when trying to create subvolume, and error traces could be found in the kernel log. This patch exists in the Bionic kernel tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=6113077cd319e747875ec71227d2b5cb54e08c76 Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 fix 6113077cd319e747875ec71227d2b5cb54e08c76 Btrfs: fix missing qgroup reservation before fallocating Steps to reproduce: mkfs.btrfs mount btrfs quota enable btrfs sub create /subv btrfs qgroup limit 10M /subv fallocate --length 20M /subv/data For the above example, fallocating will return successfully which is not expected, we try to fix it by doing qgroup reservation before fallocating. Create subvolume '/tmp/mnt-6113077cd319e747875ec71227d2b5cb54e08c76/subv' fallocate: fallocate failed: Disk quota exceeded Found kernel issue: [ 829.940603] Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 [ 830.001738] BTRFS: device fsid 134f6701-7984-42bc-affc-e423f4e6c750 devid 1 transid 5 /dev/loop0 [ 830.005573] BTRFS info (device loop0): disk space caching is enabled [ 830.005574] BTRFS info (device loop0): has skinny extents [ 830.005575] BTRFS info (device loop0): flagging fs with big metadata feature [ 830.006375] BTRFS info (device loop0): creating UUID tree [ 830.038054] BTRFS info (device loop0): qgroup scan completed (inconsistency flag cleared) [ 830.042133] WARNING: CPU: 1 PID: 15933 at /build/linux-oem-RkS9Vy/linux-oem-4.15.0/fs/btrfs/extent-tree.c:4433 btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042133] Modules linked in: btrfs zstd_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ppdev input_leds intel_cstate joydev intel_rapl_perf intel_pch_thermal parport_pc ipmi_si parport lpc_ich mac_hid ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 mgag200 crct10dif_pclmul crc32_pclmul ttm ghash_clmulni_intel pcbc igb drm_kms_helper hid_generic aesni_intel dca syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd ptp ahci usbhid glue_helper cryptd drm libahci hid pps_core video [last unloaded: zstd_compress] [ 830.042166] CPU: 1 PID: 15933 Comm: fallocate Not tainted 4.15.0-1030-oem #35-Ubuntu [ 830.042167] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [ 830.042176] RIP: 0010:btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042177] RSP: 0018:aa474a647d88 EFLAGS: 00010287 [ 830.042178] RAX: RBX: 0140 RCX: 0140 [ 830.042178] RDX: 0001 RSI: RDI: 8febd2814200 [ 830.042179] RBP: aa474a647db0 R08: 00027fc0 R09: c0877688 [ 830.042180] R10: 8feb877f R11: 0001 R12: 8febd2814200 [ 830.042180] R13: 8feb877f R14: 8feb1ff25f40 R15: 0140 [ 830.042181] FS: 7f7b7a10c540() GS:8febe084() knlGS: [ 830.042182] CS: 0010 DS: ES: CR0: 80050033 [ 830.042183] CR2: 7f7b79f4baa0 CR3: 00045a996004 CR4: 003606e0 [ 830.042184] DR0: DR1: DR2: [ 830.042184] DR3: DR6: fffe0ff0 DR7: 0400 [ 830.042185] Call Trace: [ 830.042194] btrfs_free_reserved_data_space+0x50/0x70 [btrfs] [ 830.042205] btrfs_fallocate+0x3f8/0x750 [btrfs] [ 830.042208] vfs_fallocate+0x144/0x260 [ 830.042209] SyS_fallocate+0x48/0x80 [ 830.042211] do_syscall_64+0x73/0x130 [ 830.042214] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 830.042215] RIP: 0033:0x7f7b79c13857 [ 830.042215] RSP: 002b:7ffc1ad01498 EFLAGS: 0246 ORIG_RAX: 011d [ 830.042216] RAX: ffda RBX: RCX: 7f7b79c13857 [ 830.042217] RDX: RSI: RDI: 0008 [ 830.042217] RBP: 0004 R08: R09: [ 830.042218] R10: 0140 R11: 0246 R12:
[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes
It happened to me, is not usual, in fact was muy first time, in my case it hanged forever, i was making a heavy use with nfs, ocal and lot of paralel copy writes and it stucked. No problems with the disks, just the process using 99% of cpu. -- 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/1654517 Title: ZFS I/O hangs for minutes Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Won't Fix Bug description: I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel threads are created, `dmesg` contains [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 seconds. [ 9184.451610] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471 2 0x [ 9184.451616] a240ab3a7aa8 00ffbb6ade1f a24095148000 a240e5ca5580 [ 9184.451618] 0046 a240ab3a8000 a240ff359200 7fff [ 9184.451620] a23d36cf9050 0001 a240ab3a7ac0 bbe96b15 [ 9184.451621] Call Trace: [ 9184.451627] [] schedule+0x35/0x80 [ 9184.451628] [] schedule_timeout+0x22a/0x3f0 [ 9184.451631] [] ? __switch_to+0x2ce/0x6c0 [ 9184.451633] [] ? pick_next_task_fair+0x48c/0x4c0 [ 9184.451635] [] ? ktime_get+0x41/0xb0 [ 9184.451636] [] io_schedule_timeout+0xa4/0x110 [ 9184.451644] [] cv_wait_common+0xb2/0x130 [spl] [ 9184.451646] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.451650] [] __cv_wait_io+0x18/0x20 [spl] [ 9184.451689] [] zio_wait+0xfd/0x1d0 [zfs] [ 9184.451716] [] dsl_pool_sync+0xb8/0x480 [zfs] [ 9184.451745] [] spa_sync+0x37f/0xb30 [zfs] [ 9184.451747] [] ? default_wake_function+0x12/0x20 [ 9184.451779] [] txg_sync_thread+0x3a5/0x600 [zfs] [ 9184.451807] [] ? txg_delay+0x160/0x160 [zfs] [ 9184.451811] [] thread_generic_wrapper+0x71/0x80 [spl] [ 9184.451815] [] ? __thread_exit+0x20/0x20 [spl] [ 9184.451817] [] kthread+0xd8/0xf0 [ 9184.451819] [] ret_from_fork+0x1f/0x40 [ 9184.451821] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 seconds. [ 9184.451851] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.451853] mozStorage #2 D a23fe8a5bd38 0 21607 19750 0x0004 [ 9184.451855] a23fe8a5bd38 00ffa240ee8feb40 a240ecf72ac0 a2403803b900 [ 9184.451857] bc2c02f7 a23fe8a5c000 a240aa940828 a240aa940800 [ 9184.451858] a240aa940980 a23fe8a5bd50 bbe96b15 [ 9184.451860] Call Trace: [ 9184.451861] [] schedule+0x35/0x80 [ 9184.451866] [] cv_wait_common+0x110/0x130 [spl] [ 9184.451868] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.451872] [] __cv_wait+0x15/0x20 [spl] [ 9184.451904] [] zil_commit.part.11+0x79/0x7a0 [zfs] [ 9184.451909] [] ? tsd_hash_search.isra.0+0x46/0xa0 [spl] [ 9184.451913] [] ? tsd_set+0x2b4/0x500 [spl] [ 9184.451914] [] ? mutex_lock+0x12/0x30 [ 9184.451945] [] zil_commit+0x17/0x20 [zfs] [ 9184.451975] [] zfs_fsync+0x7a/0xf0 [zfs] [ 9184.452005] [] zpl_fsync+0x68/0xa0 [zfs] [ 9184.452008] [] vfs_fsync_range+0x4b/0xb0 [ 9184.452010] [] do_fsync+0x3d/0x70 [ 9184.452011] [] SyS_fsync+0x10/0x20 [ 9184.452013] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 9184.452023] INFO: task bitcoin-msghand:663 blocked for more than 120 seconds. [ 9184.452024] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.452025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.452026] bitcoin-msghand D a23eeb23bd38 0 663 26994 0x [ 9184.452028] a23eeb23bd38 00ffa23eab434000 a240ecf7 a24095148000 [ 9184.452030] a23eeb23bd20 a23eeb23c000 a240aa940828 a240aa940800 [ 9184.452031] a240aa940980 a23eeb23bd50 bbe96b15 [ 9184.452033] Call Trace: [ 9184.452034] [] schedule+0x35/0x80 [ 9184.452039] [] cv_wait_common+0x110/0x130 [spl] [ 9184.452041] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.452044] [] __cv_wait+0x15/0x20 [spl] [ 9184.452074] [] zil_commit.part.11+0x79/0x7a0 [zfs] [ 9184.452079] [] ? tsd_hash_search.isra.0+0x46/0xa0 [spl] [ 9184.452083] [] ? tsd_set+0x2b4/0x500
[Kernel-packages] [Bug 1810383] Re: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
** Tags removed: need-duplicate-check -- 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/1810383 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: System report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tzdata: Install linux-headers-4.4.0-96: Configure tzdata: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnyreb 2230 F pulseaudio Date: Thu Jan 3 07:29:24 2019 DpkgHistoryLog: Start-Date: 2019-01-03 07:29:16 Commandline: /usr/bin/unattended-upgrade Upgrade: tzdata:i386 (2018g-0ubuntu0.16.04, 2018i-0ubuntu0.16.04) DpkgTerminalLog: Preparing to unpack .../tzdata_2018i-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 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.20 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810383/+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 1810383] [NEW] package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
Public bug reported: System report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tzdata: Install linux-headers-4.4.0-96: Configure tzdata: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnyreb 2230 F pulseaudio Date: Thu Jan 3 07:29:24 2019 DpkgHistoryLog: Start-Date: 2019-01-03 07:29:16 Commandline: /usr/bin/unattended-upgrade Upgrade: tzdata:i386 (2018g-0ubuntu0.16.04, 2018i-0ubuntu0.16.04) DpkgTerminalLog: Preparing to unpack .../tzdata_2018i-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216 InstallationDate: Installed on 2016-09-06 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 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.20 SourcePackage: linux Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1221 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 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/1810383 Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Confirmed Bug description: System report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tzdata: Install linux-headers-4.4.0-96: Configure tzdata: Configure NULL: ConfigurePending Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnnyreb 2230 F pulseaudio Date: Thu Jan 3 07:29:24 2019 DpkgHistoryLog: Start-Date: 2019-01-03 07:29:16 Commandline: /usr/bin/unattended-upgrade Upgrade: tzdata:i386 (2018g-0ubuntu0.16.04, 2018i-0ubuntu0.16.04) DpkgTerminalLog: Preparing to unpack .../tzdata_2018i-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:linux-headers-4.4.0-96:4.4.0-96.119 Unpacking tzdata (2018i-0ubuntu0.16.04) over (2018g-0ubuntu0.16.04) ... dpkg: error processing package linux-headers-4.4.0-96 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice:
[Kernel-packages] [Bug 1810384] [NEW] 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on T
Public bug reported: Test failed with disk quota exceeded when trying to create subvolume, and error traces could be found in the kernel log: Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 fix 6113077cd319e747875ec71227d2b5cb54e08c76 Btrfs: fix missing qgroup reservation before fallocating Steps to reproduce: mkfs.btrfs mount btrfs quota enable btrfs sub create /subv btrfs qgroup limit 10M /subv fallocate --length 20M /subv/data For the above example, fallocating will return successfully which is not expected, we try to fix it by doing qgroup reservation before fallocating. Create subvolume '/tmp/mnt-6113077cd319e747875ec71227d2b5cb54e08c76/subv' fallocate: fallocate failed: Disk quota exceeded Found kernel issue: [ 829.940603] Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 [ 830.001738] BTRFS: device fsid 134f6701-7984-42bc-affc-e423f4e6c750 devid 1 transid 5 /dev/loop0 [ 830.005573] BTRFS info (device loop0): disk space caching is enabled [ 830.005574] BTRFS info (device loop0): has skinny extents [ 830.005575] BTRFS info (device loop0): flagging fs with big metadata feature [ 830.006375] BTRFS info (device loop0): creating UUID tree [ 830.038054] BTRFS info (device loop0): qgroup scan completed (inconsistency flag cleared) [ 830.042133] WARNING: CPU: 1 PID: 15933 at /build/linux-oem-RkS9Vy/linux-oem-4.15.0/fs/btrfs/extent-tree.c:4433 btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042133] Modules linked in: btrfs zstd_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ppdev input_leds intel_cstate joydev intel_rapl_perf intel_pch_thermal parport_pc ipmi_si parport lpc_ich mac_hid ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 mgag200 crct10dif_pclmul crc32_pclmul ttm ghash_clmulni_intel pcbc igb drm_kms_helper hid_generic aesni_intel dca syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd ptp ahci usbhid glue_helper cryptd drm libahci hid pps_core video [last unloaded: zstd_compress] [ 830.042166] CPU: 1 PID: 15933 Comm: fallocate Not tainted 4.15.0-1030-oem #35-Ubuntu [ 830.042167] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [ 830.042176] RIP: 0010:btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042177] RSP: 0018:aa474a647d88 EFLAGS: 00010287 [ 830.042178] RAX: RBX: 0140 RCX: 0140 [ 830.042178] RDX: 0001 RSI: RDI: 8febd2814200 [ 830.042179] RBP: aa474a647db0 R08: 00027fc0 R09: c0877688 [ 830.042180] R10: 8feb877f R11: 0001 R12: 8febd2814200 [ 830.042180] R13: 8feb877f R14: 8feb1ff25f40 R15: 0140 [ 830.042181] FS: 7f7b7a10c540() GS:8febe084() knlGS: [ 830.042182] CS: 0010 DS: ES: CR0: 80050033 [ 830.042183] CR2: 7f7b79f4baa0 CR3: 00045a996004 CR4: 003606e0 [ 830.042184] DR0: DR1: DR2: [ 830.042184] DR3: DR6: fffe0ff0 DR7: 0400 [ 830.042185] Call Trace: [ 830.042194] btrfs_free_reserved_data_space+0x50/0x70 [btrfs] [ 830.042205] btrfs_fallocate+0x3f8/0x750 [btrfs] [ 830.042208] vfs_fallocate+0x144/0x260 [ 830.042209] SyS_fallocate+0x48/0x80 [ 830.042211] do_syscall_64+0x73/0x130 [ 830.042214] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 830.042215] RIP: 0033:0x7f7b79c13857 [ 830.042215] RSP: 002b:7ffc1ad01498 EFLAGS: 0246 ORIG_RAX: 011d [ 830.042216] RAX: ffda RBX: RCX: 7f7b79c13857 [ 830.042217] RDX: RSI: RDI: 0008 [ 830.042217] RBP: 0004 R08: R09: [ 830.042218] R10: 0140 R11: 0246 R12: 7ffc1ad016c8 [ 830.042219] R13: R14: R15: 0140 [ 830.042219] Code: c7 49 8b 7f 08 49 83 c7 18 45 31 c9 49 89 d8 4c 89 f1 48 c7 c2 d5 5a 8e c0 4c 89 ee e8 6f 88 7c fc 4d 8b 17 4d 85 d2 75 d8 eb 97 <0f> 0b 49 c7 44 24 28 00 00 00 00 eb 85 0f 1f 84 00 00 00 00 00 [ 830.042240] ---[ end trace 4a601597480dd14c ]--- [ 830.208479] Test 6113077cd319e747875ec71227d2b5cb54e08c76 returned 0 FAIL: 6113077cd319e747875ec71227d2b5cb54e08c76 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0
[Kernel-packages] [Bug 1810377] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810377 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1810376] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1810376 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in linux package in Ubuntu: Confirmed Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810376/+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 1810377] [NEW] 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B
Public bug reported: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests 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/1810377 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in
[Kernel-packages] [Bug 1809219] Re: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported
https://lists.ubuntu.com/archives/kernel-team/2019-January/097456.html ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1809219 Title: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Killer Wireless-1550 is not supported by Bionic kernel. [Fix] This card can be supported by adding its structs and IDs into table by below commit. 0a5257bc6d89 iwlwifi: add more card IDs for 9000 series [Test] Verified wifi works after applied the commit. [Regression Potential] Low. It adds its own structs and IDs to support killer cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1809219/+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 1810376] [NEW] 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B
Public bug reported: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix 5fbc7c59fd22c5a6531b40b0759624b680a95e52 Btrfs: fix unfinished readahead thread for raid5/6 degraded mounting Steps to reproduce: # mkfs.btrfs -f /dev/sd[b-f] -m raid5 -d raid5 # mkfs.ext4 /dev/sdc --->corrupt one of btrfs device # mount /dev/sdb /mnt -o degraded # btrfs scrub start -BRd /mnt This is because readahead would skip missing device, this is not true for RAID5/6, because REQ_GET_READ_MIRRORS return 1 for RAID5/6 block mapping. If expected data locates in missing device, readahead thread would not call __readahead_hook() which makes event @rc->elems=0 wait forever. Fix this problem by checking return value of btrfs_map_block(),we can only skip missing device safely if there are several mirrors. mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: 4096/524288* *done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: c4b9a22f-cacb-44d6-80b9-cca217a61f5b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/16* *done Writing inode tables: 0/16* *done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: 0/16* *done mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. ERROR: not a btrfs filesystem: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 btrfs scrub start on /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52 failed umount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: not mounted. FAIL: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 (ret=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 02:11 seq crw-rw 1 root audio 116, 33 Dec 31 02:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 3 07:37:01 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic uec-images -- 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/1810376 Title: 5fbc7c59fd22c5a6531b40b0759624b680a95e52 in btrfs_kernel_fixes failed on B Status in linux package in Ubuntu: Confirmed Bug description: Test failed with mount operation: mount: /tmp/mnt-5fbc7c59fd22c5a6531b40b0759624b680a95e52: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. This patch could be found in Bionic tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=5fbc7c59fd22c5a6531b40b0759624b680a95e52 Invoking test 5fbc7c59fd22c5a6531b40b0759624b680a95e52 fix
