[Kernel-packages] [Bug 1708852] Re: Touchpad not detected
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708852 Title: Touchpad not detected Status in linux package in Ubuntu: Fix Released Bug description: SRU Justifications: [Impact] Touchpad on Lenovo ideapad 320-14IKB does not work. [Test Case] After adding the ID to the elan_i2c driver, the touchpad works. [Regression Potential] Very low. It only adds device ID to the driver, no functional changes. --- The touchpad is not working in any linux distribution, but works in Windows. It is not getting detected. Seems like a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matheus1504 F pulseaudio CurrentDesktop: GNOME Date: Sat Aug 5 12:58:21 2017 InstallationDate: Installed on 2017-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:1127 Acer, Inc Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 0101:0007 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-30-generic N/A linux-backports-modules-4.10.0-30-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 4A 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 320-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB: dmi.product.name: 80YF dmi.product.version: Lenovo ideapad 320-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696049] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2017-09-06 01:38 EDT--- (In reply to comment #23) > Can you test the following two kernels next: > > 4.12-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/ > 4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/ Fails with 4.12-rc1 and passes with 4.13-rc1. Thanks, Harish. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712249] Re: [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning / failure
This bug was found by Red Hat and fixed/code upstreamed by Jeff Moyer
from Red Hat. This is being added to Canonical for Ubuntu to pick up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1712249
Title:
[Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning /
failure
Status in intel:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Bug description:
Fix warnings of the form...
WARNING: CPU: 10 PID: 4983 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
sysfs: cannot create duplicate filename '/class/dax/dax12.0'
Call Trace:
dump_stack+0x63/0x86
__warn+0xcb/0xf0
warn_slowpath_fmt+0x5a/0x80
? kernfs_path_from_node+0x4f/0x60
sysfs_warn_dup+0x62/0x80
sysfs_do_create_link_sd.isra.2+0x97/0xb0
sysfs_create_link+0x25/0x40
device_add+0x266/0x630
devm_create_dax_dev+0x2cf/0x340 [dax]
dax_pmem_probe+0x1f5/0x26e [dax_pmem]
nvdimm_bus_probe+0x71/0x120
...by reusing the namespace id for the device-dax instance name.
Now that we have decided that there will never by more than one
device-dax instance per libnvdimm-namespace parent device [1], we can
directly reuse the namepace ids. There are some possible follow-on
cleanups, but those are saved for a later patch to simplify the -stable
backport.
[1]: https://lists.01.org/pipermail/linux-nvdimm/2016-December/008266.html
Fixes: 98a29c39dc68 ("libnvdimm, namespace: allow creation of multiple
pmem...")
Cc: Jeff Moyer
Cc:
Reported-by: Dariusz Dokupil
Signed-off-by: Dan Williams
Target Release: 17.10
Target Kernel: 4.13
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1712249/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715051] Re: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'h
I ran those scripts in terminal got the following yash@yash-MS-7592:~$ sudo apt-get install -f [sudo] password for yash: Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: snap-confine Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 55 not upgraded. 2 not fully installed or removed. Need to get 0 B/836 kB of archives. After this operation, 0 B of additional disk space will be used. dpkg: error processing package linux-libc-dev:amd64 (--configure): package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') dpkg: dependency problems prevent configuration of libc6-dev:amd64: libc6-dev:amd64 depends on linux-libc-dev; however: Package linux-libc-dev:amd64 is not installed. dpkg: error processing package libc6-dev:amd64 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: linux-libc-dev:amd64 libc6-dev:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) yash@yash-MS-7592:~$ sudo apt-get clean yash@yash-MS-7592:~$ sudo apt-get update Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://in.archive.ubuntu.com/ubuntu xenial InRelease Hit:3 http://in.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:4 http://in.archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done yash@yash-MS-7592:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: snap-confine Use 'sudo apt autoremove' to remove it. The following packages have been kept back: gnome-software gnome-software-common libegl1-mesa libgbm1 libgl1-mesa-dri libinput10 libmirclient9 libwayland-egl1-mesa python3-software-properties python3-update-manager software-properties-common software-properties-gtk ubuntu-software update-manager update-manager-core update-notifier update-notifier-common xserver-xorg-core-hwe-16.04 xserver-xorg-hwe-16.04 xserver-xorg-input-evdev-hwe-16.04 xserver-xorg-input-synaptics-hwe-16.04 xserver-xorg-input-wacom-hwe-16.04 xserver-xorg-video-amdgpu-hwe-16.04 xserver-xorg-video-ati-hwe-16.04 xserver-xorg-video-fbdev-hwe-16.04 xserver-xorg-video-intel-hwe-16.04 xserver-xorg-video-nouveau-hwe-16.04 xserver-xorg-video-qxl-hwe-16.04 xserver-xorg-video-radeon-hwe-16.04 xserver-xorg-video-vesa-hwe-16.04 xserver-xorg-video-vmware-hwe-16.04 The following packages will be upgraded: cups cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common gir1.2-packagekitglib-1.0 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libpackagekit-glib2-16 libsmbclient libsnapd-glib1 libwbclient0 linux-firmware samba-libs snap-confine snapd snapd-login-service ubuntu-core-launcher 24 upgraded, 0 newly installed, 0 to remove and 31 not upgraded. 2 not fully installed or removed. Need to get 57.4 MB of archives. After this operation, 5,389 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-libc-dev amd64 4.4.0-93.116 [836 kB] Get:2 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libcupsppdc1 amd64 2.1.3-4ubuntu0.3 [44.9 kB] Get:3 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libcupsmime1 amd64 2.1.3-4ubuntu0.3 [13.0 kB] Get:4 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libcupsimage2 amd64 2.1.3-4ubuntu0.3 [16.1 kB] Get:5 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libcupscgi1 amd64 2.1.3-4ubuntu0.3 [27.1 kB] Get:6 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-core-drivers amd64 2.1.3-4ubuntu0.3 [27.2 kB] Get:7 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-server-common all 2.1.3-4ubuntu0.3 [493 kB] Get:8 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-common all 2.1.3-4ubuntu0.3 [134 kB] Get:9 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-ppdc amd64 2.1.3-4ubuntu0.3 [26.7 kB] Get:10 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-daemon amd64 2.1.3-4ubuntu0.3 [302 kB] Get:11 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-bsd amd64 2.1.3-4ubuntu0.3 [34.8 kB] Get:12 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups-client amd64 2.1.3-4ubuntu0.3 [133 kB] Get:13 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libcups2 amd64 2.1.3-4ubuntu0.3 [197 kB] Get:14 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 cups
[Kernel-packages] [Bug 1572132] Re: SMB driver (SMBv2) does not show all files when mounting a windows top level share
[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/1572132
Title:
SMB driver (SMBv2) does not show all files when mounting a windows top
level share
Status in linux package in Ubuntu:
Expired
Bug description:
When using the SMBv2 Protocol to mount a top level windows share (such
as C:\) not all files (or directories) are shown that exist on the
server side. Exactly 2 files are always missing...
Steps to reproduce:
On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top
level share - a subfolder like C:\data\ seems to work)
sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0
As a result always 2 Files (or directories) are missing in the mounted
directory of the ubuntu installation.
Seems to be a kernel bug (source tree: linux/fs/cifs).
The ubuntu versions I have checked:
Ubuntu 14.04LTS amd64
Ubuntu 15.10 amd64
Ubuntu 16.04 amd64
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Apr 19 14:50:02 2016
InstallationDate: Installed on 2016-04-19 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
I have the same issue on an MSI GS70 running kernel 4.10.0-33. BUT I found a pretty easy workaround: If I turn off wifi in NetworkManager, not only does it always suspend successfully, it suspends very quickly. Thought maybe this would be helpful for others. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. Update 2: I just encountered this issue with Kernel 4.9. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work
A quick google [1] says: "SD card reader has been not work for a long time, after I upgrade to macOS Sierra version 10.12.6 , it works now :P." [1] https://github.com/coldnew/macbookpro-2015-config -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620422 Title: Macbook Pro Retina 12,1 SD Card Reader Doesn't Work Status in linux package in Ubuntu: Expired Bug description: SD card reader doesn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graingert 2672 F pulseaudio /dev/snd/controlC1: graingert 2672 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 6 00:39:03 2016 InstallationDate: Installed on 2016-01-05 (244 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-9136-generic N/A linux-backports-modules-4.4.0-9136-generic N/A linux-firmware 1.160 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago) dmi.bios.date: 10/26/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B15.1510261437 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,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/1620422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714783] Re: *beta 1 release* screen scrambling upon startup.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714783 Title: *beta 1 release* screen scrambling upon startup. Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-01 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Tags: artful Uname: Linux 4.12.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714783] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1714783/+attachment/4945117/+files/JournalErrors.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/1714783 Title: *beta 1 release* screen scrambling upon startup. Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-01 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Tags: artful Uname: Linux 4.12.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714783] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1714783/+attachment/4945118/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714783 Title: *beta 1 release* screen scrambling upon startup. Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-01 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Tags: artful Uname: Linux 4.12.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714783] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1714783/+attachment/4945116/+files/GsettingsChanges.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/1714783 Title: *beta 1 release* screen scrambling upon startup. Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-01 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Tags: artful Uname: Linux 4.12.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714783] Re: *beta 1 release* screen scrambling upon startup.
apport information ** Tags added: apport-collected ** Description changed: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.7-0ubuntu1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-09-01 (4 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) + Package: linux + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 + Tags: artful + Uname: Linux 4.12.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1714783/+attachment/4945115/+files/Dependencies.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/1714783 Title: *beta 1 release* screen scrambling upon startup. Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This issue just happened with this beta 1 release. This was during a cold startup. I'll retry a cold startup after this to see if the problem is replicated and then I'll make comments in regards to that investigation. I'm including a pic of what happened. I apologize for the flash, it's automatic on my phone. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 07:12:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-01 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-01 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Tags: artful Uname: Linux 4.12.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715279] Re: 2.6.32 netfliter . nf_conntrack . destroy_conntrack BUG
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715279 Title: 2.6.32 netfliter . nf_conntrack . destroy_conntrack BUG Status in linux package in Ubuntu: Confirmed Bug description: In my server ,i got a BUG，and i can initially locate where this bug is : nf_conntrack_in-> resolve_normal_ct -> nf_conntrack_find_get -> unlikely(!nf_ct_tuple_equal(tuple, &h->tuple)) -> nf_ct_put -> destroy_conntrack -> nf_ct_is_confirmed -> BUG_ON but I don't know why this happens，please help me ,THANK YOU! 4>[ cut here ] 15381 <2>kernel BUG at net/netfilter/nf_conntrack_core.c:206! 15382 <4>invalid opcode: [#1] SMP 15383 <4>last sysfs file: /sys/devices/system/cpu/cpu47/topology/thread_siblings_list 15384 <4>CPU 0 15385 <4>Modules linked in: nbd(U) iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables ksl b_ctk(U) fuse tcp_diag inet_diag xfs exportfs kvm_intel kvm vhost_net macvtap macvlan cdc_ether usbnet mii tun openvswitch(U) libcrc32c b onding 8021q garp stp llc toa hookers ipv6 power_meter iTCO_wdt iTCO_vendor_support dcdbas ipmi_devintf lpc_ich mfd_core shpchp igb i2c_a lgo_bit i2c_core ixgbe dca ptp pps_core mdio sg ext4 jbd2 mbcache sd_mod crc_t10dif ahci megaraid_sas wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: nbd] 15386 <4> 15387 <4>Pid: 25449, comm: mebs-nbd-core Tainted: G --- H 2.6.32-431.20.3.el6.mt20161028.x86_64 #1 Dell Inc. PowerEdge R 730/0WCJNT 15388 <4>RIP: 0010:[] [] destroy_conntrack+0x11c/0x150 [nf_conntrack] 15389 <4>RSP: 0018:881d10cd99f8 EFLAGS: 00010246 15390 troy_conntrack+0x11c/0x1RAX: RBX: 8813d96dbdc8 RCX: 0001 15391 <4>RDX: b4be RSI: 0006 RDI: 8813d96dbdc8 15392 <4>RBP: 881d10cd9a08 R08: 0002 R09: 00c0 15393 <4>R10: R11: R12: 81b18540 15394 <4>R13: 0003 R14: 0002 R15: 0002 15395 <4>FS: 7f45d2ba1720() GS:88011f60() knlGS: 15396 <4>CS: 0010 DS: ES: CR0: 8005003b 15397 <4>CR2: CR3: 001f0aa3f000 CR4: 001427e0 15398 <4>DR0: DR1: DR2: 15399 <4>DR3: DR6: fffe0ff0 DR7: 0400 15400 <4>Process mebs-nbd-core (pid: 25449, threadinfo 881d10cd8000, task 881f0a9b6aa0) 15401 <4>Stack: 15402 <4> 881d10cd9ab8 81b18540 881d10cd9a18 8148a4c7 15403 <4> 881d10cd9a38 a029bac5 881c47af1b68 81b18540 15404 <4> 881d10cd9b18 a029bdd0 a026d620 a02a7080 15405 <4>Call Trace: 15406 <4> [] nf_conntrack_destroy+0x17/0x30 15407 <4> [] nf_conntrack_find_get+0x85/0x120 [nf_conntrack] 15408 <4> [] nf_conntrack_in+0x270/0xa00 [nf_conntrack] 15409 <4> [] ? ovs_dp_process_received_packet+0x51/0x80 [openvswitch] 15410 <4> [] ipv4_conntrack_local+0x51/0x60 [nf_conntrack_ipv4] 15411 <4> [] nf_iterate+0x69/0xb0 15412 <4> [] ? dst_output+0x0/0x20 15413 <4> [] nf_hook_slow+0x76/0x120 15414 <4> [] ? dst_output+0x0/0x20 15415 <4> [] __ip_local_out+0x9f/0xb0 15416 <4> [] ip_local_out+0x16/0x30 15417 <4> [] ip_queue_xmit+0x190/0x420 15418 <4> [] ? ip_output+0xb8/0xc0 15419 <4> [] tcp_transmit_skb+0x40e/0x7b0 15420 <4> [] tcp_write_xmit+0x230/0xa90 15421 troy_conntrack+0x11c/0x150 [] __tcp_push_pending_frames+0x30/0xe0 15422 <4> [] tcp_send_fin+0x72/0x1d0 15423 <4> [] tcp_close+0x346/0x450 15424 <4> [] inet_release+0x67/0x90 15425 <4> [] sock_release+0x29/0x90 15426 <4> [] sock_close+0x17/0x30 15427 <4> [] __fput+0xf5/0x210 15428 <4> [] fput+0x25/0x30 15429 <4> [] filp_close+0x5d/0x90 15430 <4> [] sys_close+0xa5/0x100 15431 <4> [] system_call_fastpath+0x16/0x1b 15432 <4>Code: 1b ec 1e e1 eb ce f6 05 9c fa d3 e1 20 74 ce 80 3d a0 ad 00 00 00 74 c5 48 89 de 48 c7 c7 00 32 2a a0 31 c0 e8 ca cc 28 e1 eb b2 <0f> 0b eb fe f6 05 73 fa d3 e1 20 0f 84 f6 fe ff ff 80 3d 9b ad 15433 <1>RIP [] destroy_conntrack+0x11c/0x150 [nf_conntrack] 15434 <4> RSP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715279] 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 1715279 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/1715279 Title: 2.6.32 netfliter . nf_conntrack . destroy_conntrack BUG Status in linux package in Ubuntu: Incomplete Bug description: In my server ,i got a BUG，and i can initially locate where this bug is : nf_conntrack_in-> resolve_normal_ct -> nf_conntrack_find_get -> unlikely(!nf_ct_tuple_equal(tuple, &h->tuple)) -> nf_ct_put -> destroy_conntrack -> nf_ct_is_confirmed -> BUG_ON but I don't know why this happens，please help me ,THANK YOU! 4>[ cut here ] 15381 <2>kernel BUG at net/netfilter/nf_conntrack_core.c:206! 15382 <4>invalid opcode: [#1] SMP 15383 <4>last sysfs file: /sys/devices/system/cpu/cpu47/topology/thread_siblings_list 15384 <4>CPU 0 15385 <4>Modules linked in: nbd(U) iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables ksl b_ctk(U) fuse tcp_diag inet_diag xfs exportfs kvm_intel kvm vhost_net macvtap macvlan cdc_ether usbnet mii tun openvswitch(U) libcrc32c b onding 8021q garp stp llc toa hookers ipv6 power_meter iTCO_wdt iTCO_vendor_support dcdbas ipmi_devintf lpc_ich mfd_core shpchp igb i2c_a lgo_bit i2c_core ixgbe dca ptp pps_core mdio sg ext4 jbd2 mbcache sd_mod crc_t10dif ahci megaraid_sas wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: nbd] 15386 <4> 15387 <4>Pid: 25449, comm: mebs-nbd-core Tainted: G --- H 2.6.32-431.20.3.el6.mt20161028.x86_64 #1 Dell Inc. PowerEdge R 730/0WCJNT 15388 <4>RIP: 0010:[] [] destroy_conntrack+0x11c/0x150 [nf_conntrack] 15389 <4>RSP: 0018:881d10cd99f8 EFLAGS: 00010246 15390 troy_conntrack+0x11c/0x1RAX: RBX: 8813d96dbdc8 RCX: 0001 15391 <4>RDX: b4be RSI: 0006 RDI: 8813d96dbdc8 15392 <4>RBP: 881d10cd9a08 R08: 0002 R09: 00c0 15393 <4>R10: R11: R12: 81b18540 15394 <4>R13: 0003 R14: 0002 R15: 0002 15395 <4>FS: 7f45d2ba1720() GS:88011f60() knlGS: 15396 <4>CS: 0010 DS: ES: CR0: 8005003b 15397 <4>CR2: CR3: 001f0aa3f000 CR4: 001427e0 15398 <4>DR0: DR1: DR2: 15399 <4>DR3: DR6: fffe0ff0 DR7: 0400 15400 <4>Process mebs-nbd-core (pid: 25449, threadinfo 881d10cd8000, task 881f0a9b6aa0) 15401 <4>Stack: 15402 <4> 881d10cd9ab8 81b18540 881d10cd9a18 8148a4c7 15403 <4> 881d10cd9a38 a029bac5 881c47af1b68 81b18540 15404 <4> 881d10cd9b18 a029bdd0 a026d620 a02a7080 15405 <4>Call Trace: 15406 <4> [] nf_conntrack_destroy+0x17/0x30 15407 <4> [] nf_conntrack_find_get+0x85/0x120 [nf_conntrack] 15408 <4> [] nf_conntrack_in+0x270/0xa00 [nf_conntrack] 15409 <4> [] ? ovs_dp_process_received_packet+0x51/0x80 [openvswitch] 15410 <4> [] ipv4_conntrack_local+0x51/0x60 [nf_conntrack_ipv4] 15411 <4> [] nf_iterate+0x69/0xb0 15412 <4> [] ? dst_output+0x0/0x20 15413 <4> [] nf_hook_slow+0x76/0x120 15414 <4> [] ? dst_output+0x0/0x20 15415 <4> [] __ip_local_out+0x9f/0xb0 15416 <4> [] ip_local_out+0x16/0x30 15417 <4> [] ip_queue_xmit+0x190/0x420 15418 <4> [] ? ip_output+0xb8/0xc0 15419 <4> [] tcp_transmit_skb+0x40e/0x7b0 15420 <4> [] tcp_write_xmit+0x230/0xa90 15421 troy_conntrack+0x11c/0x150 [] __tcp_push_pending_frames+0x30/0xe0 15422 <4> [] tcp_send_fin+0x72/0x1d0 15423 <4> [] tcp_close+0x346/0x450 15424 <4> [] inet_release+0x67/0x90 15425 <4> [] sock_release+0x29/0x90 15426 <4> [] sock_close+0x17/0x30 15427 <4> [] __fput+0xf5/0x210 15428 <4> [] fput+0x25/0x30 15429 <4> [] filp_close+0x5d/0x90 15430 <4> [] sys_close+0xa5/0x100 15431 <4> [] system_call_fastpath+0x16/0x1b 15432 <4>Code: 1b ec 1e e1 eb ce f6 05 9c fa d3 e1 20 74 ce 80 3d a0 ad 00 00 00 74 c5 48 89 de 48 c7 c7 00 32 2a a0 31 c0 e8 ca cc 28 e1 eb b2 <0f> 0b eb fe f6 05 73 fa d3 e1 20 0f 84 f6 fe ff ff 80 3d 9b ad 15433 <1>RIP [] destroy_conntrack+0x11c/0x150 [nf_conntrack
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
** Tags added: originate-from-1695149 sutton ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Importance: Undecided => Critical ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715279] [NEW] 2.6.32 netfliter . nf_conntrack . destroy_conntrack BUG
Public bug reported: In my server ,i got a BUG，and i can initially locate where this bug is : nf_conntrack_in-> resolve_normal_ct -> nf_conntrack_find_get -> unlikely(!nf_ct_tuple_equal(tuple, &h->tuple)) -> nf_ct_put -> destroy_conntrack -> nf_ct_is_confirmed -> BUG_ON but I don't know why this happens，please help me ,THANK YOU! 4>[ cut here ] 15381 <2>kernel BUG at net/netfilter/nf_conntrack_core.c:206! 15382 <4>invalid opcode: [#1] SMP 15383 <4>last sysfs file: /sys/devices/system/cpu/cpu47/topology/thread_siblings_list 15384 <4>CPU 0 15385 <4>Modules linked in: nbd(U) iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables ksl b_ctk(U) fuse tcp_diag inet_diag xfs exportfs kvm_intel kvm vhost_net macvtap macvlan cdc_ether usbnet mii tun openvswitch(U) libcrc32c b onding 8021q garp stp llc toa hookers ipv6 power_meter iTCO_wdt iTCO_vendor_support dcdbas ipmi_devintf lpc_ich mfd_core shpchp igb i2c_a lgo_bit i2c_core ixgbe dca ptp pps_core mdio sg ext4 jbd2 mbcache sd_mod crc_t10dif ahci megaraid_sas wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: nbd] 15386 <4> 15387 <4>Pid: 25449, comm: mebs-nbd-core Tainted: G --- H 2.6.32-431.20.3.el6.mt20161028.x86_64 #1 Dell Inc. PowerEdge R 730/0WCJNT 15388 <4>RIP: 0010:[] [] destroy_conntrack+0x11c/0x150 [nf_conntrack] 15389 <4>RSP: 0018:881d10cd99f8 EFLAGS: 00010246 15390 troy_conntrack+0x11c/0x1RAX: RBX: 8813d96dbdc8 RCX: 0001 15391 <4>RDX: b4be RSI: 0006 RDI: 8813d96dbdc8 15392 <4>RBP: 881d10cd9a08 R08: 0002 R09: 00c0 15393 <4>R10: R11: R12: 81b18540 15394 <4>R13: 0003 R14: 0002 R15: 0002 15395 <4>FS: 7f45d2ba1720() GS:88011f60() knlGS: 15396 <4>CS: 0010 DS: ES: CR0: 8005003b 15397 <4>CR2: CR3: 001f0aa3f000 CR4: 001427e0 15398 <4>DR0: DR1: DR2: 15399 <4>DR3: DR6: fffe0ff0 DR7: 0400 15400 <4>Process mebs-nbd-core (pid: 25449, threadinfo 881d10cd8000, task 881f0a9b6aa0) 15401 <4>Stack: 15402 <4> 881d10cd9ab8 81b18540 881d10cd9a18 8148a4c7 15403 <4> 881d10cd9a38 a029bac5 881c47af1b68 81b18540 15404 <4> 881d10cd9b18 a029bdd0 a026d620 a02a7080 15405 <4>Call Trace: 15406 <4> [] nf_conntrack_destroy+0x17/0x30 15407 <4> [] nf_conntrack_find_get+0x85/0x120 [nf_conntrack] 15408 <4> [] nf_conntrack_in+0x270/0xa00 [nf_conntrack] 15409 <4> [] ? ovs_dp_process_received_packet+0x51/0x80 [openvswitch] 15410 <4> [] ipv4_conntrack_local+0x51/0x60 [nf_conntrack_ipv4] 15411 <4> [] nf_iterate+0x69/0xb0 15412 <4> [] ? dst_output+0x0/0x20 15413 <4> [] nf_hook_slow+0x76/0x120 15414 <4> [] ? dst_output+0x0/0x20 15415 <4> [] __ip_local_out+0x9f/0xb0 15416 <4> [] ip_local_out+0x16/0x30 15417 <4> [] ip_queue_xmit+0x190/0x420 15418 <4> [] ? ip_output+0xb8/0xc0 15419 <4> [] tcp_transmit_skb+0x40e/0x7b0 15420 <4> [] tcp_write_xmit+0x230/0xa90 15421 troy_conntrack+0x11c/0x150 [] __tcp_push_pending_frames+0x30/0xe0 15422 <4> [] tcp_send_fin+0x72/0x1d0 15423 <4> [] tcp_close+0x346/0x450 15424 <4> [] inet_release+0x67/0x90 15425 <4> [] sock_release+0x29/0x90 15426 <4> [] sock_close+0x17/0x30 15427 <4> [] __fput+0xf5/0x210 15428 <4> [] fput+0x25/0x30 15429 <4> [] filp_close+0x5d/0x90 15430 <4> [] sys_close+0xa5/0x100 15431 <4> [] system_call_fastpath+0x16/0x1b 15432 <4>Code: 1b ec 1e e1 eb ce f6 05 9c fa d3 e1 20 74 ce 80 3d a0 ad 00 00 00 74 c5 48 89 de 48 c7 c7 00 32 2a a0 31 c0 e8 ca cc 28 e1 eb b2 <0f> 0b eb fe f6 05 73 fa d3 e1 20 0f 84 f6 fe ff ff 80 3d 9b ad 15433 <1>RIP [] destroy_conntrack+0x11c/0x150 [nf_conntrack] 15434 <4> RSP ** 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/1715279 Title: 2.6.32 netfliter . nf_conntrack . destroy_conntrack BUG Status in linux package in Ubuntu: Incomplete Bug description: In my server ,i got a BUG，and i can initially locate where this bug is : nf_conntrack_in-> resolve_normal_ct -> nf_conntrack_find_get -> unlikely(!nf_ct_tuple_equal(tuple, &h->tuple)) -> nf_ct_put -> destroy_conntrack -> nf_ct_is_confirmed -> BUG_ON but I don't know why this happens，please help me ,THANK YOU! 4>[ cut here ] 15381 <2>kernel BUG at net/netfilter/nf_conntrack_core.c:206! 15382 <4>invalid opcode: [#1] SMP 15383 <4>last sysfs file: /sys/devices/system/cpu/cpu47/topology/thread_siblings_list 15384 <4>CPU 0 15385 <4>Modules linked
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
commit 293b915fd9bebf33cdc906516fb28d54649a25ac Author: Oscar Campos Date: Tue Jul 18 17:20:36 2017 -0700 Input: trackpoint - assume 3 buttons when buttons detection fails Trackpoint buttons detection fails on ThinkPad 570 and 470 series, this makes the middle button of the trackpoint to not being recogized. As I don't believe there is any trackpoint with less than 3 buttons this patch just assumes three buttons when the extended button information read fails. Signed-off-by: Oscar Campos Acked-by: Peter Hutterer Signed-off-by: Dmitry Torokhov This 2nd need to be merged to ubuntu kernel. ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in linux package in Ubuntu: In Progress Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
commit ec667683c532c93fb41e100e5d61a518971060e2 Author: Aaron Ma Date: Fri Aug 18 12:17:21 2017 -0700 Input: trackpoint - add new trackpoint firmware ID Synaptics add new TP firmware ID: 0x2 and 0x3, for now both lower 2 bits are indicated as TP. Change the constant to bitwise values. This makes trackpoint to be recognized on Lenovo Carbon X1 Gen5 instead of it being identified as "PS/2 Generic Mouse". Signed-off-by: Aaron Ma Cc: sta...@vger.kernel.org Signed-off-by: Dmitry Torokhov -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in linux package in Ubuntu: In Progress Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work
The 1st patch was already sent to stable kernel, so don't need to merge to Ubuntu 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/1715271 Title: Middle button of trackpoint doesn't work Status in linux package in Ubuntu: In Progress Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715271] [NEW] Middle button of trackpoint doesn't work
Public bug reported: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. ** Affects: linux (Ubuntu) Importance: Critical Assignee: AaronMa (mapengyu) Status: 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/1715271 Title: Middle button of trackpoint doesn't work Status in linux package in Ubuntu: In Progress Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work
Mac Book Pro 12,1 Still not working in 16.10, kernel 4.8.9-59, and 17.10, kernel 4.12.0-12 The SD card is working in Mac OS (El Capitan). Mac OS says the device is 05ac:8406 Linux does not detect it at all. Not on boot, nor on plug out/plug in. uname -a Linux vizmac 4.8.0-59-generic #64-Ubuntu SMP Thu Jun 29 19:38:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux (booted from internal SSD) lsusb Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ~ dmesg | grep -i xhci [0.00] ACPI: SSDT 0x8AD6A000 000A64 (v02 APPLE Xhci 1000 INTL 20140424) [1.141735] xhci_hcd :00:14.0: xHCI Host Controller [1.141754] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 [1.142833] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0004b810 [1.142860] xhci_hcd :00:14.0: cache line size of 256 is not supported [1.142959] usb usb1: Product: xHCI Host Controller [1.142973] usb usb1: Manufacturer: Linux 4.8.0-59-generic xhci-hcd [1.143344] xhci_hcd :00:14.0: xHCI Host Controller [1.143361] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 [1.143439] usb usb2: Product: xHCI Host Controller [1.143453] usb usb2: Manufacturer: Linux 4.8.0-59-generic xhci-hcd [1.882127] usb 1-3: new full-speed USB device number 2 using xhci_hcd [2.142182] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd [2.282135] usb 1-5: new full-speed USB device number 3 using xhci_hcd ~ uname -a Linux viz-MacBookPro 4.12.0-12-generic #13-Ubuntu SMP Thu Aug 17 16:13:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux (Booted from USB 2-2 SanDisk flash stick) lsusb Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ~ dmesg | grep -i xhci [0.00] ACPI: SSDT 0x8AD6A000 000A64 (v02 APPLE Xhci 1000 INTL 20140424) [0.991473] xhci_hcd :00:14.0: xHCI Host Controller [0.991491] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 [0.992568] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0004b810 [0.992593] xhci_hcd :00:14.0: cache line size of 256 is not supported [0.992689] usb usb1: Product: xHCI Host Controller [0.992702] usb usb1: Manufacturer: Linux 4.12.0-12-generic xhci-hcd [0.993042] xhci_hcd :00:14.0: xHCI Host Controller [0.993058] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 [0.993132] usb usb2: Product: xHCI Host Controller [0.993145] usb usb2: Manufacturer: Linux 4.12.0-12-generic xhci-hcd [1.322891] usb 1-3: new full-speed USB device number 2 using xhci_hcd [1.583064] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd [1.722951] usb 1-5: new full-speed USB device number 3 using xhci_hcd ~ The card is working through USB adapter: sudo fdisk -l ... Disk /dev/sdc: 241,9 GiB, 259710255104 bytes, 507246592 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5F3710AB-8B17-4E96-B3CF-BF3B75CB8E89 Device Start End Sectors Size Type /dev/sdc1 2048 507244543 507242496 241,9G Linux filesystem ~ The card is Transcend JetDrive 256 GB https://transcend-info.com/apple/jetdrivelite/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620422 Title: Macbook Pro Retina 12,1 SD Card Reader Doesn't Work Status in linux package in Ubuntu: Expired Bug description: SD card reader doesn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graingert 2672 F pulseaudio /dev/snd/controlC1: graingert 2672 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 6 00:39:03 2016 InstallationDate: Installed on 2016-01-05 (244 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. Mac
[Kernel-packages] [Bug 1704363] Update Released
The verification of the Stable Release Update for linux-firmware 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Released Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset
This bug was fixed in the package linux-firmware - 1.157.12 --- linux-firmware (1.157.12) xenial; urgency=medium * Add firmware for Redpine 9113 chipset (LP: #1704363) - UBUNTU: linux-firmware: add firmware images for Redpine 9113 chipset -- Seth Forshee Fri, 11 Aug 2017 09:42:04 -0500 ** Changed in: linux-firmware (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Released Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715268] Re: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot c
** 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/1715268 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: I ran 'Software Updater" on 9/5 and got this result. It said "current status =half-installed" or similar language. I can only hope this this thing will boot next time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1764 F pulseaudio Date: Tue Sep 5 21:14:11 2017 ErrorMessage: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=6343e38d-c2cb-4bdc-931f-7d7de298ee9d InstallationDate: Installed on 2016-05-15 (478 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision M6300 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715268] 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/1715268 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: I ran 'Software Updater" on 9/5 and got this result. It said "current status =half-installed" or similar language. I can only hope this this thing will boot next time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1764 F pulseaudio Date: Tue Sep 5 21:14:11 2017 ErrorMessage: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=6343e38d-c2cb-4bdc-931f-7d7de298ee9d InstallationDate: Installed on 2016-05-15 (478 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision M6300 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715268] [NEW] package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot
Public bug reported: I ran 'Software Updater" on 9/5 and got this result. It said "current status =half-installed" or similar language. I can only hope this this thing will boot next time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1764 F pulseaudio Date: Tue Sep 5 21:14:11 2017 ErrorMessage: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=6343e38d-c2cb-4bdc-931f-7d7de298ee9d InstallationDate: Installed on 2016-05-15 (478 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision M6300 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check 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/1715268 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: I ran 'Software Updater" on 9/5 and got this result. It said "current status =half-installed" or similar language. I can only hope this this thing will boot next time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan1764 F pulseaudio Date: Tue Sep 5 21:14:11 2017 ErrorMessage: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=6343e38d-c2cb-4bdc-931f-7d7de298ee9d InstallationDate: Installed on 2016-05-15 (478 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision M6300 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: package linux-image-extra-4.4.0-77-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kern
[Kernel-packages] [Bug 1714571] Comment bridged from LTC Bugzilla
--- Comment From s...@us.ibm.com 2017-09-05 17:51 EDT---
The patch was merged into perf-tip by Ingo Molnar, here:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit?id=770e96125515daf1c7bc179323f2e0d488dfe6ac
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1714571
Title:
[P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
counted twice when perf stat is done (perf:)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Triaged
Bug description:
== Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 ==
---Problem Description---
Problem description :
=
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is
because two raw point to the same name.
[
{,
"EventCode": "0x20036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
{,
"EventCode": "0x40036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
Ex :
===
[root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1
Performance counter stats for 'sleep 1':
30,163 pm_br_2path
pm_br_2path
(0.00%)
1.002046416 seconds time elapsed
[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1
Performance counter stats for 'sleep 1':
9,217 pm_ld_miss_l1
pm_ld_miss_l1
(0.00%)
1.001956110 seconds time elapsed
---Steps to Reproduce---
Steps to reproduce :
1. Install perf (linux-tools)
2. Run
perf stat -e pm_ld_miss_l1 sleep 1
perf stat -e pm_br_2path sleep 1
== Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
I built the next test kernel, up to the following commit: 74caeadc074b099b80abca86a19ab95003ca294e The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1701222 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1710690 Title: Ubuntu16.04.3: System running network stress crashes with Alignment exception Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Bug description: State: Open by: nguyenp on 11 August 2017 11:03:32 Contact: === Paul Nguyen nguy...@us.ibm.com BMC: bos1u1 Firmware Revision : 00.25 Firmware Build Time : 20170807BMC MAC address : 0c:c4:7a:f4:4d:60 PNOR Build Time : 20170729 CPLD Version : B2.91.00 Ubuntu 16.04.3: === bos1u1p1 ver 1.5.4.5 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04.3 LTS \n \l Kernel Version: 4.11.0-12-generic HTX Version: htxubuntu-448 Host Name: bos1u1p1 Machine Serial No: C819UAF32B2 Machine Type/Model: 9006-12C root@bos1u1p1:~# dpkg -l |grep mlx ii libmlx4-1 41mlnx1-OFED.4.1.0.1.0.41014 ppc64el Userspace driver for Mellanox ConnectX InfiniBand HCAs ii libmlx4-1-dbg 41mlnx1-OFED.4.1.0.1.0.41014 ppc64el Debugging symbols for the libmlx4 driver ii libmlx4-dev41mlnx1-OFED.4.1.0.1.0.41014 ppc64el Development files for the libmlx4 driver ii libmlx5-1 41mlnx1-OFED.4.1.0.1.3.0.1.41014 ppc64el Userspace driver for Mellanox ConnectX InfiniBand HCAs ii libmlx5-1-dbg 41mlnx1-OFED.4.1.0.1.3.0.1.41014 ppc64el Debugging symbols for the libmlx5 driver ii libmlx5-dev41mlnx1-OFED.4.1.0.1.3.0.1.41014 ppc64el Development files for the libmlx5 driver root@bos1u1p1:~# lsscsi [0:2:0:0]diskSEAGATE ST4000NM0034 E005 /dev/sda [0:3:123:0] enclosu ADAPTEC Smart Adapter2.99 - root@bos1u1p1:~# lspci :00:00.0 PCI bridge: IBM Device 04c1 0001:00:00.0 PCI bridge: IBM Device 04c1 0002:00:00.0 PCI bridge: IBM Device 04c1 0002:01:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T (rev 02) 0002:01:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T (rev 02) 0002:01:00.2 Ethernet controller: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T (rev 02) 0002:01:00.3 Ethernet controller: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T (rev 02) 0003:00:00.0 PCI bridge: IBM Device 04c1 0003:01:00.0 Serial Attached SCSI controller: Adaptec Series 8 12G SAS/PCIe 3 (rev 01) 0004:00:00.0 PCI bridge: IBM Device 04c1 0004:01:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) 0004:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) 0005:00:00.0 PCI bridge: IBM Device 04c1 0005:01:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) 0030:00:00.0 PCI bridge: IBM Device 04c1 0030:01:00.0 Infiniband controller: Mellanox Technologies Device 1019 0030:01:00.1 Infiniband controller: Mellanox Technologies Device 1019 0031:00:00.0 PCI bridge: IBM Device 04c1 0031:01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 0031:01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 0032:00:00.0 PCI bridge: IBM Device 04c1 0033:00:00.0 PCI bridge: IBM Device 04c1 0033:01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) 0033:01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) root@bos1u1p1:~# ifconfig -a enP2p1s0f0 Link encap:Ethernet HWaddr ac:1f:6b:09:c0:9e inet addr:9.3.20.217 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::ae1f:6bff:fe09:c09e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:62603 errors:0 dropped:0 overruns:0 frame:0 TX packets:105 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4784741 (4.7 MB) TX bytes:14043 (14.0 KB) enP2p1s0f1 Link encap:Ethernet HWaddr ac:1f:6b:09:c0:9f BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) enP2p1
[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure
Any news? Anything I should help test? -- 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/1712867 Title: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure Status in linux-azure package in Ubuntu: In Progress Status in makedumpfile package in Ubuntu: New Status in linux-azure source package in Xenial: In Progress Status in makedumpfile source package in Xenial: New Bug description: Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error: kdump-tools[1436]: ELF core (kcore) parse failed Perhaps the artful kexec-tools should be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1712867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches
** Description changed:
+ == SRU Justification ==
+ The commit requested in this bug exposes functionality needed by the Nvidia
device driver on POWER9.
+
+ This patch is a clean cherry pick and specific to powerpc.
+
+ This commit is in mainline as of 4.11-rc1.
+
== Comment: #0 - Reza A. Arbab - 2017-08-07 15:34:04 ==
We need to backport mainline commit be9ba9ff93cc ("Drop GPL from
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.
This exposes functionality needed by the Nvidia device driver on POWER9.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709179
Title:
Drop GPL from of_node_to_nid() export to match other arches
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
== SRU Justification ==
The commit requested in this bug exposes functionality needed by the Nvidia
device driver on POWER9.
This patch is a clean cherry pick and specific to powerpc.
This commit is in mainline as of 4.11-rc1.
== Comment: #0 - Reza A. Arbab - 2017-08-07 15:34:04 ==
We need to backport mainline commit be9ba9ff93cc ("Drop GPL from
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.
This exposes functionality needed by the Nvidia device driver on
POWER9.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709179/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)
@jsalisbury Will do and report back... Still would like to try this out on my own, but I fail to find out how to build the hwe kernel on my own. See my questions above. As it looks to me, the official documentation is outdated or incomplete. Can you (or anyone else) please help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711951 Title: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: This is a copy of a very similar bug report which is currently marked as triaged and where my comment is ignored maybe because of that. Please see my additional remarks at the end of this report. --- Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours. The bug has been fixed upstream, see 6625914 ACPI / EC: Drop EC noirq hooks to fix a regression 9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129 (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181) and I hope this fix will make its way into a near-future kernel update to ubuntu :) Many thanks! --- Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616 Additional remarks: - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen. - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too! I can reproduce it on my local system which has "linux-image-generic- hwe-16.04" installed (4.10.0.32.34). Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference: https://patchwork.kernel.org/patch/9835823/ https://patchwork.kernel.org/patch/9835825/ I am reporting this as a new issue because the fixes from 4.13 need to be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700606] Re: POWER9: CAPI2 enablement - Fixes
Sorry for the delay. I built a ppc64le Zesty test kernel with the requested 7 patches. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1700606/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)
Can you test the latest mainline kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711951 Title: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: This is a copy of a very similar bug report which is currently marked as triaged and where my comment is ignored maybe because of that. Please see my additional remarks at the end of this report. --- Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours. The bug has been fixed upstream, see 6625914 ACPI / EC: Drop EC noirq hooks to fix a regression 9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129 (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181) and I hope this fix will make its way into a near-future kernel update to ubuntu :) Many thanks! --- Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616 Additional remarks: - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen. - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too! I can reproduce it on my local system which has "linux-image-generic- hwe-16.04" installed (4.10.0.32.34). Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference: https://patchwork.kernel.org/patch/9835823/ https://patchwork.kernel.org/patch/9835825/ I am reporting this as a new issue because the fixes from 4.13 need to be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set
For the record, the change has been merge in makedumpfile upstream:
--
commit ade8512bd2be9eef9f2a0376b41f22d5417c72f3
Author: Eric Desrochers
Date: Wed Mar 8 09:45:02 2017 +0900
[PATCH] Fix typo in the ERRMSG of function show_mem_usage
Should be "kernel" instead of "kenrel".
Signed-off-by: Eric Desrochers
--
--
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/1670696
Title:
Typo in error msg when no crashkernel memory reservation is set
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Zesty:
Won't Fix
Status in makedumpfile package in Debian:
New
Bug description:
[Impact]
* There is a typo in ERRMSG of function show_mem_usage affecting
Xenial/Zesty, Debian and makedumpfile upstream.
This should be :
"show_mem_usage: No memory is reserved for crashkernel!"
instead of :
"show_mem_usage: No memory is reserved for crashkenrel!"
The typo is located here in src code :
# filename : makedumpfile.c
-
int show_mem_usage(void)
{
uint64_t vmcoreinfo_addr, vmcoreinfo_len;
struct cycle cycle = {0};
if (!is_crashkernel_mem_reserved()) {
==> ERRMSG("No memory is reserved for crashkenrel!\n");
return FALSE;
}
-
[Test Case]
* Take a system with no crashkernel memory reservation set
* run command : makedumpfile --mem-usage /proc/kcore
* Error message :
show_mem_usage: No memory is reserved for crashkenrel!
[Regression Potential]
* No regression, it is a trivial change with no behavioural change.
[Other Info]
* Upstream:
Patch has been submitted upstream (ML :ke...@lists.infradead.org)
- AFAIK, there is no upstream bug database, so no URL available, ML only.
- Patch will be merge in upstream version 1.6.2 # See comment #4
* Debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709738] Re: xfstest sanity checks 17 fails on data-hole-data inside page
Can you next test the following two kernels: 4.13-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2 4.13-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3 We should know the last bad kernel and first good kernel after getting these test results. If 4.13-rc2 is good, you don't have to test 4.13-rc3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709738 Title: xfstest sanity checks 17 fails on data-hole-data inside page Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: Problem Description xfstests fails with Metadata corruption at leaf on ext4 filesystem Environment -- Kernel Build: 4.12.1-041201-generic System Name : ltc-test-ci2 Model : 8247-22L Platform: PowerNV ( P8 ) Issue observed in P9 also. Uname output --- # uname -a Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with ext4 filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/ext4/445 generic/445 [failed, exit status 1] - output mismatch (see /root/harish/xfstests-dev/results//generic/445.out.bad) --- tests/generic/445.out 2017-07-13 06:04:36.244322946 -0400 +++ /root/harish/xfstests-dev/results//generic/445.out.bad 2017-07-14 02:49:06.540352923 -0400 @@ -1,2 +1,3 @@ QA output created by 445 -Silence is golden +seek sanity check failed! +(see /root/harish/xfstests-dev/results//generic/445.full for details) ... (Run 'diff -u tests/generic/445.out /root/harish/xfstests-dev/results//generic/445.out.bad' to see the entire diff) Nothing observed in dmesg. Full log is attached. Note: Issue is also observed on distro kernel - 4.11.0-10-generic. It needs to have two disks you run the test on. Make sure you create those directories before running the test. # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails
Can you test the following two kernels next: 4.12-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/ 4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715220] 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/1715220 Title: package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: internal process pre-installation script failed with exit code 1 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded ubuntu-mate system as usual, but got an error: This kernel does not support a non-PAE CPU. Yes, this is a 32-bit only CPU (Pentium M in Thinkpad T40), but it works. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: menesis 20576 F pulseaudio Date: Tue Sep 5 22:07:52 2017 ErrorMessage: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 InstallationDate: Installed on 2017-08-14 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) IwConfig: lono wireless extensions. enp2s1no wireless extensions. irda0 no wireless extensions. MachineType: IBM 2373Z82 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=df27fbb4-ea83-484e-9a9e-ae42d51e0eb3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu6 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2005 dmi.bios.vendor: IBM dmi.bios.version: 1RETDNWW (3.19 ) dmi.board.name: 2373Z82 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDNWW(3.19):bd10/13/2005:svnIBM:pn2373Z82:pvrThinkPadT42:rvnIBM:rn2373Z82:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373Z82 dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715220] [NEW] package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: internal process pre-installation script failed with exit code 1
Public bug reported: Upgraded ubuntu-mate system as usual, but got an error: This kernel does not support a non-PAE CPU. Yes, this is a 32-bit only CPU (Pentium M in Thinkpad T40), but it works. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: menesis 20576 F pulseaudio Date: Tue Sep 5 22:07:52 2017 ErrorMessage: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 InstallationDate: Installed on 2017-08-14 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) IwConfig: lono wireless extensions. enp2s1no wireless extensions. irda0 no wireless extensions. MachineType: IBM 2373Z82 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=df27fbb4-ea83-484e-9a9e-ae42d51e0eb3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu6 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2005 dmi.bios.vendor: IBM dmi.bios.version: 1RETDNWW (3.19 ) dmi.board.name: 2373Z82 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDNWW(3.19):bd10/13/2005:svnIBM:pn2373Z82:pvrThinkPadT42:rvnIBM:rn2373Z82:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373Z82 dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package artful i386 ** Summary changed: - package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 + package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: internal process pre-installation script failed with exit code 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715220 Title: package linux-image-4.12.0-12-generic (not installed) failed to install/upgrade: internal process pre-installation script failed with exit code 1 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded ubuntu-mate system as usual, but got an error: This kernel does not support a non-PAE CPU. Yes, this is a 32-bit only CPU (Pentium M in Thinkpad T40), but it works. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: menesis 20576 F pulseaudio Date: Tue Sep 5 22:07:52 2017 ErrorMessage: vidinis procesas naujas pre-installation scenarijus nutrūko gražindamas reikšmę 1 InstallationDate: Installed on 2017-08-14 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) IwConfig: lono wireless extensions. enp2s1no wireless extensions. irda0 no wireless extensions. MachineType: IBM 2373Z82 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=df27fbb4-ea83-484e-9a9e-ae42d51e0eb3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: grub-pc 2.
[Kernel-packages] [Bug 1711182] Re: ACPI ID for Hip07/08 I2C controller has typo
dannf@d05-3:~$ cat /proc/version Linux version 4.10.0-34-generic (buildd@bos01-arm64-030) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #38~16.04.1-Ubuntu SMP Wed Aug 30 18:05:59 UTC 2017 dannf@d05-3:~$ ls -l /sys/class/i2c-dev/*/device/firmware_node lrwxrwxrwx 1 root root 0 Sep 5 15:08 /sys/class/i2c-dev/i2c-4/device/firmware_node -> ../../../LNXSYSTM:00/LNXSYBUS:00/HISI02A1:00 ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711182 Title: ACPI ID for Hip07/08 I2C controller has typo Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: [Impact] Due to a typo in the upstream fix for LP: #1708293, the i2c driver still does not recognize the ACPI IDs for the i2c devices on the Hip07/08 platforms, making these devices unusable. [Test Case] ls -l /sys/class/i2c-dev/*/device/firmware_node | grep HISI [Regression Risk] This adds an ID/config for previously unsupported ACPI IDs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
I had similar issues with checksum errors on Precision 5520. Updating to the recently released BIOS version 1.4 has resolved those issues. Finally, all is well with Ubuntu, TB16, and Precision 5520. Thanks all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-
[Kernel-packages] [Bug 1714571] Re: [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)
** 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/1714571
Title:
[P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
counted twice when perf stat is done (perf:)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Triaged
Bug description:
== Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 ==
---Problem Description---
Problem description :
=
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is
because two raw point to the same name.
[
{,
"EventCode": "0x20036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
{,
"EventCode": "0x40036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
Ex :
===
[root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1
Performance counter stats for 'sleep 1':
30,163 pm_br_2path
pm_br_2path
(0.00%)
1.002046416 seconds time elapsed
[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1
Performance counter stats for 'sleep 1':
9,217 pm_ld_miss_l1
pm_ld_miss_l1
(0.00%)
1.001956110 seconds time elapsed
---Steps to Reproduce---
Steps to reproduce :
1. Install perf (linux-tools)
2. Run
perf stat -e pm_ld_miss_l1 sleep 1
perf stat -e pm_br_2path sleep 1
== Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful
Closing won't fix based on comment #5, please re-open if something changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713765 Title: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful Status in linux package in Ubuntu: Confirmed Bug description: Hi, there is this patch in discussion [1]. If I read correctly between the lines that is supposed to go to -stable trees as well as to linxu-s390x next (4.14) submissions. But the change is rather big and we have to consider taking that early or as SRU or not at all. I wanted to ask the kernel Team to keep an eye on that discussion and take the patch into consideration - IMHO it might change KVM behavior on s390 quite a bit. So I'm not sure how SRUable it is while on Artful we migth add it rather soon before release. To some extend we should wait for the discussion on the upstreaming, but then I wanted to make you aware asap. [1]: https://lists.gnu.org/archive/html/qemu- devel/2017-08/msg05286.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714583] Re: Realtek RTL8822BE Support Coming To Linux 4.14
** Changed in: linux (Ubuntu Artful) Importance: Medium => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714583 Title: Realtek RTL8822BE Support Coming To Linux 4.14 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hello, Please... Add module RTL8822BE: * https://www.phoronix.com/scan.php?page=news_item&px=Linux-Realtek-RTL8822BE * https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=5b5ab4cb5cda824ef59e0511ac5d585f35f1a1a6 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1807 F pulseaudio /dev/snd/pcmC1D0p: caravena 1807 F...m pulseaudio /dev/snd/controlC1: caravena 1807 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 1 16:51:10 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 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/1714583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715064] Re: 17.10 fails to boot on POWER9 DD2.0 with Deep stop states
Applied to artful/master-next, and also cherry picked the linux-next
commits and applied the mailing list patch to the 4.13 unstable kernel.
Note that 785a12afdb4a52903447fd890633c82fdda4b6f7 and
24be85a23d1fcdc72264a062a2e4ebaaea48feab were backports in 4.12 and not
clean cherry picks.
I'll also mention that we expect the current artful-proposed kernel to
be the last 4.12 kernel for artful before we switch to 4.13, so if that
holds we won't actually release a 4.12 with these patches (but they are
applied in case we do release another 4.12). Depending how things go the
patches will be in either the first or the second 4.13 kernel in artful-
release.
** Changed in: linux (Ubuntu Artful)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Artful)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715064
Title:
17.10 fails to boot on POWER9 DD2.0 with Deep stop states
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== Comment: #0 - Ranjal G. Shenoy
On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the
17.10 kernel Ubuntu-4.12.0-12.13 fails to boot.
It requires the following upstream fixes to be backported.
1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize
core_idle_state_ptr")
2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore &
Per-core SPRs restore")
3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from
deep-stop")
4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle
states via stop API.")
5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for
restoring state on P9 DD1")
6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't
stop time")
7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT
states when stop-api fails")
8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for
stop4 cpuidle")
9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api
only on Hotplug")
10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear
LPCR[PECE1] via stop-api only for deep state offline")
Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in
powerpc/linux.git -next branch. and 10) is posted upstream which fixes
9).
These patches have been backported on top of Ubuntu-4.12.0-12.13 and
tested on Boston where they are working as expected.
== Comment: #1 - Ranjal G. Shenoy
The lower 8 bits of core_idle_state_ptr tracks the number of non-idle
threads in the core. This is supposed to be initialized to bit-map
corresponding to the threads_per_core. However, currently it is
initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for
POWER8 which has 8 threads per core, but not for POWER9 which has 4
threads per core.
As a result, on POWER9, core_idle_state_ptr gets initialized to
0xFF. In case when all the threads of the core are idle, the bits
corresponding tracking the idle-threads are non-zero. As a result, the
idle entry/exit code fails to save/restore per-core hypervisor state
since it assumes that there are threads in the cores which are still
active.
Fix this by correctly initializing the lower bits of the
core_idle_state_ptr on the basis of threads_per_core.
Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle:
Correctly initialize core_idle_state_ptr")
== Comment: #2 - Ranjal G. Shenoy
On POWER8, in case of
- nap: both timebase and hypervisor state is retained.
- fast-sleep: timebase is lost. But the hypervisor state is retained.
- winkle: timebase and hypervisor state is lost.
Hence, the current code for handling exit from a idle state assumes
that if the timebase value is retained, then so is the hypervisor
state. Thus, the current code doesn't restore per-core hypervisor
state in such cases.
But that is no longer the case on POWER9 where we do have stop states
in which timebase value is retained, but the hypervisor state is
lost. So we have to ensure that the per-core hypervisor state gets
restored in such cases.
Fix this by ensuring that even in the case when timebase is retained,
we explicitly check if we are waking up from a deep stop that loses
per-core hypervisor state (indicated by cr4 being eq or gt), and if
this is the case, we restore the per-core hypervisor state.
Cherry-picked from commit ec4867355244 ("powe
[Kernel-packages] [Bug 1714571] Re: [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)
Can you post a link here when this patch gets pulled into linux-next or
mainline?
** 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/1714571
Title:
[P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
counted twice when perf stat is done (perf:)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 ==
---Problem Description---
Problem description :
=
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is
because two raw point to the same name.
[
{,
"EventCode": "0x20036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
{,
"EventCode": "0x40036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
Ex :
===
[root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1
Performance counter stats for 'sleep 1':
30,163 pm_br_2path
pm_br_2path
(0.00%)
1.002046416 seconds time elapsed
[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1
Performance counter stats for 'sleep 1':
9,217 pm_ld_miss_l1
pm_ld_miss_l1
(0.00%)
1.001956110 seconds time elapsed
---Steps to Reproduce---
Steps to reproduce :
1. Install perf (linux-tools)
2. Run
perf stat -e pm_ld_miss_l1 sleep 1
perf stat -e pm_br_2path sleep 1
== Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715201] Re: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** 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/1715201 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This might be caused by an out of disk space on /boot during an apt- get install. That happened around the same time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rcronk 2206 F pulseaudio /dev/snd/controlC0: rcronk 2206 F pulseaudio Date: Tue Sep 5 11:50:04 2017 DpkgHistoryLog: Start-Date: 2017-09-05 11:47:38 Commandline: apt-get install -f Requested-By: rcronk (1000) Install: linux-image-extra-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93:amd64 (4.4.0-93.116, automatic), linux-image-4.4.0-89-generic:amd64 (4.4.0-89.112, automatic), linux-image-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-extra-virtual:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-generic:amd64 (4.4.0.89.95, 4.4.0.93.98) DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9d48e248-0867-4456-9e6b-2234b10f862a InstallationDate: Installed on 2016-05-06 (487 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0507 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T6 WS REVOLUTION dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T6WSREVOLUTION:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715201] 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/1715201 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This might be caused by an out of disk space on /boot during an apt- get install. That happened around the same time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rcronk 2206 F pulseaudio /dev/snd/controlC0: rcronk 2206 F pulseaudio Date: Tue Sep 5 11:50:04 2017 DpkgHistoryLog: Start-Date: 2017-09-05 11:47:38 Commandline: apt-get install -f Requested-By: rcronk (1000) Install: linux-image-extra-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93:amd64 (4.4.0-93.116, automatic), linux-image-4.4.0-89-generic:amd64 (4.4.0-89.112, automatic), linux-image-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-extra-virtual:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-generic:amd64 (4.4.0.89.95, 4.4.0.93.98) DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9d48e248-0867-4456-9e6b-2234b10f862a InstallationDate: Installed on 2016-05-06 (487 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0507 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T6 WS REVOLUTION dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T6WSREVOLUTION:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715201] [NEW] package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: This might be caused by an out of disk space on /boot during an apt-get install. That happened around the same time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rcronk 2206 F pulseaudio /dev/snd/controlC0: rcronk 2206 F pulseaudio Date: Tue Sep 5 11:50:04 2017 DpkgHistoryLog: Start-Date: 2017-09-05 11:47:38 Commandline: apt-get install -f Requested-By: rcronk (1000) Install: linux-image-extra-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93:amd64 (4.4.0-93.116, automatic), linux-image-4.4.0-89-generic:amd64 (4.4.0-89.112, automatic), linux-image-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-extra-virtual:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-generic:amd64 (4.4.0.89.95, 4.4.0.93.98) DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9d48e248-0867-4456-9e6b-2234b10f862a InstallationDate: Installed on 2016-05-06 (487 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0507 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T6 WS REVOLUTION dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T6WSREVOLUTION:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package 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/1715201 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This might be caused by an out of disk space on /boot during an apt- get install. That happened around the same time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rcronk 2206 F pulseaudio /dev/snd/controlC0: rcronk 2206 F pulseaudio Date: Tue Sep 5 11:50:04 2017 DpkgHistoryLog: Start-Date: 2017-09-05 11:47:38 Commandline: apt-get install -f Requested-By: rcronk (1000) Install: linux-image-extra-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), linux-headers-4.4.0-93:amd64 (4.4.0-93.116, automatic), linux-image-4.4.0-89-generic:amd64 (4.4.0-89.112, automatic), linux-image-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-generic:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-image-extra-virtual:amd64 (4.4.0.89.95, 4.4.0.93.98), linux-generic:amd64
[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)
I've uploaded this to the xenial and zesty -proposed queues for review by the SRU team, however the test case / steps to reproduce could use some improvement see bug 1704932 for a better example. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696102 Title: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in xfsprogs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in xfsprogs source package in Xenial: In Progress Status in linux source package in Zesty: Invalid Status in xfsprogs source package in Zesty: In Progress Bug description: Problem Description xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent. # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530 +++ /root/xfstests-dev/results//xfs/073.out.bad 2017-03-27 11:11:43.023059702 +0530 @@ -59,8 +59,7 @@ comparing new image geometry to old unmounting and removing new image checking new image -mounting new image on loopback -comparing new image files to old -comparing new image directories to old -comparing new image geometry to old -unmounting and removing new image +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c) +(see /root/xfstests-dev/results//xfs/073.full for details) +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r) +(see /root/xfstests-dev/results//xfs/073.full for details) Metadata corruption detected at xfs_agf block 0x1/0x200 # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.conf for running with created loop device 5.. Run xfstests-dev test : ./check tests/xfs/073 Full log is attached. == Comment: #2 - Harish Sriram - 2017-05-31 01:22:11 == (In reply to comment #1) > Hi Harish, > Can you share the steps used in creating the loop device with xfs filesystem > ? > > Thank you. Create loop device: # mkdir /mnt/loop-device /mnt/test /mnt/scratch # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done Create File system: # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1347835] 💰Re: No office or employees to deal with
One huge stressor for many business owners is managing staff and the logistics of running a functional office or facility. Once again, affiliate marketers don’t have to worry about this. The vast majority of affiliate marketing companies are run out of people’s homes by solo entrepreneurs. Take a look http://www.wpsiteadmin.com/job-shop_n2x.php?m=EMTM0NzgzNUBidWdzLmxhdW5jaHBhZC5uZXQ- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1347835 Title: Hot Keys not working (not registered in evtest or acpi_listen) Status in linux package in Ubuntu: Confirmed Bug description: I'm using a Fujitsu UH552 laptop with Ubuntu Gnome 14.04. Effectively my FN+(F key) special keys sort of work. My mute (FN + F3), brightness down (FN + F6), brightness up (FN + F7), volume down (FN + F8), volume up (FN+ F9) work. However the following issues exist :- The radio kill (FN + F5), and the external monitor display selector / choose between duplicate, extend or external only button (FN + F10) does not work. The print Screen (FN + Insert) works, but its functionality is duplicated on FN + Delete. I have checked whether I am using the fujitsu_laptop module (which I am) using lsmod | grep fujitsu. I have run sudo evtest and only the keys that are working / duplicated are detected, however the duplicated key has the same scan codes (4 and 99). I then ran acpi_listen and the only hot keys recognised are:- button/mute MUTE 0080 K video/brightnessdown BRTDN 0087 video/brightnessup BRTUP 0086 button/volumedown VOLDN 0080 K button/volumeup VOLUP 0080 K Help kindly appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: craig 2953 F pulseaudio CurrentDesktop: GNOME Date: Wed Jul 23 18:21:01 2014 HibernationDevice: RESUME=UUID=e9813637-6815-4ca0-916c-5d1c9f13b1d7 InstallationDate: Installed on 2013-12-02 (233 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: FUJITSU LIFEBOOK UH552 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=eae4a826-2ad7-49c2-9e68-56b46465fd66 ro quiet splash i8042.notimeout vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-22 (92 days ago) WifiSyslog: dmi.bios.date: 07/29/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 2.15 dmi.board.name: FJNBB31 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr2.15:bd07/29/2013:svnFUJITSU:pnLIFEBOOKUH552:pvr:rvnFUJITSU:rnFJNBB31:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK UH552 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size
First I created a Ubuntu 16.04 VM on Azure, which could reproduce the bug, and "uname -a" showed: Linux decui-u1604-hwe 4.4.0-92-generic #115~14.04.1-Ubuntu SMP Thu Aug 10 15:06:53 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I installed the xenial/, and confirmed it resolved the bug: Linux decui-u1604-hwe 4.4.0-93-generic #116~lp1713884 SMP Wed Aug 30 14:16:51 UTC 2017 x86_64 x86_64 x86_64 GNU/LinuxLinux decui- And the zesty kernel resolved the bug too: u1604-hwe 4.10.0-33-generic #37~lp1713884 SMP Wed Aug 30 14:15:48 UTC 2017 x86_64 x86_64 x86_64 And the artful kernel resolved the bug too: Linux decui-u1604-hwe 4.12.0-11-generic #12~lp1713884 SMP Wed Aug 30 14:14:10 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713884 Title: [CIFS] Fix maximum SMB2 header size Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Bug description: Currently the maximum size of SMB2/3 header is set incorrectly which leads to hanging of directory listing operations on encrypted SMB3 connections. Fix this by setting the maximum size to 170 bytes that is calculated as RFC1002 length field size (4) + transform header size (52) + SMB2 header size (64) + create response size (56). https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de This applies across the board 3.16, 4.4, 4.10, artful, and azure. Microsoft would be happy to help test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)
** Changed in: xfsprogs (Ubuntu Zesty) Status: Triaged => In Progress ** Changed in: xfsprogs (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: xfsprogs (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696102 Title: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in xfsprogs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in xfsprogs source package in Xenial: In Progress Status in linux source package in Zesty: Invalid Status in xfsprogs source package in Zesty: In Progress Bug description: Problem Description xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent. # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530 +++ /root/xfstests-dev/results//xfs/073.out.bad 2017-03-27 11:11:43.023059702 +0530 @@ -59,8 +59,7 @@ comparing new image geometry to old unmounting and removing new image checking new image -mounting new image on loopback -comparing new image files to old -comparing new image directories to old -comparing new image geometry to old -unmounting and removing new image +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c) +(see /root/xfstests-dev/results//xfs/073.full for details) +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r) +(see /root/xfstests-dev/results//xfs/073.full for details) Metadata corruption detected at xfs_agf block 0x1/0x200 # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.conf for running with created loop device 5.. Run xfstests-dev test : ./check tests/xfs/073 Full log is attached. == Comment: #2 - Harish Sriram - 2017-05-31 01:22:11 == (In reply to comment #1) > Hi Harish, > Can you share the steps used in creating the loop device with xfs filesystem > ? > > Thank you. Create loop device: # mkdir /mnt/loop-device /mnt/test /mnt/scratch # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done Create File system: # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)
The problem just happened again on this kernel (4.10.0.33.35), so the issue still needs to be solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711951 Title: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: This is a copy of a very similar bug report which is currently marked as triaged and where my comment is ignored maybe because of that. Please see my additional remarks at the end of this report. --- Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours. The bug has been fixed upstream, see 6625914 ACPI / EC: Drop EC noirq hooks to fix a regression 9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129 (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181) and I hope this fix will make its way into a near-future kernel update to ubuntu :) Many thanks! --- Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616 Additional remarks: - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen. - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too! I can reproduce it on my local system which has "linux-image-generic- hwe-16.04" installed (4.10.0.32.34). Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference: https://patchwork.kernel.org/patch/9835823/ https://patchwork.kernel.org/patch/9835825/ I am reporting this as a new issue because the fixes from 4.13 need to be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714583] Re: Realtek RTL8822BE Support Coming To Linux 4.14
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Artful) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Triaged ** 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/1714583 Title: Realtek RTL8822BE Support Coming To Linux 4.14 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hello, Please... Add module RTL8822BE: * https://www.phoronix.com/scan.php?page=news_item&px=Linux-Realtek-RTL8822BE * https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=5b5ab4cb5cda824ef59e0511ac5d585f35f1a1a6 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1807 F pulseaudio /dev/snd/pcmC1D0p: caravena 1807 F...m pulseaudio /dev/snd/controlC1: caravena 1807 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 1 16:51:10 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 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/1714583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714571] Re: [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1714571
Title:
[P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
counted twice when perf stat is done (perf:)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 ==
---Problem Description---
Problem description :
=
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is
because two raw point to the same name.
[
{,
"EventCode": "0x20036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
{,
"EventCode": "0x40036",
"EventName": "PM_BR_2PATH",
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": ""
},
Ex :
===
[root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1
Performance counter stats for 'sleep 1':
30,163 pm_br_2path
pm_br_2path
(0.00%)
1.002046416 seconds time elapsed
[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1
Performance counter stats for 'sleep 1':
9,217 pm_ld_miss_l1
pm_ld_miss_l1
(0.00%)
1.001956110 seconds time elapsed
---Steps to Reproduce---
Steps to reproduce :
1. Install perf (linux-tools)
2. Run
perf stat -e pm_ld_miss_l1 sleep 1
perf stat -e pm_br_2path sleep 1
== Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714661] Re: rtl8188ee network problem
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714661 Title: rtl8188ee network problem Status in linux package in Ubuntu: Incomplete Bug description: rtl8188ee network problem --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mirvahid 2332 F pulseaudio /dev/snd/controlC1: mirvahid 2332 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-05 (120 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA Satellite S75-A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-34-generic.efi.signed root=UUID=e6692555-c8a5-4b59-a6a9-44ccf3a93d57 ro quiet splash irqpoll vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-34.38-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-34-generic N/A linux-backports-modules-4.10.0-34-generic N/A linux-firmware 1.167 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: zesty Uname: Linux 4.10.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd06/27/2013:svnTOSHIBA:pnSatelliteS75-A:pvrPSKNAU-00E004B:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite S75-A dmi.product.version: PSKNAU-00E004B dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714738] Re: Error start ubuntu, after update.
Does this bug go away if you boot into the prior kernel version? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: New => Incomplete ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => High ** Tags added: kernel-da-key zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714738 Title: Error start ubuntu, after update. Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: After update, the system not start with Kernel version 4.10.00-33-generic [24.544059] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe 8] flip_done timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714831] Re: NMI watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [thermald:1006]
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.13 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.13 ** 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/1714831 Title: NMI watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [thermald:1006] Status in linux package in Ubuntu: Incomplete Bug description: I don't know ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1231 F pulseaudio adezelin 1562 F pulseaudio /dev/snd/controlC0: gdm1231 F pulseaudio adezelin 1562 F pulseaudio Date: Sun Sep 3 23:30:04 2017 Failure: oops HibernationDevice: RESUME=UUID=c8d20e0d-bbcf-4373-b706-c920d1bcaf2b InstallationDate: Installed on 2017-09-02 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=696c9898-0f42-49d2-a274-d363e68e88db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [thermald:1006] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714859] Re: oops in 4.4.0-62-generic (ppc64le)
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.13 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.13 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714859 Title: oops in 4.4.0-62-generic (ppc64le) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Sep 1 14:23:30 p87 kernel: [17274563.423972] device vnet2 entered promiscuous mode Sep 1 14:23:30 p87 kernel: [17274563.436101] br0: port 4(vnet2) entered forwarding state Sep 1 14:23:30 p87 kernel: [17274563.436113] br0: port 4(vnet2) entered forwarding state Sep 1 14:23:31 p87 kernel: [17274564.005034] audit: type=1400 audit(1504239811.140:793): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=18952 comm="apparmor_parser" Sep 1 14:23:31 p87 kernel: [17274564.019911] audit: type=1400 audit(1504239811.156:794): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=18952 comm="apparmor_parser" Sep 1 14:23:31 p87 kernel: [17274564.324291] KVM guest htab at c079a100 (order 29), LPID 3 Sep 1 14:23:45 p87 kernel: [17274578.483572] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:53 p87 kernel: [17274766.572284] br0: port 4(vnet2) entered disabled state Sep 1 14:26:53 p87 kernel: [17274766.579930] device vnet2 left promiscuous mode Sep 1 14:26:53 p87 kernel: [17274766.579932] br0: port 4(vnet2) entered disabled state Sep 1 14:26:54 p87 kernel: [17274767.303109] audit: type=1400 audit(1504240014.441:795): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22668 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.917394] audit: type=1400 audit(1504240016.053:796): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22672 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.917673] audit: type=1400 audit(1504240016.053:797): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=22672 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.982783] device vnet2 entered promiscuous mode Sep 1 14:26:56 p87 kernel: [17274768.994891] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:56 p87 kernel: [17274768.994902] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:56 p87 kernel: [17274769.535982] audit: type=1400 audit(1504240016.673:798): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22702 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274769.546719] audit: type=1400 audit(1504240016.685:799): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=22702 comm="apparmor_parser" Sep 1 14:26:57 p87 kernel: [17274769.861666] KVM guest htab at c079a100 (order 29), LPID 3 Sep 1 14:27:11 p87 kernel: [17274784.050382] br0: port 4(vnet2) entered forwarding state Sep 1 14:28:30 p87 kernel: [17274863.605174] Unable to handle kernel paging request for data at address 0x0008 Sep 1 14:28:30 p87 kernel: [17274863.605188] Faulting instruction address: 0xc044edcc Sep 1 14:28:30 p87 kernel: [17274863.605195] Oops: Kernel access of bad area, sig: 11 [#1] Sep 1 14:28:30 p87 kernel: [17274863.605199] SMP NR_CPUS=2048 NUMA PowerNV Sep 1 14:28:30 p87 kernel: [17274863.605206] Modules linked in: tcp_diag inet_diag ebtable_filter ebtables binfmt_misc veth xfrm_user xfrm_algo vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masq
[Kernel-packages] [Bug 1715015] Re: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration ca
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1715015 Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Incomplete Bug description: Found during update: sudo apt-get install update-manager ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-83-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 4 16:01:35 2017 DuplicateSignature: package:linux-image-extra-3.13.0-83-generic:(not installed):package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=/dev/mapper/katelt--vg-swap_1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 2537WGY ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-83-generic root=/dev/mapper/hostname--vg-root ro splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-08-22 (378 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET81WW (1.41 ) dmi.board.name: 2537WGY 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:bvr6IET81WW(1.41):bd02/09/2012:svnLENOVO:pn2537WGY:pvrThinkPadT410:rvnLENOVO:rn2537WGY:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537WGY dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715051] Re: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'h
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1715051 Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Incomplete Bug description: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-libc-dev:amd64 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yash 1710 F pulseaudio Date: Tue Sep 5 08:44:43 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-09-05 08:43:58 Commandline: /usr/bin/unattended-upgrade Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic) Upgrade: python3-jwt:amd64 (1.3.0-1, 1.3.0-1ubuntu0.1), linux-image-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), liblouis9:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), python3-louis:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.78-0ubuntu0.16.04.1293, 60.0.3112.113-0ubuntu0.16.04.1298), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), liblouis-data:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-headers-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35) DuplicateSignature: package:linux-libc-dev:amd64:4.4.0-93.116 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package linux-libc-dev:amd64 (--configure): package linux-libc-dev:amd64 is not ready for configuration ErrorMessage: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2b605a61-78e4-48e2-b997-b7b02b7855d6 InstallationDate: Installed on 2017-08-29 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7592 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P26 (MS-7592) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.8:bd08/26/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715175] Re: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548]
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.13 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.13 ** 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/1715175 Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] Status in linux package in Ubuntu: Incomplete Bug description: I don't know ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1238 F pulseaudio adezelin 1874 F pulseaudio /dev/snd/controlC0: gdm1238 F pulseaudio adezelin 1874 F pulseaudio Date: Tue Sep 5 16:16:19 2017 Failure: oops HibernationDevice: RESUME=UUID=c8d20e0d-bbcf-4373-b706-c920d1bcaf2b InstallationDate: Installed on 2017-09-02 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=696c9898-0f42-49d2-a274-d363e68e88db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715088] Re: Virtual box hangs, kernel BUG at /build/linux-nhaT8l/linux-4.10.0/drivers/nvme/host/pci.c:567
** 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/1715088 Title: Virtual box hangs, kernel BUG at /build/linux- nhaT8l/linux-4.10.0/drivers/nvme/host/pci.c:567 Status in linux package in Ubuntu: Incomplete Bug description: While moving to a snapshot in VirtualBox, nothing happens and the kern.log contains this bug: 333] kernel BUG at /build/linux-nhaT8l/linux-4.10.0/drivers/nvme/host/pci.c:567! Sep 4 08:46:25 robuntu kernel: [ 444.745359] invalid opcode: [#1] SMP ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raudenaerde 2260 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 5 10:07:06 2017 HibernationDevice: RESUME=UUID=410fffc2-673e-4862-a19f-f30d149e2f00 InstallationDate: Installed on 2017-01-26 (221 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20H5CTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-20 (137 days ago) dmi.bios.date: 12/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R0DET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0DET54W(1.54):bd12/08/2016:svnLENOVO:pn20H5CTO1WW:pvrThinkPadE570:rvnLENOVO:rn20H5CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20H5CTO1WW dmi.product.version: ThinkPad E570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715113] Re: Acer Aspire 5220 touchpad no longer works in Artful Ubuntu MATE beta
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 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.13 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715113 Title: Acer Aspire 5220 touchpad no longer works in Artful Ubuntu MATE beta Status in linux package in Ubuntu: Incomplete Bug description: I have an old Acer Aspire 5220, and after the harddisk died I decided to install the Artful beta of Ubuntu MATE. Everything except the touchpad works as before but the touchpad doesn't work, I had to plug in an external USB mouse to use the system. This worked with Ubuntu 17.04 which I was running before. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: th 1222 F pulseaudio CurrentDesktop: MATE Date: Tue Sep 5 11:53:22 2017 HibernationDevice: RESUME=UUID=5f3d250a-5828-4be6-ab4f-e2955490895d MachineType: Acer Aspire 5220 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.33 dmi.board.name: Fuquene dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.33:bd05/06/2008:svnAcer:pnAspire5220:pvrV1.32:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5220 dmi.product.version: V1.32 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715064] Re: 17.10 fails to boot on POWER9 DD2.0 with Deep stop states
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Artful)
Importance: High
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: 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/1715064
Title:
17.10 fails to boot on POWER9 DD2.0 with Deep stop states
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Artful:
Triaged
Bug description:
== Comment: #0 - Ranjal G. Shenoy
On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the
17.10 kernel Ubuntu-4.12.0-12.13 fails to boot.
It requires the following upstream fixes to be backported.
1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize
core_idle_state_ptr")
2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore &
Per-core SPRs restore")
3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from
deep-stop")
4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle
states via stop API.")
5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for
restoring state on P9 DD1")
6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't
stop time")
7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT
states when stop-api fails")
8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for
stop4 cpuidle")
9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api
only on Hotplug")
10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear
LPCR[PECE1] via stop-api only for deep state offline")
Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in
powerpc/linux.git -next branch. and 10) is posted upstream which fixes
9).
These patches have been backported on top of Ubuntu-4.12.0-12.13 and
tested on Boston where they are working as expected.
== Comment: #1 - Ranjal G. Shenoy
The lower 8 bits of core_idle_state_ptr tracks the number of non-idle
threads in the core. This is supposed to be initialized to bit-map
corresponding to the threads_per_core. However, currently it is
initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for
POWER8 which has 8 threads per core, but not for POWER9 which has 4
threads per core.
As a result, on POWER9, core_idle_state_ptr gets initialized to
0xFF. In case when all the threads of the core are idle, the bits
corresponding tracking the idle-threads are non-zero. As a result, the
idle entry/exit code fails to save/restore per-core hypervisor state
since it assumes that there are threads in the cores which are still
active.
Fix this by correctly initializing the lower bits of the
core_idle_state_ptr on the basis of threads_per_core.
Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle:
Correctly initialize core_idle_state_ptr")
== Comment: #2 - Ranjal G. Shenoy
On POWER8, in case of
- nap: both timebase and hypervisor state is retained.
- fast-sleep: timebase is lost. But the hypervisor state is retained.
- winkle: timebase and hypervisor state is lost.
Hence, the current code for handling exit from a idle state assumes
that if the timebase value is retained, then so is the hypervisor
state. Thus, the current code doesn't restore per-core hypervisor
state in such cases.
But that is no longer the case on POWER9 where we do have stop states
in which timebase value is retained, but the hypervisor state is
lost. So we have to ensure that the per-core hypervisor state gets
restored in such cases.
Fix this by ensuring that even in the case when timebase is retained,
we explicitly check if we are waking up from a deep stop that loses
per-core hypervisor state (indicated by cr4 being eq or gt), and if
this is the case, we restore the per-core hypervisor state.
Cherry-picked from commit ec4867355244 ("powerpc/powernv/idle:
Decouple Timebase restore & Per-core SPRs restore")
== Comment: #3 - Ranjal G. Shenoy
On wakeup from a deep stop state which is supposed to lose the
hypervisor state, we don't restore the LPCR to the old value but set
it to a "sane" value via cur_cpu_spec->cpu_restore().
The problem is that the "sane" value doesn't include UPRT and the HR
bits which are required to run correctly in Radix mode.
Fix this on POWER9 onwards by restoring the LPCR value whatever it was
before executing the stop instruction.
Cherr
[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size
I built Artful, Zesty and Xenial test kernels with commit e89ce1f89f6. The test kernels can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1713884/ Can these kernels be tested to see if they resolve this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713884 Title: [CIFS] Fix maximum SMB2 header size Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Bug description: Currently the maximum size of SMB2/3 header is set incorrectly which leads to hanging of directory listing operations on encrypted SMB3 connections. Fix this by setting the maximum size to 170 bytes that is calculated as RFC1002 length field size (4) + transform header size (52) + SMB2 header size (64) + create response size (56). https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de This applies across the board 3.16, 4.4, 4.10, artful, and azure. Microsoft would be happy to help test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626984 Title: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts- xenial-4.4.0/security/apparmor/include/context.h:69! Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Zesty: New Bug description: I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 4.4.0-38-generic, it get oops while copying /sys/module/apparmor/parameters/audit. and it also can be triggered with cat /sys/module/apparmor/parameters/audit. [ 213.174092] [ cut here ] [ 213.174130] kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69! [ 213.174187] invalid opcode: [#1] SMP [ 213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc parport psmouse virtio_scsi floppy [ 213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic #57~14.04.1-Ubuntu [ 213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014 [ 213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 8800399c4000 [ 213.174419] RIP: 0010:[] [] aa_current_raw_label.part.6+0x4/0x6 [ 213.174478] RSP: 0018:8800399c7d60 EFLAGS: 00010246 [ 213.174506] RAX: RBX: 88003a426000 RCX: 88003e3802a0 [ 213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 88003a426000 [ 213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: [ 213.174614] R10: 1000 R11: 0246 R12: 81e44ae0 [ 213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 88003c2b2e40 [ 213.174702] FS: 7f7bea106740() GS:88003fc0() knlGS: [ 213.174743] CS: 0010 DS: ES: CR0: 80050033 [ 213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 06f0 [ 213.174819] Stack: [ 213.174832] 8800399c7d88 8136d58a 88003a426000 88003a426000 [ 213.174885] 88003e3802a0 8800399c7da0 8136fda2 88003e39c5f0 [ 213.174928] 8800399c7dd0 8109a7e4 88003c2b2e40 81a170c0 [ 213.174971] Call Trace: [ 213.174996] [] policy_view_capable+0x1ba/0x220 [ 213.175030] [] param_get_audit+0x12/0x50 [ 213.175062] [] param_attr_show+0x54/0xa0 [ 213.175092] [] module_attr_show+0x1d/0x30 [ 213.175130] [] sysfs_kf_seq_show+0xc2/0x1a0 [ 213.175162] [] kernfs_seq_show+0x23/0x30 [ 213.175199] [] seq_read+0xe5/0x350 [ 213.175227] [] kernfs_fop_read+0x10d/0x170 [ 213.176170] [] __vfs_read+0x18/0x40 [ 213.177101] [] vfs_read+0x7f/0x130 [ 213.178016] [] SyS_read+0x46/0xa0 [ 213.178932] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e [ 213.182634] RIP [] aa_current_raw_label.part.6+0x4/0x6 [ 213.183528] RSP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712724] Re: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c
Thanks for the feedback Gerald. I believe we are about to do the switch to 4.13 in Artful . That will contain the fix. So all we need to do is to re-test once that switch is made. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
@zyga those are both good questions. - Detection functionality is included in kernel patches. There's a new seccomp(2) operation to check if the log action is available and an added test to ensure that there's a certain combination of valid/invalid seccomp(2) arguments that can be used to detect if the log filter flag is available. Both of these checks will be embedded into libseccomp and the checks will be carried out when the calling code specifies actions and filter flags. - Making the necessary libseccomp-golang changes is something that I plan to do. I need to hear back from the libseccomp PR first and then will proceed to make the libseccomp-golang changes that match the libseccomp changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1567597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715175] 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/1715175 Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] Status in linux package in Ubuntu: Confirmed Bug description: I don't know ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1238 F pulseaudio adezelin 1874 F pulseaudio /dev/snd/controlC0: gdm1238 F pulseaudio adezelin 1874 F pulseaudio Date: Tue Sep 5 16:16:19 2017 Failure: oops HibernationDevice: RESUME=UUID=c8d20e0d-bbcf-4373-b706-c920d1bcaf2b InstallationDate: Installed on 2017-09-02 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=696c9898-0f42-49d2-a274-d363e68e88db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712254] Re: blktrace-smoke-test failed on s390x LPAR / zKVM with Xenial
Hi there, did this fix address the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712254 Title: blktrace-smoke-test failed on s390x LPAR / zKVM with Xenial Status in linux package in Ubuntu: Fix Committed Bug description: This test failed on Xenial with: FAILED (expecting at least 1024 block traces events from the dd process, got 0) FAILED (expecting at least 1024 block read traces events, got 107) FAILED (expecting at least 1024 block write traces events, got 8) Fail rate 2 out of 2 on each node (s2lp3 and s2lp6g001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714420] Re: kernel oops - kvm guest started at boot time
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714420 Title: kernel oops - kvm guest started at boot time Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: [SRU Justification] [Impact] ppc64le system OOPSes shortly after boot when KVM guests are started. [Fix] Cherry-pick patch e47057151422a67ce08747176fa21cb3b526a2c9 [Testcase] Tested at IBM - boot a machine with a KVM guest configured to start at boot. Without this patch, observe OOPS, with this patch, observe no OOPS. [Regression Potential] Patch is contained in arch/powerpc; so regression potential limited to that arch. Patch accepted to kernel stable trees, suggesting others also believe it to be of low risk. [Original Report] [0.00] Linux version 4.4.0-93-generic (buildd@bos01-ppc64el-025) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017 (Ubuntu 4.4.0-93.116-generic 4.4.79) ... [ 380.184554] KVM guest htab at c0799900 (order 29), LPID 2 [ 380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, MSR=90009033 [ 380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2] [ 380.527775] SMP NR_CPUS=2048 NUMA PowerNV [ 380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel udp_tunnel ipr [ 380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G D 4.4.0-93-generic #116-Ubuntu [ 380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: c01fb2428000 [ 380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: d0003aad7e40 [ 380.528997] REGS: c01fb242b7b0 TRAP: 0f60 Tainted: G D (4.4.0-93-generic) [ 380.529076] MSR: 90009033 CR: 22024848 XER: [ 380.529247] CFAR: d0003aad7ea4 SOFTE: 1 GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 c01fdbf6 GPR04: c01f8580 c01fb242bbc0 GPR08: 0001 c3c389b0 0001 d00037d578f8 GPR12: d0003aad7e40 cfb4e400 001f GPR16: 3fff7206 0080 3fff892c4390 3fff7285f200 GPR20: 010009988430 0100099affd0 3fff7285eb60 100c1ff0 GPR24: 3bcf4e10 3fff72040028 c01fdbf6 GPR28: c01f8580 c01fdbf6 c01f8580 [ 380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 380.530245] Call Trace: [ 380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 (unreliable) [ 380.530353] [c01fb242bb70] [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 380.530436] [c01fb242bba0] [d00037d4f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 380.530519] [c01fb242bbe0] [d00037d43918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0 [ 380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0 [ 380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4 [ 380.530837] Instruction dump: [ 380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 380.531350] ---[ end trace 8f9b3b82f9a07d76 ]--- Needs kernel patch e47057151422a67ce08747176fa21cb3b526a2c9 according to Cyril ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-93-generic 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 1 15:03 seq crw-rw 1 root audio 116, 33 Sep 1
[Kernel-packages] [Bug 1715175] [NEW] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548]
Public bug reported: I don't know ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1238 F pulseaudio adezelin 1874 F pulseaudio /dev/snd/controlC0: gdm1238 F pulseaudio adezelin 1874 F pulseaudio Date: Tue Sep 5 16:16:19 2017 Failure: oops HibernationDevice: RESUME=UUID=c8d20e0d-bbcf-4373-b706-c920d1bcaf2b InstallationDate: Installed on 2017-09-02 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=696c9898-0f42-49d2-a274-d363e68e88db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops artful 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/1715175 Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] Status in linux package in Ubuntu: New Bug description: I don't know ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1238 F pulseaudio adezelin 1874 F pulseaudio /dev/snd/controlC0: gdm1238 F pulseaudio adezelin 1874 F pulseaudio Date: Tue Sep 5 16:16:19 2017 Failure: oops HibernationDevice: RESUME=UUID=c8d20e0d-bbcf-4373-b706-c920d1bcaf2b InstallationDate: Installed on 2017-09-02 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic root=UUID=696c9898-0f42-49d2-a274-d363e68e88db ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [pool:2548] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697132] Re: CPU Cores Stalls/Lock
Just to factor out any specific BIOS/CPU issues, can you try with the kernel option: processor.max_cstate=1 Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash processor.max_cstate=1" then run: sudo update-grub and reboot. I just want to ensure that the hangs aren't caused by the CPUs going to a C state that causes this hang. -- 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/1697132 Title: CPU Cores Stalls/Lock Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Triaged Bug description: CPU Stalls or Locks up after a random period of time. Can not trace issue to high resources or heat. System will crash while sitting essentially idle. Sometimes system will crash after a few minutes some times it will take days. A large file transfer will usually force the crash though. I have been having similar issue since Ubuntu 14.04. I have upgrade to every version along the way to 17.04 with the same issue. I have replaced every piece of hardware except HDD. MB, Proc, power supply, memory, video card. With and without AMD micro code. This is a server so no GUI. I've tried upstream kernels but they don't support ZFS and I haven't had any luck shimming it in. Happy to try newer kernels if someone can provide one with ZFS support. Jun 9 18:54:57 TheSource kernel: [46465.931527] INFO: rcu_sched detected stalls on CPUs/tasks: Jun 9 18:54:57 TheSource kernel: [46465.931583]9-...: (12 GPs behind) idle=f03/1/0 softirq=261811/261811 fqs=6599 Jun 9 18:54:57 TheSource kernel: [46465.931624](detected by 0, t=15002 jiffies, g=380049, c=380048, q=118270) Jun 9 18:54:57 TheSource kernel: [46465.931665] Task dump for CPU 9: Jun 9 18:54:57 TheSource kernel: [46465.931666] swapper/9 R running task0 0 1 0x0008 Jun 9 18:54:57 TheSource kernel: [46465.931670] Call Trace: Jun 9 18:54:57 TheSource kernel: [46465.931677] ? cpuidle_enter_state+0x122/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931680] ? cpuidle_enter_state+0x110/0x2c0 Jun 9 18:54:57 TheSource kernel: [46465.931683] ? cpuidle_enter+0x17/0x20 Jun 9 18:54:57 TheSource kernel: [46465.931685] ? call_cpuidle+0x23/0x40 Jun 9 18:54:57 TheSource kernel: [46465.931688] ? do_idle+0x189/0x200 Jun 9 18:54:57 TheSource kernel: [46465.931690] ? cpu_startup_entry+0x71/0x80 Jun 9 18:54:57 TheSource kernel: [46465.931693] ? start_secondary+0x154/0x190 Jun 9 18:54:57 TheSource kernel: [46465.931696] ? start_cpu+0x14/0x14 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.10.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Fri Jun 9 20:17:45 2017 InstallationDate: Installed on 2017-06-03 (6 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Micro-Star International Co., Ltd MS-7A32 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=bba67c63-3cd9-4475-bf3a-a0890087330d ro RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor
[Kernel-packages] [Bug 1704720] Re: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11
Problem solved, thanks! ** Changed in: linux (Ubuntu) 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/1704720 Title: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11 Status in linux package in Ubuntu: Fix Released Bug description: After bug 1699755, this test was found failed on Artful again with kernel 4.11.0-11 $ dmesg | grep lttng [ 8282.279726] lttng_kretprobes: loading out-of-tree module taints kernel. [ 8282.279754] lttng_kretprobes: module verification failed: signature and/or required key missing - tainting kernel [ 8282.282192] lttng_tracer: Unknown symbol lttng_ftrace_unregister (err 0) [ 8282.282205] lttng_tracer: Unknown symbol lttng_ftrace_register (err 0) [ 8282.282216] lttng_tracer: Unknown symbol lttng_ftrace_destroy_private (err 0) $ sudo ./ubuntu_lttng_smoke_test.sh == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 04:00 seq crw-rw 1 root audio 116, 33 Jul 17 04:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 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: Date: Mon Jul 17 06:22:17 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: '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.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/1704720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715063] Re: ubuntu_blktrace_smoke_test failed with Trusty kernel
Patch applied to autotest-client-test repo. Thanks ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715063 Title: ubuntu_blktrace_smoke_test failed with Trusty kernel Status in linux package in Ubuntu: Fix Released Bug description: ubuntu_blktrace_smoke_test failed with: Running '/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh' PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-3.13.0-130-generic) FAILED (cannot mkfs test loop image) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944743/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944741/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944742/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944735/+files/JournalErrors.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/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944740/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944739/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944734/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944738/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944736/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944737/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
apport information ** Tags added: apport-collected zesty ** Description changed: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend - when I close the lid now it gives me a password to login when I open the - lid, but I am not sure if it is sleeping properly. Please assist, as I - do not want my laptop battery damaged by this heat again. + when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. + --- + ApportVersion: 2.20.4-0ubuntu4.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: shawn 1786 F pulseaudio + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-09-04 (1 days ago) + InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:670c Microdia + Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 13 9360 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-33-generic N/A + linux-backports-modules-4.10.0-33-generic N/A + linux-firmware 1.164.1 + Tags: zesty + Uname: Linux 4.10.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/02/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.1.0 + dmi.board.name: 05JK94 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: XPS 13 9360 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944731/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256colo
[Kernel-packages] [Bug 1715146] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944732/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944733/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] 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 1715146 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/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntubudgie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715145] Re: linux: 4.13.0-9.10 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.13.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-phase:Packaging + kernel-phase-changed:Tuesday, 05. September 2017 13:00 UTC ** Description changed: This bug is for tracking the 4.13.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Tuesday, 05. September 2017 13:00 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715145 Title: linux: 4.13.0-9.10 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.13.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Tuesday, 05. September 2017 13:00 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1715145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715145] [NEW] linux: 4.13.0-9.10 -proposed tracker
Public bug reported: This bug is for tracking the 4.13.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Artful) Importance: Medium Status: Confirmed ** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Tags added: artful ** Changed in: linux (Ubuntu Artful) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715145 Title: linux: 4.13.0-9.10 -proposed tracker Status in Kernel Development Workflow: In Progress Statu
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Attached kern.log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944721/+files/kern.log -- 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/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: New Status in linux-raspi2 source package in Xenial: Confirmed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 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: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
We have found this issue on 4.4.0-92 too. But only when the systems were put under stress. Reverting back to 4.4.0-57 resolved it. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944720/+files/dmesg.txt -- 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/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Status in linux-aws source package in Xenial: New Status in linux-raspi2 source package in Xenial: Confirmed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 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: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713458] Re: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1713456 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 05. September 2017 12:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1713456 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 05. September 2017 12:31 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1713458 Title: linux-lts-trusty: 3.13.0-130.179~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1713456 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/1713458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic
For reference; 4.13.0-041300-generic also BOOTS fine on my machine which fails with 4.9, 4.10 and 4.11. I didn't try 4.12 but Hagen says it works fine. Hopefully we can figure out where the fix is so it can be back-ported to stable 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/1697556 Title: Computer freezes after login - 4.10.0-22-generic Status in linux package in Ubuntu: Confirmed Bug description: I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days ago. Login worked fine too. A couple of days later I installed the suggested kernel update "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer freezes right after login (i.e. after pressing enter, the background image with the mouse is shown, no responses to any key strokes). Syslog excerpt: Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672] Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf intel_lpss_pci intel_pch_thermal Jun 12 22:12:48 computername kernel: [ 47.603422] hci_uart btbcm btqca btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid pinctrl_sunrisepoint video wmi pinctrl_intel fjes Jun 12 22:12:48 computername kernel: [ 47.603453] CPU: 1 PID: 1672 Comm: Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu Jun 12 22:12:48 computername kernel: [ 47.603453] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017 Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not observed with 4.10.0-21-generic. As I was not able to login to my computer I am writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore the information attached through the "ubuntu-bug linux" command here, are referring to the kernel that is actually working. I decided to nonetheless include that information as it might contain other kernel unrelated information that would help you troubleshooting. Please see attached file "syslog-4.10.0-22-generic-freeze-after- login.log" for the full syslog. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hkuehn 1796 F pulseaudio CurrentDesktop: GNOME Date: Mon Jun 12 23:17:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 05FFDN dmi.boa
[Kernel-packages] [Bug 1696673] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Description changed: - idk - - ProblemType: Package - DistroRelease: Ubuntu 17.04 - Package: linux-image-4.10.0-22-generic (not installed) - ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 - Uname: Linux 4.10.0-21-generic x86_64 - ApportVersion: 2.20.4-0ubuntu4.1 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: at0m1que 1733 F pulseaudio - /dev/snd/controlC0: at0m1que 1733 F pulseaudio - Date: Wed Jun 7 21:05:55 2017 - ErrorMessage: subprocess new pre-installation script returned error exit status 128 - HibernationDevice: RESUME=UUID=30cb6637-b58b-4a1e-9abc-3e3d425029ff - InstallationDate: Installed on 2017-04-19 (49 days ago) - InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) - IwConfig: - lono wireless extensions. - - enp5s0no wireless extensions. - MachineType: MSI MS-7693 - ProcFB: 0 nouveaufb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=a830e8e1-6eeb-4b40-b216-b4939aacf5d2 ro quiet splash vt.handoff=7 - PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. - RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 - RfKill: - - SourcePackage: linux - Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 03/28/2013 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: V10.3 - dmi.board.asset.tag: To be filled by O.E.M. - dmi.board.name: 970A-G43 (MS-7693) - dmi.board.vendor: MSI - dmi.board.version: 3.0 - dmi.chassis.asset.tag: To Be Filled By O.E.M. - dmi.chassis.type: 3 - dmi.chassis.vendor: MSI - dmi.chassis.version: 3.0 - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.3:bd03/28/2013:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: - dmi.product.name: MS-7693 - dmi.product.version: 3.0 - dmi.sys.vendor: MSI + hh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696673 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: hh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620525] Re: sbuild with overlayfs fails in yakkety
** Changed in: dpkg (Debian) Status: Fix Released => 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/1620525 Title: sbuild with overlayfs fails in yakkety Status in dpkg package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in dpkg source package in Yakkety: Invalid Status in linux source package in Yakkety: Invalid Status in dpkg package in Debian: Confirmed Bug description: overlayfs does not support renaming directories when the directories live in the lower filesystem: * Directory renames only allowed on "pure upper" (already created on * upper filesystem, never copied up). Directories which are on lower or * are merged may not be renamed. For these -EXDEV is returned and * userspace has to deal with it. This means, when copying up a * directory we can rely on it and ancestors being stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1620525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
