[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
** Tags removed: verification-needed verification-needed-artful ** Tags added: architecture-ppc64le bugnameltc-165886 severity-medium targetmilestone-inin--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: Fix Committed Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757347] [NEW] sigio test in stress_smoke_test will take about 7 hours to run
Public bug reported: I'm not sure if this is an expected behaviour. The test itself took about 7 hours to complete on an ARM64 node with X-edge kernel (4.15.0-13-generic) Mar 21 06:22:49 ms10-35-mcdivittB0-kernel stress-ng: info: [19616] successful run completed in 24297.89s (6 hours, 44 mins, 57.89 secs) This is not very ideal for a system that will be tested against different kernels. syslog for this test could be found here: https://pastebin.ubuntu.com/p/T9dsgwr8kg/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14~16.04.1 ProcVersionSignature: User Name 4.15.0-13.14~16.04.1-generic 4.15.10 Uname: Linux 4.15.0-13-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: arm64 Date: Wed Mar 21 06:22:52 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 package-from-proposed uec-images xenial ** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757347 Title: sigio test in stress_smoke_test will take about 7 hours to run Status in linux package in Ubuntu: New Bug description: I'm not sure if this is an expected behaviour. The test itself took about 7 hours to complete on an ARM64 node with X-edge kernel (4.15.0-13-generic) Mar 21 06:22:49 ms10-35-mcdivittB0-kernel stress-ng: info: [19616] successful run completed in 24297.89s (6 hours, 44 mins, 57.89 secs) This is not very ideal for a system that will be tested against different kernels. syslog for this test could be found here: https://pastebin.ubuntu.com/p/T9dsgwr8kg/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14~16.04.1 ProcVersionSignature: User Name 4.15.0-13.14~16.04.1-generic 4.15.10 Uname: Linux 4.15.0-13-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: arm64 Date: Wed Mar 21 06:22:52 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)
To make the GPIO support in 18.04, please set the config CONFIG_PINCTRL_GEMINILAKE=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/1751714 Title: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed) Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: a commit id missed in LP#1685729. [CNL] - New device IDs for CNL v4.16 cb5fda413e1d @Canonical, please take it into 18.04. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1751714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS
People, please, help with feedback. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747572 Title: CIFS SMB2/SMB3 does not work for domain based DFS Status in cifs-utils: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755208] Re: linux: 4.4.0-117.141 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755208 Title: linux: 4.4.0-117.141 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755209 (linux-lts-xenial), bug 1755210 (linux-aws) derivatives: bug 1755212 (linux-euclid), bug 1755213 (linux-raspi2), bug 1755215 (linux-snapdragon), bug 1755216 (linux-gke), bug 1755217 (linux-aws), bug 1755219 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS
TEST FAIL in artful with that kernel: linux-image-generic: Installed: 4.13.0.38.41 Candidate: 4.13.0.38.41 Version table: *** 4.13.0.38.41 500 500 http://ru.archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status Looks like kernel not patched at all. Is there any mistake? Why kernel in artful lesser than in xenial? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747572 Title: CIFS SMB2/SMB3 does not work for domain based DFS Status in cifs-utils: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757347] [NEW] sigio test in stress_smoke_test will take about 7 hours to run
You have been subscribed to a public bug: I'm not sure if this is an expected behaviour. The test itself took about 7 hours to complete on an ARM64 node with X-edge kernel (4.15.0-13-generic) Mar 21 06:22:49 ms10-35-mcdivittB0-kernel stress-ng: info: [19616] successful run completed in 24297.89s (6 hours, 44 mins, 57.89 secs) This is not very ideal for a system that will be tested against different kernels. syslog for this test could be found here: https://pastebin.ubuntu.com/p/T9dsgwr8kg/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14~16.04.1 ProcVersionSignature: User Name 4.15.0-13.14~16.04.1-generic 4.15.10 Uname: Linux 4.15.0-13-generic aarch64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: arm64 Date: Wed Mar 21 06:22:52 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 package-from-proposed uec-images xenial -- sigio test in stress_smoke_test will take about 7 hours to run https://bugs.launchpad.net/bugs/1757347 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
The behavior appears to be much better with the kernel version 4.16-rc6. However, I think this is not 100% solved, as the following error is still (but now rarely) happening when disconnecting from a network: [ 5934.740004] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 [ 5934.740010] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) With that MAC address being from the router. I believe this error, when happening on shutdown or reboot, is the source of the problem, as when that messages are not shown (apparently) the error doesn't happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Incomplete Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J4067
[Kernel-packages] [Bug 1732370] Re: arm64 system failed with test 079 in zfs_xfs_generic
** Summary changed: - ThunderX arm64 system failed with test 079 in zfs_xfs_generic + arm64 system failed with test 079 in zfs_xfs_generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1732370 Title: arm64 system failed with test 079 in zfs_xfs_generic Status in linux package in Ubuntu: Confirmed Bug description: This system constantly fails with the generic test 079 in ubuntu_zfs_xfs_generic test suite, even with the latest code from upstream. 07:59:46 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_zfs_xfs_generic.079', 'ubuntu_zfs_xfs_generic.079') 07:59:46 DEBUG| Waiting for pid 12399 for 3600 seconds 07:59:47 INFO | Running: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src 07:59:51 DEBUG| [stdout] 08:00:01 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.py", line 98, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_ generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src Exit status: 1 Duration: 13.813601017 stdout: Creating zfs pool testpool.. Creating zfs file systems test and scratch in testpool.. VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src FSTYP -- zfs PLATFORM -- Linux/aarch64 wright-kernel 4.10.0-38-generic MKFS_OPTIONS -- testpool/scratch MOUNT_OPTIONS -- testpool/scratch /mnt/scratch generic/079- output mismatch (see /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad) --- tests/generic/079.out 2017-11-15 07:40:51.054794973 + +++ /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad 2017-11-15 07:59:52.910100549 + @@ -1,7 +1,6 @@ QA output created by 079 *** starting up -testing immutable...PASS. -testing append-only...PASS. -testing immutable as non-root...PASS. -testing append-only as non-root...PASS. +acl: Function not implemented ... (Run 'diff -u tests/generic/079.out /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad' to see the entire diff) Ran: generic/079 Failures: generic/079 Failed 1 of 1 tests Destroying zfs pool testpool Removing VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42 ProcVersionSignature: User Name 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic aarch64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 15 03:29 seq crw-rw 1 root audio 116, 33 Nov 15 03:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Nov 15 06:27:54 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro RelatedPackageVersions: linux-restricted-modules-4.10.0-38-generic N/A linux-backports-modules-4.10.0-38-generic N/A linux-firmware 1.164.1 Rf
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
Possible duplicate: arm64 system failed with test 079 in zfs_xfs_generic bug 1732370 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: Fix Committed Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680349] Comment bridged from LTC Bugzilla
(In reply to comment #70) > Default Comment by Bridge > > Default Comment by Bridge > > Default Comment by Bridge > > Default Comment by Bridge > > Following comment #31, could you confirm that this is resolved with the 4.15 > kernel in Bionic? Issue is observed even on 18.04 [ 4.15.0-12-generic ]. Attaching logs. Thanks, Pavithra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680349 Title: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 == ---Problem Description--- Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Machine hangs. ---Steps to Reproduce--- 1. Configure kdump. 2. Install stress-ng # apt-get install stress-ng 3. Run stress-ng # stress-ng - a 0 Logs: root@ltc-firep3:~# kdump-config load Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K * loaded kdump kernel root@ltc-firep3:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.10.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-firep3:~# stress-ng -a 0 stress-ng: info: [3900] defaulting to a 86400 second run per stressor stress-ng: info: [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie stress-ng: info: [3900] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [3900] cache allocate: default cache size: 2048K stress-ng: info: [3907] stress-ng-atomic: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [3955] stress-ng-exec: running as root, won't run test. stress-ng: info: [3999] stress-ng-icache: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4040] stress-ng-lockbus: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4313] stress-ng-numa: system has 2 of a maximum 256 memory NUMA nodes stress-ng: info: [4455] stress-ng-rdrand: this stress
[Kernel-packages] [Bug 1680349] 18.04 console log
Default Comment by Bridge ** Attachment added: "18.04 console log" https://bugs.launchpad.net/bugs/1680349/+attachment/5085568/+files/Bug_firestone_stressng.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/1680349 Title: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 == ---Problem Description--- Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng. Machine hangs. ---Steps to Reproduce--- 1. Configure kdump. 2. Install stress-ng # apt-get install stress-ng 3. Run stress-ng # stress-ng - a 0 Logs: root@ltc-firep3:~# kdump-config load Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K * loaded kdump kernel root@ltc-firep3:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.10.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltc-firep3:~# stress-ng -a 0 stress-ng: info: [3900] defaulting to a 86400 second run per stressor stress-ng: info: [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie stress-ng: info: [3900] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [3900] cache allocate: default cache size: 2048K stress-ng: info: [3907] stress-ng-atomic: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [3955] stress-ng-exec: running as root, won't run test. stress-ng: info: [3999] stress-ng-icache: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4040] stress-ng-lockbus: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: info: [4313] stress-ng-numa: system has 2 of a maximum 256 memory NUMA nodes stress-ng: info: [4455] stress-ng-rdrand: this stressor is not implemented on this system: ppc64le Linux 4.10.0-11-generic stress-ng: fail: [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 (Invalid argument)
[Kernel-packages] [Bug 1742684] Re: Display res
[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/1742684 Title: Display res Status in linux package in Ubuntu: Expired Bug description: GPU GeForce 6150SE nForce 430 using Nvidia 304.135 wont go above 1024 display resolution. Normally 1920 after upgrading to kernel 4.13.0-26.29 Mint 18.3 Sylvia --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acer 1237 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=15e46a87-7fe7-420a-ad37-812be19f62c2 InstallationDate: Installed on 2017-12-12 (29 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 IwConfig: enp0s7no wireless extensions. enp3s0no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7309 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=bcb6f656-ad31-4a57-9f51-138eb65690f6 ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 RfKill: Tags: sylvia sylvia Uname: Linux 4.13.0-26-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V9.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7309 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV9.9:bd12/23/2009:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7309 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: In Progress Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter
[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/1743872 Title: "0BDA:A811" - Not work 802.11ac WLAN Adapter Status in linux package in Ubuntu: Expired Bug description: Hello, Not work: https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-30-generic 4.13.0-30.33 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1752 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:08:45 2018 InstallationDate: Installed on 2017-10-13 (96 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-30-generic N/A linux-backports-modules-4.13.0-30-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743946] Re: kexec reboot = NMI: PCI system error (SERR) for reason a1 on CPU 0
[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/1743946 Title: kexec reboot = NMI: PCI system error (SERR) for reason a1 on CPU 0 Status in linux package in Ubuntu: Expired Bug description: On 16.04 with linux-image-lowlatency-hwe-16.04 amd64 (currently 4.13.0-30-lowlatency) with kexec-tools default-configured to handle reboots with the current kernel version (no GRUB detect) and /proc/cmdline. The system freezes either permanently (requiring a hard power-off) or for tens of seconds, showing (copied from a photograph): kexec_core: Starting new kernel nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon NMI: PCI system error (SERR) for reason a1 on CPU 0. Dazed and confused, but trying to continue Due to the nature of the failure there is no additional logging or clues. I tried "nopti" in case recent 'Meltdown' changes were responsible but it still happens. I've only just enabled kexec on this system so have no historical indications of it having worked. System is Dell XPS M1530, Core 2 Duo T9300, 4GB RAM --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 JournalErrors: -- Logs begin at Wed 2018-01-10 04:01:51 UTC, end at Thu 2018-01-18 13:41:03 UTC. -- Jan 18 07:08:41 hostname dnsmasq[868]: warning: no upstream servers configured MachineType: Dell Inc. XPS M1530 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-30-lowlatency root=UUID=2edb423c-3c9d-4031-a18a-99f112ad48c1 ro nopti acpi_osi=! "acpi_osi=Windows 2006" pci=assign-busses,pcie_scan_all,realloc crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-30.33~16.04.1-lowlatency 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-30-lowlatency N/A linux-backports-modules-4.13.0-30-lowlatency N/A linux-firmware1.157.15 Tags: xenial Uname: Linux 4.13.0-30-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm disk plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
ok, i'm going to go with bionic's kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0 Oct 31 07:08:37 spiny kernel: usb 1-1.2: Product: USB Multime
[Kernel-packages] [Bug 1755208] Re: linux: 4.4.0-117.141 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755208 Title: linux: 4.4.0-117.141 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755209 (linux-lts-xenial), bug 1755210 (linux-aws) derivatives: bug 1755212 (linux-euclid), bug 1755213 (linux-raspi2), bug 1755215 (linux-snapdragon), bug 1755216 (linux-gke), bug 1755217 (linux-aws), bug 1755219 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755227 Title: linux: 3.13.0-144.193 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752672] Comment bridged from LTC Bugzilla
--- Comment From ukri...@us.ibm.com 2018-03-20 22:19 EDT--- Sorry about the trouble...Here are the missing patches from 4.16 that are needed before applying the 38 patches. 96cf727fe8f102bf92150b741db71ee39fb8c521 scsi: cxlflash: Reset command ioasc b070545db112e4c815fbfce25449495eff20c170 scsi: cxlflash: Update cxl-specific arguments to generic cookie af2047ec00bfd61b46b653e856dcf1e0bc567619 scsi: cxlflash: Explicitly cache number of interrupts per context 8762353106c4376deabd76473e1bd7ba36dd529c scsi: cxlflash: Remove embedded CXL work structures 0df69c6024cd089144d3b38f12352899dd4e40b1 scsi: cxlflash: Adapter context init can return error 25b8e08e83b5bc58967aae566730548f407c0439 scsi: cxlflash: Staging to support future accelerators Please let me know if you still have problems with these patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752672 Title: CAPI Flash (cxlflash) update Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This is a feature for capi flash (cxlflash) inside the kernel. We have upstreamed the below 38 patches but they are not in the maintainers tree yet. I anticipate them to be available by Friday this week. I dont want to miss the boat for 18.04 feature code cutoff. Can you please suggest if I should submit these patches as SAUCE patches or can it be pulled from mainstream once maintainer pulls it in ? 8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of interrupts for master contexts 8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context control register value 44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier names 9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend 0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function configuration f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range 77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration 6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range 90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID 16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support for OCXL 2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter contexts d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file descriptors for OCXL 1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context discovery e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload policy modification 5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU 99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an adapter context d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific mappings 8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling 9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter VPD data b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link 099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction layer 5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element lifecycle 0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt management ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt mapping and registration cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user contexts 270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context polling 302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context reading cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context mmap and release a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor mapping eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user contexts bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master contexts e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous interrupt status bits dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context state machine 9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation errors 96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset 966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations <<< The above is from my local git tree but it has been already sent to linux-scsi mailing list >>> To manage notificati
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
OK, please click 'Hide' on those comments with attachments from your laptop. This bug should be about the original machine only. Open a new bug for your laptop if you like. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I have this bug in 16.04 xenial. Last week I acepted a sys update, current. At next day I return to work boot ... success, wrote my user password, session started, seems correct, open netbeans ide to start coding a proyect,... surprice: no keyboard, until now. I, test almost all forum's suggetions, no success. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Expired Status in linux source package in Yakkety: Won't Fix Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: In Progress Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
Can we fix this by modifying the code in lttng-modules-dkms ? Something like "proposed-patch-1.txt" ** Attachment added: "proposed-fix" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+attachment/5085503/+files/proposed-patch-1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: In Progress Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate
I will be able to try sometime within the next two days. I'll keep you posted, 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/1757021 Title: ubuntu restarts on resume from hibernate Status in linux package in Ubuntu: Incomplete Bug description: Whenever I sleep the computer, upon waking/opening the lid, it reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm, adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to /etc/default/grub. Nothing seems to help. I believe this started after updating to 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 1809 F pulseaudio /dev/snd/controlC0: eric 1809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 20:50:52 2018 HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691 InstallationDate: Installed on 2017-05-29 (294 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 7352 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0H9K1J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08: dmi.product.name: Inspiron 7352 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748922] Re: linux-tools: perf incorrectly linking libbfd
Tested by adding {xenial,artful}-{updates,proposed} to sources.list on a bionic system: $ sudo apt install linux-tools-4.4.0-116 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-tools-4.4.0-116 : Depends: binutils (< 2.27) but 2.30-8ubuntu1 is to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-tools-4.4.0-117 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libdw1 libelf1 libpci3 libunwind8 linux-tools-common The following NEW packages will be installed: libdw1 libelf1 libpci3 libunwind8 linux-tools-4.4.0-117 linux-tools-common 0 upgraded, 6 newly installed, 0 to remove and 1 not upgraded. Need to get 699 kB/1161 kB of archives. After this operation, 3933 kB of additional disk space will be used. Do you want to continue? [Y/n] ^C $ $ sudo apt install linux-tools-4.13.0-37-generic Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-tools-4.13.0-37-generic : Depends: linux-tools-4.13.0-37 but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install linux-tools-4.13.0-38-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libdw1 libelf1 libnuma1 libpci3 libunwind8 linux-tools-4.13.0-38 linux-tools-common The following NEW packages will be installed: libdw1 libelf1 libnuma1 libpci3 libunwind8 linux-tools-4.13.0-38 linux-tools-4.13.0-38-generic linux-tools-common 0 upgraded, 8 newly installed, 0 to remove and 2 not upgraded. Need to get 1100 kB/1584 kB of archives. After this operation, 6991 kB of additional disk space will be used. Do you want to continue? [Y/n] $ So this works as expected. ** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748922 Title: linux-tools: perf incorrectly linking libbfd Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Under bug #783660 we switched away from linking libbfd and switched to using libiberty to demangle C++ names. Somewhere between precise and development upstream changed the order in which the tests are performed and triggered us to start linking against it again. = SRU Justification (for Artful/Xenial) = Impact: Linking perf (part of the linux-tools package) against libbfd prevents users to have linux-tools of different kernel versions installed in parallel. Which makes debugging hard. Fix: As stated above this had been fixed before but upstream changes of the kernel between 3.2 and 4.4 voided those fixes. Unfortunately without causing build failures but causing libbfd to be used again. This has already been fixed up in Bionic. The first of the two patches needs a backport for Xenial to make up for a file rename. The second can be picked into both releases. Testcase: Extracting ./usr/lib/linux-tools-*/perf from the generated linux-tools package and inspecting it with ldd. Old builds will have a reference to libbfd, the test builds did no longer. Risk of regression: low (change of build option which has been done before and also for some time in Bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741081] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Artful: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request, Artful == Enable ZFS module to be loaded without the broken ubuntu-load-zfs- unconditionally.patch. == Fix == Add a new zfs-load-module.service script that modprobes the ZFS module and remove any hard coded module loading from zfs-import-cache.service & zfs-import-scan.service and make these latter scripts require the new zfs-load-module.service script. Also remove the now defunct ubuntu-load-zfs-unconditionally.patch as this will no longer be required. == Testcase == On a clean VM, install with the fixed package, zfs should load automatically. == Regression potential == ZFS module may not load if the changes are broken. However, testing proves this not to be the case. I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup
This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu3.2 --- zfs-linux (0.6.5.11-1ubuntu3.2) artful; urgency=medium * Add new module loading systemd service (LP: #1741081) - loads zfs module unconditionally, and make the zfs-import-cache.service and zfs-import-scan.service services require this service. -- Colin Ian King Fri, 2 Mar 2018 11:47:12 + ** Changed in: zfs-linux (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1741081 Title: zfs-import-cache.service fails on startup Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Artful: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request, Artful == Enable ZFS module to be loaded without the broken ubuntu-load-zfs- unconditionally.patch. == Fix == Add a new zfs-load-module.service script that modprobes the ZFS module and remove any hard coded module loading from zfs-import-cache.service & zfs-import-scan.service and make these latter scripts require the new zfs-load-module.service script. Also remove the now defunct ubuntu-load-zfs-unconditionally.patch as this will no longer be required. == Testcase == On a clean VM, install with the fixed package, zfs should load automatically. == Regression potential == ZFS module may not load if the changes are broken. However, testing proves this not to be the case. I just noticed on my test VM of artful that zfs-import-cache.service does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of that, it fails on startup, since the cache file does not exist. This line is being deleted by debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist per: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749 This patch still exists in bionic, so I assume it will be similarly broken. If the goal of the patch is to load the module (and only that), I think it should create a third unit instead: zfs-load-module.service ^^ runs modprobe zfs zfs-import-cache.service & zfs-import-scan.service ^^ per upstream minus modprobe plus Requires=zfs-load-module.service I have tested this manually and it works. I can submit a package patch if this is the desired solution. Interestingly, before this change, zfs-import-scan.service wasn't starting. If started manually, it worked. I had to give it a `systemctl enable zfs-import-scan.service` to create the Wants symlinks. Looking at the zfsutils-linux.postinst, I see the correct boilerplate from dh_systemd, so I'm not sure why this wasn't already done. Can anyone confirm or deny whether zfs-import-scan.service is enabled out-of-the-box on their system? Is the zfs-import-scan.service not starting actually the cause of the original bug? The design is that *either* zfs-import-cache.service or zfs-import-scan.service starts. They both call modprobe zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1741081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
This package has been waiting for testing in Artful for 90 days and is blocking the release of other makedumpfile fixes for Xenial and Artful. Please test this SRU! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: Fix Committed Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757012] Re: Upgrade ZFS to v0.7.7
** Changed in: zfs-linux (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1757012 Title: Upgrade ZFS to v0.7.7 Status in zfs-linux package in Ubuntu: New Status in zfs-linux package in Debian: New Bug description: v0.7.7 is out: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1757012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
Hmm, it could also be a config change that is needed. The 4.10-rc2 kernel uses the 4.9.0-2.3 configs and the 4.10-rc3 kernel uses the 4.10.0-0.2 config. I'll compare those two as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
I installed v4.16-rc1 and it seems to be working! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
Yeah, I couldn't find anything specific in v4.10-rc3 either. I'll start a reverse bisect to see which commit that points to. It will take testing of about 7 or so test kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757277] 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 1757277 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757277 Title: soft lockup from bcache leading to high load and lockup on trusty Status in linux package in Ubuntu: Incomplete Bug description: I have an environment with Dell R630 servers with RAID controllers with two virtual disks and 22 passthru devices. 2 SAS SSDs and 20 HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs filesystems running bcache backending an 11 node swift cluster (one zone has 1 fewer nodes). Two of the zones have these nodes as described above and they appear to be exibiting soft lockups in the bcache thread of the kernel causing other kernel threads to go into i/o blocking state an keeping processes on any bcache from being successful. disk access to the virtual disks mounted with out bcache is still possible when this lockup occurs. https://pastebin.ubuntu.com/p/mtn47QqBJ3/ There are several softlockup messages found in the dmesg and many of the dumpstack are locked inside the bch_writeback_thread(); static int bch_writeback_thread(void *arg) { [...] while (!kthread_should_stop()) { down_write(&dc->writeback_lock); [...] } One coredump is found when the kswapd is doing the reclaim about the xfs inode cache. __xfs_iflock( struct xfs_inode *ip) { do { prepare_to_wait_exclusive(wq, &wait.wait, TASK_UNINTERRUPTIBLE); if (xfs_isiflocked(ip)) io_schedule(); } while (!xfs_iflock_nowait(ip)); - Possible fix commits: 1). 9baf30972b55 bcache: fix for gc and write-back race https://www.spinics.net/lists/linux-bcache/msg04713.html - Related discussions: 1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate https://www.spinics.net/lists/linux-bcache/msg04617.html 2). Re: hang during suspend to RAM when bcache cache device is attached https://www.spinics.net/lists/linux-bcache/msg04636.html We are running trusty/mitaka swift storage on these nodes with 4.4.0-111 kernel (linux-image-generic-lts-xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757169] Re: linux-kvm: 4.15.0-1003.3 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1003.3 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) -- 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/1757169 Title: linux-kvm: 4.15.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1757164 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1757169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757277] [NEW] soft lockup from bcache leading to high load and lockup on trusty
Public bug reported: I have an environment with Dell R630 servers with RAID controllers with two virtual disks and 22 passthru devices. 2 SAS SSDs and 20 HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs filesystems running bcache backending an 11 node swift cluster (one zone has 1 fewer nodes). Two of the zones have these nodes as described above and they appear to be exibiting soft lockups in the bcache thread of the kernel causing other kernel threads to go into i/o blocking state an keeping processes on any bcache from being successful. disk access to the virtual disks mounted with out bcache is still possible when this lockup occurs. https://pastebin.ubuntu.com/p/mtn47QqBJ3/ There are several softlockup messages found in the dmesg and many of the dumpstack are locked inside the bch_writeback_thread(); static int bch_writeback_thread(void *arg) { [...] while (!kthread_should_stop()) { down_write(&dc->writeback_lock); [...] } One coredump is found when the kswapd is doing the reclaim about the xfs inode cache. __xfs_iflock( struct xfs_inode *ip) { do { prepare_to_wait_exclusive(wq, &wait.wait, TASK_UNINTERRUPTIBLE); if (xfs_isiflocked(ip)) io_schedule(); } while (!xfs_iflock_nowait(ip)); - Possible fix commits: 1). 9baf30972b55 bcache: fix for gc and write-back race https://www.spinics.net/lists/linux-bcache/msg04713.html - Related discussions: 1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate https://www.spinics.net/lists/linux-bcache/msg04617.html 2). Re: hang during suspend to RAM when bcache cache device is attached https://www.spinics.net/lists/linux-bcache/msg04636.html We are running trusty/mitaka swift storage on these nodes with 4.4.0-111 kernel (linux-image-generic-lts-xenial). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: canonical-bootstack trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757277 Title: soft lockup from bcache leading to high load and lockup on trusty Status in linux package in Ubuntu: Incomplete Bug description: I have an environment with Dell R630 servers with RAID controllers with two virtual disks and 22 passthru devices. 2 SAS SSDs and 20 HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs filesystems running bcache backending an 11 node swift cluster (one zone has 1 fewer nodes). Two of the zones have these nodes as described above and they appear to be exibiting soft lockups in the bcache thread of the kernel causing other kernel threads to go into i/o blocking state an keeping processes on any bcache from being successful. disk access to the virtual disks mounted with out bcache is still possible when this lockup occurs. https://pastebin.ubuntu.com/p/mtn47QqBJ3/ There are several softlockup messages found in the dmesg and many of the dumpstack are locked inside the bch_writeback_thread(); static int bch_writeback_thread(void *arg) { [...] while (!kthread_should_stop()) { down_write(&dc->writeback_lock); [...] } One coredump is found when the kswapd is doing the reclaim about the xfs inode cache. __xfs_iflock( struct xfs_inode *ip) { do { prepare_to_wait_exclusive(wq, &wait.wait, TASK_UNINTERRUPTIBLE); if (xfs_isiflocked(ip)) io_schedule(); } while (!xfs_iflock_nowait(ip)); - Possible fix commits: 1). 9baf30972b55 bcache: fix for gc and write-back race https://www.spinics.net/lists/linux-bcache/msg04713.html - Related discussions: 1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate https://www.spinics.net/lists/linux-bcache/msg04617.html 2). Re: hang during suspend to RAM when bcache cache device is attached https://www.spinics.net/lists/linux-bcache/msg04636.html We are running trusty/mitaka swift storage on these nodes with 4.4.0-111 kernel (linux-image-generic-lts-xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755268] Re: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled)
OK, this is my meesage that I wrote to kernel's netdev list: https://www.mail-archive.com/netdev@vger.kernel.org/msg223827.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/1755268 Title: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -machine pc-i440fx-xenial,accel=kvm,usb=off -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : htt
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
Well, does not seem to be in: ubuntu@ubu-vm-01:~$ uname -a Linux ubu-vm-01 4.4.0-116-generic #140~lp1735420Commitcabab3f SMP Tue Mar 20 20:07:24 UTC 2018 s390x s390x s390x GNU/Linux ubuntu@ubu-vm-01:~$ kvm-ok INFO: /dev/kvm exists KVM acceleration can be used ubuntu@ubu-vm-01:~$ ls -la /dev/kvm crw-rw 1 root kvm 10, 232 Mar 20 12:17 /dev/kvm Interestingly I couldn't find any indication in the 4.10.0-041000rc3 changes file that point to this functionality ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757228] Re: cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752672] Re: CAPI Flash (cxlflash) update
There are significant conflicts when trying to apply these patches to 4.15, likely due to changes in 4.16. Can you advise which additional patches are needed? Thanks! ** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1752672 Title: CAPI Flash (cxlflash) update Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This is a feature for capi flash (cxlflash) inside the kernel. We have upstreamed the below 38 patches but they are not in the maintainers tree yet. I anticipate them to be available by Friday this week. I dont want to miss the boat for 18.04 feature code cutoff. Can you please suggest if I should submit these patches as SAUCE patches or can it be pulled from mainstream once maintainer pulls it in ? 8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of interrupts for master contexts 8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context control register value 44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier names 9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend 0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function configuration f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range 77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration 6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range 90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID 16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support for OCXL 2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter contexts d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file descriptors for OCXL 1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context discovery e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload policy modification 5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU 99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an adapter context d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific mappings 8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling 9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter VPD data b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link 099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction layer 5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element lifecycle 0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt management ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt mapping and registration cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user contexts 270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context polling 302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context reading cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context mmap and release a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor mapping eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user contexts bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master contexts e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous interrupt status bits dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context state machine 9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation errors 96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset 966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations <<< The above is from my local git tree but it has been already sent to linux-scsi mailing list >>> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1752672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757081] Re: freeze ubuntu 17.10
my problem solved. I think google chrome cause this freezing and I Untick "use hardware acceleration when available" , Disable "GPU Rasterization". after that my system did not freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757081 Title: freeze ubuntu 17.10 Status in linux package in Ubuntu: Incomplete Bug description: I had installed Ubuntu 17.10 on a spare partition and updating it daily my system freezes frequently It does not respond to any key presses like Ctrl Alt F1 or Ctrl Alt Del. My Leptop is Lenovo-E530 which has Intel Core i5 chip. Memory is 8GB and 2048 MB swap partition. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amin 2765 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 20 12:39:56 2018 HibernationDevice: RESUME=UUID=9542262e-d4ca-4d0c-81f4-17637dfb4fe1 InstallationDate: Installed on 2018-01-17 (61 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 62723UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=91fdd5d7-664d-4cd0-bab8-07d9c8974e1a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET74WW (2.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 62723UG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET74WW(2.08):bd11/14/2012:svnLENOVO:pn62723UG:pvrThinkPadEdgeE530:rvnLENOVO:rn62723UG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E530 dmi.product.name: 62723UG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757256] Re: Apparmor profile gajim
** Package changed: linux (Ubuntu) => apparmor (Ubuntu) ** Changed in: apparmor (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757256 Title: Apparmor profile gajim Status in apparmor package in Ubuntu: New Bug description: Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and saved usr.bin.gajim after scanning. After I restart machine and run Gajim from terminal I get: Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x6a383a1d5540 (most recent call first): Aborted (core dumped) If I delete the profile and restart machine it runs (to confirm it is profile causing). This is my current profile # vim:syntax=apparmor # -- # #Copyright (C) 2015-2018 Mikhail Morfikov # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- #include /usr/bin/gajim { #include #include #include #include #include #include #include #include #include /usr/bin/gajim mr, /usr/bin/ r, /usr/local/bin/ r, # Gajim plugins /usr/share/gajim/plugins/ r, /usr/share/gajim/plugins/** r, # Gajim home files owner @{HOME}/.config/gajim/ rw, owner @{HOME}/.config/gajim/** rw, owner @{HOME}/.local/share/gajim/ rw, owner @{HOME}/.local/share/gajim/** rwk, # User downloads owner @{HOME}/[dD]ownload{,s}/ r, owner @{HOME}/[dD]ownload{,s}/** rwl, owner @{HOME}/[dD]esktop/ r, owner @{HOME}/[dD]esktop/** rwl, # Cache owner /tmp/morfik_cache/.cache/gajim/ rwk, owner /tmp/morfik_cache/.cache/gajim/** rwk, owner @{HOME}/.cache/gajim/ rwk, owner @{HOME}/.cache/gajim/** rwk, # Deny access to webcam and mic deny /dev/video0 rw, deny /dev/v4l/by-path/ r, deny /dev/snd/pcmC0D0c rw, owner @{PROC}/@{pid}/mounts r, owner @{PROC}/@{pid}/fd/ r, owner @{PROC}/@{pid}/mountinfo r, # External apps /usr/lib/firefox/firefox rPUx, /usr/bin/gpg rPUx, /usr/share/glib-2.0/schemas/gschemas.compiled r, owner /{,var/}run/user/[0-9]*/dconf/user rw, # Silencer deny /usr/lib/python3/dist-packages/** w, deny /usr/share/gajim/plugins/** w, deny @{HOME}/ r, # Sounds /usr/bin/aplay Cx -> audio, /usr/bin/pacat Cx -> audio, profile audio { #include #include /usr/bin/aplay mr, /usr/bin/pacat mr, owner @{HOME}/.Xauthority r, /etc/machine-id r, /var/lib/dbus/machine-id r, } /sbin/ldconfig Cx -> ldconfig, profile ldconfig { #include /sbin/ldconfig mr, } /bin/dash Cx -> dash, profile dash { #include /bin/dash mr, /bin/uname rix, /usr/bin/gpg rPUx, } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1757256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla
--- Comment From nguy...@us.ibm.com 2018-03-20 16:38 EDT--- I went to https://www.spinics.net/lists/kvm/msg165629.html but it only has source code change for the problem. Can Linux team build a patch against Ubuntu 18.04 kernel 4.15.0-12-generic for test team to install. 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/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Fix Released Bug description: == Comment: #0 - Satheesh Rajendran - 2018-02-23 08:31:06 == ---Problem Description--- libvirt unable to start a KVM guest complaining about cap-htm machine property to be off Host Env: # lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 160 On-line CPU(s) list: 0-159 Thread(s) per core: 4 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported CPU max MHz: 3800. CPU min MHz: 2166. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-79 NUMA node8 CPU(s): 80-159 ii qemu-kvm 1:2.11+dfsg-1ubuntu2 ppc64el QEMU Full virtualization on x86 hardware ii libvirt-bin 4.0.0-1ubuntu3 ppc64el programs for the libvirt library # lsmcode Version of System Firmware : Product Name : OpenPOWER Firmware Product Version : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp Product Extra : occ-577915f Product Extra : skiboot-v5.9-240-g081882690163-pcbedce4 Product Extra : petitboot-v1.6.6-p019c87e Product Extra : sbe-095e608 Product Extra : machine-xml-fb5f933 Product Extra : hostboot-9bfb201 Product Extra : linux-4.14.13-openpower1-p78d7eee Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-10-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Boot a guest from libvirt with default pseries machine type or pseries-bionic /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: ,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on 2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not support Transactional Memory, try cap-htm=off Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start virt-tests-vm1 otherwise, please restart your installation. 2. Fails to boot.. Note: if we specify machine type as pseries=2.12 it boots fine like below /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries-2.12 --memory=32768 --vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. qemu-cmd line: libvirt+ 4283 1 99 09:26 ?00:00:38 qemu-system-ppc64 -enable-kvm -name guest=virt-tests-vm1,debug
[Kernel-packages] [Bug 1757256] 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 1757256 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/1757256 Title: Apparmor profile gajim Status in linux package in Ubuntu: Incomplete Bug description: Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and saved usr.bin.gajim after scanning. After I restart machine and run Gajim from terminal I get: Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x6a383a1d5540 (most recent call first): Aborted (core dumped) If I delete the profile and restart machine it runs (to confirm it is profile causing). This is my current profile # vim:syntax=apparmor # -- # #Copyright (C) 2015-2018 Mikhail Morfikov # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- #include /usr/bin/gajim { #include #include #include #include #include #include #include #include #include /usr/bin/gajim mr, /usr/bin/ r, /usr/local/bin/ r, # Gajim plugins /usr/share/gajim/plugins/ r, /usr/share/gajim/plugins/** r, # Gajim home files owner @{HOME}/.config/gajim/ rw, owner @{HOME}/.config/gajim/** rw, owner @{HOME}/.local/share/gajim/ rw, owner @{HOME}/.local/share/gajim/** rwk, # User downloads owner @{HOME}/[dD]ownload{,s}/ r, owner @{HOME}/[dD]ownload{,s}/** rwl, owner @{HOME}/[dD]esktop/ r, owner @{HOME}/[dD]esktop/** rwl, # Cache owner /tmp/morfik_cache/.cache/gajim/ rwk, owner /tmp/morfik_cache/.cache/gajim/** rwk, owner @{HOME}/.cache/gajim/ rwk, owner @{HOME}/.cache/gajim/** rwk, # Deny access to webcam and mic deny /dev/video0 rw, deny /dev/v4l/by-path/ r, deny /dev/snd/pcmC0D0c rw, owner @{PROC}/@{pid}/mounts r, owner @{PROC}/@{pid}/fd/ r, owner @{PROC}/@{pid}/mountinfo r, # External apps /usr/lib/firefox/firefox rPUx, /usr/bin/gpg rPUx, /usr/share/glib-2.0/schemas/gschemas.compiled r, owner /{,var/}run/user/[0-9]*/dconf/user rw, # Silencer deny /usr/lib/python3/dist-packages/** w, deny /usr/share/gajim/plugins/** w, deny @{HOME}/ r, # Sounds /usr/bin/aplay Cx -> audio, /usr/bin/pacat Cx -> audio, profile audio { #include #include /usr/bin/aplay mr, /usr/bin/pacat mr, owner @{HOME}/.Xauthority r, /etc/machine-id r, /var/lib/dbus/machine-id r, } /sbin/ldconfig Cx -> ldconfig, profile ldconfig { #include /sbin/ldconfig mr, } /bin/dash Cx -> dash, profile dash { #include /bin/dash mr, /bin/uname rix, /usr/bin/gpg rPUx, } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757228] Re: cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
** 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/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757256] [NEW] Apparmor profile gajim
Public bug reported: Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and saved usr.bin.gajim after scanning. After I restart machine and run Gajim from terminal I get: Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x6a383a1d5540 (most recent call first): Aborted (core dumped) If I delete the profile and restart machine it runs (to confirm it is profile causing). This is my current profile # vim:syntax=apparmor # -- # #Copyright (C) 2015-2018 Mikhail Morfikov # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- #include /usr/bin/gajim { #include #include #include #include #include #include #include #include #include /usr/bin/gajim mr, /usr/bin/ r, /usr/local/bin/ r, # Gajim plugins /usr/share/gajim/plugins/ r, /usr/share/gajim/plugins/** r, # Gajim home files owner @{HOME}/.config/gajim/ rw, owner @{HOME}/.config/gajim/** rw, owner @{HOME}/.local/share/gajim/ rw, owner @{HOME}/.local/share/gajim/** rwk, # User downloads owner @{HOME}/[dD]ownload{,s}/ r, owner @{HOME}/[dD]ownload{,s}/** rwl, owner @{HOME}/[dD]esktop/ r, owner @{HOME}/[dD]esktop/** rwl, # Cache owner /tmp/morfik_cache/.cache/gajim/ rwk, owner /tmp/morfik_cache/.cache/gajim/** rwk, owner @{HOME}/.cache/gajim/ rwk, owner @{HOME}/.cache/gajim/** rwk, # Deny access to webcam and mic deny /dev/video0 rw, deny /dev/v4l/by-path/ r, deny /dev/snd/pcmC0D0c rw, owner @{PROC}/@{pid}/mounts r, owner @{PROC}/@{pid}/fd/ r, owner @{PROC}/@{pid}/mountinfo r, # External apps /usr/lib/firefox/firefox rPUx, /usr/bin/gpg rPUx, /usr/share/glib-2.0/schemas/gschemas.compiled r, owner /{,var/}run/user/[0-9]*/dconf/user rw, # Silencer deny /usr/lib/python3/dist-packages/** w, deny /usr/share/gajim/plugins/** w, deny @{HOME}/ r, # Sounds /usr/bin/aplay Cx -> audio, /usr/bin/pacat Cx -> audio, profile audio { #include #include /usr/bin/aplay mr, /usr/bin/pacat mr, owner @{HOME}/.Xauthority r, /etc/machine-id r, /var/lib/dbus/machine-id r, } /sbin/ldconfig Cx -> ldconfig, profile ldconfig { #include /sbin/ldconfig mr, } /bin/dash Cx -> dash, profile dash { #include /bin/dash mr, /bin/uname rix, /usr/bin/gpg rPUx, } } ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1757256 Title: Apparmor profile gajim Status in linux package in Ubuntu: Incomplete Bug description: Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and saved usr.bin.gajim after scanning. After I restart machine and run Gajim from terminal I get: Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x6a383a1d5540 (most recent call first): Aborted (core dumped) If I delete the profile and restart machine it runs (to confirm it is profile causing). This is my current profile # vim:syntax=apparmor # -- # #Copyright (C) 2015-2018 Mikhail Morfikov # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- #include /usr/bin/gajim { #include #include #include #include #include #include #include #include #include /usr/bin/gajim mr, /usr/bin/ r, /usr/local/bin/ r, # Gajim plugins /usr/share/gajim/plugins/ r, /usr/share/gajim/plugins/** r, # Gajim home files owner @{HOME}/.config/gajim/ rw, owner @{HOME}/.config/gajim/** rw, owner @{HOME}/.local/share/gajim/ rw, owner @{HOME}/.local/share/gajim/** rwk, # User downloads owner @{HOME}/[dD]ownload{,s}/ r, owner @{HOME}/[dD]ownload{,s}/** rwl, owner @{HOME}/[dD]esktop/ r, owner @{HOME}/[dD]esktop/** rwl, # Cache owner /tmp/morfik_cache/.cache/gajim/ rwk, owner /tmp/morfik_cache/.cache/gajim/** rwk, owner @{HOME}/.cache/gajim/ rwk, owner @{HOME}/.cache/gajim/** rwk, # Deny access to webcam and mic deny /dev/video0 rw, deny /dev/v4l/by-path/ r, deny /dev/snd/pcmC0D0c rw, owner @{PROC}/@{pid}/m
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
There was only one commit that sticks out between 4.10-rc2 and v4.10-rc3, it is kvm and s390 related: cabab3f ("s390/kbuild: enable modversions for symbols exported from asm") I built a Xenial test kernel with a pick of this commit. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1735420/ Can you test this kernel and see if it resolves the bug? If it does not, we'll have to reverse bisect to identify the commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752310] Re: What is the zfs support policy wrt. LTS releases?
I am not sure if this is might be more of a question rather than a bug report, but I'll try to answer. At the moment the version of zfs-linux in Ubuntu bionic is 0.7.5-1ubuntu7. I don't know if there are any plans to update this particular package before release of 18.04, but at the moment this seems to be the version which will be shipped. I just found bug 1757012, so it is possible this could be updated if there is a push for it. In general, newer package versions are added to the development version of Ubuntu during the development cycle until it is officially released. So for instance 16.04 (xenial) is shipping what was the latest version in the archive at the time it was released. The package archives aren't completly frozen, it is possible to update packages with specific, important patches in a Stable Release Upgrade (https://wiki.ubuntu.com/StableReleaseUpdates) or a backport of a newer version (https://wiki.ubuntu.com/UbuntuBackports). Hope this helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1752310 Title: What is the zfs support policy wrt. LTS releases? Status in zfs-linux package in Ubuntu: Confirmed Bug description: If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is the assumption correct that LTS releases will not receive a new major ZFS release ? To be as practical as possible: Bionic will be stuck at zfs 0.7.x, Xenial at zfs 0.6.x ? If my assumption is wrong, when would Xenial see zfs 0.7 ? Has a policy been defined ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1752310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757228] Re: cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Incomplete Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.dat
[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10
$ uname -a Linux virgil 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ Booted with my external monitor plugged in, and Ctrl-Alt-F2 still gets me to a VT. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724911 Title: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification == After upgrading my laptop to Ubuntu 17.10, I am unable to access gettys on any of the text-mode VTs on my system. gdm3 is running on VT1, my user session is running on VT2. I can switch between these. If I switch to VT3, I know that the VT switch has happened in the kernel because the X cursor disappears; but the display retains the output of my X session, and the text console with getty never appears. Switching back to VT2 works fine. The same problem occurs with either Wayland or X. My laptop is docked with an external monitor, which could be a factor. (I also notice that during boot, plymouth is only rendered on the internal monitor, not the external monitor; this may be related). I have not yet tested whether this problem is reproducible if I undock. The system is booting with vt.handoff=7, which I believe is still the default in Ubuntu 17.10. This bug is a regression in Artful introduced by mainline commit: 7581d5ca2bb ("drm/i915/fbdev: Check for existence of ifbdev->vma before operations"). It was first found that this bug was fixed in v4.14-rc1. However, after a lengthy "Reverse" bisect, the exact commit could not be identified. This is because the fix came in via a merge base. A regular bisect was then done to identify commit 7581d5ca2bb as the offending commit that introduced the bug. Using the file that this commit touched, a "Reverse" bisect was done again between 7581d5ca2bb..v4.14-rc1. This identified the following commit 88be58be886f as the fix to this regression. == Fix == commit 88be58be886f1215cc73dc8c273c985eecd7385c Author: Daniel Vetter Date: Thu Jul 6 15:00:19 2017 +0200 drm/i915/fbdev: Always forward hotplug events == Regression Potential == This patch fixes a current regression and is a minor one-liner. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon24080 F pulseaudio /dev/snd/controlC0: vorlon24080 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 09:57:59 2017 HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a InstallationDate: Installed on 2010-09-24 (2582 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757217] Re: Behaviour change in reading /proc/modules could cause issues in userspace tools
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Incomplete ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Artful) ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757217 Title: Behaviour change in reading /proc/modules could cause issues in userspace tools Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This was discovered while investigating tracebacks in the cert suite. We have a script that parses /proc/modules and returns the information in a more human-readable format as part of the info gathering we do during cert testing. On 4.13 and older kernels, this script was run as a normal user with no error. On 4.15, this script dumps a python trace because /proc/modules now returns a null reference instead of just a blank memory offset. On 4.13 and older, when you read the file, you get something like this (root and non-root shown): bladernr@galactica:~$ sudo cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0xc06b5000 bladernr@galactica:~$ cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0x Note that non-root reading returns a memory offset of 0x0 which is easily parsable. Now, on 4.15, this has changed: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xc0225000 ptp 20480 2 igb,e1000e, Live 0xc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null) Now, however, non-root reading returns a null reference which causes attempts to parse the offset to fail. I imagine this is probably by design, and it's a minor bug, but I wanted to raise it as it could cause issues when running userspace tools that parse /proc/modules on 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: User Name 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 17:24 seq crw-rw 1 root audio 116, 33 Mar 20 17:24 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 20 17:59:51 2018 MachineType: LENOVO INVALID PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=9fdf32ba-26ce-4d54-8457-dbd62057c7e9 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT97CUS dmi.board.name: ThinkServer RS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT97CUS:bd04/07/2017:svnLENOVO:pnINVALID:pvrFFF:rvnLENOVO:rnThinkServerRS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: INVALID dmi.product.version: FFF dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1757012] Re: Upgrade ZFS to v0.7.7
Thanks for taking your time to report this issue and help making Ubuntu better. I found a corresponding bug report in Debian so I have attached a bug watch. Normally a newer version in Debian would be possibly to sync automatically to the development version of Ubuntu. However, it looks like the Ubuntu package for zfs-linux contains some Ubuntu-specific patches so this will probably need a manual merge once the package enters Debian. Oh, and and to get the newer version into Ubuntu bionic, that would likely require a FeatureFreezeException (https://wiki.ubuntu.com/FreezeExceptionProcess) at this point. ** Bug watch added: Debian Bug tracker #893578 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893578 ** Also affects: zfs-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893578 Importance: Unknown Status: Unknown ** Tags added: needs-debian-merge upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1757012 Title: Upgrade ZFS to v0.7.7 Status in zfs-linux package in Ubuntu: New Status in zfs-linux package in Debian: Unknown Bug description: v0.7.7 is out: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1757012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757238] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
Do you happen to have away to reproduce this bug? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757238 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Incomplete Bug description: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
No. The times I've read dmesg there was nothing like this, neither as an error popup. I'll grep D0 and D3 the next time 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/b
[Kernel-packages] [Bug 1757240] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
*** This bug is a duplicate of bug 1757238 *** https://bugs.launchpad.net/bugs/1757238 ** This bug has been marked a duplicate of bug 1757238 BUG: unable to handle kernel NULL pointer dereference at (null) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757240 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: continuous bug error messages ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:15:41 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c863bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
Ok, I'll check it out. Thank you very much! By the way, we downloaded and tested one of the Deb packages you created, and it worked quite well. Will check which one was exactly before reporting (almost sure it was the one for xenial). We managed to reproduce the issue easily by booting into pxe and, after the nic was started (trying to get an ip), we reset the machine and booted into Ubuntu. There is a huge difference by doing this and doing a cold boot, directly into Ubuntu. My hypothesis is that pxe setups the nic in a way that is not the default, by changing one (or more) of the config bits for some register. This same bit(s) is/are not being touched by the tg3 driver without patch. This way, a boot may work sometimes, maybe due to default values not being set by the kernel module tg3 (and being set by pxe code, if it executed before Linux is loaded). Anyway, the unpatched kernel breaks very quickly, while the patched kernel you provided worked out very well. This happens after running pxe. I will check your links soon and return with our results in the next days, hopefully this weekend or next week. Thank you, Paulo On Mar 20, 2018 14:16, "Kai-Heng Feng" wrote: Guy, Broadcom has a new patch [1] that need to test. Here's the kernel [2] to try. [1] https://lkml.org/lkml/2018/3/20/35 [2] https://people.canonical.com/~khfeng/lp1447664-20180320/ -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1447664 Title: 14e4:1687 broadcom tg3 network driver disconnects under high load Status in linux package in Ubuntu: Triaged Status in linux package in Debian: New Bug description: The tg3 broadcom network driver that binds with chipset 5762 goes offline and unable to recover (even with tg3 watchdog timeout) when network transmit is under high load. Call trace: https://launchpadlibrarian.net/204185480/dmesg When this happens, only a reboot would be able to fix it. Sometimes, however, bringing the interface offline and online (via ifconfig) would recover networking. I've also tested with the latest tg3 driver (dec 2014 version) and networking is still problematic. I have also disabled TSO, GSO etc... with ethtool and the bug still surfaces. This bug may be related to the integrated Firmware. Here is the procedure to replicate the issue because it is hard to replicate it under moderate network load. 1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a Ubuntu/Kubunu Live CD 14.04-15.04. 2. from another machine: start 5 sessions, repetitively copy (scp with public key authentication) a 70 meg file back and forth to the tg3 machine in each session. (not sure if this is necessary) 3. create a 1GB file on the tg3 machine, with something like dd if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000)) 4. from another machine: repetitively scp copy that 1GB file from the tg3 machine. This can be done with something like: while [ 0 ]; do scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp done; Networking will mostly goes offline in about 10-30 minutes. WORKAROUND: Add udev rule to make the changes permanent in /etc/udev/rules.d/80-tg3-fix.rules : ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu3748 F pulseaudio /dev/snd/controlC0: kubuntu3748 F pulseaudio CasperVersion: 1.360 Date: Thu Apr 23 11:16:24 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1757240] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757240 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: continuous bug error messages ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:15:41 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c863bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755268] Re: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled)
** Summary changed: - Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) + Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled) ** Description changed: # System information # - # uname -a - Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + # uname -a + Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux - # cat /etc/os-release - NAME="Ubuntu" - VERSION="16.04.4 LTS (Xenial Xerus)" - ID=ubuntu - ID_LIKE=debian - PRETTY_NAME="Ubuntu 16.04.4 LTS" - VERSION_ID="16.04" - HOME_URL="http://www.ubuntu.com/"; - SUPPORT_URL="http://help.ubuntu.com/"; - BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; - VERSION_CODENAME=xenial - UBUNTU_CODENAME=xenial + # cat /etc/os-release + NAME="Ubuntu" + VERSION="16.04.4 LTS (Xenial Xerus)" + ID=ubuntu + ID_LIKE=debian + PRETTY_NAME="Ubuntu 16.04.4 LTS" + VERSION_ID="16.04" + HOME_URL="http://www.ubuntu.com/"; + SUPPORT_URL="http://help.ubuntu.com/"; + BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; + VERSION_CODENAME=xenial + UBUNTU_CODENAME=xenial - # ethtool -i eno1 - driver: mlx4_en - version: 4.3-1.0.1 - firmware-version: 2.42.5004 - expansion-rom-version: - bus-info: :11:00.0 - supports-statistics: yes - supports-test: yes - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: yes + # ethtool -i eno1 + driver: mlx4_en + version: 4.3-1.0.1 + firmware-version: 2.42.5004 + expansion-rom-version: + bus-info: :11:00.0 + supports-statistics: yes + supports-test: yes + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: yes - # ethtool -i bond0 - driver: bonding - version: 3.7.1 - firmware-version: 2 - expansion-rom-version: - bus-info: - supports-statistics: no - supports-test: no - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: no + # ethtool -i bond0 + driver: bonding + version: 3.7.1 + firmware-version: 2 + expansion-rom-version: + bus-info: + supports-statistics: no + supports-test: no + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: no - # ethtool -i vmbr0 - driver: bridge - version: 2.3 - firmware-version: N/A - expansion-rom-version: - bus-info: N/A - supports-statistics: no - supports-test: no - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: no + # ethtool -i vmbr0 + driver: bridge + version: 2.3 + firmware-version: N/A + expansion-rom-version: + bus-info: N/A + supports-statistics: no + supports-test: no + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz - ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- + ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: + auto lo + iface lo inet loopback - auto lo - iface lo inet loopback + auto openibd + iface openibd inet manual + pre-up /etc/init.d/openibd start + pre-down /etc/init.d/openibd force-stop - auto openibd - iface openibd inet manual - pre-up /etc/init.d/openibd start - pre-down /etc/init.d/openibd force-stop + auto bond0 + iface bond0 inet manual + pre-up ip link add bond0 type bond || true + pre-up ip link set bond0 down + pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 + pre-up ip link set eno1 down + pre-up ip link set eno1d1 down + pre-up ip link set eno1 master bond0 + pre-up ip link set eno1d1 master bond0 + pre-up ip link set bond0 up + pre-down ip link del bond0 - auto bond0 - iface bond0 inet manual - pre-up ip link add bond0 type bond || true - pre-up ip link set bond0 down - pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 - pre-up ip link set eno1 down - pre-up ip link set eno1d1 down - pre-up ip link set eno1 master bond0 - pre-up ip link set eno1d1 master bond0 - pre-up ip link set bond0
[Kernel-packages] [Bug 1757238] 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/1757238 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757240] 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/1757240 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: continuous bug error messages ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:15:41 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c863bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757238] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757238 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
Will, can you provide some advice? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1757238] [NEW] BUG: unable to handle kernel NULL pointer dereference at (null)
Public bug reported: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-driver-nouveau kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757238 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: no specific info ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:27:45 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c866bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.cha
[Kernel-packages] [Bug 1757240] [NEW] BUG: unable to handle kernel NULL pointer dereference at (null)
Public bug reported: continuous bug error messages ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:15:41 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c863bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-driver-nouveau kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757240 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Confirmed Bug description: continuous bug error messages ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1015 F pulseaudio th6mas 1450 F pulseaudio /dev/snd/controlC1: gdm1015 F pulseaudio th6mas 1450 F pulseaudio Date: Mon Mar 19 20:15:41 2018 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at (null) RIP: nvkm_object_unmap+0x5/0x30 [nouveau] RSP: b5f4c863bc40 Failure: oops InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=27b90b0d-cdf1-470d-b5d0-dfb25066cfee ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at (null) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
@Seth, thunderbolt-tools was requested by Dell to be part of Ubuntu Bionic, I believe it's for some specific Dell laptops, but I can't provide any more specific details as Mario from Dell is on vacation right now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscript
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
Seems like "bolt" was handled before my MIR, which is perplexing as my request was for a Dell requested package that was filed earlier back in 2018-02-08 where as bolt was filed in 2018-02-27. I'm not sure about bolt, this seems to be a Ubuntu package and not one that is in Debian. @Mario, any comments since I'm kind of driving this for Dell for you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs securit
[Kernel-packages] [Bug 1757228] Re: cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
FIY. This has not been merged into Linus' tree yet. Cascardo. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Bionic) Status: In Progress => 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/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
I had the same problem and fix #9 worked for me (adding "pci=noaer"). I'm on Ubuntu 17.10 on a HP Pavilion laptop 14-008nf and all hardware seems to be working. I was flooded with this(took lots of disk space cause logging constantly): akem@akem-HP-Pavilion-Notebook:~$ tail /var/log/syslog Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950330] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950337] pcieport :00:1d.0:[ 0] Receiver Error (First) Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950348] pcieport :00:1d.0: AER: Corrected error received: id=00e8 Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950746] pcieport :00:1d.0: can't find device of ID00e8 Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950751] pcieport :00:1d.0: AER: Corrected error received: id=00e8 Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950762] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Receiver ID) Mar 20 19:00:03 akem-HP-Pavilion-Notebook kernel: [20571.950770] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.produ
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
** Changed in: linux (Ubuntu) Assignee: Colin Ian King (colin-king) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: In Progress Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757228] [NEW] cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
Public bug reported: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. ** Affects: ubuntu-power-systems Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: In Progress ** Tags: architecture-ppc64le bugnameltc-165879 severity-critical targetmilestone-inin1804 triage-g ** Tags added: architecture-ppc64le bugnameltc-165879 severity-critical targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757057] Re: sysfs test in ubuntu_stress_smoke will induce kernel oops on X-HWE ppc64le
** Changed in: linux (Ubuntu) Assignee: Colin Ian King (colin-king) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757057 Title: sysfs test in ubuntu_stress_smoke will induce kernel oops on X-HWE ppc64le Status in linux package in Ubuntu: Incomplete Bug description: Proposed kernel 4.13.0-38.43~16.04.1 on ppc64le sysfs FAILED (kernel oopsed) [ 891.312202] WARNING! power/level is deprecated; use power/control instead [ 892.138260] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.138627] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.138976] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.139303] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.139610] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 255 [ 892.141571] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.141697] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.142003] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.142319] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.142616] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.142903] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 87 [ 892.148239] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.148583] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.149406] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.149530] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 255 [ 892.149855] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.150161] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.150467] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.151980] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.152255] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.152558] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.152980] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.153545] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.153908] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.154197] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.154502] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.154813] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.155110] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.155407] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.162052] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.162406] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.162708] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 85 [ 892.163007] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.163304] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.163612] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.163912] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.164505] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.164816] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.165118] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.165413] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.165717] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.166004] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.166309] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.166613] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.166908] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.167212] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.167524] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.167803] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 22 [ 892.168128] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.168439] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.168732] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.169038] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.169335] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.169630] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.169934] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.170235] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.176000] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.176350] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.176643] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.176939] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.177258] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.177546] ses 0:0:8:0: Wrong diagnostic page; asked for 2 got 46 [ 892.177962] ses 0:0:8:0
[Kernel-packages] [Bug 1757228] Re: cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757228 Title: cxl: Fix timebase synchronization status on POWER9 missing (CAPI) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1757228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
This appears to be duplicating functionality from bolt: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1752056 Are both packages truly desired? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 1754492] Re: Dell XPS 15 - Turned off Keyboard backlight turns on after resuming from suspend
Please try kernel in https://people.canonical.com/~khfeng/lp1754492/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754492 Title: Dell XPS 15 - Turned off Keyboard backlight turns on after resuming from suspend Status in linux package in Ubuntu: Confirmed Bug description: On the Dell XPS 15 (2017; 9560) the turned off keyboard backlight turns back on following a suspend. Ubuntu GNOME Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Linux krypton 4.13.0-36-generic #40~16.04.1-Ubuntu SMP --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 2553 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9def3c5c-92fd-4360-a403-30fc2e7e6a96 InstallationDate: Installed on 2017-08-14 (207 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 007: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=2149c19b-fca4-49d2-809b-e28952692af2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757217] 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/1757217 Title: Behaviour change in reading /proc/modules could cause issues in userspace tools Status in linux package in Ubuntu: Confirmed Bug description: This was discovered while investigating tracebacks in the cert suite. We have a script that parses /proc/modules and returns the information in a more human-readable format as part of the info gathering we do during cert testing. On 4.13 and older kernels, this script was run as a normal user with no error. On 4.15, this script dumps a python trace because /proc/modules now returns a null reference instead of just a blank memory offset. On 4.13 and older, when you read the file, you get something like this (root and non-root shown): bladernr@galactica:~$ sudo cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0xc06b5000 bladernr@galactica:~$ cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0x Note that non-root reading returns a memory offset of 0x0 which is easily parsable. Now, on 4.15, this has changed: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xc0225000 ptp 20480 2 igb,e1000e, Live 0xc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null) Now, however, non-root reading returns a null reference which causes attempts to parse the offset to fail. I imagine this is probably by design, and it's a minor bug, but I wanted to raise it as it could cause issues when running userspace tools that parse /proc/modules on 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: User Name 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 17:24 seq crw-rw 1 root audio 116, 33 Mar 20 17:24 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 20 17:59:51 2018 MachineType: LENOVO INVALID PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=9fdf32ba-26ce-4d54-8457-dbd62057c7e9 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT97CUS dmi.board.name: ThinkServer RS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT97CUS:bd04/07/2017:svnLENOVO:pnINVALID:pvrFFF:rvnLENOVO:rnThinkServerRS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: INVALID dmi.product.version: FFF dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpa
[Kernel-packages] [Bug 1757228] [NEW] cxl: Fix timebase synchronization status on POWER9 missing (CAPI)
You have been subscribed to a public bug: The following patch, already in mainline, is missing in Ubuntu 18.04 (kernel v4.15): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c2be663d5307fb9751a562ac664fa7 ("cxl: Fix timebase synchronization status on P9") Please integrate this patch into Ubuntu 18.04. Thanks in advance for your support. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-165879 severity-critical targetmilestone-inin1804 -- cxl: Fix timebase synchronization status on POWER9 missing (CAPI) https://bugs.launchpad.net/bugs/1757228 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757217] [NEW] Behaviour change in reading /proc/modules could cause issues in userspace tools
Public bug reported: This was discovered while investigating tracebacks in the cert suite. We have a script that parses /proc/modules and returns the information in a more human-readable format as part of the info gathering we do during cert testing. On 4.13 and older kernels, this script was run as a normal user with no error. On 4.15, this script dumps a python trace because /proc/modules now returns a null reference instead of just a blank memory offset. On 4.13 and older, when you read the file, you get something like this (root and non-root shown): bladernr@galactica:~$ sudo cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0xc06b5000 bladernr@galactica:~$ cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0x Note that non-root reading returns a memory offset of 0x0 which is easily parsable. Now, on 4.15, this has changed: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xc0225000 ptp 20480 2 igb,e1000e, Live 0xc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null) Now, however, non-root reading returns a null reference which causes attempts to parse the offset to fail. I imagine this is probably by design, and it's a minor bug, but I wanted to raise it as it could cause issues when running userspace tools that parse /proc/modules on 4.15. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: User Name 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 17:24 seq crw-rw 1 root audio 116, 33 Mar 20 17:24 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 20 17:59:51 2018 MachineType: LENOVO INVALID PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=9fdf32ba-26ce-4d54-8457-dbd62057c7e9 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT97CUS dmi.board.name: ThinkServer RS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT97CUS:bd04/07/2017:svnLENOVO:pnINVALID:pvrFFF:rvnLENOVO:rnThinkServerRS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: INVALID dmi.product.version: FFF dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Description changed: This was discovered while investigating tracebacks in the cert suite. We have a script that parses /proc/modules and returns the information in a more human-readable format as part of the info gathering we do during cert testing. On 4.13 and older kernels, this script was run as a normal user with no error. On 4.15, this script dumps a python trace because /proc/modules now returns a null reference instead of just a blank memory offset. On 4.13 and older, when you read the file, you get something like this - (root and non-root shown) + (root and non-root shown): bladernr@galactica:~$ sudo cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0xc06b5000 bladernr@galactica:~$ cat /proc/modules |grep nls_iso8859 nls_iso8859_1 16384 1 - Live 0x Note that non-root reading returns a memory offset of 0x0 which is easily parsable. + + Now, on 4.15, this has changed: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xc0225000 ptp 20480 2 igb,e1000e, Live 0xc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null) Now, however, non-root reading returns a null reference which causes attempts to parse the offset to fail. I imagine this is probably by design, and it's a minor bug, but I wanted to raise it as it could cause issues when running userspace tools that parse /proc/modules on 4.15. ProblemTyp
[Kernel-packages] [Bug 1757218] [NEW] QCA9377 isn't being recognized sometimes
Public bug reported: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: New Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless netwo
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
Confirmed with systemd 229-4ubuntu21.2 that dev-nbd4p1.device is only "plugged", after client is running, and all symlinks and partitions exist. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757143] Re: /proc/modules has Null references causing python parsing issues
I'm going to go ahead and mark the kernel task as invalid as the workaround is to read /proc/modules as root. ** Merge proposal linked: https://code.launchpad.net/~bladernr/plainbox-provider-resource/+git/plainbox-provider-resource/+merge/341752 ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757143 Title: /proc/modules has Null references causing python parsing issues Status in linux package in Ubuntu: Invalid Status in plainbox-provider-checkbox package in Ubuntu: Fix Committed Bug description: EDIT: this originally looked like some sort of regression in the module_resource script of plainbox-provider-resource, however, on diving in a bit it seems the root cause is that /proc/modules in 4.15 is different than in previous kernels. This is a line from 4.15's /proc/modules data: e1000e 249856 0 - Live 0x (null) And this is the same module info from 4.13: e1000e 249856 0 - Live 0x That null character at the end appears to be causing the script to choke. For that reason, because /proc/modules has somehow changed to include null references (0xNULL is invalid, where 0x000 is parsable), I've added a kernel task to this bug. Original Summary: I ran into this issue (and came across some further glitches) while running canonical-certification-server on Ubuntu Server 18.04 on s390x (having 16.04 full selected in canonical-certification-server user interface): $ /usr/lib/plainbox-provider-resource-generic/bin/module_resource Traceback (most recent call last): File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 73, in sys.exit(main()) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 62, in main for module in modules: File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 57, in get_modules yield get_module(line) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
Yes, the latter attachments are from my laptop, which shows the same issue. Note that the issue happens on resume from screen standby, not resume from machine standby -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757166] Re: linux-aws: 4.15.0-1002.2 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.15.0-1002.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1757166 Title: linux-aws: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1757164 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1757166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.
I've got installed nvidia drivers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751887 Title: The brightness of the screen cannot be adjusted with either the buttons or the slider. Status in linux package in Ubuntu: Incomplete Bug description: Brightness is always at 100% and cannot be adjusted with either the FN brightness buttons or the Unity top bar slider. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: albertoinet 1199 F pulseaudio /dev/snd/controlC0: albertoinet 1199 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 20:49:16 2018 HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f InstallationDate: Installed on 2018-02-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Micro-Star International Co., Ltd. GT72VR 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1785IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-1785 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: GT dmi.product.name: GT72VR 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757143] Re: /proc/modules has Null references causing python parsing issues
After chatting with xnox on IRC, he discovered that the output of catting /proc/modules in 4.15 now depends on who is doing the catting. So `cat /proc/modules` as a normal user will return null references while `sudo cat /proc/modules` will return the actual memory offsets, accurately. For example: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xc0225000 ptp 20480 2 igb,e1000e, Live 0xc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null) So for the cert tooling, this should be a simple fix then, just to ensure that the module script runs as root. ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: Confirmed => Triaged ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: Triaged => In Progress ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: Fix Committed => 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/1757143 Title: /proc/modules has Null references causing python parsing issues Status in linux package in Ubuntu: Incomplete Status in plainbox-provider-checkbox package in Ubuntu: In Progress Bug description: EDIT: this originally looked like some sort of regression in the module_resource script of plainbox-provider-resource, however, on diving in a bit it seems the root cause is that /proc/modules in 4.15 is different than in previous kernels. This is a line from 4.15's /proc/modules data: e1000e 249856 0 - Live 0x (null) And this is the same module info from 4.13: e1000e 249856 0 - Live 0x That null character at the end appears to be causing the script to choke. For that reason, because /proc/modules has somehow changed to include null references (0xNULL is invalid, where 0x000 is parsable), I've added a kernel task to this bug. Original Summary: I ran into this issue (and came across some further glitches) while running canonical-certification-server on Ubuntu Server 18.04 on s390x (having 16.04 full selected in canonical-certification-server user interface): $ /usr/lib/plainbox-provider-resource-generic/bin/module_resource Traceback (most recent call last): File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 73, in sys.exit(main()) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 62, in main for module in modules: File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 57, in get_modules yield get_module(line) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757143] 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 1757143 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/1757143 Title: /proc/modules has Null references causing python parsing issues Status in linux package in Ubuntu: Incomplete Status in plainbox-provider-checkbox package in Ubuntu: In Progress Bug description: EDIT: this originally looked like some sort of regression in the module_resource script of plainbox-provider-resource, however, on diving in a bit it seems the root cause is that /proc/modules in 4.15 is different than in previous kernels. This is a line from 4.15's /proc/modules data: e1000e 249856 0 - Live 0x (null) And this is the same module info from 4.13: e1000e 249856 0 - Live 0x That null character at the end appears to be causing the script to choke. For that reason, because /proc/modules has somehow changed to include null references (0xNULL is invalid, where 0x000 is parsable), I've added a kernel task to this bug. Original Summary: I ran into this issue (and came across some further glitches) while running canonical-certification-server on Ubuntu Server 18.04 on s390x (having 16.04 full selected in canonical-certification-server user interface): $ /usr/lib/plainbox-provider-resource-generic/bin/module_resource Traceback (most recent call last): File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 73, in sys.exit(main()) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 62, in main for module in modules: File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 57, in get_modules yield get_module(line) File "/usr/lib/plainbox-provider-resource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757143] Re: Problem with plainbox-provider while running canonical-certification-server on 18.04 / s390x
So now I've got a dump of /proc/modules from 16.04.4 (4.13) and the issue is much more apparent: ubuntu@xwing:~$ cat /proc/modules nls_iso8859_1 16384 1 - Live 0x ppdev 20480 0 - Live 0x intel_rapl 20480 0 - Live 0x x86_pkg_temp_thermal 16384 0 - Live 0x intel_powerclamp 16384 0 - Live 0x coretemp 16384 0 - Live 0x kvm_intel 204800 0 - Live 0x joydev 20480 0 - Live 0x input_leds 16384 0 - Live 0x kvm 589824 1 kvm_intel, Live 0x irqbypass 16384 1 kvm, Live 0x intel_cstate 20480 0 - Live 0x intel_rapl_perf 16384 0 - Live 0x mei_me 40960 0 - Live 0x lpc_ich 24576 0 - Live 0x wmi_bmof 16384 0 - Live 0x mei 102400 1 mei_me, Live 0x ie31200_edac 16384 0 - Live 0x shpchp 36864 0 - Live 0x parport_pc 32768 0 - Live 0x parport 49152 2 ppdev,parport_pc, Live 0x mac_hid 16384 0 - Live 0x ib_iser 49152 0 - Live 0x rdma_cm 57344 1 ib_iser, Live 0x iw_cm 45056 1 rdma_cm, Live 0x ib_cm 49152 1 rdma_cm, Live 0x ib_core 217088 4 ib_iser,rdma_cm,iw_cm,ib_cm, Live 0x iscsi_tcp 20480 0 - Live 0x libiscsi_tcp 20480 1 iscsi_tcp, Live 0x libiscsi 53248 3 ib_iser,iscsi_tcp,libiscsi_tcp, Live 0x scsi_transport_iscsi 98304 4 ib_iser,iscsi_tcp,libiscsi, Live 0x autofs4 40960 2 - Live 0x btrfs 1101824 0 - Live 0x raid10 49152 0 - Live 0x raid456 143360 0 - Live 0x async_raid6_recov 20480 1 raid456, Live 0x async_memcpy 16384 2 raid456,async_raid6_recov, Live 0x async_pq 16384 2 raid456,async_raid6_recov, Live 0x async_xor 16384 3 raid456,async_raid6_recov,async_pq, Live 0x async_tx 16384 5 raid456,async_raid6_recov,async_memcpy,async_pq,async_xor, Live 0x xor 24576 2 btrfs,async_xor, Live 0x hid_generic 16384 0 - Live 0x hid_logitech_hidpp 32768 0 - Live 0x hid_logitech_dj 20480 0 - Live 0x usbhid 49152 0 - Live 0x hid 118784 4 hid_generic,hid_logitech_hidpp,hid_logitech_dj,usbhid, Live 0x raid6_pq 118784 4 btrfs,raid456,async_raid6_recov,async_pq, Live 0x libcrc32c 16384 1 raid456, Live 0x raid1 40960 0 - Live 0x raid0 20480 0 - Live 0x multipath 16384 0 - Live 0x linear 16384 0 - Live 0x i915 1830912 1 - Live 0x crct10dif_pclmul 16384 0 - Live 0x crc32_pclmul 16384 0 - Live 0x ghash_clmulni_intel 16384 0 - Live 0x pcbc 16384 0 - Live 0x aesni_intel 188416 0 - Live 0x drm_kms_helper 167936 1 i915, Live 0x aes_x86_64 20480 1 aesni_intel, Live 0x syscopyarea 16384 1 drm_kms_helper, Live 0x crypto_simd 16384 1 aesni_intel, Live 0x igb 217088 0 - Live 0x glue_helper 16384 1 aesni_intel, Live 0x cryptd 24576 3 ghash_clmulni_intel,aesni_intel,crypto_simd, Live 0x sysfillrect 16384 1 drm_kms_helper, Live 0x e1000e 249856 0 - Live 0x dca 16384 1 igb, Live 0x sysimgblt 16384 1 drm_kms_helper, Live 0x ahci 36864 0 - Live 0x i2c_algo_bit 16384 2 i915,igb, Live 0x fb_sys_fops 16384 1 drm_kms_helper, Live 0x libahci 32768 1 ahci, Live 0x drm 360448 3 i915,drm_kms_helper, Live 0x ptp 20480 2 igb,e1000e, Live 0x megaraid_sas 139264 2 - Live 0x pps_core 20480 1 ptp, Live 0x wmi 24576 1 wmi_bmof, Live 0x video 40960 1 i915, Live 0x ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Problem with plainbox-provider while running canonical-certification-server on 18.04 / s390x + /proc/modules has Null references causing python parsing issues ** Description changed: + EDIT: this originally looked like some sort of regression in the + module_resource script of plainbox-provider-resource, however, on diving + in a bit it seems the root cause is that /proc/modules in 4.15 is + different than in previous kernels. + + This is a line from 4.15's /proc/modules data: + e1000e 249856 0 - Live 0x (null) + + And this is the same module info from 4.13: + e1000e 249856 0 - Live 0x + + That null character at the end appears to be causing the script to
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
Guy, Broadcom has a new patch [1] that need to test. Here's the kernel [2] to try. [1] https://lkml.org/lkml/2018/3/20/35 [2] https://people.canonical.com/~khfeng/lp1447664-20180320/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447664 Title: 14e4:1687 broadcom tg3 network driver disconnects under high load Status in linux package in Ubuntu: Triaged Status in linux package in Debian: New Bug description: The tg3 broadcom network driver that binds with chipset 5762 goes offline and unable to recover (even with tg3 watchdog timeout) when network transmit is under high load. Call trace: https://launchpadlibrarian.net/204185480/dmesg When this happens, only a reboot would be able to fix it. Sometimes, however, bringing the interface offline and online (via ifconfig) would recover networking. I've also tested with the latest tg3 driver (dec 2014 version) and networking is still problematic. I have also disabled TSO, GSO etc... with ethtool and the bug still surfaces. This bug may be related to the integrated Firmware. Here is the procedure to replicate the issue because it is hard to replicate it under moderate network load. 1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a Ubuntu/Kubunu Live CD 14.04-15.04. 2. from another machine: start 5 sessions, repetitively copy (scp with public key authentication) a 70 meg file back and forth to the tg3 machine in each session. (not sure if this is necessary) 3. create a 1GB file on the tg3 machine, with something like dd if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000)) 4. from another machine: repetitively scp copy that 1GB file from the tg3 machine. This can be done with something like: while [ 0 ]; do scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp done; Networking will mostly goes offline in about 10-30 minutes. WORKAROUND: Add udev rule to make the changes permanent in /etc/udev/rules.d/80-tg3-fix.rules : ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu3748 F pulseaudio /dev/snd/controlC0: kubuntu3748 F pulseaudio CasperVersion: 1.360 Date: Thu Apr 23 11:16:24 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L06 v02.15 dmi.board.asset.tag: 2UA5041TG4 dmi.board.name: 2215 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA5041TG4 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP EliteDesk 705 G1 MT dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu) 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/1757191 Title: Intel NICs not properly reporting link speed in SysFS in Xenial Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: This was discovered during certification testing of 16.04.4 (I've now seen this behaviour at least 2 times) A system under test has a 2 port Intel X550 NIC (10Gb) Udev reports the NIC as this: Category: NETWORK Interface: enp94s0f0 Product: Ethernet Controller 10G X550T Vendor: Intel Corporation Driver: ixgbe (ver: 5.1.0-k) Path: /devices/pci:5d/:5d:00.0/:5e:00.0 ID: [8086:1563] Subsystem ID: [152d:8a13] Ethtool shows this info (this is for the second port, which has the issue) Settings for enp94s0f1: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 1Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes Note ethtool shows an active 10Gb link. The test tool determines the NIC speed by introspecting the sysfs data for each NIC port. In this case, by looking at /sys/class/net/DEVICENAME/speed I've now seen this on a couple different NICs using the ixgbe driver. The first port will properly show connected link speed in /sys/class/net/DEVICENAME/speed but the second port shows -1 in that file. Because of this, certification tests are failing because the tool believes that the link speed is incorrect. This current example is using kernel 4.13.0-37.42~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757164] Re: linux: 4.15.0-13.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757164 Title: linux: 4.15.0-13.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1757173 (linux-hwe-edge) derivatives: bug 1757165 (linux-raspi2), bug 1757166 (linux-aws), bug 1757167 (linux-azure), bug 1757168 (linux-gcp), bug 1757169 (linux-kvm) kernel-phase:Promoted to proposed kernel-phase-changed:Tuesday, 20. March 2018 16:02 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1757164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
This build failure occurs because of the following artful commit: commit 356852284931cda6749c41f77acefcb13bd534fe Author: Wanpeng Li Date: Thu Jan 4 01:57:52 2018 -0500 KVM: Fix stack-out-of-bounds read in write_mmio CVE-2017-17741 This redefines the kvm_mmio trace event as follows: TRACE_EVENT(kvm_mmio, - TP_PROTO(int type, int len, u64 gpa, u64 val), + TP_PROTO(int type, int len, u64 gpa, void *val), TP_ARGS(type, len, gpa, val), ..which is different from the lttng prototype in instrumentation/events /lttng-module/kvm.h: #if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,15,0) \ || LTTNG_KERNEL_RANGE(4,14,14, 4,15,0) \ || LTTNG_KERNEL_RANGE(4,9,77, 4,10,0) \ || LTTNG_KERNEL_RANGE(4,4,112, 4,5,0) \ || LTTNG_KERNEL_RANGE(3,16,52, 3,17,0) \ || LTTNG_KERNEL_RANGE(3,2,97, 3,3,0) \ || LTTNG_DEBIAN_KERNEL_RANGE(4,9,65,0,3,0, 4,10,0,0,0,0)) LTTNG_TRACEPOINT_EVENT(kvm_mmio, TP_PROTO(int type, int len, u64 gpa, void *val), TP_ARGS(type, len, gpa, val), TP_FIELDS( ctf_integer(u32, type, type) ctf_integer(u32, len, len) ctf_integer(u64, gpa, gpa) ctf_sequence_hex(unsigned char, val, val, u32, len) ) ) #else LTTNG_TRACEPOINT_EVENT(kvm_mmio, TP_PROTO(int type, int len, u64 gpa, u64 val), TP_ARGS(type, len, gpa, val), TP_FIELDS( ctf_integer(u32, type, type) ctf_integer(u32, len, len) ctf_integer(u64, gpa, gpa) ctf_integer(u64, val, val) ) ) Not sure how we #ifdef around this as the kernel version is 4.13 yet it now has a 4.15 API ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17741 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: In Progress Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757193] Re: Boot crash with Trusty 3.13
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757193 Title: Boot crash with Trusty 3.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: While doing kernel testing using the Trusty 3.13 code base, I get the following boot crash with QEMU: [0.338393] BUG: unable to handle kernel paging request at 014142f0 [0.338987] IP: [] 0x014142f0 [0.339388] PGD 180f067 PUD 0 [0.339388] Oops: 0010 [#1] SMP [0.339388] Modules linked in: [0.339388] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.11-ckt39-trusty #6 [0.339388] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [0.339388] task: 88003f708000 ti: 88003f6fa000 task.ti: 88003f6fa000 [0.339388] RIP: 0010:[] [] 0x014142f0 [0.339388] RSP: :88003f6fbe98 EFLAGS: 00050246 [0.339388] RAX: RBX: RCX: [0.339388] RDX: RSI: 88003deb9eb4 RDI: 818b8590 [0.339388] RBP: 88003f6fbe98 R08: R09: 88003fa14ae0 [0.339388] R10: 81264c68 R11: eafdd000 R12: 818b8590 [0.339388] R13: 00ad R14: R15: [0.339388] FS: () GS:88003fa0() knlGS: [0.339388] CS: 0010 DS: ES: CR0: 80050033 [0.339388] CR2: 014142f0 CR3: 0180c000 CR4: 00360770 [0.339388] DR0: DR1: DR2: [0.339388] DR3: DR6: fffe0ff0 DR7: 0400 [0.339388] Stack: [0.339388] 88003f6fbf08 81000402 88003f6fbf00 81065f88 [0.339388] 88003f6fbef0 88003ffd96a1 817e9d28 00ad00060006 [0.339388] 817b013d 8196cef0 8196d018 0006 [0.339388] Call Trace: [0.339388] [] do_one_initcall+0xf2/0x140 [0.339388] [] ? parse_args+0x1e8/0x320 [0.339388] [] kernel_init_freeable+0x14c/0x1d1 [0.339388] [] ? do_early_param+0x88/0x88 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] [] kernel_init+0x9/0x120 [0.339388] [] ret_from_fork+0x6e/0xa0 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] Code: Bad RIP value. [0.339388] RIP [] 0x014142f0 [0.339388] RSP [0.339388] CR2: 014142f0 [0.339388] ---[ end trace a71242bdac7e8632 ]--- [0.339388] note: swapper/0[1] exited with preempt_count 1 [0.357079] swapper/0 (1) used greatest stack depth: 5424 bytes left [0.357539] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [0.357539] [0.358073] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) Git bisect identified the following commit as the culprit: commit 56764fdc3a847371531b8044155c70412fc5be76 Author: Andy Whitcroft Date: Thu Feb 22 11:24:00 2018 +0100 UBUNTU: SAUCE: x86, extable: fix uaccess fixup detection BugLink: http://bugs.launchpad.net/bugs/1750786 The existing code intends to identify a subset of fixups which need special handling, uaccess related faults need to record the failure. This is done by adjusting the fixup code pointer by a (random) constant 0x7ff0. This is detected in fixup_exception by comparing the two pointers. The intent of this code is to detect the the delta between the original code and its fixup code being greater than the constant. However, the code as written triggers undefined comparison behaviour. In this kernel this prevents the condition triggering, leading to panics when jumping to the corrupted fixup address. Convert the code to better implement the intent. Convert both of the offsets to final addresses and compare the delta between those. Also add a massive comment to explain all of this including the implicit assumptions on order of the segments that this comparison implies. Fixes: 706276543b69 ("x86, extable: Switch to relative exception table entries") Signed-off-by: Andy Whitcroft Acked-by: Colin Ian King Acked-by: Khalid Elmously Signed-off-by: Kleber Sacilo
[Kernel-packages] [Bug 1757193] 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 1757193 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757193 Title: Boot crash with Trusty 3.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: While doing kernel testing using the Trusty 3.13 code base, I get the following boot crash with QEMU: [0.338393] BUG: unable to handle kernel paging request at 014142f0 [0.338987] IP: [] 0x014142f0 [0.339388] PGD 180f067 PUD 0 [0.339388] Oops: 0010 [#1] SMP [0.339388] Modules linked in: [0.339388] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.11-ckt39-trusty #6 [0.339388] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [0.339388] task: 88003f708000 ti: 88003f6fa000 task.ti: 88003f6fa000 [0.339388] RIP: 0010:[] [] 0x014142f0 [0.339388] RSP: :88003f6fbe98 EFLAGS: 00050246 [0.339388] RAX: RBX: RCX: [0.339388] RDX: RSI: 88003deb9eb4 RDI: 818b8590 [0.339388] RBP: 88003f6fbe98 R08: R09: 88003fa14ae0 [0.339388] R10: 81264c68 R11: eafdd000 R12: 818b8590 [0.339388] R13: 00ad R14: R15: [0.339388] FS: () GS:88003fa0() knlGS: [0.339388] CS: 0010 DS: ES: CR0: 80050033 [0.339388] CR2: 014142f0 CR3: 0180c000 CR4: 00360770 [0.339388] DR0: DR1: DR2: [0.339388] DR3: DR6: fffe0ff0 DR7: 0400 [0.339388] Stack: [0.339388] 88003f6fbf08 81000402 88003f6fbf00 81065f88 [0.339388] 88003f6fbef0 88003ffd96a1 817e9d28 00ad00060006 [0.339388] 817b013d 8196cef0 8196d018 0006 [0.339388] Call Trace: [0.339388] [] do_one_initcall+0xf2/0x140 [0.339388] [] ? parse_args+0x1e8/0x320 [0.339388] [] kernel_init_freeable+0x14c/0x1d1 [0.339388] [] ? do_early_param+0x88/0x88 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] [] kernel_init+0x9/0x120 [0.339388] [] ret_from_fork+0x6e/0xa0 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] Code: Bad RIP value. [0.339388] RIP [] 0x014142f0 [0.339388] RSP [0.339388] CR2: 014142f0 [0.339388] ---[ end trace a71242bdac7e8632 ]--- [0.339388] note: swapper/0[1] exited with preempt_count 1 [0.357079] swapper/0 (1) used greatest stack depth: 5424 bytes left [0.357539] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [0.357539] [0.358073] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) Git bisect identified the following commit as the culprit: commit 56764fdc3a847371531b8044155c70412fc5be76 Author: Andy Whitcroft Date: Thu Feb 22 11:24:00 2018 +0100 UBUNTU: SAUCE: x86, extable: fix uaccess fixup detection BugLink: http://bugs.launchpad.net/bugs/1750786 The existing code intends to identify a subset of fixups which need special handling, uaccess related faults need to record the failure. This is done by adjusting the fixup code pointer by a (random) constant 0x7ff0. This is detected in fixup_exception by comparing the two pointers. The intent of this code is to detect the the delta between the original code and its fixup code being greater than the constant. However, the code as written triggers undefined comparison behaviour. In this kernel this prevents the condition triggering, leading to panics when jumping to the corrupted fixup address. Convert the code to better implement the intent. Convert both of the offsets to final addresses and compare the delta between those. Also add a massive comment to explain all of this including the implicit assumptions on order of
Re: [Kernel-packages] [Bug 1757062] Re: [Apple Inc. MacBook4, 1] hibernate/resume failure [non-free: wl]
The issue started after upgrading from 17.10 to 18.04. The computer also have a terrible lag during boot, increasing the boot time till 5 minutes, it seems that it depends by graphic card driver (intel gma950) not working. 2018-03-20 17:07 GMT+01:00 Joseph Salisbury : > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.16 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc6 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1757062 > > Title: > [Apple Inc. MacBook4,1] hibernate/resume failure [non-free: wl] > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > The computer is very slow during bootup > > ProblemType: KernelOops > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-12-generic 4.15.0-12.13 > ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 > Uname: Linux 4.15.0-12-generic x86_64 > NonfreeKernelModules: wl > Annotation: This occurred during a previous hibernation, and prevented > the system from resuming properly. > ApportVersion: 2.20.8-0ubuntu10 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: cristian 6302 F pulseaudio > Date: Tue Mar 20 07:41:27 2018 > DuplicateSignature: hibernate/resume:Apple Inc. > MacBook4,1:MB41.88Z.00C1.B00.0802091535 > ExecutablePath: /usr/share/apport/apportcheckresume > Failure: hibernate/resume > HibernationDevice: RESUME=UUID=8d16b38f-7434-4b43-a54e-c59b16695944 > InstallationDate: Installed on 2016-12-25 (449 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > InterpreterPath: /usr/bin/python3.6 > MachineType: Apple Inc. MacBook4,1 > ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume > ProcEnviron: >PATH=(custom, no user) >LANG=it_IT.UTF-8 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic > root=UUID=9c2b8ddb-ddb0-450d-961c-854c607ab0d2 ro quiet splash > vt.handoff=1 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, > 3.6.4-1 > PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, > 2.7.14-4 > RelatedPackageVersions: >linux-restricted-modules-4.15.0-12-generic N/A >linux-backports-modules-4.15.0-12-generic N/A >linux-firmware 1.173 > SourcePackage: linux > Title: [Apple Inc. MacBook4,1] hibernate/resume failure [non-free: wl] > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > dmi.bios.date: 02/09/08 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: MB41.88Z.00C1.B00.0802091535 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: Mac-F22788A9 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-F22788A9 > dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/ > 08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac- > F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: > dmi.product.family: MacBook > dmi.product.name: MacBook4,1 > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1757062/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757062 Title: [Apple Inc. MacBook4,1] hibernate/resume failure [non-free: wl] Status in linux package in Ubuntu: Incomplete Bug description: The computer is very slow during bootup ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: wl Annotation: This occurred during a previous hibernation, and prevented the system from resumi
[Kernel-packages] [Bug 1757169] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) -- 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/1757169 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1757164 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1757169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
I tried some more: 4.10 rc3 does have the patch: ubuntu@ubu-vm-01:~$ uname -a Linux ubu-vm-01 4.10.0-041000rc3-generic #201701081831 SMP Mon Jan 9 00:34:16 UTC 2017 s390x s390x s390x GNU/Linux ubuntu@ubu-vm-01:~$ kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm INFO: For more detailed results, you should run this as root HINT: sudo /usr/sbin/kvm-ok ubuntu@ubu-vm-01:~$ ls -la /dev/kvm ls: cannot access '/dev/kvm': No such file or directory 4.10-rc2 seems to be the last one without: ubuntu@ubu-vm-01:~$ uname -a Linux ubu-vm-01 4.10.0-041000rc2-generic #201701011831 SMP Mon Jan 2 00:41:33 UTC 2017 s390x s390x s390x GNU/Linux ubuntu@ubu-vm-01:~$ kvm-ok INFO: /dev/kvm exists KVM acceleration can be used ubuntu@ubu-vm-01:~$ ls -la /dev/kvm crw--- 1 root root 10, 232 Mar 20 07:41 /dev/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/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Have you ever seen error message that says the nvme device stays in D3 and refused to change to D0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-gener
[Kernel-packages] [Bug 1757193] Re: Boot crash with Trusty 3.13
The upstream commit that fixes 706276543b69 ("x86, extable: Switch to relative exception table entries") (which the problematic commit tries to do as well) is: ommit 548acf19234dbda5a52d5a8e7e205af46e9da840 Author: Tony Luck Date: Wed Feb 17 10:20:12 2016 -0800 x86/mm: Expand the exception table logic to allow new handling options Huge amounts of help from Andy Lutomirski and Borislav Petkov to produce this. Andy provided the inspiration to add classes to the exception table with a clever bit-squeezing trick, Boris pointed out how much cleaner it would all be if we just had a new field. Linus Torvalds blessed the expansion with: ' I'd rather not be clever in order to save just a tiny amount of space in the exception table, which isn't really criticial for anybody. ' The third field is another relative function pointer, this one to a handler that executes the actions. We start out with three handlers: 1: Legacy - just jumps the to fixup IP 2: Fault - provide the trap number in %ax to the fixup code 3: Cleaned up legacy for the uaccess error hack Signed-off-by: Tony Luck Reviewed-by: Borislav Petkov Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Link: http://lkml.kernel.org/r/f6af78fcbd348cf4939875cfda9c19689b5e50b8.1455732970.git.tony.l...@intel.com Signed-off-by: Ingo Molnar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757193 Title: Boot crash with Trusty 3.13 Status in linux package in Ubuntu: New Bug description: While doing kernel testing using the Trusty 3.13 code base, I get the following boot crash with QEMU: [0.338393] BUG: unable to handle kernel paging request at 014142f0 [0.338987] IP: [] 0x014142f0 [0.339388] PGD 180f067 PUD 0 [0.339388] Oops: 0010 [#1] SMP [0.339388] Modules linked in: [0.339388] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.11-ckt39-trusty #6 [0.339388] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [0.339388] task: 88003f708000 ti: 88003f6fa000 task.ti: 88003f6fa000 [0.339388] RIP: 0010:[] [] 0x014142f0 [0.339388] RSP: :88003f6fbe98 EFLAGS: 00050246 [0.339388] RAX: RBX: RCX: [0.339388] RDX: RSI: 88003deb9eb4 RDI: 818b8590 [0.339388] RBP: 88003f6fbe98 R08: R09: 88003fa14ae0 [0.339388] R10: 81264c68 R11: eafdd000 R12: 818b8590 [0.339388] R13: 00ad R14: R15: [0.339388] FS: () GS:88003fa0() knlGS: [0.339388] CS: 0010 DS: ES: CR0: 80050033 [0.339388] CR2: 014142f0 CR3: 0180c000 CR4: 00360770 [0.339388] DR0: DR1: DR2: [0.339388] DR3: DR6: fffe0ff0 DR7: 0400 [0.339388] Stack: [0.339388] 88003f6fbf08 81000402 88003f6fbf00 81065f88 [0.339388] 88003f6fbef0 88003ffd96a1 817e9d28 00ad00060006 [0.339388] 817b013d 8196cef0 8196d018 0006 [0.339388] Call Trace: [0.339388] [] do_one_initcall+0xf2/0x140 [0.339388] [] ? parse_args+0x1e8/0x320 [0.339388] [] kernel_init_freeable+0x14c/0x1d1 [0.339388] [] ? do_early_param+0x88/0x88 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] [] kernel_init+0x9/0x120 [0.339388] [] ret_from_fork+0x6e/0xa0 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] Code: Bad RIP value. [0.339388] RIP [] 0x014142f0 [0.339388] RSP [0.339388] CR2: 014142f0 [0.339388] ---[ end trace a71242bdac7e8632 ]--- [0.339388] note: swapper/0[1] exited with preempt_count 1 [0.357079] swapper/0 (1) used greatest stack depth: 5424 bytes left [0.357539] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [0.357539] [0.358073] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) Git bisect identified the following commit as the culprit: commit 56764fdc3a847371531b8044155c70412fc5be76 Author: Andy Whitcroft Date: Thu Feb 22 11:24:00 2018 +0100 UBUNTU: SAUCE: x86, extable: fix uaccess fixup detection BugLink: http://bugs.launchpad.net/bugs/1750786 The existing code intends to identify a subset of fixups which need special handling, uaccess related faults need to record the failure. This i
[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757191 Title: Intel NICs not properly reporting link speed in SysFS in Xenial Status in linux package in Ubuntu: New Bug description: This was discovered during certification testing of 16.04.4 (I've now seen this behaviour at least 2 times) A system under test has a 2 port Intel X550 NIC (10Gb) Udev reports the NIC as this: Category: NETWORK Interface: enp94s0f0 Product: Ethernet Controller 10G X550T Vendor: Intel Corporation Driver: ixgbe (ver: 5.1.0-k) Path: /devices/pci:5d/:5d:00.0/:5e:00.0 ID: [8086:1563] Subsystem ID: [152d:8a13] Ethtool shows this info (this is for the second port, which has the issue) Settings for enp94s0f1: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 100baseT/Full 1000baseT/Full 1baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 1Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: umbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes Note ethtool shows an active 10Gb link. The test tool determines the NIC speed by introspecting the sysfs data for each NIC port. In this case, by looking at /sys/class/net/DEVICENAME/speed I've now seen this on a couple different NICs using the ixgbe driver. The first port will properly show connected link speed in /sys/class/net/DEVICENAME/speed but the second port shows -1 in that file. Because of this, certification tests are failing because the tool believes that the link speed is incorrect. This current example is using kernel 4.13.0-37.42~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp