[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9
Tried the command: sudo make -C linux/tools/testing/selftests TARGETS=powerpc run_tests With the upstream linux tree, it works. But it's not working with the current Cosmic tree, re-open the linux task and starting the bisect process. ** Changed in: linux (Ubuntu) Status: Invalid => 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/1808318 Title: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Bug description: This test passed with 4.18.0-12 on the last cycle [1] But failed with the proposed 4.18.0-13 this time. Test failed to build because of a missing include file: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory Tried to reproduce this cycle with 4.18.0-12 first and this can be reproduced as well. 39. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 40. BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all 41. make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 42. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned 43. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned 44. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned 45. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned 46. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler 47. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 48. make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 49. stderr: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory 51. make[1]: *** No rule to make target '../../../../scripts/subarch.include'. 52. make[1]: Failed to remake makefile '../../../../scripts/subarch.include'. 53. make: *** [Makefile:38: alignment] Error 2 [1] http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 13 10:20 seq crw-rw 1 root audio 116, 33 Dec 13 10:20 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser',
[Kernel-packages] [Bug 1708852] Re: Touchpad not detected
** Description changed: SRU Justifications: - [Impact] + [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 -- You 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 Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: 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:
[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
You should be able to open the link required by apport-collect by copying and pasting it to another machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808520] Re: [UBUNTU] zkey: Enhance error message about missing CCA library.
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808520 Title: [UBUNTU] zkey: Enhance error message about missing CCA library. Status in Ubuntu on IBM z Systems: Triaged Status in s390-tools package in Ubuntu: New Bug description: Description: zkey: Enhance error message about missing CCA library. Symptom: "zkey-cryptsetup reencipher" fails with missing library and confusing error message. Problem: The "zkey reencipher" command as well as the "zkey-cryptsetup reencipher" command requires the IBM CCA Host Libraries and Tools package to be installed. This is a closed source library that is not distributed by the distributions, but must be downloaded separately from an IBM web page. Solution: Enhance the error message to point to the web page where the package can be downloaded. Reproduction: Run the "zkey-cryptsetup reencipher" or "zkey reencipher" command without having installed the IBM CCA Host Libraries and Tools package. Upstream commit(s): 5a10aa73a97b18bf572523e7f86d48797071fb38 package: s390-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1808520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@ALinuxUser: There are 2 modes for touchpad, One is PS/2 mode, the other is smbus mode. 1, Old touchpad firmware: touchpad can *not* work in PS/2 mode. Only smbus mode is available 2, latest touchpad firmware: Both PS/2 and smbus work well except after S3. For now I didn't reproduce touchpad lost issue after S3 on PS/2 mode. and dr_strangehate confirm PS/2 works well from S3 after updated to latest firmware. >From your log, touchpad firmware is old ( not updated to latest version). But you used PS/2 mode, it looks like your touchpad worked on PS/2 mode. This should not be expected on old firmware. And for your log, it is not completed, it didn't show any issues of touchpad. For smbus mode, there should be some firmware/driver issue, not found yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root
[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9
After reading the kernel selftest document, I think this should be fixed from out tool https://www.kernel.org/doc/html/v4.16/dev-tools/kselftest.html We're running a subtest with: sudo make -C linux/tools/testing/selftests/$SUBTEST all run_tests Base on the document, it should be: sudo make -C tools/testing/selftests TARGETS=$SUBTEST run_tests ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808318 Title: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: This test passed with 4.18.0-12 on the last cycle [1] But failed with the proposed 4.18.0-13 this time. Test failed to build because of a missing include file: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory Tried to reproduce this cycle with 4.18.0-12 first and this can be reproduced as well. 39. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 40. BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all 41. make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 42. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned 43. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned 44. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned 45. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned 46. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler 47. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 48. make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 49. stderr: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory 51. make[1]: *** No rule to make target '../../../../scripts/subarch.include'. 52. make[1]: Failed to remake makefile '../../../../scripts/subarch.include'. 53. make: *** [Makefile:38: alignment] Error 2 [1] http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio
[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
My server doesn't have a graphical UI and the apport-collect did not work. The output of lsmod is attached. ** Attachment added: "lsmod.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+attachment/531/+files/lsmod.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9
** Description changed:
== Justification ==
Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")
introduced a requirement that Makefiles more than one level below the
selftests directory need to define top_srcdir, but it didn't update
any of the powerpc Makefiles.
This broke building all the powerpc selftests with eg:
- make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
- BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
- make[2]: Entering directory
'/src/linux/tools/testing/selftests/powerpc/alignment'
- ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
- make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
- make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
- Makefile:38: recipe for target 'alignment' failed
-
+ make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
+ BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
+ make[2]: Entering directory
'/src/linux/tools/testing/selftests/powerpc/alignment'
+ ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
+ make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
+ make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
+ Makefile:38: recipe for target 'alignment' failed
== Fix ==
7e0cf1c983b5 (selftests/powerpc: Fix Makefiles for headers_install change)
It can be cherry-picked for Cosmic. And it's already landed in Disco.
== Regression Potential ==
None, this just fixes the broken build issue for the test. Nothing else will
be affected.
This test passed with 4.18.0-12 on the last cycle [1]
But failed with the proposed 4.18.0-13 this time.
Test failed to build because of a missing include file:
50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
Tried to reproduce this cycle with 4.18.0-12 first and this can be
reproduced as well.
39. make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
40.
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
41. make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
42. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
43. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c
-o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
44. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
45. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c
-o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
46. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
47. make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
48. make: Leaving directory
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@mapengy What you write is unclear. Re 1: Are you asserting that I at present I am using that kernel switch? Or are you rather suggesting that I try out that kernel switch? At any rate: I do use that switch already (on a 4.19 kernel) and, no, the touchpad does not work after suspend. 2: What? As to, 'Could you upload dmesg after touchpad lost ?': I have uploaded it already. If you need me to upload it again or in some new fashion, then please (i) tell me clearly what you need, (ii) give me some indication that going to the trouble will be worth my while. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A
[Kernel-packages] [Bug 1775858] Re: hwclock test failed on Power8 / Power9 system with Bionic kernel
Bug replaced by 1802233, closing this. ** Changed in: ubuntu-kernel-tests Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775858 Title: hwclock test failed on Power8 / Power9 system with Bionic kernel Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: $ /sbin/hwclock --debug --set --date "2004/10/20 04:10:00" hwclock from util-linux 2.31.1 System Time: 1528467313.266333 Trying to open: /dev/rtc0 No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.1 Architecture: ppc64el Date: Fri Jun 8 14:05:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.04 0.67 0.79 1/1401 6691 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-22-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:12:37 UTC 2018 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 0 cpu_freq: min: 2.796 GHz (cpu 79) max: 2.850 GHz (cpu 81) avg: 2.823 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
amdgpu-pci-0300 sensor works only if the gpu is under load -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805849] Re: apt repository in proposed packages availability issue
We have worked around this by doing dry test installs of azure kernel inside
containers, and wait until that is successfully getting installed.
We also tried to look for a set of packages for linux-azure - from linux-azure,
headers, image, but that also didn't help.
I wasn't aware of linux-signed-azure, which isn't installed by default.
We can close this, thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805849
Title:
apt repository in proposed packages availability issue
Status in linux package in Ubuntu:
Triaged
Status in linux-azure package in Ubuntu:
Triaged
Bug description:
We have a watcher that does the following:
- verifies if any linux-azure kernels have been published in proposed repo.
- if it detects one, it will install.
The problem we have is that even though we detect a new kernel in proposed,
the installation of it will fail as there are unmet package dependencies not
being available.
This does resolve after several hours, but the way it works is not reliable
that we see the main package being available, but the packages in the repo are
not ready yet.
So it seems to be a timing issue from the time the kernel is released, and
the time the packages actual get on the repo.
Can you please suggest on some methods to better handle the detect &
install for these, or some suggestions to how we do this from below.
How we search for new kernel availability from proposed:
#apt-cache madison linux-azure | grep ${release}-proposed
But doing an install right after that will fail most of the times if the
kernel was just published:
#apt clean all
#apt -y update
#apt install linux-azure/$release
^ this is after we add the proposed repo in sources.list.
Actual error in the end:
linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
E: Unable to correct problems, you have held broken packages.
This is observed on all LTS versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685442]
Same bug with Linux Mint MATE, kernel 4.15.0-42, GPU Intel Mobile GM965/960, module i915. Adding "video=SVIDEO-1:d" works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A
[Kernel-packages] [Bug 1806409] Re: linux: 4.18.0-13.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** 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 backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 (linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), bug 1806425 (linux-azure-edge) derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 (linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED certification-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806409 Title: linux: 4.18.0-13.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 (linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), bug 1806425 (linux-azure-edge) derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 (linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Had the same problem on Dell Latitude E6400 laptop using Gentoo Linux
with udev versions newer than udev-233. Disabling Bluetooth in BIOS
solved the issue, however, I need bluetooth. Researching the web
resulted in this page:
https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses-
high-cpu-conflict-with-wifi
Following the instructions mentioned by one user in the comments helped
me to solve the cpu load issue with udev-239 and kernel 4.18.17, while
Bluetooth still works.
Run the following command:
/lib/systemd/systemd-udevd -D
This should print garbage in endless loop containing ".../97-hid2hci.rules:"
If so, edit /lib/udev/rules.d/97-hid2hci.rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules
from:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
to:
ACTION=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
And this fixed the issue (after reboot).
Best regards
Florian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759836
Title:
systemd-udevd consumes 100% of CPU
Status in linux:
Confirmed
Status in The Ubuntu Power Consumption Project:
New
Status in bluez package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Bug description:
The systemd-udevd proccess consumes 100% of a thread everytime, but
i'm not noticing any difference in my computer.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 29 08:52:54 2018
InstallationDate: Installed on 2018-03-05 (23 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
MachineType: Dell Inc. Inspiron N5010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 08R0GW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias:
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron N5010
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808520] [NEW] [UBUNTU] zkey: Enhance error message about missing CCA library.
Public bug reported: Description: zkey: Enhance error message about missing CCA library. Symptom: "zkey-cryptsetup reencipher" fails with missing library and confusing error message. Problem: The "zkey reencipher" command as well as the "zkey-cryptsetup reencipher" command requires the IBM CCA Host Libraries and Tools package to be installed. This is a closed source library that is not distributed by the distributions, but must be downloaded separately from an IBM web page. Solution: Enhance the error message to point to the web page where the package can be downloaded. Reproduction: Run the "zkey-cryptsetup reencipher" or "zkey reencipher" command without having installed the IBM CCA Host Libraries and Tools package. Upstream commit(s): 5a10aa73a97b18bf572523e7f86d48797071fb38 package: s390-tools ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-174104 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-174104 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808520 Title: [UBUNTU] zkey: Enhance error message about missing CCA library. Status in linux package in Ubuntu: New Bug description: Description: zkey: Enhance error message about missing CCA library. Symptom: "zkey-cryptsetup reencipher" fails with missing library and confusing error message. Problem: The "zkey reencipher" command as well as the "zkey-cryptsetup reencipher" command requires the IBM CCA Host Libraries and Tools package to be installed. This is a closed source library that is not distributed by the distributions, but must be downloaded separately from an IBM web page. Solution: Enhance the error message to point to the web page where the package can be downloaded. Reproduction: Run the "zkey-cryptsetup reencipher" or "zkey reencipher" command without having installed the IBM CCA Host Libraries and Tools package. Upstream commit(s): 5a10aa73a97b18bf572523e7f86d48797071fb38 package: s390-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Ok, I'll try putting it under load when I have the time. But I thought there were supposed to be more cpu sensors.. or am I wrong? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9
Fix found in the upstream tree: 7e0cf1c983b5b24426d130fd949a055d520acc9a ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808318 Title: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Bug description: This test passed with 4.18.0-12 on the last cycle [1] But failed with the proposed 4.18.0-13 this time. Test failed to build because of a missing include file: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory Tried to reproduce this cycle with 4.18.0-12 first and this can be reproduced as well. 39. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 40. BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all 41. make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 42. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned 43. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned 44. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned 45. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned 46. gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler 47. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment' 48. make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc' 49. stderr: 50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or directory 51. make[1]: *** No rule to make target '../../../../scripts/subarch.include'. 52. make[1]: Failed to remake makefile '../../../../scripts/subarch.include'. 53. make: *** [Makefile:38: alignment] Error 2 [1] http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 13 10:20 seq crw-rw 1 root audio 116, 33 Dec 13 10:20 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9
** Description changed:
+ == Justification ==
+ Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")
+ introduced a requirement that Makefiles more than one level below the
+ selftests directory need to define top_srcdir, but it didn't update
+ any of the powerpc Makefiles.
+
+ This broke building all the powerpc selftests with eg:
+
+ make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
+ BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
+ make[2]: Entering directory
'/src/linux/tools/testing/selftests/powerpc/alignment'
+ ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
+ make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
+ make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
+ Makefile:38: recipe for target 'alignment' failed
+
+
+ == Fix ==
+ 7e0cf1c983b5 (selftests/powerpc: Fix Makefiles for headers_install change)
+ It can be cherry-picked for Cosmic. And it's already landed in Disco.
+
+ == Regression Potential ==
+ None, this just fixes the broken build issue for the test. Nothing else will
be affected.
+
+
+
This test passed with 4.18.0-12 on the last cycle [1]
But failed with the proposed 4.18.0-13 this time.
Test failed to build because of a missing include file:
50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
Tried to reproduce this cycle with 4.18.0-12 first and this can be
reproduced as well.
-
39. make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
40.
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
41. make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
42. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
43. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c
-o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
44. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
45. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c
-o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
46. gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"'
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
47. make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
48. make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
49. stderr:
50. ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or
directory
51. make[1]: *** No rule to make target
'../../../../scripts/subarch.include'.
52. make[1]: Failed to remake makefile
'../../../../scripts/subarch.include'.
53. make: *** [Makefile:38: alignment] Error 2
-
- [1]
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: - promote-to-proposed: Manual kernel-block/kernel-block-ppa present + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: - promote-to-proposed: Manual kernel-block/kernel-block-ppa present + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Tags removed: kernel-block-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Tags removed: kernel-block-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808520] [NEW] [UBUNTU] zkey: Enhance error message about missing CCA library.
You have been subscribed to a public bug: Description: zkey: Enhance error message about missing CCA library. Symptom: "zkey-cryptsetup reencipher" fails with missing library and confusing error message. Problem: The "zkey reencipher" command as well as the "zkey-cryptsetup reencipher" command requires the IBM CCA Host Libraries and Tools package to be installed. This is a closed source library that is not distributed by the distributions, but must be downloaded separately from an IBM web page. Solution: Enhance the error message to point to the web page where the package can be downloaded. Reproduction: Run the "zkey-cryptsetup reencipher" or "zkey reencipher" command without having installed the IBM CCA Host Libraries and Tools package. Upstream commit(s): 5a10aa73a97b18bf572523e7f86d48797071fb38 package: s390-tools ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-174104 severity-high targetmilestone-inin--- -- [UBUNTU] zkey: Enhance error message about missing CCA library. https://bugs.launchpad.net/bugs/1808520 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789227] Re: nvme devices namespace assigned to the wrong controller
This bug was fixed in the package debian-installer - 20101020ubuntu543.4 --- debian-installer (20101020ubuntu543.4) bionic; urgency=medium * build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS without d-i/allow_unauthenticated_ssl in stock initramfs image as in Debian. (LP: #1807023) -- Mauricio Faria de Oliveira Mon, 26 Nov 2018 16:49:46 -0200 ** Changed in: debian-installer (Ubuntu Bionic) Status: Fix Committed => 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/1789227 Title: nvme devices namespace assigned to the wrong controller Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Impact == During device discovery, when multipath is disabled, nvme multipath module will very likely think that the name space on one nvme controller belongs to the other controller. == Fix == Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream From: Keith Busch When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath, namespaces with multiple paths were not creating unique names due to reusing the same instance number from the namespace's head. This patch fixes this by falling back to the non-multipath naming method when the parameter disabled using multipath. Reported-by: Mike Snitzer Signed-off-by: Keith Busch Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1789227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806488 Title: Support non-strict iommu mode on arm64 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [Impact] There's a significant performance gain to be had by removing the need to flush the IOMMU TLB on every unmap. I'm seeing a 25% performance gain w/ fio reads on a single NVMe device. This mode of operation is available for x86 via the "intel_iommu=strict" parameter. This support is now available upstream for ARM platforms via the "iommu.strict=[0|1]" parameter, while keeping the default in strict mode. [Test Case] $ cat fio.rc [global] rw=read direct=1 ioengine=libaio iodepth=2048 numjobs=10 bs=4k group_reporting=1 group_reporting=1 cpumask=0xff runtime=100 loops = 1 [job1] filename=/dev/nvme0n1 [Fix] 44f6876a00e83 iommu/arm-smmu: Support non-strict mode b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode 9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode 68a6efe86f6a1 iommu: Add "iommu.strict" command line option 2da274cdf998a iommu/dma: Add support for non-strict mode 07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook 85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap() [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808592] [NEW] package linux-firmware 1.173.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127
Private bug reported: Created automatically. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Dec 7 09:34:16 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173.2 Setting up linux-firmware (1.173.2) ... awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check ** Information type changed from Public to Private -- 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/1808592 Title: package linux-firmware 1.173.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 Status in linux-firmware package in Ubuntu: New Bug description: Created automatically. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Dec 7 09:34:16 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173.2 Setting up linux-firmware (1.173.2) ... awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux-firmware Title: package linux-firmware 1.173.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1808592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04
P52: "cat /sys/bus/serio/devices/serio1/firmware_id": PNP: LEN2132 PNP0f13 Confirming a fresh install of ubuntu 18.10 works yields a fully functional touchpad but updating (tested with current kernel 4.18.0-12-generic) renders the touchpad unusable. Issuing "sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol'" restores the trackpads functionality for the current session as already described. "dmesg | grep -i elan" yields: [3.167455] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f2001) [3.179490] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x0e. [3.191246] psmouse serio1: elantech: Elan sample query result 00, 28, 96 [3.202881] psmouse serio1: elantech: Trying to set up SMBus access [4.032146] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [4.048144] elan_i2c 0-0015: failed to get resolution: -5 [4.048168] elan_i2c: probe of 0-0015 failed with error -5 after echoing "elantech", dmesg shows [ 2185.669979] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input17 [ 2185.683258] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input16 instead of the former last three lines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 Status in linux package in Ubuntu: Confirmed Bug description: Confirmed affected laptops: ThinkPad: L480 L580 P72 P52 When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag:
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the 4.15.0-1007.7 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: 1806659 - phase: Uploaded - phase-changed: Wednesday, 12. December 2018 19:38 UTC + phase: Promoted to proposed + phase-changed: Friday, 14. December 2018 22:10 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Packages copies requested + automated-testing: Testing FAILED + regression-testing: Testing in progress + verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 14. December 2018 22:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Tags added: kernel-block-proposed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 14. December 2018 22:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Tags added: kernel-block-proposed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) 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/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 14. December 2018 21:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: - promote-to-proposed: Packages copied but not yet published to -proposed + promote-to-proposed: Packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: promote-to-proposed: Packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: - promote-to-proposed: Packages copies requested + promote-to-proposed: Packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 20:11 UTC reason: promote-to-proposed: Packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798776] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2018-12-14 16:44 EDT--- Patch is queued according to maintainer, should be part of 4.21. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798776 Title: kvm_stat : missing python dependency Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: After installing linux-tools-host, the included kvm_stat utility won't work: root@ubuntu:~# kvm_stat -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or directory Reason is that there is apparently no dependency on a python package from the linux-tools-host package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1798776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
I am also affected by this issue, however on a wholly different platform - an intel H370 based motherboard with a Core i3-8100 CPU. It was suggested that I attempt to supress logging output via a sysrq keyboard combo, so I pressed alt+sysrq+0 but this appears to be disabled by default as I saw the following printed to the TTY along with the IRQ handler messages: sysrq: SysRq : This sysrq operation is disabled. It would be great if some proper attention would be paid to this issue as it makes the use of such systems via TTY extremely frustrating. Should I perhaps try the most up to date mainline kernel I can find? Thanks ** Attachment added: "dmesg on cold boot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+attachment/5222398/+files/dmesg-cold.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/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
After upgrade to Ubuntu 18.10 (kernel 4.18.0-12-generic) I got the same touchpad freeze on Asus X540NA and the right click doesn't work at all. [ 1786.393499] input: ELAN1200:00 04F3:3067 Mouse as /devices/pci:00/:00:17.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3067.0001/input/input97 [ 1786.396367] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/82) [ 1786.396462] input: ELAN1200:00 04F3:3067 Touchpad as /devices/pci:00/:00:17.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3067.0001/input/input98 [ 1786.396602] hid-generic 0018:04F3:3067.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3067] on i2c-ELAN1200:00 [ 1786.475422] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466) [ 1786.476119] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/16466) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Florian is dope
i started this thread the day ubuntu 18 was released, I've tried the work around. It solved my problem, so I want to thank the original solution contributor (...forgot which email it was. Read it and implemented it a while ago). but I also thank you Florian for the clear, concise, well articulated, up to date description of the work around. Specifically the line numbers and code diff. much appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780628] Re: linux-4.15.0-23-generic RAID 5 kernel BUG
I have a same problem with the current version of Ubuntu 18.04.1 LTS (Bionic Beaver) with kernel 4.15.0-42-generic. I have a new RAID 5 array with 4 12TB drives. As the array is being initialized, it takes 3 to 10 minutes to reach a kernel bug (under the additional system load less than 1 minute). ** Attachment added: "Call Trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780628/+attachment/575/+files/trace.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/1780628 Title: linux-4.15.0-23-generic RAID 5 kernel BUG Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have a machine running linux-4.15.0-23-generic, and I can reliably trigger a kernel BUG under heavy write I/O using RAID 5. $ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md0 : active raid5 sdd2[1] sda2[0] sdb2[2] sdc2[3] 23440220160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] bitmap: 0/59 pages [0KB], 65536KB chunk unused devices: [35679.932015] [ cut here ] [35679.932017] kernel BUG at /build/linux-uT8zSN/linux-4.15.0/drivers/md/raid5.c:1757! [35679.932044] invalid opcode: [#1] SMP PTI [35679.932054] Modules linked in: xfs nls_iso8859_1 ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm irqbypass intel_cstate intel_rapl_perf snd_timer acpi_pad mei_me mei input_leds mac_hid snd shpchp wmi_bmof intel_pch_thermal soundcore parport_pc parport sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper [35679.932199] cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci pps_core drm libahci wmi video [35679.932229] CPU: 2 PID: 272 Comm: md0_raid5 Not tainted 4.15.0-23-generic #25-Ubuntu [35679.932245] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018 [35679.932266] RIP: 0010:raid_run_ops+0xbcc/0x15f0 [raid456] [35679.932277] RSP: 0018:a95d0133fb30 EFLAGS: 00010006 [35679.932289] RAX: RBX: 96231cf67a34 RCX: [35679.932304] RDX: 96231d2cd7c0 RSI: 962303321380 RDI: 96231d2cd828 [35679.932318] RBP: a95d0133fbe8 R08: 1000 R09: a95d0133fac0 [35679.932333] R10: 1000 R11: 96231d2cd848 R12: 96231d2cda08 [35679.932347] R13: 96231d2cd828 R14: 96231d2cd7c0 R15: 962319bc8000 [35679.932362] FS: () GS:96232e48() knlGS: [35679.932379] CS: 0010 DS: ES: CR0: 80050033 [35679.932391] CR2: 564929900bb8 CR3: 41a0a003 CR4: 003606e0 [35679.932405] Call Trace: [35679.932415] handle_stripe+0x669/0x21c0 [raid456] [35679.932428] handle_active_stripes.isra.62+0x3da/0x5a0 [raid456] [35679.932442] raid5d+0x407/0x5f0 [raid456] [35679.932454] md_thread+0x129/0x170 [35679.932463] ? handle_active_stripes.isra.62+0x5a0/0x5a0 [raid456] [35679.932477] ? md_thread+0x129/0x170 [35679.932487] ? wait_woken+0x80/0x80 [35679.932497] kthread+0x121/0x140 [35679.932505] ? find_pers+0x70/0x70 [35679.932515] ? kthread_create_worker_on_cpu+0x70/0x70 [35679.932527] ret_from_fork+0x35/0x40 [35679.932536] Code: 48 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 9a 09 00 00 48 8b 7d 98 44 89 f1 31 d2 4c 89 e6 e8 9d a9 e7 ff 48 89 45 98 e9 06 f6 ff ff <0f> 0b 0f 0b e9 89 f9 ff ff 8b 4d 90 89 fe e9 7e fd ff ff 4c 8b [35679.932588] RIP: raid_run_ops+0xbcc/0x15f0 [raid456] RSP: a95d0133fb30 [35679.932603] ---[ end trace 22e551ef3119d0b0 ]--- $ cat /proc/version_signature Ubuntu 4.15.0-23.25-generic 4.15.18 --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Reproduced today on MAAS 2.5 / latest Bionic. qemu/maas versions: https://paste.ubuntu.com/p/kDk3c9tVFX/ good vm dump: http://paste.ubuntu.com/p/zTW2p6JGQJ/ good vm log: http://paste.ubuntu.com/p/V7GP9KgP8S/ good vm serial output: http://paste.ubuntu.com/p/FDymQcH8qD/ bad vm dump: http://paste.ubuntu.com/p/ZCv5dv3DTS/ bad vm log: http://paste.ubuntu.com/p/4Zk5qq9TfB/ bad vm serial output: http://paste.ubuntu.com/p/QgbmZsjPPP/ ** Changed in: maas Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: qemu (Ubuntu) Status: Incomplete => New ** Tags added: cpe-onsite ** Tags added: field-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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763387] Re: Bionic HWE kernel (4.15) does not contain the bnx2 (Broadcom NetXtreme II network card) firmware
*** This bug is a duplicate of bug 1763823 *** https://bugs.launchpad.net/bugs/1763823 I believe that this bug should have been fixed by the updates for bug 1763823. Marking as a duplicate, but please let me know if this is still an issue. ** This bug has been marked a duplicate of bug 1763823 Update firmware for 18.04 hwe kernel -- 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/1763387 Title: Bionic HWE kernel (4.15) does not contain the bnx2 (Broadcom NetXtreme II network card) firmware Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-meta-hwe-edge package in Ubuntu: New Bug description: Hello. I have the server equipped with a Broadcom NetXtreme II BCM5708 network card. The server works fine with a standart Xenial kernel (4.4), but fails to boot with linux-image-4.15.0-13-generic kernel. Steps to reproduce: Install linux-image-generic-hwe-16.04-edge and reboot What happens: Server is not able to set up the network interface due to the missing firmware (screenshot attached). Workaround: cp -r -a /lib/firmware/4.4.0-119-generic/bnx2/ /lib/firmware/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic-hwe-16.04-edge 4.15.0.13.39 ProcVersionSignature: Ubuntu 4.15.0-13.14~16.04.1-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Apr 12 16:41:51 2018 InstallationDate: Installed on 2018-02-27 (43 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Dependencies: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=bc2239ba-a70e-477b-8983-58fc2c8782f0 InstallationDate: Installed on 2018-02-27 (178 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: HP ProLiant DL360 G5 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux-meta-hwe-edge PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3265acd8-e900-4343-8400-23905f0e98d9 ro ProcVersionSignature: Ubuntu 4.15.0-13.14~16.04.1-generic 4.15.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial xenial Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-08 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 01/24/2008 dmi.bios.vendor: HP dmi.bios.version: P58 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP58:bd01/24/2008:svnHP:pnProLiantDL360G5:pvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 G5 dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Dependencies: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=bc2239ba-a70e-477b-8983-58fc2c8782f0 InstallationDate: Installed on 2018-02-27 (178 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: HP ProLiant DL360 G5 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux-meta-hwe-edge PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3265acd8-e900-4343-8400-23905f0e98d9 ro ProcVersionSignature: Ubuntu 4.15.0-13.14~16.04.1-generic 4.15.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial xenial Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-08 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 01/24/2008 dmi.bios.vendor: HP dmi.bios.version: P58 dmi.chassis.type: 23
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Setting this back to incomplete for MAAS because there is not enough information to determine this is a MAAS Bug. That said, given that this work with any VM other than one with 2048 of RAM, the issue may appear to be the kernel or libvirt. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Subscribing field-medium as workaround (e.g not to use 2048mb ram VMs) exists, but solution still need to be found. Also, before yesterday (e.g on libvirt 1:2.11+dfsg-1ubuntu7.8 + maas 2.5rc2) worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
siyia (siyia), e-mail has been sent. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808528] [NEW] Update linux-firmware in bionic for 18.10 hwe kernel
Public bug reported: SRU Justification Impact: A 4.18-based hwe kernel has been introduced into bionic. However some of the firmware files it requires are missing from bionic's linux- firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in xenial. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. ** Affects: linux-firmware (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: Invalid ** Affects: linux-firmware (Ubuntu Bionic) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid -- 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/1808528 Title: Update linux-firmware in bionic for 18.10 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: SRU Justification Impact: A 4.18-based hwe kernel has been introduced into bionic. However some of the firmware files it requires are missing from bionic's linux-firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in xenial. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1808528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808412] Re: 4.15.0 memory allocation issue
When the memory allocation was stalled, here is what perf top was giving me: Samples: 483K of event 'cycles:ppp', Event count (approx.): 52114089074 Overhead Shared Object Symbol 28.53% [kernel] [k] total_mapcount 25.34% [kernel] [k] kvm_age_rmapp 13.54% [kernel] [k] slot_rmap_walk_next 11.24% [kernel] [k] kvm_handle_hva_range 6.35% [kernel] [k] rmap_get_first 3.69% [kernel] [k] __x86_indirect_thunk_r13 1.33% [kernel] [k] __isolate_lru_page 0.63% [kernel] [k] isolate_lru_pages.isra.58 0.48% [kernel] [k] page_vma_mapped_walk 0.40% [kernel] [k] __mod_node_page_state 0.35% [kernel] [k] clear_page_erms 0.31% [kernel] [k] shrink_page_list 0.28% [kernel] [k] _find_next_bit 0.27% [kernel] [k] putback_inactive_pages 0.27% [kernel] [k] move_active_pages_to_lru 0.27% [kernel] [k] inactive_list_is_low 0.22% [kernel] [k] __mod_zone_page_state numactl -H when the memorry allocation stalled: root@gpu-compute028:~# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 64288 MB node 0 free: 55983 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 64489 MB node 1 free: 63810 MB node distances: node 0 1 0: 10 21 1: 21 10 root@gpu-compute028:~# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 64288 MB node 0 free: 366 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 64489 MB node 1 free: 63782 MB node distances: node 0 1 0: 10 21 1: 21 10 root@gpu-compute028:~# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 64288 MB node 0 free: 368 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 64489 MB node 1 free: 63757 MB node distances: node 0 1 0: 10 21 1: 21 10 root@gpu-compute028:~# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 64288 MB node 0 free: 368 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 64489 MB node 1 free: 63744 MB node distances: node 0 1 0: 10 21 1: 21 10 root@gpu-compute028:~# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 node 0 size: 64288 MB node 0 free: 366 MB node 1 cpus: 1 3 5 7 9 11 13 15 node 1 size: 64489 MB node 1 free: 63504 MB node distances: node 0 1 0: 10 21 1: 21 10 then i killed the process. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808412 Title: 4.15.0 memory allocation issue Status in linux package in Ubuntu: Confirmed Bug description: My server is : PowerEdge T630 2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz 128G of ram 4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops after about half of the memory. When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long time. I tested kernel : linux-image-4.13.0-37 not affected linux-image-4.13.0-45 not affected linux-image-4.15.0-34 affected linux-image-4.15.0-42 affected After disabling transparent_hugepage on 4.15 everything seems to work correctly. cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808528] Re: Update linux-firmware in bionic for 18.10 hwe kernel
** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808528 Title: Update linux-firmware in bionic for 18.10 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Fix Committed Bug description: SRU Justification Impact: A 4.18-based hwe kernel has been introduced into bionic. However some of the firmware files it requires are missing from bionic's linux-firmware, rendering the relevant hardware inoperable. Fix: Add the missing firmware files. Regression Potential: Most of these files will not be used by the existing kernels in xenial. A few may be, and while regressions are not expected it's possible that new firmware versions might introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1808528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805154]
The GNU_EH_FRAME segment is actually empty in our builds. This breaks unwinding across signal handlers on i386 because the libgcc unwinder does not recognize i386 __kernel_sigreturn as a signal handler frame anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805154 Title: glibc 2.28-0ubuntu1 ADT test failure with linux 4.19.0-5.6 Status in Linux: Confirmed Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in Fedora: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/amd64/g/glibc/20181119_075302_9b2e2@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/g/glibc/20181119_064219_9b2e2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1805154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808609] Re: None of my external drives appear after Linux crash.
I reinstalled Ubuntu MATE 18.10 and updated/upgraded the packages and rebooted. Still none of my external USB 3 drives appear What do I do next to try and get a working computer? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Confirmed Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808609] [NEW] None of my external drives appear after Linux crash.
Public bug reported: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic package-from-proposed ** Attachment added: "Screenshot at 2018-12-14 22-44-18.png" https://bugs.launchpad.net/bugs/1808609/+attachment/5222434/+files/Screenshot%20at%202018-12-14%2022-44-18.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Confirmed Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion:
[Kernel-packages] [Bug 1808609] 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/1808609 Title: None of my external drives appear after Linux crash. Status in linux package in Ubuntu: Confirmed Bug description: First my system became incredibly slow (consistent with the memory leak in Caja). I xKill Caja and then tried to restart it. I then closed every app and tried to do a shutdown. I got a warning that Caja still had processes running preventing shutdown. I chose shut down anyway. I eventually got the progress screen showing that Linux was trying to shut down. After 1 1/2 hours of the progress screen, I manually turned off power. I was able to reboot but all of my external drives are missing. I tried turning off and then back on one drive with no result. When I plug a drive back in I do not feel the vibration caused by the drive spinning up. Nor do I feel the drive do the initial seek. This indicated that Linux is not even attempting to access the drives. Do I have to reinstall Ubuntu MATE 18.10 (again) in order to use external USB drives? The attached screen shots shows only partitions on my two internal hard drives. Gparted does not show the disks. Disks from the Control Center shows only internal devices. Without access to my external drives I am stalled. I can't even do backups. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2606 F pulseaudio /dev/snd/controlC0: robert 2606 F pulseaudio CurrentDesktop: MATE Date: Fri Dec 14 22:38:44 2018 InstallationDate: Installed on 2018-11-30 (14 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1808609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797759] Re: screen goes blank when mate loads - unable to see the login screen
[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/1797759 Title: screen goes blank when mate loads - unable to see the login screen Status in linux package in Ubuntu: Expired Bug description: After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank before the login screen appears. Kernel Linux 4.15.0-36-generic x86_64. It was fine using Ubuntu Mate 16.x. I have found by booting to save mode and select boot from HDD everything works except the font is a bit large and some screens go off the bottom of the screen and I can't view this part of the screen. When checking software & updates there are no additional drivers loaded. The monitor preferences show monitor is known, resolution is 1280 x 800, refresh rates is 0 hz. None of this info can be changed. I have run the software update 3-4 times hoping that it would right itself. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Mon Oct 15 00:25:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:7008] InstallationDate: Installed on 2018-09-01 (43 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.50 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: SGH038PG56 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797828] Re: Kernel Panic at reboot or shutdown
[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/1797828 Title: Kernel Panic at reboot or shutdown Status in linux package in Ubuntu: Expired Bug description: I recive a kernel panel error sometimes when i reboot or shutdown my laptop. cat /proc/version_signature > version.log Ubuntu 4.15.0-36.39-generic 4.15.18 --- [7.644992] [ cut here ] [7.644993] sysfs: cannot create duplicate filename '/devices/pci:00/:00:1a.7/usb1/1-2/1-2:1.0/media0' [7.645012] WARNING: CPU: 1 PID: 302 at /build/linux-39dmni/linux-4.15.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70 [7.645013] Modules linked in: nvidia_uvm(POE) uvcvideo(+) videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 bnep videobuf2_core videodev media snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep kvm_intel kvm irqbypass snd_pcm snd_seq_midi snd_seq_midi_event serio_raw pcmcia snd_rawmidi arc4 iwl3945 snd_seq iwlegacy snd_seq_device btusb nvidia(POE) btrtl snd_timer btbcm btintel mac80211 bluetooth lpc_ich ecdh_generic input_leds yenta_socket pcmcia_rsrc tifm_7xx1 pcmcia_core joydev tifm_core snd cfg80211 soundcore drm shpchp ip6t_REJECT nf_reject_ipv6 sony_laptop nf_log_ipv6 xt_hl ip6t_rt mac_hid nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 [7.645066] xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat sch_fq_codel nf_conntrack_ftp nf_conntrack libcrc32c coretemp parport_pc iptable_filter ppdev lp parport ip_tables x_tables autofs4 uas usb_storage hid_generic usbhid hid psmouse ahci libahci firewire_ohci firewire_core pata_acpi crc_itu_t sky2 video [last unloaded: videobuf2_memops] [7.645092] CPU: 1 PID: 302 Comm: systemd-udevd Tainted: P OE 4.15.0-36-generic #39-Ubuntu [7.645093] Hardware name: Sony Corporation VGN-SZ61MN_B/VAIO , BIOS R0122S5 04/04/2008 [7.645096] RIP: 0010:sysfs_warn_dup+0x56/0x70 [7.645097] RSP: 0018:ad0d40c0b850 EFLAGS: 00010286 [7.645099] RAX: RBX: 94d035d5b000 RCX: 0006 [7.645100] RDX: 0007 RSI: 0086 RDI: 94d03fd16490 [7.645101] RBP: ad0d40c0b868 R08: 0001 R09: 03ba [7.645102] R10: 0001 R11: R12: 94d038909dd8 [7.645103] R13: 94d0301ff088 R14: 94d038b0f810 R15: 94d03003c840 [7.645105] FS: 7f1e1a9b1680() GS:94d03fd0() knlGS: [7.645107] CS: 0010 DS: ES: CR0: 80050033 [7.645108] CR2: 0210baa8 CR3: 0001340f4000 CR4: 06e0 [7.645109] Call Trace: [7.645114] sysfs_create_dir_ns+0x77/0x90 [7.645118] kobject_add_internal+0xac/0x2b0 [7.645119] kobject_add+0x71/0xd0 [7.645123] ? device_private_init+0x23/0x70 [7.645124] device_add+0x12c/0x680 [7.645129] cdev_device_add+0x4e/0x80 [7.645130] ? cdev_init+0x55/0x60 [7.645136] media_devnode_register+0xe7/0x180 [media] [7.645139] __media_device_register+0x77/0x110 [media] [7.645148] uvc_probe+0x96f/0xed0 [uvcvideo] [7.645150] ? kernfs_activate+0x78/0x80 [7.645152] ? kernfs_add_one+0xe4/0x130 [7.645155] usb_probe_interface+0x129/0x300 [7.645159] ? uvc_parse_standard_control+0x1400/0x1400 [uvcvideo] [7.645161] ? usb_probe_interface+0x129/0x300 [7.645163] driver_probe_device+0x31e/0x490 [7.645165] __driver_attach+0xa7/0xf0 [7.645167] ? driver_probe_device+0x490/0x490 [7.645169] bus_for_each_dev+0x70/0xc0 [7.645171] driver_attach+0x1e/0x20 [7.645172] bus_add_driver+0x1c7/0x270 [7.645174] driver_register+0x60/0xe0 [7.645176] usb_register_driver+0x81/0x150 [7.645178] ? 0xc151a000 [7.645179] ? 0xc151a000 [7.645183] uvc_init+0x29/0x1000 [uvcvideo] [7.645186] do_one_initcall+0x52/0x19f [7.645189] ? __vunmap+0x81/0xb0 [7.645191] ? _cond_resched+0x19/0x40 [7.645193] ? kmem_cache_alloc_trace+0xa6/0x1b0 [7.645196] ? do_init_module+0x27/0x209 [7.645198] do_init_module+0x5f/0x209 [7.645200] load_module+0x191e/0x1f10 [7.645203] ? ima_post_read_file+0x96/0xa0 [7.645206] SYSC_finit_module+0xfc/0x120 [7.645208] ? SYSC_finit_module+0xfc/0x120 [7.645210] SyS_finit_module+0xe/0x10 [7.645212] do_syscall_64+0x73/0x130 [7.645214]
[Kernel-packages] [Bug 1797837] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
[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/1797837 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Expired Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797670] Re: upgrading to 16.04 bug
[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/1797670 Title: upgrading to 16.04 bug Status in linux package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-53-generic 3.13.0-53.87 ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: taktak 2369 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 13 05:57:00 2018 HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3 InstallationDate: Installed on 2012-12-06 (2136 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.11 SourcePackage: linux StagingDrivers: keucr UpgradeStatus: Upgraded to trusty on 2018-10-13 (0 days ago) WifiSyslog: Oct 13 05:52:19 Takostro kernel: [ 657.752075] ERROR @wl_dev_intvar_get : error (-1) Oct 13 05:52:19 Takostro kernel: [ 657.752081] ERROR @wl_cfg80211_get_tx_power : error (-1) dmi.bios.date: 09/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 047MWF dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222479/+files/ProcEnviron.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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390, 396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from beta and previously 18.04 as original install) Resolved by switching to lightdm and booting into Cinnamon Desktop instead of Gnome. Mate works as well. Also uncommented "WaylandEnable=false" for future possible use of gdm3 and gnome desktop. Can someone either mark this as "not fixed" or "won't fix" since it's clearly not resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152]
(In reply to Kevin from comment #15) > Jan 11 16:17:44 kernel: [ 2197.614240] lodebug: dev_hold 11 > dst_init > > (after __neigh_create function call, the reference count for loopback device > is incorrectly increased to 13) > > Jan 11 16:20:41 kernel: [ 2374.898917] lodebug: dev_hold 13 > __neigh_create This is hard to believe or explain. The only way to increase the counter is to call dev_hold(), and whenever dev_hold() is called, a message saying so would be logged. The only explanation I can think of would be if the memory area holding the per-cpu counters would have been accidentally overwritten (say by overrun of an array in nearby memory). But a more likely explanation is that there is a missing line in the log, either due to copy and paste error, or because somehow the message never made it to the log buffer (are there still contexts in which printk doesn't work?) Question: do you see the same apparent +2 counter increase whenever you hit the "waiting for to become free" error, or was it a one-time thing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
** Changed in: linux Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222481/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
apport information ** Tags added: apport-collected ** Description changed: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 15 07:22 seq + crw-rw 1 root audio 116, 33 Dec 15 07:22 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc + IwConfig: + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. + MachineType: ASUSTeK COMPUTER INC. P9D-X Series + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash + ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-42-generic N/A + linux-backports-modules-4.15.0-42-generic N/A + linux-firmware 1.173.2 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-42-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 10/13/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0901 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P9D-X Series + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 17 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: P9D-X Series + dmi.product.version: Rev 1.xx + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222474/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error:
[Kernel-packages] [Bug 1808183] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222476/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222475/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222478/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222480/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
I finally managed to work my way through the text based apport-collect and was able to send the data. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222482/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222483/+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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808183] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1808183/+attachment/5222477/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out
Looking at the log file we can see the following:
2018-05-21 09:55:56,514 DEBUG nvidiaUpdate()
2018-05-21 09:55:58,109 INFO no old nvidia driver installed, installing no new
Then looking at DistUpgradeCache from ubuntu-release-upgrader there is
this:
540 # get new detection module and use the modalises files
541 # from within the release-upgrader
542 nv = NvidiaDetection(obsolete="./ubuntu-drivers-obsolete.pkgs")
543 #nv = NvidiaDetection()
544 # check if a binary driver is installed now
545 for oldDriver in nv.oldPackages:
546 if oldDriver in self and self[oldDriver].is_installed:
547 self.mark_remove(oldDriver, "old nvidia driver")
548 break
549 else:
550 logging.info("no old nvidia driver installed, installing
no new")
551 return False
Unfortunately, the dist-upgrader tarball doesn't actually have "ubuntu-
drivers-obsolete.pkgs" in it so nv.oldPackages is always empty and no
old nvidia driver will be detected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1773637
Title:
Distribution upgrade to 18.04: used nvidia display driver is commented
out
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
Confirmed
Bug description:
I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
After the installation had finished, Xorg wouldn't start. I later found out
that this was because the installation routine had commented out the nvidia
display driver I used in the xorg.conf:
Section "Device"
Identifier "nvidia"
#Driver "nvidia"
BusID "PCI:10@0:0:0"
Option "ConstrainCursor" "off"
EndSection
As the installtion routine backuped my xorg.conf I could verify that
the line hadn't been commented out before upgrading. Removing the "#"
solved the problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
.proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:0a:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57
PDT 2018
GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 27 11:43:16 2018
DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
InstallationDate: Installed on 2017-11-02 (205 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
dmi.bios.date: 11/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 229D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.15
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 097312405F1620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx:
[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out
And it looks like this is something I removed last year, here's the changelog entry. * build-tarball.sh: Stop updating ubuntu-drivers-obsolete.pkgs since it isn't needed any more see Launchpad bug 1682291 for details. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1773637 Title: Distribution upgrade to 18.04: used nvidia display driver is commented out Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade. After the installation had finished, Xorg wouldn't start. I later found out that this was because the installation routine had commented out the nvidia display driver I used in the xorg.conf: Section "Device" Identifier "nvidia" #Driver "nvidia" BusID "PCI:10@0:0:0" Option "ConstrainCursor" "off" EndSection As the installtion routine backuped my xorg.conf I could verify that the line hadn't been commented out before upgrading. Removing the "#" solved the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 27 11:43:16 2018 DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d] Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d] InstallationDate: Installed on 2017-11-02 (205 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 229D dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 097312405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out
Hey, thanks for helping out with the log file. Could you also add '/var/log/dist-upgrade/xorg_fixup.log' to your bug report? Thanks again! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1773637 Title: Distribution upgrade to 18.04: used nvidia display driver is commented out Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade. After the installation had finished, Xorg wouldn't start. I later found out that this was because the installation routine had commented out the nvidia display driver I used in the xorg.conf: Section "Device" Identifier "nvidia" #Driver "nvidia" BusID "PCI:10@0:0:0" Option "ConstrainCursor" "off" EndSection As the installtion routine backuped my xorg.conf I could verify that the line hadn't been commented out before upgrading. Removing the "#" solved the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 27 11:43:16 2018 DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d] Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d] InstallationDate: Installed on 2017-11-02 (205 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 229D dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 097312405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808600] [NEW] Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10
You have been subscribed to a public bug: 2018-12-01T17:06:36.572303+01:00 DELLVENUE7140 su: pam_systemd(su:session): Cannot create session: Already running in a session 2018-12-01T17:06:36.572578+01:00 DELLVENUE7140 su: pam_unix(su:session): session opened for user root by filarsky(uid=1000) 2018-12-01T17:06:38.809874+01:00 DELLVENUE7140 kernel: [ 34.145441] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:38.809901+01:00 DELLVENUE7140 kernel: [ 34.145443] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:38.809902+01:00 DELLVENUE7140 kernel: [ 34.145448] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145452] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145456] mmc0: sdhci: Argument: 0x | Trn mode: 0x003b 2018-12-01T17:06:38.809904+01:00 DELLVENUE7140 kernel: [ 34.145460] mmc0: sdhci: Present: 0x01ff | Host ctl: 0x0017 2018-12-01T17:06:38.809905+01:00 DELLVENUE7140 kernel: [ 34.145464] mmc0: sdhci: Power: 0x000f | Blk gap: 0x 2018-12-01T17:06:38.809914+01:00 DELLVENUE7140 kernel: [ 34.145467] mmc0: sdhci: Wake-up: 0x | Clock: 0x0007 2018-12-01T17:06:38.809915+01:00 DELLVENUE7140 kernel: [ 34.145471] mmc0: sdhci: Timeout: 0x000a | Int stat: 0x 2018-12-01T17:06:38.809916+01:00 DELLVENUE7140 kernel: [ 34.145475] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b 2018-12-01T17:06:38.809955+01:00 DELLVENUE7140 kernel: [ 34.145478] mmc0: sdhci: AC12 err: 0x0004 | Slot int: 0x 2018-12-01T17:06:38.809956+01:00 DELLVENUE7140 kernel: [ 34.145482] mmc0: sdhci: Caps: 0x25f8c8bf | Caps_1: 0x2077 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145486] mmc0: sdhci: Cmd: 0x123a | Max curr: 0x005800c8 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145490] mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 2018-12-01T17:06:38.809958+01:00 DELLVENUE7140 kernel: [ 34.145494] mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 2018-12-01T17:06:38.809959+01:00 DELLVENUE7140 kernel: [ 34.145496] mmc0: sdhci: Host ctl2: 0x800b 2018-12-01T17:06:38.809960+01:00 DELLVENUE7140 kernel: [ 34.145499] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc00208 2018-12-01T17:06:38.809961+01:00 DELLVENUE7140 kernel: [ 34.145500] mmc0: sdhci: 2018-12-01T17:06:38.809966+01:00 DELLVENUE7140 kernel: [ 34.145684] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.869767+01:00 DELLVENUE7140 kernel: [ 34.201457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.869781+01:00 DELLVENUE7140 kernel: [ 34.201709] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.925667+01:00 DELLVENUE7140 kernel: [ 34.257457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.925684+01:00 DELLVENUE7140 kernel: [ 34.259406] mmcblk0: error -84 sending status command, aborting 2018-12-01T17:06:39.309674+01:00 DELLVENUE7140 kernel: [ 34.641396] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:40.315726+01:00 DELLVENUE7140 systemd-timesyncd[857]: Synchronized to time server 129.250.35.251:123 (2.opensuse.pool.ntp.org). 2018-12-01T17:06:49.561926+01:00 DELLVENUE7140 kernel: [ 44.899647] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:49.561938+01:00 DELLVENUE7140 kernel: [ 44.899648] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:49.561939+01:00 DELLVENUE7140 kernel: [ 44.899653] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 LSPCI : https://pastebin.com/sVKA47r3 After update to kernel 4.19 (OS: opensuse) [Previous log applies to 4.12] 2018-12-02T10:26:57.264780+01:00 DELLVENUE7140 kernel: [ 39.552776] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.264814+01:00 DELLVENUE7140 kernel: [ 39.553062] mmc0: new ultra high speed SDR104 SDXC card at address 2018-12-02T10:26:57.280688+01:00 DELLVENUE7140 kernel: [ 39.570818] mmcblk0: mmc0: SR400 367 GiB 2018-12-02T10:26:57.336742+01:00 DELLVENUE7140 kernel: [ 39.624763] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.596691+01:00 DELLVENUE7140 kernel: [ 39.887665] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 2018-12-02T10:26:57.688834+01:00 DELLVENUE7140 kernel: [ 39.976691] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.744789+01:00 DELLVENUE7140 kernel: [ 40.032659] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.744823+01:00 DELLVENUE7140 kernel: [ 40.032976] print_req_error: I/O error, dev mmcblk0, sector 0
[Kernel-packages] [Bug 1808600] Re: Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10
** Project changed: launchpad => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808600 Title: Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10 Status in linux package in Ubuntu: New Bug description: 2018-12-01T17:06:36.572303+01:00 DELLVENUE7140 su: pam_systemd(su:session): Cannot create session: Already running in a session 2018-12-01T17:06:36.572578+01:00 DELLVENUE7140 su: pam_unix(su:session): session opened for user root by filarsky(uid=1000) 2018-12-01T17:06:38.809874+01:00 DELLVENUE7140 kernel: [ 34.145441] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:38.809901+01:00 DELLVENUE7140 kernel: [ 34.145443] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:38.809902+01:00 DELLVENUE7140 kernel: [ 34.145448] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145452] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145456] mmc0: sdhci: Argument: 0x | Trn mode: 0x003b 2018-12-01T17:06:38.809904+01:00 DELLVENUE7140 kernel: [ 34.145460] mmc0: sdhci: Present: 0x01ff | Host ctl: 0x0017 2018-12-01T17:06:38.809905+01:00 DELLVENUE7140 kernel: [ 34.145464] mmc0: sdhci: Power: 0x000f | Blk gap: 0x 2018-12-01T17:06:38.809914+01:00 DELLVENUE7140 kernel: [ 34.145467] mmc0: sdhci: Wake-up: 0x | Clock: 0x0007 2018-12-01T17:06:38.809915+01:00 DELLVENUE7140 kernel: [ 34.145471] mmc0: sdhci: Timeout: 0x000a | Int stat: 0x 2018-12-01T17:06:38.809916+01:00 DELLVENUE7140 kernel: [ 34.145475] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b 2018-12-01T17:06:38.809955+01:00 DELLVENUE7140 kernel: [ 34.145478] mmc0: sdhci: AC12 err: 0x0004 | Slot int: 0x 2018-12-01T17:06:38.809956+01:00 DELLVENUE7140 kernel: [ 34.145482] mmc0: sdhci: Caps: 0x25f8c8bf | Caps_1: 0x2077 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145486] mmc0: sdhci: Cmd: 0x123a | Max curr: 0x005800c8 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145490] mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 2018-12-01T17:06:38.809958+01:00 DELLVENUE7140 kernel: [ 34.145494] mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 2018-12-01T17:06:38.809959+01:00 DELLVENUE7140 kernel: [ 34.145496] mmc0: sdhci: Host ctl2: 0x800b 2018-12-01T17:06:38.809960+01:00 DELLVENUE7140 kernel: [ 34.145499] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc00208 2018-12-01T17:06:38.809961+01:00 DELLVENUE7140 kernel: [ 34.145500] mmc0: sdhci: 2018-12-01T17:06:38.809966+01:00 DELLVENUE7140 kernel: [ 34.145684] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.869767+01:00 DELLVENUE7140 kernel: [ 34.201457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.869781+01:00 DELLVENUE7140 kernel: [ 34.201709] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.925667+01:00 DELLVENUE7140 kernel: [ 34.257457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.925684+01:00 DELLVENUE7140 kernel: [ 34.259406] mmcblk0: error -84 sending status command, aborting 2018-12-01T17:06:39.309674+01:00 DELLVENUE7140 kernel: [ 34.641396] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:40.315726+01:00 DELLVENUE7140 systemd-timesyncd[857]: Synchronized to time server 129.250.35.251:123 (2.opensuse.pool.ntp.org). 2018-12-01T17:06:49.561926+01:00 DELLVENUE7140 kernel: [ 44.899647] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:49.561938+01:00 DELLVENUE7140 kernel: [ 44.899648] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:49.561939+01:00 DELLVENUE7140 kernel: [ 44.899653] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 LSPCI : https://pastebin.com/sVKA47r3 After update to kernel 4.19 (OS: opensuse) [Previous log applies to 4.12] 2018-12-02T10:26:57.264780+01:00 DELLVENUE7140 kernel: [ 39.552776] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.264814+01:00 DELLVENUE7140 kernel: [ 39.553062] mmc0: new ultra high speed SDR104 SDXC card at address 2018-12-02T10:26:57.280688+01:00 DELLVENUE7140 kernel: [ 39.570818] mmcblk0: mmc0: SR400 367 GiB 2018-12-02T10:26:57.336742+01:00 DELLVENUE7140 kernel: [ 39.624763] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-02T10:26:57.596691+01:00 DELLVENUE7140 kernel: [ 39.887665] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id:
[Kernel-packages] [Bug 1808600] 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 1808600 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/1808600 Title: Dell venue 7140 micro SD card reader doesnt work with SD card 400GB, it works on windows8.1/10 Status in linux package in Ubuntu: Incomplete Bug description: 2018-12-01T17:06:36.572303+01:00 DELLVENUE7140 su: pam_systemd(su:session): Cannot create session: Already running in a session 2018-12-01T17:06:36.572578+01:00 DELLVENUE7140 su: pam_unix(su:session): session opened for user root by filarsky(uid=1000) 2018-12-01T17:06:38.809874+01:00 DELLVENUE7140 kernel: [ 34.145441] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:38.809901+01:00 DELLVENUE7140 kernel: [ 34.145443] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:38.809902+01:00 DELLVENUE7140 kernel: [ 34.145448] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145452] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 2018-12-01T17:06:38.809903+01:00 DELLVENUE7140 kernel: [ 34.145456] mmc0: sdhci: Argument: 0x | Trn mode: 0x003b 2018-12-01T17:06:38.809904+01:00 DELLVENUE7140 kernel: [ 34.145460] mmc0: sdhci: Present: 0x01ff | Host ctl: 0x0017 2018-12-01T17:06:38.809905+01:00 DELLVENUE7140 kernel: [ 34.145464] mmc0: sdhci: Power: 0x000f | Blk gap: 0x 2018-12-01T17:06:38.809914+01:00 DELLVENUE7140 kernel: [ 34.145467] mmc0: sdhci: Wake-up: 0x | Clock: 0x0007 2018-12-01T17:06:38.809915+01:00 DELLVENUE7140 kernel: [ 34.145471] mmc0: sdhci: Timeout: 0x000a | Int stat: 0x 2018-12-01T17:06:38.809916+01:00 DELLVENUE7140 kernel: [ 34.145475] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b 2018-12-01T17:06:38.809955+01:00 DELLVENUE7140 kernel: [ 34.145478] mmc0: sdhci: AC12 err: 0x0004 | Slot int: 0x 2018-12-01T17:06:38.809956+01:00 DELLVENUE7140 kernel: [ 34.145482] mmc0: sdhci: Caps: 0x25f8c8bf | Caps_1: 0x2077 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145486] mmc0: sdhci: Cmd: 0x123a | Max curr: 0x005800c8 2018-12-01T17:06:38.809957+01:00 DELLVENUE7140 kernel: [ 34.145490] mmc0: sdhci: Resp[0]: 0x | Resp[1]: 0x 2018-12-01T17:06:38.809958+01:00 DELLVENUE7140 kernel: [ 34.145494] mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x 2018-12-01T17:06:38.809959+01:00 DELLVENUE7140 kernel: [ 34.145496] mmc0: sdhci: Host ctl2: 0x800b 2018-12-01T17:06:38.809960+01:00 DELLVENUE7140 kernel: [ 34.145499] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc00208 2018-12-01T17:06:38.809961+01:00 DELLVENUE7140 kernel: [ 34.145500] mmc0: sdhci: 2018-12-01T17:06:38.809966+01:00 DELLVENUE7140 kernel: [ 34.145684] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.869767+01:00 DELLVENUE7140 kernel: [ 34.201457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.869781+01:00 DELLVENUE7140 kernel: [ 34.201709] mmcblk0: error -84 sending status command, retrying 2018-12-01T17:06:38.925667+01:00 DELLVENUE7140 kernel: [ 34.257457] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:38.925684+01:00 DELLVENUE7140 kernel: [ 34.259406] mmcblk0: error -84 sending status command, aborting 2018-12-01T17:06:39.309674+01:00 DELLVENUE7140 kernel: [ 34.641396] mmc0: Tuning timeout, falling back to fixed sampling clock 2018-12-01T17:06:40.315726+01:00 DELLVENUE7140 systemd-timesyncd[857]: Synchronized to time server 129.250.35.251:123 (2.opensuse.pool.ntp.org). 2018-12-01T17:06:49.561926+01:00 DELLVENUE7140 kernel: [ 44.899647] mmc0: Timeout waiting for hardware interrupt. 2018-12-01T17:06:49.561938+01:00 DELLVENUE7140 kernel: [ 44.899648] mmc0: sdhci: SDHCI REGISTER DUMP === 2018-12-01T17:06:49.561939+01:00 DELLVENUE7140 kernel: [ 44.899653] mmc0: sdhci: Sys addr: 0x0008 | Version: 0x0603 LSPCI : https://pastebin.com/sVKA47r3 After update to kernel 4.19 (OS: opensuse) [Previous log applies to 4.12] 2018-12-02T10:26:57.264780+01:00 DELLVENUE7140 kernel: [ 39.552776] mmc0: Tuning timeout, falling back to fixed sampling clock
[Kernel-packages] [Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
@Vadim, I will try to reproduce your problem next week. thanks. hui. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
Awesome, thank you. Let me know if you want me to run particular tests or provide information. I'm not sure if the issue manifests every time. On kernels before 4.19.7 I was hearing noise sometimes, especially after waking up from S3 sleep, but S4 hibernation or reboot (possibly turning the machine off was required) was solving it every time. I did not have the issue with quiet sound output. Have a nice weekend, Vadim. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
oky, i now also experienced the issue a couple of times but it only occurs in 1 out of 10 times and i resolved by an additional suspend/resume. In dmesg i see: psmouse serio1: Failed to disable mouse on isa0060/serio1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN
[Kernel-packages] [Bug 1805414] Re: [Ubuntu] kernel: zcrypt: reinit ap queue state machine
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097301.html
** Description changed:
- Description: kernel: zcrypt: reinit ap queue state machine
-
- Symptom: Zcrypt ap queue device not operational at host level after a
- kvm guest used it.
-
- Problem: The vfio device driver when receiving an ap queue device does
+ == SRU Justification ==
+ The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
- interrupts for the ap device done by the ap bus core
+ interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
+ This commit has also been cc'd to upstream stable.
+
+ == Fix ==
+ 104f708fd ("s390/zcrypt: reinit ap queue state machine during device probe")
+
+ == Regression Potential ==
+ Low. Limited to s390.
+
+
+ == Original Bug Description ==
+ Description: kernel: zcrypt: reinit ap queue state machine
+
+ Symptom: Zcrypt ap queue device not operational at host level after a
+ kvm guest used it.
+
+ Problem: The vfio device driver when receiving an ap queue device does
+ additional resets thereby removing the registration for
+ interrupts for the ap device done by the ap bus core
+ code. So when later the vfio driver releases the device and
+ one of the default zcrypt drivers takes care of the device
+ the interrupt registration needs to get renewed. The current
+ code does no renew and result is that requests send into such
+ a queue will never see a reply processed - the application
+ hangs.
+
Solution: This patch adds a function which resets the aq queue state
- machine for the ap queue device and triggers the walk through
- the initial states (which are reset and registration for
- interrupts). This function is now called before the driver's
- probe function is invoked.
- When the association between driver and device is released,
- the driver's remove function is called. The current
- implementation calls a ap queue function
- ap_queue_remove(). This invokation has been moved to the ap
- bus function to make the probe / remove pair for ap bus and
- drivers more symmetric.
+ machine for the ap queue device and triggers the walk through
+ the initial states (which are reset and registration for
+ interrupts). This function is now called before the driver's
+ probe function is invoked.
+ When the association between driver and device is released,
+ the driver's remove function is called. The current
+ implementation calls a ap queue function
+ ap_queue_remove(). This invokation has been moved to the ap
+ bus function to make the probe / remove pair for ap bus and
+ drivers more symmetric.
Reproduction: Set up an kvm guest to use one or more ap queues in
- pass-through mode. Start the guest. Stop the guest. Reassign
- the ap resources back to the host system. Run an application
- which uses exactly this ap resources. Without the fix, the
- application hangs; with the fix the application should run
- fine.
+ pass-through mode. Start the guest. Stop the guest. Reassign
+ the ap resources back to the host system. Run an application
+ which uses exactly this ap resources. Without the fix, the
+ application hangs; with the fix the application should run
+ fine.
- Upstream commit(s):
+ Upstream commit(s):
104f708fd1241b22f808bdf066ab67dc5a051de5
Available on kernel.org
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805414
Title:
[Ubuntu] kernel: zcrypt: reinit ap queue state machine
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
In Progress
Bug description:
== SRU Justification ==
The vfio device driver when receiving an ap queue device does
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
*more info: i am using ubuntu 18.04.1, 4.19.9 from mainline, libinput 1.12.1, attached is my dmesg, the last but one suspend/resume deactivated the touchpad and the last one restored it. i had psmouse.synaptics_intertouch=1, i am now testing psmouse.synaptics_intertouch=0 ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5222301/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018
[Kernel-packages] [Bug 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097304.html
** Description changed:
- Description: qeth: fix length check in SNMP processing
- Symptom: Undefined behaviour.
- Problem: The response for a SNMP request can consist of multiple parts,
+ == SRU Justification ==
+ The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
+
+
+ == Fix ==
+ 9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
+
+ == Regression Potential ==
+ Low. Changes limited to s390.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+ == Original bug description ==
+
+ Description: qeth: fix length check in SNMP processing
+ Symptom: Undefined behaviour.
+ Problem: The response for a SNMP request can consist of multiple parts,
+ which the cmd callback stages into a kernel buffer until all
+ parts have been received. If the callback detects that the
+ staging buffer provides insufficient space, it bails out with
+ error.
+ This processing is buggy for the first part of the response -
+ while it initially checks for a length of 'data_len', it later
+ copies an additional amount of
+ 'offsetof(struct qeth_snmp_cmd, data)' bytes.
Solution: Fix the calculation of 'data_len' for the first part of the
- response.
+ response.
Upstream-ID: 9a764c1e59684c0358e16ccaafd870629f2cfe67
Should be applied to all Ubuntu Releases in Service
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805802
Title:
[UBUNTU] qeth: fix length check in SNMP processing
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
In Progress
Bug description:
== SRU Justification ==
The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
== Fix ==
9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
== Regression Potential ==
Low. Changes limited to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original bug description ==
Description: qeth: fix length check in SNMP processing
Symptom: Undefined behaviour.
Problem: The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
Solution: Fix the calculation of 'data_len' for the first part of the
response.
Upstream-ID: 9a764c1e59684c0358e16ccaafd870629f2cfe67
Should be applied to all Ubuntu Releases in Service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
** Description changed: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - - I'm running the latest BIOS. + - 4.15.0-42 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. - This bug seems very similar to what's described here for the Thinkpad - E485/E585: - https://web.archive.org/web/20180919160303/https://evilazrael.de/content - /getting-linux-boot-lenovo-thinkpad-e485e585 - I'll attach screenshots of various times I've encountered this bug over the last year. - - $ lsb_release -rd - Description: Ubuntu 18.04.1 LTS - Release: 18.04 - - $ apt-cache policy linux-image-4.15.0-42-generic - linux-image-4.15.0-42-generic: - Installed: 4.15.0-42.45 - Candidate: 4.15.0-42.45 - Version table: - *** 4.15.0-42.45 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO ** Description changed: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. + This bug seems very similar to what's described here for the Thinkpad + E485/E585: + https://web.archive.org/web/20180919160303/https://evilazrael.de/content + /getting-linux-boot-lenovo-thinkpad-e485e585 + I'll attach screenshots of various times I've encountered this bug over the last year. + + $ lsb_release -rd + Description:Ubuntu 18.04.1 LTS + Release:18.04 + + $ apt-cache policy linux-image-4.15.0-42-generic +
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: - promote-to-proposed: Ready for review + promote-to-proposed: Review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: promote-to-proposed: Review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: - promote-to-proposed: Packages copied but not yet published to -proposed + promote-to-proposed: Packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807702 Title: linux-oracle: 4.15.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7 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: 1806659 phase: Uploaded phase-changed: Wednesday, 12. December 2018 19:38 UTC reason: promote-to-proposed: Packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808588] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 - phase: Uploaded - phase-changed: Wednesday, 12. December 2018 20:11 UTC + phase: Promoted to proposed + phase-changed: Friday, 14. December 2018 21:38 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Packages waiting in -proposed for mirror sync + automated-testing: Testing FAILED + regression-testing: Testing in progress + verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 14. December 2018 21:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222377/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222376/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222375/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808588] [NEW] Upgrade from 18.04 to 18.10 lost trackpad/trackpoint
Public bug reported: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1808588/+attachment/5222374/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808588 Title: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my laptop. The installation process seemed to go well, but on reboot my trackpad and trackpoint no longer move the pointer, register taps or click buttons, and are seemingly unrecognized by the system. General information: Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11 (that might be a 'O' rather than an '0' on the sticker) Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint When symptoms first appeared: On first reboot after the change to Cosmic. Also on subsequent reboots and waking from sleep and suspend. No trackpad device is listed in /proc/bus/input/devices. The trackpad and trackpoint and buttons work if I boot into another OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
oky i could reproduce it with psmouse.synaptics_intertouch=0. Here my dmesg. As above the last suspend/resume restored the touchpad and the last but one deactivated it. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5222385/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available
[Kernel-packages] [Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
Hi Hui Wang, While waiting for your patch to reach the mainline, I just insert these two lines myself. However, I still have issues with the sound. Scenario: laptop is off, headphones are inserted, sound (both mic and output) is muted; I turn it on, log in etc., unmute the output and play something. The sound is often too quiet (maybe 10 to 15 dB weaker than expected). If I unplug the headphones and plug them back in, the sound level rises to expected levels, but I start hearing noise reminiscent of cheap soundcards (with grounding problems?), where the noise characteristics change with the activity of other devices (e.g., mouse movements). The noise is stronger if I touch the touchpad. If I mute the sound, the noise disappears. This does not happen if I remove the "0x12" line, whether or not I add the .chained/.chain_id lines. Interestingly, init_pin_configs in sysfs shows the same value for 0x12: $ cat /sys/class/sound/hwC0D0/init_pin_configs 0x12 0x90a60130 0x13 0x4000 0x14 0x90170110 0x16 0x41f0 0x17 0x41f0 0x18 0x41f0 0x19 0x04a11040 0x1a 0x41f0 0x1b 0x41f0 0x1d 0x4061 0x1e 0x41f0 0x21 0x04211020 (driver_pin_configs and user_pin_configs are empty.) Thank you, Vadim. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805079 Title: click/pop noise in the headphone on several lenovo laptops Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] Lenovo told us that some linux uers reported headphone noise on Lenovo's website. After investigating, we found those Lenovo laptop mdoels all have the codec of alc285, and we can reproduce the noise problem too. [Fix] Don't use the DAC of headphone, let headphone share the DAC with speaker, the noise disappears. [Test Case] After applying this patch, we tested on Lenovo P52, P72, X1 carbon and X1 Yoda2, no noise anymore [Regression Potential] Low. This patch only apply to several lenovo machines, and after applying this patch, both speaker and headphone still work very well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in
apport information ** Description changed: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-12-10 (4 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: upower + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 + Tags: cosmic + Uname: Linux 4.18.0-12-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/1808193/+attachment/5222351/+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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-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/1808193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
@Mike, do you feel comfortable with the testing you've done to submit an SRU request? Or would you like to perform some additional testing? ** Changed in: linux (Ubuntu Cosmic) 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/1788549 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: == Comment: #0 - Michael Ranweiler - 2018-08-21 13:52:03 == +++ This bug was initially created as a clone of Bug #170766 +++ Please apply the following kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=db2173198b9513f7add8009f225afa1f1c79bcc6 powerpc/powernv/pci: Work around races in PCI bridge enabling The generic code is racy when multiple children of a PCI bridge try to enable it simultaneously. This leads to drivers trying to access a device through a not-yet-enabled bridge, and this EEH errors under various circumstances when using parallel driver probing. There is work going on to fix that properly in the PCI core but it will take some time. x86 gets away with it because (outside of hotplug), the BIOS enables all the bridges at boot time. This patch does the same thing on powernv by enabling all bridges that have child devices at boot time, thus avoiding subsequent races. It's suitable for backporting to stable and distros, while the proper PCI fix will probably be significantly more invasive. Signed-off-by: Benjamin Herrenschmidt Cc: sta...@vger.kernel.org Signed-off-by: Michael Ellerman == Comment: #2 - Michael Ranweiler - 2018-08-21 18:23:35 == This has some fuzz and also move it back from the pci macro to dev_err so we'll attach the backported patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808193] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222354/+files/ProcEnviron.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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-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/1808193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808193] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222352/+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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-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/1808193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808193] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222353/+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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-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/1808193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
