[Kernel-packages] [Bug 1755762] Re: linux: 4.13.0-38.43 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/artful/4.13.0-38.43 /artful-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1755762 Title: linux: 4.13.0-38.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: 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 1755767 (linux-hwe), bug 1755769 (linux-azure-edge), bug 1755771 (linux-gcp), bug 1755773 (linux-azure), bug 1755774 (linux-oem) derivatives: bug 1755765 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755954] Re: external mic not work on Dell OptiPlex 7460 AIO
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755954
Title:
external mic not work on Dell OptiPlex 7460 AIO
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux-oem source package in Xenial:
Fix Committed
Status in linux source package in Artful:
New
Status in linux-oem source package in Artful:
Invalid
Bug description:
== SRU Justification ==
We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't
detect external mic and can't record sound via external mic. After applying
the fixup of ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, the problem can be fixed.
== Fix ==
40e2c4e5("iALSA: hda/realtek - Add headset mode support for Dell laptop")
== Regression Potential ==
very low, since this patch only applies to specific Dell machines which have
subsystem id: 1028084b and 1028084e.
== Test Case ==
plug the headset and record the sound on this machine, we can see the
external mic in the sound-setting and can record sound through this mic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1755954/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725154 Title: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: New Status in linux-oem source package in Artful: Invalid Bug description: Issue happens every time we get connected to any WPA network and stay idle for more than 60 seconds. We are working with upstream for a real fix: https://www.spinics.net/lists/linux-wireless/msg167017.html, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1725154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745081 Title: Add support for Realtek WiFi device [10ec:b822] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Committed Bug description: 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:b822] Subsystem: Lenovo Device [17aa:b023] Flags: fast devsel, IRQ 255 I/O ports at c000 [disabled] [size=256] Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1745081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755954] Re: external mic not work on Dell OptiPlex 7460 AIO
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755954
Title:
external mic not work on Dell OptiPlex 7460 AIO
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Status in linux-oem source package in Xenial:
Fix Committed
Status in linux source package in Artful:
New
Status in linux-oem source package in Artful:
Invalid
Bug description:
== SRU Justification ==
We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't
detect external mic and can't record sound via external mic. After applying
the fixup of ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, the problem can be fixed.
== Fix ==
40e2c4e5("iALSA: hda/realtek - Add headset mode support for Dell laptop")
== Regression Potential ==
very low, since this patch only applies to specific Dell machines which have
subsystem id: 1028084b and 1028084e.
== Test Case ==
plug the headset and record the sound on this machine, we can see the
external mic in the sound-setting and can record sound through this mic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1755954/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745081 Title: Add support for Realtek WiFi device [10ec:b822] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Committed Bug description: 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:b822] Subsystem: Lenovo Device [17aa:b023] Flags: fast devsel, IRQ 255 I/O ports at c000 [disabled] [size=256] Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1745081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758264] [NEW] ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF" on Witherspoon system due to java dumping
You have been subscribed to a public bug:
== Comment: #0 - INDIRA P. JOGA - 2018-03-22 06:45:23
==
Problem Description:
===
Unable to start "STAF" on Witherspoon system due to java dumping
Steps to re-create:
==
> System installed with Ubunu1804 build.
root@whip:# uname -a
Linux whip 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018 ppc64le
ppc64le ppc64le GNU/Linux
> We are using staf framework to run the LTP test buckets.
> Unable to start the staf process.
> It fails to start and i see java dumping core.
> core details
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06 core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06 core.20180322.060603.4631.0001.dmp
> Attached core files
NOTE:-
--
System is on a private network. Access the private network via SSH to
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password.
(Banner itself is behind a BSO, so must authenticate through that first.)
Login details :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]
Host login:-ssh -p 2200 root@bmc-wax (0penBmc) (or)
ssh root@wax (don2rry)
== Comment: #5 - INDIRA P. JOGA - 2018-03-22 07:09:14
==
Unable to attach core file because huge size.
Please find the path from the system:
root@whip:/# pwd
/
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06 core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06 core.20180322.060603.4631.0001.dmp
root@whip:/#
Regards,
Indira
== Comment: #6 - INDIRA P. JOGA - 2018-03-22 07:20:12
==
Also you can find them in banner
banner@banner:~> pwd
/home/banner
banner@banner:~> ls -l core*
-rw--- 1 banner banner 114753536 Mar 22 06:46
core.20180322.060600.4626.0001.dmp
-rw--- 1 banner banner 115736576 Mar 22 06:46
core.20180322.060603.4631.0001.dmp
== Comment: #8 - SEETEENA THOUFEEK - 2018-03-22
09:00:18 ==
Please pick
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features")
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
** Tags: architecture-ppc64le bugnameltc-165949 severity-critical
targetmilestone-inin---
--
ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF" on
Witherspoon system due to java dumping
https://bugs.launchpad.net/bugs/1758264
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 1758264] Re: ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF" on Witherspoon system due to java dumping
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Status: New => Triaged
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Tags added: triage-g
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758264
Title:
ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF"
on Witherspoon system due to java dumping
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - INDIRA P. JOGA - 2018-03-22
06:45:23 ==
Problem Description:
===
Unable to start "STAF" on Witherspoon system due to java dumping
Steps to re-create:
==
> System installed with Ubunu1804 build.
root@whip:# uname -a
Linux whip 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
> We are using staf framework to run the LTP test buckets.
> Unable to start the staf process.
> It fails to start and i see java dumping core.
> core details
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
> Attached core files
NOTE:-
--
System is on a private network. Access the private network via SSH to
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password.
(Banner itself is behind a BSO, so must authenticate through that first.)
Login details :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]
Host login:-ssh -p 2200 root@bmc-wax (0penBmc) (or)
ssh root@wax (don2rry)
== Comment: #5 - INDIRA P. JOGA - 2018-03-22
07:09:14 ==
Unable to attach core file because huge size.
Please find the path from the system:
root@whip:/# pwd
/
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
root@whip:/#
Regards,
Indira
== Comment: #6 - INDIRA P. JOGA - 2018-03-22
07:20:12 ==
Also you can find them in banner
banner@banner:~> pwd
/home/banner
banner@banner:~> ls -l core*
-rw--- 1 banner banner 114753536 Mar 22 06:46
core.20180322.060600.4626.0001.dmp
-rw--- 1 banner banner 115736576 Mar 22 06:46
core.20180322.060603.4631.0001.dmp
== Comment: #8 - SEETEENA THOUFEEK - 2018-03-22
09:00:18 ==
Please pick
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758264/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750388] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2018-03-23 05:05 EDT--- Any updates on this bugzilla? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750388 Title: 17.10 - BPF test tool build with errors Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
No problems seen so far with 4.15.7-041507-generic either, after 25 minutes connected to the VPN. Sounds like it might be a problem in the Ubuntu changes to 4.15 after all. ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: New Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
** Package changed: linux-meta (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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: New Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747572] Re: CIFS SMB2/SMB3 does not work for domain based DFS
@Sergey, glad this was successful now. Thanks for verifying, I marked the status as done now. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747572 Title: CIFS SMB2/SMB3 does not work for domain based DFS Status in cifs-utils: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: There is upstream bug report: https://bugzilla.samba.org/show_bug.cgi?id=12917 "Fix was merged upstream and should be in the next kernel update. Ask your distribution maintainers to backport it." Aurélien Aptel It looks like the following patches should be backported: [v3,3/3] CIFS: dump IPC tcon in debug proc file [v3,2/3] CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl [v3,1/3] CIFS: make IPC a regular tcon Link to patchwork: https://patchwork.kernel.org/project/cifs- client/list/?submitter=146481 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 6 09:50:57 2018 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cifs-utils/+bug/1747572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Still not working on 4.16.0-rc6. Is there actually development going on concering this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747896] Re: OOM and High CPU utilization in update_blocked_averages because of too many cfs_rqs in rq->leaf_cfs_rq_list
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747896 Title: OOM and High CPU utilization in update_blocked_averages because of too many cfs_rqs in rq->leaf_cfs_rq_list Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The CPU utilization keeps high and the flamegraph[1] shows that the CPU is busy updating the load average in the for loop inside update_blocked_averages() function. Also, the OOM happens because of the decayed cfs_rqs are not released. [Fix] commit a9e7f6544b9cebdae54d29f87a7ba2a83c0471b5 Author: Tejun Heo Date: Tue Apr 25 17:43:50 2017 -0700 sched/fair: Fix O(nr_cgroups) in load balance path Currently, rq->leaf_cfs_rq_list is a traversal ordered list of all live cfs_rqs which have ever been active on the CPU; unfortunately, this makes update_blocked_averages() O(# total cgroups) which isn't scalable at all. This shows up as a small CPU consumption and scheduling latency increase in the load balancing path in systems with CPU controller enabled across most cgroups. In an edge case where temporary cgroups were leaking, this caused the kernel to consume good several tens of percents of CPU cycles running update_blocked_averages(), each run taking multiple millisecs. This patch fixes the issue by taking empty and fully decayed cfs_rqs off the rq->leaf_cfs_rq_list. [Test] 1). Running the script #/bin/bash for i in $(seq 1 10); do ( for j in $(seq 1 3000); do ssh -S none u@localhost date;done; echo "done $i" ) & done 2). Observe the cfs_rqs $ watch -n1 "grep cfs_rq /proc/sched_debug| wc -l" 3). Observe the CPU utilization rate $ sudo htop The patched kernel[2] shows that the CPU utilization rate is normal, the cfs_rqs is decreased periodically, and the memory can be limited. [Reference] [1]. http://kernel.ubuntu.com/~gavinguo/168887/2018-01-31_07-38-45.perf.data.svg [2]. https://launchpad.net/~mimi0213kimo/+archive/ubuntu/cfs-rq-clean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
In addition to what Po-Hsu Lin and Daniel Axtens said, to have each of the kernels test-booted and checked for obvious regressions would be great and if in addition one of those can be tested for the reported problem being fixed, then this is sufficient. But mainly this procedure is to ensure we do not break things while trying to fix problems. And if there is some regression it takes time to isolate the change and revert it. Hence the urge to get reporter test as soon as possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: SRU Justification = A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x card attached, and uses openvswitch to bridge an ibmveth interface for traffic from other LPARs. We see the following crash sometimes when running netperf: May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert! May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 0x25e42a7e 0x00462a38 0x00010052 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump - ... (dump of registers follows) ... Subsequent debugging reveals that the packets causing the issue come through the ibmveth interface - from the AIX LPAR. The veth protocol is 'special' - communication between LPARs on the same chassis can use very large (64k) frames to reduce overhead. Normal networks cannot handle such large packets, so traditionally, the VIOS partition would signal to the AIX partitions that it was 'special', and AIX would send regular, ethernet-sized packets to VIOS, which VIOS would then send out. This signalling between VIOS and AIX is done in a way that is not standards-compliant, and so was never made part of Linux. Instead, the Linux driver has always understood large frames and passed them up the network stack. In some cases (e.g. with TCP), multiple TCP segments are coalesced into one large packet. In Linux, this goes through the generic receive offload code, using a similar mechanism to GSO. These segments can be very large which presents as a very large MSS (maximum segment size) or gso_size. Normally, the large packet is simply passed to whatever network application on Linux is going to consume it, and everything is OK. However, in this case, the packets go through Open vSwitch, and are then passed to the bnx2x driver. The bnx2x driver/hardware supports TSO and GSO, but with a restriction: the maximum segment size is limited to around 9700 bytes. Normally this is more than adequate. However, if a large packet with very large (>9700 byte) TCP segments arrives through ibmveth, and is passed to bnx2x, the hardware will panic. [Impact] bnx2x card panics, requiring power cycle to restore functionality. The workaround is turning off TSO, which prevents the crash as the kernel resegments *all* packets in software, not just ones that are too big. This has a performance cost. [Fix] Test packet size in bnx2x feature check path and disable GSO if it is too large. To do this we move a function from one file to another and add another in the networking core. [Regression Potential] A/B/X: The changes to the network core are easily reviewed. The changes to behaviour are limited to the bnx2x card driver. The most likely failure case is a false-positive on the size check, which would lead to a performance regression only. T: This also involves a different change to the networking core to add the old-style GSO checking, which is more invasive. However the changes are simple and easily reviewed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
Hi, As well as Po-Hsu's comment above, I also have this internal update from the kernel team: As this is also a security fix, don't stress too much. If things could be verified for at least for one of the kernels until next week that is better than nothing. We are rather unlikely rip out fixes if they have a CVE (and do not appear to regress other things) (FYI, this issue is covered by CVE-2018-126.) So, just to confirm, in order of priority: 1) First confirm there are no new regressions (just a quick 'smoke test') on the 3 kernels. 2) Second, do a full test of 1 of the kernels. 3) Test the remaining 2 kernels. Please keep this bug updated as you go through each step. Hopefully this helps reduce the pressure for you! Regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: SRU Justification = A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x card attached, and uses openvswitch to bridge an ibmveth interface for traffic from other LPARs. We see the following crash sometimes when running netperf: May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert! May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 0x25e42a7e 0x00462a38 0x00010052 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump - ... (dump of registers follows) ... Subsequent debugging reveals that the packets causing the issue come through the ibmveth interface - from the AIX LPAR. The veth protocol is 'special' - communication between LPARs on the same chassis can use very large (64k) frames to reduce overhead. Normal networks cannot handle such large packets, so traditionally, the VIOS partition would signal to the AIX partitions that it was 'special', and AIX would send regular, ethernet-sized packets to VIOS, which VIOS would then send out. This signalling between VIOS and AIX is done in a way that is not standards-compliant, and so was never made part of Linux. Instead, the Linux driver has always understood large frames and passed them up the network stack. In some cases (e.g. with TCP), multiple TCP segments are coalesced into one large packet. In Linux, this goes through the generic receive offload code, using a similar mechanism to GSO. These segments can be very large which presents as a very large MSS (maximum segment size) or gso_size. Normally, the large packet is simply passed to whatever network application on Linux is going to consume it, and everything is OK. However, in this case, the packets go through Open vSwitch, and are then passed to the bnx2x driver. The bnx2x driver/hardware supports TSO and GSO, but with a restriction: the maximum segment size is limited to around 9700 bytes. Normally this is more than adequate. However, if a large packet with very large (>9700 byte) TCP segments arrives through ibmveth, and is passed to bnx2x, the hardware will panic. [Impact] bnx2x card panics, requiring power cycle to restore functionality. The workaround is turning off TSO, which prevents the crash as the kernel resegments *all* packets in software, not just ones that are too big. This has a performance cost. [Fix] Test packet size in bnx2x feature check path and disable GSO if it is too large. To do this we move a function from one file to another and add another in the networking core. [Regression Potential] A/B/X: The changes to the network core are easily reviewed. The changes to behaviour are limited to the bnx2x card driver. The most likely failure case is a false-positive on the size check, which would lead to a performance regression only. T: This also involves a different change to the networking core to add the old-style GSO checking, which is more invasive. However the changes are simple and easily reviewed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1754601] 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 1754601 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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Incomplete Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750388] Re: 17.10 - BPF test tool build with errors
** Changed in: ubuntu-z-systems Status: Invalid => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750388 Title: 17.10 - BPF test tool build with errors Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Invalid Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755228] Re: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker
There is no automated testing for ESM PPA uploads. ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1755228 Title: linux-lts-trusty: 3.13.0-144.193~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755227 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745945] Re: Kernel update makes HDMI unresponsive
Also affects me since update to 4.13.0-32. Still using 4.13.0-31 (latest working) I have missed 33-36, but since the problem is still there in 37 I fear it's persistent. Using a lenovo X230. Added the output of lshw for both kernels. It is well visible that several drivers are missing in 37. (HDMI, WIFI some USB) that are there in 31. ** Attachment added: "output of lshw on kernel 4.13.0-31 and 4.13.0-37" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745945/+attachment/5087955/+files/lshw_31_37.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745945 Title: Kernel update makes HDMI unresponsive Status in linux package in Ubuntu: Incomplete Bug description: I've update to 4.13.0-32-generic in attempts to fix the same problem listed in Bug #1734084. The only reason I've made this bug is because I'm on 17.10 not 17.04. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy linux-image-4.13.0-32-generic linux-image-4.13.0-32-generic: Installed: 4.13.0-32.35 Candidate: 4.13.0-32.35 Version table: *** 4.13.0-32.35 500 500 http://mirror.kayo.moe/ubuntu artful-updates/main amd64 Packages 500 http://mirror.kayo.moe/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caymon 1499 F pulseaudio /dev/snd/pcmC1D0p: caymon 1499 F...m pulseaudio /dev/snd/controlC1: caymon 1499 F pulseaudio CurrentDesktop: GNOME Date: Mon Jan 29 00:55:27 2018 HibernationDevice: RESUME=UUID=29e48daf-947d-44ac-bf09-520219553efe InstallationDate: Installed on 2017-10-23 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/25/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain
Verified on 4.4.0-117-generic, APST was enabled. #sudo nvme get-feature -f 0x0c -H /dev/nvme0n1 get-feature:0x0c (Autonomous Power State Transition), Current value: 0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 1500 ms Idle Transition Power State (ITPS): 3 . Entry[ 1] ** Attachment added: "nvme-get-feature.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602/+attachment/5087978/+files/nvme-get-feature.log ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1664602 Title: Using an NVMe drive causes huge power drain Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: PCIe NVMe drives are very common in new laptops. The Zesty's kernels (including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous power state transitions). A patch does exist : http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html https://github.com/damige/linux-nvme It seems that we cannot expect this before kernel 4.11. Additionally my laptop CPU does never go under PC3 power saving state, powertop says. I don't know if it's related. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ft 1900 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10 InstallationDate: Installed on 2016-12-12 (63 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 RelatedPackageVersions: linux-restricted-modules-4.10.0-8-generic N/A linux-backports-modules-4.10.0-8-generic N/A linux-firmware1.163 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.5 dmi.board.name: 0YH43H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1664602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
I am not sure if I have done the correct thing, but following the instructions above I have managed to install xenial-proposed kernel 4.13.0-38 on my Mint 18.2 XFCE system: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.13.0-38-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro I can confirm that APST is disabled by default, and no apparent issues after several cycles of suspend and resume. I can't see any option to add or change tags. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] A user reported his NVMe went out to lunch after S3. [Fix] Disable APST for this particular NVMe + Motherboard setup. [Test] User confirmed this quirk works for his system. [Regression Potential] Very Low. This applies to a specific device setup, also user can override this quirk by "nvme_core.force_apst=1". === Original Bug Report === Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 S
[Kernel-packages] [Bug 1745945] Re: Kernel update makes HDMI unresponsive
OK, I solved it. Needed to install also linux-image-extra since this seems to contain all those drivers. so in this case linux-image-extra-4.13.0-37-generic Still stange that this got somehow "lost" during kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745945 Title: Kernel update makes HDMI unresponsive Status in linux package in Ubuntu: Incomplete Bug description: I've update to 4.13.0-32-generic in attempts to fix the same problem listed in Bug #1734084. The only reason I've made this bug is because I'm on 17.10 not 17.04. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy linux-image-4.13.0-32-generic linux-image-4.13.0-32-generic: Installed: 4.13.0-32.35 Candidate: 4.13.0-32.35 Version table: *** 4.13.0-32.35 500 500 http://mirror.kayo.moe/ubuntu artful-updates/main amd64 Packages 500 http://mirror.kayo.moe/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caymon 1499 F pulseaudio /dev/snd/pcmC1D0p: caymon 1499 F...m pulseaudio /dev/snd/controlC1: caymon 1499 F pulseaudio CurrentDesktop: GNOME Date: Mon Jan 29 00:55:27 2018 HibernationDevice: RESUME=UUID=29e48daf-947d-44ac-bf09-520219553efe InstallationDate: Installed on 2017-10-23 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/25/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
** Attachment added: "kernel.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5087994/+files/kernel.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/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758305] [NEW] Panic during SyS_reboot
Public bug reported: BUG: unable to handle kernel NULL pointer dereference at (null) IP: device_shutdown+0xbb/0x200 PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI See the screenshot for more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ksta 1624 F pulseaudio /dev/snd/controlC2: ksta 1624 F pulseaudio /dev/snd/controlC1: ksta 1624 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 07:01:58 2018 InstallationDate: Installed on 2018-03-13 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "IMG_20180323_065051.jpg" https://bugs.launchpad.net/bugs/1758305/+attachment/5088005/+files/IMG_20180323_065051.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758305 Title: Panic during SyS_reboot Status in linux package in Ubuntu: New Bug description: BUG: unable to handle kernel NULL pointer dereference at (null) IP: device_shutdown+0xbb/0x200 PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI See the screenshot for more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ksta 1624 F pulseaudio /dev/snd/controlC2: ksta 1624 F pulseaudio /dev/snd/controlC1: ksta 1624 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 07:01:58 2018 InstallationDate: Installed on 2018-03-13 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
** Attachment added: "journalctl.log.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5088004/+files/journalctl.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756092] Re: Screen freeze for some time when unlocking
Uploaded the dmesg and journalctl log as 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/1756092 Title: Screen freeze for some time when unlocking Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: When trying to unlock the machine, sometimes the screen freezes entirely (including mouse and keyboard input) for a long time either right away or after submitting the password. The freeze lasts for 10-20s, and sometimes the display goes into suspend. I've seen this behavior on both my computers, both fresh 18.04 installs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 15 15:09:26 2018 InstallationDate: Installed on 2018-02-25 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-11 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Tags: bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] A user reported his NVMe went out to lunch after S3. [Fix] Disable APST for this particular NVMe + Motherboard setup. [Test] User confirmed this quirk works for his system. [Regression Potential] Very Low. This applies to a specific device setup, also user can override this quirk by "nvme_core.force_apst=1". === Original Bug Report === Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed
[Kernel-packages] [Bug 1758305] 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/1758305 Title: Panic during SyS_reboot Status in linux package in Ubuntu: Confirmed Bug description: BUG: unable to handle kernel NULL pointer dereference at (null) IP: device_shutdown+0xbb/0x200 PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI See the screenshot for more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ksta 1624 F pulseaudio /dev/snd/controlC2: ksta 1624 F pulseaudio /dev/snd/controlC1: ksta 1624 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 07:01:58 2018 InstallationDate: Installed on 2018-03-13 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
apport information ** Tags added: apport-collected ** Description changed: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: michael1608 F pulseaudio + /dev/snd/controlC1: michael1608 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d + InstallationDate: Installed on 2017-10-24 (149 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: Dell Inc. Latitude E7440 + Package: openconnect 7.08-3 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-12-generic N/A + linux-backports-modules-4.15.0-12-generic N/A + linux-firmware 1.173 + Tags: wayland-session bionic wayland-session + Uname: Linux 4.15.0-12-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 02/02/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0WK2DM + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E7440 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088046/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64
[Kernel-packages] [Bug 1754601] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088056/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088057/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088048/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088051/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088049/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088059/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088055/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088047/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088060/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088050/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088054/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088053/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088052/+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/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088058/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Tags added: id-5aa24a811395b99975a9af89
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
New
Status in chrony package in Ubuntu:
Confirmed
Status in clamav package in Ubuntu:
New
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
New
Status in ifmetric package in Ubuntu:
New
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
New
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Committed
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
New
Status in vzctl package in Ubuntu:
New
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
What's the correct way to find that kernel? So far I have been taking my kernels from here (including the v4.16rc1 which I tried): http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088061/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
The information I added today is rather relativised by the fact that today I am unable to reproduce the problem with the Ubuntu 4.15 kernels either. I will update this when (if?) it happens again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection Status in linux package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: New Bug description: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1608 F pulseaudio /dev/snd/controlC1: michael1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d InstallationDate: Installed on 2017-10-24 (149 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Latitude E7440 Package: openconnect 7.08-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: wayland-session bionic wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy
Yes, it is an XPS13 L322X model. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746740 Title: XPS13 L322X Bionic (daily dev) touchpad laggy Status in libinput: Confirmed Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Also, all function keys work as expected, even F6 (keyboard 3-states backlight), but OSD picture for this last feature randomly auto- triggers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1876 F pulseaudio CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 14:05:22 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
v4.15-rc6: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc6-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.15-rc4: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc4-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.15-rc3: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc3-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.14-rc2: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc2-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - So, somewhere between rc1 and rc2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1755245] Re: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1755245 Title: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180309_144848_e1b37@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
Fix for bionic - lots of thanks to @tyhicks for the explanation and help ** Patch added: "fix2-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+attachment/5088302/+files/fix2-bionic.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux source package in Artful: Invalid Status in lttng-modules source package in Artful: In Progress Status in linux source package in Bionic: Invalid Status in lttng-modules source package in Bionic: New Bug description: [Impact] * The 4.13.0-38 artful kernel included a change (backported from 4.15) that modifies the definition of kvm_mmio(). This breaks the lttng-modules-dkms package because it is using the old (<4.15) definition. * lttng-modules-dkms already has a list of kernel version "exceptions" with which it uses the >=4.15 definition. Proposed solution is to add the Ubuntu kernel range 4.13.0-38 up to 4.14.255-255 to that list of exceptions. [Test Case] * Tested by first successfully building lttng-modules-dkms on 4.13.0-37, then reproducing the problem described here on 4.13.0-38, then applying the code-change and confirming that I can successfully build on both 4.13.0-37 and 4.13.0-38 after that. [Regression Potential] * Low-regression potential. Could prevent lttng-modules-dkms from being built for specific kernel versions, but this is unlikely as the change was tested to confirm that it works as expected on 4.13.0-37 and 4.13.0-38 - and should work fine for other Ubuntu kernels as well. The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1624569] Re: thunder: chip errata w/ multiple CQEs for a TSO packet
** Changed in: linux (Ubuntu) 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/1624569 Title: thunder: chip errata w/ multiple CQEs for a TSO packet Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] With small segment sizes, it is possible for the driver to free an SKB before transmitting it, potentially resulting in a crash. [Test Case] The test case for this is to use a small MTU (200) and mount an NFS exported directory. Create several (~4) 1M files w/ dd, then copy them locally. However, I have not been able to trigger the crash myself. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1623627] Re: thunder: faulty TSO padding
** Changed in: linux (Ubuntu) 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/1623627 Title: thunder: faulty TSO padding Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] Certain packet sizes will trigger spurious TCP retransmissions on Cavium Thunder-X systems when TSO is enabled (the default). This can result in excess traffic and additional latency. [Test Case] Connect 2 systems to a 10G switch: - 1 ThunderX node (the client) - 1 "other" node - doesn't have to be ThunderX (the server) On the server, run the "receiver" command from the attached tcptest tarball: $ ./receiver Also on the server, run tcpdump to capture the traffic: $ sudo tcpdump -i -w tcpdump.out On the client, run the "sender" command from the tcptest tarball, with a 1461 packet size: $ ./sender 1461 1461 Kill the tcpdump process, and open it in wireshark. On failure, you'll see several "[TCP Spurious Retransmission]" packets - on success you should see none. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
This looks promising and landed in -rc2: Btrfs: fix reported number of inode blocks after buffered append writes https://www.spinics.net/lists/linux-btrfs/msg71274.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
lgtm! sponsored to bionic ** Changed in: lttng-modules (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux source package in Artful: Invalid Status in lttng-modules source package in Artful: In Progress Status in linux source package in Bionic: Invalid Status in lttng-modules source package in Bionic: Fix Committed Bug description: [Impact] * The 4.13.0-38 artful kernel included a change (backported from 4.15) that modifies the definition of kvm_mmio(). This breaks the lttng-modules-dkms package because it is using the old (<4.15) definition. * lttng-modules-dkms already has a list of kernel version "exceptions" with which it uses the >=4.15 definition. Proposed solution is to add the Ubuntu kernel range 4.13.0-38 up to 4.14.255-255 to that list of exceptions. [Test Case] * Tested by first successfully building lttng-modules-dkms on 4.13.0-37, then reproducing the problem described here on 4.13.0-38, then applying the code-change and confirming that I can successfully build on both 4.13.0-37 and 4.13.0-38 after that. [Regression Potential] * Low-regression potential. Could prevent lttng-modules-dkms from being built for specific kernel versions, but this is unlikely as the change was tested to confirm that it works as expected on 4.13.0-37 and 4.13.0-38 - and should work fine for other Ubuntu kernels as well. The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757497] Comment bridged from LTC Bugzilla
--- Comment From cls...@us.ibm.com 2018-03-23 11:01 EDT---
Patch accepted upstream in the powerpc tree as git commit
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
("powerpc/64s: Fix lost pending interrupt due to race causing lost update to
irq_happened")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757497
Title:
Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
namespaces (Bolt / NVMe)
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
---Problem Description---
We are seeing similar IO Hang on some namespaces when running HTX 16
namespaces on Ubuntu18.04
---uname output---
Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
---Additional Hardware Info---
(Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)
Machine Type = AC922
---Steps to Reproduce---
1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
2> Install htxubuntu-472.deb
3> make sure you create name spaces
#!/bin/bash
device=/dev/nvme0
echo $device
nvme format $device
nvme set-feature $device -f 0x0b --value=0x0100
nvme delete-ns $device -n 0x
sleep 5
nvme list
nvme get-log $device -l 200 -i 4
max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`
for i in $(eval echo {1..$max})
do
echo $i
nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl
$device | awk -F: '{print $2}'`
sleep 2
nvme get-log $device -l 200 -i 4
sleep 2
done
nvme list
3> run mdt.hd on those namespaces
Contact Information = naveed...@in.ibm.com
Stack trace output:
-
-
Device id:/dev/nvme0n8
Timestamp:Feb 20 16:57:30 2018
err=
sev=1
Exerciser Name:hxestorage
Serial No:Not Available
Part No:Not Available
Location:Not Available
FRU Number:Not Available
Device:Not Available
Error Text:Hardware Exerciser stopped on error
-
-
Device id:/dev/nvme0n10
Timestamp:Feb 20 16:57:36 2018
err=
sev=1
Exerciser Name:hxestorage
Serial No:Not Available
Part No:Not Available
Location:Not Available
FRU Number:Not Available
Device:Not Available
Error Text:Hung I/O alert! Segment table-1, Detected 1 I/O(s) hung.
Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
Process ID: 0x8161
1st lba Blocks KernelHang Duration
(Hex)(Hex)ThreadCnt(Secs)
** Threshold of 1800 secs on one or more I/Os exceeded!
0x5ae08b 8 7e0457eaf180 44800
-
-
Device id:/dev/nvme0n10
Timestamp:Feb 20 16:57:36 2018
err=
sev=1
Exerciser Name:hxestorage
Serial No:Not Available
Part No:Not Available
Location:Not Available
FRU Number:Not Available
Device:Not Available
Error Text:Hardware Exerciser stopped on error
-
-
Device id:/dev/nvme0n4
Timestamp:Feb 20 17:14:19 2018
err=
sev=4
Exerciser Name:hxestorage
Serial No:Not Available
Part No:Not Available
Location:Not Available
FRU Number:Not Available
Device:Not Available
Error Text:Hung I/O alert! Segment table-1, Detected 1 I/O(s) hung.
Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
Process ID: 0x815b
1st lba Blocks KernelHang Duration
(Hex)(Hex)ThreadCnt(Secs)
0x398a7e 2 71d5a180 33000
-
[17643.202114] INFO: task hxestor
[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64
I can reproduce this issue with 4.13.0-37-generic. The debugfs info for the zip driver shows that 2 requests are pending. Either the requests are not submitted properly (Decomp Req Submitted=0) or not completed (DOORBELL regs = 0). root@crb1s:/sys/kernel/debug/thunderx_zip# cat zip_stats ZIP Device 0 Stats --- Comp Req Submitted: 0 Comp Req Completed: 0 Compress In Bytes : 0 Compressed Out Bytes : 0 Average Chunk size: 0 Average Compression ratio : 0 Decomp Req Submitted : 0 Decomp Req Completed : 0 Decompress In Bytes : 0 Decompressed Out Bytes: 0 Decompress Bad requests : 0 Pending Req : 2 - root@crb1s:/sys/kernel/debug/thunderx_zip# cat zip_regs ZIP Device 0 Registers ZIP_CMD_CTL: 0x0002 ZIP_THROTTLE : 0x0010 ZIP_CONSTANTS : 0x02017c002006 ZIP_QUE0_MAP : 0x0003 ZIP_QUE1_MAP : 0x0003 ZIP_QUE_ENA: 0x0003 ZIP_QUE_PRI: 0x0003 ZIP_QUE0_DONE : 0x ZIP_QUE1_DONE : 0x ZIP_QUE0_DOORBELL : 0x ZIP_QUE1_DOORBELL : 0x ZIP_QUE0_SBUF_ADDR : 0xfa040100 ZIP_QUE1_SBUF_ADDR : 0xfa042000 ZIP_QUE0_SBUF_CTL : 0x03f1 ZIP_QUE1_SBUF_CTL : 0x03f1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755073 Title: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 Status in linux package in Ubuntu: Confirmed Bug description: This is a POTENTIAL REGRESSION. This test has passed with 4.13.0-36.40, but not 4.13.0-37.42 The test will stuck with error message in dmesg: ubuntu@starmie-kernel:~$ dmesg [ 470.227210] zram: Added device: zram0 [ 472.262544] zram0: detected capacity change from 0 to 134217728 [ 472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 475.761947] zram0: detected capacity change from 134217728 to 0 [ 476.796641] zram0: detected capacity change from 0 to 134217728 [ 476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 480.233817] zram0: detected capacity change from 134217728 to 0 [ 481.239001] zram0: detected capacity change from 0 to 134217728 [ 508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [mkfs.ext4:2253] [ 508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd [ 508.087138] CPU: 8 PID: 2253 Comm: mkfs.ext4 Not tainted 4.13.0-37-generic #42-Ubuntu [ 508.087141] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 508.087144] task: 801f57a86900 task.stack: 23ec [ 508.087158] PC is at zip_deflate+0x184/0x2e8 [thunderx_zip] [ 508.087164] LR is at zip_deflate+0x17c/0x2e8 [thunderx_zip] [ 508.087167] pc : [] lr : [] pstate: 20400145 [ 508.087169] sp : 23ec3580 [ 508.087171] x29: 23ec3580 x28: [ 508.087177] x27: 801f57a86900 x26: 0001b104 [ 508.087182] x25: 801f5618c000 x24: 801f6a15bc18 [ 508.087188] x23: 1000 x22: 23ec3688 [ 508.087193] x21: 801f5a2d4880 x20: 801f6a15bc18 [ 508.087199] x19: 23ec3608 x18: [ 508.087204] x17: 0001 x16: [ 508.087209] x15: bd4048db x14: fa13 [ 508.087215] x13: 1000 x12: fa12 [ 508.087220] x11: x10: [ 508.087225] x9 : x8 : [ 508.087230] x7 : x6 : 8000101d6080 [ 508.087236] x5 : 01a69058 x4 : 0008 [ 508.087241] x3 : x2 : [ 508.087246] x1 : 801f6a15be08 x0 : [ 508.087252] Call trace: [ 508.087256] Exception stack(0x23ec3440 to 0x23ec3580) [ 508.087260]
[Kernel-packages] [Bug 1739522] Re: [Bug] ISH support for CFL-H
** Changed in: intel Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: intel Status: New => In Progress ** Information type changed from Private to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739522 Title: [Bug] ISH support for CFL-H Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description ISH driver is not loaded on CFL-H. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1739522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Thanks for doing all the leg work. I'll build a test kernel with that commit and post it shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Proposed kernels show the same improved behaviour as the earlier test
kernels.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
We are seeing this on multiple servers after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory
is continously decreasing at a high rate and the servers start swapping and
finally OOMing services within days. With the 4.10 kernel, decrease of free
memory is slower and stabilizes after a while.
Latest kernel tested is linux-image-4.13.0-32-generic but the issue
also affects older kernels from that series, tested back to linux-
image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.
The servers are running as OpenStack controller nodes using either
Ocata or Pike UCA plus ceph. See attached graph for the memory
behaviour.
== Fix ==
2b9478ffc550("i40e: Fix memory leak related filter programming status")
62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")
== Regression Potential ==
Low. Limited to i40e and fix existing regression.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 9 09:45:50 2018
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
This bug was fixed in the package lttng-modules - 2.10.5-1ubuntu1 --- lttng-modules (2.10.5-1ubuntu1) bionic; urgency=medium * Fix builds for 4.13.0-38 kernel (LP: #1756240) - Update definition of kvm_mmio() to match the new kernel -- Khalid Elmously Fri, 23 Mar 2018 10:20:08 -0400 ** Changed in: lttng-modules (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/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux source package in Artful: Invalid Status in lttng-modules source package in Artful: In Progress Status in linux source package in Bionic: Invalid Status in lttng-modules source package in Bionic: Fix Released Bug description: [Impact] * The 4.13.0-38 artful kernel included a change (backported from 4.15) that modifies the definition of kvm_mmio(). This breaks the lttng-modules-dkms package because it is using the old (<4.15) definition. * lttng-modules-dkms already has a list of kernel version "exceptions" with which it uses the >=4.15 definition. Proposed solution is to add the Ubuntu kernel range 4.13.0-38 up to 4.14.255-255 to that list of exceptions. [Test Case] * Tested by first successfully building lttng-modules-dkms on 4.13.0-37, then reproducing the problem described here on 4.13.0-38, then applying the code-change and confirming that I can successfully build on both 4.13.0-37 and 4.13.0-38 after that. [Regression Potential] * Low-regression potential. Could prevent lttng-modules-dkms from being built for specific kernel versions, but this is unlikely as the change was tested to confirm that it works as expected on 4.13.0-37 and 4.13.0-38 - and should work fine for other Ubuntu kernels as well. The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755245] Re: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42
I've added more smarts into stress-ng to detect if the OOM killer killed these stressors and not mark it as failed http://kernel.ubuntu.com/git/cking/stress- ng.git/commit/?id=be1ef4b962e50ced6d80db7eaa03eee77b43e003 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755245 Title: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42 Status in linux package in Ubuntu: Fix Committed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180309_144848_e1b37@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758375] [NEW] efifb broken on ThunderX-based Gigabyte nodes
Public bug reported: [Impact] The following error is reported on boot: [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for efifb! This results in the efifb not being activated at boot. On this platform, the same device will be initialized by the astdrmfb driver later in boot, so this isn't fatal, so the real SRU justification here is getting rid of the error message. It is possible that there are platforms where the efifb is behind a PCI bridge, and there is no accelerated alternative that will load later. This (theoretical) issue is most likely to impact d-i installs, where only a subset of fb drivers are included. [Test Case] dmesg | grep "failed to claim resource for efifb" [Regression Risk] The fix for this has been upstream since v4.14. I have a test fix in ppa:dannf/efifb for regression testing. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Artful) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Artful) 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/1758375 Title: efifb broken on ThunderX-based Gigabyte nodes Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: In Progress Bug description: [Impact] The following error is reported on boot: [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for efifb! This results in the efifb not being activated at boot. On this platform, the same device will be initialized by the astdrmfb driver later in boot, so this isn't fatal, so the real SRU justification here is getting rid of the error message. It is possible that there are platforms where the efifb is behind a PCI bridge, and there is no accelerated alternative that will load later. This (theoretical) issue is most likely to impact d-i installs, where only a subset of fb drivers are included. [Test Case] dmesg | grep "failed to claim resource for efifb" [Regression Risk] The fix for this has been upstream since v4.14. I have a test fix in ppa:dannf/efifb for regression testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Hmm, even though git describe returns that tag, it seem s-rc2 has that commit. I'll still build an Artful test kernel with that commit to see if it fixes the bug and figure out the tagging in the background. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
It looks like that commit landed in -rc3: git describe --contains e3b8a48 v4.15-rc3~3^2~11 However, -rc2 is good, correct? I'll have a look at the other btrfs commits in -rc2 and see if any stick out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : h
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341982 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT
** Changed in: amd Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742759 Title: boot failure on AMD Raven + WestonXT Status in amd: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: This issue has been fixed with with patch: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm- next-4.16&id=052c299080cd6859f82a8154a7a673fafabe644c drm/amdgpu: add atpx quirk handling (v2) Add quirks for handling PX/HG systems. In this case, add a quirk for a weston dGPU that only seems to properly power down using ATPX power control rather than HG (_PR3). v2: append a new weston XT To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1742759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756121] Re: Xenial update to 4.4.116 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756121 Title: Xenial update to 4.4.116 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.116 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.116 stable release shall be applied: * Linux 4.4.116 * ftrace: Remove incorrect setting of glob search field * mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user copy * ovl: fix failure to fsync lower dir * ACPI: sbshc: remove raw pointer from printk() message * nvme: Fix managing degraded controllers * btrfs: Handle btrfs_set_extent_delalloc failure in fixup worker * pktcdvd: Fix pkt_setup_dev() error path * EDAC, octeon: Fix an uninitialized variable warning * xtensa: fix futex_atomic_cmpxchg_inatomic * alpha: fix reboot on Avanti platform * alpha: fix crash if pthread_create races with signal delivery * signal/sh: Ensure si_signo is initialized in do_divide_error * signal/openrisc: Fix do_unaligned_access to send the proper signal * Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version * Revert "Bluetooth: btusb: fix QCA Rome suspend/resume" * Bluetooth: btsdio: Do not bind to non-removable BCM43341 * HID: quirks: Fix keyboard + touchpad on Toshiba Click Mini not working * kernel/async.c: revert "async: simplify lowest_in_progress()" * media: cxusb, dib0700: ignore XC2028_I2C_FLUSH * media: ts2020: avoid integer overflows on 32 bit machines * watchdog: imx2_wdt: restore previous timeout after suspend+resume * KVM: nVMX: Fix races when sending nested PI while dest enters/leaves L2 * arm: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls * crypto: caam - fix endless loop when DECO acquire fails * media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic * media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors * media: v4l2-compat-ioctl32.c: drop pr_info for unknown buffer type * media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32 * media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha * media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs * media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer * media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32 * media: v4l2-compat-ioctl32.c: avoid sizeof(type) * media: v4l2-compat-ioctl32.c: move 'helper' functions to __get/put_v4l2_format32 * media: v4l2-compat-ioctl32.c: fix the indentation * media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF * vb2: V4L2_BUF_FLAG_DONE is set after DQBUF * media: v4l2-ioctl.c: don't copy back the result for -ENOTTY * nsfs: mark dentry with DCACHE_RCUACCESS * crypto: poly1305 - remove ->setkey() method * crypto: cryptd - pass through absence of ->setkey() * crypto: hash - introduce crypto_hash_alg_has_setkey() * ahci: Add Intel Cannon Lake PCH-H PCI ID * ahci: Add PCI ids for Intel Bay Trail, Cherry Trail and Apollo Lake AHCI * ahci: Annotate PCI ids for mobile Intel chipsets as such * kernfs: fix regression in kernfs_fop_write caused by wrong type * NFS: reject request for id_legacy key without auxdata * NFS: commit direct writes even if they fail partially * NFS: Add a cond_resched() to nfs_commit_release_pages() * nfs/pnfs: fix nfs_direct_req ref leak when i/o falls back to the mds * ubi: block: Fix locking for idr_alloc/idr_remove * mtd: nand: sunxi: Fix ECC strength choice * mtd: nand: Fix nand_do_read_oob() return value * mtd: nand: brcmnand: Disable prefetch by default * mtd: cfi: convert inline functions to macros * media: dvb-usb-v2: lmedm04: move ts2020 attach to dm04_lme2510_tuner * media: dvb-usb-v2: lmedm04: Improve logic checking of warm start * dccp: CVE-2017-8824: use-after-free in DCCP code * sched/rt: Up the root domain ref count when passing it around via IPIs * sched/rt: Use container_of() to get root domain in rto_push_irq_work_func() * usb: gadget: uvc: Missing files for configfs interface * posix-timer: Properly
[Kernel-packages] [Bug 1755509] Re: Xenial update to 4.4.115 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755509 Title: Xenial update to 4.4.115 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.115 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.115 stable release shall be applied: * loop: fix concurrent lo_open/lo_release * bpf: fix branch pruning logic * x86: bpf_jit: small optimization in emit_bpf_tail_call() * bpf: fix bpf_tail_call() x64 JIT * bpf: introduce BPF_JIT_ALWAYS_ON config * bpf: arsh is not supported in 32 bit alu thus reject it * bpf: avoid false sharing of map refcount with max_entries * bpf: fix divides by zero * bpf: fix 32-bit divide by zero * bpf: reject stores into ctx via st and xadd * x86/pti: Make unpoison of pgd for trusted boot work for real * kaiser: fix intel_bts perf crashes * ALSA: seq: Make ioctls race-free * crypto: aesni - handle zero length dst buffer * crypto: af_alg - whitelist mask and type * power: reset: zx-reboot: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * gpio: iop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * gpio: ath79: add missing MODULE_DESCRIPTION/LICENSE * mtd: nand: denali_pci: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE * igb: Free IRQs when device is hotplugged * KVM: x86: emulator: Return to user-mode on L1 CPL=0 emulation failure * KVM: x86: Don't re-execute instruction when not passing CR2 value * KVM: X86: Fix operand/address-size during instruction decoding * KVM: x86: ioapic: Fix level-triggered EOI and IOAPIC reconfigure race * KVM: x86: ioapic: Clear Remote IRR when entry is switched to edge-triggered * KVM: x86: ioapic: Preserve read-only values in the redirection table * ACPI / bus: Leave modalias empty for devices which are not present * cpufreq: Add Loongson machine dependencies * bcache: check return value of register_shrinker * drm/amdgpu: Fix SDMA load/unload sequence on HWS disabled mode * drm/amdkfd: Fix SDMA ring buffer size calculation * drm/amdkfd: Fix SDMA oversubsription handling * openvswitch: fix the incorrect flow action alloc size * mac80211: fix the update of path metric for RANN frame * btrfs: fix deadlock when writing out space cache * KVM: VMX: Fix rflags cache during vCPU reset * xen-netfront: remove warning when unloading module * nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0) * nfsd: Ensure we check stateid validity in the seqid operation checks * grace: replace BUG_ON by WARN_ONCE in exit_net hook * nfsd: check for use of the closed special stateid * lockd: fix "list_add double add" caused by legacy signal interface * hwmon: (pmbus) Use 64bit math for DIRECT format values * net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit * quota: Check for register_shrinker() failure. * SUNRPC: Allow connect to return EHOSTUNREACH * kmemleak: add scheduling point to kmemleak_scan() * drm/omap: Fix error handling path in 'omap_dmm_probe()' * xfs: ubsan fixes * scsi: aacraid: Prevent crash in case of free interrupt during scsi EH path * scsi: ufs: ufshcd: fix potential NULL pointer dereference in ufshcd_config_vreg * media: usbtv: add a new usbid * usb: gadget: don't dereference g until after it has been null checked * staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID * usb: option: Add support for FS040U modem * USB: serial: pl2303: new device id for Chilitag * USB: cdc-acm: Do not log urb submission errors on disconnect * CDC-ACM: apply quirk for card reader * USB: serial: io_edgeport: fix possible sleep-in-atomic * usbip: prevent bind loops on devices attached to vhci_hcd * usbip: list: don't list devices attached to vhci_hcd * USB: serial: simple: add Motorola Tetra driver * usb: f_fs: Prevent gadget unbind if it is already unbound * usb: uas: unconditionally bring back host after reset * selinux: general protection fault in sock_has_perm * serial: imx: Only wakeup via RTSDEN bit if the system has RTS/CTS * spi: imx: do not access
[Kernel-packages] [Bug 1739498] Comment bridged from LTC Bugzilla
--- Comment From frede...@fr.ibm.com 2018-03-23 12:29 EDT---
Hi,
I got my hands on a WS system and could boot kernel 4.13.0-38.43 with
disable_radix kernel option
and I confirm that this issue does not appear anymore.
(I checked before that I actually got it with 4.13.0-37.42)
Regards,
F.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739498
Title:
Ubuntu 17.10 crashes on vmalloc.c
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is seeing a crash on Power9 when running on Artful.
This issue happens only when disabling RPT ("disable_radix"), which is not
the default in Artful.
These fixes are already in Bionic master-next, so they are only being
requested
in Artful.
== Fixes ==
63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")
== Regression Potential ==
These commits are specific to powerpc and fix a crash.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
When running Ubuntu 17.10 on POWER9, I got the following error:
[409038.118908] WARNING: CPU: 47 PID: 294 at
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
[409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
ttm drm tg3 ahci libahci
[409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW
4.13.0-12-generic #13-Ubuntu
[409038.118934] Workqueue: events pcpu_balance_workfn
[409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
[409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR:
[409038.118937] REGS: c03fe3be3810 TRAP: 0700 Tainted: GW
(4.13.0-12-generic)
[409038.118938] MSR: 9282b033
[409038.118944] CR: 24024828 XER: 2004
[409038.118944] CFAR: c032bdb8 SOFTE: 1
GPR00: 2df0 c03fe3be3a90 c15e3000
c000203fff6b6880
GPR04: c000203fff223608 0008 c000203fff6b6888
GPR08: 2df0 0800 0160
c000203fff6b6888
GPR12: 0002 cfaded80 c0f6c050
c03fe3be3bc0
GPR16: 0010 c189daf8
c000203fff223608
GPR20: 2f50 c000203fff2235f8 c000203fff223600
GPR24: c000203fff6b6888 0001
2f50
GPR28: 0002 000f d800
d000
[409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
[409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
[409038.118965] Call Trace:
[409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0
(unreliable)
[409038.118968] [c03fe3be3b60] [c02f5fd4]
pcpu_create_chunk+0xb4/0x1b0
[409038.118970] [c03fe3be3ba0] [c02f7890]
pcpu_balance_workfn+0x600/0x960
[409038.118972] [c03fe3be3ca0] [c01205d8]
process_one_work+0x298/0x5a0
[409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
[409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
[409038.118979] [c03fe3be3e30] [c000b4e8]
ret_from_kernel_thread+0x5c/0x74
[409038.118980] Instruction dump:
[409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78
3b40 e953
---uname output---
4.13.0-12-generic
== Comment: #3 - ANEESH K. K V - 2017-12-20 05:59:13 ==
https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au
The above may be related?
Related discussions
https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz
-aneesh
== Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
I j
[Kernel-packages] [Bug 1758384] [NEW] [Acer AO532h] hibernate/resume failure
Public bug reported: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Acer AO532h] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO532h dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.family: Intel_Mobile dmi.product.name: AO532h dmi.product.version: V1.26 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic hibernate resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758384 Title: [Acer AO532h] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173
[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758384 Title: [Acer AO532h] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Acer AO532h] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO532h dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.family: Intel_Mobile dmi.product.name: AO532h dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745508 Title: Please backport vmd suspend/resume patches to 16.04 hwe Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification == This bug was opened to request commit e2b1820bd5d0 be backported from 4.14 to the 4.13 kernel in Artful. Without this patch, servers with VMD enabled run into issues suspending and resuming. Commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f is in mainline as of v4.14-rc1. [Fixes] commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f Author: Scott Bauer Date: Fri Aug 11 14:54:32 2017 -0600 PCI: vmd: Free up IRQs on suspend path [Impact] Without this patch, servers with VMD enabled may run into issues suspending and resuming [Test Case] Typically this manifests by having many other devices having acquired IRQ resources competing with VMD. Without the patch, the server may fail to suspend when it can't move the IRQs to core 0 because of the lack of IRQs available on core 0. [Regression Potential] Low. This only affects one component of one arch and affects the non-typical use-case of suspending a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758384] 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/1758384 Title: [Acer AO532h] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Acer AO532h] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO532h dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.family: Intel_Mobile dmi.product.name: AO532h dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730770] Re: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs
** Changed in: intel Status: Incomplete => In Progress ** Changed in: intel Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730770 Title: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: Need to enable pmc_core driver for Coffee Lake so we can get at the slp_s0# counter, which measures S0ix residency. Target Kernel:4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739498] Re: Ubuntu 17.10 crashes on vmalloc.c
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739498
Title:
Ubuntu 17.10 crashes on vmalloc.c
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
IBM is seeing a crash on Power9 when running on Artful.
This issue happens only when disabling RPT ("disable_radix"), which is not
the default in Artful.
These fixes are already in Bionic master-next, so they are only being
requested
in Artful.
== Fixes ==
63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")
== Regression Potential ==
These commits are specific to powerpc and fix a crash.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
When running Ubuntu 17.10 on POWER9, I got the following error:
[409038.118908] WARNING: CPU: 47 PID: 294 at
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
[409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
ttm drm tg3 ahci libahci
[409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW
4.13.0-12-generic #13-Ubuntu
[409038.118934] Workqueue: events pcpu_balance_workfn
[409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
[409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR:
[409038.118937] REGS: c03fe3be3810 TRAP: 0700 Tainted: GW
(4.13.0-12-generic)
[409038.118938] MSR: 9282b033
[409038.118944] CR: 24024828 XER: 2004
[409038.118944] CFAR: c032bdb8 SOFTE: 1
GPR00: 2df0 c03fe3be3a90 c15e3000
c000203fff6b6880
GPR04: c000203fff223608 0008 c000203fff6b6888
GPR08: 2df0 0800 0160
c000203fff6b6888
GPR12: 0002 cfaded80 c0f6c050
c03fe3be3bc0
GPR16: 0010 c189daf8
c000203fff223608
GPR20: 2f50 c000203fff2235f8 c000203fff223600
GPR24: c000203fff6b6888 0001
2f50
GPR28: 0002 000f d800
d000
[409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
[409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
[409038.118965] Call Trace:
[409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0
(unreliable)
[409038.118968] [c03fe3be3b60] [c02f5fd4]
pcpu_create_chunk+0xb4/0x1b0
[409038.118970] [c03fe3be3ba0] [c02f7890]
pcpu_balance_workfn+0x600/0x960
[409038.118972] [c03fe3be3ca0] [c01205d8]
process_one_work+0x298/0x5a0
[409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
[409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
[409038.118979] [c03fe3be3e30] [c000b4e8]
ret_from_kernel_thread+0x5c/0x74
[409038.118980] Instruction dump:
[409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78
3b40 e953
---uname output---
4.13.0-12-generic
== Comment: #3 - ANEESH K. K V - 2017-12-20 05:59:13 ==
https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au
The above may be related?
Related discussions
https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz
-aneesh
== Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1739498/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Yeah, rc2 was 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/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750388] Re: 17.10 - BPF test tool build with errors
This bug report shows that you are using the clang-4.0 package from the Ubuntu archive and that it fails to find architecture-specific headers under /usr/include/s390x-linux-gnu, so that is certainly a valid bug in that package. However, clang is not a supported package in Ubuntu main. In Ubuntu 18.04, the default version of clang is clang-6.0, not clang-4.0. Does this build work with clang-6.0? ** Package changed: linux (Ubuntu) => llvm-toolchain-4.0 (Ubuntu) ** Changed in: llvm-toolchain-4.0 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750388 Title: 17.10 - BPF test tool build with errors Status in Ubuntu on IBM z Systems: Triaged Status in llvm-toolchain-4.0 package in Ubuntu: New Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
I built an Artful test kernel with commit e3b8a48. It also needed commit f48bf66b6 as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1757565 Can you test this kernel and see if it resolves this bug? Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Maili
[Kernel-packages] [Bug 1756455] Re: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
Ok, that works. I should be able to provide basic validation much more easily. We are having trouble reproducing the crash with the unpatched kernel, as we've put many remediating workarounds in place and it's been an adventure to remember where they all are and how exactly they all interacted (and also there are some other bugs currently being worked on in our test environment that affect our ability to reproduce as well). We know it will crash though, and as soon as we get the test setup in place to reproduce the crash I'm confident we can repeat it every time and get a good validation that the patch is solving our problem as well. If we still can't reproduce the crash by COB Monday, I'll switch gears to provide just a basic boot/function validation and will make sure I get that to you by Tuesday at the latest. We only have the environment to test xenial ppc64el. We have xenial and trusty x86_64, but not with bnx2x. We don't have artful anywhere that I can test with. Based on that, I was only planning to provide a report for xenial ppc64el. Does the smoke testing make sense to perform without bnx2x hardware present? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: SRU Justification = A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x card attached, and uses openvswitch to bridge an ibmveth interface for traffic from other LPARs. We see the following crash sometimes when running netperf: May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert! May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 0x25e42a7e 0x00462a38 0x00010052 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1 May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: [bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump - ... (dump of registers follows) ... Subsequent debugging reveals that the packets causing the issue come through the ibmveth interface - from the AIX LPAR. The veth protocol is 'special' - communication between LPARs on the same chassis can use very large (64k) frames to reduce overhead. Normal networks cannot handle such large packets, so traditionally, the VIOS partition would signal to the AIX partitions that it was 'special', and AIX would send regular, ethernet-sized packets to VIOS, which VIOS would then send out. This signalling between VIOS and AIX is done in a way that is not standards-compliant, and so was never made part of Linux. Instead, the Linux driver has always understood large frames and passed them up the network stack. In some cases (e.g. with TCP), multiple TCP segments are coalesced into one large packet. In Linux, this goes through the generic receive offload code, using a similar mechanism to GSO. These segments can be very large which presents as a very large MSS (maximum segment size) or gso_size. Normally, the large packet is simply passed to whatever network application on Linux is going to consume it, and everything is OK. However, in this case, the packets go through Open vSwitch, and are then passed to the bnx2x driver. The bnx2x driver/hardware supports TSO and GSO, but with a restriction: the maximum segment size is limited to around 9700 bytes. Normally this is more than adequate. However, if a large packet with very large (>9700 byte) TCP segments arrives through ibmveth, and is passed to bnx2x, the hardware will panic. [Impact] bnx2x card panics, requiring power cycle to restore functionality. The workaround is turning off TSO, which prevents the crash as the kernel resegments *all* packets in software, not just ones that are too big. This has a performance cost. [Fix] Test packet size in bnx2x feature check path and disable GSO if it is too large. To do this we move a function from one file to another and add another in the networking core. [Regression Potential] A/B/X: The changes to the network core are easily reviewed. The changes to behaviour are limited to the bnx2x card driver. The most likely failure case is a false-positive on the size check, which would lead to a performance regression only. T: This also involves a different change to the
[Kernel-packages] [Bug 1756455] 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 1756455 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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Test kernel: GOOD root@ubuntu:~# cat /proc/version_signature Ubuntu 4.13.0-37.42~lp1757565-generic 4.13.13 root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.prod
[Kernel-packages] [Bug 1755245] Re: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42
This failure was probably an OOM kill on the test, the stress-ng update as mentioned in comment #2 will be able to identify these and not mark them as a test failure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755245 Title: linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42 Status in linux package in Ubuntu: Fix Committed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180309_144848_e1b37@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088490/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088489/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] Re: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery
apport information ** Tags added: apport-collected bionic ** Description changed: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. - I am not attaching any logs because I cannot see anything unusual there, - kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in - fact, there is only one entry there "msr: Direct access to MSR 1b0"). - Please let me know what additional information you may need. + I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dmitry 1568 F pulseaudio + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 + InstallationDate: Installed on 2018-03-10 (13 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP HP Spectre x360 Convertible 13-ae0xx + Package: linux-signed + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 + 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-12-generic N/A + linux-backports-modules-4.15.0-12-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 02/22/2018 + dmi.bios.vendor: AMI + dmi.bios.version: F.15 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 83B9 + dmi.board.vendor: HP + dmi.board.version: 56.37 + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Spectre + dmi.product.name: HP Spectre x360 Convertible 13-ae0xx + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088488/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp.
[Kernel-packages] [Bug 1756455] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088494/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088499/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088495/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088497/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088496/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088493/+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/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088491/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088492/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1756455/+attachment/5088498/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: Kernel 4.15.0-12 reboots instead of turning off on HP Spectre x360 13-ae004 on battery Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 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-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.
I tried a lot of thing. Please see this topic for see the list that things than doesn't work https://askubuntu.com/questions/1010405/the-brightness-of-laptop-screen- cannot-be-adjusted-with-either-the-buttons-or-th/1011557 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751887 Title: The brightness of the screen cannot be adjusted with either the buttons or the slider. Status in linux package in Ubuntu: Incomplete Bug description: Brightness is always at 100% and cannot be adjusted with either the FN brightness buttons or the Unity top bar slider. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: albertoinet 1199 F pulseaudio /dev/snd/controlC0: albertoinet 1199 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 20:49:16 2018 HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f InstallationDate: Installed on 2018-02-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Micro-Star International Co., Ltd. GT72VR 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1785IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-1785 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: GT dmi.product.name: GT72VR 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
In *Bionic*, the kernel in proposed (4.15.0-13.14) and in release (4.15.0-12.13) both fix this regression. I won't test the fix on Artful; I don't have the system installed and I don't want to spend the time since Artful won't be supported for very long anyway (and this bug affects only very few users). ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Color dithering not working correctly because the graphics driver assumes the panel support 8bpc, but the panel only supports 6bpc. [Test] User reports the issue start appearing from v4.8-rc2. The issue is fixed with the patch. [Fix] Add a quirk to tell DRM that this panel only supports 6bpc. [Regression Potential] Low. This fix matches a very specific panel. === Original Bug Report === - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To ma
[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
That's great news. I'll SRU those two commits to the Artful kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
