[Kernel-packages] [Bug 1824472] 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/1824472 Title: Brightness issue Status in linux package in Ubuntu: Confirmed Bug description: I have Dell inspiron G3. I am not able to change the screen brightness. I tried many solutions, but none worked. 1. I tried changing acpi_backlight = vendor: Now this does solve but it creates another problem. Because for my laptop to shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset. 2. I tried installing applications: But when I run these applications it show "No backlights were found on the system" Kindly address the issue and provide a solution. It is causing great trouble. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishita1806 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 11:55:50 2019 HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090 InstallationDate: Installed on 2019-02-28 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset acpi_backlight=vendor vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 05K0D2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1173759] Re: Ubuntu 13.04 can detect wi-fi but can't connect
A standout amongst the most well-known issues looked in the wake of introducing Ubuntu is the system issue. A few times you will have no remote system in Ubuntu and a few times moderate remote association and at some point it will change among quick and moderate. On the off chance that you are fortunate, it could be fixed by introducing legitimacy drivers in Ubuntu however for the most part, you will be left raging, reviling over moderate or no WiFi association. http://jaisalmerchiragdesertcamp.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1173759 Title: Ubuntu 13.04 can detect wi-fi but can't connect Status in linux package in Ubuntu: Expired Bug description: HP Pavilion laptop with Ralink RT5390 wireless interface 1. Can detect home wi-fi signal but can't connect. Keeps asking for password then "disconnects" over and over again. 2. All other computers, tablets, and smartphones at home can connect to the wi-fi without any trouble at all. 3. HP Pavilion laptop can connect to the internet if tethered to my smartphone (used as a portable wi-fi hotspot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker
** Summary changed: - linux-oem-osp1: -proposed tracker + linux-oem-osp1: 5.0.0-1003.4 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824382 Title: linux-oem-osp1: 5.0.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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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: 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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Friday, 12. April 2019 08:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
@arighi, thanks. Let me know if you need more testing and/or help. Good luck with the 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification: [Impact] * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a race condition that leave fuse inode's mutex held, triggering a deadlock * The problem is that the lock and unlock paths are relying on get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be acquired/released, but its value might be set in the lock path and unset in the unlock path (leaving the mutex held) [Test Case] * A test case that triggers the bug almost immediately can be found here https://github.com/hanwen/go-fuse/pull/288 [Fix] * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the locking path and pass a variable to fuse_unlock_inode() to determine if the mutex was acquired or not [Regression Potential] * Fix has been tested on the affected platform. It is an upstream fix that seems to affect only 4.7+ kernels, more exactly in our case only Bionic kernels (and derived) are affected. Cosmic and above already include this fix. So regression potential is minimal. [Original bug report] Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace
[Kernel-packages] [Bug 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -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 -- kernel-stable-master-bug: 1824383 - phase: Ready for Packaging - phase-changed: Friday, 12. April 2019 02:11 UTC + phase: Packaging + phase-changed: Friday, 12. April 2019 08:11 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824382 Title: linux-oem-osp1: 5.0.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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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: 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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Friday, 12. April 2019 08:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS
right, so OTOH the old regression on ppc hasn't been fully verified yet, but blacklisting bochs_drm causes 1823152 on x86 which surely is more important than ppc.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in kmod source package in Disco: Confirmed Status in linux source package in Disco: Incomplete Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
This is in all newer versions of iproute2 (newer than Xenial), setting
the general task to Fix Released
** Changed in: iproute2 (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS
@Timo - Ack, this should be enabled again. And if really still an issue for PPC then a different solution than to disable it should be evaluated (can we do arch specific blakclisting?). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in kmod source package in Disco: Confirmed Status in linux source package in Disco: Incomplete Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You 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 kernel-stable-master-bug: 1822820 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 1805079] Re: click/pop noise in the headphone on several lenovo laptops
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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: 1822820 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 10. April 2019 17:08 UTC + phase: Promote to Proposed + phase-changed: Friday, 12. April 2019 09:08 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-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/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 kernel-stable-master-bug: 1822820 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 1824472] Re: Brightness issue
Hi, could you also upload a copy of syslog booted without "acpi_backlight=vendor"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824472 Title: Brightness issue Status in linux package in Ubuntu: Confirmed Bug description: I have Dell inspiron G3. I am not able to change the screen brightness. I tried many solutions, but none worked. 1. I tried changing acpi_backlight = vendor: Now this does solve but it creates another problem. Because for my laptop to shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset. 2. I tried installing applications: But when I run these applications it show "No backlights were found on the system" Kindly address the issue and provide a solution. It is causing great trouble. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishita1806 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 11:55:50 2019 HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090 InstallationDate: Installed on 2019-02-28 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset acpi_backlight=vendor vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 05K0D2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS
the disco kernel being prepared does enable bochs again, but kmod still needs to be fixed.. there's no mechanism for arch-specific blacklisting (right now at least), but the kernel option could still be disabled for ppc if absolutely necessary -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in kmod source package in Disco: Confirmed Status in linux source package in Disco: Incomplete Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge 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 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 12. April 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=18/beta' - snap-release-to-edge: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=18/edge' + snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): + arch=amd64:channel=18/candidate:rev=56' 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/1822808 Title: linux-gcp: 4.15.0-1030.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed 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 verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 12. April 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): arch=amd64:channel=18/candidate:rev=56' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => 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 -- kernel-stable-master-bug: 1824383 - phase: Packaging - phase-changed: Friday, 12. April 2019 08:11 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 12. April 2019 09:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824382 Title: linux-oem-osp1: 5.0.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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: 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 -- kernel-stable-master-bug: 1824383 phase: Holding before Promote to Proposed phase-changed: Friday, 12. April 2019 09:41 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] Re: Touchpad right click does not work as expected on Dell G7 7588
** Summary changed: - Right click does not work as expected on Dell G7 7588 + Touchpad right click does not work as expected on Dell G7 7588 -- 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/1823684 Title: Touchpad right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: Confirmed Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=13 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309562, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309563, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 17:50:24 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1823684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] tarball of patches for bionic with additional pre-reqs
--- Comment on attachment From mranw...@us.ibm.com 2019-04-12 05:43 EDT--- Hi Manoj, thank you. I attached a tarball with patches - in addition to that one it looked best to add these in: 8cf4c05712f0 powerpc/lib/code-patching: refactor patch_instruction() 8183d99f4a22 powerpc/lib/feature-fixups: use raw_patch_instruction() 51c3c62b58b3 powerpc: Avoid code patching freed init sections b45ba4a51cde powerpc/lib: fix book3s/32 boot failure due to code patching The first two are just pre-reqs to keep it cleaner, but since 37bc3e5fd764 is in that seems the right thing to do. The last mostly fixes an error on 32 bit ppc kernels, which aren't supported, but this keeps it closer to upstream in the event of needing some further changes and cleans it up. I tested this with: root@ltc-wspoon5:/home/mranweil# echo 0 > /sys/kernel/debug/powerpc/barrier_nospec root@ltc-wspoon5:/home/mranweil# dmesg |grep -i skip [ 345.961730] Skipping init section patching addr: 0xc10e2b1c root@ltc-wspoon5:/home/mranweil# In addition to the previous tests. ** Attachment added: "tarball of patches for bionic with additional pre-reqs" https://bugs.launchpad.net/bugs/1822870/+attachment/5255147/+files/dd23spectre-patches-bionic.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822987] Re: nouveau timeout with nvidia GTX 1060
** Summary changed: - nouveau timeout on Disco with nvidia GTX 1060 + nouveau timeout with nvidia GTX 1060 ** Also affects: linux (Ubuntu Bionic) 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/1822987 Title: nouveau timeout with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 003606e0 [ 15.714873] DR0: DR1: DR2: [ 15.714874] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.714874] Call Trace: [ 15.714893] acr_r352_bootstrap+0x1a9/0x2b0 [nouveau] [ 15.714910] acr_r352_reset+0x39/0x230 [nouveau] [ 15.714926] nvkm_secboot_reset+0x35/0x70 [nouveau] [ 15.714944] gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau] [ 15.714962] ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau] [ 15.714979] gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau] [ 15.714997] gf100_gr_init+0x563/0x590 [nouveau] [ 15.715015] gf100_gr_init_+0x5b/0x60 [nouveau] [ 15.715032] nvkm_gr_init+0x1d/0x20 [nouveau] [ 15.715041] nvkm_engine_init+0xb9/0x1f0 [nouveau] [ 15.715052] nvkm_subdev_init+0xbc/0x210 [nouveau] [ 15.715061] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 15.715071] nvkm_engine_ref+0x13/0x20 [nouveau] [ 15.715081] nvkm_ioctl_new+0x129/0x220 [nouveau] [ 15.715098] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 15.715115] ? gf100_gr_dtor+0xd0/0xd0 [nouveau] [ 15.715125] nvkm_io
[Kernel-packages] [Bug 1824333] [NEW] autofs kernel module missing
You have been subscribed to a public bug: linux-modules-4.18.0-17-generic misses the autofs module whereas linux- modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- autofs kernel module missing https://bugs.launchpad.net/bugs/1824333 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824472] Re: Brightness issue
Could you also try use `nouveau.modeset=0` instead of nomodeset and remove acpi_backlight as well? The full kernel parameters would then become: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nouveau.modeset=0 vt.handoff=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824472 Title: Brightness issue Status in linux package in Ubuntu: Confirmed Bug description: I have Dell inspiron G3. I am not able to change the screen brightness. I tried many solutions, but none worked. 1. I tried changing acpi_backlight = vendor: Now this does solve but it creates another problem. Because for my laptop to shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset. 2. I tried installing applications: But when I run these applications it show "No backlights were found on the system" Kindly address the issue and provide a solution. It is causing great trouble. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishita1806 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 11:55:50 2019 HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090 InstallationDate: Installed on 2019-02-28 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset acpi_backlight=vendor vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 05K0D2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778844] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2019-04-12 05:41 EDT--- Hi , Any update on this bug, when this fix is expected in official build. Please update the approximate date, as issue exists with latest Ubuntu180401 kernel - 4.15.0-47-generic. Regards, Indira -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRA
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Also affects: autofs (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) 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/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: New Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: New Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
Hi Robert, I haven't found the reason. For my limited kernel knowledge I have checked and discussed a bit. in [1] I found $ grep -Hrn autofs debian.master/contro* debian.master/control.d/generic.inclusion-list:181:fs/autofs4/autofs4.ko But then was made aware that with 4.18 ther kernel started to include this series [2] Which means it was moved to a different path. Maybe this would be enough to fix it, btu that is up to the kernel team diff --git a/debian.master/control.d/generic.inclusion-list b/debian.master/control.d/generic.inclusion-list index 3797f760226a..19fb0d4620c0 100644 --- a/debian.master/control.d/generic.inclusion-list +++ b/debian.master/control.d/generic.inclusion-list @@ -178,7 +178,7 @@ drivers/xen/* ! find sound/core -name oss -prune -o -name *.ko -print fs/9p/* fs/aufs/aufs.ko -fs/autofs4/autofs4.ko +fs/autofs/autofs4.ko fs/binfmt_misc.ko fs/btrfs/* fs/cachefiles/cachefiles.ko [1]: git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=68abbe729567cef128b2c2141f2ed2567f3b8372 ** Changed in: autofs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: New Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: New Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
** Changed in: autofs (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: New Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: New Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824177] Re: dmesg spammed with nvidia-nvlink messages during install
I looked into this, and we simply need a way to prevent the udev rule from trying to load the modules on the live installer. Iain Lane suggested using an empty udev rule in /run/udev/rules.d/ to override the nvidia one, in casper. I am going to work on the relevant changes. ** Also affects: casper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1824177 Title: dmesg spammed with nvidia-nvlink messages during install Status in casper package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop. I've selected the 3rd party driver option in ubiquity and now my dmesg is spammed 10x per second with this chunk. This appears to be slowing down the install. [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major device number 235 [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, major device number 235 [Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 1 device(s). [Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: NVRM: nouveau, rivafb, nvidiafb or rivatv NVRM: was loaded and obtained ownership of the NVIDIA device(s). [Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module (and/or NVRM: reconfigure your kernel without the conflicting NVRM: driver(s)), then try loading the NVIDIA kernel module NVRM: again. [Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 16:29:38 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1824177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824472] Re: Unable to set brightness on Dell G3 3579 with nomodeset
** Summary changed: - Brightness issue + Unable to set brightness on Dell G3 3579 with nomodeset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824472 Title: Unable to set brightness on Dell G3 3579 with nomodeset Status in linux package in Ubuntu: Confirmed Bug description: I have Dell inspiron G3. I am not able to change the screen brightness. I tried many solutions, but none worked. 1. I tried changing acpi_backlight = vendor: Now this does solve but it creates another problem. Because for my laptop to shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset. 2. I tried installing applications: But when I run these applications it show "No backlights were found on the system" Kindly address the issue and provide a solution. It is causing great trouble. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishita1806 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 11:55:50 2019 HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090 InstallationDate: Installed on 2019-02-28 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset acpi_backlight=vendor vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 05K0D2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: Confirmed Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821395] Re: fscache: jobs might hang when fscache disk is full
Verification successful with xfstests on nfs+fscache.
No regression in cosmic-proposed from cosmic-updates.
cosmic-updates / 4.18.0-17:
Failures: generic/035 generic/258 generic/294 generic/448 generic/467
generic/477 generic/484 generic/490 generic/495
Failed 9 of 437 tests
cosmic-proposed / 4.18.0-18:
Failures: generic/035 generic/258 generic/294 generic/448 generic/467
generic/477 generic/484 generic/490 generic/495
Failed 9 of 437 tests
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821395
Title:
fscache: jobs might hang when fscache disk is full
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* fscache issue where jobs get hung when fscache disk is full.
* trivial upstream fix; already applied in X/D, required in B/C:
commit c5a94f434c82 ("fscache: fix race between enablement and
dropping of object").
[Test Case]
* Test kernel verified / regression-tested by reporter.
* Apparently there's no simple test case,
but these are the conditions to hit the problem:
1) The active dataset size is equal to the cache disk size.
The application reads the data over and over again.
2) Disk is near full (90%+)
3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
4) new cachefiles are created and some fail with no disk space.
5) race in dropping object state machine and
deferred lookup state machine causes the hang.
6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
[Regression Potential]
* Low; contained in fscache; no further fixes applied upstream.
* This patch is applied in a stable tree (linux-4.4.y).
[Original Description]
An user reported an fscache issue where jobs get hung when the fscache
disk is full.
After investigation, it's been found to be an issue already reported/fixed
upstream,
by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of
object").
This patch is required in Bionic and Cosmic, and it's applied in
Xenial (via stable) and Disco.
Apparently there's no simple test case, but these are the conditions
to hit the problem:
1) The active dataset size is equal to the cache disk size.
The application reads the data over and over again.
2) Disk is near full (90%+)
3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
4) new cachefiles are created and some fail with no disk space.
5) race in dropping object state machine and
deferred lookup state machine causes the hang.
6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
HP Z820 Workstation machine HP 158B motherboard 4.15.0-47-generic kernel same error ... [ 821.269834] do_IRQ: 4.38 No irq handler for vector [ 823.270705] do_IRQ: 4.38 No irq handler for vector [ 824.271303] do_IRQ: 4.38 No irq handler for vector [ 826.272120] do_IRQ: 4.38 No irq handler for vector [ 833.340194] do_IRQ: 4.38 No irq handler for vector [ 838.342193] do_IRQ: 4.38 No irq handler for vector ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 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-4.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.
[Kernel-packages] [Bug 1821395] Re: fscache: jobs might hang when fscache disk is full
Verification successful with xfstests on nfs+fscache.
No regression in bionic-proposed from bionic-updates.
bionic-updates / 4.15.0-47:
Failures: generic/035 generic/075 generic/091 generic/112 generic/263
generic/294 generic/306 generic/307 generic/430 generic/431 generic/434
generic/469 generic/484 generic/495
Failed 14 of 437 tests
bionic-proposed / 4.15.0-48:
Failures: generic/035 generic/075 generic/091 generic/112 generic/263
generic/294 generic/306 generic/307 generic/430 generic/431 generic/434
generic/469 generic/484 generic/495
Failed 14 of 437 tests
** 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/1821395
Title:
fscache: jobs might hang when fscache disk is full
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* fscache issue where jobs get hung when fscache disk is full.
* trivial upstream fix; already applied in X/D, required in B/C:
commit c5a94f434c82 ("fscache: fix race between enablement and
dropping of object").
[Test Case]
* Test kernel verified / regression-tested by reporter.
* Apparently there's no simple test case,
but these are the conditions to hit the problem:
1) The active dataset size is equal to the cache disk size.
The application reads the data over and over again.
2) Disk is near full (90%+)
3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
4) new cachefiles are created and some fail with no disk space.
5) race in dropping object state machine and
deferred lookup state machine causes the hang.
6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
[Regression Potential]
* Low; contained in fscache; no further fixes applied upstream.
* This patch is applied in a stable tree (linux-4.4.y).
[Original Description]
An user reported an fscache issue where jobs get hung when the fscache
disk is full.
After investigation, it's been found to be an issue already reported/fixed
upstream,
by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of
object").
This patch is required in Bionic and Cosmic, and it's applied in
Xenial (via stable) and Disco.
Apparently there's no simple test case, but these are the conditions
to hit the problem:
1) The active dataset size is equal to the cache disk size.
The application reads the data over and over again.
2) Disk is near full (90%+)
3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
4) new cachefiles are created and some fail with no disk space.
5) race in dropping object state machine and
deferred lookup state machine causes the hang.
6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821395] Re: fscache: jobs might hang when fscache disk is full
Regression testing setup/steps
===
fscache
---
sudo apt-get -y install cachefilesd
echo 'RUN=yes' | sudo tee -a /etc/default/cachefilesd
sudo modprobe fscache
sudo systemctl start cachefilesd
nfs
---
sudo apt-get -y install nfs-kernel-server
sudo systemctl start nfs-kernel-server
sudo mkdir -p /{srv,mnt}/nfs-{test,scratch}
# different fsid if in the same local filesystem
echo '/srv/nfs-test127.0.0.1(rw,no_subtree_check,no_root_squash,fsid=0)' |
sudo tee -a /etc/exports
echo '/srv/nfs-scratch 127.0.0.1(rw,no_subtree_check,no_root_squash,fsid=1)' |
sudo tee -a /etc/exports
sudo exportfs -ra
xfs-tests
-
sudo apt-get -y install automake gcc make git xfsprogs xfslibs-dev \
uuid-dev uuid-runtime libtool-bin e2fsprogs libuuid1 attr libattr1-dev \
libacl1-dev libaio-dev libgdbm-dev quota gawk fio dbench python sqlite3
git clone https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
cd xfstests-dev
git log --oneline -1 HEAD
f3c1bca generic: Test that SEEK_HOLE can find a punched hole
make -j$(nproc); echo $? # must be 0
sudo useradd fsgqa
sudo groupadd fsgqa
sudo useradd 123456-fsgqa
export TEST_DEV=127.0.0.1:/srv/nfs-test
export TEST_DIR=/mnt/nfs-test
export SCRATCH_DEV=127.0.0.1:/srv/nfs-scratch
export SCRATCH_MNT=/mnt/nfs-scratch
export TEST_FS_MOUNT_OPTS="-o fsc" # for fscache / test dev
export NFS_MOUNT_OPTIONS="-o fsc" # for fscache / scratch dev
cd ~/xfstests-dev
sudo -E ./check -nfs -g quick 2>&1 | tee ~/xfs-tests.nfs.log.$(uname -r)
<...>
---
In another terminal, check the NFS mounts are indeed with the 'fsc'
(fscache) attribute:
$ mount | grep nfs | grep fsc
127.0.0.1:/srv/nfs-test on /mnt/nfs-test type nfs4
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,fsc,local_lock=none,addr=127.0.0.1)
127.0.0.1:/srv/nfs-scratch on /mnt/nfs-scratch type nfs4
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,fsc,local_lock=none,addr=127.0.0.1)
And compare fscache stats before/after run:
$ cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=0 dat=0 spc=0
Objects: alc=0 nal=0 avl=0 ded=0
ChkAux : non=0 ok=0 upd=0 obs=0
Pages : mrk=0 unc=0
Acquire: n=0 nul=0 noc=0 ok=0 nbf=0 oom=0
Lookups: n=0 neg=0 pos=0 crt=0 tmo=0
Invals : n=0 run=0
Updates: n=0 nul=0 run=0
Relinqs: n=0 nul=0 wcr=0 rtr=0
AttrChg: n=0 ok=0 nbf=0 oom=0 run=0
Allocs : n=0 ok=0 wt=0 nbf=0 int=0
Allocs : ops=0 owt=0 abt=0
Retrvls: n=0 ok=0 wt=0 nod=0 nbf=0 int=0 oom=0
Retrvls: ops=0 owt=0 abt=0
Stores : n=0 ok=0 agn=0 nbf=0 oom=0
Stores : ops=0 run=0 pgs=0 rxd=0 olm=0
VmScan : nos=0 gon=0 bsy=0 can=0 wt=0
Ops: pend=0 run=0 enq=0 can=0 rej=0
Ops: ini=0 dfr=0 rel=0 gc=0
CacheOp: alo=0 luo=0 luc=0 gro=0
CacheOp: inv=0 upo=0 dro=0 pto=0 atc=0 syn=0
CacheOp: rap=0 ras=0 alp=0 als=0 wrp=0 ucp=0 dsp=0
...
$ cat /proc/fs/fscache/stats
FS-Cache statistics
Cookies: idx=412 dat=2441632 spc=0
Objects: alc=8929 nal=0 avl=8741 ded=8928
ChkAux : non=0 ok=86 upd=0 obs=1123
Pages : mrk=371441 unc=371441
Acquire: n=2442044 nul=0 noc=0 ok=2442044 nbf=0 oom=0
Lookups: n=8929 neg=8817 pos=112 crt=8817 tmo=0
Invals : n=152 run=152
Updates: n=0 nul=0 run=152
Relinqs: n=2442044 nul=0 wcr=0 rtr=0
AttrChg: n=0 ok=0 nbf=0 oom=0 run=0
Allocs : n=0 ok=0 wt=0 nbf=0 int=0
Allocs : ops=0 owt=0 abt=0
Retrvls: n=1498 ok=0 wt=195 nod=1498 nbf=0 int=0 oom=0
Retrvls: ops=1498 owt=575 abt=0
Stores : n=371145 ok=371145 agn=0 nbf=0 oom=0
Stores : ops=1117 run=372234 pgs=371118 rxd=371118 olm=0
VmScan : nos=49 gon=0 bsy=0 can=0 wt=0
Ops: pend=575 run=2767 enq=372387 can=0 rej=0
Ops: ini=372795 dfr=37 rel=372795 gc=37
CacheOp: alo=0 luo=0 luc=0 gro=0
CacheOp: inv=0 upo=0 dro=0 pto=0 atc=0 syn=0
CacheOp: rap=0 ras=0 alp=0 als=0 wrp=0 ucp=0 dsp=0
CacheEv: nsp=1123 stl=0 rtr=0 cul=0
---
Note, in 4.15.0 kernels, some tests apparently run forever:
generic/430, 431 and 434 (same behavior in nfs+fscache, ext4, xfs),
they were killed with 'sudo kill -TERM $(pidof xfs_io)'.
# ref: https://wiki.linux-nfs.org/wiki/index.php/Xfstests
** 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/1821395
Title:
fscache: jobs might hang when fscache disk is full
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* fscache issue where jobs get hung when fscache disk is full.
* trivial upstream fix; already applied in X/D, required in B/C:
commit c5a94f434c82 ("fscache: fix race between enablement and
dropping of object").
[Test Case]
* Test kernel verified / regression-tested by reporter.
* Apparently there's no simple test case,
[Kernel-packages] [Bug 1822987] Re: nouveau timeout with nvidia GTX 1060
This can be reproduced in the very beginning of Bionic 4.15.0-20-generic, please see the attachment for boot dmesg. ** Attachment added: "4.15.0-20-generic-dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822987/+attachment/5255152/+files/4.15.0-20-generic-dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822987 Title: nouveau timeout with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 003606e0 [ 15.714873] DR0: DR1: DR2: [ 15.714874] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.714874] Call Trace: [ 15.714893] acr_r352_bootstrap+0x1a9/0x2b0 [nouveau] [ 15.714910] acr_r352_reset+0x39/0x230 [nouveau] [ 15.714926] nvkm_secboot_reset+0x35/0x70 [nouveau] [ 15.714944] gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau] [ 15.714962] ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau] [ 15.714979] gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau] [ 15.714997] gf100_gr_init+0x563/0x590 [nouveau] [ 15.715015] gf100_gr_init_+0x5b/0x60 [nouveau] [ 15.715032] nvkm_gr_init+0x1d/0x20 [nouveau] [ 15.715041] nvkm_engine_init+0xb9/0x1f0 [nouveau] [ 15.715052] nvkm_subdev_init+0xbc/0x210 [nouveau] [ 15.715061] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 15.715071] nvkm_engine_ref+0x13/0x20 [nouveau] [ 15.715081] nvkm_ioctl_new+0x129/0x220 [nouveau] [ 15.715098] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [
[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 12. April 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap gcp-kernel not in expected channel(s): - arch=amd64:channel=18/candidate:rev=56' 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/1822808 Title: linux-gcp: 4.15.0-1030.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 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 verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 12. April 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 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/1822808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Tags added: 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: In Progress Status in linux source package in Cosmic: In Progress Bug description: 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 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Fix sent to mailing list: https://lists.ubuntu.com/archives/kernel-
team/2019-April/099806.html
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => 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/1822247
Title:
ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification, BIONIC ==
[Impact]
Running the autotest regression test ubuntu_nbd_smoke occasionally
trips I/O errors such as:
[ 700.668758] print_req_error: I/O error, dev nbd0, sector 0
[ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read
This happens when the nbd client detaches and the backing store is
removed. The fix is to ensure a rescan occurs.
[Fix]
Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set
bd_invalidated"). If a disconnect action happens the
partition table gets invalidated and rescanned properly.
[Test]
Without the fix running the Ubuntu Kernel Team nbd smoke test will
occasionally trip the bug and the error message from the kernel
appears and the test fails. With the fix, this test has been run tens
of times without showing the failure.
To test run:
autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control
[Regression Potential]
This fix touches just the NBD driver and has been upstream since May
2018 without any subsequent bug reports against it, so it is a known
good fix. At most it sets the bd_invalidated flag more aggressively,
so the rescan will occur, so I believe the regression potential is
very limited just to ndb client connect/disconnect activity.
-
Reproduce rate: 2 out of 3 runs
This issue can be found on other arches as well, normally it will fail with
the first run and pass with the second attempt.
* Command:
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
_test.sh
Exit status: 1
Duration: 7.90551400185
stdout:
creating backing nbd image /tmp/nbd_image.img
Image path:/tmp/nbd_image.img
Mount point: /mnt/nbd-test-13924
Date: Fri Mar 29 06:06:04 UTC 2019
Host: baltar
Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
Machine: baltar ppc64le ppc64le
CPUs online: 160
CPUs total:160
Page size: 65536
Pages avail: 1904339
Pages total: 2089666
Free space:
Filesystem Size Used Avail Use% Mounted on
udev 61G 0 61G 0% /dev
tmpfs13G 12M 13G 1% /run
/dev/sda2 1.8T 11G 1.7T 1% /
tmpfs64G 0 64G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs64G 0 64G 0% /sys/fs/cgroup
tmpfs13G 0 13G 0% /run/user/1000
NBD device /dev/nbd0 created
found nbd export
NBD exports found:
test
starting client with NBD device /dev/nbd0
Negotiation: ..size = 128MB
creating ext4 on /dev/nbd0
mkfs on /dev/nbd0 succeeded after 0 attempt(s)
checking ext4 on /dev/nbd0
fsck from util-linux 2.31.1
/dev/nbd0: clean, 11/32768 files, 9787/131072 blocks
mount:
/dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered)
mounted on /dev/nbd0
free:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nbd0 122835 1550112111 2% /mnt/nbd-test-13924
creating large file /mnt/nbd-test-13924/largefile
-rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile
free:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-13924
removing file /mnt/nbd-test-13924/largefile
unmounting /mnt/nbd-test-13924
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[ 694.662746] creating backing nbd image /tmp/nbd_image.img
[ 695.821047] NBD device /dev/nbd0 created
[ 696.271555] found nbd export
[ 697.318393] starting client with NBD device /dev/nbd0
[ 697.323210] creating ext4 on /dev/nbd0
[ 697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
[ 697.821953] checking ext4 on /dev/nbd0
[ 697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode.
Opts: (null)
[ 697.925418] mounted on /dev/nbd0
[ 697.927107] creating large file /mnt/nbd-test-13924/largefile
[ 698.839327] removing file /mnt/nbd-te
[Kernel-packages] [Bug 1824520] [NEW] Unable to turn off the airplane mode with wireless key on Dell M3800
Public bug reported: The airplane mode can be activated with the wireless key combination on this laptop (fn + PrtScn) You will see the "Airplane mode enabled" notification, and the BT / Wireless turned off accordingly. However the same key combination cannot turn the wireless back on. You will see the "Airplane mode disabled" notification followed by the "Airplane mode enabled" message. It feels a bit like a repeat-key issue. But the evtest shows the identical result: * Turn on the airplane mode: Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070280.383302, -- SYN_REPORT Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070280.383327, -- SYN_REPORT * Turn off the airplane mode: Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070325.562502, -- SYN_REPORT Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070325.562514, -- SYN_REPORT dmesg for turning on the airplane mode: Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4581] device (wlp6s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 6521 Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill Switch Status. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1 Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv6 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv4 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 10.101.46.102. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for fe80::bb23:69c3:d7b9:f6df on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for 10.101.46.102 on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: nl80211: deinit ifname=p2p-dev-wlp6s0 disabled_11b_rates=0 Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[1866]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded. Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[1866]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[1866]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-
[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Added verifiction-done tags for bionic and cosmic based on comments #17 and #18. ** Tags added: verification-done-bionic verification-done-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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in The Bionic Beaver: Confirmed Status in linux-firmware source package in Bionic: Fix Committed Status in The Cosmic Cuttlefish: Confirmed Status in linux-firmware source package in Cosmic: Fix Committed Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501001C | hcmd Dec 13 11:53:36 james-x1 kernel: [ 856.845072] iwlwifi :02:00.0: 0x00023008 | isr0 Dec 13 11:53:36 james-x1 kernel: [ 856.845075] iwlwifi :02:00.0: 0x000D | isr1 Dec 13 11:53:36 james-x1 kernel: [ 856.845077] iwlwifi :02:00.0: 0x08001802 | isr2 Dec 13 11:53:36 james-x1 kernel: [ 856.845080] iwlwifi :02:00.0: 0x0041FDC0 | isr3 Dec 13 11:53:36 james-x1 kernel: [ 856.845082] iwlwifi :02:00.0: 0x | isr4 Dec 13 11:53:36 james-x1 kernel: [ 856.845084] iwlwifi :02:00.0: 0x00580118 | last cmd Id Dec 13 11:53:36 james-x1 kernel: [ 856.845087] iwlwifi :02:00.0: 0x | wait_event Dec 13 11:53:36 james-x1 kernel: [ 856.845089] iwlwifi :02:00.0: 0x76DD | l2p_control Dec 13 11:53:36 james-x1 kernel: [ 856.845091] iwlwifi :02:00.0: 0x0020 | l2p_duration Dec 13 11:53:36 james-x1 kernel: [ 856.845094] iwlwifi :02:00.0: 0x | l2p_mhvalid Dec 13 11:53:36 james-x1 kernel: [ 856.845096] iwlwifi :02:00.0: 0x00A0 | l2p_addr_match Dec 13 11:53:36 james-x1 kernel: [ 856.845099] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Dec 13 11:53:36 james-x1 kernel: [ 856.845101] iwlwifi :02:00.0: 0x22040707 | timestamp Dec 13 11:53:36 james-x1 kernel: [ 856.845103] iwlwifi :02:00.0: 0x6070
[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully
Thanks for verifying on cosmic! Looks like verification for bionic is still missing however. -- 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/1794055 Title: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: Missing firmware for nouveau is causing errors to appear in dmesg. Fix: Add missing firmware files from upstream linux-firmware. Test Case: Confirm that errors in dmesg are gone once new firmware files are present. Regression Potential: New and updated firmware always has potential to cause regressions, however this firmware has been in disco for several months with no reported issues. --- == Comment: #0 - Kalpana Shetty - 2018-09-15 23:55:13 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com ---uname output--- root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Witherspoon DD2.2 LC Steps: 1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS 2. Boot the OS ---> PASS but error thrown on the console related open source NVIDIA driver. [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe] Ubuntu, with Linux 4.18.0-7-generic (recovery mode) Ubuntu, with Linux 4.18.0-7-generic Ubuntu [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061] Ubuntu, with Linux 4.18.0-7-generic (recovery mode) * Ubuntu, with Linux 4.18.0-7-generic Ubuntu System information System configuration System status log Language Rescan devices Retrieve config from URL Plugins (0) Exit to shell ?? Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [ 57.513329] kexec_core: Starting new kernel [ 149.358703978,5] OPAL: Switch to big-endian OS [ 153.355498935,5] OPAL: Switch to little-endian OS [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.132733] vio vio: uevent: failed to send synthetic uevent [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22 [ 19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM] [ 19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx [ 19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22 [ 34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM] [ 34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx [ 34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22 [ 49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM] [ 49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx [ 49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22 [ 64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM] [ 64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx [ 65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22 [ 80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM] [ 80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx [ 80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22 [ 95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM] /dev/nvme0n1p2: recovering journal /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks -.mount kmod-static-nodes.service dev-hugepages.mount dev-mqueue.mount sys-kernel-debug.mount ufw.service lvm2-lvmetad.service systemd-remount-fs.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service lvm2-monitor.service finalrd.service console-setup.service swapfile.swap ebtables.service systemd-udevd.service systemd-journald.service systemd-journal-flush.service systemd-tmpfiles-setup.s
[Kernel-packages] [Bug 1824525] [NEW] Right click does not work on Dell M3800 Synaptics clickpad
Public bug reported: Right click on the clickpad does not work. Looks like the right button has been recognized as a left button. Left click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448142, (155,161), root:(1986,1189), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448282, (155,161), root:(1986,1189), state 0x100, button 1, same_screen YES Left click in evtest: Event: time 1555071929.858424, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071929.858424, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071929.906290, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071930.044313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 Right click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415207, (175,58), root:(2006,1086), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415367, (175,58), root:(2006,1086), state 0x100, button 1, same_screen YES Right click in evtest: Event: time 1555071932.491732, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071932.491732, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071932.549622, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071932.720730, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1660 F pulseaudio /dev/snd/controlC1: u 1660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 08:20:54 2019 InstallationDate: Installed on 2019-04-03 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Dell Precision M3800 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-4.18.0-17-generic root=UUID=62683a38-d516-49dd-9344-9a248877fb9b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1824525 Title: Right click does not work on Dell M3800 Synaptics clickpad Status in linux package in Ubuntu: Confirmed Bug description: Right click on the clickpad does not work. Looks like the right button has been recognized as a left button. Left click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448142, (155,161), root:(1986,1189), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448282, (155,161), root:(1986,1189), state 0x100, button 1, same_screen YES Left click in evtest: Event: time 1555071929.858424, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071929.858424, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071929.906290, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071930.044313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 325 (BT
[Kernel-packages] [Bug 1824525] 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/1824525 Title: Right click does not work on Dell M3800 Synaptics clickpad Status in linux package in Ubuntu: Confirmed Bug description: Right click on the clickpad does not work. Looks like the right button has been recognized as a left button. Left click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448142, (155,161), root:(1986,1189), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448282, (155,161), root:(1986,1189), state 0x100, button 1, same_screen YES Left click in evtest: Event: time 1555071929.858424, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071929.858424, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071929.906290, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071930.044313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 Right click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415207, (175,58), root:(2006,1086), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415367, (175,58), root:(2006,1086), state 0x100, button 1, same_screen YES Right click in evtest: Event: time 1555071932.491732, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071932.491732, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071932.549622, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071932.720730, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1660 F pulseaudio /dev/snd/controlC1: u 1660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 08:20:54 2019 InstallationDate: Installed on 2019-04-03 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Dell Precision M3800 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-4.18.0-17-generic root=UUID=62683a38-d516-49dd-9344-9a248877fb9b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824520] 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/1824520 Title: Unable to turn off the airplane mode with wireless key on Dell M3800 Status in linux package in Ubuntu: Confirmed Bug description: The airplane mode can be activated with the wireless key combination on this laptop (fn + PrtScn) You will see the "Airplane mode enabled" notification, and the BT / Wireless turned off accordingly. However the same key combination cannot turn the wireless back on. You will see the "Airplane mode disabled" notification followed by the "Airplane mode enabled" message. It feels a bit like a repeat-key issue. But the evtest shows the identical result: * Turn on the airplane mode: Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070280.383302, -- SYN_REPORT Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070280.383327, -- SYN_REPORT * Turn off the airplane mode: Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070325.562502, -- SYN_REPORT Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070325.562514, -- SYN_REPORT dmesg for turning on the airplane mode: Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4581] device (wlp6s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 6521 Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill Switch Status. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1 Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv6 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv4 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 10.101.46.102. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for fe80::bb23:69c3:d7b9:f6df on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for 10.101.46.102 on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: nl80211: deinit ifname=p2p-dev-wlp6s0 disabled_11b_rates=0 Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[1866]: Failed to StopUnit service: GDBus.Error:org
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Kai-Heng Feng, I can confirm on my XPS 9370 that everything seems to be working on 5.10-rc3-mainline which includes that patches from #47, but does not seem to have patches from #65 and #66. I'll try compile these in when I get some time. Have the latter two patches (#65, #66) been submitted as I can't see them on the latest mainline kernel on kernel.org? Thanks for your help. -- You 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 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug 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: 1824383 - phase: Holding before Promote to Proposed - phase-changed: Friday, 12. April 2019 09:41 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 12. April 2019 12:41 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-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/1824382 Title: linux-oem-osp1: 5.0.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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1824383 phase: Ready for Promote to Proposed phase-changed: Friday, 12. April 2019 12:41 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822987] Re: nouveau timeout with nvidia GTX 1060
With some more test, it looks like bug 1821027 was caused by userspace, not 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/1822987 Title: nouveau timeout with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 003606e0 [ 15.714873] DR0: DR1: DR2: [ 15.714874] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.714874] Call Trace: [ 15.714893] acr_r352_bootstrap+0x1a9/0x2b0 [nouveau] [ 15.714910] acr_r352_reset+0x39/0x230 [nouveau] [ 15.714926] nvkm_secboot_reset+0x35/0x70 [nouveau] [ 15.714944] gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau] [ 15.714962] ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau] [ 15.714979] gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau] [ 15.714997] gf100_gr_init+0x563/0x590 [nouveau] [ 15.715015] gf100_gr_init_+0x5b/0x60 [nouveau] [ 15.715032] nvkm_gr_init+0x1d/0x20 [nouveau] [ 15.715041] nvkm_engine_init+0xb9/0x1f0 [nouveau] [ 15.715052] nvkm_subdev_init+0xbc/0x210 [nouveau] [ 15.715061] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 15.715071] nvkm_engine_ref+0x13/0x20 [nouveau] [ 15.715081] nvkm_ioctl_new+0x129/0x220 [nouveau] [ 15.715098] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 15.715115] ? gf100_gr_dtor+0xd0/0xd0 [nouveau] [ 15.715125] nvkm_ioctl+0xe2/0x180 [nouveau] [ 15.715143] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 15.715152] nvif_
[Kernel-packages] [Bug 1821027] Re: Feedback on the Dell G7 7588 Boot Time
OK, I have this tested again with OS installed on the NVME. It looks like something in the userspace is the cause: :: 4.15.0-20-generic-analyze :: Startup finished in 8.429s (firmware) + 3.576s (loader) + 2.412s (kernel) + 23.634s (userspace) = 38.052s graphical.target reached after 23.627s in userspace :: 4.15.0-30-generic-analyze :: Startup finished in 8.268s (firmware) + 3.529s (loader) + 2.879s (kernel) + 23.184s (userspace) = 37.861s graphical.target reached after 23.164s in userspace :: 4.15.0-42-generic-analyze :: Startup finished in 8.252s (firmware) + 3.513s (loader) + 1.957s (kernel) + 23.106s (userspace) = 36.829s graphical.target reached after 23.087s in userspace :: 4.15.0-45-generic-analyze :: Startup finished in 8.257s (firmware) + 3.528s (loader) + 1.982s (kernel) + 23.070s (userspace) = 36.837s graphical.target reached after 23.050s in userspace :: 4.15.0-46-generic-analyze :: Startup finished in 9.794s (firmware) + 3.805s (loader) + 2.984s (kernel) + 41.040s (userspace) = 57.625s graphical.target reached after 24.048s in userspace :: 4.15.0-47-generic-analyze :: Startup finished in 9.950s (firmware) + 3.694s (loader) + 3.074s (kernel) + 41.436s (userspace) = 58.156s graphical.target reached after 23.965s in userspace >From a side-by-side comparison, it's fwupd.service: ==> 4.15.0-42-generic-blame <== 20.720s plymouth-quit-wait.service 6.037s NetworkManager-wait-online.service 4.667s bolt.service ==> 4.15.0-45-generic-blame <== 20.682s plymouth-quit-wait.service 6.037s NetworkManager-wait-online.service 4.466s bolt.service ==> 4.15.0-46-generic-blame <== 26.178s fwupd.service 20.367s plymouth-quit-wait.service 6.220s NetworkManager-wait-online.service ==> 4.15.0-47-generic-blame <== 26.287s fwupd.service 20.386s plymouth-quit-wait.service 6.208s NetworkManager-wait-online.service ** Summary changed: - Feedback on the Dell G7 7588 Boot Time + fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821027 Title: fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Incomplete Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/oseMTobN/920-pi2-kernel-440-1107115-86 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- 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/1822828 Title: linux-raspi2: 4.4.0-1107.115 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822834 phase: Signoff phase-changed: Thursday, 11. April 2019 13:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824383] Re: linux: 5.0.0-11.12 -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 1824381 (bionic/linux-hwe-edge), bug 1824382 (bionic/linux-oem-osp1) derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 (linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Thursday, 11. April 2019 15:43 UTC reason: prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824383 Title: linux: 5.0.0-11.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New 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 1824381 (bionic/linux-hwe-edge), bug 1824382 (bionic/linux-oem-osp1) derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 (linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Thursday, 11. April 2019 15:43 UTC reason: prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Thursday, 11. April 2019 18:10 UTC reason: prepare-package-meta: Pending -- package tag not yet published - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1824377 Title: linux-gcp: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: New 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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Thursday, 11. April 2019 18:10 UTC reason: prepare-package-meta: Pending -- package tag not yet published promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -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 -- kernel-stable-master-bug: 1824383 phase: Promote to Proposed phase-changed: Friday, 12. April 2019 02:10 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1824376 Title: linux-azure: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: New 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 -- kernel-stable-master-bug: 1824383 phase: Promote to Proposed phase-changed: Friday, 12. April 2019 02:10 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821027] Re: fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588
** 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/1821027 Title: fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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: 1822834 phase: Signoff phase-changed: Thursday, 11. April 2019 13:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected channel(s): + arch=armhf:channel=latest/candidate:rev=86' 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/1822828 Title: linux-raspi2: 4.4.0-1107.115 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822834 phase: Signoff phase-changed: Thursday, 11. April 2019 13:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected channel(s): arch=armhf:channel=latest/candidate:rev=86' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
Submitted patch to mailing list for next SRU cycle. ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu Cosmic) 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/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: In Progress Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
We believe that should be fixed by those commits * https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/e807cbd8 client: Fix bluetooth_client_set_trusted() not working (that would probably explain the LinkKey section missing from the config) * https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/4f1e0b35 ' lib: Always try to pair pointer devices ' Those fixes are in 3.32 in disco and I've uploaded a bionic SRU now https://launchpadlibrarian.net/418989286/gnome-bluetooth_3.28.0-2ubuntu0.2_source.changes (the SRU needs to be reviewed/accepted next) ** Description changed: + * Impact + Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting + + * Test case + Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles + + * Regression potential + The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd + + -- + This affects at least 2 different bluetooth mice(both logitech) - The behavior is that initial config when using the gui works but that the resulting + The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-bluetooth (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pack
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
In the mean time I've installed KDE Neon which is supposed to be based on Ubuntu 18.04. I'm running kernel version 5.0.1 and still got the disconnect problem with my Asus FX503VD with the touchpad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I've backported the is_trusted/pair pointer devices changes in a bionic SRU and used bug #1779289 for the update (the bug here seems like it's not only about that) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Invalid Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
Some issues have been fixed on Disco so it would be worth trying there. I've backported the upstream_trusted/pair pointer devices changes in a bionic SRU and used bug #1779289 for the update (the bug here seems like it's not only about that though) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
When I encounter situation like this, I alway do another "bisection in bisection" to find the fix commit, then cherry-pick the fix to continue the original bisection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822682] Re: nvidia driver issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Confirmed -- 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/1822682 Title: nvidia driver issues Status in linux-firmware package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Confirmed Status in linux-signed-hwe source package in Bionic: Confirmed Status in linux-firmware source package in Cosmic: Confirmed Status in linux-signed-hwe source package in Cosmic: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Kernel: Linux 4.18.0-15-generic Intel Core i7-7700HQ + GeForce 1050Ti after: sudo update-initramfs -u (i'm using this command after installing fresh Ubuntu because it can't reboot correctly) I get : update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau Had no such trouble on Ubuntu 18.04.01 with older kernel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 00:18:33 2019 InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822682] Re: nvidia driver issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Cosmic) Status: New => Confirmed -- 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/1822682 Title: nvidia driver issues Status in linux-firmware package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Confirmed Status in linux-signed-hwe source package in Bionic: Confirmed Status in linux-firmware source package in Cosmic: Confirmed Status in linux-signed-hwe source package in Cosmic: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Kernel: Linux 4.18.0-15-generic Intel Core i7-7700HQ + GeForce 1050Ti after: sudo update-initramfs -u (i'm using this command after installing fresh Ubuntu because it can't reboot correctly) I get : update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau Had no such trouble on Ubuntu 18.04.01 with older kernel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 00:18:33 2019 InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822682] Re: nvidia driver issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe (Ubuntu Bionic) Status: New => Confirmed -- 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/1822682 Title: nvidia driver issues Status in linux-firmware package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Confirmed Status in linux-signed-hwe source package in Bionic: Confirmed Status in linux-firmware source package in Cosmic: Confirmed Status in linux-signed-hwe source package in Cosmic: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Kernel: Linux 4.18.0-15-generic Intel Core i7-7700HQ + GeForce 1050Ti after: sudo update-initramfs -u (i'm using this command after installing fresh Ubuntu because it can't reboot correctly) I get : update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau Had no such trouble on Ubuntu 18.04.01 with older kernel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 00:18:33 2019 InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822682] Re: nvidia driver issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe (Ubuntu Cosmic) Status: New => Confirmed -- 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/1822682 Title: nvidia driver issues Status in linux-firmware package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Confirmed Status in linux-signed-hwe source package in Bionic: Confirmed Status in linux-firmware source package in Cosmic: Confirmed Status in linux-signed-hwe source package in Cosmic: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Kernel: Linux 4.18.0-15-generic Intel Core i7-7700HQ + GeForce 1050Ti after: sudo update-initramfs -u (i'm using this command after installing fresh Ubuntu because it can't reboot correctly) I get : update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau Had no such trouble on Ubuntu 18.04.01 with older kernel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 00:18:33 2019 InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822682] Re: nvidia driver issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Confirmed -- 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/1822682 Title: nvidia driver issues Status in linux-firmware package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Confirmed Status in linux-signed-hwe source package in Bionic: Confirmed Status in linux-firmware source package in Cosmic: Confirmed Status in linux-signed-hwe source package in Cosmic: Confirmed Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Kernel: Linux 4.18.0-15-generic Intel Core i7-7700HQ + GeForce 1050Ti after: sudo update-initramfs -u (i'm using this command after installing fresh Ubuntu because it can't reboot correctly) I get : update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau Had no such trouble on Ubuntu 18.04.01 with older kernel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 00:18:33 2019 InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824383] Re: linux: 5.0.0-11.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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 1824381 (bionic/linux-hwe-edge), bug 1824382 (bionic/linux-oem-osp1) derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 (linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Thursday, 11. April 2019 15:43 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: + automated-testing: Ongoing -- testing in progress prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + regression-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/1824383 Title: linux: 5.0.0-11.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: New 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 1824381 (bionic/linux-hwe-edge), bug 1824382 (bionic/linux-oem-osp1) derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 (linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 (linux-snapdragon) -- swm properties -- phase: Packaging phase-changed: Thursday, 11. April 2019 15:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Thursday, 11. April 2019 18:10 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: + automated-testing: Ongoing -- testing in progress prepare-package-meta: Pending -- package tag not yet published - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + regression-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/1824377 Title: linux-gcp: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-gcp package in Ubuntu: New 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 -- kernel-stable-master-bug: 1824383 phase: Packaging phase-changed: Thursday, 11. April 2019 18:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress prepare-package-meta: Pending -- package tag not yet published regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824376] Re: linux-azure: 5.0.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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 -- kernel-stable-master-bug: 1824383 - phase: Promote to Proposed - phase-changed: Friday, 12. April 2019 02:10 UTC + phase: Testing + phase-changed: Friday, 12. April 2019 14:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff -- 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/1824376 Title: linux-azure: 5.0.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in linux-azure package in Ubuntu: New 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 -- kernel-stable-master-bug: 1824383 phase: Testing phase-changed: Friday, 12. April 2019 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Also to minimize the gamut of potential regressions, only includes necessary modules, e.g. PCI and xHCI. Things like graphics and network driver can be excluded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702961] Re: Intel wifi instability with 4.10 and Intel Device 24fd
I'm going to close out this bug, as I have not experienced this since moving to 18.04. ** Changed in: linux (Ubuntu) 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/1702961 Title: Intel wifi instability with 4.10 and Intel Device 24fd Status in linux package in Ubuntu: Fix Released Bug description: Wifi drops and has to reconnect regularly. This is on a Dell Precision 5520. Kernel warnings in log include. [ cut here ] WARNING: CPU: 4 PID: 1042 at /build/linux-hwe-dbNd9L/linux-hwe-4.10.0/drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1523 iwl_mvm_rm_sta+0x3ea/0x460 [iwlmvm] Modules linked in: ccm rfcomm bbswitch(OE) bnep snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch joydev i2c_designware_platform i2c_designware_core dell_wmi mxm_wmi nls_iso8859_1 dell_rbtn dell_laptop dell_smbios dcdbas dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc iwlmvm aesni_intel mac80211 aes_x86_64 crypto_simd glue_helper cryptd iwlwifi cfg80211 rtsx_pci_ms memstick snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm input_leds snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore uvcvideo videobuf2_vmalloc videobuf2_memops idma64 videobuf2_v4l2 virt_dma videobuf2_core videodev media btusb btrtl mei_me shpchp mei processor_thermal_device intel_lpss_pci intel_soc_dts_iosf intel_pch_thermal hci_uart btbcm btqca btintel bluetooth dell_smo8800 wmi intel_hid intel_lpss_acpi nvidia_uvm(POE) sparse_keymap mac_hid intel_lpss tpm_crb int3400_thermal int3403_thermal acpi_als int340x_thermal_zone acpi_thermal_rel kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport autofs4 i915 rtsx_pci_sdmmc nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm nvme ahci rtsx_pci nvme_core libahci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes CPU: 4 PID: 1042 Comm: wpa_supplicant Tainted: P OE 4.10.0-27-generic #30~16.04.2-Ubuntu Hardware name: Dell Inc. Precision 5520/0R6JFH, BIOS 1.3.4 06/08/2017 Call Trace: dump_stack+0x63/0x90 __warn+0xcb/0xf0 warn_slowpath_null+0x1d/0x20 iwl_mvm_rm_sta+0x3ea/0x460 [iwlmvm] iwl_mvm_mac_sta_state+0x40a/0x600 [iwlmvm] drv_sta_state+0x8a/0x460 [mac80211] __sta_info_destroy_part2+0x17a/0x1b0 [mac80211] __sta_info_flush+0x103/0x1b0 [mac80211] ieee80211_set_disassoc+0xba/0x3f0 [mac80211] ieee80211_mgd_auth+0x26c/0x3c0 [mac80211] ? cfg80211_get_bss+0x1c5/0x2d0 [cfg80211] ieee80211_auth+0x18/0x20 [mac80211] cfg80211_mlme_auth+0x101/0x210 [cfg80211] nl80211_authenticate+0x30b/0x370 [cfg80211] genl_family_rcv_msg+0x1db/0x3b0 genl_rcv_msg+0x59/0xa0 ? genl_notify+0x80/0x80 netlink_rcv_skb+0xa4/0xc0 genl_rcv+0x28/0x40 netlink_unicast+0x18c/0x240 netlink_sendmsg+0x2fb/0x3a0 ? aa_sock_msg_perm+0x61/0x150 sock_sendmsg+0x38/0x50 ___sys_sendmsg+0x2c2/0x2d0 ? destroy_inode+0x3b/0x60 ? evict+0x136/0x1a0 ? iput+0x1bb/0x240 ? __dentry_kill+0x110/0x160 ? dput+0x214/0x250 ? mntput+0x24/0x40 ? __fput+0x190/0x220 __sys_sendmsg+0x54/0x90 SyS_sendmsg+0x12/0x20 entry_SYSCALL_64_fastpath+0x1e/0xad RIP: 0033:0x7f6d6dd04450 RSP: 002b:7ffcd1f168b8 EFLAGS: 0246 ORIG_RAX: 002e RAX: ffda RBX: 0004 RCX: 7f6d6dd04450 RDX: RSI: 7ffcd1f16940 RDI: 0007 RBP: 562488dd1adc R08: R09: 00df R10: 1000 R11: 0246 R12: 562488dd1adc R13: 562488dd4550 R14: R15: ---[ end trace 24fe098f56796fbc ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2 [modified: boot/vmlinuz-4.10.0-27-generic] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 7 11:25:55 2017 InstallationDate: Installed on 2017-07-06 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170706) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824525] Re: Right click does not work on Dell M3800 Synaptics clickpad
[2.536487] psmouse serio1: synaptics: Your touchpad (PNP: DLL060d PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. It may want to use SMBus (i.e. i2c_i801). Try removing it from blacklist, or upgrade kmod in disco-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/1824525 Title: Right click does not work on Dell M3800 Synaptics clickpad Status in linux package in Ubuntu: Confirmed Bug description: Right click on the clickpad does not work. Looks like the right button has been recognized as a left button. Left click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448142, (155,161), root:(1986,1189), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2448282, (155,161), root:(1986,1189), state 0x100, button 1, same_screen YES Left click in evtest: Event: time 1555071929.858424, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071929.858424, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071929.906290, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071930.044313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071930.077387, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 Right click in xev: ButtonPress event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415207, (175,58), root:(2006,1086), state 0x0, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x321, root 0x191, subw 0x0, time 2415367, (175,58), root:(2006,1086), state 0x100, button 1, same_screen YES Right click in evtest: Event: time 1555071932.491732, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1555071932.491732, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1 Event: time 1555071932.549622, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1555071932.720730, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1555071932.747618, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1660 F pulseaudio /dev/snd/controlC1: u 1660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 08:20:54 2019 InstallationDate: Installed on 2019-04-03 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Dell Precision M3800 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-4.18.0-17-generic root=UUID=62683a38-d516-49dd-9344-9a248877fb9b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824520] Re: Unable to turn off the airplane mode with wireless key on Dell M3800
Please attach full dmesg and `rfkill list` when this issue happens, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824520 Title: Unable to turn off the airplane mode with wireless key on Dell M3800 Status in linux package in Ubuntu: Confirmed Bug description: The airplane mode can be activated with the wireless key combination on this laptop (fn + PrtScn) You will see the "Airplane mode enabled" notification, and the BT / Wireless turned off accordingly. However the same key combination cannot turn the wireless back on. You will see the "Airplane mode disabled" notification followed by the "Airplane mode enabled" message. It feels a bit like a repeat-key issue. But the evtest shows the identical result: * Turn on the airplane mode: Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070280.383302, -- SYN_REPORT Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070280.383327, -- SYN_REPORT * Turn off the airplane mode: Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070325.562502, -- SYN_REPORT Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070325.562514, -- SYN_REPORT dmesg for turning on the airplane mode: Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4581] device (wlp6s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 6521 Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill Switch Status. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1 Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv6 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv4 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 10.101.46.102. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for fe80::bb23:69c3:d7b9:f6df on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for 10.101.46.102 on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: nl80211: deinit ifname=p2p-dev-wlp6s0 disabled_11b_rates=0 Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[1866]: Failed to StopUnit service: GDBus.Error:org.freedesktop.syste
[Kernel-packages] [Bug 1824546] [NEW] Intel N3060 booting into black screen with 5.0 kernel
You have been subscribed to a public bug: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Intel N3060 booting into black screen with 5.0 kernel https://bugs.launchpad.net/bugs/1824546 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] 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 1824546 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug 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: Holding before Promote to Proposed - phase-changed: Thursday, 11. April 2019 09:07 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 12. April 2019 15:29 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-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/1822810 Title: linux-ibm-gt: 4.15.0-1019.21 -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 promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1822820 phase: Ready for Promote to Proposed phase-changed: Friday, 12. April 2019 15:29 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
The latest i2c-amd-mp2 driver will be included in next Ubuntu Bionic, Cosmic and Disco kernel release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/IDyzIdvg/921-pi- kernel-4150-103436-27-18-pi3 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- 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/1822802 Title: linux-raspi2: 4.15.0-1034.36 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822820 phase: Signoff phase-changed: Thursday, 11. April 2019 15:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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: 1822820 phase: Signoff phase-changed: Thursday, 11. April 2019 15:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): + arch=arm64:channel=18-pi3/candidate:rev=28 arch=armhf:channel=18-pi3/candidate:rev=27 + arch=armhf:channel=18-cm3/candidate:rev=27 arch=armhf:channel=18-pi2/candidate:rev=27' 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/1822802 Title: linux-raspi2: 4.15.0-1034.36 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822820 phase: Signoff phase-changed: Thursday, 11. April 2019 15:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): arch=arm64:channel=18-pi3/candidate:rev=28 arch=armhf:channel=18-pi3/candidate:rev=27 arch=armhf:channel=18-cm3/candidate:rev=27 arch=armhf:channel=18-pi2/candidate:rev=27' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel
apport information ** Tags added: apport-collected ** Description changed: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: john 1085 F pulseaudio + DistroRelease: Ubuntu 19.04 + HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 + InstallationDate: Installed on 2016-08-27 (957 days ago) + InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:07dc Intel Corp. + Bus 001 Device 003: ID 064e:9404 Suyin Corp. + Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Acer Aspire one 1-431 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 + 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-4.18.0-16-generic N/A + linux-backports-modules-4.18.0-16-generic N/A + linux-firmware 1.178 + Tags: disco + Uname: Linux 4.18.0-16-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 12/28/2015 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V1.10 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: Oxford + dmi.board.vendor: Acer + dmi.board.version: V1.10 + dmi.chassis.type: 10 + dmi.chassis.vendor: Acer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: + dmi.product.family: BSW + dmi.product.name: Aspire one 1-431 + dmi.product.sku: AO1-431_106D_1.10 + dmi.product.version: V1.10 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255230/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-
[Kernel-packages] [Bug 1824546] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255238/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255231/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255241/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255239/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255232/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255235/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255234/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255233/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255240/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255237/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1824546/+attachment/5255236/+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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Incomplete Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824306] Re: test_530_config_binfmt_aout in ubuntu_qrt_kernel_security failed
I messed up when writing the test and forgot to consider that
CONFIG_BINFMT_AOUT is specific to i386. I've fixed that in QRT:
https://git.launchpad.net/qa-regression-
testing/commit/?id=6e659984b07987dd24acf5872d408afafbdb6510
I'm going to mark this bug as invalid since those test failures
shouldn't have happened.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824306
Title:
test_530_config_binfmt_aout in ubuntu_qrt_kernel_security failed
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux source package in Cosmic:
Invalid
Bug description:
This is a new test case
def test_530_config_binfmt_aout(self):
'''Ensure BINFMT_AOUT is disabled (LP: #1818552)'''
expected = False
if not self.kernel_at_least('5.0'):
expected = True
self.assertKernelConfig('BINFMT_AOUT', expected)
For kernel < 5.0 it will expect this option to be enabled.
AssertionError: BINFMT_AOUT option was expected to be set in the
kernel config
Seems that Tyler is working on this in bug 1818552
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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: 1822834 phase: Signoff phase-changed: Thursday, 11. April 2019 13:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected channel(s): - arch=armhf:channel=latest/candidate:rev=86' 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/1822828 Title: linux-raspi2: 4.4.0-1107.115 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822834 phase: Signoff phase-changed: Thursday, 11. April 2019 13:09 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824553] [NEW] Bionic update: update stable patchset for fuse 2019-04-12
Public bug reported: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Andrea Righi (arighi) Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824553 Title: Bionic update: update stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel
** 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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
On my system, I found that the immediate cause of those messages was running apcupsd, with the default configuration of trying to talk over a serial cable, but without a UPS connected to it. Even if it was otherwise configured for USB, I also had to remove the "DEVICE /dev/ttyS0" line to fix the IRQ errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 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-4.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824553] Re: Bionic update: update stable patchset for fuse 2019-04-12
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Assignee: Andrea Righi (arighi) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824553 Title: Bionic update: update stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824553] Re: Bionic update: update stable patchset for fuse 2019-04-12
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824553 Title: Bionic update: update stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel
Workaround found at https://wiki.archlinux.org/index.php/Intel_graphics#Xorg_configuration ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (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/1824546 Title: Intel N3060 booting into black screen with 5.0 kernel Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots, staying on a black screen with stable cursor. I can however select 4.18 kernel from grub and it boots perfectly. I am using Intel Celeron N3060 CPU. Please find attached the dmesg output. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1085 F pulseaudio DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69 InstallationDate: Installed on 2016-08-27 (957 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9404 Suyin Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire one 1-431 Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 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-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Oxford dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire one 1-431 dmi.product.sku: AO1-431_106D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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: 1822820 phase: Signoff phase-changed: Thursday, 11. April 2019 15:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): - arch=arm64:channel=18-pi3/candidate:rev=28 arch=armhf:channel=18-pi3/candidate:rev=27 - arch=armhf:channel=18-cm3/candidate:rev=27 arch=armhf:channel=18-pi2/candidate:rev=27' 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/1822802 Title: linux-raspi2: 4.15.0-1034.36 -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-signing-to-proposed series: Invalid 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 snap-certification-testing series: Fix Released 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822820 phase: Signoff phase-changed: Thursday, 11. April 2019 15:35 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824553] Re: Bionic update: upstream stable patchset for fuse 2019-04-12
** Summary changed: - Bionic update: update stable patchset for fuse 2019-04-12 + Bionic update: upstream stable patchset for fuse 2019-04-12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824553 Title: Bionic update: upstream stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824559] [NEW] Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
Public bug reported: Hello, I have an issue with a lenovo yoga mouse. This mouse has 2 working mode either bluetooth or with a provided usb dongle. USB dongle works fine, but bluetooth don't. Cursor is slow and laggy. "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse while USB mode and other mouse reports 125Hz. Polling speed is too slow. I tried different howto suggesting to change usbhid mousepoll value => does not help. The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid killed my other mouse, but not the lenovo, while modprobe -r btusb killed the lenovo). I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and an older dell Precision M6400 16.04 kernel 4.15). Bluetooth pairing works well, either with gnome bluetooth interface or with "bluetoothctl" Both laptops reports ~20-22Hz polling speed with evhz (and same laggy behavior) I also tried 2 bluetooth interface on the XPS13 9370 : the integrated bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the Sabrent, I have switched off integrated bluetooth with rfkill). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 12 18:05:16 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-05-10 (337 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.7-050007-generic root=UUID=d36c5071-0243-427d-8fe1-7416c3b775f1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2019-03-02 (40 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:8B:33:C6 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:12041 acl:294 sco:0 events:363 errors:0 TX bytes:8633 acl:76 sco:0 commands:171 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) Status in bluez package in Ubuntu: New Bug description: Hello, I have an issue with a lenovo yoga mouse. This mouse has 2 working mode either bluetooth or with a provided usb dongle. USB dongle works fine, but bluetooth don't. Cursor is slow and laggy. "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse while USB mode and other mouse reports 125Hz. Polling speed is too slow. I tried different howto suggesting to change usbhid mousepoll value => does not help. The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid killed my other mouse, but not the lenovo, while modprobe -r btusb killed the lenovo). I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and an older dell Precision M6400 16.04 kernel 4.15). Bluetooth pairing works well, either with gnome bluetooth interface or with "bluetoothctl" Both laptops reports ~20-22Hz polling speed with evhz (and same laggy behavior) I also tried 2 bluetooth interface on the XPS13 9370 : the integrated bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the Sabrent, I have switched off integrated bluetooth with rfkill). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 12 18:05:16 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-05-10 (337 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I have a freeze issue when it sits unused for about 15 minutes. The issue I found is that the Keychain is using a massive amount of system resources. I have launch a console session with alt+F# (which takes about 5 minutes to show), run top, and then kill the keychain process. Then the system responds like normal. This never happened with 18.04, only after upgrade to 18.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
