[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
This bug is also present on an X1 Carbon (gen 3). modprobe i2c-i801 after removing it from the blacklist.conf seems to solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793373] Re: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793373 Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Incomplete Bug description: I was trying run the OS updates and got the error above? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1897 F pulseaudio Date: Wed Sep 19 14:17:52 2018 DuplicateSignature: package:linux-image-extra-4.4.0-119-generic:4.4.0-119.143 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package linux-image-extra-4.4.0-119-generic (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=8b487a35-1a21-4674-9720-185dd8bfd41c InstallationDate: Installed on 2016-05-25 (847 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X540SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=1c9ef1ae-d7a6-4e81-b5c5-76f25af8c7ef ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2018-09-19 (0 days ago) dmi.bios.date: 11/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540SA.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540SA.207:bd11/25/2015:svnASUSTeKCOMPUTERINC.:pnX540SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X540SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780817] Re: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780817 Title: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic) Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When starting a nested VM in a Bionic VM, the "host" VM kernel panics following a simple drop to QEMU monitor by hitting A-c. For some reason kdump is unable to capture the kernel panic so I only have a screen capture of the panic. It also happens on the latest mainline kernel(4.18-rc4). It is fairly trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the following : qemu-system-x86_64 -enable-kvm \ -name balloontest \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 2048M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/home/caribou/balloon/efi.vars Use A-c to drop to QEMU monitor and . ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[ 267.784299] general protection fault: [#1] SMP PTI [ 267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 267.804312] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 267.811666] RIP: 0010:native_write_cr4+0x4/0x10 [ 267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006 [ 267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8 [ 267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0 [ 267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: [ 267.818625] R10: R11: R12: 00025040 [ 267.820130] R13: 0001 R14: R15: [ 267.821638] FS: () GS:8c01ffd8() knlGS: [ 267.823352] CS: 0010 DS: ES: CR0: 80050033 [ 267.824592] CR2: CR3: 00058c00a006 CR4: 003626e0 [ 267.826108] DR0: DR1: DR2: [ 267.827567] DR3: DR6: fffe0ff0 DR7: 0400 [ 267.828973] Call Trace: [ 267.829470] [ 267.829893] hardware_disable+0xaa/0xc0 [kvm_intel] [ 267.830897] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 267.831928] hardware_disable_nolock+0x2b/0x30 [kvm] [ 267.832912] flush_smp_call_function_queue+0x4c/0xf0 [ 267.833911] generic_smp_call_function_single_interrupt+0x13/0x30 [ 267.835121] smp_call_function_interrupt+0x36/0xd0 [ 267.836069] call_function_interrupt+0x84/0x90 [ 267.836950] [ 267.837396] RIP: 0010:native_safe_halt+0x6/0x10 [ 267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: ff03 [ 267.839698] RAX: acd97150 RBX: 0006 RCX: [ 267.840978] RDX: RSI: RDI: [ 267.842258] RBP: a2e1431afe80 R08: 0002 R09: [ 267.843554] R10: 00b3 R11: 00a6 R12: 0006 [ 267.844826] R13: R14: R15: [ 267.846107] ? __cpuidle_text_start+0x8/0x8 [ 267.846875] default_idle+0x20/0x100 [ 267.847533] arch_cpu_idle+0x15/0x20 [ 267.848186] default_idle_call+0x23/0x30 [ 267.848917] do_idle+0x172/0x1f0 [ 267.849516] cpu_startup_entry+0x73/0x80 [ 267.850255] start_secondary+0x1ab/0x200 [ 267.850971] secondary_startup_64+0xa5/0xb0 [ 267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0> [ 267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48 [ 268.848104] invalid opcode: [#2] SMP PTI [ 268.848524] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 n
[Kernel-packages] [Bug 1792209] Re: net: hns: Avoid hang when link is changed while handling packets
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792209 Title: net: hns: Avoid hang when link is changed while handling packets Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] If an admin uses ethtool to change the link speed or duplex setting while the hardware is still processing packets, a hardware hang may result. [Test Case] While traffic is in-progress, use ethtool to change link speed/duplex. [Fix] Fixes have been applied upstream: 455c4401fe7a5 net: hns: add netif_carrier_off before change speed and duplex 31fabbee8f5c6 net: hns: add the code for cleaning pkt in chip [Regression Risk] The only Ubuntu-supported system that uses this driver is the HiSilicon D05 board, on which the fix was explicitly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with X-AWS
I can reproduce this in 4.4.0-1067-aws, so this is not a regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1793451 Title: mlock203 test in ubuntu_ltp_syscalls failed with X-AWS Status in linux-aws package in Ubuntu: New Bug description: 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891 15:11:31 DEBUG| [stdout] cmdline="mlock203" 15:11:31 DEBUG| [stdout] contacts="" 15:11:31 DEBUG| [stdout] analysis=exit 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s 15:11:31 DEBUG| [stdout] mlock203.c:63: FAIL: Locking one memory again increased VmLck 15:11:31 DEBUG| [stdout] 15:11:31 DEBUG| [stdout] Summary: 15:11:31 DEBUG| [stdout] passed 0 15:11:31 DEBUG| [stdout] failed 1 15:11:31 DEBUG| [stdout] skipped 0 15:11:31 DEBUG| [stdout] warnings 0 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] initiation_status="ok" 15:11:31 DEBUG| [stdout] duration=0 termination_type=exited termination_id=1 corefile=no 15:11:31 DEBUG| [stdout] cutime=0 cstime=0 15:11:31 DEBUG| [stdout] <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78 ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144 Uname: Linux 4.4.0-1068-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 20 06:44:13 2018 Ec2AMI: ami-0e32ec5bc225539f5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1793451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker
4.4.0-1068.78 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad config 3, only spotted on t2.small, passed on the rest ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 1786729) inotify07 failed (bug 1774387), inotify08 (bug 1775784) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) quotactl01 failed (bug 1790028) mlock203 failed (bug 1793451) Skipped / blacklisted: * ubuntu_ltp * ubuntu_nbd_smoke_test * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test Note: ubuntu_ltp_syscalls test must be reviewed on the Jenkins server, the hang issue (bug 179) will prevent it from copy the test report ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793338 Title: Fix unusable NVIDIA GPU after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] NVIDIA GPU becomes unusable after S3. [Test] The NVIDIA GPU works well after applying this patch. [Fix] Rewrite 0 to Intel PCI bridge 'Prefetchable Base Upper 32 Bits'. This should be done by BIOS S3 code [1], but now the issue reappears, let's do the same via Linux PCI subsystem. [Regression Potential] Low. After applying this patch I haven't noticed any change on already working PCI devices. Also this patch is acked by PCI and ACPI maintainers, so we can be more confident. [1] https://bugzilla.kernel.org/show_bug.cgi?id=116851#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:Witherspoon:DD2.2 - Sysrq trigger disabled when writing to /proc/sysrq-trigger
This is not limited to ppc64el and at least applies to s390x, too. ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793369 Title: Ubuntu18.10:Witherspoon:DD2.2 - Sysrq trigger disabled when writing to /proc/sysrq-trigger Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: == Comment: #0 - Praveen K. Pandey - 2018-09-19 04:49:39 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled when writing to /proc/sysrq-trigger while testing kdump trying trigger kdump panic via /proc/sysrq-trigger it failed as : SysRq : This sysrq operation is disabled LOG: root@test:~# cat /proc/sys/kernel/sysrq 176 root@test:~# echo c > /proc/sysrq-trigger root@test:~# dmesg [ 380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status flags(0x2) [ 389.404239] sysrq: SysRq : This sysrq operation is disabled. root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6 CONFIG_MAGIC_SYSRQ_SERIAL=y root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq #kernel.sysrq=438 root@test:~# 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.18.0-7-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-7-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@test:~# Regards Praveen == Comment: #2 - Praveen K. Pandey - 2018-09-19 05:16:11 == when i enable in /etc/sysctl.conf it works . i append below value in sysctl.conf echo "kernel.sysrq = 1" >> /etc/sysctl.conf I think this is should be enable by default in ubuntu 18.10 as earlier ubuntu distro it has , not sure why it got removed as kdump mechanism require this . Praveen Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
What packages and versions have been tested during verification? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Triaged Bug description: SRU Request: [Impact] The driver package won't remove the blacklist file from /etc (/etc/modprobe.d/nvidia-340.conf), preventing nouveau from being loaded. [Test case] 1) Enable proposed, install the new nvidia-340 2) Uninstall nvidia-340 3) See if either /etc/modprobe.d/nvidia-340.conf or /lib/modprobe.d/nvidia-340.conf. [Regression potential] Low, since it should move a blacklist file from /etc to /lib __ Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
That should be good. I just like to have the latest mainline already tested in case upstream asks for it. I'll ping upstream and see what the next steps should be. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in Ubuntu: In Progress Status in openvswitch package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in openvswitch source package in Artful: Invalid Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Invalid Status in linux source package in Cosmic: In Progress Status in openvswitch source package in Cosmic: Invalid Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793461] [NEW] Improvements to the kernel source package preparation
Public bug reported: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Precise) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793221] Re: hns3: Retrieve RoCE MSI-X config from firmware
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793221 Title: hns3: Retrieve RoCE MSI-X config from firmware Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] MSI-X configuration is hardcoded in the hns3 driver, but the actual configuration may change across revisions. Query firmware for the MSI-X offset/numbers instead. [Test Case] Regression testing: Confirm that, on existing hardware, the same MSIs are allocated before and after the patch. grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.old grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.new diff -u msi.old msi.new [Fix] 375dd5e43212 net: hns3: Refine the MSIX allocation for PF 07acf909ee33 net: hns3: Fix MSIX allocation issue for VF [Regression Risk] Restricted to a single driver, only used on HiSilicon SoCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793461] 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 1793461 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 ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Precise) Status: New => Incomplete ** Changed in: linux (Ubuntu Trusty) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Incomplete Status in linux source package in Precise: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Aurelijus: please follow these steps for testing: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed nvidia-settings/bionic-proposed ** Description changed: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. - [Test Case] - 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 + 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia - [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. + + + _ + * Steps to test the updates: + + 1) Enable the bionic-proposed repositories + + 2) Create /etc/apt/preferences.d/proposed-updates with the following + content: + + Package: * + Pin: release a=bionic-proposed + Pin-Priority: 400 + + 3) Update the list of packages: + + sudo apt-get update + + 4) Install the packages from -proposed using the following command: + + sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed + ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed + nvidia-settings/bionic-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep.
[Kernel-packages] [Bug 1793451] [NEW] mlock203 test in ubuntu_ltp_syscalls failed with X-AWS
Public bug reported: 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891 15:11:31 DEBUG| [stdout] cmdline="mlock203" 15:11:31 DEBUG| [stdout] contacts="" 15:11:31 DEBUG| [stdout] analysis=exit 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s 15:11:31 DEBUG| [stdout] mlock203.c:63: FAIL: Locking one memory again increased VmLck 15:11:31 DEBUG| [stdout] 15:11:31 DEBUG| [stdout] Summary: 15:11:31 DEBUG| [stdout] passed 0 15:11:31 DEBUG| [stdout] failed 1 15:11:31 DEBUG| [stdout] skipped 0 15:11:31 DEBUG| [stdout] warnings 0 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] initiation_status="ok" 15:11:31 DEBUG| [stdout] duration=0 termination_type=exited termination_id=1 corefile=no 15:11:31 DEBUG| [stdout] cutime=0 cstime=0 15:11:31 DEBUG| [stdout] <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78 ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144 Uname: Linux 4.4.0-1068-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 20 06:44:13 2018 Ec2AMI: ami-0e32ec5bc225539f5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images package-from-proposed xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1793451 Title: mlock203 test in ubuntu_ltp_syscalls failed with X-AWS Status in linux-aws package in Ubuntu: New Bug description: 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891 15:11:31 DEBUG| [stdout] cmdline="mlock203" 15:11:31 DEBUG| [stdout] contacts="" 15:11:31 DEBUG| [stdout] analysis=exit 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s 15:11:31 DEBUG| [stdout] mlock203.c:63: FAIL: Locking one memory again increased VmLck 15:11:31 DEBUG| [stdout] 15:11:31 DEBUG| [stdout] Summary: 15:11:31 DEBUG| [stdout] passed 0 15:11:31 DEBUG| [stdout] failed 1 15:11:31 DEBUG| [stdout] skipped 0 15:11:31 DEBUG| [stdout] warnings 0 15:11:31 DEBUG| [stdout] <<>> 15:11:31 DEBUG| [stdout] initiation_status="ok" 15:11:31 DEBUG| [stdout] duration=0 termination_type=exited termination_id=1 corefile=no 15:11:31 DEBUG| [stdout] cutime=0 cstime=0 15:11:31 DEBUG| [stdout] <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78 ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144 Uname: Linux 4.4.0-1068-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 20 06:44:13 2018 Ec2AMI: ami-0e32ec5bc225539f5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1793451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793462] [NEW] linux-azure: fix getabis information
Public bug reported: The "debian.azure*/etc/getabis" files for all the azure kernel are missing some critical information. All the kernels are missing the following repo_list entry: http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/pool/main/l /linux-signed-azure While xenial/linux-azure and trusty/linux-azure are also missing "linux- modules" in package_prefixes. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: The "debian.azure*/etc/getabis" files for all the azure kernel are missing some critical information. All the kernels are missing the following repo_list entry: http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/pool/main/l - /linux-azure + /linux-signed-azure While xenial/linux-azure and trusty/linux-azure are also missing "linux- modules" in package_prefixes. -- 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/1793462 Title: linux-azure: fix getabis information Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-azure source package in Cosmic: New Bug description: The "debian.azure*/etc/getabis" files for all the azure kernel are missing some critical information. All the kernels are missing the following repo_list entry: http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/pool/main/l /linux-signed-azure While xenial/linux-azure and trusty/linux-azure are also missing "linux-modules" in package_prefixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1793462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793464] [NEW] Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel
Public bug reported: This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM node The test itself will pass, but the system will hang after a few second. Steps: 1. Deploy a node with 4.4 Xenial 2. Run the ubuntu_nbd_smoke_test If you have access to the console, you will see that this system actually bumped into a kernel panic: Unable to handle kernel pointer dereference in virtual kernel address space failing address: 03ff802c1000 TEID: 03ff802c1803 Fault in home space mode while using kernel ASCE. Log here: https://pastebin.ubuntu.com/p/dNmtvbGjmz/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-136-generic 4.4.0-136.162 ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144 Uname: Linux 4.4.0-136-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Sep 20 03:46:00 2018 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-136-generic N/A linux-backports-modules-4.4.0-136-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x third-party-packages xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793464 Title: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel Status in linux package in Ubuntu: New Bug description: This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM node The test itself will pass, but the system will hang after a few second. Steps: 1. Deploy a node with 4.4 Xenial 2. Run the ubuntu_nbd_smoke_test If you have access to the console, you will see that this system actually bumped into a kernel panic: Unable to handle kernel pointer dereference in virtual kernel address space failing address: 03ff802c1000 TEID: 03ff802c1803 Fault in home space mode while using kernel ASCE. Log here: https://pastebin.ubuntu.com/p/dNmtvbGjmz/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-136-generic 4.4.0-136.162 ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144 Uname: Linux 4.4.0-136-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Sep 20 03:46:00 2018 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-136-generic N/A linux-backports-modules-4.4.0-136-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770271] Re: VegaM support
cosmic has 4.18 already ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in mesa source package in Xenial: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: New Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
I built the next test kernel, up to the following commit: 84d28cc43f2d9820bd97e8dc428b00483322f660 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793463] [NEW] SRU: Enable middle button of touchpad on ThinkPad P72
Public bug reported: [Impact] ThinkPad P72 has 3 physical hardware button on touchpad. Middle button didn't work due to kernel mask it. [Fix] Add this button support by PNPID in kernel input driver. [Test Case] Touchpad left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: originate-from-1790805 sutton ** Tags added: originate-from-1790805 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793463 Title: SRU: Enable middle button of touchpad on ThinkPad P72 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] ThinkPad P72 has 3 physical hardware button on touchpad. Middle button didn't work due to kernel mask it. [Fix] Add this button support by PNPID in kernel input driver. [Test Case] Touchpad left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793463] 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 1793463 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793463 Title: SRU: Enable middle button of touchpad on ThinkPad P72 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] ThinkPad P72 has 3 physical hardware button on touchpad. Middle button didn't work due to kernel mask it. [Fix] Add this button support by PNPID in kernel input driver. [Test Case] Touchpad left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Should this also work with Kubuntu 18.04 with SDDM instead of GDM3? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793464] 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 1793464 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793464 Title: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel Status in linux package in Ubuntu: Incomplete Bug description: This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM node The test itself will pass, but the system will hang after a few second. Steps: 1. Deploy a node with 4.4 Xenial 2. Run the ubuntu_nbd_smoke_test If you have access to the console, you will see that this system actually bumped into a kernel panic: Unable to handle kernel pointer dereference in virtual kernel address space failing address: 03ff802c1000 TEID: 03ff802c1803 Fault in home space mode while using kernel ASCE. Log here: https://pastebin.ubuntu.com/p/dNmtvbGjmz/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-136-generic 4.4.0-136.162 ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144 Uname: Linux 4.4.0-136-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Sep 20 03:46:00 2018 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-136-generic N/A linux-backports-modules-4.4.0-136-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793178] Re: [kernel-fixed-upstream]Battery not found on Clevo N350DW laptop
** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793178 Title: [kernel-fixed-upstream]Battery not found on Clevo N350DW laptop Status in linux package in Ubuntu: Confirmed Bug description: Hello, the laptop runs flawlessly with Windows 10 and Linux except that in Linux the battery is not found in the system. I tried launching the Kernel with all acpi_osi and acpi_os_name parameters that the DSDT presented and with acpi=force, no luck. I patched the DSDT, it had 6 errors but 182 warnings, 250 remarks and 350 optimisations. I added under External(...) variable definitions one entry and commented out another that got me rid of the errors and I was able to compile a dsdt.aml. I duplicated the actual initrd and vmlinuz entries and cat the dsdt to the initrd. Restarted everything and it worked but no battery was found. It is completly invisible to the system. No my expertise has reached its limits, maybe you can have a look at it. Thank you very much, tell me what other infos you need. Greetings, Olli ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 3329 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Sep 18 18:39:35 2018 InstallationDate: Installed on 2018-09-17 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: TUXEDO N350DW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34.acpi root=UUID=77f9e7b0-9ad2-4aec-bbc6-6a3971cc9134 ro quiet splash acpi_osi=!Windows2012 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnTUXEDO:pnN350DW:pvrNotApplicable:rvnTUXEDO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793463] Re: SRU: Enable middle button of touchpad on ThinkPad P72
commit 91a97507323e1ad4bfc10f4a5922e67cdaf8b3cd Author: Aaron Ma Date: Tue Sep 18 09:32:22 2018 -0700 Input: elantech - enable middle button of touchpad on ThinkPad P72 Adding 2 new touchpad IDs to support middle button support. Cc: sta...@vger.kernel.org Signed-off-by: Aaron Ma Signed-off-by: Dmitry Torokhov -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793463 Title: SRU: Enable middle button of touchpad on ThinkPad P72 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] ThinkPad P72 has 3 physical hardware button on touchpad. Middle button didn't work due to kernel mask it. [Fix] Add this button support by PNPID in kernel input driver. [Test Case] Touchpad left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723612] Re: new laptop: Lenovo Y520-15IKBM no wireless networks found
$ gitoneline | grep ideapad | head -1 56c9bba135ab ike@canonical.com 2018-08-15 13:17:48 +0300 platform/x86: ideapad: Add Y520-15IKBM and Y720-15IKBM to no_hw_rfkill Patch has been accepted. Let me sort out how much we need to backport. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723612 Title: new laptop: Lenovo Y520-15IKBM no wireless networks found Status in linux package in Ubuntu: In Progress Bug description: platform/x86: ideapad-laptop: Add Y720-15IKBM to no_hw_rfkill Lenovo Legion Y720-15IKBM is yet another Lenovo model that does not have an hw rfkill switch, resulting in wifi always reported as hard blocked. Please add the model to the list of models without rfkill switch, in module ideapad-laptop ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: loek 2044 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 16:14:40 2017 HibernationDevice: RESUME=UUID=4864f7b1-0f01-42de-8c0b-fe93495c315f InstallationDate: Installed on 2017-10-09 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:2414 Syntek Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YY ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=349aa14b-4edc-478e-9b00-da8d368233f8 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5XCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y520-15IKBM dmi.modalias: dmi:bvnLENOVO:bvr5XCN13WW:bd09/07/2017:svnLENOVO:pn80YY:pvrLenovoY520-15IKBM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBM: dmi.product.name: 80YY dmi.product.version: Lenovo Y520-15IKBM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Thomas: sorry but support for Lightdm and SDDM will be available in the next update. On Thu, 20 Sep 2018 at 10:06, Thomas Rupprecht < rupprecht.thomas+launch...@gmail.com> wrote: > Should this also work with Kubuntu 18.04 with SDDM instead of GDM3? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=Fix Committed; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Tags: verification-done-bionic verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait brian-murray cantfind > dodger-forum happy-snizzo ilvipero janitor luiscastro193 mikhailnov odysei > sil2100 tjaalton ubname vorlon ximex xintx-ua > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Thomas Rupprecht (ximex) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xw
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
I've already testest that kernel. It doesn't work. (linux-image- unsigned-4.14.0-041400-generic_4.14.0-041400.201809190746_amd64.deb) And the generic 4.15.0-33 also doesn't work (tested with the official ubuntu kernel, not the one on the website). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793463] Re: SRU: Enable middle button of touchpad on ThinkPad P72
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793463 Title: SRU: Enable middle button of touchpad on ThinkPad P72 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Bug description: [Impact] ThinkPad P72 has 3 physical hardware button on touchpad. Middle button didn't work due to kernel mask it. [Fix] Add this button support by PNPID in kernel input driver. [Test Case] Touchpad left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793461] Re: Improvements to the kernel source package preparation
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Fix Committed Status in linux source package in Precise: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Fix Committed Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
When you say you 'already' tested that kernel, do you mean you already tested it before I posted it in comment #31? The kernel name might look similar to a prior kernel, but there is a unique date stamp in the name, '201809190746' in the latest test 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791751] Re: linux-kvm: 4.4.0-1034.40 -proposed tracker
4.4.0-1034.40 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kvm_unit_tests - 18 failed on chico ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) mlock203 failed (bug 1793451) quotactl01 failed (bug 1790028) ubuntu_lxc - python3 API failed (bug 1764618) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1791751 Title: linux-kvm: 4.4.0-1034.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1791745 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793086] Re: qeth: use vzalloc for QUERY OAT buffer
Bionic and Cosmic SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095563.html
** Description changed:
+
+ == SRU Justification ==
+ IBM reports the qethqoat tool fails. qeth_query_oat_command() currently
+ allocates the kernel buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
+
+ This commit will cause the use of vzalloc() instead of kzalloc(), backing
+ the allocation with non-contiguous memory.
+
+ Xenial also needs this commit, but requres a slightly different
+ backport. It's SRU will be sent separate.
+
+ == Fix ==
+ aec45e857c55 ("s390/qeth: use vzalloc for QUERY OAT buffer")
+
+ == Regression Potential ==
+ Low, limited to s390.
+
+ == Test Case ==
+ IBM verified testing of this commit up-front.
+
+
+
+
Description: qeth: use vzalloc for QUERY OAT buffer
Symptom: qethqoat tool fails.
- Problem: qeth_query_oat_command() currently allocates the kernel
- buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
+ Problem: qeth_query_oat_command() currently allocates the kernel
+ buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
Solution: Using vzalloc() instead of kzalloc(), backing the
allocation with non-contiguous memory.
-
Commit -ID: aec45e857c5538664edb76a60dd452e3265f37d1
kernel 4.19.
To be fixed for 18.10, 18,04 and 16.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1793086
Title:
qeth: use vzalloc for QUERY OAT buffer
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM reports the qethqoat tool fails. qeth_query_oat_command() currently
allocates the kernel buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
This commit will cause the use of vzalloc() instead of kzalloc(), backing
the allocation with non-contiguous memory.
Xenial also needs this commit, but requres a slightly different
backport. It's SRU will be sent separate.
== Fix ==
aec45e857c55 ("s390/qeth: use vzalloc for QUERY OAT buffer")
== Regression Potential ==
Low, limited to s390.
== Test Case ==
IBM verified testing of this commit up-front.
Description: qeth: use vzalloc for QUERY OAT buffer
Symptom: qethqoat tool fails.
Problem: qeth_query_oat_command() currently allocates the kernel
buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
Solution: Using vzalloc() instead of kzalloc(), backing the
allocation with non-contiguous memory.
Commit -ID: aec45e857c5538664edb76a60dd452e3265f37d1
kernel 4.19.
To be fixed for 18.10, 18,04 and 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1793086/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
Sorry. I didn't noticed that. OK, tested with this latest kernel "201809190746". It crashes with Console Message: "nouveau fb: trapped write at <>" something like this... and I never get the Login Screen and the whole thing freezes... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I've try to test without success, also following Alberto's procedure #40 packages have dependencies problems: Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-gl-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-dkms-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-kernel-source-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-compute-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-compute-utils-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-decode-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-encode-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-utils-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "xserver-xorg-video-nvidia-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-cfg1-390" per via di "xserver-xorg-video-nvidia-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-ifr1-390" per via di "nvidia-driver-390" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libnvidia-fbc1-390" per via di "nvidia-driver-390" Versione "3.28.3-0ubuntu18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "gdm3" Versione "3.28.3-0ubuntu18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "libgdm1" per via di "gdm3" Versione "3.28.3-0ubuntu18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "gir1.2-gdm-1.0" per via di "gdm3" Versione "1:0.5.2.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "ubuntu-drivers-common" Versione "0.8.8.1" (Ubuntu:18.04/bionic-proposed [all]) selezionata per "nvidia-prime" Versione "390.77-0ubuntu0.18.04.1" (Ubuntu:18.04/bionic-proposed [amd64]) selezionata per "nvidia-settings" Alcuni pacchetti non possono essere installati. Questo può voler dire che è stata richiesta una situazione impossibile oppure, se si sta usando una distribuzione in sviluppo, che alcuni pacchetti richiesti non sono ancora stati creati o sono stati rimossi da Incoming. Le seguenti informazioni possono aiutare a risolvere la situazione: I seguenti pacchetti hanno dipendenze non soddisfatte: nvidia-driver-390 : Dipende: libnvidia-gl-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Dipende: libnvidia-compute-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Dipende: libnvidia-decode-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Dipende: libnvidia-encode-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Dipende: libnvidia-ifr1-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Dipende: libnvidia-fbc1-390 (= 390.77-0ubuntu0.18.04.1) ma la versione 390.48-0ubuntu3 sta per essere installata Raccomanda: libnvidia-compute-390:i386 (= 390.77-0ubuntu0.18.04.1) Raccomanda: libnvidia-decode-390:i386 (= 390.77-0ubuntu0.18.04.1) Raccomanda: libnvidia-encode-390:i386 (= 390.77-0ubuntu0.18.04.1) Raccomanda: libnvidia-ifr1-390:i386 (= 390.77-0ubuntu0.18.04.1) Raccomanda: libnvidia-fbc1-390:i386 (= 390.77-0ubuntu0.18.04.1) Raccomanda: libnvidia-gl-390:i386 (= 390.77-0ubuntu0.18.04.1) E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati. ** Tags removed: verification-done-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers
[Kernel-packages] [Bug 1793461] Re: Improvements to the kernel source package preparation
** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Fix Committed Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793086] Re: qeth: use vzalloc for QUERY OAT buffer
Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095566.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1793086
Title:
qeth: use vzalloc for QUERY OAT buffer
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM reports the qethqoat tool fails. qeth_query_oat_command() currently
allocates the kernel buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
This commit will cause the use of vzalloc() instead of kzalloc(), backing
the allocation with non-contiguous memory.
Xenial also needs this commit, but requres a slightly different
backport. It's SRU will be sent separate.
== Fix ==
aec45e857c55 ("s390/qeth: use vzalloc for QUERY OAT buffer")
== Regression Potential ==
Low, limited to s390.
== Test Case ==
IBM verified testing of this commit up-front.
Description: qeth: use vzalloc for QUERY OAT buffer
Symptom: qethqoat tool fails.
Problem: qeth_query_oat_command() currently allocates the kernel
buffer for the SIOC_QETH_QUERY_OAT ioctl with kzalloc.
Solution: Using vzalloc() instead of kzalloc(), backing the
allocation with non-contiguous memory.
Commit -ID: aec45e857c5538664edb76a60dd452e3265f37d1
kernel 4.19.
To be fixed for 18.10, 18,04 and 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1793086/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by regression introduced by commit 287922eb0b18
** Summary changed:
- Kernel hang on drive pull caused by incomplete backport for bug 1597908
+ Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791790
Title:
Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
The following commit was applied to Xenial and introduced this
regression:
287922eb0b18 ("block: defer timeouts to a workqueue")
This regression was introduced in mainline as of v4.5-rc1. Bionc was
also affected by this regression, but it already go the fix when commit
4e9b6f20828a was applied to mainline in v4.15-rc1.
The regression caused a kernel hang because the HPSA driver has a tendency
to aggressively remove missing devices.
== Fix ==
4e9b6f20828a ("block: Fix a race between blk_cleanup_queue() and timeout
handling")
== Regression Potential ==
Low. This commit fixes a regression and has been cc'd to stable, so it
has had addition upstream review. This commit is already applied to
Bionic and Cosmic.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu 16.04 LTS
4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.
This patch changes the context in which timeout work is scheduled for
block devices in the kernel. Previously, timeout work was executed
directly from the timer callback that fired when a deadline was met.
After the patch, timeout work is scheduled using a background work
queue. This means that by the time the work executes, the device queue
which originally scheduled the work could be torn down. In order to
prevent this, the patch takes a reference on the device queue when
executing the timeout work.
The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the
last reference on the queue. The drain tries to clean up any
outstanding work, including timeout work. After a freeze, the timeout
work in the background queue is unable to obtain a reference, and
exits early without completing work. The work is now permanently stuck
in the queue and it will never be completed. The drain in the device
teardown path spins indefinitely.
The bug manifests as a hang that looks like this:
[] schedule+0x35/0x80
[] hpsa_scan_start+0x109/0x140 [hpsa]
[] ? wake_atomic_t_function+0x60/0x60
[] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
[] process_one_work+0x165/0x480
[] worker_thread+0x4b/0x4c0
[] ? process_one_work+0x480/0x480
[] kthread+0xd8/0xf0
[] ? kthread_create_on_node+0x1e0/0x1e0
[] ret_from_fork+0x3f/0x70
[] ? kthread_create_on_node+0x1e0/0x1e0
The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af
We hit this bug nearly 100% of the time on some of our HP hardware.
The HPSA driver has a tendency to aggressively remove missing devices,
so it widens the race. As a result, we've been building our own kernel
with this patch applied. It would be really nice if we could get it
into mainline Ubuntu.
Let me know what additional information is needed. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
** Changed in: linux (Ubuntu) Status: In Progress => 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/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793491] [NEW] ubuntu_nbd_smoke_test failed with KVM kernels
Public bug reported: This test failed with Bionic 4.15 KVM kernel: Cannot load Network Block Device module nbd.o stderr: modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm When look into the config, in 4.15 KVM kernel it is (also applies to the 4.4 KVM kernel): # CONFIG_BLK_DEV_NBD is not set But it's =m in Bionic kernel: # CONFIG_BLK_DEV_NBD is not set So we will need to decide if we want to add this into the KVM kernels, or disable the test for KVM kernels ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1021-kvm 4.15.0-1021.21 ProcVersionSignature: User Name 4.15.0-1021.21-kvm 4.15.18 Uname: Linux 4.15.0-1021-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 09:41:04 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images xenial ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Summary changed: - ubuntu_nbd_smoke_test failed with 4.15 Bionic KVM kernel + ubuntu_nbd_smoke_test failed with KVM kernels ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1793491 Title: ubuntu_nbd_smoke_test failed with KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: This test failed with Bionic 4.15 KVM kernel: Cannot load Network Block Device module nbd.o stderr: modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm When look into the config, in 4.15 KVM kernel it is (also applies to the 4.4 KVM kernel): # CONFIG_BLK_DEV_NBD is not set But it's =m in Bionic kernel: # CONFIG_BLK_DEV_NBD is not set So we will need to decide if we want to add this into the KVM kernels, or disable the test for KVM kernels ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1021-kvm 4.15.0-1021.21 ProcVersionSignature: User Name 4.15.0-1021.21-kvm 4.15.18 Uname: Linux 4.15.0-1021-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 09:41:04 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1793491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
The 4.15.0-33-generic #37~lp1792100Commit84d28cc43f2 kernel works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by regression introduced by commit 287922eb0b18
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095569.html
** Description changed:
- A bug was introduced when backporting the fix for
- http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
- 16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.
+ == SRU Justification ==
+ The following commit was applied to Xenial and introduced this
+ regression:
+ 287922eb0b18 ("block: defer timeouts to a workqueue")
+
+ This regression was introduced in mainline as of v4.5-rc1. Bionc was
+ also affected by this regression, but it already go the fix when commit
+ 4e9b6f20828a was applied to mainline in v4.15-rc1.
+
+ The regression caused a kernel hang because the HPSA driver has a tendency
+ to aggressively remove missing devices.
+
+ == Fix ==
+ 4e9b6f20828a ("block: Fix a race between blk_cleanup_queue() and timeout
handling")
+
+ == Regression Potential ==
+ Low. This commit fixes a regression and has been cc'd to stable, so it
+ has had addition upstream review. This commit is already applied to
+ Bionic and Cosmic.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
+
+ A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu 16.04 LTS
4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.
This patch changes the context in which timeout work is scheduled for
block devices in the kernel. Previously, timeout work was executed
directly from the timer callback that fired when a deadline was met.
After the patch, timeout work is scheduled using a background work
queue. This means that by the time the work executes, the device queue
which originally scheduled the work could be torn down. In order to
prevent this, the patch takes a reference on the device queue when
executing the timeout work.
The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the last
reference on the queue. The drain tries to clean up any outstanding
work, including timeout work. After a freeze, the timeout work in the
background queue is unable to obtain a reference, and exits early
without completing work. The work is now permanently stuck in the queue
and it will never be completed. The drain in the device teardown path
spins indefinitely.
The bug manifests as a hang that looks like this:
[] schedule+0x35/0x80
[] hpsa_scan_start+0x109/0x140 [hpsa]
[] ? wake_atomic_t_function+0x60/0x60
[] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
[] process_one_work+0x165/0x480
[] worker_thread+0x4b/0x4c0
[] ? process_one_work+0x480/0x480
[] kthread+0xd8/0xf0
[] ? kthread_create_on_node+0x1e0/0x1e0
[] ret_from_fork+0x3f/0x70
[] ? kthread_create_on_node+0x1e0/0x1e0
The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af
We hit this bug nearly 100% of the time on some of our HP hardware. The
HPSA driver has a tendency to aggressively remove missing devices, so it
widens the race. As a result, we've been building our own kernel with
this patch applied. It would be really nice if we could get it into
mainline Ubuntu.
Let me know what additional information is needed. Thanks!
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791790
Title:
Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
The following commit was applied to Xenial and introduced this
regression:
287922eb0b18 ("block: defer timeouts to a workqueue")
This regression was introduced in mainline as of v4.5-rc1. Bionc was
also affected by this regression, but it already go the fix when commit
4e9b6f20828a was applied to mainline in v4.15-rc1.
The regression caused a kernel hang because the HPSA driver has a tendency
to aggressively remove missing devices.
== Fix ==
4e9b6f20828a ("block: Fix a race between blk_cleanup_queue() and timeout
handling")
== Regression Potential ==
Low. This commit fixes a regression and has been cc'd to stable, so it
has had addition upstream review. This commit is already applied to
Bionic and Cosmic.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A bug wa
[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9
** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789118 Title: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: After the most recent 18.04 32-bit upgrade of linux-image-generic, it now refuses to boot under Xen PV mode: . . . [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes) [0.114423] pinctrl core: initialized pinctrl subsystem [0.134326] RTC time: 165:165:165, date: 165/165/65 [0.134442] NET: Registered protocol family 16 [0.134457] xen:grant_table: Grant tables using version 1 layout [0.134502] Grant table initialized [0.134544] audit: initializing netlink subsys (disabled) [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized audit_enabled=0 res=1 [0.134678] EISA bus registered [0.136019] PCI: setting up Xen PCI frontend stub [0.136073] BUG: unable to handle kernel paging request at edc21fd9 [0.136084] IP: eisa_bus_probe+0x19/0x36 [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = [0.136100] Oops: [#1] SMP [0.136105] Modules linked in: [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic #36-Ubuntu [0.136120] EIP: eisa_bus_probe+0x19/0x36 [0.136125] EFLAGS: 00010246 CPU: 0 [0.136130] EAX: edc21fd9 EBX: ECX: 01e0d000 EDX: 0200 [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24 [0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021 [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660 [0.136166] Call Trace: [0.136173] do_one_initcall+0x49/0x174 [0.136179] ? parse_args+0x143/0x390 [0.136187] ? set_debug_rodata+0x14/0x14 [0.136193] kernel_init_freeable+0x149/0x1c5 [0.136201] ? rest_init+0xa0/0xa0 [0.136207] kernel_init+0xd/0xf0 [0.136213] ret_from_fork+0x2e/0x38 [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8 [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24 [0.14] CR2: edc21fd9 [0.14] ---[ end trace 8c00b3cb7d4f06ba ]--- [0.140013] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 This is: [0.00] Linux version 4.15.0-33-generic (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic 4.15.18) Switching to a 64-bit kernel allows boot to proceed. I cannot include output of the commands you request (uname, version_signature, dmesg, lspci) because the guest doesn't boot. The above kernel output is from a just-installed clean guest however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788351] Re: bind03 in ubuntu_ltp_syscalls failed with X/B
Passed with Bionic-KVM, Bionic
Failed with Xenial-KVM, Xenial
I will update the title.
** Summary changed:
- bind03 in ubuntu_ltp_syscalls failed with X/B
+ bind03 in ubuntu_ltp_syscalls failed with X
** Changed in: ubuntu-kernel-tests
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/1788351
Title:
bind03 in ubuntu_ltp_syscalls failed with X
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a new test. It has passed on Trusty but failed on X/B (I guess
in C as well)
<<>>
tag=bind03 stime=1534863126
cmdline="bind03"
contacts=""
analysis=exit
<<>>
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
bind03.c:48: FAIL: expected EINVAL: EADDRINUSE
Summary:
passed 0
failed 1
skipped 0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>
From the commit message of this test:
With 0fb44559ffd6 ("af_unix: move unix_mknod() out of bindlock")
the behavior of bind() for STREAM UNIX sockets changed in
case a socket that is already bound is passed to bind() again.
This testcase fails for the new behavior and passes for the
old one.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1032-kvm 4.4.0-1032.38
ProcVersionSignature: User Name 4.4.0-1032.38-kvm 4.4.140
Uname: Linux 4.4.0-1032-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Aug 22 07:33:43 2018
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger
** Summary changed: - Ubuntu18.10:Witherspoon:DD2.2 - Sysrq trigger disabled when writing to /proc/sysrq-trigger + Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793369 Title: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc /sysrq-trigger Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: == Comment: #0 - Praveen K. Pandey - 2018-09-19 04:49:39 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled when writing to /proc/sysrq-trigger while testing kdump trying trigger kdump panic via /proc/sysrq-trigger it failed as : SysRq : This sysrq operation is disabled LOG: root@test:~# cat /proc/sys/kernel/sysrq 176 root@test:~# echo c > /proc/sysrq-trigger root@test:~# dmesg [ 380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status flags(0x2) [ 389.404239] sysrq: SysRq : This sysrq operation is disabled. root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6 CONFIG_MAGIC_SYSRQ_SERIAL=y root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq #kernel.sysrq=438 root@test:~# 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.18.0-7-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-7-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@test:~# Regards Praveen == Comment: #2 - Praveen K. Pandey - 2018-09-19 05:16:11 == when i enable in /etc/sysctl.conf it works . i append below value in sysctl.conf echo "kernel.sysrq = 1" >> /etc/sysctl.conf I think this is should be enable by default in ubuntu 18.10 as earlier ubuntu distro it has , not sure why it got removed as kdump mechanism require this . Praveen Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789746] Re: getxattr: always handle namespaced attributes
Thanks Joseph, the kernel resolves the issue!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789746
Title:
getxattr: always handle namespaced attributes
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
Hey everyone,
When running in a container with a user namespace, if you call getxattr
with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
silently skips the user namespace fixup that it normally does resulting in
un-fixed-up data being returned.
This is caused by posix_acl_fix_xattr_to_user() being passed the total
buffer size and not the actual size of the xattr as returned by
vfs_getxattr().
I have pushed a commit upstream that fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5
This commit passes the actual length of the xattr as returned by
vfs_getxattr() down.
A reproducer for the issue is:
touch acl_posix
setfacl -m user:0:rwx acl_posix
and the compile:
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
/* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
int main(int argc, void **argv)
{
ssize_t ret1, ret2;
char buf1[128], buf2[132];
int fret = EXIT_SUCCESS;
char *file;
if (argc < 2) {
fprintf(stderr,
"Please specify a file with "
"\"system.posix_acl_access\" permissions set\n");
_exit(EXIT_FAILURE);
}
file = argv[1];
ret1 = getxattr(file, "system.posix_acl_access",
buf1, sizeof(buf1));
if (ret1 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}
ret2 = getxattr(file, "system.posix_acl_access",
buf2, sizeof(buf2));
if (ret2 < 0) {
fprintf(stderr, "%s - Failed to retrieve "
"\"system.posix_acl_access\" "
"from \"%s\"\n", strerror(errno), file);
_exit(EXIT_FAILURE);
}
if (ret1 != ret2) {
fprintf(stderr, "The value of \"system.posix_acl_"
"access\" for file \"%s\" changed "
"between two successive calls\n", file);
_exit(EXIT_FAILURE);
}
for (ssize_t i = 0; i < ret2; i++) {
if (buf1[i] == buf2[i])
continue;
fprintf(stderr,
"Unexpected different in byte %zd: "
"%02x != %02x\n", i, buf1[i], buf2[i]);
fret = EXIT_FAILURE;
}
if (fret == EXIT_SUCCESS)
fprintf(stderr, "Test passed\n");
else
fprintf(stderr, "Test failed\n");
_exit(fret);
}
and run:
./tester acl_posix
On a non-fixed up kernel this should return something like:
root@c1:/# ./t
Unexpected different in byte 16: ffa0 != 00
Unexpected different in byte 17: ff86 != 00
Unexpected different in byte 18: 01 != 00
and on a fixed kernel:
root@c1:~# ./t
Test passed
Please backport this to the 4.15 (bionic) and 4.4 (xenial) kernels. :)
Thanks!
Christian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789746/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793498] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095572.html
** Description changed:
- After the most recent 18.04 32-bit upgrade of linux-image-generic, it
- now refuses to boot under Xen PV mode:
+ == SRU Justification ==
+ After an upgrade to Bionic, the bug reporter states the 32-bit kernel
+ does not boot under Xen PV mode. This bug does not affect 64-bit
+ kernels and if fixed by mainline commit 6a92b11169a6.
+
+ == Fix ==
+ 6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")
+
+ == Regression Potential ==
+ Low. This commit only affects x86 kernels. This commit has also been cc'd
to upstream stable, so it has had
+ additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+ After the most recent 18.04 32-bit upgrade of linux-image-generic, it now
refuses to boot under Xen PV mode:
.
.
.
[0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x,
max_idle_ns: 764504178510 ns
[0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
[0.114423] pinctrl core: initialized pinctrl subsystem
[0.134326] RTC time: 165:165:165, date: 165/165/65
[0.134442] NET: Registered protocol family 16
[0.134457] xen:grant_table: Grant tables using version 1 layout
[0.134502] Grant table initialized
[0.134544] audit: initializing netlink subsys (disabled)
[0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized
audit_enabled=0 res=1
[0.134678] EISA bus registered
[0.136019] PCI: setting up Xen PCI frontend stub
[0.136073] BUG: unable to handle kernel paging request at edc21fd9
[0.136084] IP: eisa_bus_probe+0x19/0x36
- [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte =
+ [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte =
[0.136100] Oops: [#1] SMP
[0.136105] Modules linked in:
[0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic
#36-Ubuntu
[0.136120] EIP: eisa_bus_probe+0x19/0x36
[0.136125] EFLAGS: 00010246 CPU: 0
[0.136130] EAX: edc21fd9 EBX: ECX: 01e0d000 EDX: 0200
[0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
[0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
[0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
[0.136166] Call Trace:
[0.136173] do_one_initcall+0x49/0x174
[0.136179] ? parse_args+0x143/0x390
[0.136187] ? set_debug_rodata+0x14/0x14
[0.136193] kernel_init_freeable+0x149/0x1c5
[0.136201] ? rest_init+0xa0/0xa0
[0.136207] kernel_init+0xd/0xf0
[0.136213] ret_from_fork+0x2e/0x38
[0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
[0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
[0.14] CR2: edc21fd9
[0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
[0.140013] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0009
This is: [0.00] Linux version 4.15.0-33-generic
(buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic
4.15.18)
Switching to a 64-bit kernel allows boot to proceed.
I cannot include output of the commands you request (uname,
version_signature, dmesg, lspci) because the guest doesn't boot. The
above kernel output is from a just-installed clean guest however.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789118
Title:
Fails to boot under Xen PV: BUG: unable to handle kernel paging
request at edc21fd9
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
After an upgrade to Bionic, the bug reporter states the 32-bit kernel
does not boot under Xen PV mode. This bug does not affect 64-bit
kernels and if fixed by mainline commit 6a92b11169a6.
== Fix ==
6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")
== Regression Potential ==
Low. This commit only affects x86 kernels. This commit has also been cc'd
to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
After the most recent 18.04 32-bit upgrade of linux-image-generic, it now
refuses to boot under Xen PV mode:
[Kernel-packages] [Bug 1793498] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase-changed:Thursday, 20. September 2018 10:31 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 20. September 2018 10:31 UTC kernel-stable-phase:Packaging + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793498 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 20. September 2018 10:31 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
Thanks for the link, for some reason I was looking in the wrong place.
The issue seems to have been introduced in 4.15.0-13 (4.15.0-12 works).
There is in fact a CIFS related patch[1][2][3] that was backported and
is most probably the one introducing this regression.
[1] https://www.spinics.net/lists/linux-cifs/msg13861.html
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747572
[3] https://bugzilla.samba.org/show_bug.cgi?id=12917
** Bug watch added: Samba Bugzilla #12917
https://bugzilla.samba.org/show_bug.cgi?id=12917
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792580
Title:
Mounting SOFS SMB shares fails
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1
Mounting scale-out SMB shares is failing.
mount -t cifs -o
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares
Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9
STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel:
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status
code 0xc0c9 to POSIX err -5
Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *
ShareState: Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped: True
ScopeName : S2DSCALEOUT
ShadowCopy: False
Special : False
Temporary : False
Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 7 16:51 seq
crw-rw 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Linux 4.15.0-34 fails to boot in VirtualBox. 4.4.0-135 boots OK, same everything else. stefan@stefan-lubuntu12:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic stefan@stefan-lubuntu12:~$ uname -a Linux stefan-lubuntu12 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:46:32 UTC 2018 i686 i686 i686 GNU/Linux Also, cannot install 18.04 from ISO in new VM, probably also because of that. Good thing I did not upgrade my physical machines to 18.04, like some poor souls in here did! 'Nuff said, S. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Released Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 2018-09-20 07:06 EDT--- Hi, We lost the old environment as jmet got returned. Got a new Witherspoon jmet and retried the kdump scenario & issue recreated on latest ubuntu180401 kernel (4.15.0-34-generic) kernel. > Triggered kdump with default crashkernel parameter and it went to initramfs > state root@wax:~# cat /proc/cmdline root=UUID=38d0124f-14d8-4098-a746-03f9bda5c22e ro crashkernel=8192M splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M > Collected console & dmesg logs from same state > Rebooted system & collected sosreport, tar czf lp1778844_sys.tar.gz /sys/ > Also tried comment#23 steps & collected /tmp/initrd.img root@wax:~# cat /etc/initramfs-tools/initramfs.conf | grep MODULES # MODULES: [ most | netboot | dep | list ] MODULES=dep root@wax:~# mkinitramfs -o /tmp/initrd.img W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast root@wax:~# uname -r 4.15.0-34-generic root@wax:~# ls -l /tmp/initrd.img -rw-r--r-- 1 root root 24128581 Sep 20 04:59 /tmp/initrd.img > Attaching all above logs & if i am unable to attach any of the logs because of size issue. Logs are placed in the path banner.isst.aus.stglabs.ibm.com [banner/don2rry ] : /home/banner/169067_sep20 > Attaching console logs from first step till last step ( starting from system booting with latest kernel level, trigger crash , initramfs state etc...) Thanks & Regards, Indira -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: 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
[Kernel-packages] [Bug 1793505] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1793506] [NEW] Ignore this bug
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Impo
[Kernel-packages] [Bug 1793498] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: precise ** Summary changed: - linux: -proposed tracker + Ignore this bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793498 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 20. September 2018 10:31 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] [NEW] no matching swap device at initramfs
Public bug reported: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: New Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] sosreport_kdump_initramfstsate
--- Comment on attachment From indira.pr...@in.ibm.com 2018-09-20 07:34 EDT--- Attached sosreport from wax_kdump_initramfs state ** Attachment added: "sosreport_kdump_initramfstsate" https://bugs.launchpad.net/bugs/1778844/+attachment/5190945/+files/sosreport-wax-20180920041434.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: 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 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0
[Kernel-packages] [Bug 1778844] /initrd.img file
--- Comment on attachment From indira.pr...@in.ibm.com 2018-09-20 07:38 EDT--- Attached initrd.img file from wax ** Attachment added: "/initrd.img file" https://bugs.launchpad.net/bugs/1778844/+attachment/5190946/+files/initrd.img -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: 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 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 0e4f79d56818 [ 73.058099] GPR20: 0
[Kernel-packages] [Bug 1778844] Consolelogs_wax_kdump_initrmafs state
--- Comment on attachment From indira.pr...@in.ibm.com 2018-09-20 07:31 EDT--- Attached IPMI console logs from start of the tests till end. ** Attachment added: "Consolelogs_wax_kdump_initrmafs state" https://bugs.launchpad.net/bugs/1778844/+attachment/5190944/+files/169067_bugrecreation_wax_180401_latets_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: 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 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e
[Kernel-packages] [Bug 1793506] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: precise ** Summary changed: - linux: -proposed tracker + Ignore this bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793506 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger
The sysrq mechanism allows someone with physical access to the system to easily cause it to boot by just pressing some keys. That's why the sysrq default allows only very few commands to be issued. kdump is for real crashes. kdump testing may require using the sysrq-trigger mechanism, but that could just as well write to /proc/sys/kernel/sysrq before causing the crash. In fact, that's just what kdump-tools autopkgtest does. echo 1 > /proc/sys/kernel/sysrq echo c > /proc/sysrq-trigger So, not a bug here. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => 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/1793369 Title: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc /sysrq-trigger Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in linux source package in Cosmic: Invalid Status in systemd source package in Cosmic: Won't Fix Bug description: == Comment: #0 - Praveen K. Pandey - 2018-09-19 04:49:39 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled when writing to /proc/sysrq-trigger while testing kdump trying trigger kdump panic via /proc/sysrq-trigger it failed as : SysRq : This sysrq operation is disabled LOG: root@test:~# cat /proc/sys/kernel/sysrq 176 root@test:~# echo c > /proc/sysrq-trigger root@test:~# dmesg [ 380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status flags(0x2) [ 389.404239] sysrq: SysRq : This sysrq operation is disabled. root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6 CONFIG_MAGIC_SYSRQ_SERIAL=y root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq #kernel.sysrq=438 root@test:~# 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.18.0-7-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-7-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@test:~# Regards Praveen == Comment: #2 - Praveen K. Pandey - 2018-09-19 05:16:11 == when i enable in /etc/sysctl.conf it works . i append below value in sysctl.conf echo "kernel.sysrq = 1" >> /etc/sysctl.conf I think this is should be enable by default in ubuntu 18.10 as earlier ubuntu distro it has , not sure why it got removed as kdump mechanism require this . Praveen Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] 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 1793508 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793505] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Thursday, 20. September 2018 12:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 20. September 2018 12:01 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793505 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 20. September 2018 12:01 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793515] [NEW] linux: 4.15.0-36.39 -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Kleber Sacilotto de Souza (kleber-souza) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.20-2 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: k
[Kernel-packages] [Bug 1793515] Re: linux: -proposed tracker
This is a testing tracking bugs. ** Summary changed: - linux: -proposed tracker + linux: 4.15.0-36.39 -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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793515 Title: linux: 4.15.0-36.39 -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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 2018-09-20 07:42 EDT--- Unable to attach "lp1778844_sys.tar.gz" file because of size, please refer to logs path .Also test machine is taken back for other release testing. banner.isst.aus.stglabs.ibm.com [banner/don2rry ] : /home/banner/169067_sep20 Regards, Indira -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: 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 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@ubname: installing the meta-package worked here, but you can install the single packages manually: sudo apt install libnvidia-gl-390/bionic-proposed libnvidia-compute-390 /bionic-proposed libnvidia-decode-390/bionic-proposed libnvidia- encode-390/bionic-proposed libnvidia-ifr1-390/bionic-proposed libnvidia- fbc1-390/bionic-proposed You might have to do the same for the i386 dependencies. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic ** Description changed: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. - _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed - nvidia-settings/bionic-proposed + nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-proposed + libnvidia-compute-390/bionic-proposed libnvidia-decode-390/bionic- + proposed libnvidia-encode-390/bionic-proposed libnvidia-ifr1-390/bionic- + proposed libnvidia-fbc1-390/bionic-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-p
[Kernel-packages] [Bug 1793515] Re: linux: 4.15.0-36.39 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable 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/1793515 Title: linux: 4.15.0-36.39 -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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1793515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
after updated all the 5 packages below to new version, this issue seems fixed in my quick testing. nvidia-driver-390 (390.77-0ubuntu0.18.04.1) gdm3 (3.28.3-0ubuntu18.04.1) ubuntu-drivers-common (1:0.5.2.1) nvidia-prime (0.8.8.1) nvidia-settings (390.77-0ubuntu0.18.04.1) ** 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 nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger
** Changed in: ubuntu-power-systems Status: Triaged => 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/1793369 Title: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc /sysrq-trigger Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in linux source package in Cosmic: Invalid Status in systemd source package in Cosmic: Won't Fix Bug description: == Comment: #0 - Praveen K. Pandey - 2018-09-19 04:49:39 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled when writing to /proc/sysrq-trigger while testing kdump trying trigger kdump panic via /proc/sysrq-trigger it failed as : SysRq : This sysrq operation is disabled LOG: root@test:~# cat /proc/sys/kernel/sysrq 176 root@test:~# echo c > /proc/sysrq-trigger root@test:~# dmesg [ 380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status flags(0x2) [ 389.404239] sysrq: SysRq : This sysrq operation is disabled. root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ=y CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6 CONFIG_MAGIC_SYSRQ_SERIAL=y root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq #kernel.sysrq=438 root@test:~# 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.18.0-7-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-7-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@test:~# Regards Praveen == Comment: #2 - Praveen K. Pandey - 2018-09-19 05:16:11 == when i enable in /etc/sysctl.conf it works . i append below value in sysctl.conf echo "kernel.sysrq = 1" >> /etc/sysctl.conf I think this is should be enable by default in ubuntu 18.10 as earlier ubuntu distro it has , not sure why it got removed as kdump mechanism require this . Praveen Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793526] [NEW] linux-lts-trusty: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1793525 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1793525 kernel-sru-cycle-1000.10.15 precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-packa
[Kernel-packages] [Bug 1793525] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1793526 (linux-lts-trusty) derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-1000.10.15 kernel-sru-master-kernel trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: trusty ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance
[Kernel-packages] [Bug 1793524] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-1000.10.15 kernel-sru-master-kernel precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta A
[Kernel-packages] [Bug 1750349] Re: [Hyper-V] include kvp fix for Avoid reading past allocated blocks from KVP file
Joe, Brad - I see this bug still reads 'committed' for bionic.
Looking for a Fix released for all so that we can close it.
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1750349
Title:
[Hyper-V] include kvp fix for Avoid reading past allocated blocks from
KVP file
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This commit is being requested in Bionic and linux-azure by Microsoft. It
has
already been applied to Bionic. It is being requested in Artful, so it makes
it's way into linux-azure through the re-base process.
This fix is required if a large number of records are injected into a pool,
which can cause the kvp daemon to crash.
This commit has been cc'd to upstream stable. However, it has not yet been
applied
to Artful, since upstream 4.13 is EOL.
== Fix ==
297d6b6e56c2 ("hv: kvp: Avoid reading past allocated blocks from KVP file")
== Regression Potential ==
Low. This patch has also been sent to upstream stable, so it has had
additional upstream
review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767832] Re: ASUS touchpad right button not working
I just found time in order to debug this problem. I found a "bug" in the hid-multitouch driver. I also enabled the confidence management provided by this touchpad in order to avoid pointer movements when we are using the keyboard. I'll try to submit this patch to the kernel developers team. ** Patch added: "hid-multitouch.c patch for ASUS T304UA touchpads" https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+attachment/5190974/+files/asus_touchpad.patch ** Changed in: linux (Ubuntu) Status: Expired => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767832 Title: ASUS touchpad right button not working Status in Ubuntu-Certification: Invalid Status in linux package in Ubuntu: Fix Committed Bug description: On my ASUS T304UA, the right button of the trackpad generates no input event whereas the left button and the left half part of the middle button works (checked with libinput-debug-events). I checked with the latest available kernel: 4.17.0-041700rc2-generic Needless to say that the trackpad perfectly works under Windows. The device is: Bus 001 Device 005: ID 0b05:184a ASUSTek Computer, Inc. I guess that the corresponding kernel driver is: hid_multitouch Example of libinput-debug-events : left click then right click : -event17 POINTER_BUTTON+1.11sBTN_LEFT (272) pressed, seat count: 1 event17 POINTER_BUTTON+1.23sBTN_LEFT (272) released, seat count: 0 It seems that there is a bug in the trackpad driver... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793531] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-1000.10.15 kernel-sru-master-kernel precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta A
[Kernel-packages] [Bug 1793535] [NEW] Start Laptop
Public bug reported: Just a normal startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asp2185 F pulseaudio CurrentDesktop: MATE Date: Thu Sep 20 15:16:59 2018 HibernationDevice: RESUME=UUID=94539c5b-fff0-414b-8dab-86e5fa9ec493 InstallationDate: Installed on 2018-06-26 (85 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. UX430UNR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=cfa1696f-c23c-4141-9dd3-82f55ce0038e ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.304:bd03/09/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX430UNR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793535 Title: Start Laptop Status in linux package in Ubuntu: Confirmed Bug description: Just a normal startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asp2185 F pulseaudio CurrentDesktop: MATE Date: Thu Sep 20 15:16:59 2018 HibernationDevice: RESUME=UUID=94539c5b-fff0-414b-8dab-86e5fa9ec493 InstallationDate: Installed on 2018-06-26 (85 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. UX430UNR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=cfa1696f-c23c-4141-9dd3-82f55ce0038e ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.304:bd03/09/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX430UNR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793535] 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/1793535 Title: Start Laptop Status in linux package in Ubuntu: Confirmed Bug description: Just a normal startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asp2185 F pulseaudio CurrentDesktop: MATE Date: Thu Sep 20 15:16:59 2018 HibernationDevice: RESUME=UUID=94539c5b-fff0-414b-8dab-86e5fa9ec493 InstallationDate: Installed on 2018-06-26 (85 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. UX430UNR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=cfa1696f-c23c-4141-9dd3-82f55ce0038e ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.304:bd03/09/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX430UNR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792600] Re: cross-toolchain-base ftbfs with linux-4.18
right, now using that and checking in an autopkg test, so migration of kernels with a changed build system will block. ** Changed in: cross-toolchain-base (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/1792600 Title: cross-toolchain-base ftbfs with linux-4.18 Status in cross-toolchain-base package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: according to the build logs, the build process changed and calls the host compiler even for building the header files. This worked in 4.15, but not anymore in 4.18. To limit the build to one cross arch: CROSS_ARCHS=arm64 DEB_BUILD_OPTIONS=... dpkg-buildpackage -b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/1792600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767832] Re: ASUS touchpad right button not working
I think this commit fixes your issue?
commit ec6adef5fbc3f140c70e7499fdad818acb3a46c6
Author: Benjamin Tissoires
Date: Tue Sep 4 15:31:12 2018 +0200
HID: multitouch: fix Elan panels with 2 input modes declaration
When implementing commit 7f81c8db5489 ("HID: multitouch: simplify
the settings of the various features"), I wrongly removed a test
that made sure we never try to set the second InputMode feature
to something else than 0.
This broke badly some recent Elan panels that now forget to send the
click button in some area of the touchpad.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=200899
Fixes: 7f81c8db5489 ("HID: multitouch: simplify the settings of the various
features")
Cc: sta...@vger.kernel.org # v4.18+
Signed-off-by: Benjamin Tissoires
Signed-off-by: Jiri Kosina
** Bug watch added: Linux Kernel Bug Tracker #200899
https://bugzilla.kernel.org/show_bug.cgi?id=200899
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767832
Title:
ASUS touchpad right button not working
Status in Ubuntu-Certification:
Invalid
Status in linux package in Ubuntu:
Fix Committed
Bug description:
On my ASUS T304UA, the right button of the trackpad generates no input event
whereas the left button and the left half part of the middle button works
(checked with libinput-debug-events).
I checked with the latest available kernel: 4.17.0-041700rc2-generic
Needless to say that the trackpad perfectly works under Windows.
The device is:
Bus 001 Device 005: ID 0b05:184a ASUSTek Computer, Inc.
I guess that the corresponding kernel driver is: hid_multitouch
Example of libinput-debug-events : left click then right click :
-event17 POINTER_BUTTON+1.11sBTN_LEFT (272) pressed, seat count: 1
event17 POINTER_BUTTON+1.23sBTN_LEFT (272) released, seat count: 0
It seems that there is a bug in the trackpad driver...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
I built the next test kernel, up to the following commit: d4be7ce8e6324691737b45f336d770245ba07310 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
Thanks for the feedback. I submitted those three commits for bug
1747572. To see if they introduced the regression, I built a test
kernel with those three commits reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792580
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792580
Title:
Mounting SOFS SMB shares fails
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1
Mounting scale-out SMB shares is failing.
mount -t cifs -o
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares
Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9
STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel:
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status
code 0xc0c9 to POSIX err -5
Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *
ShareState: Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped: True
ScopeName : S2DSCALEOUT
ShadowCopy: False
Special : False
Temporary : False
Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 7 16:51 seq
crw-rw 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767832] Re: ASUS touchpad right button not working
damned I did all this job for nothing... I didn't see the patch but seems it's exactly I encountered and the solution I found it seems that it fixes the issue right! However as I said I also enabled the use of confidence field which really improve the use of the keyboard of this computer. IT could be interesting for other people. I'll send an email to Benjamin in order to discuss that point with him. Thanks a lot ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767832 Title: ASUS touchpad right button not working Status in Ubuntu-Certification: Invalid Status in linux package in Ubuntu: Fix Committed Bug description: On my ASUS T304UA, the right button of the trackpad generates no input event whereas the left button and the left half part of the middle button works (checked with libinput-debug-events). I checked with the latest available kernel: 4.17.0-041700rc2-generic Needless to say that the trackpad perfectly works under Windows. The device is: Bus 001 Device 005: ID 0b05:184a ASUSTek Computer, Inc. I guess that the corresponding kernel driver is: hid_multitouch Example of libinput-debug-events : left click then right click : -event17 POINTER_BUTTON+1.11sBTN_LEFT (272) pressed, seat count: 1 event17 POINTER_BUTTON+1.23sBTN_LEFT (272) released, seat count: 0 It seems that there is a bug in the trackpad driver... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
4.16 does not work at all. 4.17 and 4.18 work just fine. Haven't tested 4.19-rc1 though anymore, as suggested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
Awesome, thanks for the build. Worked as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792580
Title:
Mounting SOFS SMB shares fails
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1
Mounting scale-out SMB shares is failing.
mount -t cifs -o
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares
Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9
STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel:
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status
code 0xc0c9 to POSIX err -5
Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *
ShareState: Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped: True
ScopeName : S2DSCALEOUT
ShadowCopy: False
Special : False
Temporary : False
Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 7 16:51 seq
crw-rw 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-33-generic N/A
linux-backports-modules-4.15.0-33-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788563] Re: L1TF mitigation not effective in some CPU and RAM combinations
Do you have any ETA for Xenial fixed 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/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
This bug has been reported in multiple bugs and affects Trusty,
Xenial and Bionic. All releases need different backports, so T and X
will be sent in separate SRU requests.
Due to this bug in the original L1TF patch set, L1TF mitigation not
effective in certain CPU and installed RAM configurations.
== Fixes ==
9df9516940a6 ("x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on
32bit")
b0a182f87568 ("x86/speculation/l1tf: Fix off-by-one error when warning that
system has too much RAM")
cc51e5428ea5 ("x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+")
== Regression Potential ==
Low. These are security fixes and have all been cc'd to upstream
stable, so they have had additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Lenovo Thinkpad W530 system with 32 GB RAM
dmesg | grep -i l1tf
[0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation
not effective.
[ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
for details.
Related:
https://bugzilla.opensuse.org/show_bug.cgi?id=1105536
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgera 2809 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug 23 03:38:40 2018
InstallationDate: Installed on 2018-08-11 (12 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 24382LU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-32-generic N/A
linux-backports-modules-4.15.0-32-generic N/A
linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 24382LU
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad W530
dmi.product.name: 24382LU
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1793373] Re: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
Joseph: I tried your fix typing it in the terminal but I got the message below Isteven@steven-X540SA:~$ sudo apt-get install -f [sudo] password for steven: Reading package lists... Done Building dependency tree Reading state information... Done E: The package linux-image-extra-4.4.0-119-generic needs to be reinstalled, but I can't find an archive for it. Any ideas how to reinstall the package above? Thanks, Steven Fick On Thu, Sep 20, 2018 at 2:20 AM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1793373 > > Title: > package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to > install/upgrade: package is in a very bad inconsistent state; you > should reinstall it before attempting configuration > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I was trying run the OS updates and got the error above? > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143 > ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 > Uname: Linux 4.4.0-133-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: steven 1897 F pulseaudio > Date: Wed Sep 19 14:17:52 2018 > DuplicateSignature: >package:linux-image-extra-4.4.0-119-generic:4.4.0-119.143 >Processing triggers for dbus (1.10.6-1ubuntu3.3) ... >dpkg: error processing package linux-image-extra-4.4.0-119-generic > (--configure): > package is in a very bad inconsistent state; you should > ErrorMessage: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > HibernationDevice: RESUME=UUID=8b487a35-1a21-4674-9720-185dd8bfd41c > InstallationDate: Installed on 2016-05-25 (847 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd >Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. >Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. X540SA > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed > root=UUID=1c9ef1ae-d7a6-4e81-b5c5-76f25af8c7ef ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc N/A > SourcePackage: linux > Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed > to install/upgrade: package is in a very bad inconsistent state; you > should reinstall it before attempting configuration > UpgradeStatus: Upgraded to xenial on 2018-09-19 (0 days ago) > dmi.bios.date: 11/25/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X540SA.207 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X540SA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrX540SA.207:bd11/25/2015:svnASUSTeKCOMPUTERINC.:pnX540SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: X540SA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793373/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793373 Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Incomplete Bug description: I was trying run the OS updates and got the error above? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
Hi Jeremy/Joseph/Support, It's been quiet some time...I'm still stuck with the same issue...any update. Earlier I had attached the modinfo details required by Jeremy Pl consider this as urgent and necessary. Thanking you in advance. Br, Joseph ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792973] Re: ubuntu_nbd_smoke_test failed on 4.15 Trusty Azure
I have this verified on Trusty 4.15 Azure, this is still not working, even with linux-modules-extra-4.15.0-1023-azure installed Output for this rerun: https://pastebin.ubuntu.com/p/sQKYKPysDd/ I'm wondering if this is related to releases, as I can see similar failures: server is not listening disconnect, sock, done stderr: umount: /mnt/nbd-test-1611: not found On bare-metal Trusty system, reports can be found in the comment of bug 1793321 The reason why this test was executed on Trusty that is we just implemented a new kernel-version based blacklist feature, and rename the blacklist from blacklist.trusty to blacklist.3.13.0. So as we're running 4.15 kernel on Trusty, this test was triggered. If this is not expected to work on Trusty, we can blacklist it again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1792973 Title: ubuntu_nbd_smoke_test failed on 4.15 Trusty Azure Status in ubuntu-kernel-tests: New Status in linux-signed-azure package in Ubuntu: New Bug description: The ubuntu_nbd_smoke test will timeout on a 4.15 Trusty Azure node. The test will get killed by the timeout setting and the job hangs. There is also a rmmod related error message: [stderr] rmmod: ERROR: Module nbd is not currently loaded Running 'DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes nbd-server nbd-client gdb' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] gdb is already the newest version. [stdout] The following NEW packages will be installed: [stdout] nbd-client nbd-server [stdout] 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. [stdout] Need to get 104 kB of archives. [stdout] After this operation, 430 kB of additional disk space will be used. [stdout] Get:1 http://azure.archive.ubuntu.com/ubuntu/ trusty-updates/main nbd-client amd64 1:3.7-1ubuntu0.1 [45.1 kB] [stdout] Get:2 http://azure.archive.ubuntu.com/ubuntu/ trusty-updates/main nbd-server amd64 1:3.7-1ubuntu0.1 [58.8 kB] [stdout] Preconfiguring packages ... [stdout] Fetched 104 kB in 0s (9,346 kB/s) [stdout] Selecting previously unselected package nbd-client. [stdout] (Reading database ... 54762 files and directories currently installed.) [stdout] Preparing to unpack .../nbd-client_1%3a3.7-1ubuntu0.1_amd64.deb ... [stdout] Unpacking nbd-client (1:3.7-1ubuntu0.1) ... [stdout] Selecting previously unselected package nbd-server. [stdout] Preparing to unpack .../nbd-server_1%3a3.7-1ubuntu0.1_amd64.deb ... [stdout] Unpacking nbd-server (1:3.7-1ubuntu0.1) ... [stdout] Processing triggers for man-db (2.6.7.1-1ubuntu1) ... [stdout] Processing triggers for ureadahead (0.100.0-16) ... [stdout] Setting up nbd-client (1:3.7-1ubuntu0.1) ... [stderr] Stopping NBD client process: [stderr] rmmod: ERROR: Module nbd is not currently loaded [stderr] nbd-client. [stderr] Starting NBD client process: Connecting...Activating... [stderr] nbd-client. [stderr] update-initramfs: deferring update (trigger activated) [stdout] Setting up nbd-server (1:3.7-1ubuntu0.1) ... [stderr] [stderr] Creating config file /etc/nbd-server/config with new version [stderr] Adding system user `nbd' (UID 108) ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Adding new group `nbd' (GID 113) ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Adding new user `nbd' (UID 108) with group `nbd' ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Not creating home directory `/etc/nbd-server'. [stderr] [stderr] ** (process:2877): WARNING **: Could not parse config file: The config file does not specify any exports [stderr] ** Message: No configured exports; quitting. [stderr] nbd-server. [stdout] Processing triggers for ureadahead (0.100.0-16) ... [stdout] Processing triggers for initramfs-tools (0.103ubuntu4.11) ... [stdout] update-initramfs: Generating /boot/initrd.img-4.15.0-1023-azure true' Runni
[Kernel-packages] [Bug 1767832] Re: ASUS touchpad right button not working
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767832 Title: ASUS touchpad right button not working Status in Ubuntu-Certification: Invalid Status in linux package in Ubuntu: Fix Committed Bug description: On my ASUS T304UA, the right button of the trackpad generates no input event whereas the left button and the left half part of the middle button works (checked with libinput-debug-events). I checked with the latest available kernel: 4.17.0-041700rc2-generic Needless to say that the trackpad perfectly works under Windows. The device is: Bus 001 Device 005: ID 0b05:184a ASUSTek Computer, Inc. I guess that the corresponding kernel driver is: hid_multitouch Example of libinput-debug-events : left click then right click : -event17 POINTER_BUTTON+1.11sBTN_LEFT (272) pressed, seat count: 1 event17 POINTER_BUTTON+1.23sBTN_LEFT (272) released, seat count: 0 It seems that there is a bug in the trackpad driver... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792973] Re: ubuntu_nbd_smoke_test failed on 4.15 Trusty Azure
I have this verified on Trusty 4.15 Azure, looks like the timeout issue does not exist anymore. However the test is still failing even with linux-modules- extra-4.15.0-1023-azure installed Output for this rerun: https://pastebin.ubuntu.com/p/sQKYKPysDd/ I'm wondering if this is related to releases, as I can see similar failures: server is not listening disconnect, sock, done stderr: umount: /mnt/nbd-test-1611: not found On bare-metal Trusty system, reports can be found in the comment of bug 1793321 The reason why this test was executed on Trusty that is we just implemented a new kernel-version based blacklist feature, and rename the blacklist from blacklist.trusty to blacklist.3.13.0. So as we're running 4.15 kernel on Trusty, this test was triggered. If this is not expected to work on Trusty, we can blacklist it again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1792973 Title: ubuntu_nbd_smoke_test failed on 4.15 Trusty Azure Status in ubuntu-kernel-tests: New Status in linux-signed-azure package in Ubuntu: New Bug description: The ubuntu_nbd_smoke test will timeout on a 4.15 Trusty Azure node. The test will get killed by the timeout setting and the job hangs. There is also a rmmod related error message: [stderr] rmmod: ERROR: Module nbd is not currently loaded Running 'DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes nbd-server nbd-client gdb' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] gdb is already the newest version. [stdout] The following NEW packages will be installed: [stdout] nbd-client nbd-server [stdout] 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. [stdout] Need to get 104 kB of archives. [stdout] After this operation, 430 kB of additional disk space will be used. [stdout] Get:1 http://azure.archive.ubuntu.com/ubuntu/ trusty-updates/main nbd-client amd64 1:3.7-1ubuntu0.1 [45.1 kB] [stdout] Get:2 http://azure.archive.ubuntu.com/ubuntu/ trusty-updates/main nbd-server amd64 1:3.7-1ubuntu0.1 [58.8 kB] [stdout] Preconfiguring packages ... [stdout] Fetched 104 kB in 0s (9,346 kB/s) [stdout] Selecting previously unselected package nbd-client. [stdout] (Reading database ... 54762 files and directories currently installed.) [stdout] Preparing to unpack .../nbd-client_1%3a3.7-1ubuntu0.1_amd64.deb ... [stdout] Unpacking nbd-client (1:3.7-1ubuntu0.1) ... [stdout] Selecting previously unselected package nbd-server. [stdout] Preparing to unpack .../nbd-server_1%3a3.7-1ubuntu0.1_amd64.deb ... [stdout] Unpacking nbd-server (1:3.7-1ubuntu0.1) ... [stdout] Processing triggers for man-db (2.6.7.1-1ubuntu1) ... [stdout] Processing triggers for ureadahead (0.100.0-16) ... [stdout] Setting up nbd-client (1:3.7-1ubuntu0.1) ... [stderr] Stopping NBD client process: [stderr] rmmod: ERROR: Module nbd is not currently loaded [stderr] nbd-client. [stderr] Starting NBD client process: Connecting...Activating... [stderr] nbd-client. [stderr] update-initramfs: deferring update (trigger activated) [stdout] Setting up nbd-server (1:3.7-1ubuntu0.1) ... [stderr] [stderr] Creating config file /etc/nbd-server/config with new version [stderr] Adding system user `nbd' (UID 108) ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Adding new group `nbd' (GID 113) ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Adding new user `nbd' (UID 108) with group `nbd' ... [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] sent invalidate(passwd) request, exiting [stderr] sent invalidate(group) request, exiting [stderr] Not creating home directory `/etc/nbd-server'. [stderr] [stderr] ** (process:2877): WARNING **: Could not parse config file: The config file does not specify any exports [stderr] ** Message: No configured exports; quitting. [stderr] nbd-server. [stdout] Processing triggers for ureadahead (0.100.0-16) ... [stdout] Processing triggers for initramfs-tools (0.103ubuntu4.11) ... [stdout] update-initramfs: G
[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Installed Linux Mint 19 32-bit xfce on HP 2710p. The bug is still there. video=SVIDEO-1:d boot option on live USB works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 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.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 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.8.0-36-generic N/A linux-backports-mod
[Kernel-packages] [Bug 1793508] Re: no matching swap device at initramfs
apport information ** Tags added: apport-collected bionic ** Description changed: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio + /dev/snd/controlC0: udippel3274 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 + InstallationDate: Installed on 2012-07-29 (2244 days ago) + InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) + MachineType: LENOVO 2904FXG + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-34-generic N/A + linux-backports-modules-4.15.0-34-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-34-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 10/11/2012 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6UET70WW (1.50 ) + dmi.board.name: 2904FXG + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.family: ThinkPad T410s + dmi.product.name: 2904FXG + dmi.product.version: ThinkPad T410s + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191100/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd6
[Kernel-packages] [Bug 1793508] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191101/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191106/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191110/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/519/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191104/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793508] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1793508/+attachment/5191109/+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/1793508 Title: no matching swap device at initramfs Status in linux package in Ubuntu: Incomplete Bug description: This is the result of a well-known - wrong - behaviour. It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty of help, unambiguously. Like https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151 https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available and many more. However, I couldn't find a bug report for it. It struck me at the upgrade from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet, I could not find a real explanation nor a bug report. In my case, like in many of those, the UUID for resume was kind of 'out of the blue'. And once changed to the real UUID for the swap device, everything is fine. However, I am not happy with a situation like that. Many a user that we tried over the last 20 years to adopt Linux as main OS will not want to search Google for this bug, and will not want to vi (or similar) some system file. Therefore I take the liberty to report this. From the dates of the posts, it seems that this bug has been lingering for quite some time, Wouldn't it be the right moment to prevent it from striking again? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D8p: udippel3274 F...m pulseaudio /dev/snd/controlC0: udippel3274 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e0d4bc2a-197e-4934-9a9b-70c57cdf4fa8 InstallationDate: Installed on 2012-07-29 (2244 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MachineType: LENOVO 2904FXG NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=5f392269-154d-4ccc-bc24-920438d4651c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2904FXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2904FXG:pvrThinkPadT410s:rvnLENOVO:rn2904FXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2904FXG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
