[Kernel-packages] [Bug 1768429] Re: Xenial update to 4.4.129 stable release
Skipped the following commit (commit to be reverted is not applied): * Revert "perf tests: Decompress kernel module before objdump" -- 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/1768429 Title: Xenial update to 4.4.129 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.129 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.129 stable release shall be applied: * Linux 4.4.129 * writeback: safer lock nesting * fanotify: fix logic of events on child * ext4: bugfix for mmaped pages in mpage_release_unused_pages() * mm/filemap.c: fix NULL pointer in page_cache_tree_insert() * mm: allow GFP_{FS,IO} for page_cache_read page cache allocation * autofs: mount point create should honour passed in mode * Don't leak MNT_INTERNAL away from internal mounts * rpc_pipefs: fix double-dput() * hypfs_kill_super(): deal with failed allocations * jffs2_kill_sb(): deal with failed allocations * powerpc/lib: Fix off-by-one in alternate feature patching * powerpc/eeh: Fix enabling bridge MMIO windows * MIPS: memset.S: Fix clobber of v1 in last_fixup * MIPS: memset.S: Fix return of __clear_user from Lpartial_fixup * MIPS: memset.S: EVA & fault support for small_memset * MIPS: uaccess: Add micromips clobbers to bzero invocation * HID: hidraw: Fix crash on HIDIOCGFEATURE with a destroyed device * ALSA: hda - New VIA controller suppor no-snoop path * ALSA: rawmidi: Fix missing input substream checks in compat ioctls * ALSA: line6: Use correct endpoint type for midi output * ext4: fix deadlock between inline_data and ext4_expand_extra_isize_ea() * ext4: fix crashes in dioread_nolock mode * drm/radeon: Fix PCIe lane width calculation * ext4: don't allow r/w mounts if metadata blocks overlap the superblock * vfio/pci: Virtualize Maximum Read Request Size * vfio/pci: Virtualize Maximum Payload Size * vfio-pci: Virtualize PCIe & AF FLR * ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation * ALSA: pcm: Fix mutex unbalance in OSS emulation ioctls * ALSA: pcm: Return -EBUSY for OSS ioctls changing busy streams * ALSA: pcm: Avoid potential races between OSS ioctls and read/write * ALSA: pcm: Use ERESTARTSYS instead of EINTR in OSS emulation * ALSA: oss: consolidate kmalloc/memset 0 call to kzalloc * watchdog: f71808e_wdt: Fix WD_EN register read * thermal: imx: Fix race condition in imx_thermal_probe() * clk: bcm2835: De-assert/assert PLL reset signal when appropriate * clk: mvebu: armada-38x: add support for missing clocks * clk: mvebu: armada-38x: add support for 1866MHz variants * mmc: jz4740: Fix race condition in IRQ mask update * iommu/vt-d: Fix a potential memory leak * um: Use POSIX ucontext_t instead of struct ucontext * dmaengine: at_xdmac: fix rare residue corruption * IB/srp: Fix completion vector assignment algorithm * IB/srp: Fix srp_abort() * ALSA: pcm: Fix UAF at PCM release via PCM timer access * RDMA/ucma: Don't allow setting RDMA_OPTION_IB_PATH without an RDMA device * ext4: fail ext4_iget for root directory if unallocated * ext4: don't update checksum of new initialized bitmaps * jbd2: if the journal is aborted then don't allow update of the log tail * random: use a tighter cap in credit_entropy_bits_safe() * thunderbolt: Resume control channel after hibernation image is created * ASoC: ssm2602: Replace reg_default_raw with reg_default * HID: core: Fix size as type u32 * HID: Fix hid_report_len usage * powerpc/powernv: Fix OPAL NVRAM driver OPAL_BUSY loops * powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops * powerpc/64: Fix smp_wmb barrier definition use use lwsync consistently * powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() * HID: i2c-hid: fix size check and type usage * usb: dwc3: pci: Properly cleanup resource * USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw * ACPI / hotplug / PCI: Check presence of slot itself in get_slot_status() * ACPI / video: Add quirk to force acpi-video backlight on Samsung 670Z5E * regmap: Fix reversed bounds check in regmap_raw_write() * xen-netfront:
[Kernel-packages] [Bug 1768435] [NEW] aio-dio-extend-stat test in aio_dio_bugs failed on s390x
Public bug reported: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file' write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file Exit status: 1 Duration: 0.10453414917 stdout: write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:24:25 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768435 Title: aio-dio-extend-stat test in aio_dio_bugs failed on s390x Status in linux package in Ubuntu: New Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading sta
[Kernel-packages] [Bug 1768429] Re: Xenial update to 4.4.129 stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.129 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.129 stable release shall be applied: - +* Linux 4.4.129 +* writeback: safer lock nesting +* fanotify: fix logic of events on child +* ext4: bugfix for mmaped pages in mpage_release_unused_pages() +* mm/filemap.c: fix NULL pointer in page_cache_tree_insert() +* mm: allow GFP_{FS,IO} for page_cache_read page cache allocation +* autofs: mount point create should honour passed in mode +* Don't leak MNT_INTERNAL away from internal mounts +* rpc_pipefs: fix double-dput() +* hypfs_kill_super(): deal with failed allocations +* jffs2_kill_sb(): deal with failed allocations +* powerpc/lib: Fix off-by-one in alternate feature patching +* powerpc/eeh: Fix enabling bridge MMIO windows +* MIPS: memset.S: Fix clobber of v1 in last_fixup +* MIPS: memset.S: Fix return of __clear_user from Lpartial_fixup +* MIPS: memset.S: EVA & fault support for small_memset +* MIPS: uaccess: Add micromips clobbers to bzero invocation +* HID: hidraw: Fix crash on HIDIOCGFEATURE with a destroyed device +* ALSA: hda - New VIA controller suppor no-snoop path +* ALSA: rawmidi: Fix missing input substream checks in compat ioctls +* ALSA: line6: Use correct endpoint type for midi output +* ext4: fix deadlock between inline_data and ext4_expand_extra_isize_ea() +* ext4: fix crashes in dioread_nolock mode +* drm/radeon: Fix PCIe lane width calculation +* ext4: don't allow r/w mounts if metadata blocks overlap the superblock +* vfio/pci: Virtualize Maximum Read Request Size +* vfio/pci: Virtualize Maximum Payload Size +* vfio-pci: Virtualize PCIe & AF FLR +* ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation +* ALSA: pcm: Fix mutex unbalance in OSS emulation ioctls +* ALSA: pcm: Return -EBUSY for OSS ioctls changing busy streams +* ALSA: pcm: Avoid potential races between OSS ioctls and read/write +* ALSA: pcm: Use ERESTARTSYS instead of EINTR in OSS emulation +* ALSA: oss: consolidate kmalloc/memset 0 call to kzalloc +* watchdog: f71808e_wdt: Fix WD_EN register read +* thermal: imx: Fix race condition in imx_thermal_probe() +* clk: bcm2835: De-assert/assert PLL reset signal when appropriate +* clk: mvebu: armada-38x: add support for missing clocks +* clk: mvebu: armada-38x: add support for 1866MHz variants +* mmc: jz4740: Fix race condition in IRQ mask update +* iommu/vt-d: Fix a potential memory leak +* um: Use POSIX ucontext_t instead of struct ucontext +* dmaengine: at_xdmac: fix rare residue corruption +* IB/srp: Fix completion vector assignment algorithm +* IB/srp: Fix srp_abort() +* ALSA: pcm: Fix UAF at PCM release via PCM timer access +* RDMA/ucma: Don't allow setting RDMA_OPTION_IB_PATH without an RDMA device +* ext4: fail ext4_iget for root directory if unallocated +* ext4: don't update checksum of new initialized bitmaps +* jbd2: if the journal is aborted then don't allow update of the log tail +* random: use a tighter cap in credit_entropy_bits_safe() +* thunderbolt: Resume control channel after hibernation image is created +* ASoC: ssm2602: Replace reg_default_raw with reg_default +* HID: core: Fix size as type u32 +* HID: Fix hid_report_len usage +* powerpc/powernv: Fix OPAL NVRAM driver OPAL_BUSY loops +* powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops +* powerpc/64: Fix smp_wmb barrier definition use use lwsync consistently +* powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() +* HID: i2c-hid: fix size check and type usage +* usb: dwc3: pci: Properly cleanup resource +* USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw +* ACPI / hotplug / PCI: Check presence of slot itself in get_slot_status() +* ACPI / video: Add quirk to force acpi-video backlight on Samsung 670Z5E +* regmap: Fix reversed bounds check in regmap_raw_write() +* xen-netfront: Fix hang on device removal +* ARM: dts: at91: sama5d4: fix pinctrl compatible string +* ARM: dts: at91: at91sam9g25: fix mux-mask pinctrl property +* usb: musb: gadget: misplaced out of bounds check +* mm, slab: reschedule cache_reap() on the same CPU +* ipc/shm: fix use-after-free of shm file via remap_file_pages() +* resource: fix integer overflow a
[Kernel-packages] [Bug 1768430] [NEW] aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
Public bug reported: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in linux package in Ubuntu: Incomplete Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-
[Kernel-packages] [Bug 1768430] 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 1768430 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/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in linux package in Ubuntu: Incomplete Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1768430] Re: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
** Description changed: It can be reproduced on zVM, zKVM and Ubuntu on LPAR + + This should not be considered as a regression, the test suite stopped on + the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest - Running 'apt-get install --yes --force-yes build-essential gcc' - Reading package lists... - Building dependency tree... - Reading state information... - build-essential is already the newest version (12.1ubuntu2). - gcc is already the newest version (4:5.3.1-1ubuntu1). - The following packages were automatically installed and are no longer required: - linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic - linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic - Use 'sudo apt autoremove' to remove them. - 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. - Running 'which gcc' - /usr/bin/gcc - Dependency libaio successfully built - Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' - buffered read returned -1, should be 300 - Exception escaping from test: + Running 'apt-get install --yes --force-yes build-essential gcc' + Reading package lists... + Building dependency tree... + Reading state information... + build-essential is already the newest version (12.1ubuntu2). + gcc is already the newest version (4:5.3.1-1ubuntu1). + The following packages were automatically installed and are no longer required: + linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic + linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic + Use 'sudo apt autoremove' to remove them. + 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. + Running 'which gcc' + /usr/bin/gcc + Dependency libaio successfully built + Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' + buffered read returned -1, should be 300 + Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: - + Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: - linux-restricted-modules-4.4.0-123-generic N/A - linux-backports-modules-4.4.0-123-generic N/A - linux-firmware
Re: [Kernel-packages] [Bug 1761751] Re: [REGRESSION] drm/amd/dc: Add dc display driver (v2)
I don't think it is the same bug. I have a card with HDMI and DVI connectors (XFX RX 460). The HDMI connector is connected to the monitor, the DVI connector is unplugged. // David On 2018-04-30 17:40, Harry Wentland wrote: > Replied on the ticket. > > If this is about non-functioning LVDS or VGA I'm aware of it and trying > to find time to find a good solution. > > Harry > > On 2018-04-30 11:14 AM, Joseph Salisbury wrote: >> Hi Harry, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found the following commit introduced the bug: >> >> >> commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c >> Author: Harry Wentland >> Date: Tue Sep 12 15:58:20 2017 -0400 >> >> drm/amd/dc: Add dc display driver (v2) >> >> >> The regression was introduced as of v4.15-rc1 and still exists in >> current mainline. The commit does not need to be reverted to resolve >> the bug. Disabling the CONFIG_DRM_AMD_DC_PRE_VEGA option makes the bug >> go away. >> >> I was hoping to get your feedback, since you are the patch author. Do >> you think gathering any additional data will help diagnose this issue? >> >> >> Thanks, >> >> Joe >> >> >> [0] http://pad.lv/1761751 >> -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1768429] [NEW] Xenial update to 4.4.129 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.129 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.129 stable release shall be applied: * Linux 4.4.129 * writeback: safer lock nesting * fanotify: fix logic of events on child * ext4: bugfix for mmaped pages in mpage_release_unused_pages() * mm/filemap.c: fix NULL pointer in page_cache_tree_insert() * mm: allow GFP_{FS,IO} for page_cache_read page cache allocation * autofs: mount point create should honour passed in mode * Don't leak MNT_INTERNAL away from internal mounts * rpc_pipefs: fix double-dput() * hypfs_kill_super(): deal with failed allocations * jffs2_kill_sb(): deal with failed allocations * powerpc/lib: Fix off-by-one in alternate feature patching * powerpc/eeh: Fix enabling bridge MMIO windows * MIPS: memset.S: Fix clobber of v1 in last_fixup * MIPS: memset.S: Fix return of __clear_user from Lpartial_fixup * MIPS: memset.S: EVA & fault support for small_memset * MIPS: uaccess: Add micromips clobbers to bzero invocation * HID: hidraw: Fix crash on HIDIOCGFEATURE with a destroyed device * ALSA: hda - New VIA controller suppor no-snoop path * ALSA: rawmidi: Fix missing input substream checks in compat ioctls * ALSA: line6: Use correct endpoint type for midi output * ext4: fix deadlock between inline_data and ext4_expand_extra_isize_ea() * ext4: fix crashes in dioread_nolock mode * drm/radeon: Fix PCIe lane width calculation * ext4: don't allow r/w mounts if metadata blocks overlap the superblock * vfio/pci: Virtualize Maximum Read Request Size * vfio/pci: Virtualize Maximum Payload Size * vfio-pci: Virtualize PCIe & AF FLR * ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation * ALSA: pcm: Fix mutex unbalance in OSS emulation ioctls * ALSA: pcm: Return -EBUSY for OSS ioctls changing busy streams * ALSA: pcm: Avoid potential races between OSS ioctls and read/write * ALSA: pcm: Use ERESTARTSYS instead of EINTR in OSS emulation * ALSA: oss: consolidate kmalloc/memset 0 call to kzalloc * watchdog: f71808e_wdt: Fix WD_EN register read * thermal: imx: Fix race condition in imx_thermal_probe() * clk: bcm2835: De-assert/assert PLL reset signal when appropriate * clk: mvebu: armada-38x: add support for missing clocks * clk: mvebu: armada-38x: add support for 1866MHz variants * mmc: jz4740: Fix race condition in IRQ mask update * iommu/vt-d: Fix a potential memory leak * um: Use POSIX ucontext_t instead of struct ucontext * dmaengine: at_xdmac: fix rare residue corruption * IB/srp: Fix completion vector assignment algorithm * IB/srp: Fix srp_abort() * ALSA: pcm: Fix UAF at PCM release via PCM timer access * RDMA/ucma: Don't allow setting RDMA_OPTION_IB_PATH without an RDMA device * ext4: fail ext4_iget for root directory if unallocated * ext4: don't update checksum of new initialized bitmaps * jbd2: if the journal is aborted then don't allow update of the log tail * random: use a tighter cap in credit_entropy_bits_safe() * thunderbolt: Resume control channel after hibernation image is created * ASoC: ssm2602: Replace reg_default_raw with reg_default * HID: core: Fix size as type u32 * HID: Fix hid_report_len usage * powerpc/powernv: Fix OPAL NVRAM driver OPAL_BUSY loops * powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops * powerpc/64: Fix smp_wmb barrier definition use use lwsync consistently * powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write() * HID: i2c-hid: fix size check and type usage * usb: dwc3: pci: Properly cleanup resource * USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw * ACPI / hotplug / PCI: Check presence of slot itself in get_slot_status() * ACPI / video: Add quirk to force acpi-video backlight on Samsung 670Z5E * regmap: Fix reversed bounds check in regmap_raw_write() * xen-netfront: Fix hang on device removal * ARM: dts: at91: sama5d4: fix pinctrl compatible string * ARM: dts: at91: at91sam9g25: fix mux-mask pinctrl property * usb: musb: gadget: misplaced out of bounds check * mm, slab: reschedule cache_reap() on the same CPU * ipc/shm: fix use-after-free of shm file via remap_file_pages() * resource: fix integer overflow at reallocation * fs/reiserfs/journal.c: add missing resierfs_warning() arg * ubi: Reject MLC NAND * ubi: Fix error for write access * ubi: fastmap: Don't flush fastmap work o
[Kernel-packages] [Bug 1751813] Comment bridged from LTC Bugzilla
--- Comment From naveed...@in.ibm.com 2018-05-02 02:05 EDT--- (In reply to comment #82) > (In reply to comment #81) > > This bug looks to be fixed in the d-i serial 20101020ubuntu540 build. > > > > Should we close this bug? > > Yes, closing it at our side. > > By the way, did you measure if the disk scan is considerably slower than > previously? We could not make out the difference of the time of taken for disk scan as user<<- -may be we did not notice 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/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: Fix Released Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: ---Problem Description--- Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based HDD/RAID arrays Tried with current bionic and current bionic-proposed installers wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e ---uname output--- uname -a Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:05:20 UTC 2018 ppc64le GNU/Linux Machine Type = 8247-22L (S822L) ---boot type--- Network boot ---bootloader--- petitboot shell ---Kernel cmdline used to launch install--- #cat /proc/cmdline ---Bootloader protocol--- http ---Install repository type--- Internet repository ---Install repository Location--- US ---Point of failure--- Problem during post-install (stage 2) configuration or other problem seen after reboot ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? ? ?? ? ? ??? moves; selects; activates buttons ~ # lsmod | grep -i ipr ipr 148677 0 ~ # modinfo ipr filename: /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko version:2.6.4 license:GPL description:IBM Power RAID SCSI Adapter Driver author: Brian King srcversion: 05BB872A11F65B3A73AB352 alias: pci:v1014d04DAsv1014sd04FBbc*sc*i* alias: pci:v1014d04DAsv1014sd04FCbc*sc*i* alias: pci:v1014d034Asv1014sd04C9bc*sc*i* alias: pci:v1014d034Asv1014sd04C8bc*sc*i* alias: pci:v1014d034Asv1014sd04C7bc*sc*i* alias: pci:v1014d034Asv1014sd049Cbc*sc*i* alias: pci:v1014d034Asv1014sd049Bbc*sc*i* alias: pci:v1014d034Asv1014sd049Abc*sc*i* alias: pci:v1014d034Asv1014sd0499bc*sc*i* alias: pci:v1014d034Asv1014sd0475bc*sc*i* alias: pci:v1014d034Asv1014sd0474bc*sc*i* alias: pci:v1014d034Asv1014sd04CAbc*sc*i* alias: pci:v1014d034Asv1014sd046Dbc*sc*i* alias: pci:v1014d034Asv1014sd03FEbc*sc*i* alias: pci:v1014d034Asv1014sd03FFbc*sc*i* alias: pci:v1014d034Asv1014sd03FCbc*sc*i* alias: pci:v1014d034Asv1014sd03FBbc*
[Kernel-packages] [Bug 1768422] 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 1768422 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/1768422 Title: the dependency of kernel package should restrict expected version of linux-firmware Status in linux package in Ubuntu: Incomplete Bug description: Recently, we got a lesson learn from oem issues[1][2] that linux- firmware should always be updated while update kernel package. The root cause is some kernel update will expect linux-firmware be updated as well. Users who install new kernel manually could also encounter the same issue that expected firmware is not there to feed new installed kernel. There's a dependency for linux-firmware in linux-image-generic but not restrict the version. That means installing new kernel manually will not pull latest linux-firmware as well. Say, in [2] case, user's system have: linux-firmware 1.157.4 linux-image 4.4.0-73 Then user install newer kernel by apt-get install, and he will encounter the same error because the newer linux-firmware will not be installed as well. So for better user experience, the depends of each released linux-image packages should be changed to something like Depends: linux-firmware (>= 1.157.17) or to make sure kernel could backward compatible if kernel package not restrict it's linux-firmware dependency. [1] LP: #1746155 [2] LP: #1764930 , comment #27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768422/+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 1761729] Comment bridged from LTC Bugzilla
--- Comment From pavra...@in.ibm.com 2018-05-02 01:02 EDT--- (In reply to comment #28) > I tried to reproduce this on my machine and I was not able to. I am using > kernel 4.15.0-20-generic and I run: > > # ltp-install pwd > /home/breno/ltp-install > > # ltp-install sudo ./runltp > > Is there any other way to reproduce it? Issue is not observed on 4.15.0-20-generic kernel. We can close the bug. [1]+ Exit 1 nohup ./runltp root@ltc-briggs1:/opt/ltp# uname -a Linux ltc-briggs1 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-briggs1:/opt/ltp# tail -n 30 nohup.out tag=cve-2018-5803_2 stime=1525093814 cmdline="sctp_big_chunk -a 1" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s sctp_big_chunk.c:53: INFO: sctp server listen on 38843 sctp_big_chunk.c:68: INFO: bind 1 additional IP addresses sctp_big_chunk.c:108: PASS: test doesn't cause crash Summary: passed 1 failed 0 skipped 0 warnings 0 incrementing stop <<>> initiation_status="ok" duration=5 termination_type=exited termination_id=0 corefile=no cutime=0 cstime=520 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20180118-267-g4fbb02a1d ### Done executing testcases. LTP Version: 20180118-267-g4fbb02a1d ### -- 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/1761729 Title: Ubuntu 18.04 Machine crashed while running ltp. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Briggs P8 ]: Machine crashed while running ltp. ---Environment-- Kernel Build: Ubuntu 18.04 System Name : ltc-briggs2 Model/Type : P8 Platform: BML ---Uname output--- root@ltc-briggs2:~# uname -a Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- $ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install ltp = root@ltc-briggs2:~# root@ltc-briggs2:~# [10781.098337] LTP: starting fs_inod01 (fs_inod $TMPDIR 10 10 10) [10782.837910] LTP: starting linker01 (linktest.sh 1000 1000) [10784.504474] LTP: starting openfile01 (openfile -f10 -t10) [10784.534953] LTP: starting inode01 [10784.550767] LTP: starting inode02 [10784.739104] LTP: starting stream01 [10784.740840] LTP: starting stream02 [10784.742487] LTP: starting stream03 [10784.744532] LTP: starting stream04 [10784.746087] LTP: starting stream05 [10784.747722] LTP: starting ftest01 [10785.142054] LTP: starting ftest02 [10785.158852] LTP: starting ftest03 [10785.404760] LTP: starting ftest04 [10785.527197] LTP: starting ftest05 [10785.937164] LTP: starting ftest06 [10785.958360] LTP: starting ftest07 [10786.463382] LTP: starting ftest08 [10786.592998] LTP: starting lftest01 (lftest 100) [10786.672707] LTP: starting writetest01 (writetest) [10786.774292] LTP: starting fs_di (fs_di -d $TMPDIR) [10792.973510] LTP: starting proc01 (proc01 -m 128) [10793.865686] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead [10795.785593] LTP: starting read_all_dev (read_all -d /dev -e '/dev/watchdog?(0)' -q -r 10) [10795.895774] NET: Registered protocol family 40 [10795.918763] Bluetooth: Core ver 2.22 [10795.918866] NET: Registered protocol family 31 [10795.918909] Bluetooth: HCI device and connection manager initialized [10795.918955] Bluetooth: HCI socket layer initialized [10795.918991] Bluetooth: L2CAP socket layer initialized [10795.919032] Bluetooth: SCO socket layer initialized [10798.374850] usercopy: kernel memory exposure attempt detected from 29431ea4 () (1023 bytes) [10798.374952] [ cut here ] [10798.374988] kernel BUG at /build/linux-2BXDjB/linux-4.15.0/mm/usercopy.c:72! [10798.375041] Oops: Exception in kernel mode, sig: 5 [#1] [10798.375080] LE SMP NR_CPUS=2048 [10871.343999650,5] OPAL: Switch to big-endian OS NUMA PowerNV [10798.375117] [10876.190849323,5] OPAL: Switch to little-endian OS Modules linked in: hci_vhci bluetooth ecdh_generic vhost_vsock cuse vmw_vsock_virtio_transport_common userio vsock uhid vhost_net vhost tap snd_seq snd_seq_device snd_timer snd soundcore binfmt_misc sctp quota_v2 quota_tree nls_iso8859_1 ntfs xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf
[Kernel-packages] [Bug 1768422] [NEW] the dependency of kernel package should restrict expected version of linux-firmware
Public bug reported: Recently, we got a lesson learn from oem issues[1][2] that linux- firmware should always be updated while update kernel package. The root cause is some kernel update will expect linux-firmware be updated as well. Users who install new kernel manually could also encounter the same issue that expected firmware is not there to feed new installed kernel. There's a dependency for linux-firmware in linux-image-generic but not restrict the version. That means installing new kernel manually will not pull latest linux-firmware as well. Say, in [2] case, user's system have: linux-firmware 1.157.4 linux-image 4.4.0-73 Then user install newer kernel by apt-get install, and he will encounter the same error because the newer linux-firmware will not be installed as well. So for better user experience, the depends of each released linux-image packages should be changed to something like Depends: linux-firmware (>= 1.157.17) or to make sure kernel could backward compatible if kernel package not restrict it's linux-firmware dependency. [1] LP: #1746155 [2] LP: #1764930 , comment #27 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linphone (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/1768422 Title: the dependency of kernel package should restrict expected version of linux-firmware Status in linux package in Ubuntu: New Bug description: Recently, we got a lesson learn from oem issues[1][2] that linux- firmware should always be updated while update kernel package. The root cause is some kernel update will expect linux-firmware be updated as well. Users who install new kernel manually could also encounter the same issue that expected firmware is not there to feed new installed kernel. There's a dependency for linux-firmware in linux-image-generic but not restrict the version. That means installing new kernel manually will not pull latest linux-firmware as well. Say, in [2] case, user's system have: linux-firmware 1.157.4 linux-image 4.4.0-73 Then user install newer kernel by apt-get install, and he will encounter the same error because the newer linux-firmware will not be installed as well. So for better user experience, the depends of each released linux-image packages should be changed to something like Depends: linux-firmware (>= 1.157.17) or to make sure kernel could backward compatible if kernel package not restrict it's linux-firmware dependency. [1] LP: #1746155 [2] LP: #1764930 , comment #27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768422/+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 1768422] [NEW] the dependency of kernel package should restrict expected version of linux-firmware
You have been subscribed to a public bug: Recently, we got a lesson learn from oem issues[1][2] that linux- firmware should always be updated while update kernel package. The root cause is some kernel update will expect linux-firmware be updated as well. Users who install new kernel manually could also encounter the same issue that expected firmware is not there to feed new installed kernel. There's a dependency for linux-firmware in linux-image-generic but not restrict the version. That means installing new kernel manually will not pull latest linux-firmware as well. Say, in [2] case, user's system have: linux-firmware 1.157.4 linux-image 4.4.0-73 Then user install newer kernel by apt-get install, and he will encounter the same error because the newer linux-firmware will not be installed as well. So for better user experience, the depends of each released linux-image packages should be changed to something like Depends: linux-firmware (>= 1.157.17) or to make sure kernel could backward compatible if kernel package not restrict it's linux-firmware dependency. [1] LP: #1746155 [2] LP: #1764930 , comment #27 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- the dependency of kernel package should restrict expected version of linux-firmware https://bugs.launchpad.net/bugs/1768422 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 1761831] Re: ASUS B150M Gaming hibernate/resume failure
For all 3 (three) PCs (Acer X3-710, B150M Gaming Pro and ASUS P8H67-M PRO): 1. Ubuntu MATE 17.10 & kernel 4.15.x / 4.16.x => Hibernate / Resume from Hibernate works perfectly 2. Ubuntu MATE 17.10 & kernel 4.13.0.21 => Hibernate / Resume from Hibernate works perfectly 3. Ubuntu MATE 17.10 & kernel 4.13.0.y (y >=25) => Hibernate / Resume from Hibernate does not work at all - PC restarts and a few seconds later the monitor goes black and shortly after in suspend mode - keyboard is frozen / dead - pressing any key of the keyboard does nothing, pressing Caps-Lock does nothing - see https://ubuntu-mate.community/t/hibernation-broken-in-kernel-4-13-0-25/15736 4. Ubuntu MATE 18.04 & kernel 4.15.x (x = any available) / 4.16.x (x <= 3) => Hibernate / Resume from Hibernate does not work - PC starts as if I would've rebooted it instead of resuming it from hibernate - I can work normally but previous state / session is not restored - the error window appears stating that "This occurred during a previous hibernation, and prevented the system from resuming properly" - unfortunately it does not offer submit any other bug reports (even if I click "Continue") - it's the same behaviour: for any of the listed PCs when upgraded from 17.10 to 18.04 or fresh install of 18.04 (Beta 1, Beta 2 or Release) This is the reason why I do not thing that kernels 4.15 / 4.16 are the reason for this issue, but I may be totally wrong. -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO 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.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING: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 manuf
[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13
Try reinstalling the driver? $ sudo apt --reinstall install nvidia-driver-390 -- 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/1751990 Title: problems with kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I have a laptop call dc pro. it is made in china. processor is Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The problems are: 1 the ubuntu 16.04.03 installation will hang somewhere. luckily 16.04.02 will go through. 2 the system will not boot after upgrade to kernel 4.13. the old kernel 4.8 will boot without problem. 3 After install the cuda 9.1 both kernel will boot, but nvidia did not come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia commands left "nvidia-detector nvidia-modprobe nvidia-settings" ) for the kernel 4.13, the old kernel 4.8 is ok though ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.24 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Feb 27 13:39:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-17 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weilo 1661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697 InstallationDate: Installed on 2018-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shinelon Computer W65KJ1_KK1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-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/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65KJ1_KK1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: W65KJ1_KK1 dmi.product.version: Not Applicable dmi.sys.vendor: Shinelon Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990/+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 1761831] Re: ASUS B150M Gaming hibernate/resume failure
According to this: Acer X3-710 PC - Ubuntu MATE 17.10 and kernel 4.15.x / 4.16.x - Hibernate / Resume from Hibernate works as expected Acer X3-710 PC - Ubuntu MATE 18.04 Beta 2 fresh install or upgrade from Ubuntu MATE 17.10 and kernel 4.15.x / 4.16.x - Hibernate / Resume from Hibernate does NOT WORK Sounds like it's not a kernel issue. When the resume failed, does the led turns on/off when you press caps lock? -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO 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.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING: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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+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 1766601] Re: linux: 3.13.0-146.195 -proposed tracker
3.13.0-146.195 - generic Regression test CMPL. Issue to note in amd64: ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - 40 failed on amaura, 26 failed on groucho, 39 failed on pepe Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - test 060 should be skipped (bug 1712038) test 021, 022 (bug 1747847) test 050 (bug 1684776) test 072 (bug 1747850) test 075 (bug 1712007) test 82 (bug 1747853) Issue to note in i386: ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - test suite failed to build (bug 1765366) Issue to note in ppc64le: ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1766601 Title: linux: 3.13.0-146.195 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1766603 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766601/+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 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker
4.13.0-1014.18 - gcp Regression test CMPL. Issue to note in gcp: libhugetlbfs - 1 failed , 1 killed by signal, 3 bad config ubuntu_kvm_unit_tests - test disabled ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu Lin (cypressyew) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1766596 Title: linux-gcp: 4.13.0-1014.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766596/+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 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1766599 Title: linux-oem: 4.13.0-1025.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766599/+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 1766592] Re: linux: 4.13.0-40.45 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1766592 Title: linux: 4.13.0-40.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766592/+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 1766604] Re: linux: 4.4.0-123.147 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1766604 Title: linux: 4.4.0-123.147 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial) derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766604/+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 1768381] [NEW] package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess ret
Public bug reported: running on asus c300m chromebook, installed Gallium-OS kernel for full hardware support. error seems to relate to removal of the generic kernel used by ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic (not installed) Uname: Linux 4.8.17-galliumos x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 18:55:53 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-27 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (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 linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1768381 Title: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed package in Ubuntu: New Bug description: running on asus c300m chromebook, installed Gallium-OS kernel for full hardware support. error seems to relate to removal of the generic kernel used by ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic (not installed) Uname: Linux 4.8.17-galliumos x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 18:55:53 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-27 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic (not installed) failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768381/+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 1767397] Re: linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1767397 Title: linux: 4.15.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1767410 (linux-hwe-edge) derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 (linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Tuesday, 01. May 2018 13:35 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+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 1645540] Re: [Feature] Crystal Ridge 2LM error reporting
This feature is not done. Thanks -- 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/1645540 Title: [Feature] Crystal Ridge 2LM error reporting Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: In 2LM configurations we need to error reports to differentiate between errors in the "near" memory (DRAM used as cache) and "far" memory (Crystal ridge memory) HW: Apache Pass Upstream schedule: kernel: 4.17 Target Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645540/+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 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds
Same on 18.04, but I'm using btrfs for both root and home, so can't purge the package.. Any idea? It hangs for about 30 sec before continuing, annoying to have this slow boots on a SSD.. -- 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/1460447 Title: Boot slow, "scanning for btrfs filesystems" takes 100 seconds Status in linux package in Ubuntu: Confirmed Bug description: I installed 14.10 and used btrfs for /home. Later, I did a clean install of 15.04, using the same /home partition. Ever since then, boots have been agonizingly slow; all the delay appears to be while the message "scanning for btrfs filesystems" is diplayed early in boot. The system is an i7 with one disk: root@i7:~# fdisk /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x7f84 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 117186559 117184512 55.9G 83 Linux /dev/sda2 117186560 234373119 117186560 55.9G 83 Linux /dev/sda3 234375166 1953523711 1719148546 819.8G 5 Extended /dev/sda5 234375168 273434623 39059456 18.6G 82 Linux swap / Solaris /dev/sda6 273436672 1953523711 1680087040 801.1G 83 Linux root@i7:~# df -T | grep sd /dev/sda2 ext4 57542652 10103624 44492980 19% / /dev/sda6 btrfs840043520 172076728 665321064 21% /home I'll attach a bootchart, but I suspect the btrfs delay happens before the bootchart starts? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2176 F pulseaudio /dev/snd/controlC0: dank 2176 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 08:53:37 2015 HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223 InstallationDate: Installed on 2015-05-16 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: X58 Extreme dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1460447/+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 1763403] Re: Multiple Memory Corruption Issues in ntfs.ko (Linux 4.15.0-15.16)
Excellent, thanks Sergej. ** Information type changed from Private Security to Public Security -- 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/1763403 Title: Multiple Memory Corruption Issues in ntfs.ko (Linux 4.15.0-15.16) Status in linux package in Ubuntu: Triaged Bug description: Dear all, The following memory corruption issues in ntfs.ko (such as use-after-frees, stack- and heap-out-of-bounds accesses and BUG_ON / BUG assertion fails) were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the causing NTFS filesystem image, the dmesg reports, KASAN reports and the source code of a simple mounting tool to reproduce those issues (ntfs_inject.c). A local users who have been granted the privileges necessary to mount filesystems (or a system components which auto mounts filesystems) could trigger a kernel oops, a kernel panic (depending on panic_on_oops) or exploit those bugs to raise privileges. We can verify this issues for Linux 4.15.0-15.16 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source linux"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763403/+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 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"
Sound is not completely broken: With chromium-browser i can watch videos with sound on youtube.com, and on slack.com both speaker and microphone work. But using Firefox with the same web sites does not have any sound. The music players Amarok and Rhythmbox also do not produce sound, which makes me sad. I have not found one that works. Any suggestions as to where to start if i want to try and fix this myself? -- 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/1761051 Title: laptop sound broken in latest update -- "No output or input devices found" Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: after i installed the latest update for Kubuntu 17.10 my audio devices disappeared and i lost the ability to listen to music or play sounds on my laptop. it worked fine before the update! (Caveat: sometimes ads or youtube will play through the speakers or headphones but it is unpredictable and i have no control over volume or muting.) the Plasma Audio Volume settings show "No Output Devices Available" and "No Input Devices Available". it worked fine before the last update. this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a high end version with an E3-1505M CPU and "hybrid graphics". i do not update the software every day so the problem may have been introduced upto two weeks ago, but no earlier then that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE Date: Tue Apr 3 21:38:36 2018 HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02 InstallationDate: Installed on 2018-01-12 (81 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: LENOVO 20HHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET31W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW 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: dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761051/+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 1765241] Re: virtio_scsi race can corrupt memory, panic kernel
** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1765241 Title: virtio_scsi race can corrupt memory, panic kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: There's a race in the virtio_scsi driver (for all kernels) That race is inadvertently avoided on most kernels due to a synchronize_rcu call coincidentally placed in one of the racing code paths By happenstance, the set of patches backported to the Ubuntu 4.4 kernel ended up without a synchronize_rcu in the relevant place. The issue first manifests with commit be2a20802abbde04ae09846406d7b670731d97d2 Author: Jan Kara Date: Wed Feb 8 08:05:56 2017 +0100 block: Move bdi_unregister() to del_gendisk() BugLink: http://bugs.launchpad.net/bugs/1659111 The race can cause a kernel panic due to corruption of a freelist pointer in a slab cache. The panics occur in arbitrary places as the failure occurs at an allocation after the corruption of the pointer. However, the most common failure observed has been within virtio_scsi itself during probe processing, e.g.: [3.111628] [] kfree_const+0x22/0x30 [3.112340] [] kobject_release+0x94/0x190 [3.113126] [] kobject_put+0x27/0x50 [3.113838] [] put_device+0x17/0x20 [3.114568] [] __scsi_remove_device+0x92/0xe0 [3.115401] [] scsi_probe_and_add_lun+0x95b/0xe80 [3.116287] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [3.117227] [] ? __pm_runtime_resume+0x5b/0x80 [3.118048] [] __scsi_scan_target+0x10a/0x690 [3.118879] [] scsi_scan_channel+0x7e/0xa0 [3.119653] [] scsi_scan_host_selected+0xf3/0x160 [3.120506] [] do_scsi_scan_host+0x8d/0x90 [3.121295] [] do_scan_async+0x1c/0x190 [3.122048] [] async_run_entry_fn+0x48/0x150 [3.122846] [] process_one_work+0x165/0x480 [3.123732] [] worker_thread+0x4b/0x4d0 [3.124508] [] ? process_one_work+0x480/0x480 Details on the race: CPU A: virtscsi_probe [...] __scsi_scan_target scsi_probe_and_add_lun [on return calls __scsi_remove_device, below] scsi_probe_lun [...] blk_execute_rq blk_execute_rq waits for the completion event, and then on wakeup returns up to scsi_probe_and_all_lun, which calls __scsi_remove_device. In order for the race to occur, the wakeup must occur on a CPU other than CPU B. After being woken up by the completion of the request, the call returns up the stack to scsi_probe_and_add_lun, which calls __scsi_remove_device: __scsi_remove_device blk_cleanup_queue [ no longer calls bdi_unregister ] scsi_target_reap(scsi_target(sdev)) scsi_target_reap_ref_put kref_put kref_sub scsi_target_reap_ref_release scsi_target_destroy ->target_destroy() = virtscsi_target_destroy kfree(tgt) <=== FREE TGT Note that the removal of the call to bdi_unregister in commit xenial be2a20802abbde block: Move bdi_unregister() to del_gendisk() and annotated above is the change that gates whether the issue manifests or not. The other code change from be2a20802abbde has no effect on the race. CPU B: vring_interrupt virtscsi_complete_cmd scsi_mq_done (via ->scsi_done()) scsi_mq_done blk_mq_complete_request __blk_mq_complete_request [...] blk_end_sync_rq complete [ wake up the task from CPU A ] After waking the CPU A task, execution returns up the stack, and then calls atomic_dec(&tgt->reqs) in virtscsi_complete_cmd immediately after returning from the call to ->scsi_done. If the activity on CPU A after it is woken up (starting at __scsi_remove_device) finishes before CPU B can call atomic_dec() in virtscsi_complete_cmd, then the atomic_dec() will modify a free list pointer in the freed slab object that contained tgt. This causes the system to panic on a subsequent allocation from the per-cpu slab cache. The call path on CPU B is significantly shorter than that on CPU A after wakeup, so it is likely that an external event delays CPU B. This could be either an interrupt within the VM or scheduling delays for the virtual cpu process on the hypervisor. Whatever the delay is, it is not the root cause but merely the triggering event. The virtscsi race window described above exists in all kernels that have been checked (4.4 upstream LTS, Ubuntu 4.13 and 4.15, and current mainline as of this writing). However, none of those kernels exhibit the panic in testing, only the Ubuntu 4.4 kernel after commit be2a20802abbde. The reason none of those kernels panic is they all have one thing in
[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)
Can you ensure you are booted into the test kernel posted in comment #2? It should have the following text in the uname -a output: "lp1758205" -- 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/1758205 Title: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by- path (NVMe / Bolt ) (systemd?) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: ---Problem Description--- Bolt based NVMe disks (namespaces) are not displayed on lsblk and /dev/disk/by-path # nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 1 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n10S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 10 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n11S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 11 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n12S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 12 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n13S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 13 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n14S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 14 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n15S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 15 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n16S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 16 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n17S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 17 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n18S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 18 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n19S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 19 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n2 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 2 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n20S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 20 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n21S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 21 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n22S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 22 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n23S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 23 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n24S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 24 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n25S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 25 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n26S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 26 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n27S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 27 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n28S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 28 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n29S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 29 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n3 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 3 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n30S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 30 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n31S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 31 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n32S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 32 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n4 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8 4 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12 /dev/nvme0n5 S3RVNA0J600206 PCIe3 1.6TB NVMe Fla
[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36
The original bug reporter is unable to reproduce this bug, so would it be possible for others affected to test the latest mainline kernel? It is available for download from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 -- 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/1751098 Title: Ubuntu hangs shortly after booting with kernel 4.13.0-36 Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: After upgrading to linux 4.13.0-36 my laptop hangs shortly after booting, even before logging in to the desktop. It starts with the interface being unresponsive but the mouse cursor moving, and shortly after that the mouse cursor also hangs intermittently and then permanently. Linux 4.13.0-32 works fine. My laptop is a Dell XPS 13 9360 with an Core i5 7200u. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USUARIOORDEN DE ACCESO PID /dev/snd/controlC0: nicolas2111 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Thu Feb 22 10:56:06 2018 InstallationDate: Installed on 2018-02-02 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751098/+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 1766377] Re: Ethernet E1000 Controller Hangs
Can you see if this bug also happens with the latest mainline kernel, or if it was already fixed upstream? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 -- 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/1766377 Title: Ethernet E1000 Controller Hangs Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic hanging of the LAN connection. This is happening on an Asus X99-DELUX motherboard, controller specifications: Intel® I218V, 1 x Gigabit LAN Controller(s) Intel® I211-AT, 1 x Gigabit LAN Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) appliance Support Teaming Technology ASUS Turbo LAN Utility The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM. This machine has a number of Qemu/KVM virtual guests and is using a software bridge to share the interface. This did not happen with 17.10 and 4.13.0 kernel. It is happening on multiple machines here. Here are the messages from dmesg: 1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d0880> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang: TDH TDT <2d> next_to_use <2d> next_to_clean buffer_info[next_to_clean]: time_stamp <13c8d0008> next_to_watch jiffies <13c8d1040> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3c00> PHY Extended Status<3000> PCI Status <10> [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly [1016202.413701] bridge0: port 1(eno1) entered disabled state [1016202.413732] bridge0: topology change detected, propagating [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [1016206.666708] bridge0: port 1(eno1) entered blocking state [1016206.666712] bridge0: port 1(eno1) entered listening state [1016216.750911] bridge0: port 1(eno1) entered learning state [1016232.110291] bridge0: port 1(eno1) entered forwarding state [1016232.110294] bridge0: topology change detected, sending tcn bpdu [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for regulatory database [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [1017834.414792] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [1017834.414794] cfg80211: failed to load regulatory.db If there is any other information I can provide to aid in resolution, please contact me, nan...@eskimo.com. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Mon Apr 23 16:45:30 2018 HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5 InstallationDate: Installed on 2017-05-05 (353 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1 PulseList: Error: command
[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"
OK, i'm now running the V4.16.0 kernel: > craigster0@p51:/local/home/craigster0/Downloads/linux-kernel-4.16$ uname -r > 4.16.0-041600-generic and clicking on the "speaker icon" on the menu bar at the bottom of the screen still shows "No output or input devices found". more importantly, trying to play audio with Amarok or Rhythmbox produces no audible signal. i also tried booting with the oldest kernel still installed on the box, vmlinuz-4.13.0-36-generic, which was installed well before this problem occurred and the sound still didn't work. to the best of my recollection. i don't think this problem was _caused_ by a kernel update. both speakers and microphone worked fine with all apps before i performed a software update, and failed after that. the trick is figuring out exactly which software update caused the problem! -- 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/1761051 Title: laptop sound broken in latest update -- "No output or input devices found" Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: after i installed the latest update for Kubuntu 17.10 my audio devices disappeared and i lost the ability to listen to music or play sounds on my laptop. it worked fine before the update! (Caveat: sometimes ads or youtube will play through the speakers or headphones but it is unpredictable and i have no control over volume or muting.) the Plasma Audio Volume settings show "No Output Devices Available" and "No Input Devices Available". it worked fine before the last update. this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a high end version with an E3-1505M CPU and "hybrid graphics". i do not update the software every day so the problem may have been introduced upto two weeks ago, but no earlier then that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE Date: Tue Apr 3 21:38:36 2018 HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02 InstallationDate: Installed on 2018-01-12 (81 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: LENOVO 20HHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET31W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW 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: dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761051/+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 1765025] Re: apparmor mount regression test fails when CONFIG_MANDATORY_FILE_LOCKING is disabled
This has been addressed upstream in apparmor in https://gitlab.com/apparmor/apparmor/commit/49ba6af2bf49be9eff89ce760cca60f33eb8e341 (and cherry-picked to older releases). A fix has been applied to qrt to incorporate the patch in https://git.launchpad.net/qa-regression- testing/commit/?id=0e2d55c657e40fc8acd0526a1382f2be19211abc . The Ubuntu kernel team should probbly decide whether or not linux-kvm should be consistent with the generic ubuntu kernel on CONFIG_MANDATORY_FILE_LOCKING. Thanks! ** Changed in: apparmor Status: Triaged => Fix Released ** Changed in: qa-regression-testing Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765025 Title: apparmor mount regression test fails when CONFIG_MANDATORY_FILE_LOCKING is disabled Status in AppArmor: Fix Released Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: New Bug description: Like bug 1760672, the test_regression_testsuite in ubuntu_qrt_apparmor failed with 4.15.0-1004-kvm But the error message is a little bit different. The "mount" test failed in this case. FAIL: test_regression_testsuite (__main__.ApparmorTestsuites) Run kernel regression tests -- Traceback (most recent call last): File "./test-apparmor.py", line 1716, in test_regression_testsuite self.assertEqual(expected, rc, result + report) AssertionError: Got exit code 2, expected 0 running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) (ioperm) (iopl) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3444 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3481 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3769 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3803 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3842 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3881 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3920 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount Error: mount failed. Test 'MOUNT (unconfined)' was expected to 'pass'. Reason for failure 'FAIL: mount /dev/loop0 on /tmp/sdtest.2351-23651-C7r5Aj/mountpoint failed
[Kernel-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one
** Summary changed: - Regression: /etc/modules checked against blacklist + Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767172 Title: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. e.g. bcm2835_wdt module on arm64 === Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1767172] Re: Regression: /etc/modules checked against blacklist
Please note automatic blacklisting of watchdog modules was done to prevent "accidental" watchdog misuse, resulting in "random" shutdowns of production machines. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 for more details. I'm not sure how to reconcile "blacklist as a precaution" with "I know what I am doing, I really want watchdog". -- 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/1767172 Title: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. e.g. bcm2835_wdt module on arm64 === Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1768121] Re: Mainline Kernel since 4.16.4 has postinstall script error
Part of this bug report is a duplicate with bug 1766728, and I believe that was fixed as of a couple of hours ago. The other part of this bug report, about needing libssl1.1, isn't fixed, as far as I know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768121 Title: Mainline Kernel since 4.16.4 has postinstall script error Status in linux package in Ubuntu: Confirmed Bug description: Hello, I don't know who does the packaging for the Mainline Kernel(http://kernel.ubuntu.com/~kernel-ppa/mainline/), but it has been erroring out in packaging and also for the packages in x64/32 that have made it, there are post install script errors within the packaging which disallow installation of the kernel. Tested on Ubuntu 16.04. Selecting previously unselected package linux-headers-4.16.6-041606. (Reading database ... 392264 files and directories currently installed.) Preparing to unpack linux-headers-4.16.6-041606_4.16.6-041606.201804300418_all.deb ... Unpacking linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-headers-4.16.6-041606-generic. Preparing to unpack linux-headers-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-headers-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-image-unsigned-4.16.6-041606-generic. Preparing to unpack linux-image-unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-image-unsigned-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Selecting previously unselected package linux-modules-4.16.6-041606-generic. Preparing to unpack linux-modules-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... Unpacking linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Setting up linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... dpkg: dependency problems prevent configuration of linux-headers-4.16.6-041606-generic: linux-headers-4.16.6-041606-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.16.6-041606-generic (--install): dependency problems - leaving unconfigured Setting up linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) ... Setting up linux-image-unsigned-4.16.6-041606-generic (4.16.6-041606.201804300418) ... /var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: 50: /var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-unsigned-4.16.6-041606-generic (--install): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-headers-4.16.6-041606-generic linux-image-unsigned-4.16.6-041606-generic What's new in 4.16.6 is the libssl1.1 dependency, as it just errored out with a half installed kernel and that post-installation script error you see above. Please let whoever packages these kernels know that is't been dead stick post 4.16.3. Thanks. HH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+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 1767172] 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 1767172 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/1767172 Title: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. e.g. bcm2835_wdt module on arm64 === Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1767172] Re: Regression: /etc/modules checked against blacklist
** Description changed: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. + e.g. bcm2835_wdt module on arm64 + === - - Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): + Before systemd-modules-load, /etc/init.d/kmod would load modules + directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. -- 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/1767172 Title: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. e.g. bcm2835_wdt module on arm64 === Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+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 1768315] 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 1768315 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/1768315 Title: Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki- Fedora 27 and Debian 9 Status in linux package in Ubuntu: Incomplete Bug description: I am Brazilian if it is possible to use a clear English thank you. I am using google translator. What runs it is that no matter what OS I use and where I install it, always using Nouveau it gets this instability, and when using the NVIDIA proprietary driver, it is not shown this problem but it gets stuck (locking). I have not figured out how to solve it and all the colutions I find are not the same as the ones I face. So I'm reporting this bug. Linux Zion 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" 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=bionic UBUNTU_CODENAME=bionic Handle 0x003D, DMI type 127, 4 bytes End Of Table 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 02:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : A
[Kernel-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist
Looking at where the blacklists come from, it looks like kernel autogenerates "blacklist_linux_4.15-0-15-generic.conf" files which have a combination of OSS and watchdog blacklists. this indeed is not very nice/easy to override. I wonder if the "watchdog" like modules should be shipped in separate files elsewhere on disk, and collected into a "watchdog.conf" file which matches blacklists for all installed kernels? That way it would be easier for admin to override it, by dropping in an empty /etc/modules- load.d/watchdog.conf? Not sure how to make these modules 'available' yet not autoloaded. Split them into a separate -watchdog-modules binary package? not installed = not autoloaded? without any blacklists at all? ** Description changed: - Before systemd-modules-load, /etc/init.d/kmod would load modules - directly with "modprobe" (and _not_ "modprobe -b"): + Impossible / hard to force the system to load a watchdog module because + it is blacklisted by the kernel auto-generated list of "watchdog" + modules. + + /etc/modules used to "just work" before. + + === + + + Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { - local module args - module="$1" - args="$2" + local module args + module="$1" + args="$2" - if [ "$VERBOSE" != no ]; then - log_action_msg "Loading kernel module $module" - modprobe $module $args || true - else - modprobe $module $args > /dev/null 2>&1 || true - fi + if [ "$VERBOSE" != no ]; then + log_action_msg "Loading kernel module $module" + modprobe $module $args || true + else + modprobe $module $args > /dev/null 2>&1 || true + fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { - const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; + const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... - default: - err = kmod_module_probe_insert_module(mod, probe_flags, - NULL, NULL, NULL, NULL); + default: + err = kmod_module_probe_insert_module(mod, probe_flags, + NULL, NULL, NULL, NULL); - if (err == 0) - log_info("Inserted module '%s'", kmod_module_get_name(mod)); - else if (err == KMOD_PROBE_APPLY_BLACKLIST) - log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); + if (err == 0) + log_info("Inserted module '%s'", kmod_module_get_name(mod)); + else if (err == KMOD_PROBE_APPLY_BLACKLIST) + log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. -- 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/1767172 Title: Regression: /etc/modules checked against blacklist Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Impossible / hard to force the system to load a watchdog module because it is blacklisted by the kernel auto-generated list of "watchdog" modules. /etc/modules used to "just work" before. e.g. bcm2835_wdt module on arm64 === Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL);
[Kernel-packages] [Bug 1768315] Re: Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki-Fedora 27 and Debian 9
Uma screenshot do htop. ** Description changed: I am Brazilian if it is possible to use a clear English thank you. I am using google translator. What runs it is that no matter what OS I use and where I install it, always using Nouveau it gets this instability, and when using the NVIDIA proprietary driver, it is not shown this problem but it gets stuck (locking). I have not figured out how to solve it and all the colutions I find are not the same as the ones I face. So I'm reporting this bug. Linux Zion 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" 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=bionic UBUNTU_CODENAME=bionic Handle 0x003D, DMI type 127, 4 bytes End Of Table 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 02:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX-8370 Eight-Core Processor stepping: 0 microcode : 0x600081c cpu MHz : 1807.324 cache size : 2048 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu 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 lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nri
[Kernel-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767172 Title: Regression: /etc/modules checked against blacklist Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Before systemd-modules-load, /etc/init.d/kmod would load modules directly with "modprobe" (and _not_ "modprobe -b"): load_module() { local module args module="$1" args="$2" if [ "$VERBOSE" != no ]; then log_action_msg "Loading kernel module $module" modprobe $module $args || true else modprobe $module $args > /dev/null 2>&1 || true fi } However, under 18.04, systemd-modules-load will _ignore_ modules that are manually listed in /etc/modules and process them with the blacklist (the same as "modprobe -b" would). This means that it is not possible to manually load modules that are blacklisted (like watchdog modules): systemd-238/src/modules-load/modules-load.c: static int load_module(struct kmod_ctx *ctx, const char *m) { const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST; ... default: err = kmod_module_probe_insert_module(mod, probe_flags, NULL, NULL, NULL, NULL); if (err == 0) log_info("Inserted module '%s'", kmod_module_get_name(mod)); else if (err == KMOD_PROBE_APPLY_BLACKLIST) log_info("Module '%s' is blacklisted", kmod_module_get_name(mod)); Blacklists should _not_ be applied by systemd-modules-load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
This was after a fresh install of 18.04 desktop last Friday. I don’t believe any updates have applied since then. I will look at testing the latest upstream kernel. I am not completely sure, but I think this may only happen when the t570 is on battery. --Galvin > On May 1, 2018, at 12:50 PM, Joseph Salisbury > wrote: > > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.16 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => High > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768292 > > Title: > Bionic: Intermittently sent to Emergency Mode on boot with unhandled > kernel NULL pointer dereference at 0980 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. > Sometimes, at boot, the system goes into Emergency Mode. In looking > at journalctl -xb output, the following messages are logged: > > May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri > Kosina > May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID > 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on > May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID > 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on > May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered > May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - > Copyright 2005-2007 Rodolfo Giometti > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI > initialized, starting thunderbolt > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX > ring 0 of size 10 > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX > ring 0 of size 10 > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control > channel created > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control > channel starting... > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX > ring 0 > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling > interrupt at register 0x38200 bit 0 (0x0 -> 0x1) > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX > ring 0 > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling > interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) > May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM > firmware > May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL > pointer dereference at 0980 > May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 > May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 > May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI > May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core > thunderbolt(+) wmi i2c_hid hid video > May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not > tainted 4.15.0-20-generic #21-Ubuntu > May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO > 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 > May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 > May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: > 00010296 > May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: > RCX: 0050 > May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: > 0034 RDI: > May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: > 0200 R09: 0320 > May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: > R12: > May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: > 91b2efc5bb30 R15: > May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() > GS:91b31f58() knlGS: > May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: > 80050033 > May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: > 00082f944005 CR4: 003606e0 > May 01 10:05:04 galvin-T570 kerne
[Kernel-packages] [Bug 1768315] Re: Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki-Fedora 27 and Debian 9
** Description changed: I am Brazilian if it is possible to use a clear English thank you. I am using google translator. What runs it is that no matter what OS I use and where I install it, always using Nouveau it gets this instability, and when using the NVIDIA proprietary driver, it is not shown this problem but it gets stuck (locking). I have not figured out how to solve it and all the colutions I find are not the same as the ones I face. So I'm reporting this bug. Linux Zion 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" 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=bionic UBUNTU_CODENAME=bionic Handle 0x003D, DMI type 127, 4 bytes End Of Table 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 02:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX-8370 Eight-Core Processor stepping: 0 microcode : 0x600081c cpu MHz : 1807.324 cache size : 2048 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu 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 lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_cl
[Kernel-packages] [Bug 1768162] 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 1768162 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/1768162 Title: kernel crashes during boot unless IOMMU is disabled on AMD Cpu Status in linux package in Ubuntu: Incomplete Bug description: Previous - IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues Current - After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled - Disabling IOMMU within the BIOS allow booting with 4.15 kernel - Enabling IOMMU and switching to 4.4 boots fine as well under 18.04 Not Sure if this is the same as bug 1747463 Version Log Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 20:05:32 2018 InstallationDate: Installed on 2015-06-11 (1054 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768162/+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 1768315] [NEW] Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki-Fedora 27 and Debian 9
Public bug reported: I am Brazilian if it is possible to use a clear English thank you. I am using google translator. What runs it is that no matter what OS I use and where I install it, always using Nouveau it gets this instability, and when using the NVIDIA proprietary driver, it is not shown this problem but it gets stuck (locking). I have not figured out how to solve it and all the colutions I find are not the same as the ones I face. So I'm reporting this bug. Linux Zion 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" 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=bionic UBUNTU_CODENAME=bionic Handle 0x003D, DMI type 127, 4 bytes End Of Table 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 02:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX-8370 Eight-Core Processor stepping: 0 microcode : 0x600081c cpu MHz : 1807.324 cache size : 2048 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu 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 lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bugs: fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bogomips: 8036.84 TLB size
[Kernel-packages] [Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
** 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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767667] Re: kernel crash in gnome environment
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1767667 Title: kernel crash in gnome environment Status in linux package in Ubuntu: Incomplete Bug description: Apr 28 10:30:44 tatanka gnome-system-mo[4199]: Allocating size to gnome-system-monitor 0x16542b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Apr 28 10:35:49 tatanka kernel: [52343.54] gmc_v9_0_process_interrupt: 59 callbacks suppressed Apr 28 10:35:49 tatanka kernel: [52343.522230] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0) Apr 28 10:35:49 tatanka kernel: [52343.522239] amdgpu :08:00.0: at page 0x00010940 from 27 Apr 28 10:35:49 tatanka kernel: [52343.522243] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 Apr 28 10:35:49 tatanka kernel: [52343.522252] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0) Apr 28 10:35:49 tatanka kernel: [52343.522255] amdgpu :08:00.0: at page 0x000109403000 from 27 Apr 28 10:35:49 tatanka kernel: [52343.522258] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 Apr 28 10:35:49 tatanka kernel: [52343.522266] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0) A (...) then all is freezed including ctrl+alt+F3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu Date: Sat Apr 28 12:17:42 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767667/+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 1767452] Re: kernel oops when I undocked
I just realized why I thought this was not predictable. The system continues to function just fine after the Oops *until* I close my laptop. Once I close my laptop the whole thing freezes and does not recover. Attaching one last kernel log and then will leave it alone till someone asks for more detail. ** Attachment added: "kern3.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5131578/+files/kern3.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767452 Title: kernel oops when I undocked Status in linux-signed package in Ubuntu: Confirmed Bug description: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi t
[Kernel-packages] [Bug 1767568] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131556/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131558/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131557/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+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 1768115] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160.
** Tags added: kernel-da-key -- 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> S msr= 80001033 sprg0 = pvr= 004e1202 sprg1 = c7a85800 dec= 591e3e03 sprg2 = c7a85800 sp = c004f8a234a0 sprg3 = 00010008 toc= c16eae00 dar = 023c srr0 = c00c355c srr1 = 80001033 dsisr = 4000 dscr = ppr = 0010 pir= 0011 amr= uamor = dpdes = tir = cir= fscr = 05000180 tar = pspb = mmcr0 = 8000 mmcr1 = mmcr2 = pmc1 = pmc2 = pmc3 = pmc4 = mmcra = siar = pmc5 = 026c sdar = sier = pmc6 = 0861 ebbhr = ebbrr = bescr = iamr = 4000 pidr = 0034 tidr = cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220] pc: c00e4854: xmon_core+0x1f24/0x3520 lr: c00e4850: xmon_core+0x1f20/0x3520 sp: c004f8a234a0 msr: 80041033 current = 0xc004f89faf00 paca= 0xc7a85800 softe: 0irq_happened: 0x01 pid = 24028, comm = top Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> r R00 = c043b7fc R16 = R01 = c004f8a23c90 R17 = ff70 R02 = c16eae00 R18 = 0a51b4bebfc8 R03 = c00279557200 R19 = 7fffe99edbb0 R04 = c003242499c0 R20 = 0a51b4c04db0 R05 = 0002 R21 = 0a51b4c20e90 R06 = 0004 R22 = 00040f00 R07 = ff81 R23 = 0a51b4c06560 R08 = ff80 R24 = ff80 R09 = R25 = 0a51b4bec2b8 R10 = R26 = 71f177bb0b20 R11 = R27 = R12 = 2000 R28 = c00279557200 R13 = c7a85800 R29 = c004c7734210 R14 = R30 = R15 = R31 = c003242499c0 pc = c043b808 __fsnotify_parent+0x88/0x1a0 cfar= c03f9e78 dget_parent+0xe8/0x150 lr = c043b7fc __fsnotify_parent+0x7c/0x1a0 msr = 80009033 cr = 2800 ctr = c06252b0 xer =
[Kernel-packages] [Bug 1768152] Re: Brightness controll doesn't work - Samsung R560
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768143] Re: vmxnet3: update to latest ToT
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1768143 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit reset and rxvlan disabled fix. Below are the commits: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases? Thanks, Ronak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768143/+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 1768162] Re: kernel crashes during boot unless IOMMU is disabled on AMD Cpu
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1768162 Title: kernel crashes during boot unless IOMMU is disabled on AMD Cpu Status in linux package in Ubuntu: New Bug description: Previous - IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues Current - After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled - Disabling IOMMU within the BIOS allow booting with 4.15 kernel - Enabling IOMMU and switching to 4.4 boots fine as well under 18.04 Not Sure if this is the same as bug 1747463 Version Log Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 20:05:32 2018 InstallationDate: Installed on 2015-06-11 (1054 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768162/+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 1768211] Re: norton setup
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1768211 Title: norton setup Status in linux package in Ubuntu: Invalid Bug description: Online Norton Help and Support by PC Planet PCPlanet's Certified Technicians can help you scan, detect, and remove all types of viruses and malware in your computer. Our techies have years of experience and the expertise in providing support for antivirus and fixing computer virus problems online through remote connection. Our support services are available through phone, chat and email. Just call us at 1-888-406-4114 to chat with a certified expert and get instant support for Norton Antivirus to make your computer virus free.http://pcplanet247.com/www-norton-com-setup//";>Norton Support Get Started http://pcplanet247.com/www-norton-com-setup//";>Norton Support http://pcplanet247.com/www-norton-com-setup//";>Norton Support 2016 is a version of Norton Setup productivity suite came after Norton 2013. This version is available for PCs (such as Norton Security & 360 2016) and Macs (such as Norton Delux & Premier Edition 2016 for Mac). Along with all the features of previous versions, Norton includes additional ribbon buttons, enhanced collaboration, mentions, new & improved connection options, publish to docs.com, publish to power BI, researcher, suggest a feature, text highlighter, zoom for Norton and staying in the loop. To get Norton 2016, you need to buy, download, install and then activate it. To perform these processes, there is a series of steps that needs to be followed. You can purchase Norton Antivirus setup offline or online. Upon online purchase via norton.com/setup, you will receive a 25-digit product key on your registered email ID. Upon offline purchase, you will receive an Norton retail card, on the back of which this 25-digit key is mentioned. Keep this key secure with you, as you will need it later at the time of Norton subscription activation or while logging in to your account. http://pcplanet247.com/www-norton-com-setup//";>Norton Support http://pcplanet247.com/www-norton-com-setup//";>Norton Support Norton Support NORTON SETUP Visithttp://pcplanet247.com/www-norton-com-setup//";>Norton Support and sign in to your Norton account or create a new account (new users) Enter Norton product key Select your subscription and click download button to begin the downloading process There, you will get the choice to choose from different versions and languages Depending upon your browser, run the downloaded setup Click Run (in Edge or Internet Explorer), Setup (in Chrome), or Save File (in Firefox) After installation, open any of the application of MS Office 2016 Here, you will be see a Norton Antivirus activation wizard Click activate and enter the same product key, if asked Follow the on-screen instructions to complete activation NORTON SETUP FOR MAC First two steps as same with those listed in PC Now, log in to your Norton account and install Norton setup 2016 For this, you have to open My Account and under the name of your subscription, choose Install On the next window, select install under Install information This will begin downloading the installation package Once the download completes, open Finder and go to Downloads Double-click Norton_Setup_2016_Installer.pkg Click continue Review the software license agreement Choose agree to the terms of the software license agreement Select how you want to install the Norton2016 and click continue Change your install location, if you want and then click Install Enter your Mac login password and click Install software Click the Launchpad icon in the dock to display all your applications Click the Norton icon and then click Get Started followed by What’s new This will begin activation process Enter the product key, if asked Follow the on-screen instructions to finish activation It’s good to go! Norton Setup 2016 for Business NORTON SETUP FOR PC Sign in with your work or school account by visiting http://pcplanet247.com/www-norton-com-setup//";>Norton Support From the drop-down list, choose your preferred language and accept the default to install 32-bit or select Advanced and choose 4-bit Choose Install Click Run, Setup or Save file option, depending upon your browser You will be prompted “Do you want to allow this app to make changes to your device?” Click Yes This will begin the installation You’re all set! Activate it and you will be able to access all its applications For Mac Log in with your School or work account at norton setup On the Norton page, select Install option available under Install Norton 2016 for Mac This will begin downloading the installer package Open Finder, go to Do
[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [
[Kernel-packages] [Bug 1768225] Re: SD card not mounted
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1768225 Title: SD card not mounted Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 after fresh install: HW: Macbook Pro Retina 13" SD cards are not recognized nor mounted. The sdhci driver is not loaded by default. Manual loading of sdhci and sdhci-pci does not make the SD card mount or be recognized (loading the driver is acknowledged in the syslog) Adding a configuration file under /etc/modprobe.d with options sdhci debug_quirks2=4 does not remedy the situation. (the cards and adapters tested work fine on other - older - Macs) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 1636 F pulseaudio /dev/snd/controlC1: wolf 1636 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 1 13:05:54 2018 HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d InstallationDate: Installed on 2018-04-30 (1 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 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768225/+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 1767568] Card1.Codecs.codec.1.txt
apport information ** Attachment added: "Card1.Codecs.codec.1.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131545/+files/Card1.Codecs.codec.1.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131549/+files/HookError_generic.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131553/+files/PciMultimedia.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131551/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131554/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131542/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131543/+files/Card0.Codecs.codec.2.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131544/+files/Card1.Codecs.codec.0.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131548/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131550/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Card1.Codecs.codec.2.txt
apport information ** Attachment added: "Card1.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131546/+files/Card1.Codecs.codec.2.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131555/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Card1.Codecs.codec.3.txt
apport information ** Attachment added: "Card1.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131547/+files/Card1.Codecs.codec.3.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131552/+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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+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 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
apport information ** Tags added: apport-collected apport-hook-error ** Description changed: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. - 4) What happened instead is my monitor stays on all the time, without - DPMS controlling it. + 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 + InstallationDate: Installed on 2014-07-23 (1378 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic apport-hook-error + Uname: Linux 4.15.0-20-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: False + dmi.bios.date: 03/11/2010 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F5 + dmi.board.name: X58A-UD5 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: X58A-UD5 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1767568/+attachment/5131541/+files/AlsaDevices.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/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Incomplete Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
The original reporter didn't provide logs...logs would not help. Here's the original text of this issue as reported by NetApp test engineer. Problem report from NetApp: We’re testing Ubuntu 18.04 before its upcoming release this month and have found that the most recent kernel that they have pulled in (4.15.0-15-generic) contains the lpfc driver 12.0.0.0. This driver version seems to have lost support for the LPe16002-M6 adapter but it DOES have support for the LPe16002B-M6 adapter. I’m assuming that you guys are major contributors to your own lpfc driver, so I’m hoping you can shed some light on this one before I have to resort to going out to the community. The previous lpfc version, 11.4.0.1, that was in an Ubuntu 18.04 beta, worked fine on the “non-B” card. Matt Schulte HSG QA Engineer Interoperability E-Series Linux ** Changed in: linux (Ubuntu) Status: Incomplete => New ** 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/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: Confirmed Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+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 1768152] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131515/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768292] Re: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
** Attachment added: "jounalctl -xb output for boot that ended in Emergency Mode" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768292/+attachment/5131495/+files/journalctl-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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x
[Kernel-packages] [Bug 1768152] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131517/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131516/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131513/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131514/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131511/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131512/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131507/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131509/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131510/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768292] 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 1768292 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_p
[Kernel-packages] [Bug 1768152] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131508/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131504/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] Re: Brightness controll doesn't work - Samsung R560
apport information ** Tags added: apport-collected ** Description changed: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: thomas 1205 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-30 (0 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/09/2008 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: 09LA.7027.20081209.JJC + dmi.board.name: R560 + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: + dmi.product.name: R560 + dmi.product.version: Not Applicable + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131503/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight c
[Kernel-packages] [Bug 1768152] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131506/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768152] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1768152/+attachment/5131505/+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/1768152 Title: Brightness controll doesn't work - Samsung R560 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I just migrated from Gentoo Linux to KUbuntu 18.04 LTS. Now I noticed that brightness control doesn't work in Ubuntu (FN Keys show KDE Dialog Brightness changed but display stays at full Backlight). Even writing to /sys/class/backlight/acpi_video0/brightness doesn't change the brightness level. In Gentoo everything was working fine, display backlight responded to KDE and/or to /sys/class/backlight/... . As I now I had a bug Ticket at Kernel org with user Tux12Fun an it was implemented long time ago into the Kernel Main Line. But I can't find the Ticket on Kernel.org now :-( So I try to provide all the information i can collect from the old installation. Hardware: Samsung R560 Laptop Model: NP-R560-AS05DE Gentoo Kernel:linux-4.4.67-gentoo Gentoo Video Driver: original Nvidia 340.106 with Gentoo Kernel Patch nvidia-drivers-381.09-v3.patch Ubuntu Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Video Driver: NVidia 390.42 root@rechner4:/# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 lspci -vvv attached. Kernel Config of my old Gentoo attached. I hope we can mange it to get backlight control working on Ubuntu as it's nearly inpossible to work with full backlight at night :-( Thank you for your work. Best regards form Bavaria Tux12Fun (Thomas) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1205 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. R560 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ca20d22-7baa-4892-a8a3-cd0e628190bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09LA.7027.20081209.JJC dmi.board.name: R560 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09LA.7027.20081209.JJC:bd12/09/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR560:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR560:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R560 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768152/+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 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
** Summary changed: - Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 + Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 -- 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/1768292 Title: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0980 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x49
[Kernel-packages] [Bug 1768292] [NEW] Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980
Public bug reported: Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop. Sometimes, at boot, the system goes into Emergency Mode. In looking at journalctl -xb output, the following messages are logged: May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri Kosina May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI initialized, starting thunderbolt May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX ring 0 of size 10 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel created May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel starting... May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX ring 0 May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM firmware May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer dereference at 0980 May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0 May 01 10:05:04 galvin-T570 kernel: Oops: [#1] SMP PTI May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core thunderbolt(+) wmi i2c_hid hid video May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not tainted 4.15.0-20-generic #21-Ubuntu May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017 May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30 May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 00010296 May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: RCX: 0050 May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 0034 RDI: May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 0200 R09: 0320 May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: R12: May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 91b2efc5bb30 R15: May 01 10:05:04 galvin-T570 kernel: FS: 7f4a6cf70680() GS:91b31f58() knlGS: May 01 10:05:04 galvin-T570 kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 00082f944005 CR4: 003606e0 May 01 10:05:04 galvin-T570 kernel: DR0: DR1: DR2: May 01 10:05:04 galvin-T570 kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:05:04 galvin-T570 kernel: Call Trace: May 01 10:05:04 galvin-T570 kernel: ? pcie2cio_write+0x40/0x80 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: icm_driver_ready+0x1ad/0x2b0 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: ? tb_ctl_start+0x50/0x90 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: tb_domain_add+0x79/0x100 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: nhi_probe+0x186/0x300 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: local_pci_probe+0x47/0xa0 May 01 10:05:04 galvin-T570 kernel: pci_device_probe+0x145/0x1b0 May 01 10:05:04 galvin-T570 kernel: driver_probe_device+0x31e/0x490 May 01 10:05:04 galvin-T570 kernel: __driver_attach+0xa7/0xf0 May 01 10:05:04 galvin-T570 kernel: ? driver_probe_device+0x490/0x490 May 01 10:05:04 galvin-T570 kernel: bus_for_each_dev+0x70/0xc0 May 01 10:05:04 galvin-T570 kernel: driver_attach+0x1e/0x20 May 01 10:05:04 galvin-T570 kernel: bus_add_driver+0x1c7/0x270 May 01 10:05:04 galvin-T570 kernel: ? 0xc028c000 May 01 10:05:04 galvin-T570 kernel: driver_register+0x60/0xe0 May 01 10:05:04 galvin-T570 kernel: ? 0xc028c000 May 01 10:05:04 galvin-T570 kernel: __pci_register_driver+0x5a/0x60 May 01 10:05:04 galvin-T570 kernel: nhi_init+0x2d/0x1000 [thunderbolt] May 01 10:05:04 galvin-T570 kernel: do_one_initcall+0x52/0x19f May 01 10:05:04 galvin-T570 kernel: ? _cond_resched+0x19/0x40 May 01 10:05:04 galvin-T570 kernel: ? kmem_cache_alloc_trace+0
[Kernel-packages] [Bug 1764975] Re: test_078_SLAB_freelist_randomization failed on 4.15 KVM kernel
** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1764975 Title: test_078_SLAB_freelist_randomization failed on 4.15 KVM kernel Status in QA Regression Testing: Invalid Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Fix Committed Bug description: test_078_SLAB_freelist_randomization from ubuntu_qrt_kernel_security_test has failed with 4.15.0-1004-kvm FAIL: test_078_SLAB_freelist_randomization (__main__.KernelSecurityTest) Ensure CONFIG_SLAB_FREELIST_RANDOM is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 936, in test_078_SLAB_freelist_randomization self.assertTrue(self._test_config('SLAB_FREELIST_RANDOM'), ) AssertionError: False is not true ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Wed Apr 18 08:41:24 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1764975/+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 1763630] Re: Unable to start docker application with B-KVM kernel
** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1763630 Title: Unable to start docker application with B-KVM kernel Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Bug description: Similar to bug 1760660, docker.io package installation on B-KVM will fail with: Setting up docker.io (17.03.2-0ubuntu5) ... Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-04-13 08:42:36 UTC; 10ms ago Docs: https://docs.docker.com Process: 1265 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 1265 (code=exited, status=1/FAILURE) Apr 13 08:42:36 gummo dockerd[1265]: time="2018-04-13T08:42:36.052983563Z" level=warning msg="Running modprobe nf_nat failed with message: `modprobe: WARNING: Module nf_nat not found in directory /lib/modules/4.15.0-1003-kvm`, error: exit status 1" Apr 13 08:42:36 gummo dockerd[1265]: time="2018-04-13T08:42:36.055137401Z" level=warning msg="Running modprobe xt_conntrack failed with message: `modprobe: WARNING: Module xt_conntrack not found in directory /lib/modules/4.15.0-1003-kvm`, error: exit status 1" Apr 13 08:42:36 gummo dockerd[1265]: time="2018-04-13T08:42:36.058241707Z" level=info msg="Firewalld running: false" Apr 13 08:42:36 gummo dockerd[1265]: Error starting daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain: iptables failed: iptables -t nat -N DOCKER: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/4.15.0-1003-kvm Apr 13 08:42:36 gummo dockerd[1265]: iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Apr 13 08:42:36 gummo dockerd[1265]: Perhaps iptables or your kernel needs to be upgraded. Apr 13 08:42:36 gummo dockerd[1265]: (exit status 3) Apr 13 08:42:36 gummo systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Apr 13 08:42:36 gummo systemd[1]: docker.service: Failed with result 'exit-code'. Apr 13 08:42:36 gummo systemd[1]: Failed to start Docker Application Container Engine. Maybe we need the same patch for Bionic KVM kernel as well: kvm: [config] enable all CGROUPs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 08:43:06 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1763630/+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 1764985] Re: linux-kvm 4.15 needs CONFIG_VMAP_STACK set
** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1764985 Title: linux-kvm 4.15 needs CONFIG_VMAP_STACK set Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Fix Committed Bug description: test_181_config_vmap_stack in ubuntu_qrt_kernel_security_test has failed with 4.15.0-1004-kvm FAIL: test_181_config_vmap_stack (__main__.KernelSecurityTest) Ensure kernel stack isolation is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2149, in test_181_config_vmap_stack self.assertEqual(self._get_config('VMAP_STACK'), expected) AssertionError: None != 'y' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Wed Apr 18 09:29:03 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1764985/+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 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
Hello John, or anyone else affected, Accepted s390-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/1.34.0-0ubuntu8.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: s390-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: ubuntu-release-upgrader (Ubuntu Xenial) Status: New => 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/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: Fix Committed Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_R
[Kernel-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
** Description changed: + [Impact] + Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. + + [Test Case] + Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. + + [Regression] + zipl update on s390x might fail, causing the system to be unbootable. + + Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): - installed initramfs-tools package post-installation script subprocess returned error exit status 1 + installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: - initramfs-tools + initramfs-tools Log ended: 2018-04-24 13:12:40 - --- + --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. + + Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img