[Kernel-packages] [Bug 1887607] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server

[Matthew Ruffell]

I installed 4.15.0-114-generic from -proposed to my test client machine,
which is a Ubuntu 18.04 Desktop VM.

I mounted two NFS shares, one with sec=sys, and the other with
sec=krb5p. I then opened each share up in separate tabs in Nautilus.

I then CUT a file from the sec=sys share, and PASTED it into the
sec=krb5p share. The file pasted to the new share correctly, and was
removed from the original share.

I repeated this several times, and each file movement was successful
with no hangs.

I then moved all files from the sec=krb5p share, back to the sec=sys
share, selected all files, then CUT and PASTED them to the sec=krb5p
share.

All files moved without the system hanging. I repeated this a number of
times, and the system functions correctly.

There is an occasional delay when pasting some files, that lasts for no
more than a few seconds, which happens when a file copy is interrupted,
but the NFS subsystem recovers, likely finding the correct slot and
sequence number, and the file moves successfully. The delay is likely
due to the NFS client needing a few round trips to the server to
discover the correct slot and sequence number.

The hang is fixed, and I am happy to mark this as verified.

** 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/1887607

Title:
  NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong
  between client and server

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1887607

  [Impact]

  There is a bug in NFS v4.1 that causes a large amount of RPC calls
  between a client and server when a previous RPC call is interrupted.
  This uses a large amount of bandwidth and can saturate the network.

  The symptoms are so:

  * On NFS clients:
  Attempts to access mounted NFS shares associated with the affected server 
block indefinitely.

  * On the network:
  A storm of repeated RPCs between NFS client and server uses a lot of 
bandwidth. Each RPC is acknowledged by the server with an 
NFS4ERR_SEQ_MISORDERED error.

  * Other NFS clients connected to the same NFS server:
  Performance drops dramatically.

  This occurs during a "false retry", when a client attempts to make a
  new RPC call using a slot+sequence number that references an older,
  cached call. This happens when a user process interrupts an RPC call
  that is in progress.

  I had previously fixed this for Disco in bug 1828978, and now a
  customer has run into the issue in Bionic. A reproducer is supplied in
  the testcase section, which was something missing from bug 1828978,
  since we never determined how the issue actually occurred back then.

  [Fix]

  This was fixed in 5.1 upstream with the below commit:

  commit 3453d5708b33efe76f40eca1c0ed60923094b971
  Author: Trond Myklebust 
  Date: Wed Jun 20 17:53:34 2018 -0400
  Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted

  The fix is to pre-emptively increment the sequence number if an RPC
  call is interrupted, and to address corner cases we interpret the
  NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an
  appropriate sequence number between the value we sent, and the last
  successfully acked SEQUENCE call.

  The commit also requires two fixup commits, which landed in 5.5 and
  5.8-rc6 respectively:

  commit 5c441544f045e679afd6c3c6d9f7aaf5fa5f37b0
  Author: Trond Myklebust 
  Date:   Wed Nov 13 08:34:00 2019 +0100
  Subject: NFSv4.x: Handle bad/dead sessions correctly in 
nfs41_sequence_process()

  commit 913fadc5b105c3619d9e8d0fe8899ff1593cc737
  Author: Anna Schumaker 
  Date:   Wed Jul 8 10:33:40 2020 -0400
  Subject: NFS: Fix interrupted slots by sending a solo SEQUENCE operation

  Commits 3453d5708b33efe76f40eca1c0ed60923094b971 and
  913fadc5b105c3619d9e8d0fe8899ff1593cc737 require small backports to
  bionic, as struct rpc_cred changed to const struct cred in 5.0, and
  the backports swap them back to struct rpc_cred since that is how 4.15
  works.

  [Testcase]

  You will need four machines. The first, is a kerberos KDC. Set up
  Kerberos correctly and create new service principals for the NFS
  server and for the client. I used: nfs/nfskerb.mydomain.com and
  nfs/client.mydomain.com.

  The second machine will be a NFS server with the krb5p share. Add the nfs 
server kerberos keys to the system's keytab, and set up a NFS server that 
exports a directory with sec=krb5p. Example export:
  /mnt/secretfolder *.mydomain.com(rw,sync,no_subtree_check,sec=krb5p)

  The third machine is a regular NFS server. Export a directory with normal 
sec=sys security. Example export:
  /mnt/sharedfolder *.mydomain.com(rw,sync)

  The fourth is a desktop machine. Add the client kerberos keys to the system's 
keytab. 

[Kernel-packages] [Bug 1883905] Re: Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL

[IRFAN]

** Description changed:

  Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and
  Ubuntu 20.04. Touchpad works on Windows.
  
  The touchpad does not show up in xinput --list and in the devices
  (included in the attachment). Its manufacturer is Elantech, at least I
  suppose it is, based on an output from acpidump which has shown:
  
  27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48  TY.p.ELAN0633._H
  
  on one line. If it is in fact my touchpad and its ID is 0633, then it is
  not included in elan_i2c_core.c file in my ubuntu kernel source (IDs end
  at 0632). I tried to modify it myself and compile a new, custom kernel,
  but I am quite new to linux so I failed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  maciek 3356 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  maciek 3356 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 14:50:45 2020
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
-  Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless 
Mouse
-  Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
+  Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless 
Mouse
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81W8
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=9baf434c-2f39-433d-b9ec-ed69c897ef46 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-37-generic N/A
-  linux-backports-modules-5.4.0-37-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-37-generic N/A
+  linux-backports-modules-5.4.0-37-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
  dmi.product.family: IdeaPad S145-15IIL
  dmi.product.name: 81W8
  dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
  dmi.product.version: Lenovo IdeaPad S145-15IIL
  dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883905

Title:
  Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and
  Ubuntu 20.04. Touchpad works on Windows.

  The touchpad does not show up in xinput --list and in the devices
  (included in the attachment). Its manufacturer is Elantech, at least I
  suppose it is, based on an output from acpidump which has shown:

  27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48
  TY.p.ELAN0633._H

  on one line. If it is in fact my touchpad and its ID is 0633, then it
  is not included in elan_i2c_core.c file in my ubuntu kernel source
  (IDs end at 0632). I tried to modify it myself and compile a new,
  custom kernel, but I am quite new to linux so I failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maciek 3356 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 14:50:45 2020
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - 

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Anthony Wong]

** Tags added: originate-from-1887127 originate-from-1887878 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1848680] Re: hugetlb tests in ubuntu_ltp failed on B-KVM

[Po-Hsu Lin]

In this cycle with 4.15.0-1072.73 KVM kernel
Only hugemmap05 hugemmap05_1 failed on node larry

 startup='Thu Aug 13 17:51:03 2020'
 tst_hugepage.c:56: CONF: nr_hugepages = 2, but expect 128. Not enough 
hugepages for testing.
 tag=hugemmap01 stime=1597341063 dur=0 exit=exited stat=32 core=no cu=0 cs=3
 startup='Thu Aug 13 17:51:03 2020'
 tst_hugepage.c:56: CONF: nr_hugepages = 2, but expect 128. Not enough 
hugepages for testing.
 tag=hugemmap02 stime=1597341063 dur=0 exit=exited stat=32 core=no cu=0 cs=1
 startup='Thu Aug 13 17:51:03 2020'
 tst_hugepage.c:56: CONF: nr_hugepages = 2, but expect 128. Not enough 
hugepages for testing.
 tag=hugemmap04 stime=1597341063 dur=0 exit=exited stat=32 core=no cu=0 cs=1
 startup='Thu Aug 13 17:51:04 2020'
 tst_hugepage.c:58: INFO: 2 hugepage(s) reserved
 tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
 hugemmap05.c:235: INFO: original nr_overcommit_hugepages is 0
 hugemmap05.c:90: BROK: mmap((nil),6291456,3,1,21,0) failed: ENOMEM (12)
 hugemmap05.c:185: INFO: restore nr_overcommit_hugepages to 0.

 Summary:
 passed 0
 failed 0
 skipped 0
 warnings 0
 tag=hugemmap05 stime=1597341064 dur=0 exit=exited stat=2 core=no cu=0 cs=1
 startup='Thu Aug 13 17:51:04 2020'
 tst_hugepage.c:56: CONF: nr_hugepages = 2, but expect 255. Not enough 
hugepages for testing.
 tag=hugemmap06 stime=1597341064 dur=0 exit=exited stat=32 core=no cu=0 cs=1
 startup='Thu Aug 13 17:51:04 2020'
 tst_hugepage.c:58: INFO: 2 hugepage(s) reserved
 tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
 hugemmap05.c:235: INFO: original nr_overcommit_hugepages is 0
 tst_safe_sysv_ipc.c:99: BROK: hugemmap05.c:86: shmget(218366131, 6291456, b80) 
failed: ENOMEM (12)
 hugemmap05.c:185: INFO: restore nr_overcommit_hugepages to 0.

 Summary:
 passed 0
 failed 0
 skipped 0
 warnings 0
 tag=hugemmap05_1 stime=1597341064 dur=0 exit=exited stat=2 core=no cu=0 cs=1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1848680

Title:
  hugetlb tests in ubuntu_ltp failed on B-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Bionic:
  New

Bug description:
  Failed test cases : hugemmap01 hugemmap02 hugemmap04 hugemmap05
  hugemmap05_1 hugemmap05_2 hugemmap05_3 hugemmap06 hugeshmat01
  hugeshmat02 hugeshmat03 hugeshmat04 hugeshmat05 hugeshmctl01
  hugeshmctl02 hugeshmctl03 hugeshmdt01 hugeshmget01 hugeshmget02
  hugeshmget03 hugeshmget05

  However, if you run this test suite directly, all these test will pass.
  So I think this is caused by some other failures before the hugetlbfs test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1047-kvm 4.15.0-1047.47
  ProcVersionSignature: User Name 4.15.0-1047.47-kvm 4.15.18
  Uname: Linux 4.15.0-1047-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 18 08:30:08 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848680/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892074] Re: Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps disconnecting

[You-Sheng Yang]

Seem to share same symptom with bug 1850089, but bug 1850089 is caused
by a platform customized 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/1892074

Title:
  Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps
  disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2) $ apt-cache policy linux-image-5.4.0-42-generic
  linux-image-5.4.0-42-generic:
Installed: 5.4.0-42.46
Candidate: 5.4.0-42.46
Version table:
   *** 5.4.0-42.46 500
  500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) No WiFi disconnects
  4) WiFi disconnects (other clients don't have any issues)

  The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
  dual-band (4 channels), WPA2-PSK.

  I see reglular WiFi disconnects since a few days now, possibly related
  to a kernel and/or firmware upgrade.

  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
  looks similar, but I have different Intel hardware:

  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
  160MHz Wireless Network Adapter (201NGW) (rev 30)

  [87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
  [87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
  [87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
  [87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
  [87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
  [87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
  [87471.950902] iwlwifi :00:14.3: 0x1000 | data2
  [87471.950903] iwlwifi :00:14.3: 0xF008 | data3
  [87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
  [87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
  [87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
  [87471.950910] iwlwifi :00:14.3: 0x | time gp1
  [87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
  [87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
  [87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
  [87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
  [87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
  [87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
  [87471.950926] iwlwifi :00:14.3: 0x | isr1
  [87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
  [87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
  [87471.950931] iwlwifi :00:14.3: 0x | isr4
  [87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
  [87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
  [87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
  [87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
  [87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
  [87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
  [87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
  [87471.950944] iwlwifi :00:14.3: 0x | timestamp
  [87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
  [87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
  [87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
  [87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
  [87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
  [87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
  [87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  [87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
  [87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
  [87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
  [87471.951008] iwlwifi :00:14.3: 0x00AA0108 | last host cmd
  [87471.951010] iwlwifi :00:14.3: 0x | isr status reg
  [87471.951025] 

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[You-Sheng Yang]

DKMS package named oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-
e33ba6d-core43-10. This should have been replaced with backport-iwlwifi-
dkms in Bionic. Is it possible for you to uninstall that oem-wifi-intel-
iwlwifi-lp1810708-* and install backport-iwlwifi-dkms instead?

** No longer affects: linux-signed-oem (Ubuntu)

** Also affects: backport-iwlwifi-dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: backport-iwlwifi-dkms (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1850089

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

[Kernel-packages] [Bug 1850089] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1850089

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1850089

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[You-Sheng Yang]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1850089

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]  worker_thread+0x32/0x410
  [   59.582719]  kthread+0x121/0x140
  [   59.582722]  ? process_one_work+0x420/0x420
  [   59.582726] 

[Kernel-packages] [Bug 1864603] Re: System freezes for 20 seconds while resuming from s2idle (performance mode)

[AceLan Kao]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Invalid

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864603

Title:
  System freezes for 20 seconds while resuming from s2idle (performance
  mode)

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Invalid
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Invalid

Bug description:
  [Impact]
  Realtek cardreader sometimes blocks the resume process. It stuck at blank 
screen around 20 seconds while resuming from s2idle.

  [Fix]

  [Test]

  [Regression Potential]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864603/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892074] Re: WiFi keeps disconnecting

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

** Summary changed:

- WiFi keeps disconnecting
+ Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps 
disconnecting

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892074

Title:
  Intel Killer AX1650i [8086:34f0] Subsystem [1a56:1651] WiFi keeps
  disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2) $ apt-cache policy linux-image-5.4.0-42-generic
  linux-image-5.4.0-42-generic:
Installed: 5.4.0-42.46
Candidate: 5.4.0-42.46
Version table:
   *** 5.4.0-42.46 500
  500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) No WiFi disconnects
  4) WiFi disconnects (other clients don't have any issues)

  The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
  dual-band (4 channels), WPA2-PSK.

  I see reglular WiFi disconnects since a few days now, possibly related
  to a kernel and/or firmware upgrade.

  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
  looks similar, but I have different Intel hardware:

  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
  160MHz Wireless Network Adapter (201NGW) (rev 30)

  [87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
  [87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
  [87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
  [87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
  [87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
  [87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
  [87471.950902] iwlwifi :00:14.3: 0x1000 | data2
  [87471.950903] iwlwifi :00:14.3: 0xF008 | data3
  [87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
  [87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
  [87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
  [87471.950910] iwlwifi :00:14.3: 0x | time gp1
  [87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
  [87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
  [87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
  [87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
  [87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
  [87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
  [87471.950926] iwlwifi :00:14.3: 0x | isr1
  [87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
  [87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
  [87471.950931] iwlwifi :00:14.3: 0x | isr4
  [87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
  [87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
  [87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
  [87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
  [87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
  [87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
  [87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
  [87471.950944] iwlwifi :00:14.3: 0x | timestamp
  [87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
  [87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
  [87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
  [87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
  [87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
  [87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
  [87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  [87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
  [87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
  [87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
  [87471.951008] iwlwifi :00:14.3: 0x00AA0108 | last host cmd
  [87471.951010] iwlwifi 

[Kernel-packages] [Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch

[Taihsiang Ho]

uh it's already incomplete. This is a fair status. Let's keep it as is.

** Changed in: subiquity
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890884

Title:
  kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
  arm64 arch

Status in subiquity:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso
  kernel: 4.15.0-112-generic #113-Ubuntu
  platform: Hisilicon D06 arm64 arch

  [Reproducing Steps]
  1. setup pxe boot by following 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
  2. pxe boot the machine with the image

  [Expected Result]
  Boot to subiquity

  [Actual Result]
  Kernel trace happened during booting process. Reproducing rate: 2 out of 2.

  [8.375118] md: ... autorun DONE.
  [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): 
error -6
  [8.385955] Please append a correct "root=" boot option; here are the 
available partitions:
  [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic 
#113-Ubuntu
  [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - 
V1.20.01 04/26/2019
  [8.418879] Call trace:
  [8.421316]  dump_backtrace+0x0/0x198
  [8.424965]  show_stack+0x24/0x30
  [8.428269]  dump_stack+0x98/0xbc
  [8.431572]  panic+0x128/0x2a4
  [8.434615]  mount_block_root+0x210/0x2e8
  [8.438610]  mount_root+0x7c/0x8c
  [8.441912]  prepare_namespace+0x144/0x1dc
  [8.445995]  kernel_init_freeable+0x218/0x23c
  [8.450341]  kernel_init+0x18/0x110
  [8.453817]  ret_from_fork+0x10/0x18
  [8.457486] SMP: stopping secondary CPUs
  [8.461836] Kernel Offset: disabled
  [8.465312] CPU features: 0x03200a38
  [8.468873] Memory Limit: none
  [8.473291] Unable to handle kernel paging request at virtual address 
09865034
  [8.481192] Mem abort info:
  [8.483972]   ESR = 0x9661
  [8.487013]   Exception class = DABT (current EL), IL = 32 bits
  [8.492918]   SET = 0, FnV = 0
  [8.495958]   EA = 0, S1PTW = 0
  [8.499086] Data abort info:
  [8.501953]   ISV = 0, ISS = 0x0061
  [8.505774]   CM = 0, WnR = 1
  [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval)
  [8.515502] [09865034] *pgd=0a5fe003, 
*pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703
  [8.526445] Internal error: Oops: 9661 [#1] SMP
  [8.531310] Modules linked in:
  [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
  [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic 
#113-Ubuntu
  [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - 
V1.20.01 04/26/2019
  [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO)
  [8.562144] pc : acpi_os_write_memory+0xac/0x158
  [8.566749] lr : apei_write+0xb0/0xc0
  [8.570397] sp : 09afb900
  [8.573698] x29: 09afb900 x28: fffe
  [8.578996] x27:  x26: ffa5
  [8.584294] x25: ffbe x24: 0080
  [8.589592] x23: 0005 x22: 0008
  [8.594890] x21: 0040 x20: 0010
  [8.600188] x19: 94110034 x18: 0003
  [8.605486] x17:  x16: 0009
  [8.610784] x15: 001f x14: 8205169d4225fc6e
  [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca
  [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562
  [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5
  [8.631976] x7 : 0001 x6 : 94110034
  [8.637274] x5 : 9411003c x4 : 09639fb8
  [8.642571] x3 :  x2 : 0034
  [8.647869] x1 : 0010 x0 : 09865034
  [8.653167] Call trace:
  [8.655601]  acpi_os_write_memory+0xac/0x158
  [8.659858]  apei_write+0xb0/0xc0
  [8.663160]  __apei_exec_write_register+0x88/0xb0
  [8.667851]  apei_exec_write_register_value+0x2c/0x38
  [8.672888]  __apei_exec_run+0xac/0x108
  [8.676711]  erst_write+0x154/0x268
  [8.680186]  erst_writer+0x26c/0x3b0
  [8.683751]  pstore_dump+0x1b4/0x330
  [8.687313]  kmsg_dump+0xd0/0x100
  [8.690615]  panic+0x164/0x2a4
  [8.693656]  mount_block_root+0x210/0x2e8
  [8.697652]  mount_root+0x7c/0x8c
  [8.700953]  prepare_namespace+0x144/0x1dc
  [8.705035]  kernel_init_freeable+0x218/0x23c
  [8.709380]  kernel_init+0x18/0x110
  [8.712855]  ret_from_fork+0x10/0x18
  [8.716418] Code: 54000380 710102bf 54000561 d5033e9f (f914)
  [

[Kernel-packages] [Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch

[Taihsiang Ho]

@mwhudson Thanks for the hint. I think I did make some mistakes when
setting up the grub parameters for pxe[1] because @dann seemed to
perform a similar test without the same issue in these bug
reports[2][3].

Let me set the status to be invalid until the pxe config is confirmed to
be right.


[1] The grub.cfg snippet I used to reproduce this issue

menuentry "Install Ubuntu Server (18.04.5 subiquity live 20200806.1) (Pull the 
iso from lab apache)" {
set gfxpayload=keep
linux   /casper/vmlinuz 
url=http://10.228.68.91/bionic-live-server-arm64.iso only-ubiquity ip=dhcp ---
initrd  /casper/initrd
}


[2] https://bugs.launchpad.net/subiquity/+bug/1891060
[3] https://bugs.launchpad.net/subiquity/+bug/1891059

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890884

Title:
  kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06
  arm64 arch

Status in subiquity:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso
  kernel: 4.15.0-112-generic #113-Ubuntu
  platform: Hisilicon D06 arm64 arch

  [Reproducing Steps]
  1. setup pxe boot by following 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
  2. pxe boot the machine with the image

  [Expected Result]
  Boot to subiquity

  [Actual Result]
  Kernel trace happened during booting process. Reproducing rate: 2 out of 2.

  [8.375118] md: ... autorun DONE.
  [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): 
error -6
  [8.385955] Please append a correct "root=" boot option; here are the 
available partitions:
  [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic 
#113-Ubuntu
  [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - 
V1.20.01 04/26/2019
  [8.418879] Call trace:
  [8.421316]  dump_backtrace+0x0/0x198
  [8.424965]  show_stack+0x24/0x30
  [8.428269]  dump_stack+0x98/0xbc
  [8.431572]  panic+0x128/0x2a4
  [8.434615]  mount_block_root+0x210/0x2e8
  [8.438610]  mount_root+0x7c/0x8c
  [8.441912]  prepare_namespace+0x144/0x1dc
  [8.445995]  kernel_init_freeable+0x218/0x23c
  [8.450341]  kernel_init+0x18/0x110
  [8.453817]  ret_from_fork+0x10/0x18
  [8.457486] SMP: stopping secondary CPUs
  [8.461836] Kernel Offset: disabled
  [8.465312] CPU features: 0x03200a38
  [8.468873] Memory Limit: none
  [8.473291] Unable to handle kernel paging request at virtual address 
09865034
  [8.481192] Mem abort info:
  [8.483972]   ESR = 0x9661
  [8.487013]   Exception class = DABT (current EL), IL = 32 bits
  [8.492918]   SET = 0, FnV = 0
  [8.495958]   EA = 0, S1PTW = 0
  [8.499086] Data abort info:
  [8.501953]   ISV = 0, ISS = 0x0061
  [8.505774]   CM = 0, WnR = 1
  [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval)
  [8.515502] [09865034] *pgd=0a5fe003, 
*pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703
  [8.526445] Internal error: Oops: 9661 [#1] SMP
  [8.531310] Modules linked in:
  [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
  [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic 
#113-Ubuntu
  [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - 
V1.20.01 04/26/2019
  [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO)
  [8.562144] pc : acpi_os_write_memory+0xac/0x158
  [8.566749] lr : apei_write+0xb0/0xc0
  [8.570397] sp : 09afb900
  [8.573698] x29: 09afb900 x28: fffe
  [8.578996] x27:  x26: ffa5
  [8.584294] x25: ffbe x24: 0080
  [8.589592] x23: 0005 x22: 0008
  [8.594890] x21: 0040 x20: 0010
  [8.600188] x19: 94110034 x18: 0003
  [8.605486] x17:  x16: 0009
  [8.610784] x15: 001f x14: 8205169d4225fc6e
  [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca
  [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562
  [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5
  [8.631976] x7 : 0001 x6 : 94110034
  [8.637274] x5 : 9411003c x4 : 09639fb8
  [8.642571] x3 :  x2 : 0034
  [8.647869] x1 : 0010 x0 : 09865034
  [8.653167] Call trace:
  [8.655601]  acpi_os_write_memory+0xac/0x158
  [8.659858]  apei_write+0xb0/0xc0
  [8.663160]  __apei_exec_write_register+0x88/0xb0
  [8.667851]  

[Kernel-packages] [Bug 1890867] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch

[Taihsiang Ho]

Similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890884/comments/6
let me re-visit my pxe configuration and set the status as "incomplete".

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: subiquity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890867

Title:
  kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05
  arm64 arch

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Incomplete

Bug description:
  image: 18.04.5 daily image (20200806.1)  bionic-live-server-arm64.iso
  kernel: 4.15.0-112-generic #113-Ubuntu
  platform: Hisilicon D05 arm64 arch

  [Reproducing Steps]
  1. setup pxe boot by following
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
  2. pxe boot the machine with the image

  [Expected Result]
  Boot to subiquity

  [Actual Result]
  Kernel trace happened during booting process. Reproducing rate: 2 out of 2.

  
  [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic 
#113-Ubuntu
  [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018
  [6.657871] Call trace:
  [6.660308]  dump_backtrace+0x0/0x198
  [6.663957]  show_stack+0x24/0x30
  [6.667261]  dump_stack+0x98/0xbc
  [6.670563]  panic+0x128/0x2a4
  [6.673606]  mount_block_root+0x210/0x2e8
  [6.677603]  mount_root+0x7c/0x8c
  [6.680904]  prepare_namespace+0x144/0x1dc
  [6.684987]  kernel_init_freeable+0x218/0x23c
  [6.689331]  kernel_init+0x18/0x110
  [6.692806]  ret_from_fork+0x10/0x18
  [6.696428] SMP: stopping secondary CPUs
  [6.700345] Kernel Offset: disabled
  [6.703821] CPU features: 0x2008
  [6.707382] Memory Limit: none
  [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891449] Re: Enable PCI ACS for platform opt to get the usb flash drive from WD19TB

[koba]

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1891449

Title:
  Enable PCI ACS for platform opt to get the usb flash drive from WD19TB

Status in HWE Next:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Connect with the WD19TB on the right TB port and plug the USB flash drive on 
it, the machine can't recognize the USB flash drive.

  [Fix]
  Enable the PCI ACS when Intel IOMMU is detected with platform opt in hint.

  [test]
  With the fix, the machine can recognize the USB flash drive.

  [Regression Potential]
  Low. the patch has landed on the mainline kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891449/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[You-Sheng Yang]

** Tags added: hwe-bluetooth

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891648

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891648/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892107] Re: NETWORK IS BEAKING THE OS

[Daniel van Vugt]

We can keep this bug about your networking (wifi?) problems.

Although looking at your kernel log there appears to be a separate
issue: Your 'SanDisk SSD PLUS 120GB' is experiencing hardware faults
which may indeed break the OS. That problem is not related to
networking. I suggest you try replacing the 'SanDisk SSD PLUS 120GB' or
just unplug it if you don't need it. Hopefully the problem is just that
drive and not the motherboard. But again, your disk problem is separate
and unrelated to wifi problems.

** Package changed: xorg (Ubuntu) => bcmwl (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1892107

Title:
  NETWORK IS BEAKING THE OS

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
  and this error always occurs.

  I'm doing something, the system simply informs that there is no
  internet, and it really runs out of internet and if I try to connect
  in my hand, it simply locks the entire system, leaving the fan
  running.

  I use Ubuntu, as my computer is a Macbook pro 2012 and will no longer
  receive a system update.

  Macbook pro 13" i7 mid 2012 original network card.

  
  From what I noticed, it looks like a loop is occurring, but I couldn't get 
any more details due to the crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 18 20:37:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-07-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Apple Inc. MacBookPro9,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b1280c6f-f86c-494d-b8f0-1ceed5d31914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 233.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2020-08-18T20:29:26.081990
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1892107/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892094] Re: Nvidia Desktop Brightness Reset on Blank Screen

[Daniel van Vugt]

I doubt GNOME has any intention to support this use case, but in case
I'm wrong please:

1. Verify the bug still happens in Ubuntu 20.04 and

2. Report the bug upstream at:
https://gitlab.gnome.org/GNOME/mutter/issues

** Tags added: bionic

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Nvidia Desktop Brightness Reset on Blank Screen
+ Xrandr brightness and gamma settings not remembered on power resume

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: New => Incomplete

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1892094

Title:
  Xrandr brightness and gamma settings not remembered on power resume

Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Incomplete

Bug description:
  Brightness Reset to Maximum on Nvidia GPU Desktop when setting on
  Blank Screen

  The Desktop LED Monitor brightness or Gamma level is not preserved and
  reset when I set gnome-control-center setting on Power to Blank
  Screen.

  I try to post as much details as possible.

  -I did a test by setting Nvidia X Server Color Correction and set any
  brightness and gamma.It get reset when Power Saving Blank Screen time
  active which I had set 10 minutes to save power by auto turning off
  the display.

  -The second test was by installing a Brightness Controller which use
  Xrandr but same result of getting reset when I set Blank Screen.I also
  manually set xrandr --output DVI-D-0 –brightness 0.5 --gamma
  0.5:0.5:0.5 an value get reset after the trigger from blank screen.

  -Third test by selecting Nouveau open source but same result of
  getting reset when I set Blank Screen.

  -Forth test ,  manually turn off the monitor ‘xset dpms force off’ it
  doesn’t trigger the brightness reset.

  Since the system is using Desktop GPU , the folder on xblacklight is
  empty without config files.

  The flow 
  > Set brightness >  Power Saving Blank Screen time active > Brightness reset 
> External Monitor dim and Turn Off > Press any keyboard button to wakeup the 
display > Brightness Stay at reset value of Full 100% brightness.

  The details I had tested , I suspect gsd-power may have related to this 
issue.This is happen before which I had find a solution to other brightness 
reset happen when every restart , delete a files upon restart , open a web 
browser with and play a video stream, login and logout , suspend and Power 
Saving Blank Screen.
  All of this are affected by gsd-color.Which I had found a link a fix 
suggestion
  https://github.com/LordAmit/Brightness/issues/102#issuecomment-374253884 by 
disable  /usr/lib/gnome-settings-daemon/gsd-color on startup.

  The only left is Power Saving Blank Screen still get reset when it get 
active.I am not too sure whether it is related to gsd-power , I did disable it 
but it also disable Power Saving Blank Screen together.
  It just goes to screensaver mode and did not turn off the monitor.

  I do not have any basic on gsd-power code
  https://gitlab.gnome.org/starnight/gnome-settings-
  daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power
  /gsd-power-manager.c Not knowing which line did it callback and get
  reset , presumably ‘GSD_POWER_IDLE_MODE_BLANK’ ?

  Fresh Install

  OS : Ubuntu 18.04.4
  Architecture: amd64 
  Nvidia : GTX 1050
  Driver : NVIDIA Driver Version: 440.100
  uname : 5.4.0-42-generic
  DisplayManager: gdm3

  Journalctl log when blank screen active.

  nvidia-settings[19556]: PRIME: is it supported? no
  nvidia-settings[19556]: PRIME: No offloading required. Abort
  nvidia-settings[19556]: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
  Check that logind is properly installed and pam_systemd is getting used at 
login.
  gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
  gnome-screensav[1551]: Source ID 19140 was not found when attempting to 
remove it
  gnome-session-binary[1521]: WARNING: Could not get session path for session. 
Check that logind is properly installed and pam_systemd is getting used at 
login.
  gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.

  Reading the log shows somewhere it trigger brightness reset.The Nvidia
  Setting prime message is show because I am using a desktop dedicated
  GPU without using 

[Kernel-packages] [Bug 1892107] [NEW] NETWORK IS BEAKING THE OS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
and this error always occurs.

I'm doing something, the system simply informs that there is no
internet, and it really runs out of internet and if I try to connect in
my hand, it simply locks the entire system, leaving the fan running.

I use Ubuntu, as my computer is a Macbook pro 2012 and will no longer
receive a system update.

Macbook pro 13" i7 mid 2012 original network card.


>From what I noticed, it looks like a loop is occurring, but I couldn't get any 
>more details due to the crash.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 18 20:37:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
InstallationDate: Installed on 2020-07-16 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Apple Inc. MacBookPro9,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b1280c6f-f86c-494d-b8f0-1ceed5d31914 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 233.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.apport.crashdb.conf: 2020-08-18T20:29:26.081990
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: bcmwl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu
-- 
NETWORK IS BEAKING THE OS
https://bugs.launchpad.net/bugs/1892107
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bcmwl in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891648] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1891648

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891648

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891648/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Daniel van Vugt]

Those are different profiles "ldac" and "sbc", so are actually different
bugs to this. I suggest logging those as new bugs after 5.8.0 becomes
the standard kernel in groovy (soon). If they are bugs at all (ie. you
are sure your headphones support LDAC and SBC).


** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

** No longer affects: bluez (Ubuntu)

** Tags added: a2dp

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1891648

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891648/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1874588] Re: Flickering screen after waking up from Suspend

[Daniel van Vugt]

Ian, and everyone other than Pavel,

Please open your own bugs by running:

  ubuntu-bug linux

so that we can investigate and track the status of your individual
issues.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874588

Title:
  Flickering screen after waking up from Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just did a fresh install of Ubuntu 20.04 LTS and everything was fine,
  display worked perfect. Then I put the machine in Suspend mode (by
  clicking on GUI button), left for 5 minutes, came back, woke up the
  machine (by clicking a key on the keyboard), and upon waking up, the
  display started flickering heavily.

  Relevant Specs (Sorry if I missed anything):

  AMD® Ryzen 9 3900x 12-core processor × 24
  AMD® Radeon rx 5700 xt
  GNOME version 3.36.1
  Windowing System X11
  I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors 
with resolution 1920x1080, all at 60Hz

  Most of the flickering is happening on Samsung, although once in a
  while, other monitors flicker a little bit as well.

  Things to note: When I switch Samsung to lower resolution, the
  flickering goes away. When I come back to 3840x2160, it comes back.
  When I switch to lower resolution, suspend and come back, everything
  is fine.

  If I reboot the machine, the display is fine until I suspend and wake
  up again (if I am in higher resolution).

  I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the
  only two available when I turn off FreeSync), and the issue still
  persists. Turning FreeSync on and off does nothing.

  Thank you,

  Pavel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pavel  1870 F pulseaudio
   /dev/snd/controlC0:  pavel  1870 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 21:14:00 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[daleli]

This bug affects me a lot. I visit this page everyday to see whether if
someone fix it. :(

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 

[Kernel-packages] [Bug 1874588] Re: Flickering screen after waking up from Suspend

[Ian Cameron]

Update: After much testing, the only thing I discovered would fix the
issues (including error messages on startup) was to downgrade the kernel
to 5.3.X. Upgrading wouldn't solve it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874588

Title:
  Flickering screen after waking up from Suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just did a fresh install of Ubuntu 20.04 LTS and everything was fine,
  display worked perfect. Then I put the machine in Suspend mode (by
  clicking on GUI button), left for 5 minutes, came back, woke up the
  machine (by clicking a key on the keyboard), and upon waking up, the
  display started flickering heavily.

  Relevant Specs (Sorry if I missed anything):

  AMD® Ryzen 9 3900x 12-core processor × 24
  AMD® Radeon rx 5700 xt
  GNOME version 3.36.1
  Windowing System X11
  I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors 
with resolution 1920x1080, all at 60Hz

  Most of the flickering is happening on Samsung, although once in a
  while, other monitors flicker a little bit as well.

  Things to note: When I switch Samsung to lower resolution, the
  flickering goes away. When I come back to 3840x2160, it comes back.
  When I switch to lower resolution, suspend and come back, everything
  is fine.

  If I reboot the machine, the display is fine until I suspend and wake
  up again (if I am in higher resolution).

  I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the
  only two available when I turn off FreeSync), and the issue still
  persists. Turning FreeSync on and off does nothing.

  Thank you,

  Pavel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pavel  1870 F pulseaudio
   /dev/snd/controlC0:  pavel  1870 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 21:14:00 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892091] Re: Bionic update: upstream stable patchset 2020-08-18

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- 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:
  
- 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 2020-08-18
  
-upstream stable patchset 2020-08-18
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+v4.19.139
+ 
+    from git://git.kernel.org/
+ 
+ USB: serial: qcserial: add EM7305 QDL product ID
+ USB: iowarrior: fix up report size handling for some devices
+ usb: xhci: define IDs for various ASMedia host controllers
+ usb: xhci: Fix ASMedia ASM1142 DMA addressing
+ Revert "ALSA: hda: call runtime_allow() for all hda controllers"
+ ALSA: seq: oss: Serialize ioctls
+ staging: android: ashmem: Fix lockdep warning for write operation
+ Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
+ Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
+ Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
+ omapfb: dss: Fix max fclk divider for omap36xx
+ binder: Prevent context manager from incrementing ref 0
+ vgacon: Fix for missing check in scrollback handling
+ mtd: properly check all write ioctls for permissions
+ leds: wm831x-status: fix use-after-free on unbind
+ leds: da903x: fix use-after-free on unbind
+ leds: lm3533: fix use-after-free on unbind
+ leds: 88pm860x: fix use-after-free on unbind
+ net/9p: validate fds in p9_fd_open
+ drm/nouveau/fbcon: fix module unload when fbcon init has failed for some 
reason
+ drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
+ i2c: slave: improve sanity check when registering
+ i2c: slave: add sanity check when unregistering
+ usb: hso: check for return value in hso_serial_common_create()
+ firmware: Fix a reference count leak.
+ cfg80211: check vendor command doit pointer before use
+ igb: reinit_locked() should be called with rtnl_lock
+ atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
+ tools lib traceevent: Fix memory leak in process_dynamic_array_len
+ Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
+ xattr: break delegations in {set,remove}xattr
+ ipv4: Silence suspicious RCU usage warning
+ ipv6: fix memory leaks on IPV6_ADDRFORM path
+ net: ethernet: mtk_eth_soc: fix MTU warnings
+ vxlan: Ensure FDB dump is performed under RCU
+ net: lan78xx: replace bogus endpoint lookup
+ hv_netvsc: do not use VF device if link is down
+ net: gre: recompute gre csum for sctp over gre tunnels
+ openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
+ Revert "vxlan: fix tos value before xmit"
+ selftests/net: relax cpu affinity requirement in msg_zerocopy test
+ rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
+ i40e: add num_vectors checker in iwarp handler
+ i40e: Wrong truncation from u16 to u8
+ i40e: Memory leak in i40e_config_iwarp_qvlist
+ Smack: fix use-after-free in smk_write_relabel_self()
+ UBUNTU: upstream stable to v4.19.139

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892091

Title:
  Bionic update: upstream stable patchset 2020-08-18

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress

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 2020-08-18

  Ported from the following upstream stable releases:
 v4.19.139

     from git://git.kernel.org/

  USB: serial: qcserial: add EM7305 QDL product ID
  USB: iowarrior: fix up report size handling for some devices
  usb: xhci: define IDs for various ASMedia host 

[Kernel-packages] [Bug 1892091] [NEW] Bionic update: upstream stable patchset 2020-08-18

[Kamal Mostafa]

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 2020-08-18
   from git://git.kernel.org/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892091

Title:
  Bionic update: upstream stable patchset 2020-08-18

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress

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 2020-08-18
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892091/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Kyrylo Bohdanenko]

One more update. Using mainline kernel v5.8.1 from here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/

There is a definite improvement in connectivity. However, the originally
reported issue is still there, and I am getting these in my
/var/log/syslog (w/ custom pulseaudio-module-bluetooth):

sie 18 21:43:01 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_ldac: Not connected
sie 18 21:43:13 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_sbc: Not connected
sie 18 21:43:16 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_ldac: Not connected

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1891648

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1891648/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Kyrylo Bohdanenko]

Found this bug report on kernel's bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=204765

There are bluetooth-related entries from journalctl -x:

sie 18 21:14:25 k-laptop bluetoothd[11444]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
sie 18 21:14:25 k-laptop bluetoothd[11444]: RFCOMM server failed for 
:1.36/Profile/HSPHSProfile/1108--1000-8000-00805f9b34fb: rfcomm_bind: 
Address already in use (98)
sie 18 21:14:25 k-laptop dbus-daemon[655]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
sie 18 21:14:25 k-laptop kernel: debugfs: File 'le_min_key_size' in directory 
'hci0' already present!
sie 18 21:14:25 k-laptop kernel: debugfs: File 'le_max_key_size' in directory 
'hci0' already present!


I do have similar symptoms, so it might be the bug. Since Groovy's
kernel version is 5.4, has the fix been backported?

** Bug watch added: Linux Kernel Bug Tracker #204765
   https://bugzilla.kernel.org/show_bug.cgi?id=204765

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1891648

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1891648/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Santiago Fernández Núñez]

Hi! ~kaihengfeng, I'm having the same issue (HDMI not working) after
upgrading from Ubuntu 18.04 to 20.04 using a Dell ThinkPad. Do you think
it's possible that the regression affects this model as well? Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).


  WORKAROUND: I installed the 4.15 kernel, so at the moment I can work
  with this. Higher than 4.15 the second monitor doesn't work. Tested
  until 5.8 and without good results. Just with 4.15.

  
  ---
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-azure (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1830084

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level 

[Kernel-packages] [Bug 1882093] Re: CVE-2020-{5963|5967} NVIDIA

[Steve Beattie]

Publication to focal-updates for nvidia-driver-440-server
440.95.01-0ubuntu0.20.04.1 and for groovy happened as well, closing
tasks.

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-440-server (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1882093

Title:
  CVE-2020-{5963|5967} NVIDIA

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-440-server source package in Focal:
  Fix Released

Bug description:
  Security update for CVE-2020-5963 CVE-2020-5967

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1882093/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1890883] Re: [ICH9M] (e)SATA hotplug doesn't work

[mlx]

@Kai - if I change the policy after startup (the default value is
med_power_with_dipm), I still have to issue a manual scan once (doesn't
matter if a device is attached or not), but subsequent attach/detach
changes are noticed as expected.

I found that kernel-cmdline equivalent of this setting should be
ahci.mobile_lpm_policy=0, but haven't found if/how to apply this change
to a specific ahci host port.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890883

Title:
  [ICH9M] (e)SATA hotplug doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware is a laptop - DELL Latitude E6400, SATA controller Intel
  ICH9M with 4 ports, at least 2 of which should be hotplug-enabled -
  the optical drive bay which has an push-to-eject mechanism, and a
  combo eSATA+USB port on the side.

  Trying various eSATA and plain SATA devices on the port, and inserting
  the optical drive after booting up, neither is detected automatically
  and need a manual bus scan to be detected:

  # scan - - - > /sys/class/scsi_host/host?/scan

  Hotplug works without such manual intervention on this laptop in
  Windows. I've also seen Linux handle hotplug without this intervention
  with an eSATA ExpressCard (SiI3132 chipset) on another machine (can't
  use that in this one, it's only got a CardBus slot).

  I've also read recommendations related to BIOS settings marking the
  slot as "external/removable", but I haven't seen anything of the sort
  in this machine's BIOS setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zdenek  767 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:41:53 2020
  InstallationDate: Installed on 2020-08-06 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E6400
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=5962cfa3-cf85-4f62-9655-8bf792852323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0W620R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0W620R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890883/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: systemd (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814373

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Mike Pozulp]

@John Hoff

Woohoo!!! Way to go John! That's great news. I submitted a patch to LKML
(see attached). The content is the same as the patch that worked for
you; all I did was change the commit message. Hopefully it lands in your
favorite kernel distribution soon. :)

> Is there anything I can do to help with the speaker investigation?

Yes, come over to the kernel bugzilla and read what I've written [1].
Comment 28 lists a 2-step process - get a good trace then minimize the
verbs - which has proven to be a significant technical challenge.
Comment 24 describes where I left off in my quest for a trace.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=207423

** Patch added: 
"0001-ALSA-hda-realtek-Add-quirk-for-Samsung-Galaxy-Book-I.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5402575/+files/0001-ALSA-hda-realtek-Add-quirk-for-Samsung-Galaxy-Book-I.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851518

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, 

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-gcp (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1830084

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
 

[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rafael César Neves]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1
LTS kernel 5.4.0-42-generic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892074] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892074

Title:
  WiFi keeps disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2) $ apt-cache policy linux-image-5.4.0-42-generic
  linux-image-5.4.0-42-generic:
Installed: 5.4.0-42.46
Candidate: 5.4.0-42.46
Version table:
   *** 5.4.0-42.46 500
  500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) No WiFi disconnects
  4) WiFi disconnects (other clients don't have any issues)

  The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
  dual-band (4 channels), WPA2-PSK.

  I see reglular WiFi disconnects since a few days now, possibly related
  to a kernel and/or firmware upgrade.

  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
  looks similar, but I have different Intel hardware:

  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
  160MHz Wireless Network Adapter (201NGW) (rev 30)

  [87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
  [87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
  [87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
  [87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
  [87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
  [87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
  [87471.950902] iwlwifi :00:14.3: 0x1000 | data2
  [87471.950903] iwlwifi :00:14.3: 0xF008 | data3
  [87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
  [87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
  [87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
  [87471.950910] iwlwifi :00:14.3: 0x | time gp1
  [87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
  [87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
  [87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
  [87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
  [87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
  [87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
  [87471.950926] iwlwifi :00:14.3: 0x | isr1
  [87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
  [87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
  [87471.950931] iwlwifi :00:14.3: 0x | isr4
  [87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
  [87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
  [87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
  [87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
  [87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
  [87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
  [87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
  [87471.950944] iwlwifi :00:14.3: 0x | timestamp
  [87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
  [87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
  [87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
  [87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
  [87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
  [87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
  [87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  [87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
  [87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
  [87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
  [87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
  [87471.951008] iwlwifi :00:14.3: 0x00AA0108 | last host cmd
  [87471.951010] iwlwifi :00:14.3: 0x | isr status reg
  [87471.951025] iwlwifi :00:14.3: Fseq Registers:
  [87471.951044] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1867128] Re: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: nvidia-graphics-drivers-440 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1867128

Title:
  Install nvidia_layers.json  in /usr/share/vulkan/implicit_layer.d

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New
Status in nvidia-graphics-drivers-440 source package in Bionic:
  New
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Won't Fix

Bug description:
  As per the subject, the nvidia_layers.json file should live in
  /usr/share/vulkan/implicit_layer.d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1867128/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1872021] Re: [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-completion

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872021

Title:
  [Ubuntu][Bionic] systemd caused kernel to hang on fsnotify wait-on-
  completion

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Incomplete

Bug description:
  This is with MAAS 2.7.0, commissioning an HP DL385 G7 with Bionic.
  During the first boot, the machine performs an apt-get upgrade, which 
includes an update of ipmitool (1.8.18-5ubuntu0.1) and freeipmi-tools 
(1.4.11-1.1ubuntu4.1).
  This triggers hung tasks:
  [   66.457048] cloud-init[1534]: Setting up ipmitool (1.8.18-5ubuntu0.1) ... 
   Starting IPMI event daemon...
  
  [  OK  ] Started IPMI event daemon.   
  
  [   67.240857] cloud-init[1534]: Setting up freeipmi-tools 
(1.4.11-1.1ubuntu4.1) ...
  [   67.254241] cloud-init[1534]: Processing triggers for systemd 
(237-3ubuntu10.39) ...
  [  242.642684] INFO: task systemd:1 blocked for more than 120 seconds.
  [  242.725654]   Not tainted 4.15.0-96-generic #97-Ubuntu 
  
  [  242.799835] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.906319] INFO: task kworker/u49:0:6 blocked for more than 120 seconds.  
  
  [  242.997214]   Not tainted 4.15.0-96-generic #97-Ubuntu 
  
  [  243.072024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  247.381896] cloud-init[1534]: Failed to reload daemon: Connection timed 
out  
  [  247.385109] cloud-init[1534]: Processing triggers for man-db 
(2.8.3-2ubuntu0.1) ...
  [  249.828279] cloud-init[1534]: Processing triggers for ureadahead 
(0.100.0-21) ...
  [  249.874840] cloud-init[1534]: Processing triggers for install-info 
(6.5.0.dfsg.1-2) ...
  [  250.160889] cloud-init[1534]: Processing triggers for libc-bin 
(2.27-3ubuntu1) ...
  [  363.465849] INFO: task systemd:1 blocked for more than 120 seconds.
  [  363.550072]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  363.623823] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.728949] INFO: task kworker/u49:0:6 blocked for more than 120 seconds.
  [  363.820481]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  363.894774] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  484.291609] INFO: task systemd:1 blocked for more than 120 seconds.
  [  484.381026]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  484.458451] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  484.568130] INFO: task kworker/u49:0:6 blocked for more than 120 seconds.
  [  484.661642]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  484.740371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  484.850615] INFO: task udevadm:2665 blocked for more than 120 seconds.
  [  484.942379]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  485.018318] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  607.165768] INFO: task systemd:1 blocked for more than 120 seconds.
  [  607.250976]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  607.325651] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  607.432497] INFO: task kworker/u49:0:6 blocked for more than 120 seconds.
  [  607.525757]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  607.599770] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  607.707273] INFO: task udevadm:2665 blocked for more than 120 seconds.
  [  607.795467]   Not tainted 4.15.0-96-generic #97-Ubuntu
  [  607.869751] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  I can perform more tests on this system if needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1872021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1866972

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  kernel selftest ftrace will fail with:
  [42] Register/unregister many kprobe events   [FAIL]

  [Test case]
  Run that selftest with:
  cd tools/testing/selftests/ftrace/
  sudo make run_tests

  [Regression potential]
  The suggested fix only change the test, not the ftrace code. From the nature 
of the test, the change would hardly prevent us from detecting other hard 
failures besides that we do not return EEXIST currently for duplicate probes.


  =

  
  Issue found on c4.large with 5.0.0-1027.30-aws

  Test failed with:
  [42] Register/unregister many kprobe events   [FAIL]

   selftests: ftrace: ftracetest
   
   === Ftrace unit tests ===
   [1] Basic trace file check   [PASS]
   [2] Basic test for tracers   [PASS]
   [3] Basic trace clock test   [PASS]
   [4] Basic event tracing check[PASS]
   [5] Change the ringbuffer size   [PASS]
   [6] Snapshot and tracing setting [PASS]
   [7] trace_pipe and trace_marker  [PASS]
   [8] Generic dynamic event - add/remove kprobe events [PASS]
   [9] Generic dynamic event - add/remove synthetic events  [PASS]
   [10] Generic dynamic event - selective clear (compatibility) [PASS]
   [11] Generic dynamic event - generic clear event [PASS]
   [12] event tracing - enable/disable with event level files   [PASS]
   [13] event tracing - restricts events based on pid   [PASS]
   [14] event tracing - enable/disable with subsystem level files   [PASS]
   [15] event tracing - enable/disable with top level files [PASS]
   [16] Test trace_printk from module   [UNRESOLVED]
   [17] ftrace - function graph filters with stack tracer   [PASS]
   [18] ftrace - function graph filters [PASS]
   [19] ftrace - function pid filters   [PASS]
   [20] ftrace - stacktrace filter command  [PASS]
   [21] ftrace - function trace with cpumask[PASS]
   [22] ftrace - test for function event triggers   [PASS]
   [23] ftrace - function trace on module   [UNRESOLVED]
   [24] ftrace - function profiling [PASS]
   [25] ftrace - function profiler with function tracing[PASS]
   [26] ftrace - test reading of set_ftrace_filter  [PASS]
   [27] ftrace - test for function traceon/off triggers [PASS]
   [28] Test creation and deletion of trace instances while setting an event
[PASS]
   [29] Test creation and deletion of trace instances   [PASS]
   [30] Kprobe dynamic event - adding and removing  [PASS]
   [31] Kprobe dynamic event - busy event check [PASS]
   [32] Kprobe dynamic event with arguments [PASS]
   [33] Kprobe event with comm arguments[PASS]
   [34] Kprobe event string type argument   [PASS]
   [35] Kprobe event symbol argument[PASS]
   [36] Kprobe event argument syntax[PASS]
   [37] Kprobes event arguments with types  [PASS]
   [38] Kprobe event auto/manual naming [PASS]
   [39] Kprobe dynamic event with function tracer   [PASS]
   [40] Kretprobe dynamic event with arguments  [PASS]
   [41] Kretprobe dynamic event with maxactive  [PASS]
   [42] Register/unregister many kprobe events  [FAIL]
   [43] Kprobe dynamic event - adding and removing  [PASS]
   [44] test for the preemptirqsoff tracer  [UNSUPPORTED]
   [45] Test wakeup tracer  [PASS]
   [46] Test wakeup RT tracer   [PASS]
   [47] event trigger - test extended error support [PASS]
   [48] event trigger - test field variable support [PASS]
   [49] event trigger - test multiple actions on hist trigger   [PASS]
   [50] event trigger - test inter-event histogram trigger onmatch action   
[PASS]
   [51] event trigger - test inter-event histogram trigger onmatch-onmax action 
[PASS]
   [52] event trigger - test inter-event histogram trigger onmax action [PASS]
   [53] event trigger - test synthetic_events syntax parser [PASS]
   [54] event trigger - test event enable/disable trigger   [PASS]
   [55] event trigger - test trigger filter [PASS]
   [56] event trigger - test histogram modifiers[PASS]
   [57] event trigger - test multiple histogram triggers[PASS]
   [58] event trigger - test snapshot-trigger   [PASS]
   [59] event trigger - test stacktrace-trigger [PASS]
   [60] trace_marker trigger - test snapshot trigger[PASS]
   [61] trace_marker trigger - test histogram with synthetic event against 

[Kernel-packages] [Bug 1836414] Re: Wireless 8265 / 8275 crashing on creating TDLS connection

[Besmir Zanaj]

havent had this issue recently. hope the latest updates have fixed that
in focal too

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1836414

Title:
  Wireless 8265 / 8275 crashing on creating TDLS connection

Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  Incomplete

Bug description:
  The Intel 8265 / 8275 Wireless in my Lenovo ThinkPad X1 Yoga (Gen 3)
  keeps constantly crashing with

  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Creating peer entry for 
1c:23:2c:6e:90:09
  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Dialog Token in TPK M1 1
  Jun 28 21:09:46 thinkflurl kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x8200.

  I'm reporting this against the linux-firmware package because I found
  this bug report https://bugzilla.kernel.org/show_bug.cgi?id=203055 and
  the firmware posted in comment 1 fixed the crashes. But the thing is,
  on Jun 28 21:09:46 this crash happend the first time after months of
  trouble free wifi. And in dpkg.log I don't see any updates to this
  package before the crash. So I have no clue, what caused this.

  What I expected to happen:
  I expected a stable wifi connection

  What happens:
  Wifi keeps crashing

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-firmware 1.178.2 [modified: 
lib/firmware/iwlwifi-8000C-36.ucode lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 12 20:46:10 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-04-06 (97 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836414/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1867128] Re: Install nvidia_layers.json in /usr/share/vulkan/implicit_layer.d

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1867128

Title:
  Install nvidia_layers.json  in /usr/share/vulkan/implicit_layer.d

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New
Status in nvidia-graphics-drivers-440 source package in Bionic:
  New
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Won't Fix

Bug description:
  As per the subject, the nvidia_layers.json file should live in
  /usr/share/vulkan/implicit_layer.d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1867128/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: acpid (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864045

Title:
  [SRU] Hibernation events sometimes missed on repeated attempts

Status in acpid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in acpid source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in acpid source package in Eoan:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on
  bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with
  repeated attempts. The first attempt will always be triggered, but the
  next attempt may not. The result is the agent never triggers the
  hibernation process and the instance will be forced to shutdown after
  a timeout period.

  Two workarounds have been identified. The first is to restart acpid
  during the resume handler. The second is to use the latest upstream
  acpid (as of Feb 1, 2020). This second workaround indicates there may
  be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work
  with the 5.0+ kernels.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on 
a bionic image with on-demand hibernation support enabled.
  2) Hibernate and resume the instance, ensuring the system is fully resumed 
afterward and the swap file has been removed.
  3) Hibernate and resume another time. The hibernate should be triggered 
immediately and the instance should become unresponsive as it saves state to 
disk.
  4) Resume the instance, it should come back with the same processes running.
  5) Repeat 3) - 4) as necessary.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: acpid 1:2.0.28-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1877654] Re: Add XDP support to hv_netvsc driver

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-azure (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1877654

Title:
  Add XDP support to hv_netvsc driver

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Confirmed
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux-azure-4.15 source package in Eoan:
  Invalid
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Microsoft would like to request the following three patches in all
  releases supported on Azure:

  351e1581395fc (“hv_netvsc: Add XDP support”)
  12fa74383ed4d (“hv_netvsc: Update document for XDP support”)
  184367dce4f7 (“hv_netvsc: Fix XDP refcnt for synthetic and VF NICs”)

  
  These patches add support of XDP in native mode to the hv_netvsc driver, and
  transparently sets the XDP program on the associated VF NIC as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877654/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1886364] Re: initiator causes kernel crash when login lun/disk on Focal

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886364

Title:
  initiator causes kernel crash when login lun/disk on Focal

Status in ceph-iscsi package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  Software version
  linaro@j13-r120-t32-09:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal
  linaro@j13-r120-t32-09:~$ uname -a
  Linux j13-r120-t32-09 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:57:16 UTC 
2020 aarch64 aarch64 aarch64 GNU/Linux
  linaro@j13-r120-t32-09:~$
  stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search ceph-iscsi
  Sorting... Done
  Full Text Search... Done
  ceph-iscsi/focal,now 3.4-0ubuntu2 all [installed]
    common logic and CLI tools for creating and managing LIO gateways for Ceph

  stack@j13-r120-t32-09:~/devstack-plugin-ceph$ apt search tcmu-runner
  Sorting... Done
  Full Text Search... Done
  libtcmu2/focal,now 1.5.2-5build1 arm64 [installed,automatic]
    Library that handles the userspace side of the LIO TCM-User backstore

  tcmu-runner/focal,now 1.5.2-5build1 arm64 [installed]
    Daemon that handles the userspace side of the LIO TCM-User backstore

  Hardware
  cavium thx1

  root@j13-r120-t32-09:/home/linaro# lshw -c cpu
    *-cpu
     description: CPU
     product: ARM (CN88xx)
     vendor: CN8890-2000BG2601-CP-Y-G
     physical id: 2e
     bus info: cpu@0
     version: 2.1
     serial: CPU Serial#
     slot: Socket
     size: 2GHz
     capacity: 2GHz
     clock: 156MHz
     capabilities: lm
     configuration: cores=48 enabledcores=48
  root@j13-r120-t32-09:/home/linaro# lshw -c system
  j13-r120-t32-09
  description: System
  product: R120-T32-00 (01234567890123456789AB)
  vendor: GIGABYTE
  version: 0100
  serial: GHG2N2912A0009
  width: 64 bits
  capabilities: smbios-3.0.0 dmi-3.0.0 smp cp15_barrier setend swp 
tagged_addr_disabled
  configuration: chassis=server family=Server sku=01234567890123456789AB 
uuid=--4000-8000-1C1B0D94A9DE

  Reproduce
  Setup ceph iscsi gate way and initiator in the same ubuntu focal all-in-one.
  iSCSI targets setup
  1, $ apt install ceph-iscsi targetcli-fb
  2, ceph iscsi config
  stack@j13-r120-t32-09:~/devstack-plugin-ceph$ sudo cat 
/etc/ceph/iscsi-gateway.cfg

  [config]
  api_port = 5002
  api_password = openstack
  api_user = openstack
  api_secure = false
  prometheus_host = 10.101.96.110
  gateway_keyring = ceph.client.admin.keyring
  cluster_name = ceph
  trusted_ip_list = 10.101.96.110,localhost
  minimum_gateways = 1
  pool = volumes

  3, target iqn, client iqn, disk/lun creation
  https://docs.ceph.com/docs/master//rbd/iscsi-target-cli/

  iSCSI initiator setup
  1, $ apt install open-iscsi
  https://www.server-world.info/en/note?os=Ubuntu_18.04=iscsi=3
  2,
  $ iscsiadm -m discovery -t sendtargets -p 10.101.96.110
  $ sudo iscsiadm -m node -T iqn.1993-08.org.opendev:01:a9aa4032d2c1 -l
  Login lun cause crash ceph iscsi gw node

  [  122.112611] xfs filesystem being mounted at /var/lib/ceph supports 
timestamps until 2038 (0x7fff)
  linaro@j13-r120-t32-09:~$ [ 1512.796815] Unable to handle kernel read from 
unreadable memory at virtual address 01dc0040
  [ 1512.805865] Mem abort info:
  [ 1512.808647]   ESR = 0x9604
  [ 1512.811702]   EC = 0x25: DABT (current EL), IL = 32 bits
  [ 1512.817023]   SET = 0, FnV = 0
  [ 1512.820089]   EA = 0, S1PTW = 0
  [ 1512.823238] Data abort info:
  [ 1512.826128]   ISV = 0, ISS = 0x0004
  [ 1512.829972]   CM = 0, WnR = 0
  [ 1512.832933] user pgtable: 4k pages, 48-bit VAs, pgdp=000cd14a
  [ 1512.839410] [01dc0040] pgd=
  [ 1512.844300] Internal error: Oops: 9604 [#1] SMP
  [ 1512.849169] Modules linked in: target_core_pscsi target_core_file 
target_core_iblock iscsi_target_mod xfs xt_REDIRECT xt_comment xt_nat xt_mark 
xt_connmark ip6table_raw iptable_raw xt_CHECKSUM xt_MASQUERADE xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge 
stp llc target_core_user uio target_core_mod nf_conntrack_netlink binfmt_misc 
nls_iso8859_1 nfnetlink_cttimeout nfnetlink ipmi_ssif ipmi_devintf 
cavium_rng_vf joydev input_leds ipmi_msghandler cavium_rng thunderx_edac 
openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
libcrc32c sch_fq_codel ip_tables x_tables autofs4 crct10dif_ce 

[Kernel-packages] [Bug 1842479] Re: timer_create will fail with invalid error code

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842479

Title:
  timer_create will fail with invalid error code

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  On some OpenPower systems, RTC does not support set_alarm, and 
timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of 
EOPNOTSUPP. This will break some regression testing that expects the later 
value.

  [Test cases]
  Run LTP syscalls regression testing, which we do before releasing kernels.

  [Regression potential]
  This should not break any userspace, as none should be using/expecting 
ENOTSUPP for any call. In order to do so, they would have to go out of their 
way as it's not defined on libc headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1873537] Re: PCIe AER device recovery failed due to logic flaw

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873537

Title:
  PCIe AER device recovery failed due to logic flaw

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  Impact:

  During PCI Express Downstream Port Containment (DPC) recovery,
  certain types of failures do not recover due to a logic flaw
  in pcie_do_recovery().

  The upstream git commit log explains the change:

  PCI/ERR: Update error status after reset_link()
  Commit bdb5ac85777d ("PCI/ERR: Handle fatal error recovery") uses
  reset_link() to recover from fatal errors.  But during fatal error
  recovery, if the initial value of error status is PCI_ERS_RESULT_DISCONNECT
  or PCI_ERS_RESULT_NO_AER_DRIVER then even after successful recovery (using
  reset_link()) pcie_do_recovery() will report the recovery result as
  failure.  Update the status of error after reset_link().

  You can reproduce this issue by triggering a SW DPC using "DPC Software
  Trigger" bit in "DPC Control Register".  You should see recovery failed
  dmesg log as below:

pcieport :00:16.0: DPC: containment event, status:0x1f27 source:0x
pcieport :00:16.0: DPC: software trigger detected
pci :04:00.0: AER: can't recover (no error_detected callback)
pcieport :00:16.0: AER: device recovery failed

  Fixes: bdb5ac85777d ("PCI/ERR: Handle fatal error recovery")
  Link: 
https://lore.kernel.org/r/a255fcb3a3fdebcd90f84e08b555f1786eb8eba2.158584.git.sathyanarayanan.kuppusw...@linux.intel.com
  [bhelgaas: split pci_channel_io_frozen simplification to separate patch]
  Signed-off-by: Kuppuswamy Sathyanarayanan 

  Signed-off-by: Bjorn Helgaas 
  Acked-by: Keith Busch 
  Cc: Ashok Raj 

  Note that a second prerequisite patch is necessary as well.  This
  patch,

  commit b5dfbeacf74865a8d62a4f70f501cdc61510f8e0
  Author: Kuppuswamy Sathyanarayanan 

  Date:   Fri Mar 27 17:33:24 2020 -0500

  PCI/ERR: Combine pci_channel_io_frozen cases

  is a code readability change, and makes no functional changes.

  
  Testcase:

  On a system with DPC enabled, setpci may be used to set the DPC Software
  Trigger bit (bit 6, value 0x40) in the DPC Control register of a suitable
  PCIe device (a PCIe bridge, for example).

  On a system lacking the fix, the output will be as shown above (i.e.,
  culminating in the "device recovery failed" message).  With the fix
  applied, the device successfully recovers, resulting in a message of the
  form

  pcieport :d9:01.0: AER: Device recovery successful

  
  Regression Potential:

  The risk of regression is low, as (a) the path in question currently does
  not work, and (b) the changes are minimal, comprising only a housekeeping
  change and the logically correct updating of a status variable that did
  not previously occur.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873537/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1845048] Re: Improve sysctl handling on kdump-tools

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: makedumpfile (Ubuntu Eoan)
   Status: In Progress => Won't Fix

-- 
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/1845048

Title:
  Improve sysctl handling on kdump-tools

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  Opinion
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in makedumpfile source package in Focal:
  In Progress
Status in makedumpfile source package in Groovy:
  In Progress
Status in makedumpfile package in Debian:
  New

Bug description:
  [impact]

  Documentation, and past behavior, for kdump-tools was that the
  KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be
  applied to the system kernel params at kdump 'load'.  However this is
  no longer true, and those params are no longer applied to the system's
  kernel param settings.

  [test case]

  install linux-crashdump (and kdump-tools).

  Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param
  to something other than default, e.g.:

  KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1"

  reboot, or unload/reload kdump, to pick up the changes to the file.

  Check if the panic_on_warn param is set:

  $ cat /proc/sys/kernel/panic_on_warn
  0

  the problem does not seem to be with sysctl, as manually calling it
  does work:

  $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1"
  $ cat /proc/sys/kernel/panic_on_warn
  0
  $ sudo sysctl -w $KDUMP_SYSCTL
  kernel.panic_on_oops = 1
  kernel.panic_on_warn = 1
  $ cat /proc/sys/kernel/panic_on_warn
  1

  [regression potential]

  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1845048/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1851663] Re: (In)consistent autopkgtest failures on ppc64el/s390x

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: makedumpfile (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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/1851663

Title:
  (In)consistent autopkgtest failures on ppc64el/s390x

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed

Bug description:
  Recently autopkgtest started to consistently fail in ppc64el / s390x.
  When testing manually, the kernel dump is collected and all works
  fine. By discussing with the package maintainer (Cascardo), it seems
  it started after a change in the instance type of the tests, to
  m1.large.

  This seems either a problem in the test infrastructure itself or a likely a 
"timing" problem in the test (i.e., requiring some pause or delay that is not 
currently enough).
  This demands investigation because those failures delay the package release 
for all arches, usually those releases contain important fixes.

  Also, the recurrent "workaround" is to mark the tests as "force-
  badtest" in ubuntu-hints for the 2 arches, which is in practice
  skipping the test, so those 2 arches are getting releases untested by
  the automatic infrastructure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863234

Title:
  Disabling bpf() syscall on kernel lockdown break apps when secure boot
  is on

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  The bpf(2) system call is completely blocked in Disco and Eoan when
  Secure Boot is enabled due to overly restrictive Lockdown policies.
  This makes it so that all bpf related tools are not usable on those
  releases.

  [Test Case]

  Set up test BPF programs:

  $ cat hello.bt
  BEGIN { printf("hello\n"); exit(); }
  $ cat kprobe.bt
  kprobe:do_nanosleep { printf("task sleeping...\n"); exit(); }
  $ cat open.bt
  tracepoint:syscalls:sys_enter_openat {
    printf("filename: [%s]; flags: [%d]\n",
   str(args->filename), args->flags);
  }

  Disable Secure Boot:

  $ sudo mokutil --disable-validation
  ...
  $ sudo reboot

  Ensure that hello.bt can run:

  $ sudo bpftrace hello.bt
  Attaching 1 probe...
  hello

  Ensure that a BPF program triggered by a kprobe works (run `sleep 1` in 
another terminal):
  $ sudo bpftrace kprobe.bt
  Attaching 1 probe...
  task sleeping...

  Ensure that a BPF program triggered by a tracepoint can access the filename 
and flags of openat(2):
  $ sudo bpftrace open.bt
  Attaching 1 probe...
  filename: [/proc/2317/cmdline]; flags: [0]
  filename: [/dev/iio:device1]; flags: [2048]
  ...

  Enable Secure Boot

  $ sudo mokutil --enable-validation
  ...
  $ sudo reboot

  Ensure that a basic BPF program can run:

  $ sudo bpftrace hello.bt
  Attaching 1 probe...
  hello

  Ensure that a BPF program triggered by a kprobe is blocked (kprobes aren't 
allowed under Secure Boot):
  $ sudo bpftrace kprobe.bt
  Attaching 1 probe...
  cannot attach kprobe, Operation not permitted
  Error attaching probe: 'kprobe:do_nanosleep'

  You should see the following kernel message logged:

  Lockdown: bpftrace: Use of kprobes is restricted; see man
  kernel_lockdown.7

  Ensure that a BPF program triggered by a tracepoint can NOT access the 
filename and flags of openat(2) (all filenames should be empty and all flags 
should be 0):
  $ sudo bpftrace open.bt
  Attaching 1 probe...
  filename: []; flags: [0]
  filename: []; flags: [0]
  ...

  You should see the following kernel message logged:

  Lockdown: iio-sensor-prox: BPF is restricted; see man
  kernel_lockdown.7

  [Regression Potential]

  Low. This is opening up the use of bpf(2) while under Lockdown. There
  should be no new restrictions put in place.

  [Original Report]

  In disco and eoan, lockdown is automatically enforced when secure boot
  is on [0]. Because lockdown was not in the mailine kernel at the time,
  some disrto-specific patches were added to the kernel, including one
  that drastically restricts BPF usage by completely disabling the use
  of the `bpf()` system call when lockdown is on [1].

  A consequence of that decision is that no application relying on eBPF
  can run on 19.04/19.10, unless secure boot / lockdown is disabled. For
  example, Cilium (cilium.io) strongly relies on BPF programs to
  implement its datapath and securing network connectivity between
  containers. Other applications like Suricata or Sysdig also rely on
  BPF to some extent. None of which will work by default on a EFI
  machine with secure boot activated.

  If I understand correctly, kernel 5.4 (to be used in focal) will have
  a different, lighter restricton (comming from mainline Linux kernel)
  [2], so `bpf()` for networking use cases should mostly work on 20.04.
  Is my understanding correct? If so, could this patch be backported to
  19.10 (and 19.04, if still supported) instead of completely disabling
  the syscall on lockdown?

  Links:
  [0] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517
  [1] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d
  [2] 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840122

Title:
  System fails to reboot from live session or ubiquity-dm -
  squashfs_read_data failed to read block

Status in casper package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in casper source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  Last known good image: Eoan Ubuntu Desktop 20190715

  Similar results started to happen with new linux-hwe kernel based on
  eoan for 18.04.4 release.

  Test Case:
  1. Boot eoan desktop to a live session
  2. Wait a couple of minutes until snapd settles
  3. Reboot the system from the system menu or from the command line

  Expected result:
  The system reboots

  Actual result:
  The systems fails to reboot or shutdown and displays some errors about 
failing to unmount /cdrom and squashfs errors in a loop.

  Unmounting /cdrom...
  [FAILED] Failed unmounting /cdrom.
  [  OK  ] Started Shuts down the "li…" preinstalled system cleanly.
  [  OK  ] Reached target Final Step.
  [  OK  ] Started Reboot.
  [  OK  ] Reached target Reboot.
  [  115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700
  [  115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0
  [  115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0
  [  115.775824] SQUASHFS error: squashfs_read_data failed to read block 
0x2dd2d998

  This also causes daily tests to fail and is reproducible in a VM and
  bare metal booted in legacy bios mode

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: casper 1.414
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.414
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 08:31:30 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.414
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Tags:  eoan
  Uname: Linux 5.2.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1788 F pulseaudio
  CasperVersion: 1.414
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  IwConfig:
   lono wireless extensions.

   ens3  no wireless extensions.
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
---  keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-10-generic N/A
   linux-backports-modules-5.2.0-10-generic  N/A
   linux-firmware1.181
  RfKill:

  Tags:  eoan
  Uname: Linux 5.2.0-10-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/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-disco
  

[Kernel-packages] [Bug 1882213] Re: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-raspi (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1882213

Title:
  cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and
  20.04 kernel to hang

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  New
Status in linux-raspi source package in Groovy:
  New

Bug description:
  Copying a large file using cp on my Raspberry Pi 3B (not 3B+) from an
  externally-powered USB hard disk (Seagate Expansion 2TB) to an NFS-
  mounted filesystem across Ethernet causes the kernel of releases 19.10
  and 20.04 to hang/freeze.

  This happens every time the copy is attempted, although the exact
  duration from the start of the copy to the hang varies from a few
  seconds to a couple of minutes. The kernel does not recover even after
  long waits (30mins+), and a power reset (pulling the plug) is
  required. (Although I admit I haven't tried yet simply disconnecting
  the USB cable of the HDD during a hang. Update: I've now tried that -
  the system doesn't recover after pulling the USB cable out.)

  Likewise, messages are erratic and I suspect are only symptoms,
  notably watchdog BUG soft lockup messages and RCU stall messages on
  different CPU cores for different processes/threads. There are no
  hardware messages that I've seen recorded in log files (or appearing
  on the console) matching the incidents.

  When a hang happen, network connectivity is lost - ssh sessions fail,
  and the file copy stops (even when the cp is run on the console).
  Pings to the system from other hosts on the same Ethernet LAN (and
  switch) fail with destination host unreachable.

  Although I have had a swapfile configured on the SD card, the hangs
  continue to happen doing the cp after "swapoff -a". I've also tried
  playing with taskset affinities and snappiness to no obvious effect -
  the hangs still keep happening.

  Copying from the external HDD to the SD card is successful, as is
  copying from the SD card to the NFS.

  Raspbian 4.19.0-8 (armmp-lpae) does not have this problem; it
  successfully copies the file from HDD to NFS across Ethernet without
  stalling.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11
  ProcVersionSignature: Ubuntu 5.4.0-1011.11-raspi 5.4.34
  Uname: Linux 5.4.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Fri Jun  5 07:37:44 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-raspi
  UpgradeStatus: Upgraded to focal on 2020-05-21 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1882213/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1816743] Re: Add systemd's kdump service command-line regardless if user provides or not KDUMP_CMDLINE_APPEND

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: makedumpfile (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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/1816743

Title:
  Add systemd's kdump service command-line regardless if user provides
  or not KDUMP_CMDLINE_APPEND

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed

Bug description:
  Since Xenial release, Ubuntu relies on systemd as its init system -
  there's a kdump service to prevent some other services to
  unnecessarily start in kdump environment.

  Problem: if we add something to KDUMP_CMDLINE_APPEND, the entry for
  kdump service, "systemd.unit=kdump-tools.service" is removed from the
  command-line. The user manually needs to add that, and this seems
  highly prone to error.

  We propose here to decouple the "systemd.unit=kdump-tools.service"
  parameter from KDUMP_CMDLINE_APPEND, so if user wants really to remove
  this option, they should used KDUMP_CMDLINE instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1816743/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: makedumpfile (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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/1800562

Title:
  Remove obsolete "nousb" option in kdump command-line for newer kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed

Bug description:
  [Impact]
  * Kdump command-line include an obsolete "nousb" parameter by default, which 
can cause a misimpression: users will think they are not booting with USB, but 
they are.

  * Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  * USB may be pretty essential in case for example kdump users need to
  decrypt a disk under LUKS, and there's only an USB keyboard connected
  to the system. Given the option is innocuous since Bionic, we should
  just drop it to prevent confusion.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'nousb' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz

  
  [Regression Potential]

  The regression potential is extremely low, since the "nousb" parameter
  is not used since Bionic although is there. Any bugs we would have by
  changing this are still valid by not removing the option - the
  semantics with or without "nosub" is the same since from Bionic.

  NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
  disables USB by taking the "nousb" parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845677

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  There are 2 physical speakers on the X1 7th, and one is Bass speaker
  and connect to a DAC which doesn't have volume control on it.

  [Fix]
  adjust that speaker to connect to a DAC which has volume control
  capability.

  
  [Test Case]
  adjust the output volume from UI and play sound from speaker.

  
  [Regression Risk]
  Low, these change is specific to 2 lenovo machines.


  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1831940] Re: hibernation support for linux-aws

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws-5.0 (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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/1831940

Title:
  hibernation support for linux-aws

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws-5.0 package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux-aws-5.0 source package in Xenial:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws-5.0 source package in Bionic:
  Fix Released
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-aws-5.0 source package in Disco:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Released
Status in linux-aws-5.0 source package in Eoan:
  Won't Fix
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws-5.0 source package in Focal:
  Invalid

Bug description:
  Additional AWS-specific and mainline patches are required to support
  hibernation across the various types of AWS instances.

  The following patch sets for linux-aws-xenial and linux-aws-bionic
  provide the necessary functionality, and should only impact the
  hibernation and resume paths.

  [linux-aws-xenial]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  radix-tree: delete radix_tree_locate_item()
  mm: rid swapoff of quadratic complexity
  sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to 
wake_up()
  sched/wait: Avoid abort_exclusive_wait() in ___wait_event()
  sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock()
  sched/wait: Introduce init_wait_entry()
  sched/wait: Standardize wait_bit_queue naming
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  NVMe: Allow request merges
  PM / hibernate: Do not free preallocated safe pages during image restore
  PM / hibernate: Recycle safe pages after image restoration
  PM / hibernate: Simplify mark_unsafe_pages()
  UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
  UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on 
hibernate

  [linux-aws-bionic]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  mm: rid swapoff of quadratic complexity
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  netlink: Don't shift on 64 for ngroups

  [linux-aws-edge-bionic]

  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  PM / hibernate: memory_bm_find_bit(): Tighten node optimisation
  mm: rid swapoff of quadratic complexity
  mm: refactor swap-in logic out of shmem_getpage_gfp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1831940/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-oracle (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1830084

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level 

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812622

Title:
  fib related test in net from ubuntu_kernel_selftests failed with
  Operation not supported / Error: Unknown device type.

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New
Status in linux source package in Eoan:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812622

Title:
  fib related test in net from ubuntu_kernel_selftests failed with
  Operation not supported / Error: Unknown device type.

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New
Status in linux source package in Eoan:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM / E-KVM

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1837348

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with D-KVM / E-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix

Bug description:
  Issue found on a AMD64 KVM node with Disco KVM kernel.

  selftests: net: test_vxlan_under_vrf.sh
  
  Error: Unknown device type.
  Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory
  not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11
  ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8
  Uname: Linux 5.0.0-1010-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Jul 22 05:04:42 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812622

Title:
  fib related test in net from ubuntu_kernel_selftests failed with
  Operation not supported / Error: Unknown device type.

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New
Status in linux source package in Eoan:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1836414] Re: Wireless 8265 / 8275 crashing on creating TDLS connection

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-firmware (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1836414

Title:
  Wireless 8265 / 8275 crashing on creating TDLS connection

Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  Incomplete

Bug description:
  The Intel 8265 / 8275 Wireless in my Lenovo ThinkPad X1 Yoga (Gen 3)
  keeps constantly crashing with

  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Creating peer entry for 
1c:23:2c:6e:90:09
  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Dialog Token in TPK M1 1
  Jun 28 21:09:46 thinkflurl kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x8200.

  I'm reporting this against the linux-firmware package because I found
  this bug report https://bugzilla.kernel.org/show_bug.cgi?id=203055 and
  the firmware posted in comment 1 fixed the crashes. But the thing is,
  on Jun 28 21:09:46 this crash happend the first time after months of
  trouble free wifi. And in dpkg.log I don't see any updates to this
  package before the crash. So I have no clue, what caused this.

  What I expected to happen:
  I expected a stable wifi connection

  What happens:
  Wifi keeps crashing

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-firmware 1.178.2 [modified: 
lib/firmware/iwlwifi-8000C-36.ucode lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 12 20:46:10 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-04-06 (97 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836414/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1861278] Re: RTL8821CE - 5GHZ networks not working

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: rtl8821ce (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861278

Title:
  RTL8821CE - 5GHZ networks not working

Status in linux package in Ubuntu:
  Incomplete
Status in rtl8821ce package in Ubuntu:
  Incomplete
Status in rtl8821ce source package in Bionic:
  Confirmed
Status in rtl8821ce source package in Eoan:
  Won't Fix
Status in rtl8821ce source package in Focal:
  Incomplete

Bug description:
  5 GHZ networks are not showing up

  dmesg | grep 8821
  [2.85] rtl8821ce: loading out-of-tree module taints kernel.
  [2.403456] rtl8821ce: module verification failed: signature and/or 
required key missing - tainting kernel
  [2.435475] RTW: rtl8821ce v5.2.5.2.1_.20181112_beta
  [2.435480] RTW: rtl8821ce BT-Coex version = COEX20170310-1212
  [4.599321] rtl8821ce :02:00.0 wlo1: renamed from wlan0

  dmesg |grep -i firm
  [0.147142] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [3.101456] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)

  iw list
  returns nothing...

  iwlist wlo1 freq
  wlo1  22 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 149 : 5.745 GHz
Channel 153 : 5.765 GHz
Channel 157 : 5.785 GHz
Channel 161 : 5.805 GHz
Channel 165 : 5.825 GHz
Current Frequency:2.437 GHz (Channel 6)

  Related:
  https://github.com/tomaspinho/rtl8821ce/issues/34
  https://github.com/tomaspinho/rtl8821ce/issues/103
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861278/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861936

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  

[Kernel-packages] [Bug 1858618] Re: linux-aws: swapoff optimization

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws-5.0 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
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/1858618

Title:
  linux-aws: swapoff optimization

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws-5.0 package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws-5.0 source package in Bionic:
  Fix Released
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-aws-5.0 source package in Disco:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Released
Status in linux-aws-5.0 source package in Eoan:
  Won't Fix
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws-5.0 source package in Focal:
  Invalid

Bug description:
  [Impact]

  When an instance in the AWS EC2 infrastructure is successfully
  hibernated and resumed we want to deactivate the swap file as fast as
  possible in order to make the instance available again for the user.
  By default the kernel doesn't really optimize swapoff performance, it
  tries to keep the whole system still usable and responsive while
  swapoff is running.

  However, in our specific use case, swapoff needs to complete as fast
  as possible, so we may want to give swapoff I/O a higher priority and
  use different heuristics in order to optimize the I/O and page
  readahead generated by swapoff.

  [Test Case]

  Run the hibernation test on the AWS EC2 instances.

  [Fix]

  Apply a more aggressive swapin readahead policy that allows to improve
  swapoff performance.

  [Regression Potential]

  Minimal, this change is only affecting the swapoff-related code and it
  has been tested extensively with positive test results. The only
  downside is that this different heuristic makes the system more
  unresponsive during swapoff, but this is not a problem in the AWS
  scenario, because (by explicit requirement) the user shouldn't be able
  to use the instance during this swapoff phase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1858618/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1830084

Title:
  ubuntu_kernel_selftests ftrace fails

Status in ubuntu-kernel-tests:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  Cloud: Azure
  Series: Disco
  Kernel: 5.0.0-1007.7  linux-azure
  Instance: Standard_D2_v3 and others. 

  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13
  05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest
  05/20 14:24:27 DEBUG| utils:0153| [stdout] 

  05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal 
number: 
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests ===
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file 
check
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for 
tracers
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock 
test
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing 
check
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the 
ringbuffer size
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing 
setting
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and 
trace_marker
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic 
event - add/remove kprobe events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic 
event - add/remove synthetic events
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic 
event - selective clear (compatibility)
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic 
event - generic clear event
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - 
enable/disable with event level files
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - 
restricts events based on pid
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - 
enable/disable with subsystem level files
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS]
  05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - 
enable/disable with top level files
 

[Kernel-packages] [Bug 1845687] Re: memory test in ubuntu_kvm_unit tests fails Xenial linux-kvm

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1845687

Title:
  memory test in ubuntu_kvm_unit tests fails Xenial linux-kvm

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux-kvm source package in Eoan:
  Won't Fix

Bug description:
  Series: Xenial
  Kernel: 4.4.0-1059.66 linux-kvm

  specifically clfushopt and clwb

  09/23 08:43:08 DEBUG| utils:0116| Running 'kvm-ok'
  09/23 08:43:08 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists
  09/23 08:43:08 DEBUG| utils:0153| [stdout] KVM acceleration can be used
  09/23 08:43:08 DEBUG| utils:0116| Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory'
  09/23 08:43:08 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4
  09/23 08:43:09 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s 
/usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device 
isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device 
pci-testdev -machine accel=kvm -kernel /tmp/tmp.HnxXwZrpQ9 -smp 1 -cpu host # 
-initrd /tmp/tmp.SL7FtNHKpq
  09/23 08:43:09 DEBUG| utils:0153| [stdout] enabling apic
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: clflush (present)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: sfence (present)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: lfence (present)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: mfence (present)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clflushopt (ABSENT)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clwb (ABSENT)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: invalid clwb
  09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: pcommit (ABSENT)
  09/23 08:43:09 DEBUG| utils:0153| [stdout] SUMMARY: 8 tests, 2 unexpected 
failures
  09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL memory (8 tests, 2 
unexpected failures)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845687/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-signed-oracle-5.0 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
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/1862588

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-signed-oracle-5.0 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-aws source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-signed-oracle-5.0 source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-signed-oracle-5.0 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux-aws source package in Eoan:
  Fix Released
Status in linux-gcp source package in Eoan:
  Fix Released
Status in linux-signed-oracle-5.0 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Running seccomp kernel selftests will fail.

  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.

  On failure:

  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  On success:

  [ RUN  ] global.user_notification_basic
  [   OK ] global.user_notification_basic

  
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.

  ==

  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)

  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  This cannot be reproduced with the kselftest in older kernel, probably
  a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864045

Title:
  [SRU] Hibernation events sometimes missed on repeated attempts

Status in acpid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in acpid source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in acpid source package in Eoan:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on
  bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with
  repeated attempts. The first attempt will always be triggered, but the
  next attempt may not. The result is the agent never triggers the
  hibernation process and the instance will be forced to shutdown after
  a timeout period.

  Two workarounds have been identified. The first is to restart acpid
  during the resume handler. The second is to use the latest upstream
  acpid (as of Feb 1, 2020). This second workaround indicates there may
  be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work
  with the 5.0+ kernels.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on 
a bionic image with on-demand hibernation support enabled.
  2) Hibernate and resume the instance, ensuring the system is fully resumed 
afterward and the swap file has been removed.
  3) Hibernate and resume another time. The hibernate should be triggered 
immediately and the instance should become unresponsive as it saves state to 
disk.
  4) Resume the instance, it should come back with the same processes running.
  5) Repeat 3) - 4) as necessary.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: acpid 1:2.0.28-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1860196] Re: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860196

Title:
  kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  dear everyone.

  I update ubuntu-18.04.3 to use software-updater,
  then kernel update to 5.3.0-26.

  Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up 
fine.
  but could not use applicaion, may be hung up.
  could not click icon, but mouse are moved.
  I use to restore backup and retry 3 times, but same result.

  I reboot another patition ubuntu-18.04, and get /var/log/syslog.
  I attached this report.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1711 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (140 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset 
ipv6.disable=1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: P5K/EPU
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-30 (146 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190808)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5K/EPU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=a84f138c-6bc7-4958-94c6-661217949cbb ro ipv6.disable=1 quiet
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.173.14
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1862831] Re: hciattach on rpi4 times out on first attempt

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1862831

Title:
  hciattach on rpi4 times out on first attempt

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  New

Bug description:
  I've observed this in both armhf and arm64 on:
  19.10.1-server
  18.04.4-server
  core18

  It does not seem to happen on rpi3, only on rpi4.
  If you want to use Bluetooth on rpi, one must first run:
  $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow

  On RPI4, this results in a timeout on the first attempt. Reattempting
  it right after will work though, 100% of the times I've tried it.

  In the failed attempt, the output is:
bcm43xx_init
Initialization timed out.

  And the following is the only new message to show up in dmesg when this fails:
[  270.303691] uart-pl011 fe201000.serial: no DMA platform data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1862831/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: netplan.io (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2-5.3 source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi source package in Focal:
  New
Status in netplan.io source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857257

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  Trying to checkpoint a container (docker/podman) on 18.04 fails
  starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
  this in Travis starting a few weeks ago. Manually testing it locally
  shows that linux-image-5.0.0-32-generic still works and linux-
  image-5.0.0-35-generic does not longer work. It seems to be overlayfs
  related, at least that is what we believe. The CRIU error message we
  see is:

  (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 
path=/bin/busybox
  (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed 
with -1

  
  We have not seen this only in Travis, but also multiple CRIU users reported 
that bug already. Currently we have to tell them to downgrade the kernel.

  I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
  on the 4.18.0 kernel series does not show this error.
  4.18.0-25-generic works without problems.

  See also https://github.com/checkpoint-restore/criu/issues/860

  One of the possible explanations from our side include:

  "Looks like we have the same as for st_dev now with mnt_id, that is
  bad, because we can't find on which mount to open the file if kernel
  hides these information from us."

  Running on the upstream 5.5.0-rc1 kernel does not show this error.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 18:52 seq
   crw-rw 1 root audio 116, 33 Jan  7 18:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: ubuntu-meta (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1856407

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  Won't Fix

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-firmware (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2-5.3 source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi source package in Focal:
  New
Status in netplan.io source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1858988] Re: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142]

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858988

Title:
  USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2
  card [1b21:2142]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Hotplug USB key to Sunix USB Type-A 3.1 Gen 2 card can't be detected

  [Fix]
  ASMedia XHCI USB controller PME# doesn't work under D0, so remove its cap by 
quirk.

  [Test]
  Verified on the target machine, USB 3 storage works.

  [Regression Potential]
  Low, it only affects target chip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1858988/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864092

Title:
  quotactl07 from ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  == SRU Justification ==
  This quotactl07 is a new test case added in LTP test suite, 

  The test will fail with:
<<>>
incrementing stop
tst_kconfig.c:62: INFO: Parsing kernel config 
'/boot/config-5.0.0-38-generic'
tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4'
tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts=''
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check

HINT: You _MAY_ be missing kernel fixes, see:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208

  == Fix ==
  * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call)

  Focal got this patch from stable update. This patch can be cherry-
  picked into all the other kernels.

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/

  All patched kernels are working as expected,

  == Regression Potential ==
  Low, change limited to quota on XFS, and it's just adding a check for the 
flags.

  
  == Original Bug Report ==
  Initially Found:
  Cloud: GCP
  Kernel: 5.0.0-1032.33
  Test: ubuntu_ltp_syscalls

  02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 
2020'
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: 
Parsing kernel config '/boot/config-5.0.0-1032-gcp'
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using 
test device LTP_DEV='/dev/loop2'
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: 
Formatting /dev/loop2 with xfs opts='' extra opts=''
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout 
per run is 0h 05m 00s
  02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: 
Q_XQUOTARM doesn't have quota type check
  02/20 15:04:55 DEBUG| utils:0153| [stdout]
  02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing 
kernel fixes, see:
  02/20 15:04:55 DEBUG| utils:0153| [stdout]
  02/20 15:04:55 DEBUG| utils:0153| [stdout] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208
  02/20 15:04:55 DEBUG| utils:0153| [stdout]
  02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary:
  02/20 15:04:55 DEBUG| utils:0153| [stdout] passed   0
  02/20 15:04:55 DEBUG| utils:0153| [stdout] failed   1
  02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped  0
  02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 
stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0
  02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 
2020'
  02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout 
per run is 0h 05m 00s
  02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) 
returned 512

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-raspi2-5.3 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2-5.3 source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi source package in Focal:
  New
Status in netplan.io source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  Won't Fix
Status in linux-firmware-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2-5.3 source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi source package in Focal:
  New
Status in netplan.io source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
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/1864041

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Released
Status in linux-aws source package in Eoan:
  Won't Fix
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1864603] Re: System freezes for 20 seconds while resuming from s2idle (performance mode)

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864603

Title:
  System freezes for 20 seconds while resuming from s2idle (performance
  mode)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  Realtek cardreader sometimes blocks the resume process. It stuck at blank 
screen around 20 seconds while resuming from s2idle.

  [Fix]

  [Test]

  [Regression Potential]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864603/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1879327] Re: Enforce all config annotations

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879327

Title:
  Enforce all config annotations

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Not all config annotations are enforced, which means config could regress 
without notice.

  [Test case]
  Check the logs mention much more options being enforced. From the hundreds to 
more than 1.

  [Regression potential]
  Builds will start failing when config doesn't match annotations. However, 
this is an opt-in for now, which means only those branches prepared to accept 
it will risk such regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886860

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux source package in Eoan:
  Won't Fix
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  New

Bug description:
  [Impact]
  When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as it's 
not incremented anymore, but decremented when sockets are closed.

  This might lead to crashes possibly because of use-after-free when
  packets are received as shown in LP #1886668.

  [Test case]
  Ran reproducer from comment #2.

  [Regression potential]
  We could break the use of cgroup bpf. The use of cgroup bpf looks to still be 
working from the reproducer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1892074] [NEW] WiFi keeps disconnecting

[Alexander List]

Public bug reported:

1) $ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

2) $ apt-cache policy linux-image-5.4.0-42-generic
linux-image-5.4.0-42-generic:
  Installed: 5.4.0-42.46
  Candidate: 5.4.0-42.46
  Version table:
 *** 5.4.0-42.46 500
500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status

3) No WiFi disconnects
4) WiFi disconnects (other clients don't have any issues)

The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
dual-band (4 channels), WPA2-PSK.

I see reglular WiFi disconnects since a few days now, possibly related
to a kernel and/or firmware upgrade.

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
looks similar, but I have different Intel hardware:

00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
160MHz Wireless Network Adapter (201NGW) (rev 30)

[87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
[87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
[87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
[87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
[87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
[87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
[87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
[87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
[87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
[87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
[87471.950902] iwlwifi :00:14.3: 0x1000 | data2
[87471.950903] iwlwifi :00:14.3: 0xF008 | data3
[87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
[87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
[87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
[87471.950910] iwlwifi :00:14.3: 0x | time gp1
[87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
[87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
[87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
[87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
[87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
[87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
[87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
[87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
[87471.950926] iwlwifi :00:14.3: 0x | isr1
[87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
[87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
[87471.950931] iwlwifi :00:14.3: 0x | isr4
[87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
[87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
[87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
[87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
[87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
[87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
[87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
[87471.950944] iwlwifi :00:14.3: 0x | timestamp
[87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
[87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
[87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
[87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
[87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
[87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
[87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
[87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
[87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
[87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
[87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
[87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
[87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
[87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
[87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
[87471.951008] iwlwifi :00:14.3: 0x00AA0108 | last host cmd
[87471.951010] iwlwifi :00:14.3: 0x | isr status reg
[87471.951025] iwlwifi :00:14.3: Fseq Registers:
[87471.951044] iwlwifi :00:14.3: 0xE101 | FSEQ_ERROR_CODE
[87471.951049] iwlwifi :00:14.3: 0x00290033 | FSEQ_TOP_INIT_VERSION
[87471.951068] iwlwifi :00:14.3: 0x80070043 | FSEQ_CNVIO_INIT_VERSION
[87471.951090] iwlwifi :00:14.3: 0xA481 | FSEQ_OTP_VERSION
[87471.951110] iwlwifi :00:14.3: 0x0002 | FSEQ_TOP_CONTENT_VERSION
[87471.951131] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[87471.951152] iwlwifi :00:14.3: 0x02000300 | FSEQ_CNVI_ID
[87471.951157] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1886568] Re: Eoan update: upstream stable patchset 2020-07-06

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886568

Title:
  Eoan update: upstream stable patchset 2020-07-06

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix

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 2020-07-06

  Ported from the following upstream stable releases:
  v4.19.130, v.5.4.48

     from git://git.kernel.org/

  power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select
  clk: sunxi: Fix incorrect usage of round_down()
  ASoC: tegra: tegra_wm8903: Support nvidia, headset property
  i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
  iio: pressure: bmp280: Tolerate IRQ before registering
  remoteproc: Fix IDR initialisation in rproc_alloc()
  clk: qcom: msm8916: Fix the address location of pll->config_reg
  backlight: lp855x: Ensure regulators are disabled on probe failure
  ASoC: davinci-mcasp: Fix dma_chan refcnt leak when getting dma type
  ARM: integrator: Add some Kconfig selections
  scsi: qedi: Check for buffer overflow in qedi_set_path()
  ALSA: hda/realtek - Introduce polarity for micmute LED GPIO
  ALSA: isa/wavefront: prevent out of bounds write in ioctl
  PCI: Allow pci_resize_resource() for devices on root bus
  scsi: qla2xxx: Fix issue with adapter's stopping state
  iio: bmp280: fix compensation of humidity
  f2fs: report delalloc reserve as non-free in statfs for project quota
  i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
  clk: samsung: Mark top ISP and CAM clocks on Exynos542x as critical
  usblp: poison URBs upon disconnect
  serial: 8250: Fix max baud limit in generic 8250 port
  dm mpath: switch paths in dm_blk_ioctl() code path
  PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only 
register
  ps3disk: use the default segment boundary
  vfio/pci: fix memory leaks in alloc_perm_bits()
  RDMA/mlx5: Add init2init as a modify command
  m68k/PCI: Fix a memory leak in an error handling path
  gpio: dwapb: Call acpi_gpiochip_free_interrupts() on GPIO chip de-registration
  mfd: wm8994: Fix driver operation if loaded as modules
  scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
  clk: clk-flexgen: fix clock-critical handling
  powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 
events run
  nfsd: Fix svc_xprt refcnt leak when setup callback client failed
  PCI: vmd: Filter resource type bits from shadow register
  powerpc/crashkernel: Take "mem=" option into account
  pwm: img: Call pm_runtime_put() in pm_runtime_get_sync() failed case
  yam: fix possible memory leak in yam_init_driver
  NTB: ntb_pingpong: Choose doorbells based on port number
  NTB: Fix the default port and peer numbers for legacy drivers
  mksysmap: Fix the mismatch of '.L' symbols in System.map
  apparmor: fix introspection of of task mode for unconfined tasks
  ASoC: meson: add missing free_irq() in error path
  scsi: sr: Fix sr_probe() missing deallocate of device minor
  scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM
  x86/purgatory: Disable various profiling and sanitizing options
  staging: greybus: fix a missing-check bug in gb_lights_light_config()
  arm64: dts: mt8173: fix unit name warnings
  scsi: qedi: Do not flush offload work if ARP not resolved
  ARM: dts: sun8i-h2-plus-bananapi-m2-zero: Fix led polarity
  gpio: dwapb: Append MODULE_ALIAS for platform driver
  scsi: qedf: Fix crash when MFW calls for protocol stats while function is 
still probing
  pinctrl: rza1: Fix wrong array assignment of rza1l_swio_entries
  firmware: qcom_scm: fix bogous abuse of dma-direct internals
  staging: gasket: Fix mapping refcnt leak when put attribute fails
  staging: gasket: Fix mapping refcnt leak when register/store fails
  ALSA: usb-audio: Improve frames size computation
  ALSA: usb-audio: Fix racy list management in output queue
  s390/qdio: put thinint indicator after early error
  slimbus: ngd: get drvdata from correct device
  thermal/drivers/ti-soc-thermal: Avoid dereferencing ERR_PTR
  usb: dwc3: gadget: Properly handle failed kick_transfer
  staging: sm750fb: add missing case while setting FB_VISUAL
  PCI: v3-semi: Fix a memory leak in 

[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1854485

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Released
Status in nvidia-settings source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the README.
    Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast
    extensions.For more details, see the "Configuring SLI and Multi-GPU
    

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1215411

Title:
  libcpupower.so is not installed from linux-tools

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Invalid
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: makedumpfile (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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/1800873

Title:
  Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
  line

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in makedumpfile source package in Focal:
  Confirmed
Status in makedumpfile source package in Groovy:
  Confirmed

Bug description:
  Currently kdump has an useful option to append parameters to the kdump
  kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a
  reciprocal option which users could use to remove parameters without
  needing to rewrite the whole line.

  The option name proposed here is KDUMP_CMDLINE_REMOVE, which would
  tentatively "sed"-out the options from the kernel command-line before
  appending the new ones from KDUMP_CMDLINE_APPEND.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800873/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1804533] Re: xen hibernation support for linux-aws (bionic+)

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws (Ubuntu Eoan)
   Status: New => Won't Fix

-- 
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/1804533

Title:
  xen hibernation support for linux-aws (bionic+)

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws source package in Cosmic:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Released
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-aws source package in Focal:
  New

Bug description:
  AWS-specific xen hibernation support (as is already supported in
  linux-aws Xenial and Trusty) has been ported to linux-aws Bionic by
  the Amazon team.

  Patches to be applied to linux-aws-bionic:

  UBUNTU: SAUCE [aws] x86/xen: Introduce new function to map 
HYPERVISOR_shared_info on
  UBUNTU: SAUCE [aws] x86/xen: add system core suspend and resume callbacks
  UBUNTU: SAUCE [aws] xen-netfront: add callbacks for PM suspend and 
hibernation support
  UBUNTU: SAUCE [aws] xen-time-introduce-xen_-save-restore-_steal_clock
  UBUNTU: SAUCE [aws] x86/xen: save and restore steal clock
  UBUNTU: SAUCE [aws] xen/events: add xen_shutdown_pirqs helper function
  UBUNTU: SAUCE [aws] x86/xen: close event channels for PIRQs in system core 
suspend
  UBUNTU: SAUCE [aws] PM / hibernate: update the resume offset on 
SNAPSHOT_SET_SWAP_AREA

  This patch set passes simple hibernation smoke-testing on an instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1804533/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1861243] Re: Revert temporary md/raid0 layout patch

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861243

Title:
  Revert temporary md/raid0 layout patch

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  A "temporary" patch was applied to Xenial, Bionic, Disco and Eoan as
  part of the fix for: https://bugs.launchpad.net/bugs/1850540:

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/xenial/commit/?id=faf36efcc6d6bf50c9b5a2a6d7f0efdae296e8a6

  "UBUNTU: SAUCE: md/raid0: Use kernel specific layout" (this uses by
  default the layout for multi-zone md RAID0 arrays that the kernel was
  using before / instead of failing to assemble those and require the
  user to make a choice).

  Once the rollout of a fixed user-space and maybe some grace period we
  should revert this to be back behaving like upstream does. This bug is
  for tracking the reversion of the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861243/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-gcp (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
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/1840488

Title:
  Disable Bluetooth in cloud kernels

Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-gcp package in Ubuntu:
  Triaged
Status in linux-gke-4.15 package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Triaged
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Triaged
Status in linux-gke-4.15 source package in Xenial:
  Invalid
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  Triaged
Status in linux-aws source package in Bionic:
  Triaged
Status in linux-gcp source package in Bionic:
  Triaged
Status in linux-gke-4.15 source package in Bionic:
  Triaged
Status in linux-gke-5.0 source package in Bionic:
  Triaged
Status in linux-oracle source package in Bionic:
  Triaged
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-gke-4.15 source package in Disco:
  Invalid
Status in linux-gke-5.0 source package in Disco:
  Invalid
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-gke-4.15 source package in Eoan:
  Invalid
Status in linux-gke-5.0 source package in Eoan:
  Invalid
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  Some cloud-focused kernels have CONFIG_BT enabled but cloud instances
  shouldn't need bluetooth support. Disabling the bluetooth subsystem
  reduces the amount of security-sensitive code we have to worry about
  in the cloud kernels and also has the nice side effect of minimizing
  build times and kernel sizes.

  The cloud kernels known to have bluetooth enabled include:

  * [B/D/E] linux-aws (arm64 only)
  * [X/B/D/E] linux-gcp
  * [B] linux-gke-4.15
  * [B] linux-gke-5.0
  * [X/B/D/E] linux-oracle

  [Test Case]

  1. Install patched kernel and reboot into it
  2. Ensure that the following command does NOT display any output:
     $ grep CONFIG_BT=[my] /boot/config-$(uname -r)

  [Regression Potential]

  There could be an unexpected dependence on bluetooth within one of the
  clouds but I think it is highly unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842473] Re: sched_getattr will return EFBIG

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842473

Title:
  sched_getattr will return EFBIG

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  With the introduction of utilization clamps interface on
  sched_[sg]etattr, sched_getattr will fail when used with the previous
  smaller struct sched_attr. And instead of using E2BIG as documented,
  it also ends up using EFBIG instead.

  The interface change currently breaks userspace on 5.3 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842473/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-oracle (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
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/1840488

Title:
  Disable Bluetooth in cloud kernels

Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-gcp package in Ubuntu:
  Triaged
Status in linux-gke-4.15 package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Triaged
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Triaged
Status in linux-gke-4.15 source package in Xenial:
  Invalid
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  Triaged
Status in linux-aws source package in Bionic:
  Triaged
Status in linux-gcp source package in Bionic:
  Triaged
Status in linux-gke-4.15 source package in Bionic:
  Triaged
Status in linux-gke-5.0 source package in Bionic:
  Triaged
Status in linux-oracle source package in Bionic:
  Triaged
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-gke-4.15 source package in Disco:
  Invalid
Status in linux-gke-5.0 source package in Disco:
  Invalid
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-gke-4.15 source package in Eoan:
  Invalid
Status in linux-gke-5.0 source package in Eoan:
  Invalid
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  Some cloud-focused kernels have CONFIG_BT enabled but cloud instances
  shouldn't need bluetooth support. Disabling the bluetooth subsystem
  reduces the amount of security-sensitive code we have to worry about
  in the cloud kernels and also has the nice side effect of minimizing
  build times and kernel sizes.

  The cloud kernels known to have bluetooth enabled include:

  * [B/D/E] linux-aws (arm64 only)
  * [X/B/D/E] linux-gcp
  * [B] linux-gke-4.15
  * [B] linux-gke-5.0
  * [X/B/D/E] linux-oracle

  [Test Case]

  1. Install patched kernel and reboot into it
  2. Ensure that the following command does NOT display any output:
     $ grep CONFIG_BT=[my] /boot/config-$(uname -r)

  [Regression Potential]

  There could be an unexpected dependence on bluetooth within one of the
  clouds but I think it is highly unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux-aws (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
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/1840488

Title:
  Disable Bluetooth in cloud kernels

Status in linux-aws package in Ubuntu:
  Triaged
Status in linux-gcp package in Ubuntu:
  Triaged
Status in linux-gke-4.15 package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Triaged
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Triaged
Status in linux-gke-4.15 source package in Xenial:
  Invalid
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  Triaged
Status in linux-aws source package in Bionic:
  Triaged
Status in linux-gcp source package in Bionic:
  Triaged
Status in linux-gke-4.15 source package in Bionic:
  Triaged
Status in linux-gke-5.0 source package in Bionic:
  Triaged
Status in linux-oracle source package in Bionic:
  Triaged
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-gcp source package in Disco:
  Won't Fix
Status in linux-gke-4.15 source package in Disco:
  Invalid
Status in linux-gke-5.0 source package in Disco:
  Invalid
Status in linux-oracle source package in Disco:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-gcp source package in Eoan:
  Won't Fix
Status in linux-gke-4.15 source package in Eoan:
  Invalid
Status in linux-gke-5.0 source package in Eoan:
  Invalid
Status in linux-oracle source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  Some cloud-focused kernels have CONFIG_BT enabled but cloud instances
  shouldn't need bluetooth support. Disabling the bluetooth subsystem
  reduces the amount of security-sensitive code we have to worry about
  in the cloud kernels and also has the nice side effect of minimizing
  build times and kernel sizes.

  The cloud kernels known to have bluetooth enabled include:

  * [B/D/E] linux-aws (arm64 only)
  * [X/B/D/E] linux-gcp
  * [B] linux-gke-4.15
  * [B] linux-gke-5.0
  * [X/B/D/E] linux-oracle

  [Test Case]

  1. Install patched kernel and reboot into it
  2. Ensure that the following command does NOT display any output:
     $ grep CONFIG_BT=[my] /boot/config-$(uname -r)

  [Regression Potential]

  There could be an unexpected dependence on bluetooth within one of the
  clouds but I think it is highly unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1853969] Re: usbhid 1-3.1:1.1: can't add hid device: -32

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853969

Title:
  usbhid 1-3.1:1.1: can't add hid device: -32

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  A keyboard behind an USB hub no longer works after upgrading to Eoan
  5.3.

  Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
  2019 x86_64 x86_64 x86_64 GNU/Linux

  Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB 
device number 8 using xhci_hcd
  Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found, 
idVendor=058f, idProduct=6254, bcdDevice= 1.00
  Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
  Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
  Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB 
device number 9 using xhci_hcd
  Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
  Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device 
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
  Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite 
USB Keyboard
  Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
  Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB 
Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
  Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic 
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite 
USB Keyboard] on usb-:00:14.0-3.1/input0
  Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid 
device: -32
  Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1 
failed with error -32
  Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB 
device number 10 using xhci_hcd
  Nov 18 07:48:35 gollum kernel: [   10.026058] usb 1-3.2: New USB device 
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
  Nov 18 07:48:35 gollum kernel: [   10.026060] usb 1-3.2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Nov 18 07:48:35 gollum kernel: [   10.026061] usb 1-3.2: Product: Laser Mouse
  Nov 18 07:48:35 gollum kernel: [   10.026061] usb 1-3.2: Manufacturer: Mouse
  Nov 18 07:48:35 gollum kernel: [   10.031943] input: Mouse Laser Mouse as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
  Nov 18 07:48:35 gollum kernel: [   10.032031] hid-generic 
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on 
usb-:00:14.0-3.2/input0
  Nov 18 07:48:35 gollum kernel: [   10.112241] usb 1-3.3: new high-speed USB 
device number 11 using xhci_hcd
  Nov 18 07:48:36 gollum kernel: [   10.457643] usb 1-3.3: New USB device 
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
  Nov 18 07:48:36 gollum kernel: [   10.457649] usb 1-3.3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=2
  Nov 18 07:48:36 gollum kernel: [   10.457652] usb 1-3.3: SerialNumber: 
D1C29B20

  Preliminary investigation shows that the following commit seems to cause 
issues:
  ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juergh 3461 F pulseaudio
   /dev/snd/controlC0:  juergh 3461 F pulseaudio
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2017-05-25 (1050 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Pavilion Desktop PC 570-p0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file 
drivers/usb/* +pt" hid.debug=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.183.5
  Tags:  eoan
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: Upgraded to eoan on 

[Kernel-packages] [Bug 1879196] Re: 'shifted' (shiftfs) FS mount became inconsistent with host FS; resolved by dropping caches

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879196

Title:
  'shifted' (shiftfs) FS mount became inconsistent with host FS;
  resolved by dropping caches

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Triaged

Bug description:
  On Ubuntu 20.04 with linux-image-5.4.0-30-generic from the Canonical
  Kernel Team's proposed PPA, I ran into the following problem with
  using a shiftfs 'shifted' ext4 FS mount inside a LXD container.

  On the host, I created a file (in emacs) that was in no way special
  (single line text file):

   james@malefic:~/projects/ethq/deb$ stat 
ethq-0.6.1~git2020517/debian/ethq.install
File: ethq-0.6.1~git2020517/debian/ethq.install
Size: 15  Blocks: 8  IO Block: 4096   regular file
  Device: fd01h/64769dInode: 7085913 Links: 1
  Access: (0664/-rw-rw-r--)  Uid: ( 1000/   james)   Gid: ( 1000/   james)
  Access: 2020-05-17 22:48:36.274528130 +0100
  Modify: 2020-05-17 22:37:17.676232019 +0100
  Change: 2020-05-17 22:37:17.676232019 +0100
   Birth: -
   james@malefic:~/projects/ethq/deb$ stat ethq-0.6.1~git2020517/debian/rules

  But in the container, I saw this:

  ubuntu@ethq-build:~/ethq/deb/ethq-0.6.1~git2020517$ ls -l debian/
  ls: cannot access 'debian/ethq.install': No such file or directory
  total 20
  -rw-rw-r-- 1 ubuntu ubuntu 150 May 17 21:25 changelog
  -rw-r--r-- 1 ubuntu ubuntu   2 May 17 21:36 compat
  -rw-rw-r-- 1 ubuntu ubuntu 514 May 17 21:14 control
  -rw-rw-r-- 1 ubuntu ubuntu 720 May 17 21:20 copyright
  -? ? ?  ??? ethq.install
  -rwxr-xr-x 1 ubuntu ubuntu  30 May 17 21:35 rules
  ubuntu@ethq-build:~/ethq/deb/ethq-0.6.1~git2020517$ stat debian/ethq.install
  stat: cannot stat 'debian/ethq.install': No such file or directory
  ubuntu@ethq-build:~/ethq/deb/ethq-0.6.1~git2020517$ 

  On a suggestion from Stephane Graber, I tried running:

echo 3 > /proc/sys/vm/drop_caches

  Which seemed to resolve the problem:

  ubuntu@ethq-build:~/ethq/deb/ethq-0.6.1~git2020517$ stat debian/ethq.install
File: 'debian/ethq.install'
Size: 15  Blocks: 8  IO Block: 4096   regular file
  Device: fd01h/64769dInode: 7085913 Links: 1
  Access: (0664/-rw-rw-r--)  Uid: ( 1000/  ubuntu)   Gid: ( 1000/  ubuntu)
  Access: 2020-05-17 21:48:36.274528130 +
  Modify: 2020-05-17 21:37:17.676232019 +
  Change: 2020-05-17 21:37:17.676232019 +
   Birth: -
  ubuntu@ethq-build:~/ethq/deb/ethq-0.6.1~git2020517$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879196/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1867916

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of bcache who manually specified a block size
     greater than the page size when creating the device
     with 'make-bcache' started to hit a kernel BUG/oops
     after kernel upgrades.  (This is not widely used.)

   * The issue has been exposed with commit ad6bf88a6c19
     ("block: fix an integer overflow in logical block size")
     because it increased the range of values accepted as
     logical block size, which used to overflow to zero,
     and thus receive a default of 512 via block layer.

   * The issue existed previously, but with fewer values
     exposed (e.g. 8k, 16k, 32k); the regression reports
     happened with larger values (512k) for RAID stripes.

  [Fix]

   * The upstream commit dcacbc1242c7 ("bcache: check and
     adjust logical block size for backing devices") checks
     the block size and adjusts it if needed, to the value
     of the underlying device's logical block size.

   * It is merged as of v5.8-rcN, and sent to v5.7 stable.

  [Test Case]

   * Run make-bcache with block size greater than page size.
     $ sudo make-bcache --bdev $DEV --block 8k

   * Expected results: bcache device registered; no BUG/oops.
   * Details steps on comment #43.

  [Regression Potential]

   * Restricted to users who specify a bcache block size
     greater than page size.

   * Regressions could theoretically manifest on bcache
     device probe/register, if the underlying device's
     logical block size for whatever triggers issues not
     seen previously with the overflow/default 512 bytes.

  [Other Info]

   * Unstable has the patch on both master/master-5.7.
   * Groovy should get it on rebase.

  [Original Bug Description]
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does 
not boot any longer. It always crashes during boot with a kernel panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw 

[Kernel-packages] [Bug 1873074] Re: kernel panic hit by kube-proxy iptables-save/restore caused by aufs

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873074

Title:
  kernel panic hit by kube-proxy iptables-save/restore caused by aufs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Systems with aufs mounts are vulnerable to a kernel BUG(),
     which can turn into a panic/crash if panic_on_oops is set.

   * It is exploitable by unprivileged local users; and also
     remote access operations (e.g., web server) potentially.

   * This issue has also manifested in Kubernetes deployments
     with a kernel panic in iptables-save or iptables-restore
     after a few weeks of uptime, without user interaction.

   * Usually all Kubernetes worker nodes hit the issue around
     the same time.

  [Fix]

   * The issue is fixed with 2 patches in aufs4-linux.git:
   - 515a586eeef3 aufs: do not call i_readcount_inc()
   - f10aea57d39d aufs: bugfix, IMA i_readcount

   * The first addresses the issue, and the second addresses a
     regression in the aufs feature to change RW branches to RO.

   * The kernel v5.3 aufs patches had an equivalent fix to the
     second patch, which is present in the Focal aufs patchset
     (and on ubuntu-unstable/master & /master-5.8 on 20200629)

   - 1d26f910c53f aufs: for v5.3-rc1, maintain i_readcount
 (in aufs5-linux.git)

  [Test Case]

   * Repeatedly open/close the same file in read-only mode in
     aufs (UINT_MAX times, to overflow a signed int back to 0.)

   * Alternatively, monitor the underlying filesystems's file
     inode.i_readcount over several open/close system calls.
     (should not monotonically increase; rather, return to 0.)

  [Regression Potential]

   * This changes the core path that aufs opens files, so there
     is a risk of regression; however, the fix changes aufs for
     how other filesystems work, so this generally is OK to do.
     In any case, most regressions would manifest in open() or
     close() (where the VFS handles/checks inode.i_readcount.)

   * The aufs maintainer has access to an internal test-suite
     used to validate aufs changes, used to identify the first
     regression (in the branch RW/RO mode change), and then to
     validate/publish the patches upstream; should be good now.

   * This has also been tested with 'stress-ng --class filesystem'
     and with 'xfstests -overlay' (patch to use aufs vs overlayfs)
     on Xenial/Bionic/Focal (-proposed vs. -proposed + patches).
     No regressions observed in stress-ng/xfstests log or dmesg.

  [Other Info]

   * Applied on Unstable (branches master and master-5.8)
   * Not required on Groovy (still 5.4; should sync from Unstable)
   * Required on LTS releases: Bionic and Focal and Xenial.
   * Required on other releases: Disco and Eoan (for custom kernels)

  [Original Bug Description]

  Problem Report:
  --

  An user reported several nodes in their Kubernetes clusters
  hit a kernel panic at about the same time, and periodically
  (usually 35 days of uptime, and in same order nodes booted.)

  The kernel panics message/stack trace are consistent across
  nodes, in __fput() by iptables-save/restore from kube-proxy.

  Example:

  """
  [3016161.866702] kernel BUG at .../include/linux/fs.h:2583!
  [3016161.866704] invalid opcode:  [#1] SMP
  ...
  [3016161.866780] CPU: 40 PID: 33068 Comm: iptables-restor Tainted: P OE 
4.4.0-133-generic #159-Ubuntu
  ...
  [3016161.866786] RIP: 0010:[...] [...] __fput+0x223/0x230
  ...
  [3016161.866818] Call Trace:
  [3016161.866823] [...] fput+0xe/0x10
  [3016161.866827] [...] task_work_run+0x86/0xb0
  [3016161.866831] [...] exit_to_usermode_loop+0xc2/0xd0
  [3016161.866833] [...] syscall_return_slowpath+0x4e/0x60
  [3016161.866839] [...] int_ret_from_sys_call+0x25/0x9f
  """

  (uptime: 3016161 seconds / (24*60*60) = 34.90 days)

  They have provided a crashdump (privately available) used
  for analysis later in this bug report.

  Note: the root cause turns out to be independent of K8s,
  as explained in the Root Cause section.

  Related Report:
  --

  This behavior matches this public bug of another user:
  https://github.com/kubernetes/kubernetes/issues/70229

  """
  I have several machines happen kernel panic，and these
  machine have same dump trace like below:

  KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-104-generic
  ...
  PANIC: "kernel BUG at .../include/linux/fs.h:2582!"
  ...
  COMMAND: "iptables-restor"
  ...
  

[Kernel-packages] [Bug 1864527] Re: CPU0 is busy after S3 in Dell Precision 3530

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864527

Title:
  CPU0 is busy after S3 in Dell Precision 3530

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Released

Bug description:
  CPU0 (and sometimes other cores too) is not entering C10 half of the
  time when system is idle. "top" shows a touchpad driver takes 5%~6% of
  CPU usage, and "/proc/interrupts" reveals considerable interrupts from
  the touchpad device. This results in additional 4~5 watt power
  consumption.

  This anomaly can be workarounded by simply touching the touchpad - in
  other words, it is more visible when using a USB mouse.

  This can be fixed by a kernel 5.5 commit 52cf93e63ee6 which is included in 
bionic (4.15) and focal kernel (5.4) but not in eoan (5.3).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexhung   3397 F pulseaudio
   /dev/snd/pcmC0D0p:   alexhung   3397 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-10-29 (118 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Precision 3530
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=b0c947ea-9aa0-4ca2-a634-7b925900c129 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.6.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.6.4:bd01/30/2018:svnDellInc.:pnPrecision3530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3530
  dmi.product.sku: 0820
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864527/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884766

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  general protection fault:  [#1] SMP PTI
  ...
  RIP: 0010:__release_sock+0x54/0xe0
  ...
  Call Trace:
   release_sock+0x30/0xa0
   af_alg_accept+0x122/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884766/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886744

Title:
  Enable Quectel EG95 LTE modem [2c7c:0195]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  No modems were found by `mmcli -L`

  [Fix]
  Below 2 commits are required to enable this chip.
  https://lkml.org/lkml/2020/7/7/200
  https://lkml.org/lkml/2020/7/7/199

  [Test]
  Verified on the machine with EG95 LTE modem

  [Regression Potential]
  Low, just adding IDs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1886744/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp