[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL
--- icl_commit_20190702.list_kernv_drm-tip 2019-07-02 13:55:00.666216695
+0800
+++ icl_commit_20190709.list_kernv_drm-tip 2019-07-09 13:40:15.070144631
+0800
@@ -1,13 +1,52 @@
+patches series of drm/i915: Random plane stuff,,,
+1/6 26443a4bc44 ADDED!,drm/i915: Add windowing for primary planes on gen2/3
and chv,2019-07-03 23:08:19,next-20190708
+2/6 423ee8e99aa ADDED!,drm/i915: Disable sprite gamma on ivb-bdw,2019-07-03
23:08:20,next-20190708
+3/6 94e15723df8 ADDED!,drm/i915: Program plane gamma ramps,2019-07-03
23:08:21,next-20190708
+4/6 d56e823ac32 ADDED!,drm/i915: Deal with cpp==8 for g4x
watermarks,2019-07-03 23:08:22,next-20190708
+5/6 94e35ce2217 ADDED!,drm/i915: Cosmetic fix for skl+ plane switch
statement,2019-07-03 23:08:23,next-20190708
+6/6 3e69db291bd,drm/i915: Clean up skl vs. icl plane formats,2019-07-03
23:08:24,next-20190708
+patches series of More mmio and intel_gt cleanups and refactorings,,,
+1/3 9b77011e412 ADDED!,drm/i915: Rework some interrupt handling functions to
take intel_gt,2019-07-04 13:17:54,next-20190708
+2/3 f0818984fa5,drm/i915: Remove some legacy mmio accessors from interrupt
handling,2019-07-04 13:17:55,next-20190708
+3/3 NOT-IN-UPSTREAM,drm/i915: Move dev_priv->pm_i{m,e}r into intel_gt,,
+56e9371bc3f,drm/i915: Deal with machines that expose less than three QGV
points,2019-06-06 15:42:10,next-20190708
+8e9ecb3e1e3,drm/i915/display: Handle lost primary_port across
suspend,2019-07-02 15:09:50,next-20190708
+patches series of drm/i915: CTS fixes,,,
+1/3 361b6905132 ADDED!,drm/i915: fix whitelist selftests with readonly
registers,2019-06-29 14:13:50,next-20190703
+2/3 2c903da50f5 ADDED!,drm/i915: whitelist
PS_(DEPTH|INVOCATION)_COUNT,2019-06-28 15:07:19,next-20190703
+3/3 3fe0107e45a,drm/i915/icl: whitelist PS_(DEPTH|INVOCATION)_COUNT,2019-06-28
15:07:20,next-20190703
+4a8134d57c6,drm/i915/icl: Drop port parameter to
icl_get_combo_buf_trans(),2019-06-25 17:03:48,next-20190703
+patches series of drm/i915: Fix TypeC port mode switching,,,
+01/23 39a5883f867,drm/i915/icl: Add support to read out the TBT PLL HW
state,2019-06-28 17:36:13,next-20190703
+02/23 28212321622 ADDED!,drm/i915: Tune down WARNs about TBT AUX power well
enabling,2019-06-28 17:36:14,next-20190703
+03/23 bc85328ff43,drm/i915: Move the TypeC port handling code to a separate
file,2019-06-28 17:36:15,next-20190703
+04/23 e9b7e1422d4 ADDED!,drm/i915: Sanitize the terminology used for TypeC
port modes,2019-06-28 17:36:16,next-20190703
+05/23 3b2ed431342 ADDED!,drm/i915: Don't enable the DDI-IO power in the TypeC
TBT-alt mode,2019-06-28 17:36:17,next-20190703
+06/23 29ae36abf08 ADDED!,drm/i915: Fix the TBT AUX power well
enabling,2019-06-28 17:36:18,next-20190703
+07/23 dd7239c545b ADDED!,drm/i915: Use the correct AUX power domain in TypeC
TBT-alt mode,2019-06-28 17:36:19,next-20190703
+08/23 ab7bc4e1a55,drm/i915: Unify the TypeC port notation in debug/error
messages,2019-06-28 17:36:20,next-20190703
+09/23 c905eb28bd3,drm/i915: Factor out common parts from TypeC port handling
functions,2019-06-28 17:36:21,next-20190703
+10/23 ddec362724f ADDED!,drm/i915: Wait for TypeC PHY complete flag to clear
in safe mode,2019-06-28 17:36:22,next-20190703
+11/23 424f109f5c5,drm/i915: Handle the TCCOLD power-down event,2019-06-28
17:36:23,next-20190703
+12/23 1cd5ef6ee23 ADDED!,drm/i915: Sanitize the TypeC connect/detect
sequences,2019-06-28 17:36:24,next-20190703
+13/23 32691b58d15 ADDED!,drm/i915: Fix the TypeC port mode sanitization during
loading/resume,2019-06-28 17:36:25,next-20190703
+14/23 8c10e226266 ADDED!,drm/i915: Keep the TypeC port mode fixed for
detect/AUX transfers,2019-06-28 17:36:26,next-20190703
+15/23 4f36afb26cb ADDED!,drm/i915: Sanitize the TypeC FIA lane configuration
decoding,2019-06-28 17:36:27,next-20190703
+16/23 866955fa452 ADDED!,drm/i915: Sanitize the shared DPLL reserve/release
interface,2019-06-28 17:36:28,next-20190703
+17/23 01b24f50b67 ADDED!,drm/i915: Sanitize the shared DPLL find/reference
interface,2019-06-28 17:36:29,next-20190703
+18/23 726ca99666d,drm/i915/icl: Split getting the DPLLs to port type specific
functions,2019-06-28 17:36:30,next-20190703
+19/23 eea72c4c216,drm/i915/icl: Reserve all required PLLs for TypeC
ports,2019-06-28 17:36:31,next-20190703
+20/23 24a7bfe0c2d,drm/i915: Keep the TypeC port mode fixed when the port is
active,2019-06-28 17:36:32,next-20190703
+21/23 d5ce34da314 ADDED!,drm/i915: Add state verification for the TypeC port
mode,2019-06-28 17:36:33,next-20190703
+22/23 a171f8e7f46 ADDED!,drm/i915: Remove unneeded disconnect in TypeC legacy
port mode,2019-06-28 17:36:34,next-20190703
+23/23 3ee2771e47b ADDED!,drm/i915: WARN about invalid lane reversal in
TBT-alt/DP-alt modes,2019-06-28 17:36:35,next-20190703
+patches series of 9c811fce8a4,,,
+1/3 9c811fce8a4,drm/i915/icl: Add new supported CD clocks,2019-06-25
18:40:51,next-20190628
+2/3 6e63790efdf,drm/i915/ehl: Remove unsupported cd clocks,2019-06-25
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
The mainline kernel works fine. Thanks for the tip. Please could you elaborate a little what was wrong in layman's terms? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x
** Tags added: ubuntu-qrt-kernel-security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813721
Title:
SECURITY_SELINUX_DISABLE should be enable on X s390x
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
enabled in all of our kernels.
Currently it's not enabled for s390x in Xenial. And causing the
test_081_config_security_selinux_disable test in ubuntu_kernel_security
test suite complaining about this:
==
FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
== Test ==
A test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
This issue can be verified with a q-r-t test:
test_081_config_security_selinux_disable, the test will pass with the
patched kernel.
test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ...
(skipped: l) ok
== Regression Potential ==
Low, we already have this config enabled in all kernels except this
specific Xenial s390x.
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-142-generic N/A
linux-backports-modules-4.4.0-142-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813721/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
No I think you did everything right.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Bug description:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 113-M2-E113
dmi.board.vendor: EVGA
dmi.board.version: 1
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.chassis.vendor: EVGA
dmi.chassis.version: 113-M2-E113
dmi.modalia
[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x
** Description changed:
== SRU Justification ==
- Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in
all of our kernels.
+ Security team requires the CONFIG_SECURITY_SELINUX_DISABLE should be
+ enabled in all of our kernels.
+
+ Currently it's not enabled for s390x in Xenial. And causing the
+ test_081_config_security_selinux_disable test in ubuntu_kernel_security
+ test suite complaining about this:
+
+ ==
+ FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
+ Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
+ --
+ Traceback (most recent call last):
+ File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
+ self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
+ File "./test-kernel-security.py", line 207, in assertKernelConfig
+ self.assertKernelConfigSet(name)
+ File "./test-kernel-security.py", line 194, in assertKernelConfigSet
+ '%s option was expected to be set in the kernel config' % name)
+ AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
== Test ==
A test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
- This issue can be verified with test_081_config_security_selinux_disable
- test from q-r-t, the test will pass with the patched kernel.
+ This issue can be verified with a q-r-t test:
+ test_081_config_security_selinux_disable, the test will pass with the
+ patched kernel.
test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ...
(skipped: l) ok
== Regression Potential ==
- Low, we already have this config enabled in all kernels except this specific
Xenial s390x.
+ Low, we already have this config enabled in all kernels except this
+ specific Xenial s390x.
-
- == Original Bug Report ==
-
- This test from q-r-t has failed exclusively on Xenial s390x:
- ==
- FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
- Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
- --
- Traceback (most recent call last):
- File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
- self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
- File "./test-kernel-security.py", line 207, in assertKernelConfig
- self.assertKernelConfigSet(name)
- File "./test-kernel-security.py", line 194, in assertKernelConfigSet
- '%s option was expected to be set in the kernel config' % name)
- AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-142-generic N/A
linux-backports-modules-4.4.0-142-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813721
Title:
SECURITY_SELINUX_DISABLE should be enable on X s390x
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: thermald (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: thermald (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dmesg
Status in linux package in Ubuntu:
In Progress
Status in thermald package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in thermald source package in Bionic:
New
Status in linux source package in Disco:
Fix Committed
Status in thermald source package in Disco:
New
Bug description:
== SRU Justification Bionic/Disco ==
proc_thermal messages are spamming the kernel log when used in
conjunction with thermal. This is because the message is not set at
the correct kernel log level.
== Fix ==
Upstream fix 44c0c23725a16c8803b8809b87651405e8741e4d ("drivers:
thermal: processor_thermal: Downgrade error message"). This is in 5.2
so not applicable for Eoan.
This fix needs a minor backport wiggle for Bionic because the driver
is located in a different place.
== Test case ==
Without the fix the kernel log is being spammed periodically with
messages in the form:
[ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
[ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
With the fix these messages are no longer appearing.
== Regression Potential ==
This changes the log level, so regression potential is very limited,
unless some program is relying on this message for some particular
reason.
---
[ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
[ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
[ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91]
[ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91]
[ 41.572682] random: crng init done
[ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting
Kernel 4.18.0-18-generic
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: juno 1175 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-04-15 (0 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0025 Intel Corp.
Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 1ea7:0064
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N24_25GU
Package: thermald 1.7.0-5ubuntu2
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic
root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi=
acpi_os_name=Linux vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
RelatedPackageVersions:
linux-restricted-modules-4.18.0-18-generic N/A
linux-backports-modules-4.18.0-18-generic N/A
linux-firmware 1.173.5
Tags: bionic
Uname: Linux 4.18.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/18/2018
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.06
dmi.board.asset.tag: Tag 12345
dmi.board.name: N24_25GU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N24_25GU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
To manage
[Kernel-packages] [Bug 1835845] Re: Bionic update: upstream stable patchset 2019-07-08
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1835845
Title:
Bionic update: upstream stable patchset 2019-07-08
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-07-08
Ported from the following upstream stable releases:
v4.14.61, v4.17.13,
v4.14.62, v4.17.14,
v4.14.63, v4.17.15,
v4.14.64, v4.17.16,
v4.14.65, v4.17.17,
v4.14.66, v4.17.18,
v4.14.67, v4.17.19
from git://git.kernel.org/
bonding: avoid lockdep confusion in bond_get_stats()
inet: frag: enforce memory limits earlier
ipv4: frags: handle possible skb truesize change
net: dsa: Do not suspend/resume closed slave_dev
net: stmmac: Fix WoL for PCI-based setups
rxrpc: Fix user call ID check in rxrpc_service_prealloc_one
can: ems_usb: Fix memory leak on ems_usb_disconnect()
virtio_balloon: fix another race between migration and ballooning
x86/apic: Future-proof the TSC_DEADLINE quirk for SKX
kvm: x86: vmx: fix vpid leak
audit: fix potential null dereference 'context->module.name'
userfaultfd: remove uffd flags from vma->vm_flags if UFFD_EVENT_FORK fails
RDMA/uverbs: Expand primary and alt AV port checks
crypto: padlock-aes - Fix Nano workaround data corruption
drm/vc4: Reset ->{x, y}_scaling[1] when dealing with uniplanar formats
scsi: sg: fix minor memory leak in error path
net/mlx5e: E-Switch, Initialize eswitch only if eswitch manager
net/mlx5e: Set port trust mode to PCP as default
x86/efi: Access EFI MMIO data as unencrypted when SEV is active
drm/atomic: Check old_plane_state->crtc in drm_atomic_helper_async_check()
drm/atomic: Initialize variables in drm_atomic_helper_async_check() to make
gcc happy
scsi: qla2xxx: Fix unintialized List head crash
scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion
scsi: qla2xxx: Fix ISP recovery on unload
scsi: qla2xxx: Return error when TMF returns
genirq: Make force irq threading setup more robust
nohz: Fix local_timer_softirq_pending()
nohz: Fix missing tick reprogram when interrupting an inline softirq
ring_buffer: tracing: Inherit the tracing setting to next ring buffer
i2c: imx: Fix reinit_completion() use
Btrfs: fix file data corruption after cloning a range and fsync
nvme-pci: allocate device queues storage space at probe
nvme-pci: Fix queue double allocations
xfs: catch inode allocation state mismatch corruption
xfs: validate cached inodes are free when allocated
perf/x86/intel/uncore: Fix hardcoded index of Broadwell extra PCI devices
parisc: Enable CONFIG_MLONGCALLS by default
parisc: Define mb() and add memory barriers to assembler unlock sequences
kasan: add no_sanitize attribute for clang builds
Mark HI and TASKLET softirq synchronous
xen/netfront: don't cache skb_shinfo()
scsi: sr: Avoid that opening a CD-ROM hangs with runtime power management
enabled
scsi: qla2xxx: Fix memory leak for allocating abort IOCB
init: rename and re-order boot_cpu_state_init()
root dentries need RCU-delayed freeing
make sure that __dentry_kill() always invalidates d_seq, unhashed or not
fix mntput/mntput race
fix __legitimize_mnt()/mntput() race
mtd: nand: qcom: Add a NULL check for devm_kasprintf()
phy: phy-mtk-tphy: use auto instead of force to bypass utmi signals
ARM: dts: imx6sx: fix irq for pcie bridge
kprobes/x86: Fix %p uses in error messages
x86/irqflags: Provide a declaration for native_save_fl
x86/apic: Ignore secondary threads if nosmt=force
x86/mm/kmmio: Make the tracer robust against L1TF
tools headers: Synchronise x86 cpufeatures.h for L1TF additions
x86/microcode: Allow late microcode loading with SMT disabled
x86/smp: fix non-SMP broken build due to redefinition of
apic_id_is_primary_thread
cpu/hotplug: Non-SMP machines do not make use of booted_once
sched/deadline: Update rq_clock of later_rq when pushing a task
zram: remove BD_CAP_SYNCHRONOUS_IO with writeback feature
x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled
x86: i8259: Add missing include file
kbuild: verify that $DEPMOD is installed
crypto: x86/sha256-mb - fix digest copy in sha256_mb_mgr_get_comp_job_avx2()
cr
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
Somehow descriptor override doesn't work for your system. Please test latest mainline kernel here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Expired Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. Workaround: use kernel 4.19.4. Sidenote: thanks to penalvch for explaining how to report this! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x
** Description changed:
+ == SRU Justification ==
+ Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in
all of our kernels.
+
+ == Test ==
+ A test kernel could be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
+
+ This issue can be verified with test_081_config_security_selinux_disable
+ test from q-r-t, the test will pass with the patched kernel.
+
+ test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest)
+ Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) ...
(skipped: l) ok
+
+ == Regression Potential ==
+ Low, we already have this config enabled in all kernels except this specific
Xenial s390x.
+
+
+ == Original Bug Report ==
+
This test from q-r-t has failed exclusively on Xenial s390x:
- ==
- FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
- Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
- --
- Traceback (most recent call last):
- File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
- self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
- File "./test-kernel-security.py", line 207, in assertKernelConfig
- self.assertKernelConfigSet(name)
- File "./test-kernel-security.py", line 194, in assertKernelConfigSet
- '%s option was expected to be set in the kernel config' % name)
- AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
-
- --
+ ==
+ FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
+ Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
+ --
+ Traceback (most recent call last):
+ File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
+ self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
+ File "./test-kernel-security.py", line 207, in assertKernelConfig
+ self.assertKernelConfigSet(name)
+ File "./test-kernel-security.py", line 194, in assertKernelConfigSet
+ '%s option was expected to be set in the kernel config' % name)
+ AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
+
+ --
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
-
+
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
-
+
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
-
+
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3
crashkernel=196M
RelatedPackageVersions:
- linux-restricted-modules-4.4.0-142-generic N/A
- linux-backports-modules-4.4.0-142-generic N/A
- linux-firmware 1.157.21
+ linux-restricted-modules-4.4.0-142-generic N/A
+ linux-backports-modules-4.4.0-142-generic N/A
+ linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813721
Title:
SECURITY_SELINUX_DISABLE should be enable on X s390x
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
Security team requires the CONFIG_SECURITY_SELINUX_DISABLE to be enabled in
all of our kernels.
== Test ==
A test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1813721-s390x-selinux/
This issue can be ver
[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
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/1813721
Title:
SECURITY_SELINUX_DISABLE should be enable on X s390x
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
This test from q-r-t has failed exclusively on Xenial s390x:
==
FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2158, in
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in
the kernel config
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.4.0-142-generic N/A
linux-backports-modules-4.4.0-142-generic N/A
linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813721/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
@phil995511, from your log in comment #35, I think that has the same result with my comment #30 because 1) wifi seems to work perfectly, and 2) Bluetooth "request failed to create LE connection: status 0x0c" takes firmware update in bug 1835449. As for your dmesg log in comment #36 in regard to backport-iwlwifi-dkms, I don't think you're really using iwlwifi dkms module because there is no version info printed in dmesg. To make sure that, try `dkms status` and see if backport-iwlwifi has been listed as installed for current running kernel version. By the way, I also noticed following error messages about tsc clocksource: clocksource: timekeeping watchdog on CPU6: Marking clocksource 'tsc' as unstable because the skew is too large: clocksource: 'hpet' wd_now: 1ea65be5 wd_last: 1e28da7d mask: clocksource: 'tsc' cs_now: 172ded8864 cs_last: 16ea6ab29a mask: tsc: Marking TSC unstable due to clocksource watchdog TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. It's a known issue that we're tracking, and as it suggested, currently the only solution is to add 'tsc=unstable' to kernel boot parameters. Would you mind attaching `cat /proc/cpuinfo` so that we may add a record to the affected CPU models list? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829652] Re: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel
kernel 5.0.0-21-generic fixes the issue. Thanks for your help! ** Tags removed: disco verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829652 Title: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: [Impact] If you pass a vf of an intel 10G nic - such as the X550T - into a VM, and that nic does not support IPsec, the system will oops. [Test Case] Enable virtual functions (e.g. (class/net/em1/device/sriov_numvfs = 4). Use an XML snippet to delegate virtual function to VM, e.g.: Start VM. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git/commit/?h=dev-queue&id=a2243a4faae5a3c210995ade2cbca369b20daa0f [Regression Risk] Restricted to the ixgbe driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835845] [NEW] Bionic update: upstream stable patchset 2019-07-08
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-07-08
Ported from the following upstream stable releases:
v4.14.61, v4.17.13,
v4.14.62, v4.17.14,
v4.14.63, v4.17.15,
v4.14.64, v4.17.16,
v4.14.65, v4.17.17,
v4.14.66, v4.17.18,
v4.14.67, v4.17.19
from git://git.kernel.org/
bonding: avoid lockdep confusion in bond_get_stats()
inet: frag: enforce memory limits earlier
ipv4: frags: handle possible skb truesize change
net: dsa: Do not suspend/resume closed slave_dev
net: stmmac: Fix WoL for PCI-based setups
rxrpc: Fix user call ID check in rxrpc_service_prealloc_one
can: ems_usb: Fix memory leak on ems_usb_disconnect()
virtio_balloon: fix another race between migration and ballooning
x86/apic: Future-proof the TSC_DEADLINE quirk for SKX
kvm: x86: vmx: fix vpid leak
audit: fix potential null dereference 'context->module.name'
userfaultfd: remove uffd flags from vma->vm_flags if UFFD_EVENT_FORK fails
RDMA/uverbs: Expand primary and alt AV port checks
crypto: padlock-aes - Fix Nano workaround data corruption
drm/vc4: Reset ->{x, y}_scaling[1] when dealing with uniplanar formats
scsi: sg: fix minor memory leak in error path
net/mlx5e: E-Switch, Initialize eswitch only if eswitch manager
net/mlx5e: Set port trust mode to PCP as default
x86/efi: Access EFI MMIO data as unencrypted when SEV is active
drm/atomic: Check old_plane_state->crtc in drm_atomic_helper_async_check()
drm/atomic: Initialize variables in drm_atomic_helper_async_check() to make gcc
happy
scsi: qla2xxx: Fix unintialized List head crash
scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion
scsi: qla2xxx: Fix ISP recovery on unload
scsi: qla2xxx: Return error when TMF returns
genirq: Make force irq threading setup more robust
nohz: Fix local_timer_softirq_pending()
nohz: Fix missing tick reprogram when interrupting an inline softirq
ring_buffer: tracing: Inherit the tracing setting to next ring buffer
i2c: imx: Fix reinit_completion() use
Btrfs: fix file data corruption after cloning a range and fsync
nvme-pci: allocate device queues storage space at probe
nvme-pci: Fix queue double allocations
xfs: catch inode allocation state mismatch corruption
xfs: validate cached inodes are free when allocated
perf/x86/intel/uncore: Fix hardcoded index of Broadwell extra PCI devices
parisc: Enable CONFIG_MLONGCALLS by default
parisc: Define mb() and add memory barriers to assembler unlock sequences
kasan: add no_sanitize attribute for clang builds
Mark HI and TASKLET softirq synchronous
xen/netfront: don't cache skb_shinfo()
scsi: sr: Avoid that opening a CD-ROM hangs with runtime power management
enabled
scsi: qla2xxx: Fix memory leak for allocating abort IOCB
init: rename and re-order boot_cpu_state_init()
root dentries need RCU-delayed freeing
make sure that __dentry_kill() always invalidates d_seq, unhashed or not
fix mntput/mntput race
fix __legitimize_mnt()/mntput() race
mtd: nand: qcom: Add a NULL check for devm_kasprintf()
phy: phy-mtk-tphy: use auto instead of force to bypass utmi signals
ARM: dts: imx6sx: fix irq for pcie bridge
kprobes/x86: Fix %p uses in error messages
x86/irqflags: Provide a declaration for native_save_fl
x86/apic: Ignore secondary threads if nosmt=force
x86/mm/kmmio: Make the tracer robust against L1TF
tools headers: Synchronise x86 cpufeatures.h for L1TF additions
x86/microcode: Allow late microcode loading with SMT disabled
x86/smp: fix non-SMP broken build due to redefinition of
apic_id_is_primary_thread
cpu/hotplug: Non-SMP machines do not make use of booted_once
sched/deadline: Update rq_clock of later_rq when pushing a task
zram: remove BD_CAP_SYNCHRONOUS_IO with writeback feature
x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is disabled
x86: i8259: Add missing include file
kbuild: verify that $DEPMOD is installed
crypto: x86/sha256-mb - fix digest copy in sha256_mb_mgr_get_comp_job_avx2()
crypto: vmac - require a block cipher with 128-bit block size
crypto: vmac - separate tfm and request context
crypto: blkcipher - fix crash flushing dcache in error path
crypto: ablkcipher - fix crash flushing dcache in error path
crypto: skcipher - fix aligning block size in skcipher_copy_iv()
crypto: skcipher - fix crash flushing dcache in error path
x86/platform/UV: Mark memblock related init code and data correctly
dccp: fix undefined behavior with 'cwnd' shift in ccid2_cwnd_restart()
l2tp: use sk_dst_check() to avoid race on sk->sk_dst_cache
llc: use refcount_inc_not_
Re: [Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
That was my personal experience and conclusion after being in this thread for *years* and being an Ubuntu user for even more years. So save yourself some time - that's my message. On Mon, Jul 8, 2019 at 4:22 PM hexvolt wrote: > I feel like I have to share my experience with this WiFi adapter and > ubuntu. I'm in this thread for a few years. In the beginning, I tried > everything, all permutations of kernel versions and driver versions and > sometimes it worked a little better than not working at all, sometimes it > was working but dead slow, but in any way after the next software update, > you would have to start this journey again. Bluetooth never worked > properly. Almost always, nothing was stable. It was like I was spending > days trying to hack the system and make basic vital things work, despite > the fact I spent quite some money on my Ubuntu-based laptop. > > Then I gave up and, after googling a lot, I bought another WiFi module > Intel 7620. WiFi was finally stable. Bluetooth never was stable either > though, so I didn't use it and by that time I was just happy to have a > stable WiFi. But after each software update, I held my breath and rechecked > if it still works properly and not lagging at 1MBpS speed. As to Bluetooth > - you can still forget about it. > > This is my advice: if you need everything to work properly and stable, and > you need the same Unix eco-system for work\programming (or just because you > like it), my advice - just buy Mac next time you will be upgrading your > hardware. Unfortunately, that's the only way to have Unix-based user > machine (not talking about servers) with working hardware and peripherals. > Ubuntu's driver's system has a major flaw in design because of its hard > dependency on kernel versions. That's why this will *always* happen - > broken drivers, unstable devices etc etc with every update. And that's why > hardware manufacturers don't produce linux drivers much - it's just too > expensive to maintain and redevelop them for each combination of kernel\OS > versions you have. > > TLDR: Unfortunately, this is the endless problem you will ALWAYS have in > linux, not just with this WiFi module. No matter how hard the community or > manufacturers commit to Linux's driver's base. If you want a proper > Unix-based system with stable hardware and peripherals, buy Mac and ditch > Ubuntu. Unless you are getting fun digging into kernels and hacking the OS > on a regular basis. > > On Mon, Jul 8, 2019 at 1:15 PM Jean wrote: > >> Hello, the kuba-moo / benjarobin driver+patches worked fine until today >> when I migrated from Debian Stretch to Debian Buster. I could get wifi >> working, but not bluetooth, because the 'bpatch' try to uninstall the >> current linux-image and replace it by 5 others packages, which could >> break my system. Something appears to be changed in the way of using >> kernel source, but I don't know enough to understand how to manage it. >> Does anyone use mt7630e with Debian Buster and can help me ? Thanks a >> lot. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1220146 >> >> Title: >> Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box >> >> Status in HWE Next: >> Fix Released >> Status in HWE Next trusty series: >> Won't Fix >> Status in Linux: >> Unknown >> Status in vivid: >> New >> Status in linux package in Ubuntu: >> Triaged >> Status in linux-lts-xenial package in Ubuntu: >> Confirmed >> Status in linux package in Fedora: >> New >> >> Bug description: >> This device is appearing in some OEM machines, but driver is not yet >> available in mainline. >> >> The driver seems to be present in machines with pre-installed OS, but >> isn't available on the download-and-install versions! >> >> The driver that upstream is working on can be found at >> https://github.com/lwfinger/mt7630. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions >> > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next: Fix Released Status in HWE Next trusty series: Won't Fix Status in Linux: Unknown Status in vivid: New Status in linux package in Ubuntu: Triaged Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.ne
[Kernel-packages] [Bug 1274908] Re: Consider adding a 'semi automatic' audio change switch to HDMI input.
Is this just a bug? Here is the pulseaudio debug I get when inserting my HDMI cable. It can be seen it's *trying* to switch over, but the lack of profile? is causing the issue. 4.15.0-54-generic kernel, Ubuntu 18.04, pulseaudio 1:11.1-1ubuntu7.2 An explicit 'pactl set-card-profile 0 output:hdmi-stereo-extra1' works. Some race issue with setup? Jul 8 21:51:32 kent gsd-color[1762]: no xrandr-Samsung Electric Company-SAMSUNG-16780800 device found: Failed to find output xrandr-Samsung Electric Company-SAMSUNG-16780800 Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] alsa-util.c: Monitor name in ELD info is 'SAMSUNG' (for device=7) Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] module-alsa-card.c: Jack 'HDMI/DP,pcm=7 Jack' is now plugged in Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] device-port.c: Setting port hdmi-output-1 to status yes Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port hdmi-output-1 Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port hdmi-output-1, preferred = hdmi-stereo-extra1 Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: No suitable profile found Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-stereo-extra1 to availability status unknown Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-surround-extra1 to availability status unknown Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-surround71-extra1 to availability status unknown Jul 8 21:51:32 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] alsa-util.c: ELD info empty (for device=7) Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] module-alsa-card.c: Jack 'HDMI/DP,pcm=7 Jack' is now unplugged Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] device-port.c: Setting port hdmi-output-1 to status no Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-stereo-extra1 to availability status no Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-surround-extra1 to availability status no Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-surround71-extra1 to availability status no Jul 8 21:51:44 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:46 kent gsd-color[1762]: no xrandr-Samsung Electric Company-SAMSUNG-16780800 device found: Failed to find output xrandr-Samsung Electric Company-SAMSUNG-16780800 Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] alsa-util.c: Monitor name in ELD info is 'SAMSUNG' (for device=7) Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] module-alsa-card.c: Jack 'HDMI/DP,pcm=7 Jack' is now plugged in Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] device-port.c: Setting port hdmi-output-1 to status yes Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port hdmi-output-1 Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port hdmi-output-1, preferred = hdmi-stereo-extra1 Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] module-switch-on-port-available.c: No suitable profile found Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-stereo-extra1 to availability status unknown Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. Jul 8 21:51:46 kent pulseaudio[6907]: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:hdmi-surround-extra1 to availability status unknown Jul 8 21:51
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
I feel like I have to share my experience with this WiFi adapter and ubuntu. I'm in this thread for a few years. In the beginning, I tried everything, all permutations of kernel versions and driver versions and sometimes it worked a little better than not working at all, sometimes it was working but dead slow, but in any way after the next software update, you would have to start this journey again. Bluetooth never worked properly. Almost always, nothing was stable. It was like I was spending days trying to hack the system and make basic vital things work, despite the fact I spent quite some money on my Ubuntu-based laptop. Then I gave up and, after googling a lot, I bought another WiFi module Intel 7620. WiFi was finally stable. Bluetooth never was stable either though, so I didn't use it and by that time I was just happy to have a stable WiFi. But after each software update, I held my breath and rechecked if it still works properly and not lagging at 1MBpS speed. As to Bluetooth - you can still forget about it. This is my advice: if you need everything to work properly and stable, and you need the same Unix eco-system for work\programming (or just because you like it), my advice - just buy Mac next time you will be upgrading your hardware. Unfortunately, that's the only way to have Unix-based user machine (not talking about servers) with working hardware and peripherals. Ubuntu's driver's system has a major flaw in design because of its hard dependency on kernel versions. That's why this will *always* happen - broken drivers, unstable devices etc etc with every update. And that's why hardware manufacturers don't produce linux drivers much - it's just too expensive to maintain and redevelop them for each combination of kernel\OS versions you have. TLDR: Unfortunately, this is the endless problem you will ALWAYS have in linux, not just with this WiFi module. No matter how hard the community or manufacturers commit to Linux's driver's base. If you want a proper Unix-based system with stable hardware and peripherals, buy Mac and ditch Ubuntu. Unless you are getting fun digging into kernels and hacking the OS on a regular basis. On Mon, Jul 8, 2019 at 1:15 PM Jean wrote: > Hello, the kuba-moo / benjarobin driver+patches worked fine until today > when I migrated from Debian Stretch to Debian Buster. I could get wifi > working, but not bluetooth, because the 'bpatch' try to uninstall the > current linux-image and replace it by 5 others packages, which could > break my system. Something appears to be changed in the way of using > kernel source, but I don't know enough to understand how to manage it. > Does anyone use mt7630e with Debian Buster and can help me ? Thanks a > lot. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1220146 > > Title: > Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box > > Status in HWE Next: > Fix Released > Status in HWE Next trusty series: > Won't Fix > Status in Linux: > Unknown > Status in vivid: > New > Status in linux package in Ubuntu: > Triaged > Status in linux-lts-xenial package in Ubuntu: > Confirmed > Status in linux package in Fedora: > New > > Bug description: > This device is appearing in some OEM machines, but driver is not yet > available in mainline. > > The driver seems to be present in machines with pre-installed OS, but > isn't available on the download-and-install versions! > > The driver that upstream is working on can be found at > https://github.com/lwfinger/mt7630. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next: Fix Released Status in HWE Next trusty series: Won't Fix Status in Linux: Unknown Status in vivid: New Status in linux package in Ubuntu: Triaged Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:queued + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Testing - phase-changed: Monday, 08. July 2019 12:34 UTC + phase: Signoff + phase-changed: Monday, 08. July 2019 20:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Monday, 08. July 2019 20:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Monday, 08. July 2019 12:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:building,signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834675] Re: zfs-linux should be updated to 0.8.1
Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1834675 Title: zfs-linux should be updated to 0.8.1 Status in zfs-linux package in Ubuntu: Fix Released Bug description: 0.8.1 is the latest stable version. Eoan should ideally include this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1834675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
Still fails:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
===
thermald:
Installed: 1.8.0-1ubuntu1
Candidate: 1.8.0-1ubuntu1
Version table:
*** 1.8.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
===
5.0.0-20-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Thank's. I will return on sunday to this because I have a brake. Oryginalna wiadomość Od: Kai-Heng Feng Data: 08.07.2019 19:37 (GMT+01:00) Do: t...@interia.pl Temat: [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Spotted this commit when I am doing an unrelated task:commit f7fac17ca925faa03fc5eb854c081a24075f8badAuthor: Andrey Smirnov Date: Wed May 22 14:34:01 2019 +0300 xhci: Convert xhci_handshake() to use readl_poll_timeout_atomic() Xhci_handshake() implements the algorithm already captured by readl_poll_timeout_atomic(). Convert the former to use the latter to avoid repetition. Turned out this patch also fixes a bug on the AMD Stoneyridge platform where usleep(1) sometimes takes over 10ms. This means a 5 second timeout can easily take over 15 seconds which will trigger the watchdog and reboot the system. [Add info about patch fixing a bug to commit message -Mathias] Signed-off-by: Andrey Smirnov Tested-by: Raul E Rangel Reviewed-by: Raul E Rangel Cc: Signed-off-by: Mathias Nyman Signed-off-by: Greg Kroah-Hartman Can you try this? It's in Linux kernel v5.2.-- You received this bug notification because you are subscribed to the bugreport.https://bugs.launchpad.net/bugs/1822363Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detectedStatus in linux package in Ubuntu: ConfirmedBug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional.To manage notifications about this bug go to:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Spotted this commit when I am doing an unrelated task: commit f7fac17ca925faa03fc5eb854c081a24075f8bad Author: Andrey Smirnov Date: Wed May 22 14:34:01 2019 +0300 xhci: Convert xhci_handshake() to use readl_poll_timeout_atomic() Xhci_handshake() implements the algorithm already captured by readl_poll_timeout_atomic(). Convert the former to use the latter to avoid repetition. Turned out this patch also fixes a bug on the AMD Stoneyridge platform where usleep(1) sometimes takes over 10ms. This means a 5 second timeout can easily take over 15 seconds which will trigger the watchdog and reboot the system. [Add info about patch fixing a bug to commit message -Mathias] Signed-off-by: Andrey Smirnov Tested-by: Raul E Rangel Reviewed-by: Raul E Rangel Cc: Signed-off-by: Mathias Nyman Signed-off-by: Greg Kroah-Hartman Can you try this? It's in Linux kernel v5.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 595047]
correction:
> In this case it's 1 seconds.
*In this case it's 10 seconds.
Also, heads up:
I found that 'tlp' in `/etc/default/tlp`, on ArchLinux, will overwrite the
values set in `/etc/sysctl.d/*.conf` files if these are set to non `0`, ie.
MAX_LOST_WORK_SECS_ON_AC=10
MAX_LOST_WORK_SECS_ON_BAT=10
will set:
vm.dirty_expire_centisecs=1000
vm.dirty_writeback_centisecs=1000
regardless of what values you set them in `/etc/sysctl.d/*.conf` files.
/etc/default/tlp is owned by tlp 1.2.2-1
Not setting those (eg. commenting them out) will have tlp set the to its
default of 15 sec (aka =1500). So the workaround is to set them to =0
which makes tlp not set them at all, thus the values from
`/etc/sysctl.d/*.conf` files is allowed to remain as set.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/595047/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 595047]
Had this again 20 minutes ago.
Was dopying 8.7GiB of data from one directory to another directory on the same
filesystem (ext4 (rw,relatime,data=ordered)) on the same disk (Western Digital
WDC WD30EZRX-00D8PB0 spinning metal disk).
The KDE UI became unresponsive (Everything other than /home and user
data in on a SSD), could not launch any new applications. Opening a new
tab on Firefox to go to Youtube didnt load the page, and kept saying
waiting for youtube.com in the status bar (network gets halted?).
dmesg shows these, are they important?
[25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120
seconds.
[25013.905945] Tainted: P OE4.15.0-54-generic #58-Ubuntu
[25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[25013.905949] DOMCacheThread D0 17496 2243 0x
[25013.905951] Call Trace:
[25013.905954] __schedule+0x291/0x8a0
[25013.905957] schedule+0x2c/0x80
[25013.905959] jbd2_log_wait_commit+0xb0/0x120
[25013.905962] ? wait_woken+0x80/0x80
[25013.905965] __jbd2_journal_force_commit+0x61/0xb0
[25013.905967] jbd2_journal_force_commit+0x21/0x30
[25013.905970] ext4_force_commit+0x29/0x2d
[25013.905972] ext4_sync_file+0x14a/0x3b0
[25013.905975] vfs_fsync_range+0x51/0xb0
[25013.905977] do_fsync+0x3d/0x70
[25013.905980] SyS_fsync+0x10/0x20
[25013.905982] do_syscall_64+0x73/0x130
[25013.905985] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[25013.905987] RIP: 0033:0x7fc9cb839b07
[25013.905988] RSP: 002b:7fc9a7aeb200 EFLAGS: 0293 ORIG_RAX:
004a
[25013.905990] RAX: ffda RBX: 00a0 RCX: 7fc9cb839b07
[25013.905992] RDX: RSI: 7fc9a7aeaff0 RDI: 00a0
[25013.905993] RBP: R08: R09: 72732f656d6f682f
[25013.905994] R10: R11: 0293 R12: 01f6
[25013.905995] R13: 7fc97fc5d038 R14: 7fc9a7aeb340 R15: 7fc987523380
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3
[Kernel-packages] [Bug 595047]
KDE have problem too, same copy via CLI or via Ultracopier (GUI) have no
problem.
I note too KDE have UI more slow, plasma doing CPU usage in case I use the
HDD...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/595047/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 595047]
What's the value of `vm.dirty_writeback_centisecs` ?, ie.
$ sysctl vm.dirty_writeback_centisecs
try setting it to 0 to disable it, ie.
`$ sudo sysctl -w vm.dirty_writeback_centisecs=0`
I found that this helps my network transfer not stall/stop at all(for a
few seconds when that is =1000 for example) while some kinda of non-
async `sync`(command)-like flushing is going on periodically while
transferring GiB of data files from sftp to SSD!(via Midnight Commander,
on a link limited to 10MiB per second)
vm.dirty_writeback_centisecs is how often the pdflush/flush/kdmflush
processes wake up and check to see if work needs to be done.
Coupled with the above I've been using another value:
`vm.dirty_expire_centisecs=1000`
for both cases (when stall and not stall), so this one remained fixed to =1000.
vm.dirty_expire_centisecs is how long something can be in cache before
it needs to be written. In this case it's 1 seconds. When the
pdflush/flush/kdmflush processes kick in they will check to see how old
a dirty page is, and if it's older than this value it'll be written
asynchronously to disk. Since holding a dirty page in memory is unsafe
this is also a safeguard against data loss.
Well, with the above, at least I'm not experiencing network stalls when
copying GiB of data via Midnight Commander's sftp to my SSD until some
kernel-caused sync-ing is completed in the background.
I don't know if this will work for others, but if curious about any of
my other (sysctl)settings, they should be available for perusing
[here](https://github.com/howaboutsynergy/q1q/tree/0a2cd4ba658067140d3f0ae89a0897af54da52a4/OSes/archlinux/etc/sysctl.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/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/595047/+subscriptions
--
Mailing list: https://launchpad.n
[Kernel-packages] [Bug 1801540]
Anders, looks like those two files are exactly the same? I think the Linux file didn't get uploaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
better now? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Created attachment 283579 linuxdecoded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Actually, i've tried some puppy linux before, and it was bootable without editing anything -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Created attachment 283577 winn pci data translated -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Created attachment 283581 windecoded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Created attachment 283575 linux pci data translated -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
Hello, the kuba-moo / benjarobin driver+patches worked fine until today when I migrated from Debian Stretch to Debian Buster. I could get wifi working, but not bluetooth, because the 'bpatch' try to uninstall the current linux-image and replace it by 5 others packages, which could break my system. Something appears to be changed in the way of using kernel source, but I don't know enough to understand how to manage it. Does anyone use mt7630e with Debian Buster and can help me ? Thanks a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next: Fix Released Status in HWE Next trusty series: Won't Fix Status in Linux: Unknown Status in vivid: New Status in linux package in Ubuntu: Triaged Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
** Summary changed: - Kernel 4.15.0-50 wont boot as Xen-DomU with PVH + Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829378 Title: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works). Kernel 4.15.0-48 and prior did boot without any problems as PVH. We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50. Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH- DomU. See also https://lists.xenproject.org/archives/html/xen- users/2019-05/msg00010.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834902 phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 14:09 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834891 Title: linux-gcp: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834902 phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 14:09 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833563] Re: REGRESSION: Hard lockup on boot with 4.15.0-52-generic, was working until 4.15.0-48-generic
the bug remains in 4.15.0-54 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833563 Title: REGRESSION: Hard lockup on boot with 4.15.0-52-generic, was working until 4.15.0-48-generic Status in linux package in Ubuntu: Confirmed Bug description: REGRESSION: Hard lockup on boot with 4.15.0-52-generic, was working until 4.15.0-48-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lazarus1778 F pulseaudio /dev/snd/controlC0: lazarus1778 F pulseaudio /dev/snd/controlC2: lazarus1778 F pulseaudio /dev/snd/controlC1: lazarus1778 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 20 16:23:18 2019 HibernationDevice: RESUME=UUID=51f14032-e4cc-43f0-ae93-a127efdfe596 InstallationDate: Installed on 2018-11-30 (201 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp3s0no wireless extensions. lono wireless extensions. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=fe9484a0-3a92-400c-bfc8-d30b2baec952 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
ubuntu@P8lpar4:~$ uname -a Linux P8lpar4 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:21:40 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@P8lpar4:~$ ubuntu@P8lpar4:~$ apt policy linux-image-generic linux-image-generic: Installed: 4.15.0.55.57 Candidate: 4.15.0.55.57 Version table: *** 4.15.0.55.57 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main ppc64el Packages 100 /var/lib/dpkg/status 4.15.0.54.56 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el Packages 4.15.0.20.23 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages ubuntu@P8lpar4:~$ ubuntu@P8lpar4:~$ sudo su root@P8lpar4:/home/ubuntu# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# -- dmesg -- [ 476.574556] cpu 120 (hwid 120) Ready to die... [ 476.647003] cpu 121 (hwid 121) Ready to die... [ 476.710155] cpu 122 (hwid 122) Ready to die... [ 476.766678] cpu 123 (hwid 123) Ready to die... [ 476.829791] cpu 124 (hwid 124) Ready to die... [ 476.883594] cpu 125 (hwid 125) Ready to die... [ 476.933738] cpu 126 (hwid 126) Ready to die... [ 476.986045] cpu 127 (hwid 127) Ready to die... root@P8lpar4:/home/ubuntu# ** Tags removed: verification-needed-bionic ** 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/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 T
[Kernel-packages] [Bug 1835580] Re: Disco update: 5.0.16 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => New ** Changed in: linux (Ubuntu Disco) Assignee: Connor Kuehl (connork) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835580 Title: Disco update: 5.0.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: 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 following upstream stable patches should be included in the Ubuntu kernel: 5.0.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH
Sonmething new? Do you need further information? We tried kernel linux-image-4.15.0-54 and were not able to boot as pvh (xen buld from source 4.12-staging from today). linux-image-4.15.0-48 we are able to boot as pvh. Some patches between 4.15.0-48 and 4.15.0-50 destroyed the ability to boot as pvh. ky. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829378 Title: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works). Kernel 4.15.0-48 and prior did boot without any problems as PVH. We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50. Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH- DomU. See also https://lists.xenproject.org/archives/html/xen- users/2019-05/msg00010.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 - phase: Promote to Proposed - phase-changed: Monday, 08. July 2019 07:12 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 08. July 2019 15:12 UTC reason: - promote-signing-to-proposed: Pending -- builds not complete in Signing signed:queued - promote-to-proposed: Pending -- packages copied to Signing signed:queued + promote-signing-to-proposed: Pending -- ready for review variant: debs -- 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/1835189 Title: linux-lts-trusty: 3.13.0-172.223~12.04.1 -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-signing-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Ready for Promote to Proposed phase-changed: Monday, 08. July 2019 15:12 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Packaging - phase-changed: Monday, 08. July 2019 12:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 08. July 2019 15:04 UTC reason: - prepare-package: Pending -- package tag not yet published - prepare-package-meta: Pending -- package tag not yet published - prepare-package-signed: Pending -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 15:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:12 UTC reason: - promote-to-proposed: Pending -- packages copies requested to Signing meta:missing,signed:missing + promote-signing-to-proposed: Pending -- builds not complete in Signing signed:queued + promote-to-proposed: Pending -- packages copied to Signing signed:queued variant: debs -- 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/1835189 Title: linux-lts-trusty: 3.13.0-172.223~12.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:12 UTC reason: promote-signing-to-proposed: Pending -- builds not complete in Signing signed:queued promote-to-proposed: Pending -- packages copied to Signing signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: Invalid ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Invalid => 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/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - - backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834883 Title: linux-aws: 4.18.0-1021.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:12 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- packages copies requested to Signing meta:missing,signed:missing variant: debs -- 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/1835189 Title: linux-lts-trusty: 3.13.0-172.223~12.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:12 UTC reason: promote-to-proposed: Pending -- packages copies requested to Signing meta:missing,signed:missing variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834902 - phase: Packaging - phase-changed: Wednesday, 03. July 2019 23:04 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 08. July 2019 14:09 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834891 Title: linux-gcp: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834902 phase: Holding before Promote to Proposed phase-changed: Monday, 08. July 2019 14:09 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1835189 Title: linux-lts-trusty: 3.13.0-172.223~12.04.1 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:12 UTC reason: promote-to-proposed: Pending -- packages copies requested to Signing meta:missing,signed:missing variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Changed in: ubuntu-power-systems Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Incomplete Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Bionic: New Status in makedumpfile source package in Bionic: New Status in kexec-tools source package in Cosmic: New Status in makedumpfile source package in Cosmic: New Status in kexec-tools source package in Disco: New Status in makedumpfile source package in Disco: New Status in kexec-tools source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.55
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Monday, 08. July 2019 12:35 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package: Pending -- package tag not yet published + prepare-package-meta: Pending -- package tag not yet published + prepare-package-signed: Pending -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Monday, 08. July 2019 12:35 UTC reason: prepare-package: Pending -- package tag not yet published prepare-package-meta: Pending -- package tag not yet published prepare-package-signed: Pending -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
My Dell XPS 9570 has been modified with add of an Intel card 9260 wifi/bluetooth, because the "Killer 1550 wifi / bluetooth card" that came with it does not work properly. "Killer 1550" removed for Intel 9260. https://www.killernetworking.com/products/killer-wireless-ac-1550/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Power Off => Boot on kernel 5.0.0-20 => Add the ppa:canonical-hwe-team/pc-oem-dkms Then I make : sudo apt install backport-iwlwifi-dkms Then power OFF => Power ON, Boot on kernel 5.0.0-20 => There are no changes, it does not work. ** Attachment added: "DMSEG with backport-iwlwifi-dkms" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+attachment/5275643/+files/DMSEG%20with%20backport-iwlwifi-dkms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Power Off => Boot on kernel 5.0.0-20 => command dmseg on terminal ** Attachment added: "Power Off => Boot on kernel 5.0.0-20 => command dmseg on terminal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+attachment/5275640/+files/Dmseg%20on%20Dell%20XPS%209570 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Power Off => Boot on kernel 5.0.0-20 => command dmseg on terminal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 336652]
KDE have problem too, same copy via CLI or via Ultracopier (GUI) have no problem. I note too KDE have UI more slow, plasma doing CPU usage in case I use the HDD... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/336652 Title: Poor system performance under I/O load Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: This bug seems to particularly affect the Dell Latitude D420, D430 and (from the kernel.org bug) at least the D830 laptop models; but others have been reported. Under I/O load, which need not be excessive - running usb-creator or even just checking one's email - the system performs remarkably poorly, far less than other laptop users see. It can often take minutes to open a window, and sometimes the screen isn't repainted. Certainly most applications are "dimmed" by Compiz under I/O. It also appears to massively negatively affect boot performance, with one core spending its entire time in I/O wait - something we don't see elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/336652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 336652]
Had this again 20 minutes ago. Was dopying 8.7GiB of data from one directory to another directory on the same filesystem (ext4 (rw,relatime,data=ordered)) on the same disk (Western Digital WDC WD30EZRX-00D8PB0 spinning metal disk). The KDE UI became unresponsive (Everything other than /home and user data in on a SSD), could not launch any new applications. Opening a new tab on Firefox to go to Youtube didnt load the page, and kept saying waiting for youtube.com in the status bar (network gets halted?). dmesg shows these, are they important? [25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120 seconds. [25013.905945] Tainted: P OE4.15.0-54-generic #58-Ubuntu [25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25013.905949] DOMCacheThread D0 17496 2243 0x [25013.905951] Call Trace: [25013.905954] __schedule+0x291/0x8a0 [25013.905957] schedule+0x2c/0x80 [25013.905959] jbd2_log_wait_commit+0xb0/0x120 [25013.905962] ? wait_woken+0x80/0x80 [25013.905965] __jbd2_journal_force_commit+0x61/0xb0 [25013.905967] jbd2_journal_force_commit+0x21/0x30 [25013.905970] ext4_force_commit+0x29/0x2d [25013.905972] ext4_sync_file+0x14a/0x3b0 [25013.905975] vfs_fsync_range+0x51/0xb0 [25013.905977] do_fsync+0x3d/0x70 [25013.905980] SyS_fsync+0x10/0x20 [25013.905982] do_syscall_64+0x73/0x130 [25013.905985] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [25013.905987] RIP: 0033:0x7fc9cb839b07 [25013.905988] RSP: 002b:7fc9a7aeb200 EFLAGS: 0293 ORIG_RAX: 004a [25013.905990] RAX: ffda RBX: 00a0 RCX: 7fc9cb839b07 [25013.905992] RDX: RSI: 7fc9a7aeaff0 RDI: 00a0 [25013.905993] RBP: R08: R09: 72732f656d6f682f [25013.905994] R10: R11: 0293 R12: 01f6 [25013.905995] R13: 7fc97fc5d038 R14: 7fc9a7aeb340 R15: 7fc987523380 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/336652 Title: Poor system performance under I/O load Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: This bug seems to particularly affect the Dell Latitude D420, D430 and (from the kernel.org bug) at least the D830 laptop models; but others have been reported. Under I/O load, which need not be excessive - running usb-creator or even just checking one's email - the system performs remarkably poorly, far less than other laptop users see. It can often take minutes to open a window, and sometimes the screen isn't repainted. Certainly most applications are "dimmed" by Compiz under I/O. It also appears to massively negatively affect boot performance, with one core spending its entire time in I/O wait - something we don't see elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/336652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
There is no change, I've tested it. Please let us wait for the AMD developer who can fix this. https://github.com/torvalds/linux/search?q=iommu&type=Commits -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
i think somebody needs to test this on new 5.2 kernel cuz there are some iommu stuff in git 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Ready for Packaging - phase-changed: Monday, 08. July 2019 05:44 UTC + phase: Packaging + phase-changed: Monday, 08. July 2019 12:35 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Monday, 08. July 2019 12:35 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed - phase-changed: Monday, 08. July 2019 11:02 UTC + bugs-spammed: true + phase: Ready for Testing + phase-changed: Monday, 08. July 2019 12:34 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Monday, 08. July 2019 12:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
I redid the following tests. Procedure followed completely power OFF and power ON : * 5.0.0-15-generic : wifi full work / bluetooth not work * 5.0.0-16-generic : wifi full work / bluetooth not work * 5.0.0-17-generic : wifi full work / bluetooth not work * 5.0.0-19-generic : wifi full work / bluetooth not work * 5.0.0-20-generic : wifi full work / bluetooth not work 5.2.x not tested again because crash my laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835700] Re: linux: 5.2.0-8.9 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 5.2.0-8.9 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: 5.2.0-8.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Monday, 08. July 2019 05:44 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
This failure is extremely annoying because there is no RJ-45 socket on my laptop ... as on many modern notebooks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Hello, First, I have tested Debian 10 (with out firmware packages) on my Dell XPS 9570 : https://cdimage.debian.org/debian-cd/ If I add the Intel drivers : https://www.intel.fr/content/www/fr/fr/support/articles/05511 /network-and-i-o/wireless-networking.html All run perfectly. If I test the Debian 10 Unofficial non-free images (including firmware packages) : https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including- firmware/ The driver in use seems not to be the same as the one I tested above but it also works. Test to integrate the driver : https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz And inform me so that I test it. I will try to answer your 2 messages from 04.07 & 05.07.2019 tonight when I have more time. Best regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Monday, 08. July 2019 10:03 UTC + phase: Promote to Proposed + phase-changed: Monday, 08. July 2019 11:02 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror + sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Monday, 08. July 2019 11:02 UTC reason: promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833842] Re: Kernel 4.4.0-151 fails to boot
This might be the same as https://bugs.launchpad.net/ubuntu/+source /linux-signed/+bug/1829657 (-145 works, -148 doesn't (-146 boots, but might have other problems)) -- 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/1833842 Title: Kernel 4.4.0-151 fails to boot Status in linux-signed package in Ubuntu: New Bug description: On startup, choosing Linux image 4.4.0-151 on grub makes system freeze immediately. Same behaviour with Linux image 4.4.0-150. No problem with Linux image 4.4.0-141. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-151-generic 4.4.0-151.178 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 23 11:55:00 2019 InstallationDate: Installed on 2015-05-02 (1513 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1833842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)
Update and good news: I've been reminded that the firmware I have can boot the platform with either ACPI and Device Tree tables. I've been in ACPI mode and now, after flipping to DT, the platform boots fine and all 4 interfaces (one thing I haven't noticed that only one was completely missing previously) get detected and are functional. The wget kernel.org/big.tarball works fine now as well, so I think this proves that the CONFIG_MVPP2=m was all that was needed. Thanks! ** Description changed: At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - - neither as a model or a built-in: + neither as a module or a built-in: $ uname -m aarch64 - $ grep MVPP2 /boot/config-5.0.0-20-generic + $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835054 Title: Missing NIC driver for Armada 8040 (Macchiatobin) Status in linux package in Ubuntu: Incomplete Bug description: At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a module or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed 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/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Monday, 08. July 2019 10:03 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)
Good news: The module is *definitely* built and loads fine. Thanks! Bad news: The driver has some issues... Full boot log attached, but first of all, spot the delay: ... [2.849454] mvpp2 MRVL0110:00 eth0: Using random mac address ee:ad:f4:3c:ad:cf ... [2.932894] mvpp2 MRVL0110:01 eth1: Using random mac address 16:0c:52:c7:5a:cb ... [2.946932] mvpp2 MRVL0110:01 eth2: Using random mac address 7a:b8:9a:01:af:46 ... [2.962885] mvpp2 MRVL0110:01 enamrvl110i1: renamed from eth1 ... [3.229057] mvpp2 MRVL0110:01 rename4: renamed from eth2 ... [3.504865] mvpp2 MRVL0110:00 enamrvl110i0: renamed from eth0 ... [5.334377] Virtual CRAT table created for CPU [5.334414] Parsing CRAT table with 1 nodes [5.334450] Creating topology SYSFS entries [5.334512] Topology: Add CPU node [5.334545] Finished initializing topology [ 63.937562] systemd-udevd[201]: eth2: Worker [221] processing SEQNUM=1947 is taking a long time [ 93.650969] systemd-udevd[221]: eth2: Failed to rename network interface 4 from 'eth2' to 'enamrvl110i1': File exists [ 93.892377] raid6: neonx8 gen() 3687 MB/s [ 93.940370] raid6: neonx8 xor() 3241 MB/s [ 93.988376] raid6: neonx4 gen() 3112 MB/s [ 94.036370] raid6: neonx4 xor() 2696 MB/s [ 94.084377] raid6: neonx2 gen() 2644 MB/s ... Then, the "rename4" interface gets IP over DHCP and things seems ok, until I start generating more traffic (like pulling a tarball from kernel.org)... Then the interface "hangs", ie. no more data gets in nor out, but without any messages in the kernel log. For better or worse, these symptoms more or less match what I observed using Debian Buster installer over the weekend, so I suspect it's an issue with "my" firmware (I believe others made it work on Macchiatobin). >From the "missing driver" perspective, the problem has been fixed :-) ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+attachment/5275626/+files/dmesg.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/1835054 Title: Missing NIC driver for Armada 8040 (Macchiatobin) Status in linux package in Ubuntu: Incomplete Bug description: At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for network controllers(s) in Marvell SOCs, particularly Armada 8040 - neither as a model or a built-in: $ uname -m aarch64 $ grep MVPP2 /boot/config-5.0.0-20-generic $ It makes very hard (and impossible for non-advanced users) to install and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a reasonably priced and performant server/mini-desktop platform. Could it be added, please, and the installer image re-generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828227] Re: shiftfs: allow changing ro/rw for subvolumes
** Changed in: linux (Ubuntu) Status: Expired => Fix Released ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828227 Title: shiftfs: allow changing ro/rw for subvolumes Status in linux package in Ubuntu: Fix Released Bug description: Unprivileged users can already toggle whether a subvolume will be ro or rw. Not having this working with shiftfs regresses various use-cases. Issues have already been seen by Stéphane Graber (Cced here). To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO, BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834883 Title: linux-aws: 4.18.0-1021.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Promote to Proposed - phase-changed: Monday, 08. July 2019 08:34 UTC + phase: Ready for Testing + phase-changed: Monday, 08. July 2019 10:04 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835112 Title: linux-fips: 4.15.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Testing phase-changed: Monday, 08. July 2019 10:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed - phase-changed: Monday, 08. July 2019 07:32 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 08. July 2019 10:03 UTC reason: - promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building - promote-to-proposed: Pending -- packages copied to Signing signed:building + promote-signing-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Monday, 08. July 2019 10:03 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 ** Changed in: linux-oem (Ubuntu Cosmic) Status: Invalid => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11478 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11479 ** Changed in: linux-oem (Ubuntu Disco) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#AB
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 ** Changed in: linux-oem (Ubuntu Cosmic) Status: Invalid => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11478 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11479 ** Changed in: linux-oem (Ubuntu Disco) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless
[Kernel-packages] [Bug 1832299] Re: Add new sound card PCIID into the alsa driver
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID AC
[Kernel-packages] [Bug 1832299] Re: Add new sound card PCIID into the alsa driver
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11478 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11479 ** Changed in: linux-oem (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscri
[Kernel-packages] [Bug 1833962] Re: linux-oem: 4.15.0-1045.50 -proposed tracker
This bug was fixed in the package linux-oem - 4.15.0-1045.50 --- linux-oem (4.15.0-1045.50) bionic; urgency=medium * linux-oem: 4.15.0-1045.50 -proposed tracker (LP: #1833962) [ Ubuntu: 4.15.0-54.58 ] * linux: 4.15.0-54.58 -proposed tracker (LP: #1833987) * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() -- Chia-Lin Kao (AceLan) Wed, 26 Jun 2019 17:29:41 +0800 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1833962 Title: linux-oem: 4.15.0-1045.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Ready for Security phase-changed: Friday, 05. July 2019 06:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 04. July 2019 20:41 UTC + phase: Promote to Proposed + phase-changed: Monday, 08. July 2019 08:34 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror + sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835112 Title: linux-fips: 4.15.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 08:34 UTC reason: promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed
The test will pass if you run this directly: tag=fanotify11 stime=1562574226 cmdline="fanotify11" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s fanotify11.c:66: INFO: Test #0: without FAN_REPORT_TID: tgid=2380, tid=0, event.pid=0 fanotify11.c:91: PASS: event.pid == tgid fanotify11.c:66: INFO: Test #1: with FAN_REPORT_TID: tgid=2380, tid=2381, event.pid=2380 fanotify11.c:72: CONF: FAN_REPORT_TID not supported in kernel? Summary: passed 1 failed 0 skipped 1 warnings 0 <<>> initiation_status="ok" So this timeout failure is probably caused by some failures (fanotify07 or fanotify08) before this test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808107 Title: fanotify11 in ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Timeouted on Trusty: startup='Tue Dec 11 11:58:36 2018' tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, event.pid=5447 fanotify11.c:89: PASS: event.pid == tgid Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed 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/1835112 Title: linux-fips: 4.15.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1833987 phase: Promote to Proposed phase-changed: Monday, 08. July 2019 08:34 UTC reason: promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Still weird. The only Gnome extensions active are the follwoing ones from the Ubuntu repository: gnome-shell-extension-disconnect-wifi gnome-shell-extension-top-icons-plus gnome-shell-extension-ubuntu-dock I am still facing the freezing issues, but only if my Dell XPS13 notebook goes into S3 suspend for quite some time (like more than 5 minutes). I changed that behavior to S2 instead (removed "mem_sleep_default=deep" from GRUB_CMDLINE_LINUX_DEFAULT in grub config). Now even after more than 5 minutes of hibernation there wasn't any freezing. Suspending into S2 is just for debugging exercises and currently not a permanent solution as S2 significantly drains the battery (see https://bugzilla.kernel.org/show_bug.cgi?id=199689). ** Bug watch added: Linux Kernel Bug Tracker #199689 https://bugzilla.kernel.org/show_bug.cgi?id=199689 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume fo
[Kernel-packages] [Bug 1835714] [NEW] no CDROM labels in udevadm info since 4.4.0-155.182
Public bug reported: When I upgrade a xenial server with the kernel in proposed, my CDROM are not linked anymore under /dev/disk/by-label/. My ext4 filesystems are present under /dev/disk/by-label/. Before the upgrade: uname -a Linux eolebase 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # OpenNebula provides a context CDROM to configure the VM, the LABEL is reported udevadm info /dev/sr0 P: /devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0 N: sr0 L: -100 S: cdrom S: disk/by-id/ata-QEMU_DVD-ROM_QM1 S: disk/by-label/CONTEXT S: disk/by-path/pci-:00:01.1-ata-1 S: disk/by-uuid/2019-07-08-09-47-08-00 S: dvd E: DEVLINKS=/dev/dvd /dev/disk/by-path/pci-:00:01.1-ata-1 /dev/cdrom /dev/disk/by-uuid/2019-07-08-09-47-08-00 /dev/disk/by-label/CONTEXT /dev/disk/by-id/ata-QEMU_DVD-ROM_QM1 E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0 E: DEVTYPE=disk E: ID_ATA=1 E: ID_BUS=ata E: ID_CDROM=1 E: ID_CDROM_DVD=1 E: ID_CDROM_MEDIA=1 E: ID_CDROM_MEDIA_CD=1 E: ID_CDROM_MEDIA_SESSION_COUNT=1 E: ID_CDROM_MEDIA_TRACK_COUNT=1 E: ID_CDROM_MEDIA_TRACK_COUNT_DATA=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_FOR_SEAT=block-pci-_00_01_1-ata-1 E: ID_FS_APPLICATION_ID=GENISOIMAGE\x20ISO\x209660\x2fHFS\x20FILESYSTEM\x20CREATOR\x20\x28C\x29\x201993\x20E.YOUNGDALE\x20\x28C\x29\x201997-2006\x20J.PEARSON\x2fJ.SCHILLING\x20\x28C\x29\x202006-2007\x20CDRKIT\x20TEAM E: ID_FS_LABEL=CONTEXT E: ID_FS_LABEL_ENC=CONTEXT E: ID_FS_SYSTEM_ID=LINUX E: ID_FS_TYPE=iso9660 E: ID_FS_USAGE=filesystem E: ID_FS_UUID=2019-07-08-09-47-08-00 E: ID_FS_UUID_ENC=2019-07-08-09-47-08-00 E: ID_FS_VERSION=Joliet Extension E: ID_MODEL=QEMU_DVD-ROM E: ID_MODEL_ENC=QEMU\x20DVD-ROM\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PATH=pci-:00:01.1-ata-1 E: ID_PATH_TAG=pci-_00_01_1-ata-1 E: ID_REVISION=2.5+ E: ID_SERIAL=QEMU_DVD-ROM_QM1 E: ID_SERIAL_SHORT=QM1 E: ID_TYPE=cd E: MAJOR=11 E: MINOR=0 E: SUBSYSTEM=block E: TAGS=:uaccess:systemd:seat: E: USEC_INITIALIZED=2519001 After the upgrade: uname -a Linux eolebase 4.4.0-155-generic #182-Ubuntu SMP Tue Jul 2 14:43:15 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # There is no more LABEL udevadm info /dev/sr0 P: /devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0 N: sr0 L: -100 S: cdrom S: disk/by-id/ata-QEMU_DVD-ROM_QM1 S: disk/by-path/pci-:00:01.1-ata-1 S: dvd E: DEVLINKS=/dev/disk/by-id/ata-QEMU_DVD-ROM_QM1 /dev/disk/by-path/pci-:00:01.1-ata-1 /dev/dvd /dev/cdrom E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0 E: DEVTYPE=disk E: ID_ATA=1 E: ID_BUS=ata E: ID_CDROM=1 E: ID_CDROM_DVD=1 E: ID_CDROM_MEDIA=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_FOR_SEAT=block-pci-_00_01_1-ata-1 E: ID_MODEL=QEMU_DVD-ROM E: ID_MODEL_ENC=QEMU\x20DVD-ROM\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PATH=pci-:00:01.1-ata-1 E: ID_PATH_TAG=pci-_00_01_1-ata-1 E: ID_REVISION=2.5+ E: ID_SERIAL=QEMU_DVD-ROM_QM1 E: ID_SERIAL_SHORT=QM1 E: ID_TYPE=cd E: MAJOR=11 E: MINOR=0 E: SUBSYSTEM=block E: TAGS=:uaccess:systemd:seat: E: USEC_INITIALIZED=1540484 # The LABEL is set on the filesystem blkid /dev/sr0 /dev/sr0: UUID="2019-07-08-09-47-08-00" LABEL="CONTEXT" TYPE="iso9660" lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-155-generic 4.4.0-155.182 ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181 Uname: Linux 4.4.0-155-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 8 09:57:30 2019 InstallationDate: Installed on 2018-07-02 (370 days ago) InstallationMedia: EOLE 2.6.2.1 "Xenial Xerus" - Release amd64 (20180702) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed xenial -- 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/1835714 Title: no CDROM labels in udevadm info since 4.4.0-155.182 Status in linux-signed package in Ubuntu: New Bug description: When I upgrade a xenial server with the kernel in proposed, my CDROM are not linked anymore under /dev/disk/by-label/. My ext4 filesystems are present under /dev/disk/by-label/. Before the upgrade: uname -a Linux eolebase 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # OpenNebula provides a context CDROM to configure the V
[Kernel-packages] [Bug 1828813] Re: fanotify12 in ubuntu_ltp_syscalls test failed on X
** Tags added: ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828813 Title: fanotify12 in ubuntu_ltp_syscalls test failed on X Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: tag=fanotify12 stime=1557223465 dur=350 exit=exited stat=1 core=no cu=0 cs=0 startup='Tue May 7 10:04:25 2019' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s fanotify12.c:137: INFO: Test #0: inode mark, FAN_OPEN events fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=22 fanotify12.c:239: PASS: Received event: mask=20, pid=20859, fd=23 Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775153] Re: fanotify09 in LTP syscall test failed with T/X/A kernel
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu 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/1775153 Title: fanotify09 in LTP syscall test failed with T/X/A kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Artful: Won't Fix Bug description: The "fanotify09" from the LTP syscall tests has failed on a testing node with A/T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "fanotify09" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=fanotify09 stime=1528192114 cmdline="fanotify09" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify09.c:134: PASS: group 0 get event: mask 2 pid=43803 fd=9 fanotify09.c:182: FAIL: group 1 got event fanotify09.c:182: FAIL: group 2 got event Summary: passed 1 failed 2 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: User Name 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 5 08:30 seq crw-rw 1 root audio 116, 33 Jun 5 08:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jun 5 09:14:07 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-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: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: ThunderX CRB dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Friday, 05. July 2019 20:03 UTC + phase: Promote to Proposed + phase-changed: Monday, 08. July 2019 07:32 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building + promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Monday, 08. July 2019 07:32 UTC reason: promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
Hi. Meaning touchpad and mouse wheel are broken, don't use them at all and everything is faster since reboot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: - - If you don't use mousewheel or touchpad everything will be fast and responsive. + If you don't use mousewheel or touchpad (since reboot) everything will + be fast and responsive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad (since reboot) everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
