[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] AMD MP2 I2C driver doesn't support more than one bus. This makes touchpad on Lenovo Yoga 530 doensn't work as expected. [Fix] Sync the MP2 driver with upstream version. [Test] The new upstream driver doesn't break on Latitude 5495. Users haven't given any feedback yet, but since Disco is freezing I am sending this out. [Regression Potential] Low. It's from upstream, and only a subset of Raven Ridge has this device. === Original Bug Report === The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Eoan) Importance: High Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 source package in Eoan: Triaged Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Added to the description what we need from anyone affected. @Maas Team see former comment for the requested guiding of users how to get this data. The Maas task is back from incomplete to confirmed for providing these howto's ** Changed in: maas 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Confirmed Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
@sfeole Thanks for the Dup hit that as well now - as all others I ask you to please help to catch the data needed to finally recreate and debug this. >From IRC: [07:00] sfeole: please attach your guest XML, and the used initrd and kernel to the bug [07:02] best would be also the pxeconfig that is provided @MAAS Team So far this only occurred with MAAS and all other tries to recreate worked. I wonder if either TFTP or the PXE loader used could be the trigger of the bug. Therefore (from IRC as well): [07:02] roaksoax: on this bug one of the components we still have to verify if it is related is the way you provide the TFP [07:02] could you outline on the bug how users once they hit the bug could extract that and attach it to the bug [07:03] that way we can hopefully finally recreate the case I tried so back in comment #31, but that was only trying to recreate your setup. For PXEconfig (I was guessing) and TFTP (I used the normal tftpd package) we could still get more similar to your setup. I'll add a section to the description of the bug what users are supposed to attach, it would be great if you could help to outline how users can get those. @MAAS Team [07:03] and IIRC you don't use tftpd or such but something maas internal for tftpd is that right - could you outline how one could use/setup this so that we can compare tftpd vs maas-tftpd as well? That is an extra question to that above, if you could help here as well that would be great. ** Description changed: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. + + + So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. + + If you are affected, please attach to the bug + - the kernel used to boot the guest + - the initrd used to boot the guest + - libvirt guest XML used to define the guest + - PXE config provided to the guest + - the cloud image used to start the guest (That will likely not fit as bug + attachment, consider storing it somewhere and contact us) + + TODO: The Maas Team will outline how to get all these artifacts. + TODO: add reference to the comment outlining this (once added) -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Confirmed Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1813129] Re: tm-unavailable in powerpc/tm failed on Bionic Power9
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1813129 Title: tm-unavailable in powerpc/tm failed on Bionic Power9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == Justification == The tm-unavailable test in powerpc from ubuntu_kernel_selftests will fail on Bionic PowerPC: $ sudo ./tm-unavailable Checking if FP/VEC registers are sane after a FP unavailable exception... Illegal instruction This is because the Hardware Transactional Memory (HTM) is not supported on the revision of the processor in our PowerPC boxes. == Fix == b395e55b (selftests/powerpc: Skip tm-unavailable if TM is not enabled) With a prerequisite to make it a clean cherry-pick: 5783ee6e (selftests/powerpc: Check for pthread errors in tm-unavailable) An extra check for this test: SKIP_IF(!have_htm()) Will be added to ensure we have HTM support before start testing. This patchset has already landed in Cosmic and newer, and can be cherry-picked for Bionic. For Xenial, we don't have this test in our tree. == Test == Patch verified on a Bionic P9 system, the test will be marked as passed (skipped) with these two patches applied. == Regression potential == None. This patch is just for the kernel testing tool. == Original Bug Report == $ sudo ./tm-unavailable Checking if FP/VEC registers are sane after a FP unavailable exception... Illegal instruction For Power8 it's OK: For P9 on Cosmic, this test will be skipped: selftests: tm: tm-unavailable test: tm_unavailable_test tags: git_version:unknown skip: tm_unavailable_test ok 1..10 selftests: tm: tm-unavailable [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 07:22 seq crw-rw 1 root audio 116, 33 Jan 24 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 24 08:46:56 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.15 0.10 1.47 1/1357 32937 ProcLocks: 1: FLOCK ADVISORY WRITE 3482 00:17:520 0 EOF 2: POSIX ADVISORY WRITE 3746 00:17:580 0 EOF 3: POSIX ADVISORY WRITE 1800 00:17:368 0 EOF 4: FLOCK ADVISORY WRITE 3744 00:17:568 0 EOF 5: POSIX ADVISORY WRITE 3831 00:17:588 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 5 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 3) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813129/+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 1813134] Re: cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed on Bionic P9
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1813134 Title: cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed on Bionic P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == Justification == The cp_abort test in context_switch was designed for Power9, however this test is broken and it fails everytime as Paste on Power9 only works on accelerators and no longer on real memory. == Fix == 00c946a0 (selftests/powerpc: Remove redundant cp_abort test) This will remove the cp_abort test. Patch has already been applied in C and onward. == Test == Patch verified on a Bionic P9 system, the test will no longer exist. == Regression Potential == None. This patchset is just for the kernel testing tool. == Original Bug Report == This issue can only be reproduced on Power9 with Bionic kernel. $ sudo ./cp_abort test: cp_abort tags: git_version:c186097-dirty !! killing cp_abort !! child died by signal 15 failure: cp_abort It will get skipped on P8 Also to note that this test was completely removed in Cosmic with commit 00c946a06e ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 07:22 seq crw-rw 1 root audio 116, 33 Jan 24 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 24 09:06:32 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.07 0.03 0.42 1/1360 33961 ProcLocks: 1: FLOCK ADVISORY WRITE 3482 00:17:520 0 EOF 2: POSIX ADVISORY WRITE 3746 00:17:580 0 EOF 3: POSIX ADVISORY WRITE 1800 00:17:368 0 EOF 4: FLOCK ADVISORY WRITE 3744 00:17:568 0 EOF 5: POSIX ADVISORY WRITE 3831 00:17:588 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 5 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.863 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813134/+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 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822871 Title: enabling ftrace on Hi1620 CS causes an Oops Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [Impact] Attempting to enable the function tracer causes an Oops. This impacts the current disco kernel, as well as latest upstream (@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539). This is 100% reproducible on D06 CS systems, but not reproducible on D06 ES systems (the previous silicon rev). [Test Case] $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325! [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12 [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 2280-A CS V2.16.01 03/16/2019 [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO) [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80 [ 3125.766979] sp : 2837b9f0 [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880 [ 3125.775591] x27: x26: [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000 [ 3125.786200] x23: 0002 x22: 3dce9d2289a4 [ 3125.791504] x21: 2837ba8c x20: 2837b000 [ 3125.796808] x19: 3dce9d228000 x18: [ 3125.802112] x17: x16: 3dceb7742780 [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001 [ 3125.812720] x13: bef50bb9e188 x12: [ 3125.818023] x11: 7efba3e79608 x10: 0a70 [ 3125.823327] x9 : 3dceb6deeacc x8 : [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10 [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8 [ 3125.839239] x3 : x2 : 9000 [ 3125.844543] x1 : x0 : [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476) [ 3125.856281] Call trace: [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38 [ 3125.863593] plt_entries_equal.part.3+0x40/0x80 [ 3125.868115] plt_entries_equal+0x5c/0x70 [ 3125.872031] ftrace_make_call+0xf0/0x150 [ 3125.875950] __ftrace_replace_code+0xe8/0xf8 [ 3125.880212] ftrace_replace_code+0x64/0xc0 [ 3125.884301] ftrace_modify_all_code+0xb0/0x148 [ 3125.888738] arch_ftrace_update_code+0x10/0x18 [ 3125.893174] ftrace_run_update_code+0x20/0x70 [ 3125.897524] ftrace_startup_enable+0x4c/0x58 [ 3125.901788] ftrace_startup+0xa4/0x140 [ 3125.905531] register_ftrace_function+0x64/0x80 [ 3125.910059] function_trace_init+0x50/0x98 [ 3125.914149] tracing_set_tracer+0xf4/0x1c0 [ 3125.918238] tracing_set_trace_write+0x10c/0x168 [ 3125.922852] __vfs_write+0x60/0x1a8 [ 3125.926333] vfs_write+0xac/0x1b8 [ 3125.929641] ksys_write+0x6c/0xd8 [ 3125.932949] __arm64_sys_write+0x24/0x30 [ 3125.936866] el0_svc_common+0x78/0x120 [ 3125.940608] el0_svc_handler+0x38/0x78 [ 3125.944349] el0_svc+0x8/0xc [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421) [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]--- [Fix] 4e69ecf4da1ee arm64/module: ftrace: deal with place relative nature of PLTs 5a3ae7b314a22 arm64/ftrace: fix inadvertent BUG() in trampoline check [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+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 1827880] Re: bionic/linux: completely remove snapdragon files from sources
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1827880 Title: bionic/linux: completely remove snapdragon files from sources Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] As requested by bug 1820868, we have split bionic/linux-snapdragon to its own source package and own git branch for better maintainability. Functionally that split was complete, however some leftover files where not removed from the sources leaving some dead files on the tree. [Fix] Sauce patch to remove all the files that were previously used to produce the snapdragon binaries from the linux master source. [Test Case] Compile test bionic/linux source and verify that nothing breaks. [Regression potential] Minimum. The fix is to remove files that are not being used anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827880/+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 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827972 Title: The noise keeps occurring when Headset is plugged in on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Steps to reproduce: 1. Plug in headset 2. Select Headset mode Expected result: There is no noise when headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827972/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
I have been running into this (curtin 18.1-17-gae48e86f-
0ubuntu1~16.04.1)
I think this commit basically agrees with my thoughts but I just wanted
to share them explicitly in case they are interesting
(1) If you *unregister* the cache device from the backing device, it
first has to purge all the dirty data back to the backing device. This
may obviously take a while.
(2) When doing that, I managed to deadlock bcache at least once on
xenial-hwe 4.15 where it was trying to reclaim memory from XFS, which I
assume was trying to write to the bcache.. traceback:
https://pastebin.canonical.com/117528/ - you can't get out of that
without a reboot
(3) However generally I had good luck simplying "stop"ing the cache
devices (it seems perhaps that is what this bug is designed to do,
switch to stop, instead of unregister?). Specifically though I was
stopping the backing devices, and then later the cache device. It seems
like the current commit is the other way around?
** Tags added: sts
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1794232] Re: Geneve tunnels don't work when ipv6 is disabled
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794232 Title: Geneve tunnels don't work when ipv6 is disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically. Fix: Fixed by upstream commit in v5.0: Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 "geneve: correctly handle ipv6.disable module parameter" Hence available in Disco and later; required in X,B,C. Testcase: 1. Boot with "ipv6.disable=1" 2. Then try and create a geneve tunnel using: # ovs-vsctl add-br br1 # ovs-vsctl add-port br1 geneve1 -- set interface geneve1 type=geneve options:remote_ip=192.168.x.z // ip of the other host Regression Potential: Low, only geneve tunnels when ipv6 dynamically disabled, current status is it doesn't work at all. Other Info: * Mainline commit msg includes reference to a fix for non-metadata tunnels (infrastructure is not yet in our tree prior to Disco), hence not being included at this time under this case. At this time, all geneve tunnels created as above are metadata-enabled. --- [Impact] When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in an OS environment with open vswitch, where ipv6 has been disabled, the create fails with the error : “ovs-vsctl: Error detected while setting up 'geneve0': could not add network device geneve0 to ofproto (Address family not supported by protocol)." [Fix] There is an upstream commit for this in v5.0 mainline (and in Disco and later Ubuntu kernels). "geneve: correctly handle ipv6.disable module parameter" Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 This fix is needed on all our series prior to Disco and the v5.0 kernel: X, C, B. It is identical to the fix we implemented and tested internally with, but had not pushed upstream yet. [Test Case] (Best to do this on a kvm guest VM so as not to interfere with your system's networking) 1. On any Ubuntu Xenial kernel, disable ipv6. This example is shown with the 4.15.0-23-generic kernel (which differs slightly from 4.4.x in symptoms): - Edit /etc/default/grub to add the line: GRUB_CMDLINE_LINUX="ipv6.disable=1" - # update-grub - Reboot 2. Install OVS # apt install openvswitch-switch 3. Create a Geneve tunnel # ovs-vsctl add-br br1 # ovs-vsctl add-port br1 geneve1 -- set interface geneve1 type=geneve options:remote_ip=192.168.x.z (where remote_ip is the IP of the other host) You will see the following error message: "ovs-vsctl: Error detected while setting up 'geneve1'. See ovs-vswitchd log for details." From /var/log/openvswitch/ovs-vswitchd.log you will see: "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system: failed to add geneve1 as port: Address family not supported by protocol" You will notice from the "ifconfig" output that the device genev_sys_6081 is not created. If you do not disable IPv6 (remove ipv6.disable=1 from /etc/default/grub + update-grub + reboot), the same 'ovs-vsctl add-port' command completes successfully. You can see that it is working properly by adding an IP to the br1 and pinging each host. On kernel 4.4 (4.4.0-128-generic), the error message doesn't happen using the 'ovs-vsctl add-port' command, no warning is shown in ovs-vswitchd.log, but the device genev_sys_6081 is also not created and ping test won't work. With the fixed test kernel, the interfaces and tunnel is created successfully. [Regression Potential] * Low -- affects the geneve driver only, and when ipv6 is disabled, and since it doesn't work in that case at all, this fix gets the tunnel up and running for the common case. [Other Info] * Analysis Geneve tunnels should work with either IPv4 or IPv6 environments as a design and support principle. Currently, however, what's in the implementation requires support for ipv6 for metadata-based tunnels which geneve is: rather than: a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled b) ipv4 + metadata + ipv6 What enforces this in the current 4.4.0-x code when opening a Geneve tunnel is the following in geneve_open() : bool ipv6 = geneve->remote.sa.sa_family == AF_INET6; bool metadata = geneve->collect_md; ... #if IS_ENABLED(CONFIG_IPV6) geneve->sock6 = NULL;
[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap
Cosmic VM with proposed kernel withstand the stress for over 12 hours. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1814874 Title: NULL pointer dereference when using z3fold and zswap Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == When using z3fold and zswap on a VM under overcommitted memory stress, z3fold will complains about an "unknown buddy id 0" and fail to get a pointer to the mapped allocation in z3fold_map(). z3fold: unknown buddy id 0 WARNING: CPU: 2 PID: 1584 at mm/z3fold.c:971 z3fold_zpool_map+0xce/0x100 [z3fold] And it will leads to a null pointer dereference in zswap BUG: unable to handle kernel NULL pointer dereference at PGD 0 P4D 0 Oops: [#1] SMP PTI CPU: 2 PID: 1584 Comm: stress Tainted: GW 4.18.0-17-generic #18-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 RIP: 0010:zswap_writeback_entry+0x4d/0x360 == Fix == ca0246bb (z3fold: fix possible reclaim races) This patch has already in Disco, and can be cherry-picked into B/C. Not needed for Xenial and older kernels as z3fold is not supported. == Test == Test kernels for Bionic / Cosmic could be found here: http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Bionic/ http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/ This issue can be reproduced easily in a KVM with the following setup: * 8G disk, 4G RAM, 4 CPUs * 1G swap * "zswap.enabled=1 zswap.zpool=z3fold zswap.max_pool_percent=7" added to grub * "z3fold" module added into /etc/initramfs-tools/modules Stress it with two childs running: * stress --vm-bytes 512M --vm 4 --vm-hang 3 * stress --vm-bytes 512M --vm 4 --vm-hang 7 The VM is expected to crash within 5 minutes. With the patched kernel, the VM can withstand this stress for over an hour with crashing with this issue == Regression potential == Small. Fix limited to z3fold. User needs to enable it explicitly for this feature. == Original Bug Report == Under memory pressure, my VM locks up. This has been reported upstream though I don't know how far any solution has progressed. https://bugzilla.kernel.org/show_bug.cgi?id=201603 Feb 6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0 Feb 6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle kernel NULL pointer dereference at 0008 The little bit of log I managed to salvage is attached. This has happened to two identical VMs. Unusually it has not occurred on a third VM which is configured the same but has less RAM (fingers crossed it won't). Irrelevant information: I thought the lock-ups were due to me using a BTRFS filesystem, however I swapped over to NILFS2 and this still occurs. The only difference seems to be that I am now able to grab some of the kernel output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:55:05 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1814874/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Yeah, kernel bugs have a slightly different process regarding "Confirmed". ** 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828133] Re: Intel CyclonePeak wifi firmware
** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828133 Title: Intel CyclonePeak wifi firmware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] To avoid conflicts, also update 9000 series firmware to ABI 46 which has been added since v5.1-rc1 from iwlwifi tree[1] for-upstream branch 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares fdfb1531 iwlwifi: add -46.ucode firmwares for 9000 series 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git [Test Case] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] Low. Those firmware are for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads those firmware. [Misc] Can't apply the same patchset on Cosmic, and taking into account that Cosmic is going to EoL on July, so skip Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828133/+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 1828133] Re: Intel CyclonePeak wifi firmware
** Tags added: originate-from-1810708 somerville ** Description changed: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] - To avoid conflicts, also update 9000 series firmware to ABI 46 which has been added since v5.1-rc1 from iwlwifi/for-upstream - 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series - 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares - fdfb1531 iwlwifi: add -46.ucode firmwares for 9000 series + To avoid conflicts, also update 9000 series firmware to ABI 46 which has been added since v5.1-rc1 from iwlwifi tree[1] for-upstream branch +95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series +68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares +fdfb1531 iwlwifi: add -46.ucode firmwares for 9000 series + + 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- + firmware.git [Test Case] - Verified on AX200NGW & 22560NGW chips, wifi works well. + Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] - Low. Those firmware are for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver loads those firmware. + Low. Those firmware are for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads those firmware. [Misc] Can't apply the same patchset on Cosmic, and taking into account that Cosmic is going to EoL on July, so skip Cosmic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828133 Title: Intel CyclonePeak wifi firmware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] To avoid conflicts, also update 9000 series firmware to ABI 46 which has been added since v5.1-rc1 from iwlwifi tree[1] for-upstream branch 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares fdfb1531 iwlwifi: add -46.ucode firmwares for 9000 series 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git [Test Case] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] Low. Those firmware are for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads those firmware. [Misc] Can't apply the same patchset on Cosmic, and taking into account that Cosmic is going to EoL on July, so skip Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828133/+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 1828283] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828283 Title: After using my computer for a while the wifi refuses to work Status in linux package in Ubuntu: Confirmed Bug description: After using my computer (op sys Ubuntu 16.04.6 LTS) for a while the wi-fi refuses to work. Apps and programs run fine, just no wi-fi. After I open the System Settings menu and try to click on Network the whole window grays out and stops responding and the whole system crashes. If I try to reboot the computer it does reboot but after a considerable amount of time. Meanwhile, I get a black screen and the message "[75873.475364] BUG: unable to handle kernel paging request at c9d6e808" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 8 17:59:04 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-142-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-145-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-146-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-145-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-146-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:083f] Subsystem: Dell Jet PRO [Radeon R5 M230] [1028:083f] InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=6d8b6200-17f0-42e3-949a-5bfcbc310569 ro acpi_rev_override locale=C alx.enable_wol=1 mem_sleep_default=deep splash quiet SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0J11DH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0J11DH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 3576 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 8 17:48:12 2019 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1680 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.8 To
[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
I ran the "apport-collect 1828136" command as directed by the automated script. A little puzzled that it gave the message dpkg-query: no packages found matching alsa-driver dpkg-query: no packages found matching linux -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262474/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262482/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
The automated script said I should change the status to "confirmed" even though I am the reporter. When 18.10 came out some other people reported similar issues: https://ubuntuforums.org/showthread.php?t=2403077 https://ubuntuforums.org/showthread.php?t=2405764 -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262472/+files/AudioDevicesInUse.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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262478/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262473/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262475/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262479/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262480/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262481/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262477/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262476/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
apport information ** Tags added: apport-collected ** Description changed: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + DistroRelease: Ubuntu 19.04 + HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a + InstallationDate: Installed on 2014-04-19 (1845 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/tcsh + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + RfKill: + + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 12/04/2012 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: DH67CL + dmi.board.vendor: Intel Corporation + dmi.board.version: AAG10212-203 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1828136/+attachment/5262471/+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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date:
[Kernel-packages] [Bug 1828136] 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 1828136 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828066] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828066 Title: ubuntu19.04 can not receive key input in virtualbox fullscreen mode Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I install ubuntu19.04 in virtualbox6.0, virtualbox runs in linux, If I switch to fullScreen mode ubuntu19.04 can not receive key input anymore. I tried a lot of linux distribution, both have this bug. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1636 F pulseaudio /dev/snd/controlC0: widon 1636 F pulseaudio BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: disco DistroRelease: Ubuntu 19.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mullins [Radeon R4/R5 Graphics] [1043:1b9d] Subsystem: ASUSTeK Computer Inc. Jet PRO [Radeon R5 M230] [1043:226d] InstallationDate: Installed on 2019-05-01 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X555YI Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=21dde348-df07-402f-b864-625b26407472 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco ubuntu Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1828066/+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 1828283] Re: After using my computer for a while the wifi refuses to work
The only relevant problem I can see in the above logs is: [ 174.789693] pcieport :00:1c.5: AER: Corrected error received: id=00e5 [ 174.789747] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) [ 174.789754] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 174.789758] pcieport :00:1c.5:[ 0] Receiver Error [ 231.552097] pcieport :00:1c.5: AER: Corrected error received: id=00e5 [ 231.552120] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) [ 231.552131] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 231.552139] pcieport :00:1c.5:[ 0] Receiver Error That device (1c.5) is the "Intel Corporation Sunrise Point-LP PCI Express Root Port #6". In my experience this can indicate a faulty wifi card, faulty slot, faulty motherboard, or just a kernel bug. ** Summary changed: - Kernel Failure (that's what it says) + After using my computer for a while the wifi refuses to work ** Package changed: xorg (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/1828283 Title: After using my computer for a while the wifi refuses to work Status in linux package in Ubuntu: New Bug description: After using my computer (op sys Ubuntu 16.04.6 LTS) for a while the wi-fi refuses to work. Apps and programs run fine, just no wi-fi. After I open the System Settings menu and try to click on Network the whole window grays out and stops responding and the whole system crashes. If I try to reboot the computer it does reboot but after a considerable amount of time. Meanwhile, I get a black screen and the message "[75873.475364] BUG: unable to handle kernel paging request at c9d6e808" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 8 17:59:04 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-142-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-145-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-146-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-145-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-146-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:083f] Subsystem: Dell Jet PRO [Radeon R5 M230] [1028:083f] InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=6d8b6200-17f0-42e3-949a-5bfcbc310569 ro acpi_rev_override locale=C alx.enable_wol=1 mem_sleep_default=deep splash quiet SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0J11DH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0J11DH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 3576 dmi.sys.vendor: Dell Inc. version.compiz: compiz
[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Sorry, yes, while that problem is shown in the attached files it does sound irrelevant now. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New ** 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828283] [NEW] After using my computer for a while the wifi refuses to work
You have been subscribed to a public bug: After using my computer (op sys Ubuntu 16.04.6 LTS) for a while the wi- fi refuses to work. Apps and programs run fine, just no wi-fi. After I open the System Settings menu and try to click on Network the whole window grays out and stops responding and the whole system crashes. If I try to reboot the computer it does reboot but after a considerable amount of time. Meanwhile, I get a black screen and the message "[75873.475364] BUG: unable to handle kernel paging request at c9d6e808" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 8 17:59:04 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-142-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-145-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-146-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-145-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-146-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:083f] Subsystem: Dell Jet PRO [Radeon R5 M230] [1028:083f] InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=6d8b6200-17f0-42e3-949a-5bfcbc310569 ro acpi_rev_override locale=C alx.enable_wol=1 mem_sleep_default=deep splash quiet SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0J11DH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0J11DH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 3576 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 8 17:48:12 2019 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1680 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 failure freeze kernel ubuntu xenial -- After using my computer for a while the wifi refuses to work https://bugs.launchpad.net/bugs/1828283 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
[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Added a kernel task because our kernel engineers are experts at such ALSA issues. And often the solution lies in the kernel. -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828066] Re: ubuntu19.04 can not receive key input in virtualbox fullscreen mode
** Changed in: libinput (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1828066 Title: ubuntu19.04 can not receive key input in virtualbox fullscreen mode Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I install ubuntu19.04 in virtualbox6.0, virtualbox runs in linux, If I switch to fullScreen mode ubuntu19.04 can not receive key input anymore. I tried a lot of linux distribution, both have this bug. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 1636 F pulseaudio /dev/snd/controlC0: widon 1636 F pulseaudio BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: disco DistroRelease: Ubuntu 19.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mullins [Radeon R4/R5 Graphics] [1043:1b9d] Subsystem: ASUSTeK Computer Inc. Jet PRO [Radeon R5 M230] [1043:226d] InstallationDate: Installed on 2019-05-01 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X555YI Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=21dde348-df07-402f-b864-625b26407472 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco ubuntu Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1828066/+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 1579410] Re: Cannot suspend HP ProLiant SE316M1R2
** Changed in: linux (Ubuntu) Importance: Medium => Wishlist -- 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/1579410 Title: Cannot suspend HP ProLiant SE316M1R2 Status in linux package in Ubuntu: Won't Fix Bug description: pm-suspend does not work on HP ProLiant SE316M1R2 system. I am not sure if hardware actually supports that though, but there is kernel crash (see syslog.txt attached with Call Trace) which maybe is the cause. Monitor goes off for few seconds but after that system resumes and works as before. Also, some interesting lines: May 7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38 May 7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): pci_pm_freeze+0x0/0xe0 returns -38 May 7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 failed to freeze async: error -38s2disks These lines also appears when using s2disk. s2ram gives: KMS graphics driver is in use, skipping quirks. s2ram_do: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.21.22 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sat May 7 20:55:52 2016 HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3 InstallationDate: Installed on 2015-10-12 (208 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant SE316M1R2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago) dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1R2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579410/+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 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
Selwyn, to clarify, have you tested the commit noted in #31 with your hardware and confirmed it fixes the issue? ** Tags added: disco -- 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/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Incomplete Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. Workaround: use kernel 4.19.4. Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 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/1812561/+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 1828168] Re: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro
PaulSchulz, thank you for reporting this and helping make Ubuntu better. In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following: 1) The one to test is in a folder at the very top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the issue is reproducible with the mainline kernel, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed. Thank you for your help. ** Tags added: bios-outdated-38.16.85.0 ** Summary changed: - Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro + [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work ** Description changed: - Original bug here: https://bugs.launchpad.net/bugs/1449438 - - This bug was created with - ubuntu-bug linux - ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: paul 2763 F pulseaudio - /dev/snd/controlC1: paul 2763 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: paul 2763 F pulseaudio + /dev/snd/controlC1: paul 2763 F pulseaudio Date: Wed May 8 16:35:11 2019 InstallationDate: Installed on 2018-01-13 (480 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface Pro 3 ProcEnviron: - LANGUAGE=en_AU:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=2aaa6b5c-4cbb-4d78-92b5-b8f96f30eb4f 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. RelatedPackageVersions: - linux-restricted-modules-5.0.0-13-generic N/A - linux-backports-modules-5.0.0-13-generic N/A - linux-firmware1.178 + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-23 (14 days ago) dmi.bios.date: 06/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2550 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2550:bd06/12/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.sku: Surface_Pro_3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux
[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep
Gioele Barabucci, instructions for testing the latest mainline kernel are available via https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/comments/18 . ** 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/1792672 Title: Regression: acpi reports battery state incorrectly after sleep Status in linux package in Ubuntu: Incomplete Bug description: On Samsung Series 9 laptops the battery state and the charger status are incorrectly reported in kernel 4.15. This bug is a regression: it has been fixed in 2012 [1] it used to work fine until Linux 14.10 (included). Quoting Matthew McCallum from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161 > If I disconnect power, remove the back cover, disconnect both the main battery and the backup battery, I am able to get power status updates (e.g. battery will show as charging/charged when plugged in, or just regular battery when not). Once I sleep, I have to repeat this process if I want the battery status to work again. > > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gioele 1939 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029 InstallationDate: Installed on 2017-06-24 (447 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3D-A03IT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/+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 1828134] Re: Wifi not working after suspend/resume cycle
Hi Andrea -- Thanks for the suggestion. I attempted this and it seems to not help. The first suspend/resume worked, and I was hopeful, but after 4 more attempts (obviously I have reboots in between each failed attempt), it didn't prove to be a solid option. FYI, so far the comment I made in #3 still holds true -- 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/1828134 Title: Wifi not working after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+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 1824812] Re: apparmor does not start in Disco LXD containers
** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1824812 Title: apparmor does not start in Disco LXD containers Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: In LXD apparmor now skips starting. Steps to reproduce: 1. start LXD container $ lxc launch ubuntu-daily:d d-testapparmor (disco to trigger the issue, cosmic as reference) 2. check the default profiles loaded $ aa-status => This will in cosmic and up to recently disco list plenty of profiles active even in the default install. Cosmic: 25 profiles are loaded. 25 profiles are in enforce mode. Disco: 15 profiles are loaded. 15 profiles are in enforce mode. All those 15 remaining are from snaps. The service of apparmor.service actually states that it refuses to start. $ systemctl status apparmor ... Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor in container I can get those profiles (the default installed ones) loaded, for example: $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient makes it appear 22 profiles are in enforce mode. /sbin/dhclient I was wondering as in my case I found my guest with no (=0) profiles loaded. But as shown above after "apparmor_parser -r" and package install profiles seemed fine. Then the puzzle was solved, on package install they will call apparmor_parser via the dh_apparmor snippet and it is fine. To fully disable all of them: $ lxc stop $ lxc start $ lxc exec d-testapparmor aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. That would match the service doing an early exit as shown in systemctl status output above. The package install or manual load works, but none are loaded by the service automatically e.g. on container restart. --- --- --- This bug started as: Migrations to Disco trigger "Unable to find security driver for model apparmor" This most likely is related to my KVM-in-LXD setup but it worked fine for years and I'd like to sort out what broke. I have migrated to Disco's qemu 3.1 already which makes me doubts generic issues in qemu 3.1 in general. The virt tests that run cross release work fine starting from X/B/C but all those chains fail at mirgating to Disco now with: $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live kvmguest-bionic-normal qemu+ssh://10.21.151.207/system error: unsupported configuration: Unable to find security driver for model apparmor I need to analyze what changed To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824812/+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 1828302] Re: CSR Bluetooth driver: Insufficient performance compared to WIndows driver
Looks a lot like an issue that occurs only on my ryzen desktop, and not on my Intel laptop, any ideas? -- 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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luky 1581 F pulseaudio /dev/snd/controlC1: luky 1581 F pulseaudio /dev/snd/pcmC1D0c: luky 1581 F...m pulseaudio /dev/snd/controlC2: luky 1581 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-07 (1 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: 3: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1792100] Re: Boot hangs at "loading initial ramdisk..."
** Also affects: linux 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/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1792100/+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 1828302] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1828302/+attachment/5262459/+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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luky 1581 F pulseaudio /dev/snd/controlC1: luky 1581 F pulseaudio /dev/snd/pcmC1D0c: luky 1581 F...m pulseaudio /dev/snd/controlC2: luky 1581 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-07 (1 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: 3: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1828302] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1828302/+attachment/5262460/+files/CurrentDmesg.txt ** 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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luky 1581 F pulseaudio /dev/snd/controlC1: luky 1581 F pulseaudio /dev/snd/pcmC1D0c: luky 1581 F...m pulseaudio /dev/snd/controlC2: luky 1581 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-07 (1 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: 3: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.K0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR (MS-7A37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1828302] Re: CSR Bluetooth driver: Insufficient performance compared to WIndows driver
apport information ** Tags added: apport-collected disco ** Description changed: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: luky 1581 F pulseaudio + /dev/snd/controlC1: luky 1581 F pulseaudio + /dev/snd/pcmC1D0c: luky 1581 F...m pulseaudio + /dev/snd/controlC2: luky 1581 F pulseaudio + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-05-07 (1 days ago) + InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) + IwConfig: + enp24s0 no wireless extensions. + + lono wireless extensions. + MachineType: Micro-Star International Co., Ltd. MS-7A37 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + RfKill: + 3: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/22/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.K0 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B350M MORTAR (MS-7A37) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 4 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7A37 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1828302/+attachment/5262458/+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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name:
[Kernel-packages] [Bug 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Tuesday, 07. May 2019 12:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826354 Title: linux-azure: 4.15.0-1044.48 -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: 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 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Tuesday, 07. May 2019 12:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+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 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker
monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure Instances kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests fail in kvm_unit_tests , 1821152: ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826354 Title: linux-azure: 4.15.0-1044.48 -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: 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 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Tuesday, 07. May 2019 12:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+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 1828302] 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 1828302 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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: Incomplete Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1828302] Re: CSR Bluetooth driver: Insufficient performance compared to WIndows driver
** Description changed: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB - BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 - UP RUNNING PSCAN - RX bytes:667 acl:0 sco:0 events:49 errors:0 - TX bytes:4783 acl:0 sco:0 commands:48 errors:0 - Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 - Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 - Link policy: RSWITCH HOLD SNIFF PARK - Link mode: SLAVE ACCEPT - Name: 'luky-XPS-15-9550 #2 - Class: 0x3c010c - Service Classes: Rendering, Capturing, Object Transfer, Audio - Device Class: Computer, Laptop - HCI Version: 2.1 (0x4) Revision: 0x149c - LMP Version: 2.1 (0x4) Subversion: 0x149c - Manufacturer: Cambridge Silicon Radio (10) + BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 + UP RUNNING PSCAN + RX bytes:667 acl:0 sco:0 events:49 errors:0 + TX bytes:4783 acl:0 sco:0 commands:48 errors:0 + Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 + Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 + Link policy: RSWITCH HOLD SNIFF PARK + Link mode: SLAVE ACCEPT + Name: 'luky-XPS-15-9550 #2 + Class: 0x3c010c + Service Classes: Rendering, Capturing, Object Transfer, Audio + Device Class: Computer, Laptop + HCI Version: 2.1 (0x4) Revision: 0x149c + LMP Version: 2.1 (0x4) Subversion: 0x149c + Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic - - In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters + In Windows this adapter work normally, on Ubuntu Linux it's barely able + to connect to any device and maintain a stable connection, it completely + loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different + + Worth noting that I also tried this on my laptop, and here looks like it + works insanely better than my desktop pc... + + My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo -- 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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: New Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1828302] [NEW] CSR Bluetooth driver: Insufficient performance compared to WIndows driver
Public bug reported: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo ** 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/1828302 Title: CSR Bluetooth driver: Insufficient performance compared to WIndows driver Status in linux package in Ubuntu: New Bug description: I'm reporting this because I'm pretty sure a class 2 bluetooth adapter shouldn't be unable to connect at less than 1 meter, when comparing this to the Windows driver at least... The bluetooth device is a CSR USB bluetooth 2.1 adapter hci1: Type: Primary Bus: USB BD Address: 00:15:83:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:667 acl:0 sco:0 events:49 errors:0 TX bytes:4783 acl:0 sco:0 commands:48 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'luky-XPS-15-9550 #2 Class: 0x3c010c Service Classes: Rendering, Capturing, Object Transfer, Audio Device Class: Computer, Laptop HCI Version: 2.1 (0x4) Revision: 0x149c LMP Version: 2.1 (0x4) Subversion: 0x149c Manufacturer: Cambridge Silicon Radio (10) the kernel driver in use is `btusb` the ubuntu version is 19.04 the kernel version is 5.0.0-13-generic In Windows this adapter work normally, on Ubuntu Linux it's barely able to connect to any device and maintain a stable connection, it completely loses the connection unlikely in Windows after more than 40 centimeters Already tried the 5.1 mainline kernel, it doesn't seem different Worth noting that I also tried this on my laptop, and here looks like it works insanely better than my desktop pc... My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828302/+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 1828304] [NEW] QCA6174 slow transfer speeds
Public bug reported: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic- updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828304 Title: QCA6174 slow transfer speeds Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic-updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828304/+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 1828298] [NEW] Kernel Oops - unable to handle kernel paging request at ffffc90000d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi]
Public bug reported: After using my computer (Dell Inspiron 3576, running Ununtu 16.04.6 LTS) for a while the wi-fi suddenly stops working. The rest of my apps and programs continue to run smoothly. However, when I open "System Settings" and then try to open "Network", the computer hangs and in order to get it working again I have to reboot it. The reboot takes forever; meanwhle, I get a black screen with this message: [75873.475364] BUG: unable to handle kernel paging request at c9d6e808 [] IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] PGD 2569aa067 PUD 2569ab067 PMD 255a96067 PTE 0 Oops: [#1] SMP Full error readout in the attached photos. Btw, there seems to be a very similar issue for this model Dell laptops: https://www.dell.com/community/Linux-General/Wi-Fi-WiFi-not-found-after- suspend-sleep/td-p/7186711 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 21:56:07 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-oops xenial ** Attachment added: "Ooops photos" https://bugs.launchpad.net/bugs/1828298/+attachment/5262448/+files/Call%20Trace.jpg -- 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/1828298 Title: Kernel Oops - unable to handle kernel paging request at c9d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] Status in linux-signed package in Ubuntu: New Bug description: After using my computer (Dell Inspiron 3576, running Ununtu 16.04.6 LTS) for a while the wi-fi suddenly stops working. The rest of my apps and programs continue to run smoothly. However, when I open "System Settings" and then try to open "Network", the computer hangs and in order to get it working again I have to reboot it. The reboot takes forever; meanwhle, I get a black screen with this message: [75873.475364] BUG: unable to handle kernel paging request at c9d6e808 [] IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] PGD 2569aa067 PUD 2569ab067 PMD 255a96067 PTE 0 Oops: [#1] SMP Full error readout in the attached photos. Btw, there seems to be a very similar issue for this model Dell laptops: https://www.dell.com/community/Linux-General/Wi-Fi-WiFi-not- found-after-suspend-sleep/td-p/7186711 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 21:56:07 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 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-signed/+bug/1828298/+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 1828298] Re: Kernel Oops - unable to handle kernel paging request at ffffc90000d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi]
** Attachment added: "Bug Kernel Oops.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1828298/+attachment/5262452/+files/Bug%20Kernel%20Oops.jpg -- 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/1828298 Title: Kernel Oops - unable to handle kernel paging request at c9d6e808; IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] Status in linux-signed package in Ubuntu: New Bug description: After using my computer (Dell Inspiron 3576, running Ununtu 16.04.6 LTS) for a while the wi-fi suddenly stops working. The rest of my apps and programs continue to run smoothly. However, when I open "System Settings" and then try to open "Network", the computer hangs and in order to get it working again I have to reboot it. The reboot takes forever; meanwhle, I get a black screen with this message: [75873.475364] BUG: unable to handle kernel paging request at c9d6e808 [] IP [] iwl_trans_pcie_read32+0x12/0x20 [iwlwifi] PGD 2569aa067 PUD 2569ab067 PMD 255a96067 PTE 0 Oops: [#1] SMP Full error readout in the attached photos. Btw, there seems to be a very similar issue for this model Dell laptops: https://www.dell.com/community/Linux-General/Wi-Fi-WiFi-not- found-after-suspend-sleep/td-p/7186711 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 21:56:07 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-12-13 (146 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 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-signed/+bug/1828298/+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 1819485] Re: AMD Rome : Additional patches
The following patches will not be submitted: CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices -- 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/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+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 1819485] Re: AMD Rome : Additional patches
SRU [Impact] Some house cleaning and adding PCI devices for Rome. The PCI topology patch is so that the correct root PCI device gets used for the correct SMU access. With the PCI topology patch, k10temp(thermal monitoring) will accurately provide the temperature for both sockets. The MCE patch adds more robustness. [Test Case] On a Rome system, just load k10temp, and the sysfs entries are in: localhost:/sys/bus/pci/drivers/k10temp/:00:*.3/hwmon/hwmonN/ on Rome and if you have sensors installed, sensors should display the information. [Regression Potential] Risk is low as the code is localized to AMD specific hardware and what is added is PCI awareness for devices on Rome. [Other Info] All these patches have already been accepted upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+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 1579410] Re: Cannot suspend HP ProLiant SE316M1R2
So it's not something fixable... ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1579410 Title: Cannot suspend HP ProLiant SE316M1R2 Status in linux package in Ubuntu: Won't Fix Bug description: pm-suspend does not work on HP ProLiant SE316M1R2 system. I am not sure if hardware actually supports that though, but there is kernel crash (see syslog.txt attached with Call Trace) which maybe is the cause. Monitor goes off for few seconds but after that system resumes and works as before. Also, some interesting lines: May 7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): hpsa_suspend+0x0/0x10 [hpsa] returns -38 May 7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): pci_pm_freeze+0x0/0xe0 returns -38 May 7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 failed to freeze async: error -38s2disks These lines also appears when using s2disk. s2ram gives: KMS graphics driver is in use, skipping quirks. s2ram_do: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.21.22 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sat May 7 20:55:52 2016 HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3 InstallationDate: Installed on 2015-10-12 (208 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: HP ProLiant SE316M1R2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago) dmi.bios.date: 07/02/2013 dmi.bios.vendor: HP dmi.bios.version: R02 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant SE316M1R2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579410/+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 1826858] Re: XPS 9343 System freezes requiring hard reset
Maybe this can help https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/comments/42? -- 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/1826858 Title: XPS 9343 System freezes requiring hard reset Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to disco I have started having regular freezes of my laptop. There is no response to key presses, mouse movement etc. Only recourse is to reset the system. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 29 11:13:13 2019 HibernationDevice: RESUME=UUID=e76f9b75-a3b2-48c0-931f-7af49bda53bb InstallationDate: Installed on 2019-01-06 (112 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-13 (15 days ago) dmi.bios.date: 08/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826858/+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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
FWIW this is the (not upstreamed yet) patch to solve the issue: https://lkml.org/lkml/2019/4/30/213 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828281] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828281 Title: Can't shutdown blocked for more than 120 seconds Status in linux package in Ubuntu: Confirmed Bug description: Version.log && lspci-vnvn.log https://drive.google.com/drive/folders/1RDfz1ozwAFTP7AuHO8_U16zuZAVPKRDS?usp=sharing Ubuntu 19.04 Problem: When i try to shudown my pc. I have black screen and this errors INFO: task systemd-shutdow:1 blocked for more than 120 seconds Not tainted 5.0.0-13-generic #14-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dinfy 2482 F pulseaudio /dev/snd/controlC1: dinfy 2482 F pulseaudio /dev/snd/pcmC1D0p: dinfy 2482 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 8 21:25:11 2019 InstallationDate: Installed on 2019-04-17 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS ELITE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e7c90f20-bb22-4450-a634-e81110327fcb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-26 (12 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS ELITE-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSELITE-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828281/+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 1828281] [NEW] Can't shutdown blocked for more than 120 seconds
Public bug reported: Version.log && lspci-vnvn.log https://drive.google.com/drive/folders/1RDfz1ozwAFTP7AuHO8_U16zuZAVPKRDS?usp=sharing Ubuntu 19.04 Problem: When i try to shudown my pc. I have black screen and this errors INFO: task systemd-shutdow:1 blocked for more than 120 seconds Not tainted 5.0.0-13-generic #14-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dinfy 2482 F pulseaudio /dev/snd/controlC1: dinfy 2482 F pulseaudio /dev/snd/pcmC1D0p: dinfy 2482 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 8 21:25:11 2019 InstallationDate: Installed on 2019-04-17 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS ELITE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e7c90f20-bb22-4450-a634-e81110327fcb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-26 (12 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS ELITE-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSELITE-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1828281 Title: Can't shutdown blocked for more than 120 seconds Status in linux package in Ubuntu: New Bug description: Version.log && lspci-vnvn.log https://drive.google.com/drive/folders/1RDfz1ozwAFTP7AuHO8_U16zuZAVPKRDS?usp=sharing Ubuntu 19.04 Problem: When i try to shudown my pc. I have black screen and this errors INFO: task systemd-shutdow:1 blocked for more than 120 seconds Not tainted 5.0.0-13-generic #14-Ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dinfy 2482 F pulseaudio /dev/snd/controlC1: dinfy 2482 F pulseaudio /dev/snd/pcmC1D0p: dinfy 2482 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 8 21:25:11 2019 InstallationDate: Installed on 2019-04-17 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS ELITE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e7c90f20-bb22-4450-a634-e81110327fcb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-26 (12 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS ELITE-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSELITE-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Sorry I didn't answer before. The script by @rasch seems to have solved the issue for me. I didn't have any problem with WiFi since using it almost two weeks ago. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820872] Re: Xenial: Sync to upstream v4.9 (Spectre)
** 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/1820872 Title: Xenial: Sync to upstream v4.9 (Spectre) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: == SRU Justification == Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the Spectre-related areas. == Regression Potential == Low. These are cosmetic cleanups (non-functional changes) and backports of low-risk commits that have been in upstream stable for quite a while already. == Fix == Backport the relevant commits. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+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 1822760] Re: Bionic: Sync to Xenial (Spectre)
** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1822760 Title: Bionic: Sync to Xenial (Spectre) Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == There are a couple of Spectre related commits in Xenial that never landed in Bionic. Fix that to prevent a regression when upgrading from Xenial to Bionic. == Regression Potential == Low. These are not very intrusive commits that have been in upstream for quite a while. == Fix == Backport the relevant commits from upstream. == Test Case == TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822760/+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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
THe script by @rasch did not help for the issue that I have on my XPS 9360 where the wifi adapter is gone after resuming from sleep. Not sure if it's supposed to. Putting the machine back to sleep and then waking it up again solves things. However, if it's plugged in while I put it to sleep, waking it up does not help, so I also have to make sure it's unplugged. I've had this since I got the machine last year, with every version of Ubuntu that's been available since then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827555] Re: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827555 Title: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14) Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux-hwe source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-hwe source package in Disco: Invalid Bug description: [Impact] * On the System76 Gazelle (gaze14), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is identical to the patch already applied for the System76 Darter Pro (darp5). [Test Case] * With the affected hardware, attempt to use a headset with a microphone input. There will be no microphone input from the headset until applying this patch. [Regression Potential] * Extremely low, it specifically identifies the affected hardware. [Other Info] * I have attached the patch as it will be applied to upstream Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+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 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824864
Title:
CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
New
Status in linux source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
New
Status in linux source package in Cosmic:
Confirmed
Status in systemd source package in Cosmic:
New
Status in linux source package in Disco:
Fix Committed
Status in systemd source package in Disco:
New
Status in linux source package in Eoan:
Confirmed
Status in systemd source package in Eoan:
New
Bug description:
[Impact]
* Too small dmsg kernel buf ring size leads to loosing/missing early
boot kernel messages which happen before journald starts slurping them
up and storing them on disc. This results in messages similar to this
one on boot "missed NN kernel messages on boot". This is especially
pronounced on arm64 as the default setting there is way lower than any
other 32bit or 64bit architecture we ship. Also amd64 appears to have
the highest setting of 18 among all architectures we ship. The best
course of action to bump all 64bit arches to 18, and keep all 32bit
arches at the current & upstream default of 17.
[Test Case]
* $ cat /boot/config-`uname -r` | grep CONFIG_LOG_BUF_SHIFT
on 64bit arches result should be: CONFIG_LOG_BUF_SHIFT=18
on 32bit arches result should be: CONFIG_LOG_BUF_SHIFT=17
* run systemd adt test, the boot-and-services test case should not
fail journald tests with "missed kernel messages" visible in the error
logs.
[Regression Potential]
* Increasing the size of the log_buf, will increase kernel memory
usage which cannot be reclaimed. It will now become 256kb on arm64,
ppc64el, s390x instead of 8kB/128kb/128kb respectively. 32bit arches
remain unchanged at 128kb.
[Other Info]
* Original bug report
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux
kernel command line in the dmesg (journalctl -k -b). And it is
consistently failing on arm64 scalingstack KVM EFI machines with
messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el':
'13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before
running the tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 08. May 2019 16:27 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 08. May 2019 17:12 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress -- 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Promote to Proposed phase-changed: Wednesday, 08. May 2019 17:12 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] On the LattePanda board, the headphone detection signal is not correct, it is inverted: plugging in headphones disables headphone output [Fix] In the codec driver, there already is a fixup, just set the inv_jd1_1 to true. [Test Case] It is tested by the bug reporter, please refer to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23 [Regression Risk] Low. This fix is specific to a board which is defined by DMI strings. My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string =
[Kernel-packages] [Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] In our OEM projects, we often meet this issues, there is no any monitor plugged, but in the gnome-sound-setting, there are 4 hdmi/dp audio devices. [Fix] We check the eld_valid when reporting the hdmi/dp jack event [Test Case] On the problematic machines, we do s3 test without plugging monitor, there is no hdmi audio device in the sound-setting. On the machines without this problem, we do s3 test, pluggin/unplugging monitor test, the hdmi audio work well as before. [Regression Risk] Low. We have done many tests on machines with or without this problem, there is no regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+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 1483095] Re: Bluetooth device 0cf3:e007 may sometimes fail to initialize
** Changed in: hwe-next Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: hwe-next/vivid Status: New => Won't Fix -- 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/1483095 Title: Bluetooth device 0cf3:e007 may sometimes fail to initialize Status in HWE Next: Won't Fix Status in HWE Next vivid series: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: On cold or warm boot, sometimes this device would fail to initialize. An error message can be found in dmesg: [ 19.268671] Bluetooth: hci0: Failed to access otp area (-113) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483095/+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 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826036 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 08. May 2019 14:04 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 08. May 2019 16:34 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress -- 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/1826032 Title: linux-fips: 4.4.0-1009.11 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826036 phase: Promote to Proposed phase-changed: Wednesday, 08. May 2019 16:34 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+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 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
*** This bug is a duplicate of bug 1826350 *** https://bugs.launchpad.net/bugs/1826350 ** This bug is no longer a duplicate of bug 1824592 linux-fips: 4.15.0-1005.6 -proposed tracker ** This bug has been marked a duplicate of bug 1826350 linux-fips: 4.15.0-1006.7 -proposed tracker -- 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/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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 verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1819716 phase: Holding before Release phase-changed: Friday, 05. April 2019 01:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 08. May 2019 15:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 08. May 2019 16:27 UTC reason: - promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed + promote-signing-to-proposed: Pending -- ready for review -- 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Ready for Promote to Proposed phase-changed: Wednesday, 08. May 2019 16:27 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker
*** This bug is a duplicate of bug 1826350 *** https://bugs.launchpad.net/bugs/1826350 ** This bug has been marked a duplicate of bug 1826350 linux-fips: 4.15.0-1006.7 -proposed tracker -- 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/1824592 Title: linux-fips: 4.15.0-1005.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822820 phase: Ready for Testing phase-changed: Monday, 22. April 2019 02:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824592/+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 1822813] Re: linux-fips: 4.15.0-1003.4 -proposed tracker
*** This bug is a duplicate of bug 1826350 *** https://bugs.launchpad.net/bugs/1826350 ** This bug is no longer a duplicate of bug 1824592 linux-fips: 4.15.0-1005.6 -proposed tracker ** This bug has been marked a duplicate of bug 1826350 linux-fips: 4.15.0-1006.7 -proposed tracker -- 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/1822813 Title: linux-fips: 4.15.0-1003.4 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 14:06 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822813/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress -- 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Ready for Promote to Proposed phase-changed: Wednesday, 08. May 2019 16:27 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1824039] Re: linux-fips: 4.15.0-1004.5 -proposed tracker
*** This bug is a duplicate of bug 1826350 *** https://bugs.launchpad.net/bugs/1826350 ** This bug is no longer a duplicate of bug 1824592 linux-fips: 4.15.0-1005.6 -proposed tracker ** This bug has been marked a duplicate of bug 1826350 linux-fips: 4.15.0-1006.7 -proposed tracker -- 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/1824039 Title: linux-fips: 4.15.0-1004.5 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 phase: Promote to Proposed phase-changed: Friday, 12. April 2019 09:08 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824039/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Ready for Promote to Proposed phase-changed: Wednesday, 08. May 2019 16:27 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1826346] Re: linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826348 phase: Signoff phase-changed: Thursday, 02. May 2019 07:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1826346 Title: linux-oracle: 4.15.0-1012.14~16.04.1 -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: 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826348 phase: Signoff phase-changed: Thursday, 02. May 2019 07:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826346/+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 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress -- 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/1826032 Title: linux-fips: 4.4.0-1009.11 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826036 phase: Ready for Promote to Proposed phase-changed: Wednesday, 08. May 2019 14:04 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+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 1826346] Re: linux-oracle: 4.15.0-1012.14~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1826346 Title: linux-oracle: 4.15.0-1012.14~16.04.1 -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: 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826348 phase: Signoff phase-changed: Thursday, 02. May 2019 07:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826346/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Tags added: kernel-block-proposed -- 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Ready for Promote to Proposed phase-changed: Wednesday, 08. May 2019 16:27 UTC reason: promote-signing-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826143 Title: linux-azure: 5.0.0-1005.5 -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: 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 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+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 1826145] Re: linux-kvm: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Monday, 29. April 2019 17:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- 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/1826145 Title: linux-kvm: 5.0.0-1005.5 -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: 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Monday, 29. April 2019 17:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826145/+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 1826141] Re: linux-aws: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Friday, 03. May 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1826141 Title: linux-aws: 5.0.0-1005.5 -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: 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: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Friday, 03. May 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826141/+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 1826139] Re: linux-raspi2: 5.0.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826139 Title: linux-raspi2: 5.0.0-1007.7 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826139/+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 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826146 Title: linux-snapdragon: 5.0.0-1011.11 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826146/+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 1826144] Re: linux-gcp: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- 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/1826144 Title: linux-gcp: 5.0.0-1005.5 -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: 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 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: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826150 phase: Signoff phase-changed: Thursday, 02. May 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826144/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1827847 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Friday, 03. May 2019 08:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - verification-testing: Ongoing -- testing in progress -- 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/1826150 Title: linux: 5.0.0-14.15 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1827847 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Friday, 03. May 2019 08:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+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 1817518] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.178.1 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+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 1817518] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.175.4 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+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 1817518] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress -- 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 - phase: Promote to Proposed - phase-changed: Wednesday, 08. May 2019 13:40 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 08. May 2019 15:42 UTC reason: - promote-signing-to-proposed: Holding -- builds not complete in Signing - promote-to-proposed: Ongoing -- packages copied but not yet published to Signing + promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed -- 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/1826350 Title: linux-fips: 4.15.0-1006.7 -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: 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1826358 phase: Holding before Promote to Proposed phase-changed: Wednesday, 08. May 2019 15:42 UTC reason: promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+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 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
Verification tests completed successfully with the Disco kernel in -proposed (https://kernel.ubuntu.com/reports/sru-report.html). ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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/1826150 Title: linux: 5.0.0-14.15 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1827847 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Friday, 03. May 2019 08:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+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 1826858] Re: XPS 9343 System freezes requiring hard reset
Most freezes seem to happen while using Firefox -- 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/1826858 Title: XPS 9343 System freezes requiring hard reset Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to disco I have started having regular freezes of my laptop. There is no response to key presses, mouse movement etc. Only recourse is to reset the system. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 29 11:13:13 2019 HibernationDevice: RESUME=UUID=e76f9b75-a3b2-48c0-931f-7af49bda53bb InstallationDate: Installed on 2019-01-06 (112 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-13 (15 days ago) dmi.bios.date: 08/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826858/+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
