[Kernel-packages] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen (kernel crash in 0010:gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915])
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen (kernel crash in 0010:gen8_ppgtt_set_pde.isra.43+0x45/0x60 [i915]) Status in linux package in Ubuntu: Expired Bug description: This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug #1820030 I was trying to report a frozen GUI over SSH. This is the second report that apport-cli generated when I ran it with xorg as the target package. I made three four reports to see if different diagnostics were geneereated as Ihave no way of knowing what is causing the lock up at present. The symptoms I see are that I started running a go test last night and my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless mouse or keyboard to move anything on the display and the time shown on the clock matches when things froze last night. Before I made the report I looked for any process using high amounts of CUP with top and htop but spotted none. I tried to local a SIGTERM the go test process but that made no difference. I shall attempt to restart my desktop service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 14 09:12:51 2019 DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] InstallationDate: Installed on 2017-11-16 (482 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused Error: unable to open display UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago) dmi.bios.date: 09/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0811 dmi.board.asset.tag: Default string dmi.board.name: STRIX H270F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Mar 12 13:46:44 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819420] Re: Apparent bug: Dell tablet crashes when plugged into docking station with 4.15.0-46 kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819420 Title: Apparent bug: Dell tablet crashes when plugged into docking station with 4.15.0-46 kernel Status in linux package in Ubuntu: Expired Bug description: This appears to be the same bug that was present, two kernels ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795 I switched to the 46 kernel from the 45 today, and noticed my tablet hangs when its plugged into the docking station. Without the docking station it appears fine. As with the previous bug, even when it hangs, I can ssh into the tablet. So it appears to be the user interface that's frozen. The mouse pointer remains mobile. Note: this run of apport is pre-crash. Note 2: I encountered this bug three boots in a row yesterday. But today I have been unable to duplicate it. So I'm a little confused. I'll try to duplicate the bug again tonight. If I can't, I'll close this thread. Note 3: I have been unable to duplicate this bug. Please consider this case resolved. If I can find a way to duplicate it, I will start another thread. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rybu 2013 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f InstallationDate: Installed on 2018-11-09 (122 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 5290 2-in-1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.3 dmi.board.name: 0M27Y3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5290 2-in-1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Tested with the latest mainline kernel on Baltar:
ubuntu@baltar:~$ uname -a
Linux baltar 5.1.1-050101-generic #201905110631 SMP Sat May 11 07:16:36 UTC
2019 ppc64le ppc64le ppc64le GNU/Linux
This issue still exist.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 - phase: Ready for Testing - phase-changed: Thursday, 09. May 2019 09:34 UTC + phase: Holding before Release + phase-changed: Tuesday, 14. May 2019 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for 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/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Holding before Release phase-changed: Tuesday, 14. May 2019 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828919] 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 1828919 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/1828919 Title: ptrace-tm-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: selftests: ptrace-tm-tar test: ptrace_tm_tar tags: git_version:unknown ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 99 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 110 failure: ptrace_tm_tar not ok 1..5 selftests: ptrace-tm-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828918] 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 1828918 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/1828918 Title: ptrace-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: selftests: ptrace-tar test: ptrace_tar tags: git_version:unknown failure: ptrace_tar not ok 1..4 selftests: ptrace-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828920] 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 1828920 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/1828920 Title: ptrace_tm_spd_tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: selftests: ptrace-tm-spd-tar test: ptrace_tm_spd_tar tags: git_version:unknown failure: ptrace_tm_spd_tar not ok 1..6 selftests: ptrace-tm-spd-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
4.4.0-1009.11 - fips Regression test CMPL, RTB. 51 / 54 tests were run, missing: ubuntu_boot, ubuntu_ramfs_stress, xfstests Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 (bug 1828813) sync_file_range02 (bug 1819116) 48 / 49 tests were run, missing: ubuntu_boot Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_kernel_selftests - failed to build reuseport_bpf (bug 1828912) dscr_inherit_test (bug 1828913) dscr_inherit_exec_test (bug 1828915) ptrace-tm-gpr (bug 1828916) ptrace-tm-spd-gpr (bug 1828917) ptrace-tar (bug 1828918) ptrace-tm-tar (bug 1828919) ptrace_tm_spd_tar (bug 1828920) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) xfstests - btrfs generic/176 timed out Note: Missing s390x test result (bug 1825099) ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Ready for Testing phase-changed: Thursday, 09. May 2019 09:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828919] [NEW] ptrace-tm-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: selftests: ptrace-tm-tar test: ptrace_tm_tar tags: git_version:unknown ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 99 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 110 failure: ptrace_tm_tar not ok 1..5 selftests: ptrace-tm-tar [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828919 Title: ptrace-tm-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: selftests: ptrace-tm-tar test: ptrace_tm_tar tags: git_version:unknown ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 99 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 110 failure: ptrace_tm_tar not ok 1..5 selftests: ptrace-tm-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828920] [NEW] ptrace_tm_spd_tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: selftests: ptrace-tm-spd-tar test: ptrace_tm_spd_tar tags: git_version:unknown failure: ptrace_tm_spd_tar not ok 1..6 selftests: ptrace-tm-spd-tar [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828920 Title: ptrace_tm_spd_tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: selftests: ptrace-tm-spd-tar test: ptrace_tm_spd_tar tags: git_version:unknown failure: ptrace_tm_spd_tar not ok 1..6 selftests: ptrace-tm-spd-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828917] 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 1828917 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/1828917 Title: ptrace-tm-spd-gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: ptrace_tm_spd_gpr tags: git_version:unknown FPR[0]: 3f50624de000 Expected: 3f70624de000 FPR[1]: 3f50624de000 Expected: 3f70624de000 FPR[2]: 3f50624de000 Expected: 3f70624de000 FPR[3]: 3f50624de000 Expected: 3f70624de000 FPR[4]: 3f50624de000 Expected: 3f70624de000 FPR[5]: 3f50624de000 Expected: 3f70624de000 FPR[6]: 3f50624de000 Expected: 3f70624de000 FPR[7]: 3f50624de000 Expected: 3f70624de000 FPR[8]: 3f50624de000 Expected: 3f70624de000 FPR[9]: 3f50624de000 Expected: 3f70624de000 FPR[10]: 3f50624de000 Expected: 3f70624de000 FPR[11]: 3f50624de000 Expected: 3f70624de000 FPR[12]: 3f50624de000 Expected: 3f70624de000 FPR[13]: 3f50624de000 Expected: 3f70624de000 FPR[14]: 3f50624de000 Expected: 3f70624de000 FPR[15]: 3f50624de000 Expected: 3f70624de000 FPR[16]: 3f50624de000 Expected: 3f70624de000 FPR[17]: 3f50624de000 Expected: 3f70624de000 FPR[18]: 3f50624de000 Expected: 3f70624de000 [FAIL] Test FAILED on line 106 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 60 FPR[19]: 3f50624de000 Expected: 3f70624de000 FPR[20]: 3f50624de000 Expected: 3f70624de000 FPR[21]: 3f50624de000 Expected: 3f70624de000 FPR[22]: 3f50624de000 Expected: 3f70624de000 FPR[23]: 3f50624de000 Expected: 3f70624de000 FPR[24]: 3f50624de000 Expected: 3f70624de000 FPR[25]: 3f50624de000 Expected: 3f70624de000 FPR[26]: 3f50624de000 Expected: 3f70624de000 FPR[27]: 3f50624de000 Expected: 3f70624de000 FPR[28]: 3f50624de000 Expected: 3f70624de000 FPR[29]: 3f50624de000 Expected: 3f70624de000 FPR[30]: 3f50624de000 Expected: 3f70624de000 FPR[31]: 3f50624de000 Expected: 3f70624de000 failure: ptrace_tm_spd_gpr not ok 1..3 selftests: ptrace-tm-spd-gpr [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828913] 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 1828913 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/1828913 Title: dscr_inherit_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: selftests: dscr_inherit_test test: dscr_inherit_test tags: git_version:unknown Kernel DSCR should be 3 but is 2 failure: dscr_inherit_test not ok 1..4 selftests: dscr_inherit_test [FAIL] Child didn't exit cleanly selftests: dscr_inherit_exec_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828912] 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 1828912 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/1828912 Title: Failed to build reuseport_bpf test in net from ubuntu_kernel_selftests on PowerPC with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf ../lib.mk:109: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' Makefile:72: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: reuseport_bpf.c: In function ‘attach_ebpf’: reuseport_bpf.c:126:33: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:126:33: note: each undeclared identifier is reported only once for each function it appears in reuseport_bpf.c: In function ‘attach_cbpf’: reuseport_bpf.c:148:33: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , sizeof(p))) ^ reuseport_bpf.c: In function ‘test_filter_no_reuseport’: reuseport_bpf.c:378:34: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:383:34: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , ^ make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf] Error 1 make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828915] 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 1828915 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/1828915 Title: dscr_inherit_exec_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: dscr_inherit_exec_test tags: git_version:unknown Parent DSCR 3 was not inherited over exec (kernel value) failure: dscr_inherit_exec_test not ok 1..5 selftests: dscr_inherit_exec_test [FAIL] Child didn't exit cleanly selftests: dscr_sysfs_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828917] [NEW] ptrace-tm-spd-gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: test: ptrace_tm_spd_gpr tags: git_version:unknown FPR[0]: 3f50624de000 Expected: 3f70624de000 FPR[1]: 3f50624de000 Expected: 3f70624de000 FPR[2]: 3f50624de000 Expected: 3f70624de000 FPR[3]: 3f50624de000 Expected: 3f70624de000 FPR[4]: 3f50624de000 Expected: 3f70624de000 FPR[5]: 3f50624de000 Expected: 3f70624de000 FPR[6]: 3f50624de000 Expected: 3f70624de000 FPR[7]: 3f50624de000 Expected: 3f70624de000 FPR[8]: 3f50624de000 Expected: 3f70624de000 FPR[9]: 3f50624de000 Expected: 3f70624de000 FPR[10]: 3f50624de000 Expected: 3f70624de000 FPR[11]: 3f50624de000 Expected: 3f70624de000 FPR[12]: 3f50624de000 Expected: 3f70624de000 FPR[13]: 3f50624de000 Expected: 3f70624de000 FPR[14]: 3f50624de000 Expected: 3f70624de000 FPR[15]: 3f50624de000 Expected: 3f70624de000 FPR[16]: 3f50624de000 Expected: 3f70624de000 FPR[17]: 3f50624de000 Expected: 3f70624de000 FPR[18]: 3f50624de000 Expected: 3f70624de000 [FAIL] Test FAILED on line 106 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 60 FPR[19]: 3f50624de000 Expected: 3f70624de000 FPR[20]: 3f50624de000 Expected: 3f70624de000 FPR[21]: 3f50624de000 Expected: 3f70624de000 FPR[22]: 3f50624de000 Expected: 3f70624de000 FPR[23]: 3f50624de000 Expected: 3f70624de000 FPR[24]: 3f50624de000 Expected: 3f70624de000 FPR[25]: 3f50624de000 Expected: 3f70624de000 FPR[26]: 3f50624de000 Expected: 3f70624de000 FPR[27]: 3f50624de000 Expected: 3f70624de000 FPR[28]: 3f50624de000 Expected: 3f70624de000 FPR[29]: 3f50624de000 Expected: 3f70624de000 FPR[30]: 3f50624de000 Expected: 3f70624de000 FPR[31]: 3f50624de000 Expected: 3f70624de000 failure: ptrace_tm_spd_gpr not ok 1..3 selftests: ptrace-tm-spd-gpr [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: test: ptrace_tm_spd_gpr tags: git_version:unknown FPR[0]: 3f50624de000 Expected: 3f70624de000 FPR[1]: 3f50624de000 Expected: 3f70624de000 FPR[2]: 3f50624de000 Expected: 3f70624de000 FPR[3]: 3f50624de000 Expected: 3f70624de000 FPR[4]: 3f50624de000 Expected: 3f70624de000 FPR[5]: 3f50624de000 Expected: 3f70624de000 FPR[6]: 3f50624de000 Expected: 3f70624de000 FPR[7]: 3f50624de000 Expected: 3f70624de000 FPR[8]: 3f50624de000 Expected: 3f70624de000 FPR[9]: 3f50624de000 Expected: 3f70624de000 FPR[10]: 3f50624de000 Expected: 3f70624de000 FPR[11]: 3f50624de000 Expected: 3f70624de000 FPR[12]: 3f50624de000 Expected: 3f70624de000 FPR[13]: 3f50624de000 Expected: 3f70624de000 FPR[14]: 3f50624de000 Expected: 3f70624de000 FPR[15]: 3f50624de000 Expected: 3f70624de000 FPR[16]: 3f50624de000 Expected: 3f70624de000 FPR[17]: 3f50624de000 Expected: 3f70624de000 FPR[18]: 3f50624de000 Expected: 3f70624de000 [FAIL] Test FAILED on line 106 ptrace(PTRACE_GETREGSET) failed: Invalid argument [FAIL] Test FAILED on line 60 FPR[19]: 3f50624de000 Expected: 3f70624de000 FPR[20]: 3f50624de000 Expected: 3f70624de000 FPR[21]: 3f50624de000 Expected: 3f70624de000 FPR[22]: 3f50624de000 Expected: 3f70624de000 FPR[23]: 3f50624de000 Expected: 3f70624de000 FPR[24]: 3f50624de000 Expected: 3f70624de000 FPR[25]: 3f50624de000 Expected: 3f70624de000 FPR[26]: 3f50624de000 Expected: 3f70624de000 FPR[27]: 3f50624de000 Expected: 3f70624de000 FPR[28]: 3f50624de000 Expected: 3f70624de000 FPR[29]: 3f50624de000 Expected: 3f70624de000 FPR[30]: 3f50624de000 Expected: 3f70624de000 FPR[31]: 3f50624de000 Expected: 3f70624de000 failure: ptrace_tm_spd_gpr not ok 1..3 selftests: ptrace-tm-spd-gpr [FAIL] - selftests: ptrace-tar ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Summary changed: - ptrace-tm-spd-gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Edit + ptrace-tm-spd-gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828917 Title: ptrace-tm-spd-gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: ptrace_tm_spd_gpr tags: git_version:unknown FPR[0]: 3f50624de000 Expected: 3f70624de000 FPR[1]: 3f50624de000 Expected: 3f70624de000 FPR[2]:
[Kernel-packages] [Bug 1828916] 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 1828916 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/1828916 Title: ptrace_tm_gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: ptrace_tm_gpr tags: git_version:unknown [FAIL] Test FAILED on line 100 FPR[0]: 3f50624de000 Expected: 3f60624de000 FPR[1]: 3f50624de000 Expected: 3f60624de000 FPR[2]: 3f50624de000 Expected: 3f60624de000 FPR[3]: 3f50624de000 Expected: 3f60624de000 FPR[4]: 3f50624de000 Expected: 3f60624de000 FPR[5]: 3f50624de000 Expected: 3f60624de000 FPR[6]: 3f50624de000 Expected: 3f60624de000 FPR[7]: 3f50624de000 Expected: 3f60624de000 FPR[8]: 3f50624de000 Expected: 3f60624de000 FPR[9]: 3f50624de000 Expected: 3f60624de000 FPR[10]: 3f50624de000 Expected: 3f60624de000 FPR[11]: 3f50624de000 Expected: 3f60624de000 FPR[12]: 3f50624de000 Expected: 3f60624de000 FPR[13]: 3f50624de000 Expected: 3f60624de000 FPR[14]: 3f50624de000 Expected: 3f60624de000 FPR[15]: 3f50624de000 Expected: 3f60624de000 FPR[16]: 3f50624de000 Expected: 3f60624de000 FPR[17]: 3f50624de000 Expected: 3f60624de000 FPR[18]: 3f50624de000 Expected: 3f60624de000 FPR[19]: 3f50624de000 Expected: 3f60624de000 FPR[20]: 3f50624de000 Expected: 3f60624de000 FPR[21]: 3f50624de000 Expected: 3f60624de000 FPR[22]: 3f50624de000 Expected: 3f60624de000 FPR[23]: 3f50624de000 Expected: 3f60624de000 FPR[24]: 3f50624de000 Expected: 3f60624de000 FPR[25]: 3f50624de000 Expected: 3f60624de000 FPR[26]: 3f50624de000 Expected: 3f60624de000 FPR[27]: 3f50624de000 Expected: 3f60624de000 FPR[28]: 3f50624de000 Expected: 3f60624de000 FPR[29]: 3f50624de000 Expected: 3f60624de000 FPR[30]: 3f50624de000 Expected: 3f60624de000 FPR[31]: 3f50624de000 Expected: 3f60624de000 failure: ptrace_tm_gpr not ok 1..2 selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828918] [NEW] ptrace-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: selftests: ptrace-tar test: ptrace_tar tags: git_version:unknown failure: ptrace_tar not ok 1..4 selftests: ptrace-tar [FAIL] ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: selftests: ptrace-tar test: ptrace_tar tags: git_version:unknown failure: ptrace_tar not ok 1..4 selftests: ptrace-tar [FAIL] - selftests: ptrace-tm-tar ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828918 Title: ptrace-tar in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: selftests: ptrace-tar test: ptrace_tar tags: git_version:unknown failure: ptrace_tar not ok 1..4 selftests: ptrace-tar [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828913] [NEW] dscr_inherit_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: selftests: dscr_inherit_test test: dscr_inherit_test tags: git_version:unknown Kernel DSCR should be 3 but is 2 failure: dscr_inherit_test not ok 1..4 selftests: dscr_inherit_test [FAIL] Child didn't exit cleanly selftests: dscr_inherit_exec_test ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - dscr_inherit_test in power failed on Power8 with X-fips + dscr_inherit_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828913 Title: dscr_inherit_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: selftests: dscr_inherit_test test: dscr_inherit_test tags: git_version:unknown Kernel DSCR should be 3 but is 2 failure: dscr_inherit_test not ok 1..4 selftests: dscr_inherit_test [FAIL] Child didn't exit cleanly selftests: dscr_inherit_exec_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828916] [NEW] ptrace_tm_gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: test: ptrace_tm_gpr tags: git_version:unknown [FAIL] Test FAILED on line 100 FPR[0]: 3f50624de000 Expected: 3f60624de000 FPR[1]: 3f50624de000 Expected: 3f60624de000 FPR[2]: 3f50624de000 Expected: 3f60624de000 FPR[3]: 3f50624de000 Expected: 3f60624de000 FPR[4]: 3f50624de000 Expected: 3f60624de000 FPR[5]: 3f50624de000 Expected: 3f60624de000 FPR[6]: 3f50624de000 Expected: 3f60624de000 FPR[7]: 3f50624de000 Expected: 3f60624de000 FPR[8]: 3f50624de000 Expected: 3f60624de000 FPR[9]: 3f50624de000 Expected: 3f60624de000 FPR[10]: 3f50624de000 Expected: 3f60624de000 FPR[11]: 3f50624de000 Expected: 3f60624de000 FPR[12]: 3f50624de000 Expected: 3f60624de000 FPR[13]: 3f50624de000 Expected: 3f60624de000 FPR[14]: 3f50624de000 Expected: 3f60624de000 FPR[15]: 3f50624de000 Expected: 3f60624de000 FPR[16]: 3f50624de000 Expected: 3f60624de000 FPR[17]: 3f50624de000 Expected: 3f60624de000 FPR[18]: 3f50624de000 Expected: 3f60624de000 FPR[19]: 3f50624de000 Expected: 3f60624de000 FPR[20]: 3f50624de000 Expected: 3f60624de000 FPR[21]: 3f50624de000 Expected: 3f60624de000 FPR[22]: 3f50624de000 Expected: 3f60624de000 FPR[23]: 3f50624de000 Expected: 3f60624de000 FPR[24]: 3f50624de000 Expected: 3f60624de000 FPR[25]: 3f50624de000 Expected: 3f60624de000 FPR[26]: 3f50624de000 Expected: 3f60624de000 FPR[27]: 3f50624de000 Expected: 3f60624de000 FPR[28]: 3f50624de000 Expected: 3f60624de000 FPR[29]: 3f50624de000 Expected: 3f60624de000 FPR[30]: 3f50624de000 Expected: 3f60624de000 FPR[31]: 3f50624de000 Expected: 3f60624de000 failure: ptrace_tm_gpr not ok 1..2 selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828916 Title: ptrace_tm_gpr in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: ptrace_tm_gpr tags: git_version:unknown [FAIL] Test FAILED on line 100 FPR[0]: 3f50624de000 Expected: 3f60624de000 FPR[1]: 3f50624de000 Expected: 3f60624de000 FPR[2]: 3f50624de000 Expected: 3f60624de000 FPR[3]: 3f50624de000 Expected: 3f60624de000 FPR[4]: 3f50624de000 Expected: 3f60624de000 FPR[5]: 3f50624de000 Expected: 3f60624de000 FPR[6]: 3f50624de000 Expected: 3f60624de000 FPR[7]: 3f50624de000 Expected: 3f60624de000 FPR[8]: 3f50624de000 Expected: 3f60624de000 FPR[9]: 3f50624de000 Expected: 3f60624de000 FPR[10]: 3f50624de000 Expected: 3f60624de000 FPR[11]: 3f50624de000 Expected: 3f60624de000 FPR[12]: 3f50624de000 Expected: 3f60624de000 FPR[13]: 3f50624de000 Expected: 3f60624de000 FPR[14]: 3f50624de000 Expected: 3f60624de000 FPR[15]: 3f50624de000 Expected: 3f60624de000 FPR[16]: 3f50624de000 Expected: 3f60624de000 FPR[17]: 3f50624de000 Expected: 3f60624de000 FPR[18]: 3f50624de000 Expected: 3f60624de000 FPR[19]: 3f50624de000 Expected: 3f60624de000 FPR[20]: 3f50624de000 Expected: 3f60624de000 FPR[21]: 3f50624de000 Expected: 3f60624de000 FPR[22]: 3f50624de000 Expected: 3f60624de000 FPR[23]: 3f50624de000 Expected: 3f60624de000 FPR[24]: 3f50624de000 Expected: 3f60624de000 FPR[25]: 3f50624de000 Expected: 3f60624de000 FPR[26]: 3f50624de000 Expected: 3f60624de000 FPR[27]: 3f50624de000 Expected: 3f60624de000 FPR[28]: 3f50624de000 Expected: 3f60624de000 FPR[29]: 3f50624de000 Expected: 3f60624de000 FPR[30]: 3f50624de000 Expected: 3f60624de000 FPR[31]: 3f50624de000 Expected: 3f60624de000 failure: ptrace_tm_gpr not ok 1..2 selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828915] [NEW] dscr_inherit_exec_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips
Public bug reported: test: dscr_inherit_exec_test tags: git_version:unknown Parent DSCR 3 was not inherited over exec (kernel value) failure: dscr_inherit_exec_test not ok 1..5 selftests: dscr_inherit_exec_test [FAIL] Child didn't exit cleanly selftests: dscr_sysfs_test ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828915 Title: dscr_inherit_exec_test in powerpc from ubuntu_kernel_selftests failed on Power8 with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: test: dscr_inherit_exec_test tags: git_version:unknown Parent DSCR 3 was not inherited over exec (kernel value) failure: dscr_inherit_exec_test not ok 1..5 selftests: dscr_inherit_exec_test [FAIL] Child didn't exit cleanly selftests: dscr_sysfs_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828912] [NEW] Failed to build reuseport_bpf test in net from ubuntu_kernel_selftests on PowerPC with X-fips
Public bug reported: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf ../lib.mk:109: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' Makefile:72: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: reuseport_bpf.c: In function ‘attach_ebpf’: reuseport_bpf.c:126:33: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:126:33: note: each undeclared identifier is reported only once for each function it appears in reuseport_bpf.c: In function ‘attach_cbpf’: reuseport_bpf.c:148:33: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , sizeof(p))) ^ reuseport_bpf.c: In function ‘test_filter_no_reuseport’: reuseport_bpf.c:378:34: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:383:34: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , ^ make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf] Error 1 make: *** [all] Error 2 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828912 Title: Failed to build reuseport_bpf test in net from ubuntu_kernel_selftests on PowerPC with X-fips Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf ../lib.mk:109: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' Makefile:72: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: reuseport_bpf.c: In function ‘attach_ebpf’: reuseport_bpf.c:126:33: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:126:33: note: each undeclared identifier is reported only once for each function it appears in reuseport_bpf.c: In function ‘attach_cbpf’: reuseport_bpf.c:148:33: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , sizeof(p))) ^ reuseport_bpf.c: In function ‘test_filter_no_reuseport’: reuseport_bpf.c:378:34: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:383:34: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , ^ make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf] Error 1 make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809224] Re: To support Intel Wireless-AX 22000 series
** Description changed: [Impact] - + New Intel Cyclone Peak Wifi doesn't work without newly added driver. + [Fix] + Cherry pick iwlwifi commits from v5.0 to v5.1, and confirmed with proper firmware the wifi works. [Test] + Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Potential] + Medium, it affects the whole iwlwifi driver, but I've verified it with fwst S3 test, and the wifi is still working after S3 test 30 times. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809224 Title: To support Intel Wireless-AX 22000 series Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] New Intel Cyclone Peak Wifi doesn't work without newly added driver. [Fix] Cherry pick iwlwifi commits from v5.0 to v5.1, and confirmed with proper firmware the wifi works. [Test] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Potential] Medium, it affects the whole iwlwifi driver, but I've verified it with fwst S3 test, and the wifi is still working after S3 test 30 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801140] Re: Strange screen behaviour with tearing
** Tags added: cosmic ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1801140 Title: Strange screen behaviour with tearing Status in nvidia-graphics-drivers-410 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: It's a known issue the amount of screen tearing when using the Optimus NVIDIA card, and with PRIME sync this is partially fixed, but the games are unplayable due to the input lag. But I'm figuring out another issue that I'm not sure about what the cause can be. I'm getting solid fps in games, but they feel choppy and different from Windows even with the same fps, tested in a lot of games, I don't know if that has something to do with the screen tearing but they look like false fps drops or a screen refresh rate issue, I'm 100% sure that they are not fps drops, the fps are stable, so that's why I think it could be extreme screen tearing or refresh rate, this is very annoying when you play games. Screen tearing is obviously occurring also in Windows, but in there it doesn't feel choppy as when playing on Linux. Same games on my non-prime desktop, with the same NVIDIA driver feel a lot different. NVIDIA driver 410 (from graphics-drivers repo) Kubuntu 18.10 with compositing disabled Tested games: Steam half life 2, Lutris DXVK Overwatch and Heroes of the storm NVIDIA GTX 960m on Dell XPS 15 9550 i5 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-410/+bug/1801140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Doesn't work for me. I have sound chip Realtek ALC236, is that the same as yours? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I've had these freeze issues for a while, and I've been following this thread for a while (comment #42 helped, though I still have occasional freezes). Googled "Fedora random freeze" today and found this: https://fedoraproject.org/wiki/Common_F28_bugs#Certain_laptops_.28Lenovo.29_hang_randomly Apparently an issue in Ubuntu also: https://www.phoronix.com/forums/forum/software/desktop-linux/1020821 -fedora-workstation-28-is-shaping-up-to-be-another-terrific- update?p=1020982#post1020982 And the timing of these bugreports/comments coincides with when these freezes started affecting me... Long story short, we can try adding `ahci.mobile_lpm_policy=1` or `ahci.mobile_lpm_policy=0` to the kernel options in grub. Supposedly confirmed to help Lenovo G50-80, X250 and T450s. We have a G40-80 and T470s affected on this thread, and mine's a Lenovo G500s (similar to G50-80). Maybe it'll help? (praying that it helps) It's possible that these freezes have multiple causes, and won't be completely fixed even if the workaround helps at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263523/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263525/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263530/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263524/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263521/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263522/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263529/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263520/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263528/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263527/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263526/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sidboswell 1563 F pulseaudio /dev/snd/controlC2: sidboswell 1563 F pulseaudio /dev/snd/controlC0: sidboswell 1563 F pulseaudio /dev/snd/controlC1: sidboswell 1563 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-20 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: ens132no wireless extensions. ens133no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828613] Re: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged
apport information ** Tags added: apport-collected ** Description changed: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: sidboswell 1563 F pulseaudio + /dev/snd/controlC2: sidboswell 1563 F pulseaudio + /dev/snd/controlC0: sidboswell 1563 F pulseaudio + /dev/snd/controlC1: sidboswell 1563 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-04-20 (22 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + IwConfig: + ens132no wireless extensions. + + ens133no wireless extensions. + + lono wireless extensions. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=32bb5737-4f6a-439a-b9b3-8784fa07fcb7 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + RfKill: + + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/23/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 080016 + dmi.board.name: EVGA P55 3X SLI E658 + dmi.board.vendor: EVGA + dmi.board.version: Ibex Peak + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1828613/+attachment/5263519/+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/1828613 Title: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged Status in linux package in Ubuntu: Confirmed Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago)
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
https://lists.freedesktop.org/archives/systemd- devel/2019-May/042570.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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: New Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: New Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: New Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-05-13 17:04 EDT--- Adding Paul Mackerras - can you help with the context for the patches - beyond the potential performance impact? We were picking up this series because it fixes the migration problem, which appeared after adding a patch for bug 169712 for performance. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530
Just as a usage report after a while: I mostly have to reboot the device after first boot again, as the recognition of the two/three finger gestures isn't working correctly aswell as the scrolling. It appears then that after using such gestures, the mouse hangs in the gesture mode. E.g. after scrolling with two fingers it stays in scroll mode even with only one finger until I scroll again. If I reboot the device again, this behaviour is fixed for the uptime. Apart from that: I had more and more problems, that my ssd out of a sudden disappeard from the system. I found the following kernel parameter that fixed it for me: nvme_core.default_ps_max_latency_us=0 Would be nice to hear if others have these things aswell, or if it's only me. Greetings, L -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] AMD MP2 I2C driver doesn't support more than one bus. This makes touchpad on Lenovo Yoga 530 doensn't work as expected. [Fix] Sync the MP2 driver with upstream version. [Test] The new upstream driver doesn't break on Latitude 5495. Users haven't given any feedback yet, but since Disco is freezing I am sending this out. [Regression Potential] Low. It's from upstream, and only a subset of Raven Ridge has this device. === Original Bug Report === The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826596] Re: Cannot boot on kernel 4.18.0-18-generic, usb ports do not wake
Now works, new memory module installed, could be related, could be new version fix. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826596 Title: Cannot boot on kernel 4.18.0-18-generic, usb ports do not wake Status in linux package in Ubuntu: Invalid Bug description: Keyboard remains inactive on boot, system freezes, black screen only. Safemode displays first two lines on screen on boot and that's it, system hangs. Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Log created: 2019-02-28T01:06:56.667227000Z Executable: /usr/lib/virtualbox/VBoxSVC Arg[0]: /usr/lib/virtualbox/VBoxSVC Arg[1]: --auto-shutdown AddRef: illegal refcnt=3221225469 state=2 System:Host: [redacted] Kernel: 4.18.0-17-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.10 wm: muffin dm: LightDM Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: Micro-Star model: B350M MORTAR ARCTIC (MS-7A37) v: 2.0 serial: UEFI: American Megatrends v: A.I0 date: 01/22/2019 CPU: Topology: 6-Core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 76787 Speed: 1377 MHz min/max: 1550/3200 MHz Core speeds (MHz): 1: 1376 2: 1375 3: 1377 4: 1375 5: 1376 6: 1376 7: 1376 8: 1374 9: 1376 10: 1377 11: 1376 12: 1377 Graphics: Device-1: AMD Lexa XT [Radeon PRO WX 3100] driver: amdgpu v: kernel bus ID: 1c:00.0 chip ID: 1002:6985 Display: x11 server: X.Org 1.19.6 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz, 2560x1440~60Hz OpenGL: renderer: AMD Radeon Pro WX3100 (POLARIS12 DRM 3.26.0 4.18.0-17-generic LLVM 7.0.0) v: 4.5 Mesa 18.2.8 compat-v: 4.4 direct render: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Description changed: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] + Restricted to SMMUv3 arm64-based systems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828868] [NEW] crashdump fails on HiSilicon D06
Public bug reported: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Comment #35. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828861] 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/1828861 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Ideapad 320-15lKB Stopped working after i installed 'sysinfo' and then uninstalled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neves 3054 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 13 17:43:54 2019 HibernationDevice: RESUME=UUID=c2aebe62-0b20-41d6-827b-3339bc476240 InstallationDate: Installed on 2018-10-13 (212 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:210f Acer, Inc Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1e0839e0-ac0d-4493-8ef5-64c03b6a6752 ro quiet splash noresume vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
@longli I would like your assessment of the changes that we've made here to get back to expected performance. I know we are not getting the same results on NVMe devices with 16.04 and 18.04 and I'm wondering if there's something substantially different with the 4.15 kernel in use on 16.04 that prevents us from making the same changes that we did with 4.18 to get better performance. -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828861] [NEW] Touchpad not working
Public bug reported: Lenovo Ideapad 320-15lKB Stopped working after i installed 'sysinfo' and then uninstalled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neves 3054 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 13 17:43:54 2019 HibernationDevice: RESUME=UUID=c2aebe62-0b20-41d6-827b-3339bc476240 InstallationDate: Installed on 2018-10-13 (212 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:210f Acer, Inc Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1e0839e0-ac0d-4493-8ef5-64c03b6a6752 ro quiet splash noresume vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828861 Title: Touchpad not working Status in linux package in Ubuntu: New Bug description: Lenovo Ideapad 320-15lKB Stopped working after i installed 'sysinfo' and then uninstalled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neves 3054 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 13 17:43:54 2019 HibernationDevice: RESUME=UUID=c2aebe62-0b20-41d6-827b-3339bc476240 InstallationDate: Installed on 2018-10-13 (212 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:210f Acer, Inc Bus 001 Device 003: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1038:1729 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80XL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1e0839e0-ac0d-4493-8ef5-64c03b6a6752 ro quiet splash noresume vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
This patch was intended to increase performance, not reduce it. Is it too late to revert it? -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
** Tags added: patch -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations
dom xml is attached. netbeans is the version in bionic- updates/-security, 10.0-3~18.04.1ubuntu1. I should note that the jvmjre used is 11.0.3+7-1ubuntu2~18.04.1, which is not in the archive yet (but will be soon), as it's a security update for openjdk that I'm testing in the vm. ** Attachment added: "dom xml description" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828632/+attachment/5263472/+files/sec-bionic-i386.xml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828632 Title: bionic i386 kernel crashes in memory pressure situations Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be made to crash in a kvm guest with memory pressure. The reproducer used is to attempt to run netbeans with openjdk-8-jre installed as the only jvm. It will fail to run, and when it fails, it also causes gnome-shell to crash. After 3 to 5 repeats of this, the kernel will crash with the following oops in dmesg: [ 545.926175] rfkill: input handler enabled [ 546.117550] [ cut here ] [ 546.117552] kernel BUG at /build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268! [ 546.117564] invalid opcode: [#1] SMP PTI [ 546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_e vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress r aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy drm pata_acpi i2c_piix4 [ 546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic #53-Ubuntu [ 546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 546.117618] EIP: vmalloc_fault+0x229/0x240 [ 546.117618] EFLAGS: 00010086 CPU: 0 [ 546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: [ 546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918 [ 546.117621] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0 [ 546.117624] Call Trace: [ 546.117637] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117638] __do_page_fault+0x39d/0x510 [ 546.117640] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117641] do_page_fault+0x27/0xf0 [ 546.117644] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117645] do_async_page_fault+0x55/0x90 [ 546.117655] common_exception+0x130/0x136 [ 546.117659] EIP: qxl_image_init+0x338/0x390 [qxl] [ 546.117659] EFLAGS: 00010286 CPU: 0 [ 546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030 [ 546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4 [ 546.117661] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117663] ? ioremap_nocache+0x12/0x20 [ 546.117665] qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl] [ 546.117668] qxl_primary_atomic_update+0x159/0x2c0 [qxl] [ 546.117680] drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper] [ 546.117684] drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper] [ 546.117688] commit_tail+0x5d/0x60 [drm_kms_helper] [ 546.117691] drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper] [ 546.117695] ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper] [ 546.117715] drm_atomic_commit+0x3f/0x50 [drm] [ 546.117719] restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper] [ 546.117723] restore_fbdev_mode+0x2c/0x150 [drm_kms_helper] [ 546.117725] ? _cond_resched+0x17/0x40 [ 546.117729] drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 [drm_kms_helper] [ 546.117732] drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper] [ 546.117743] fb_set_var+0x1a9/0x440 [ 546.117750] ? wakeup_preempt_entity+0x73/0x80 [ 546.117752] ? check_preempt_wakeup+0x108/0x230 [ 546.117753] ? check_cfs_rq_runtime+0x70/0x70 [ 546.117755] ? check_preempt_curr+0x27/0x80 [ 546.117757] ? ttwu_do_wakeup+0x17/0x190 [ 546.117760] fbcon_blank+0x29e/0x370 [ 546.117772] ? __switch_to_asm+0x27/0x4c [ 546.117774] ? fbcon_cursor+0x1b0/0x1b0 [ 546.117782] do_unblank_screen+0xaa/0x1b0 [ 546.117784] vt_ioctl+0x4e3/0x11e0 [ 546.117786] ? complete_change_console+0xe0/0xe0 [ 546.117788]
[Kernel-packages] [Bug 1828855] Re: Disco update: 5.0.9 upstream stable release
The following patches were skipped since they have already been applied: CVE-2019-9857: * inotify: Fix fsnotify_mark refcount leak in inotify_update_existing_watch() LP: #1828855: * net: hns3: Fix NULL deref when unloading driver * RDMA/hns: Fix the Oops during rmmod or insmod ko when reset occurs ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + 5.0.9 upstream stable release + from git://git.kernel.org/ -5.0.9 upstream stable release -from git://git.kernel.org/ + The following patches were applied: + * ARC: u-boot args: check that magic number is correct + * arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM + * inotify: Fix fsnotify_mark refcount leak in inotify_update_existing_watch() + * perf/core: Restore mmap record type correctly + * mips: bcm47xx: Enable USB power on Netgear WNDR3400v2 + * ext4: avoid panic during forced reboot + * ext4: add missing brelse() in add_new_gdb_meta_bg() + * ext4: report real fs size after failed resize + * ALSA: echoaudio: add a check for ioremap_nocache + * ALSA: sb8: add a check for request_region + * auxdisplay: hd44780: Fix memory leak on ->remove() + * drm/udl: use drm_gem_object_put_unlocked. + * IB/mlx4: Fix race condition between catas error reset and aliasguid flows + * i40iw: Avoid panic when handling the inetdev event + * mmc: davinci: remove extraneous __init annotation + * ALSA: opl3: fix mismatch between snd_opl3_drum_switch definition and declaration + * paride/pf: cleanup queues when detection fails + * paride/pcd: cleanup queues when detection fails + * thermal/intel_powerclamp: fix __percpu declaration of worker_data + * thermal: samsung: Fix incorrect check after code merge + * thermal: bcm2835: Fix crash in bcm2835_thermal_debugfs + * thermal/int340x_thermal: Add additional UUIDs + * thermal/int340x_thermal: fix mode setting + * thermal/intel_powerclamp: fix truncated kthread name + * scsi: iscsi: flush running unbind operations when removing a session + * sched/cpufreq: Fix 32-bit math overflow + * sched/core: Fix buffer overflow in cgroup2 property cpu.max + * x86/mm: Don't leak kernel addresses + * tools/power turbostat: return the exit status of a command + * scsi: core: Also call destroy_rcu_head() for passthrough requests + * scsi: qla2xxx: Fix NULL pointer crash due to stale CPUID + * perf stat: Fix --no-scale + * perf list: Don't forget to drop the reference to the allocated thread_map + * perf tools: Fix errors under optimization level '-Og' + * perf config: Fix an error in the config template documentation + * perf config: Fix a memory leak in collect_config() + * perf build-id: Fix memory leak in print_sdt_events() + * perf top: Fix error handling in cmd_top() + * perf hist: Add missing map__put() in error case + * perf map: Remove map from 'names' tree in __maps__remove() + * perf maps: Purge all maps from the 'names' tree + * perf top: Fix global-buffer-overflow issue + * perf evsel: Free evsel->counts in perf_evsel__exit() + * perf tests: Fix a memory leak of cpu_map object in the openat_syscall_event_on_all_cpus test + * perf tests: Fix memory leak by expr__find_other() in test__expr() + * perf tests: Fix a memory leak in test__perf_evsel__tp_sched_test() + * ACPI / utils: Drop reference in test for device presence + * PM / Domains: Avoid a potential deadlock + * blk-iolatency: #include "blk.h" + * drm/exynos/mixer: fix MIXER shadow registry synchronisation code + * irqchip/stm32: Don't clear rising/falling config registers at init + * irqchip/stm32: Don't set rising configuration registers at init + * irqchip/mbigen: Don't clear eventid when freeing an MSI + * x86/hpet: Prevent potential NULL pointer dereference + * x86/hyperv: Prevent potential NULL pointer dereference + * x86/cpu/cyrix: Use correct macros for Cyrix calls on Geode processors + * drm/nouveau/debugfs: Fix check of pm_runtime_get_sync failure + * iommu/vt-d: Check capability before disabling protected memory + * iommu/vt-d: Save the right domain ID used by hardware + * x86/hw_breakpoints: Make default case in hw_breakpoint_arch_parse() return
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
Hi, Joe. Do you think the revert is enough for now, or should we discuss about eventyually including the changes that you had mentioned on the comment #5 in the bug #1819689? -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
Exactly, Joseph. I'm attaching the exact patch I used for building the test kernel. ** Patch added: "0001-Revert-blk-mq-remove-the-request_list-usage.patch" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+attachment/5263471/+files/0001-Revert-blk-mq-remove-the-request_list-usage.patch -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations
I'm unable to reproduce this issue. Can you share your libvirt domain xml? And what version of netbeans are you using? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828632 Title: bionic i386 kernel crashes in memory pressure situations Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be made to crash in a kvm guest with memory pressure. The reproducer used is to attempt to run netbeans with openjdk-8-jre installed as the only jvm. It will fail to run, and when it fails, it also causes gnome-shell to crash. After 3 to 5 repeats of this, the kernel will crash with the following oops in dmesg: [ 545.926175] rfkill: input handler enabled [ 546.117550] [ cut here ] [ 546.117552] kernel BUG at /build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268! [ 546.117564] invalid opcode: [#1] SMP PTI [ 546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_e vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress r aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy drm pata_acpi i2c_piix4 [ 546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic #53-Ubuntu [ 546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 546.117618] EIP: vmalloc_fault+0x229/0x240 [ 546.117618] EFLAGS: 00010086 CPU: 0 [ 546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: [ 546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918 [ 546.117621] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0 [ 546.117624] Call Trace: [ 546.117637] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117638] __do_page_fault+0x39d/0x510 [ 546.117640] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117641] do_page_fault+0x27/0xf0 [ 546.117644] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117645] do_async_page_fault+0x55/0x90 [ 546.117655] common_exception+0x130/0x136 [ 546.117659] EIP: qxl_image_init+0x338/0x390 [qxl] [ 546.117659] EFLAGS: 00010286 CPU: 0 [ 546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030 [ 546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4 [ 546.117661] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117663] ? ioremap_nocache+0x12/0x20 [ 546.117665] qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl] [ 546.117668] qxl_primary_atomic_update+0x159/0x2c0 [qxl] [ 546.117680] drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper] [ 546.117684] drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper] [ 546.117688] commit_tail+0x5d/0x60 [drm_kms_helper] [ 546.117691] drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper] [ 546.117695] ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper] [ 546.117715] drm_atomic_commit+0x3f/0x50 [drm] [ 546.117719] restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper] [ 546.117723] restore_fbdev_mode+0x2c/0x150 [drm_kms_helper] [ 546.117725] ? _cond_resched+0x17/0x40 [ 546.117729] drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 [drm_kms_helper] [ 546.117732] drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper] [ 546.117743] fb_set_var+0x1a9/0x440 [ 546.117750] ? wakeup_preempt_entity+0x73/0x80 [ 546.117752] ? check_preempt_wakeup+0x108/0x230 [ 546.117753] ? check_cfs_rq_runtime+0x70/0x70 [ 546.117755] ? check_preempt_curr+0x27/0x80 [ 546.117757] ? ttwu_do_wakeup+0x17/0x190 [ 546.117760] fbcon_blank+0x29e/0x370 [ 546.117772] ? __switch_to_asm+0x27/0x4c [ 546.117774] ? fbcon_cursor+0x1b0/0x1b0 [ 546.117782] do_unblank_screen+0xaa/0x1b0 [ 546.117784] vt_ioctl+0x4e3/0x11e0 [ 546.117786] ? complete_change_console+0xe0/0xe0 [ 546.117788] tty_ioctl+0xec/0x910 [ 546.117793] ? jbd2_journal_stop+0xd7/0x3e0 [ 546.117797] ? ext4_free_inode+0x3c7/0x560 [ 546.117798] ? ext4_free_inode+0x1f2/0x560 [ 546.117812] ? intel_pmu_lbr_init_atom+0x46/0x50 [ 546.117819] ? call_rcu_sched+0x14/0x20 [ 546.117821] ? tty_vhangup+0x20/0x20 [
[Kernel-packages] [Bug 1828855] [NEW] Disco update: 5.0.9 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.9 upstream stable release from git://git.kernel.org/ The following patches were applied: * ARC: u-boot args: check that magic number is correct * arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM * inotify: Fix fsnotify_mark refcount leak in inotify_update_existing_watch() * perf/core: Restore mmap record type correctly * mips: bcm47xx: Enable USB power on Netgear WNDR3400v2 * ext4: avoid panic during forced reboot * ext4: add missing brelse() in add_new_gdb_meta_bg() * ext4: report real fs size after failed resize * ALSA: echoaudio: add a check for ioremap_nocache * ALSA: sb8: add a check for request_region * auxdisplay: hd44780: Fix memory leak on ->remove() * drm/udl: use drm_gem_object_put_unlocked. * IB/mlx4: Fix race condition between catas error reset and aliasguid flows * i40iw: Avoid panic when handling the inetdev event * mmc: davinci: remove extraneous __init annotation * ALSA: opl3: fix mismatch between snd_opl3_drum_switch definition and declaration * paride/pf: cleanup queues when detection fails * paride/pcd: cleanup queues when detection fails * thermal/intel_powerclamp: fix __percpu declaration of worker_data * thermal: samsung: Fix incorrect check after code merge * thermal: bcm2835: Fix crash in bcm2835_thermal_debugfs * thermal/int340x_thermal: Add additional UUIDs * thermal/int340x_thermal: fix mode setting * thermal/intel_powerclamp: fix truncated kthread name * scsi: iscsi: flush running unbind operations when removing a session * sched/cpufreq: Fix 32-bit math overflow * sched/core: Fix buffer overflow in cgroup2 property cpu.max * x86/mm: Don't leak kernel addresses * tools/power turbostat: return the exit status of a command * scsi: core: Also call destroy_rcu_head() for passthrough requests * scsi: qla2xxx: Fix NULL pointer crash due to stale CPUID * perf stat: Fix --no-scale * perf list: Don't forget to drop the reference to the allocated thread_map * perf tools: Fix errors under optimization level '-Og' * perf config: Fix an error in the config template documentation * perf config: Fix a memory leak in collect_config() * perf build-id: Fix memory leak in print_sdt_events() * perf top: Fix error handling in cmd_top() * perf hist: Add missing map__put() in error case * perf map: Remove map from 'names' tree in __maps__remove() * perf maps: Purge all maps from the 'names' tree * perf top: Fix global-buffer-overflow issue * perf evsel: Free evsel->counts in perf_evsel__exit() * perf tests: Fix a memory leak of cpu_map object in the openat_syscall_event_on_all_cpus test * perf tests: Fix memory leak by expr__find_other() in test__expr() * perf tests: Fix a memory leak in test__perf_evsel__tp_sched_test() * ACPI / utils: Drop reference in test for device presence * PM / Domains: Avoid a potential deadlock * blk-iolatency: #include "blk.h" * drm/exynos/mixer: fix MIXER shadow registry synchronisation code * irqchip/stm32: Don't clear rising/falling config registers at init * irqchip/stm32: Don't set rising configuration registers at init * irqchip/mbigen: Don't clear eventid when freeing an MSI * x86/hpet: Prevent potential NULL pointer dereference * x86/hyperv: Prevent potential NULL pointer dereference * x86/cpu/cyrix: Use correct macros for Cyrix calls on Geode processors * drm/nouveau/debugfs: Fix check of pm_runtime_get_sync failure * iommu/vt-d: Check capability before disabling protected memory * iommu/vt-d: Save the right domain ID used by hardware * x86/hw_breakpoints: Make default case in hw_breakpoint_arch_parse() return an error * cifs: fix that return -EINVAL when do dedupe operation * fix incorrect error code mapping for OBJECTID_NOT_FOUND * cifs: Fix slab-out-of-bounds when tracing SMB tcon * x86/gart: Exclude GART aperture from kcore * ext4: prohibit fstrim in norecovery mode * lkdtm: Print real addresses * lkdtm: Add tests for NULL pointer dereference * drm/amdgpu: psp_ring_destroy cause psp->km_ring.ring_mem NULL * drm/panel: panel-innolux: set display off in innolux_panel_unprepare * net: hns3: Fix NULL deref when unloading driver * crypto: axis - fix for recursive locking from bottom half * Revert "ACPI / EC: Remove old CLEAR_ON_RESUME quirk" * RDMA/hns: Fix the Oops during rmmod or insmod ko when reset occurs * coresight: cpu-debug: Support for CA73 CPUs * PCI: Blacklist power management of Gigabyte X299 DESIGNARE EX PCIe ports * PCI/ASPM: Save LTR Capability for suspend/resume * f2fs: sync filesystem after roll-forward recovery * drm/nouveau/volt/gf117: fix speedo readout register *
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
@Marcelo Cerri, just to confirm, the test kernel posted in comment #6 only had commit 7ac257b862f2c reverted? -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
@jhobbs
Here is the script that cleans up bcache devices on recommission:
https://pastebin.ubuntu.com/p/6WCGvM4Q32/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828415] Re: Disco update: 5.0.8 upstream stable release
SRU request sent to the mailing-list: https://lists.ubuntu.com/archives/kernel-team/2019-May/100679.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/1828415 Title: Disco update: 5.0.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.8 upstream stable release from git://git.kernel.org/ The following patches were applied: * drm/i915/gvt: do not let pin count of shadow mm go negative * kbuild: pkg: use -f $(srctree)/Makefile to recurse to top Makefile * netfilter: nft_compat: use .release_ops and remove list of extension * netfilter: nf_tables: use-after-free in dynamic operations * netfilter: nf_tables: add missing ->release_ops() in error path of newrule() * hv_netvsc: Fix unwanted wakeup after tx_disable * ibmvnic: Fix completion structure initialization * ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type * ipv6: Fix dangling pointer when ipv6 fragment * ipv6: sit: reset ip header pointer in ipip6_rcv * kcm: switch order of device registration to fix a crash * net: ethtool: not call vzalloc for zero sized memory request * net-gro: Fix GRO flush when receiving a GSO packet. * net/mlx5: Decrease default mr cache size * netns: provide pure entropy for net_hash_mix() * net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * net/sched: act_sample: fix divide by zero in the traffic path * net/sched: fix ->get helper of the matchall cls * qmi_wwan: add Olicard 600 * r8169: disable ASPM again * sctp: initialize _pad of sockaddr_in before copying to user memory * tcp: Ensure DCTCP reacts to losses * tcp: fix a potential NULL pointer dereference in tcp_sk_exit * vrf: check accept_source_route on the original netdevice * net/mlx5e: Fix error handling when refreshing TIRs * net/mlx5e: Add a lock on tir list * nfp: validate the return code from dev_queue_xmit() * nfp: disable netpoll on representors * bnxt_en: Improve RX consumer index validity check. * bnxt_en: Reset device on RX buffer errors. * net: ip_gre: fix possible use-after-free in erspan_rcv * net: ip6_gre: fix possible use-after-free in ip6erspan_rcv * net: bridge: always clear mcast matching struct on reports and leaves * net: thunderx: fix NULL pointer dereference in nicvf_open/nicvf_stop * net: vrf: Fix ping failed when vrf mtu is set to 0 * net: core: netif_receive_skb_list: unlist skb before passing to pt->func * r8169: disable default rx interrupt coalescing on RTL8168 * net: mlx5: Add a missing check on idr_find, free buf * net/mlx5e: Update xoff formula * net/mlx5e: Update xon formula * kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD * lib/string.c: implement a basic bcmp * Revert "clk: meson: clean-up clock registration" * tty: mark Siemens R3964 line discipline as BROKEN * tty: ldisc: add sysctl to prevent autoloading of ldiscs * hwmon: (w83773g) Select REGMAP_I2C to fix build error * hwmon: (occ) Fix power sensor indexing * SMB3: Allow persistent handle timeout to be configurable on mount * HID: logitech: Handle 0 scroll events for the m560 * ACPICA: Clear status of GPEs before enabling them * ACPICA: Namespace: remove address node from global list after method termination * ALSA: seq: Fix OOB-reads from strlcpy * ALSA: hda/realtek: Enable headset MIC of Acer TravelMate B114-21 with ALC233 * ALSA: hda/realtek - Add quirk for Tuxedo XC 1509 * ALSA: xen-front: Do not use stream buffer size before it is set * mm/huge_memory.c: fix modifying of page protection by insert_pfn_pmd() * arm64: dts: rockchip: fix rk3328 sdmmc0 write errors * mmc: alcor: don't write data before command has completed * mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning * parisc: Detect QEMU earlier in boot process * parisc: regs_return_value() should return gpr28 * parisc: also set iaoq_b in instruction_pointer_set() * alarmtimer: Return correct remaining time * drm/i915/gvt: do not deliver a workload if its creation fails * drm/sun4i: DW HDMI: Lower max. supported rate for H6 * drm/udl: add a release method and delay modeset teardown * kvm: svm: fix potential get_num_contig_pages overflow * include/linux/bitrev.h: fix constant bitrev * mm: writeback: use exact memcg dirty counts * ASoC: intel: Fix crash
[Kernel-packages] [Bug 1828166] Comment bridged from LTC Bugzilla
--- Comment From klaus.theur...@de.ibm.com 2019-05-13 11:48 EDT--- thanks, now I got the perf binary back. I still see Not enough memory for annotating '__irf_end' symbol! though -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828415] Re: Disco update: 5.0.8 upstream stable release
Compile tested on all supported architectures: amd64-binary: PASSED s390x-binary: PASSED ppc64el-binary: PASSED i386-binary:PASSED arm64-binary: PASSED armhf-binary: PASSED ** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828415 Title: Disco update: 5.0.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.8 upstream stable release from git://git.kernel.org/ The following patches were applied: * drm/i915/gvt: do not let pin count of shadow mm go negative * kbuild: pkg: use -f $(srctree)/Makefile to recurse to top Makefile * netfilter: nft_compat: use .release_ops and remove list of extension * netfilter: nf_tables: use-after-free in dynamic operations * netfilter: nf_tables: add missing ->release_ops() in error path of newrule() * hv_netvsc: Fix unwanted wakeup after tx_disable * ibmvnic: Fix completion structure initialization * ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type * ipv6: Fix dangling pointer when ipv6 fragment * ipv6: sit: reset ip header pointer in ipip6_rcv * kcm: switch order of device registration to fix a crash * net: ethtool: not call vzalloc for zero sized memory request * net-gro: Fix GRO flush when receiving a GSO packet. * net/mlx5: Decrease default mr cache size * netns: provide pure entropy for net_hash_mix() * net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * net/sched: act_sample: fix divide by zero in the traffic path * net/sched: fix ->get helper of the matchall cls * qmi_wwan: add Olicard 600 * r8169: disable ASPM again * sctp: initialize _pad of sockaddr_in before copying to user memory * tcp: Ensure DCTCP reacts to losses * tcp: fix a potential NULL pointer dereference in tcp_sk_exit * vrf: check accept_source_route on the original netdevice * net/mlx5e: Fix error handling when refreshing TIRs * net/mlx5e: Add a lock on tir list * nfp: validate the return code from dev_queue_xmit() * nfp: disable netpoll on representors * bnxt_en: Improve RX consumer index validity check. * bnxt_en: Reset device on RX buffer errors. * net: ip_gre: fix possible use-after-free in erspan_rcv * net: ip6_gre: fix possible use-after-free in ip6erspan_rcv * net: bridge: always clear mcast matching struct on reports and leaves * net: thunderx: fix NULL pointer dereference in nicvf_open/nicvf_stop * net: vrf: Fix ping failed when vrf mtu is set to 0 * net: core: netif_receive_skb_list: unlist skb before passing to pt->func * r8169: disable default rx interrupt coalescing on RTL8168 * net: mlx5: Add a missing check on idr_find, free buf * net/mlx5e: Update xoff formula * net/mlx5e: Update xon formula * kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD * lib/string.c: implement a basic bcmp * Revert "clk: meson: clean-up clock registration" * tty: mark Siemens R3964 line discipline as BROKEN * tty: ldisc: add sysctl to prevent autoloading of ldiscs * hwmon: (w83773g) Select REGMAP_I2C to fix build error * hwmon: (occ) Fix power sensor indexing * SMB3: Allow persistent handle timeout to be configurable on mount * HID: logitech: Handle 0 scroll events for the m560 * ACPICA: Clear status of GPEs before enabling them * ACPICA: Namespace: remove address node from global list after method termination * ALSA: seq: Fix OOB-reads from strlcpy * ALSA: hda/realtek: Enable headset MIC of Acer TravelMate B114-21 with ALC233 * ALSA: hda/realtek - Add quirk for Tuxedo XC 1509 * ALSA: xen-front: Do not use stream buffer size before it is set * mm/huge_memory.c: fix modifying of page protection by insert_pfn_pmd() * arm64: dts: rockchip: fix rk3328 sdmmc0 write errors * mmc: alcor: don't write data before command has completed * mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning * parisc: Detect QEMU earlier in boot process * parisc: regs_return_value() should return gpr28 * parisc: also set iaoq_b in instruction_pointer_set() * alarmtimer: Return correct remaining time * drm/i915/gvt: do not deliver a workload if its creation fails * drm/sun4i: DW HDMI: Lower max. supported rate for H6 * drm/udl: add a release method and delay modeset teardown * kvm: svm: fix potential
[Kernel-packages] [Bug 1828415] Re: Disco update: 5.0.8 upstream stable release
The following commits had to be added due to config changes: UBUNTU: [Packaging] remove n_r3964 from built modules list UBUNTU: [Config]: remove CONFIG_R3964 UBUNTU: [Config]: add CONFIG_LDISC_AUTOLOAD=y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828415 Title: Disco update: 5.0.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.8 upstream stable release from git://git.kernel.org/ The following patches were applied: * drm/i915/gvt: do not let pin count of shadow mm go negative * kbuild: pkg: use -f $(srctree)/Makefile to recurse to top Makefile * netfilter: nft_compat: use .release_ops and remove list of extension * netfilter: nf_tables: use-after-free in dynamic operations * netfilter: nf_tables: add missing ->release_ops() in error path of newrule() * hv_netvsc: Fix unwanted wakeup after tx_disable * ibmvnic: Fix completion structure initialization * ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type * ipv6: Fix dangling pointer when ipv6 fragment * ipv6: sit: reset ip header pointer in ipip6_rcv * kcm: switch order of device registration to fix a crash * net: ethtool: not call vzalloc for zero sized memory request * net-gro: Fix GRO flush when receiving a GSO packet. * net/mlx5: Decrease default mr cache size * netns: provide pure entropy for net_hash_mix() * net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * net/sched: act_sample: fix divide by zero in the traffic path * net/sched: fix ->get helper of the matchall cls * qmi_wwan: add Olicard 600 * r8169: disable ASPM again * sctp: initialize _pad of sockaddr_in before copying to user memory * tcp: Ensure DCTCP reacts to losses * tcp: fix a potential NULL pointer dereference in tcp_sk_exit * vrf: check accept_source_route on the original netdevice * net/mlx5e: Fix error handling when refreshing TIRs * net/mlx5e: Add a lock on tir list * nfp: validate the return code from dev_queue_xmit() * nfp: disable netpoll on representors * bnxt_en: Improve RX consumer index validity check. * bnxt_en: Reset device on RX buffer errors. * net: ip_gre: fix possible use-after-free in erspan_rcv * net: ip6_gre: fix possible use-after-free in ip6erspan_rcv * net: bridge: always clear mcast matching struct on reports and leaves * net: thunderx: fix NULL pointer dereference in nicvf_open/nicvf_stop * net: vrf: Fix ping failed when vrf mtu is set to 0 * net: core: netif_receive_skb_list: unlist skb before passing to pt->func * r8169: disable default rx interrupt coalescing on RTL8168 * net: mlx5: Add a missing check on idr_find, free buf * net/mlx5e: Update xoff formula * net/mlx5e: Update xon formula * kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD * lib/string.c: implement a basic bcmp * Revert "clk: meson: clean-up clock registration" * tty: mark Siemens R3964 line discipline as BROKEN * tty: ldisc: add sysctl to prevent autoloading of ldiscs * hwmon: (w83773g) Select REGMAP_I2C to fix build error * hwmon: (occ) Fix power sensor indexing * SMB3: Allow persistent handle timeout to be configurable on mount * HID: logitech: Handle 0 scroll events for the m560 * ACPICA: Clear status of GPEs before enabling them * ACPICA: Namespace: remove address node from global list after method termination * ALSA: seq: Fix OOB-reads from strlcpy * ALSA: hda/realtek: Enable headset MIC of Acer TravelMate B114-21 with ALC233 * ALSA: hda/realtek - Add quirk for Tuxedo XC 1509 * ALSA: xen-front: Do not use stream buffer size before it is set * mm/huge_memory.c: fix modifying of page protection by insert_pfn_pmd() * arm64: dts: rockchip: fix rk3328 sdmmc0 write errors * mmc: alcor: don't write data before command has completed * mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning * parisc: Detect QEMU earlier in boot process * parisc: regs_return_value() should return gpr28 * parisc: also set iaoq_b in instruction_pointer_set() * alarmtimer: Return correct remaining time * drm/i915/gvt: do not deliver a workload if its creation fails * drm/sun4i: DW HDMI: Lower max. supported rate for H6 * drm/udl: add a release method and delay modeset teardown * kvm: svm: fix potential get_num_contig_pages overflow *
[Kernel-packages] [Bug 1828420] Re: Xenial update: 4.4.179 upstream stable release
SRU request sent to the mailing-list: https://lists.ubuntu.com/archives/kernel-team/2019-May/100678.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/1828420 Title: Xenial update: 4.4.179 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.179 upstream stable release from git://git.kernel.org/ The following patches were applied: * arm64: debug: Don't propagate UNKNOWN FAR into si_code for debug signals * arm64: debug: Ensure debug handlers check triggering exception level * ext4: cleanup bh release code in ext4_ind_remove_space() * lib/int_sqrt: optimize initial value compute * tty/serial: atmel: Add is_half_duplex helper * mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified * i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA * Bluetooth: Fix decrementing reference count twice in releasing socket * tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped * CIFS: fix POSIX lock leak and invalid ptr deref * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * tracing: kdb: Fix ftdump to not sleep * gpio: gpio-omap: fix level interrupt idling * sysctl: handle overflow for file-max * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * fs/file.c: initialize init_files.resize_wait * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * cifs: Fix NULL pointer dereference of devname * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * usb: chipidea: Grab the (legacy) USB PHY by phandle first * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * coresight: etm4x: Add support to enable ETMv4.2 * ARM: 8840/1: use a raw_spinlock_t in unwind * mmc: omap: fix the maximum timeout setting * e1000e: Fix -Wformat-truncation warnings * IB/mlx4: Increase the timeout for CM cache * scsi: megaraid_sas: return error when create DMA pool failed * perf test: Fix failure of 'evsel-tp-sched' test on s390 * SoC: imx-sgtl5000: add missing put_device() * media: sh_veu: Correct return type for mem2mem buffer helpers * media: s5p-jpeg: Correct return type for mem2mem buffer helpers * media: s5p-g2d: Correct return type for mem2mem buffer helpers * media: mx2_emmaprp: Correct return type for mem2mem buffer helpers * leds: lp55xx: fix null deref on firmware load failure * kprobes: Prohibit probing on bsearch() * ARM: 8833/1: Ensure that NEON code always compiles with Clang * ALSA: PCM: check if ops are defined before suspending PCM * bcache: fix input overflow to cache set sysfs file io_error_halflife * bcache: fix input overflow to sequential_cutoff * bcache: improve sysfs_strtoul_clamp() * fbdev: fbmem: fix memory access if logo is bigger than the screen * cdrom: Fix race condition in cdrom_sysctl_register * ASoC: fsl-asoc-card: fix object reference leaks in fsl_asoc_card_probe * soc: qcom: gsbi: Fix error handling in gsbi_probe() * mt7601u: bump supported EEPROM version * ARM: avoid Cortex-A9 livelock on tight dmb loops * tty: increase the default flip buffer limit to 2*640K * media: mt9m111: set initial frame size other than 0x0 * hwrng: virtio - Avoid repeated init of completion * soc/tegra: fuse: Fix illegal free of IO base address * hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable * dmaengine: imx-dma: fix warning comparison of distinct pointer types * netfilter: physdev: relax br_netfilter dependency * media: s5p-jpeg: Check for fmt_ver_flag when doing fmt enumeration * regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting * wlcore: Fix memory leak in case wl12xx_fetch_firmware failure * x86/build: Mark per-CPU symbols as absolute explicitly for LLD * dmaengine: tegra: avoid overflow of byte tracking * drm/dp/mst: Configure no_stop_bit correctly for remote i2c xfers * binfmt_elf: switch to new creds
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Fix Committed -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
So looks like it is slow to sync with RTC.
ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/21 04:10:00"; sudo
strace -e ioctl "/sbin/hwclock"
ioctl(4, RTC_UIE_ON)= -1 EINVAL (Invalid argument)
ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10,
tm_year=104, ...}) = 0
ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10,
tm_year=104, ...}) = 0
when the hwclock command fails, the ioctl that fails is RTC_RD_TIME..
but running it with --verbose probably gives it just enough time to
complete the sync.
Or you could use the command as follows:
ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo
/sbin/hwclock --delay=0.5
2004-11-22 04:09:59.898618+00:00
ubuntu@tiselius:~$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel
[Kernel-packages] [Bug 1828712] Re: I/O errors when trying to loop mount an image
apport-cli contains an option for save the report from another machine. apport-cli --help says: --save=PATH In bug filing mode, save the collected information into a file instead of reporting it. This file can then be reported later on from a different machine. and: -c PATH, --crash-file=PATH Report the crash from given .apport or .crash file instead of the pending ones in /var/crash. (Implied if file is given as only argument.) However, this doesn't work with apport-collect but if the Ubuntu Kernel Bot still wants this you could open a new bug report using --save and the --crash-file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image Status in linux package in Ubuntu: Confirmed Bug description: Command sudo mount -t vfat flop1 /mnt/flop1 fails. The image is readable but the log shows many I/O errors such as May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read boot sector May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev loop0, sector 1 May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, logical block 1, async page read May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev loop0, sector 2 May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, logical block 2, async page read May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev loop0, sector 3 May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, logical block 3, async page read May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev loop0, sector 4 May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, logical block 4, async page read May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev loop0, sector 5 May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, logical block 5, async page read May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev loop0, sector 6 May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, logical block 6, async page read May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev loop0, sector 7 May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, logical block 7, async page read May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, logical block 1, async page read The command, understandably, reports "can't read superblock on /dev/loop0". The problem happens even on newly created images. Here's a sample set of commands and responses: $ mkfs.msdos -C flop1 1440 $ ls -l -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1 $ hd flop1 <--- output looks reasonable including 55 aa and two FATs ---> $ sudo mkdir /mnt/flop1 $ sudo mount -o loop flop1 /mnt/flop1 mount: /mnt/flop1: can't read superblock on /dev/loop0. $ losetup -f /dev/loop0 $ I see plenty of reports of similar on different websites but without resolution, including one on Launchpad but where the OP stopped responding so it did not get resolved. I don't know when this problem started to occur on this machine. If it's relevant, this is running under VirtualBox which reports itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host extensions' enabled. However, mounting a floppy image previously worked on this virtual machine. I have rebooted with /forcefsck to check the root (and only) filesystem. I have upgraded to the latest LTS Ubuntu, as below, but the problem persists. System info: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The machine is command-line only, i.e. no windowing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1828410] Re: Disco update: 5.0.7 upstream stable release
SRU request sent to the mailing-list: https://lists.ubuntu.com/archives/kernel-team/2019-May/100654.html ** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828410 Title: Disco update: 5.0.7 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.7 upstream stable release from git://git.kernel.org/ The following patches were applied: * ext4: cleanup bh release code in ext4_ind_remove_space() * CIFS: fix POSIX lock leak and invalid ptr deref * nvme-fc: fix numa_node when dev is null * nvme-loop: init nvmet_ctrl fatal_err_work when allocate * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * f2fs: fix to adapt small inline xattr space in __find_inline_xattr() * f2fs: fix to avoid deadlock in f2fs_read_inline_dir() * tracing: kdb: Fix ftdump to not sleep * net/mlx5e: Fix access to non-existing receive queue * net/mlx5: Avoid panic when setting vport rate * net/mlx5: Avoid panic when setting vport mac, getting vport config * xsk: fix to reject invalid flags in xsk_bind * clk: ti: clkctrl: Fix clkdm_name regression for TI_CLK_CLKCTRL_COMPAT * gpio: gpio-omap: fix level interrupt idling * include/linux/relay.h: fix percpu annotation in struct rchan * sysctl: handle overflow for file-max * net: stmmac: Avoid sometimes uninitialized Clang warnings * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * libbpf: force fixdep compilation at the start of the build * iio: adc: fix warning in Qualcomm PM8xxx HK/XOADC driver * x86/hyperv: Fix kernel panic when kexec on HyperV * perf c2c: Fix c2c report for empty numa node * mm/sparse: fix a bad comparison * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm, swap: bounds check swap_info array accesses to avoid NULL derefs * docs/core-api/mm: fix user memory accessors formatting * mm,oom: don't kill global init via memory.oom.group * memcg: killed threads should not invoke memcg OOM killer * mm, mempolicy: fix uninit memory access * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * f2fs: fix to data block override node segment by mistake * fs/file.c: initialize init_files.resize_wait * page_poison: play nicely with KASAN * kasan: fix kasan_check_read/write definitions * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * f2fs: fix to check inline_xattr_size boundary correctly * cifs: Accept validate negotiate if server return NT_STATUS_NOT_SUPPORTED * cifs: Fix NULL pointer dereference of devname * perf beauty msg_flags: Add missing %s lost when adding prefix suppression logic * netfilter: nf_tables: check the result of dereferencing base_chain->stats * PCI: mediatek: Fix memory mapped IO range size computation * netfilter: conntrack: tcp: only close if RST matches exact sequence * iommu/vt-d: Disable ATS support on untrusted devices * jbd2: fix invalid descriptor block checksum * ext4: fix bigalloc cluster freeing when hole punching under load * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * mm/resource: Return real error codes from walk failures * PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove() * wil6210: check null pointer in _wil_cfg80211_merge_extra_ies * mt76: fix a leaked reference by adding a missing of_node_put * ath10k: Fix the wrong updation of BW in tx_stats debugfs entry * lockdep/lib/tests: Fix run_tests.sh * crypto: crypto4xx - add missing of_node_put after of_device_is_available * crypto: cavium/zip - fix collision with generic cra_driver_name * tools/bpf: selftests: add map lookup to test_map_in_map bpf prog * usb: chipidea: Grab the (legacy) USB PHY by phandle first * powerpc/powernv/ioda: Fix locked_vm counting for memory used by IOMMU tables * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * kbuild: invoke syncconfig if include/config/auto.conf.cmd is missing * kbuild: make -r/-R effective in top Makefile for
[Kernel-packages] [Bug 1826345] Re: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Ready for Testing phase-changed: Monday, 13. May 2019 04:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826345 Title: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Ready for Testing phase-changed: Monday, 13. May 2019 04:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826345] Re: linux-ibm-gt: 4.15.0-1020.22 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1826345 Title: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Ready for Testing phase-changed: Monday, 13. May 2019 04:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828420] Re: Xenial update: 4.4.179 upstream stable release
Build tested on all supported architectures: amd64-binary: PASSED arm64-binary: PASSED armhf-binary: PASSED s390x-binary: PASSED ppc64el-binary: PASSED powerpc-binary: PASSED i386-binary:PASSED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828420 Title: Xenial update: 4.4.179 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.179 upstream stable release from git://git.kernel.org/ The following patches were applied: * arm64: debug: Don't propagate UNKNOWN FAR into si_code for debug signals * arm64: debug: Ensure debug handlers check triggering exception level * ext4: cleanup bh release code in ext4_ind_remove_space() * lib/int_sqrt: optimize initial value compute * tty/serial: atmel: Add is_half_duplex helper * mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified * i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA * Bluetooth: Fix decrementing reference count twice in releasing socket * tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped * CIFS: fix POSIX lock leak and invalid ptr deref * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * tracing: kdb: Fix ftdump to not sleep * gpio: gpio-omap: fix level interrupt idling * sysctl: handle overflow for file-max * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * fs/file.c: initialize init_files.resize_wait * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * cifs: Fix NULL pointer dereference of devname * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * usb: chipidea: Grab the (legacy) USB PHY by phandle first * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * coresight: etm4x: Add support to enable ETMv4.2 * ARM: 8840/1: use a raw_spinlock_t in unwind * mmc: omap: fix the maximum timeout setting * e1000e: Fix -Wformat-truncation warnings * IB/mlx4: Increase the timeout for CM cache * scsi: megaraid_sas: return error when create DMA pool failed * perf test: Fix failure of 'evsel-tp-sched' test on s390 * SoC: imx-sgtl5000: add missing put_device() * media: sh_veu: Correct return type for mem2mem buffer helpers * media: s5p-jpeg: Correct return type for mem2mem buffer helpers * media: s5p-g2d: Correct return type for mem2mem buffer helpers * media: mx2_emmaprp: Correct return type for mem2mem buffer helpers * leds: lp55xx: fix null deref on firmware load failure * kprobes: Prohibit probing on bsearch() * ARM: 8833/1: Ensure that NEON code always compiles with Clang * ALSA: PCM: check if ops are defined before suspending PCM * bcache: fix input overflow to cache set sysfs file io_error_halflife * bcache: fix input overflow to sequential_cutoff * bcache: improve sysfs_strtoul_clamp() * fbdev: fbmem: fix memory access if logo is bigger than the screen * cdrom: Fix race condition in cdrom_sysctl_register * ASoC: fsl-asoc-card: fix object reference leaks in fsl_asoc_card_probe * soc: qcom: gsbi: Fix error handling in gsbi_probe() * mt7601u: bump supported EEPROM version * ARM: avoid Cortex-A9 livelock on tight dmb loops * tty: increase the default flip buffer limit to 2*640K * media: mt9m111: set initial frame size other than 0x0 * hwrng: virtio - Avoid repeated init of completion * soc/tegra: fuse: Fix illegal free of IO base address * hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable * dmaengine: imx-dma: fix warning comparison of distinct pointer types * netfilter: physdev: relax br_netfilter dependency * media: s5p-jpeg: Check for fmt_ver_flag when doing fmt enumeration * regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting * wlcore: Fix memory leak in case wl12xx_fetch_firmware failure * x86/build: Mark per-CPU symbols as absolute explicitly for LLD * dmaengine: tegra: avoid overflow of byte tracking
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
If you use it in verbose mode it works. It could be that it is slow to
read from the rtc and the verbose mode just enough time to sync?
ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/10/25 04:10:00"; sudo
/sbin/hwclock --verbose
hwclock from util-linux 2.33.1
System Time: 1557759815.855012
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1098677400 seconds after 1969
Last calibration done at 1098677400 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
ioctl(4, RTC_UIE_ON, 0): Invalid argument
Waiting in loop for time from /dev/rtc0 to change
...got clock tick
Time read from Hardware Clock: 2004/10/25 04:10:01
Hw clock time : 2004/10/25 04:10:01 = 1098677401 seconds since 1969
Time since last adjustment is 1 second
Calculated Hardware Clock drift is 0.00 seconds
2004-10-25 04:09:59.806484+00:00
ubuntu@tiselius:~$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826145] Re: linux-kvm: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 - phase: Ready for Testing - phase-changed: Monday, 13. May 2019 05:07 UTC + phase: Holding before Release + phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1826145 Title: linux-kvm: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826145] Re: linux-kvm: 5.0.0-1005.5 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1826145 Title: linux-kvm: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Testing - phase-changed: Monday, 13. May 2019 05:10 UTC + phase: Holding before Release + phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Holding before Release phase-changed: Monday, 13. May 2019 15:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Refer -- https://askubuntu.com/questions/1128454/dell-xps-15-9570 -ath10k-qca6174-wifi-adapter-crashing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown
** Changed in: ubuntu-z-systems 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/1828394 Title: [UBUNTU] qdio: clear intparm during shutdown Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] * Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space" [Fix] * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear intparm during shutdown" [Test Case] * Offline an OSA CHPID with multiple active qeth interfaces. [Regression Potential] * The regression potential can be considered as very low since it only affects the s390x platform * and there it only affects the (ccW) qeth (OSA) network devices * and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation. [Other Info] * The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work. * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE. _ Description: qdio: clear intparm during shutdown Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space". Problem: During shutdown, qdio returns its ccw device back to control by qeth - but doesn't reset the interrupt parameter on the device. If qdio_shutdown() failed to terminate its long-running IO on the ccw_device, qeth will subsequently do so. In this case the IRQ for the IO completion is presented to qeth_irq() with the _old_ interrupt parameter, which gets mis-interpreted as a valid qeth_cmd_buffer pointer. Dereferencing this bogus pointer in qeth_release_buffer() triggers the crash. Solution: When returning the ccw device in qdio_shutdown(), also reset its interrupt parameter. Reproduction: Offline an OSA CHPID with multiple active qeth interfaces. Component: Kernel Upstream-ID: 89286320a236d245834075fa13adb0bdd827ecaa Reported: Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828420] Re: Xenial update: 4.4.179 upstream stable release
The following commits had to be added due to changes on the config options: UBUNTU: [Packaging] remove n_r3964 from built modules list UBUNTU: [Config]: remove CONFIG_R3964 UBUNTU: [Config]: add CONFIG_LDISC_AUTOLOAD=y UBUNTU: [Config]: remove CONFIG_SAMSUNG_PM_CHECK ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828420 Title: Xenial update: 4.4.179 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.179 upstream stable release from git://git.kernel.org/ The following patches were applied: * arm64: debug: Don't propagate UNKNOWN FAR into si_code for debug signals * arm64: debug: Ensure debug handlers check triggering exception level * ext4: cleanup bh release code in ext4_ind_remove_space() * lib/int_sqrt: optimize initial value compute * tty/serial: atmel: Add is_half_duplex helper * mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified * i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA * Bluetooth: Fix decrementing reference count twice in releasing socket * tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped * CIFS: fix POSIX lock leak and invalid ptr deref * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux- * tracing: kdb: Fix ftdump to not sleep * gpio: gpio-omap: fix level interrupt idling * sysctl: handle overflow for file-max * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK * mm/cma.c: cma_declare_contiguous: correct err handling * mm/page_ext.c: fix an imbalance with kmemleak * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512! * mm/slab.c: kmemleak no scan alien caches * ocfs2: fix a panic problem caused by o2cb_ctl * f2fs: do not use mutex lock in atomic context * fs/file.c: initialize init_files.resize_wait * cifs: use correct format characters * dm thin: add sanity checks to thin-pool and external snapshot creation * cifs: Fix NULL pointer dereference of devname * fs: fix guard_bio_eod to check for real EOD errors * tools lib traceevent: Fix buffer overflow in arg_eval * usb: chipidea: Grab the (legacy) USB PHY by phandle first * scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c * coresight: etm4x: Add support to enable ETMv4.2 * ARM: 8840/1: use a raw_spinlock_t in unwind * mmc: omap: fix the maximum timeout setting * e1000e: Fix -Wformat-truncation warnings * IB/mlx4: Increase the timeout for CM cache * scsi: megaraid_sas: return error when create DMA pool failed * perf test: Fix failure of 'evsel-tp-sched' test on s390 * SoC: imx-sgtl5000: add missing put_device() * media: sh_veu: Correct return type for mem2mem buffer helpers * media: s5p-jpeg: Correct return type for mem2mem buffer helpers * media: s5p-g2d: Correct return type for mem2mem buffer helpers * media: mx2_emmaprp: Correct return type for mem2mem buffer helpers * leds: lp55xx: fix null deref on firmware load failure * kprobes: Prohibit probing on bsearch() * ARM: 8833/1: Ensure that NEON code always compiles with Clang * ALSA: PCM: check if ops are defined before suspending PCM * bcache: fix input overflow to cache set sysfs file io_error_halflife * bcache: fix input overflow to sequential_cutoff * bcache: improve sysfs_strtoul_clamp() * fbdev: fbmem: fix memory access if logo is bigger than the screen * cdrom: Fix race condition in cdrom_sysctl_register * ASoC: fsl-asoc-card: fix object reference leaks in fsl_asoc_card_probe * soc: qcom: gsbi: Fix error handling in gsbi_probe() * mt7601u: bump supported EEPROM version * ARM: avoid Cortex-A9 livelock on tight dmb loops * tty: increase the default flip buffer limit to 2*640K * media: mt9m111: set initial frame size other than 0x0 * hwrng: virtio - Avoid repeated init of completion * soc/tegra: fuse: Fix illegal free of IO base address * hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable * dmaengine: imx-dma: fix warning comparison of distinct pointer types * netfilter: physdev: relax br_netfilter dependency * media: s5p-jpeg: Check for fmt_ver_flag when doing fmt enumeration * regulator: act8865: Fix act8600_sudcdc_voltage_ranges setting * wlcore: Fix memory leak in case
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Next step is for the kernel team to assess whether this is a test case
issue, or a real kernel bug.
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Status: New => 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/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el
** Tags added: reverse-proxy-bugzilla -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827162 Title: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el
** Changed in: ubuntu-power-systems Assignee: (unassigned) => bugproxy (bugproxy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827162 Title: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827162 Title: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el
** Changed in: ubuntu-power-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827162 Title: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
** 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/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The integrity subsystem is still reporting error messages like this at boot: integrity: Unable to open file: /etc/keys/x509_evm.der (-2) In a previous commit we have downgraded this error to warning: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- next=58441dc86d7b066a2c02079829a96035587a7066 (this fix is applied everywhere, not only in bionic) But there's another place (security/integrity/digsig.c) that reports the same error message that should be also downgraded to warning for consistency. [Test Case] No special test case is required, errors are reported at boot if an integrity policy is enabled. [Fix] Downgrade also this error message to a warning. [Regression Potential] It is a one-liner that changes a printk() error message, regression potential is minimal. [Original bug report] == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @
[Kernel-packages] [Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm
** Summary changed: - net test in ubuntu_kernel_selftest failed on linux-kvm 4.4 + net test in ubuntu_kernel_selftest failed on linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760087 Title: net test in ubuntu_kernel_selftest failed on linux-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Steps: 1. Deploy a KVM node with Xenial, install linux-kvm on it. 2. git clone --depth 1 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux 3. Run the "net" sub set in the kernel_selftest Result: * test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory * test_bpf: [FAIL] * selftests: test_bpf.sh [FAIL] Output: $ sudo make -C linux/tools/testing/selftests/net all run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Nothing to be done for 'all'. running socket test [PASS] selftests: run_netsocktests [PASS] running psock_fanout test test: control single socket test: control multiple sockets test: datapath 0x0 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,5, expect=20,5 test: datapath 0x1000 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x1 info: count=0,0, expect=0,0 info: count=10,10, expect=10,10 info: count=18,17, expect=18,17 test: datapath 0x3 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x6 info: count=0,0, expect=0,0 info: count=5,15, expect=15,5 info: count=20,15, expect=15,20 test: datapath 0x7 bpf: Function not implemented bpf verifier: ���ߟ [FAIL] running psock_tpacket test test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory [FAIL] selftests: run_afpackettests [PASS] test_bpf: [FAIL] selftests: test_bpf.sh [FAIL] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 12:12:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826416] Re: [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy"
** Description changed: + [Impact] + A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux- azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. + + [Test Case] + + When the issue happens, there is no error message in dmesg or syslog, + and it's just the host side NetVSP driver stops reading from the guest- + to-host ring, and the guest network stops working. So we don't really + have any logs to provide here. + + [Regression Potential] + + Low risk since that's a simple patch from stable upstream touching only + Hyper-V specific code. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826416 Title: [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Bug description: [Impact] A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux-azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. [Test Case] When the issue happens, there is no error message in dmesg or syslog, and it's just the host side NetVSP driver stops reading from the guest-to-host ring, and the guest network stops working. So we don't really have any logs to provide here. [Regression Potential] Low risk since that's a simple patch from stable upstream touching only Hyper-V specific code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827555] Re: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14)
A mistake was made in the previous patch. A new patch was sent to the kernel-team mailing list on May 10. I have attached its contents. ** Patch added: "system76_gaze14_fix.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+attachment/5263451/+files/system76_gaze14_fix.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/1827555 Title: [ALSA] [PATCH] Headset fixup for System76 Gazelle (gaze14) Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux-hwe source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-hwe source package in Disco: Invalid Bug description: [Impact] * On the System76 Gazelle (gaze14), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is identical to the patch already applied for the System76 Darter Pro (darp5). [Test Case] * With the affected hardware, attempt to use a headset with a microphone input. There will be no microphone input from the headset until applying this patch. [Regression Potential] * Extremely low, it specifically identifies the affected hardware. [Other Info] * I have attached the patch as it will be applied to upstream Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827755] Re: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request
Next steps: IBM to verify if this issue is already resolved in 19.04, and report back to 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/1827755 Title: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Normally nx-compress and nx-842-powernv modules are loaded when selects 842-nx compressor if not loaded and execute forever during system execution. So we will not see this bug in normal case. But we are seeing NX CRB request timeout when uninstall these modules and load them or select 842-nx compressor. ---uname output--- 18.04 Machine Type = P9 system ---Steps to Reproduce--- - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Patches are included in 4.19-rc1 6e708000ec2c93c2bde6a46aa2d6c3e80d4eaeb9 - powerpc/powernv: Export opal_check_token symbol 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 - crypto/nx: Initialize 842 high and normal RxFIFO control registers > Looks like the first commit was included in a recent 18.04 update > (4.15.0-48.51), see > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819989 > > but I don't see the second one there yet. > > If this is still needed, I would suggest getting this bug mirrored to LP to > put on Canonical's radar. We need second commit (656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca) to fix this actual issue. But no use of having the first commit without second one. The first one just exports opal_check_token symbol which is used in the second commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided => High
** Changed in: kexec-tools (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1828187
Title:
ibm,dynamic-memory property not found while loading kexec kernel
(4.18.0-18-generic)
Status in The Ubuntu-power-systems project:
Triaged
Status in kexec-tools package in Ubuntu:
New
Bug description:
== Comment: #0 - Hari Krishna Bathini - 2019-05-07
13:37:51 ==
---Problem Description---
On 4.18.0-18-generic kernel, kexec load command throws below traces:
---
Regular kexec load:
root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
root@ubuntu:~#
---
KDump kernel load:
root@ubuntu:~# kdump-config unload
* unloaded kdump kernel
root@ubuntu:~# kdump-config load
* Creating symlink /var/lib/kdump/vmlinuz
* Creating symlink /var/lib/kdump/initrd.img
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1
systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb
elfcorehdr=158912K
* loaded kdump kernel
root@ubuntu:~#
---
Contact Information = hbath...@in.ibm.com
---uname output---
Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC
2019 ppc64le ppc64le ppc64le GNU/Linux
---Additional Hardware Info---
na
Machine Type = na
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Load panic kernel or regular kernel with kexec command:
kdump-config unload; kdump-config load
OR
kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
Actual Result:
DT files are not found while loading the kernel
Expected result:
kexec loads without any warning/error messages
Userspace tool common name: kexec-tools
The userspace tool has the following bit modes: 64-bit
Userspace rpm: kexec-tools
Userspace tool obtained from project website: na
*Additional Instructions for hbath...@in.ibm.com:
-Attach ltrace and strace of userspace application.
== Comment: #1 - Hari Krishna Bathini -
2019-05-07 13:44:25 ==
Since v4.16 kernel, ibm,dynamic-memory-v2 Device Tree Property is supported
in the kernel. This leaves kexec-tools on ppc64le broken without the below
fix patches:
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=c740fdb2048265551f77d3f0fe53b2fddc0c8489
("kexec: add a helper function to add ranges")
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=b10924a7da3ca48c04982cd23daf04882afb1a87
("kexec/ppc64: add support to parse ibm, dynamic-memory-v2 property")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Tags added: powervm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Triaged Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
The test kernel is reaching 52K IOPS as expected. -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Triaged Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828394 Title: [UBUNTU] qdio: clear intparm during shutdown Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] * Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space" [Fix] * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear intparm during shutdown" [Test Case] * Offline an OSA CHPID with multiple active qeth interfaces. [Regression Potential] * The regression potential can be considered as very low since it only affects the s390x platform * and there it only affects the (ccW) qeth (OSA) network devices * and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation. [Other Info] * The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work. * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE. _ Description: qdio: clear intparm during shutdown Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space". Problem: During shutdown, qdio returns its ccw device back to control by qeth - but doesn't reset the interrupt parameter on the device. If qdio_shutdown() failed to terminate its long-running IO on the ccw_device, qeth will subsequently do so. In this case the IRQ for the IO completion is presented to qeth_irq() with the _old_ interrupt parameter, which gets mis-interpreted as a valid qeth_cmd_buffer pointer. Dereferencing this bogus pointer in qeth_release_buffer() triggers the crash. Solution: When returning the ccw device in qdio_shutdown(), also reset its interrupt parameter. Reproduction: Offline an OSA CHPID with multiple active qeth interfaces. Component: Kernel Upstream-ID: 89286320a236d245834075fa13adb0bdd827ecaa Reported: Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828394 Title: [UBUNTU] qdio: clear intparm during shutdown Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: [Impact] * Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space" [Fix] * 89286320a236d245834075fa13adb0bdd827ecaa 8928632 "s390/qdio: clear intparm during shutdown" [Test Case] * Offline an OSA CHPID with multiple active qeth interfaces. [Regression Potential] * The regression potential can be considered as very low since it only affects the s390x platform * and there it only affects the (ccW) qeth (OSA) network devices * and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation. [Other Info] * The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work. * It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE. _ Description: qdio: clear intparm during shutdown Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space". Problem: During shutdown, qdio returns its ccw device back to control by qeth - but doesn't reset the interrupt parameter on the device. If qdio_shutdown() failed to terminate its long-running IO on the ccw_device, qeth will subsequently do so. In this case the IRQ for the IO completion is presented to qeth_irq() with the _old_ interrupt parameter, which gets mis-interpreted as a valid qeth_cmd_buffer pointer. Dereferencing this bogus pointer in qeth_release_buffer() triggers the crash. Solution: When returning the ccw device in qdio_shutdown(), also reset its interrupt parameter. Reproduction: Offline an OSA CHPID with multiple active qeth interfaces. Component: Kernel Upstream-ID: 89286320a236d245834075fa13adb0bdd827ecaa Reported: Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Ready for Testing phase-changed: Thursday, 09. May 2019 09:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Ready for Testing phase-changed: Thursday, 09. May 2019 09:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Ready for Testing phase-changed: Thursday, 09. May 2019 09:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 - phase: Ready for Testing - phase-changed: Thursday, 09. May 2019 09:11 UTC + phase: Holding before Release + phase-changed: Monday, 13. May 2019 13:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826350 Title: linux-fips: 4.15.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Holding before Release phase-changed: Monday, 13. May 2019 13:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826350 Title: linux-fips: 4.15.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Holding before Release phase-changed: Monday, 13. May 2019 13:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: udisks2 (Ubuntu Eoan) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: New Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: New Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: New Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
@Kai-Heng is there a patched kernel package I can test with? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9
** Tags removed: bugnameltc-177392 ** Tags added: bugnameltc-177393 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827335 Title: Unable to put offline CPU back online on Bionic/B-hwe-edge P9 Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: You will see these CPUs in offline state after boot. ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline 156-159 ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online 1 tee: /sys/devices/system/cpu/cpu156/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online 1 tee: /sys/devices/system/cpu/cpu157/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online 1 tee: /sys/devices/system/cpu/cpu158/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online 1 tee: /sys/devices/system/cpu/cpu159/online: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1 ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-14-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 2 06:46:36 2019 ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 18:55:27 UTC 2019 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 79) max: 2.945 GHz (cpu 81) avg: 2.903 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
