date:20200721

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Computer hung when resuming from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  The computer seemingly hung when resuming from suspend and failed to
  show the login screen. Switching to Ctr+Alt+F2 was showing a lot of
  disk errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vadi   3100 F pulseaudio
   /dev/snd/controlC1:  vadi   3100 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed May 20 07:01:51 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2979 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1879017] Re: dd caused systemd-udevd call trace

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  dd caused systemd-udevd call trace

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using dd to copy an image onto sdcard seems to cause a kernel stack
  trace.  dd seems to hang.

  [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 
seconds.
  [ 3747.220652]   Tainted: P  IOE 5.4.0-29-generic #33-Ubuntu
  [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   
 
  [ 3747.220656] systemd-udevd   D0  2451  1 0x4124
  [ 3747.220660] Call Trace:
  [ 3747.220670]  __schedule+0x2e3/0x740
  [ 3747.220673]  schedule+0x42/0xb0
  [ 3747.220675]  schedule_preempt_disabled+0xe/0x10
  [ 3747.220678]  __mutex_lock.isra.0+0x182/0x4f0
  [ 3747.220683]  ? exact_lock+0x11/0x20
  [ 3747.220685]  __mutex_lock_slowpath+0x13/0x20
  [ 3747.220687]  mutex_lock+0x2e/0x40
  [ 3747.220692]  __blkdev_get+0x78/0x550
  [ 3747.220694]  blkdev_get+0x3d/0x140
  [ 3747.220697]  ? blkdev_get_by_dev+0x50/0x50
  [ 3747.220699]  blkdev_open+0x8f/0xa0
  [ 3747.220704]  do_dentry_open+0x143/0x3a0
  [ 3747.220706]  vfs_open+0x2d/0x30
  [ 3747.220710]  do_last+0x194/0x900
  [ 3747.220713]  path_openat+0x8d/0x290
  [ 3747.220716]  do_filp_open+0x91/0x100
  [ 3747.220720]  ? __alloc_fd+0x46/0x150
  [ 3747.220722]  do_sys_open+0x17e/0x290
  [ 3747.220724]  __x64_sys_openat+0x20/0x30
  [ 3747.220729]  do_syscall_64+0x57/0x190
  [ 3747.220735]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 3747.220738] RIP: 0033:0x7f18e48a1d1b
  [ 3747.220745] Code: Bad RIP value.
  [ 3747.220746] RSP: 002b:7ffd19e936a0 EFLAGS: 0246 ORIG_RAX: 
0101
  [ 3747.220748] RAX: ffda RBX: 7ffd19e937b0 RCX: 
7f18e48a1d1b
  [ 3747.220749] RDX: 000a0800 RSI: 558d7f09f470 RDI: 
ff9c
  [ 3747.220750] RBP: 558d7f09f470 R08: 558d7d4740c0 R09: 

  [ 3747.220751] R10:  R11: 0246 R12: 
000a0800
  [ 3747.220752] R13: 558d7f0b2920 R14: 7ffd19e93778 R15: 
0001

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  js11209 F pulseaudio
   /dev/snd/controlC1:  js11209 F pulseaudio
   /dev/snd/controlC0:  js11209 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Fri May 15 22:44:18 2020
  InstallationDate: Installed on 2020-02-02 (103 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  MachineType: Dell Inc. Precision WorkStation T7500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 
elevator=deadline splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0D881F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd10/15/2018:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.

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

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

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

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

apport-collect 1887914

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

Title:
  Partial freeze if booting with USB-C dock attached

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub
  (a kind of dock) already attached, the machine crashes after entering
  password into the graphical login interface. More precisely the login
  does not complete (in a reasonable time frame) and I cannot switch to
  another virtual terminal. Some menus can be selected, but there is no
  action (e.g. reboot) and I have to do a hard shutdown (pressing the
  power button for 4 sec.). The log files show a kernel oops. When
  attaching the dock after login the system seems to work normally.

  I do have the latest displaylink drivers installed
  (www.displaylink.com).

  Attached is a log file snippet.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-03-25 (483 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

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

Can confirm the patched kernel at
https://launchpad.net/~lizthegrey/+archive/ubuntu/kernel/+build/19618859
works.

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1887914] Re: Partial freeze if booting with USB-C dock attached

2020-07-21 Thread Daniel van Vugt

I just realized this is the USB-C logic crashing in the kernel:

Jul 21 20:31:20 volfe kernel: Call Trace:
Jul 21 20:31:20 volfe kernel:  ucsi_altmode_update_active+0xab/0xf0 [typec_ucsi]
Jul 21 20:31:20 volfe kernel:  ucsi_register_port+0x2c6/0x3c0 [typec_ucsi]
Jul 21 20:31:20 volfe kernel:  ucsi_init+0xd2/0x1c0 [typec_ucsi]
Jul 21 20:31:20 volfe kernel:  process_one_work+0x1eb/0x3b0
Jul 21 20:31:20 volfe kernel:  worker_thread+0x4d/0x400
Jul 21 20:31:20 volfe kernel:  kthread+0x104/0x140
Jul 21 20:31:20 volfe kernel:  ? process_one_work+0x3b0/0x3b0
Jul 21 20:31:20 volfe kernel:  ? kthread_park+0x90/0x90
Jul 21 20:31:20 volfe kernel:  ret_from_fork+0x35/0x40

So it looks like a kernel bug.

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

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

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

Title:
  Partial freeze if booting with USB-C dock attached

Status in linux package in Ubuntu:
  New

Bug description:
  When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub
  (a kind of dock) already attached, the machine crashes after entering
  password into the graphical login interface. More precisely the login
  does not complete (in a reasonable time frame) and I cannot switch to
  another virtual terminal. Some menus can be selected, but there is no
  action (e.g. reboot) and I have to do a hard shutdown (pressing the
  power button for 4 sec.). The log files show a kernel oops. When
  attaching the dock after login the system seems to work normally.

  I do have the latest displaylink drivers installed
  (www.displaylink.com).

  Attached is a log file snippet.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-03-25 (483 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1887724] Re: [amdgpu] Xorg freeze

2020-07-21 Thread Daniel van Vugt

You would remove:

  blacklist ath10k_pci

from /etc/modprobe.d/blacklist.conf and then reboot.

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

Title:
  [amdgpu] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random freezing-- different freezing every time. I switched GUIs from
  Gnome to Cinnamon and it seems to freeze less, but still averaging
  about once a day. I cannot reproduce, is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Wed Jul 15 15:44:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [1028:0884]
  InstallationDate: Installed on 2020-06-04 (40 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=0ed970bf-fd17-4242-8a3e-5c1224ed5b72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 02YPPF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn02YPPF:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Dell Inc.
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  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/linux/+bug/1887724/+subscriptions

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

[Kernel-packages] [Bug 1887914] [NEW] Partial freeze if booting with USB-C dock attached

You have been subscribed to a public bug:

When booting my Lenovo E490 with the Lenovo Powered USB-C Travel Hub (a
kind of dock) already attached, the machine crashes after entering
password into the graphical login interface. More precisely the login
does not complete (in a reasonable time frame) and I cannot switch to
another virtual terminal. Some menus can be selected, but there is no
action (e.g. reboot) and I have to do a hard shutdown (pressing the
power button for 4 sec.). The log files show a kernel oops. When
attaching the dock after login the system seems to work normally.

I do have the latest displaylink drivers installed
(www.displaylink.com).

Attached is a log file snippet.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-03-25 (483 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: mutter 3.36.3-0ubuntu0.20.04.1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Tags:  focal
Uname: Linux 5.4.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev remote sambashare sudo wireshark
_MarkForUpload: True

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


** Tags: apport-collected focal
-- 
Partial freeze if booting with USB-C dock attached
https://bugs.launchpad.net/bugs/1887914
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-21 Thread Daniel van Vugt

The answer to your question is comment #15. :)

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-21 Thread Luis Alberto Pabón

A workaround, if you really need auto-login, is to install lightdm (at
this point still choose gdm3), enable auto-login via gnome settings,
then switch to lightdm (sudo dpkg-reconfigure gdm3). Not sure why it
autologins but it does. Can't lock the gnome session however as not
using gdm anymore.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in grub2 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

  PPA:

[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-21 Thread Travis

What's the status for Ubuntu Focal?

How can I help to emphasize the importance of backporting the fix to the
stable release?

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2020-07-21 Thread Diego

It also happens with driver nvidia-340.108 in elementary OS 5.1.6 Hera.
In my case the error happens with VLC when trying to open the Hikvision rstp 
streaming (H264), the error lines run fast but stop when closing VLC.

I leave some lines of the error.


VLC media player 3.0.11 Vetinari (revision 3.0.11-0-gdc0c5ced72)
[564386f97a00] main libvlc: Ejecutar vlc con la interfaz predeterminada. 
Use «cvlc» para usar vlc sin interfaz.
Qt: Session management error: None of the authentication protocols specified 
are supported
QApplication: invalid style override 'adwaita' passed, ignoring it.
Available styles: Breeze, Windows, Fusion
[564386f8d3c0] main playlist: playlist is empty
[7fc12c04aee0] main decoder error: buffer deadlock prevented
MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds 
the client's buffer size (25).  70154 bytes of trailing data will be 
dropped!
MultiFramedRTPSource::doGetNextFrame1(): The total received frame size exceeds 
the client's buffer size (50).  100677 bytes of trailing data will be 
dropped!
[h264 @ 0x7fc13000a4e0] illegal memory management control operation 13
[7fc1340020b0] egl_x11 gl error: cannot select OpenGL API
[7fc12c04aee0] avcodec decoder: Using NVIDIA VDPAU Driver Shared Library  
340.108  Wed Dec 11 14:31:24 PST 2019 for hardware decoding
[h264 @ 0x7fc13000a4e0] Failed setup for format vdpau: hwaccel initialisation 
returned error.
[7fc12c04aee0] avcodec decoder error: existing hardware acceleration cannot 
be reused
[h264 @ 0x7fc13000a4e0] top block unavailable for requested intra mode -1
[h264 @ 0x7fc13000a4e0] error while decoding MB 2 0, bytestream 668
[h264 @ 0x7fc130026900] Missing reference picture, default is 65530
[h264 @ 0x7fc130026900] Missing reference picture, default is 65530
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65526
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65528
[h264 @ 0x7fc1300a6aa0] cabac_init_idc 3 overflow
[h264 @ 0x7fc1300a6aa0] decode_slice_header error
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65530
[h264 @ 0x7fc13000a4e0] illegal modification_of_pic_nums_idc 6
[h264 @ 0x7fc13000a4e0] decode_slice_header error
[h264 @ 0x7fc130026900] Missing reference picture, default is 65531
[h264 @ 0x7fc130026900] Missing reference picture, default is 65531
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532
[h264 @ 0x7fc13002dec0] Missing reference picture, default is 65532
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534
[h264 @ 0x7fc13008ab20] Missing reference picture, default is 65534
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536
[h264 @ 0x7fc1300a6aa0] Missing reference picture, default is 65536
[h264 @ 0x7fc13000a4e0] cabac_init_idc 3 overflow
[h264 @ 0x7fc13000a4e0] decode_slice_header error
[7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width
[7fc138078d00] freetype spu text error: LayoutParagraph(): Invalid max width
[h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538
[h264 @ 0x7fc13000a4e0] Missing reference picture, default is 65538
[h264 @ 0x7fc130026900] reference count overflow
[h264 @ 0x7fc130026900] decode_slice_header error

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video

Re: [Kernel-packages] [Bug 1879334] Re: Desktop Activities - first key typed is repeated 21 times

2020-07-21 Thread buchs

Yes, any key pressed was repeated.

On Mon, Jul 20, 2020 at 11:30 PM Kai-Heng Feng <1879...@bugs.launchpad.net>
wrote:

> Does any key other than "A" has the issue?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1879334
>
> Title:
>   Desktop Activities - first key typed is repeated 21 times
>
> Status in linux package in Ubuntu:
>   Expired
>
> Bug description:
>   Pretty simple scenario. I often press the Super key and then start
>   typing a command name. Within the last two weeks (I stay up to date on
>   any updates to 18.04), when I press the first key it gets repeated a
>   total of 21 times. It is only the first key. If I press backspace or
>   Ctl-u to erase the entries, then there is no problem. It seems that
>   this problem went from being intermittent to being constant now.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879334/+subscriptions
>

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

Title:
  Desktop Activities - first key typed is repeated 21 times

Status in linux package in Ubuntu:
  Expired

Bug description:
  Pretty simple scenario. I often press the Super key and then start
  typing a command name. Within the last two weeks (I stay up to date on
  any updates to 18.04), when I press the first key it gets repeated a
  total of 21 times. It is only the first key. If I press backspace or
  Ctl-u to erase the entries, then there is no problem. It seems that
  this problem went from being intermittent to being constant now.

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

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

[Kernel-packages] [Bug 1888429] Re: Eoan update: upstream stable patchset 2020-07-21

2020-07-21 Thread 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-07-21
  
-upstream stable patchset 2020-07-21
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.19.133, v.5.4.52
+ 
+    from git://git.kernel.org/
+ 
+ KVM: s390: reduce number of IO pins to 1
+ spi: spi-fsl-dspi: Adding shutdown hook
+ spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
+ regmap: fix alignment issue
+ ARM: dts: omap4-droid4: Fix spi configuration and increase rate
+ drm/tegra: hub: Do not enable orphaned window group
+ gpu: host1x: Detach driver on unregister
+ spi: spidev: fix a race between spidev_release and spidev_remove
+ spi: spidev: fix a potential use-after-free in spidev_release()
+ ixgbe: protect ring accesses with READ- and WRITE_ONCE
+ i40e: protect ring accesses with READ- and WRITE_ONCE
+ drm: panel-orientation-quirks: Add quirk for Asus T101HA panel
+ drm: panel-orientation-quirks: Use generic orientation-data for Acer S1003
+ s390/kasan: fix early pgm check handler execution
+ cifs: update ctime and mtime during truncate
+ ARM: imx6: add missing put_device() call in imx6q_suspend_init()
+ scsi: mptscsih: Fix read sense data size
+ usb: dwc3: pci: Fix reference count leak in dwc3_pci_resume_work
+ block: release bip in a right way in error path
+ nvme-rdma: assign completion vector correctly
+ x86/entry: Increase entry_stack size to a full page
+ net: qrtr: Fix an out of bounds read qrtr_endpoint_post()
+ drm/mediatek: Check plane visibility in atomic_update
+ net: cxgb4: fix return error value in t4_prep_fw
+ smsc95xx: check return value of smsc95xx_reset
+ smsc95xx: avoid memory leak in smsc95xx_bind
+ net: hns3: fix use-after-free when doing self test
+ ALSA: compress: fix partial_drain completion state
+ arm64: kgdb: Fix single-step exception handling oops
+ nbd: Fix memory leak in nbd_add_socket
+ cxgb4: fix all-mask IP address comparison
+ bnxt_en: fix NULL dereference in case SR-IOV configuration fails
+ net: macb: mark device wake capable when "magic-packet" property present
+ mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON()
+ ALSA: opl3: fix infoleak in opl3
+ ALSA: hda - let hs_mic be picked ahead of hp_mic
+ ALSA: usb-audio: add quirk for MacroSilicon MS2109
+ KVM: arm64: Fix definition of PAGE_HYP_DEVICE
+ KVM: arm64: Stop clobbering x0 for HVC_SOFT_RESTART
+ KVM: x86: bit 8 of non-leaf PDPEs is not reserved
+ KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode
+ KVM: x86: Mark CR4.TSD as being possibly owned by the guest
+ kallsyms: Refactor kallsyms_show_value() to take cred
+ module: Refactor section attr into bin attribute
+ module: Do not expose section addresses to non-CAP_SYSLOG
+ kprobes: Do not expose probe addresses to non-CAP_SYSLOG
+ bpf: Check correct cred for CAP_SYSLOG in bpf_dump_raw_ok()
+ Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
+ btrfs: fix fatal extent_buffer readahead vs releasepage race
+ drm/radeon: fix double free
+ dm: use noio when sending kobject event
+ ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE
+ ARC: elf: use right ELF_ARCH
+ s390/mm: fix huge pte soft dirty copying
+ perf/x86/rapl: Move RAPL support to common x86 code
+ perf/x86/rapl: Fix RAPL config variable bug
+ UBUNTU: [Packaging] module intel-rapl-perf rename
+ drm: mcde: Fix display initialization problem
+ ASoC: SOF: Intel: add PCI ID for CometLake-S
+ ALSA: hda: Intel: add missing PCI IDs for ICL-H, TGL-H and EKL
+ net: ethernet: mvneta: Fix Serdes configuration for SoCs without comphy
+ net: ethernet: mvneta: Add 2500BaseX support for SoCs without comphy
+ ibmvnic: continue to init in CRQ reset returns H_CLOSED
+ powerpc/kvm/book3s64: Fix kernel crash with nested kvm & DEBUG_VIRTUAL
+ iommu/vt-d: Don't apply gfx quirks to untrusted devices
+ sched/core: Check cpus_mask, not cpus_ptr in __set_cpus_allowed_ptr(), to fix 
mask corruption
+ gpio: pca953x: Override IRQ for one of the expanders on Galileo

[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

This bug was fixed in the package linux-oem - 4.15.0-1093.103

---
linux-oem (4.15.0-1093.103) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1093.103 -proposed tracker (LP: #1887026)

  * [SRU] plug headset won't proper reconfig ouput to it on machine with default
output (LP: #1882248)
- SAUCE: ALSA: hda - let hs_mic be picked ahead of hp_mic

  * Freezing on boot since kernel 4.15.0-72-generic release (LP: #1856387)
- x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode

  [ Ubuntu: 4.15.0-112.113 ]

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount
  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap
  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

  [ Ubuntu: 4.15.0-111.112 ]

  * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999)
  * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461)
- SAUCE: mlxsw: Add missmerged ERR_PTR hunk
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

 -- Kelsey Skunberg   Tue, 14 Jul 2020
12:21:34 -0600

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  In bug 1840239, HPET is disabled on some systems for they caused TSC
  being marked unstable while it is not. This caused an regression as bug
  1851216 that some systems may then hang at early, so a fix cherry picked
  back from v5.3-rc1. However, this fix also introduce yet another
  regression that some other users may hang at boot while PIT is diabled
  in the previous fix.

  [Fix]
  Commit 979923871f69 ("x86/timer: Don't skip PIT setup when APIC is
  disabled or in legacy mode") from v5.6-rc1, also backported to v5.4.19
  and v5.5.3, fixes PIT setup in this case.

  [Test Case]
  Simply boot a patch kernel on systems affected and it shouldn't hang.

  [Regression Potential]
  Low. Stable patch and trivial backport.

  [Other Info]
  The same fix for bug 1851216 was also backported to Disco and Eoan, but
  they were then fixed with this 979923871f69 commit backported in bug
  1866858 and bug 1867051, which pulls v5.4 stable patches into Disco and
  Eoan correspondingly, leaving B/OEM-B the only victims so far.

  == Original Bug Description ==

  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002

[Kernel-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

This bug was fixed in the package linux-oem - 4.15.0-1093.103

---
linux-oem (4.15.0-1093.103) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1093.103 -proposed tracker (LP: #1887026)

  * [SRU] plug headset won't proper reconfig ouput to it on machine with default
output (LP: #1882248)
- SAUCE: ALSA: hda - let hs_mic be picked ahead of hp_mic

  * Freezing on boot since kernel 4.15.0-72-generic release (LP: #1856387)
- x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode

  [ Ubuntu: 4.15.0-112.113 ]

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount
  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap
  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

  [ Ubuntu: 4.15.0-111.112 ]

  * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999)
  * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461)
- SAUCE: mlxsw: Add missmerged ERR_PTR hunk
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

 -- Kelsey Skunberg   Tue, 14 Jul 2020
12:21:34 -0600

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

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

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

[Kernel-packages] [Bug 1886682] Re: linux-image-raspi provides zfs modules only for arm64

This bug was fixed in the package linux-meta-raspi-5.4 - 5.4.0.1015.19

---
linux-meta-raspi-5.4 (5.4.0.1015.19) bionic; urgency=medium

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * Miscellaneous Ubuntu changes
- Revert "UBUNTU: [Packaging] Add transitional packages for raspi2 hwe
  upgrades"

linux-meta-raspi-5.4 (5.4.0.1015.17) bionic; urgency=medium

  * Bump ABI 5.4.0-1015

linux-meta-raspi-5.4 (5.4.0.1014.16) bionic; urgency=medium

  * linux-image-raspi provides zfs modules only for arm64 (LP: #1886682)
- [Packaging] Only provide zfs for arm64

linux-meta-raspi-5.4 (5.4.0.1014.15) bionic; urgency=medium

  * Enable ZFS for Raspberry Pi arm64 (LP: #1884110)
- [Packaging] Remove architecture selector from 'Provides' field

linux-meta-raspi-5.4 (5.4.0.1014.14) bionic; urgency=medium

  * Bump ABI 5.4.0-1014

  * Packaging resync (LP: #1786013)
- [Packaging] resync debian/dkms-versions from main package

  * Enable ZFS for Raspberry Pi arm64 (LP: #1884110)
- [Config] raspi: Enable zfs modules for arm64

  * Add transitionals for hwe raspi2 upgrades (LP: #1885522)
- [Packaging] Add transitional packages for raspi2 hwe upgrades

 -- Juerg Haefliger   Mon, 13 Jul 2020 18:53:29
+0200

** Changed in: linux-meta-raspi-5.4 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  linux-image-raspi provides zfs modules only for arm64

Status in linux-meta-raspi package in Ubuntu:
  Invalid
Status in linux-meta-raspi-5.4 package in Ubuntu:
  Invalid
Status in linux-meta-raspi-5.4 source package in Bionic:
  Fix Released
Status in linux-meta-raspi source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The linux-image-raspi armhf package falsely claims that it provides
  zfs modules. Only the arm64 package actually does.

  [Test Case]

  $ apt-cache show linux-image-raspi | grep -P '^Provides|^Architecture'
  Architecture: armhf
  Provides: wireguard-modules (= 1.0.20200506-1~20.04.1), zfs-modules (= 
0.8.3-1ubuntu12.1)

  [Regression Potential]

  Low.

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

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

[Kernel-packages] [Bug 1888429] [NEW] Eoan update: upstream stable patchset 2020-07-21

2020-07-21 Thread 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-07-21

Ported from the following upstream stable releases:
v4.19.133, v.5.4.52

   from git://git.kernel.org/

KVM: s390: reduce number of IO pins to 1
spi: spi-fsl-dspi: Adding shutdown hook
spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
regmap: fix alignment issue
ARM: dts: omap4-droid4: Fix spi configuration and increase rate
drm/tegra: hub: Do not enable orphaned window group
gpu: host1x: Detach driver on unregister
spi: spidev: fix a race between spidev_release and spidev_remove
spi: spidev: fix a potential use-after-free in spidev_release()
ixgbe: protect ring accesses with READ- and WRITE_ONCE
i40e: protect ring accesses with READ- and WRITE_ONCE
drm: panel-orientation-quirks: Add quirk for Asus T101HA panel
drm: panel-orientation-quirks: Use generic orientation-data for Acer S1003
s390/kasan: fix early pgm check handler execution
cifs: update ctime and mtime during truncate
ARM: imx6: add missing put_device() call in imx6q_suspend_init()
scsi: mptscsih: Fix read sense data size
usb: dwc3: pci: Fix reference count leak in dwc3_pci_resume_work
block: release bip in a right way in error path
nvme-rdma: assign completion vector correctly
x86/entry: Increase entry_stack size to a full page
net: qrtr: Fix an out of bounds read qrtr_endpoint_post()
drm/mediatek: Check plane visibility in atomic_update
net: cxgb4: fix return error value in t4_prep_fw
smsc95xx: check return value of smsc95xx_reset
smsc95xx: avoid memory leak in smsc95xx_bind
net: hns3: fix use-after-free when doing self test
ALSA: compress: fix partial_drain completion state
arm64: kgdb: Fix single-step exception handling oops
nbd: Fix memory leak in nbd_add_socket
cxgb4: fix all-mask IP address comparison
bnxt_en: fix NULL dereference in case SR-IOV configuration fails
net: macb: mark device wake capable when "magic-packet" property present
mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON()
ALSA: opl3: fix infoleak in opl3
ALSA: hda - let hs_mic be picked ahead of hp_mic
ALSA: usb-audio: add quirk for MacroSilicon MS2109
KVM: arm64: Fix definition of PAGE_HYP_DEVICE
KVM: arm64: Stop clobbering x0 for HVC_SOFT_RESTART
KVM: x86: bit 8 of non-leaf PDPEs is not reserved
KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode
KVM: x86: Mark CR4.TSD as being possibly owned by the guest
kallsyms: Refactor kallsyms_show_value() to take cred
module: Refactor section attr into bin attribute
module: Do not expose section addresses to non-CAP_SYSLOG
kprobes: Do not expose probe addresses to non-CAP_SYSLOG
bpf: Check correct cred for CAP_SYSLOG in bpf_dump_raw_ok()
Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
btrfs: fix fatal extent_buffer readahead vs releasepage race
drm/radeon: fix double free
dm: use noio when sending kobject event
ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE
ARC: elf: use right ELF_ARCH
s390/mm: fix huge pte soft dirty copying
perf/x86/rapl: Move RAPL support to common x86 code
perf/x86/rapl: Fix RAPL config variable bug
UBUNTU: [Packaging] module intel-rapl-perf rename
drm: mcde: Fix display initialization problem
ASoC: SOF: Intel: add PCI ID for CometLake-S
ALSA: hda: Intel: add missing PCI IDs for ICL-H, TGL-H and EKL
net: ethernet: mvneta: Fix Serdes configuration for SoCs without comphy
net: ethernet: mvneta: Add 2500BaseX support for SoCs without comphy
ibmvnic: continue to init in CRQ reset returns H_CLOSED
powerpc/kvm/book3s64: Fix kernel crash with nested kvm & DEBUG_VIRTUAL
iommu/vt-d: Don't apply gfx quirks to untrusted devices
sched/core: Check cpus_mask, not cpus_ptr in __set_cpus_allowed_ptr(), to fix 
mask corruption
gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2
gpio: pca953x: Fix GPIO resource leak on Intel Galileo Gen 2
bpf, sockmap: RCU splat with redirect and strparser error or TLS
bpf, sockmap: RCU dereferenced psock may be used outside RCU block
netfilter: ipset: call ip_set_free() instead of kfree()
net: mvneta: fix use of state->speed
net: dsa: microchip: set the correct number of ports
netfilter: conntrack: refetch conntrack after nf_conntrack_update()
perf report TUI: Fix segmentation fault in perf_evsel__hists_browse()
perf intel-pt: Fix PEBS sample for XMM registers
net: hns3: add a missing uninit debugfs when unload driver
RDMA/siw: Fix reporting vendor_part_id
IB/mlx5: Fix 50G per lane indication
net/mlx5: Fix eeprom support for SFP module

[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-21 Thread Brian Murray

Hello Matt, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash

[Kernel-packages] [Bug 1883597] Re: Kernel 4.4.0-184 hangs when issuing tc qdisc command

2020-07-21 Thread Rune Torgersen

Bug present in 4.4.0-186.

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

Title:
  Kernel 4.4.0-184 hangs when issuing tc qdisc command

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 
25mbit" causes CPU lockup
  (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394])

  This does not occur on 4.4.0.179 or earlier.
  Happens on both a intel i40e driver and ixgbe.
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Jun 15 14:52 seq
   crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a
  InstallationDate: Installed on 2019-02-22 (479 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd 
   Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro SSG-6029P-E1CR12L
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic 
root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 
nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M
  ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-184-generic N/A
   linux-backports-modules-4.4.0-184-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-184-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11DPH-T
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SSG-6029P-E1CR12L
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Jun 15 14:52 seq
   crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a
  InstallationDate: Installed on 2019-02-22 (479 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd 
   Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro SSG-6029P-E1CR12L
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic 
root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 
nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M
  ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-184-generic N/A
   linux-backports-modules-4.4.0-184-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory

[Kernel-packages] [Bug 1873961] Comment bridged from LTC Bugzilla

--- Comment From z...@us.ibm.com 2020-07-21 14:57 EDT---
It can be any NIC, or even lo device.
The fix2.txt has the example like this:
$ $TC qdisc add dev lo ingress
$ $TC filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
$ $TC fitler add dev lo parent : prio 5 proto ip flower ip_proto tcp \
tcp_flags 0x909/f00

$ $TC filter show dev lo parent :
filter protocol ip pref 3 flower chain 0
filter protocol ip pref 3 flower chain 0 handle 0x1
eth_type ipv4
ip_tos 0x8/32
not_in_hw
filter protocol ip pref 5 flower chain 0
filter protocol ip pref 5 flower chain 0 handle 0x1
eth_type ipv4
ip_proto tcp
tcp_flags 0x909/f00  /* <--- */

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions

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

[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value

2020-07-21 Thread Stefan Bader

Sorry this seems to have gotten list in translation. I already got the
one patch fixed up. What I need is some generic instructions to check
the result. Can one just use any pair of NICs or do they have to be
special?

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions

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

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

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

apport-collect 1887723

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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887723

Title:
  mlx5_core: Error cqe on cqn

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New

Bug description:
  I have encountered the following repeating error with kernel
  5.6.0-1018-oem. Network was disturbed and error kept repeating until
  for one hour until the system was hung.

  316294.820469] mlx5_core :44:00.1 enp68s0f1: Error cqe on cqn 0x816, ci 
0xc5, sqn 0x1908, opcode 0xd, syndrome 0x4, vendor syndrome 0x51
  [316294.833103] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833106] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833110] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833116] 0030: 00 00 00 00 04 00 51 04 0e 00 19 08 53 64 dc d2
  [316294.833118] WQE DUMP: WQ size 1024 WQ cur size 0, WQE index 0x364, len: 
128
  [316294.833120] : 00 53 64 0e 00 19 08 07 00 00 00 08 00 00 00 00
  [316294.833121] 0010: 00 00 00 00 c0 00 05 a0 00 00 00 00 00 42 00 a3
  [316294.833123] 0020: 8e bf 47 d7 86 14 ad f8 ef 46 08 00 45 00 12 34
  [316294.833124] 0030: 76 d8 40 00 40 06 77 97 c3 a8 4a 4a 5f 67 cc fa
  [316294.833126] 0040: 01 bb d8 2a 5c 7e 3d a0 b0 c5 3e 74 80 18 00 0b
  [316294.833127] 0050: 4c 7b 00 00 01 01 08 0a 63 59 a1 46 00 41 05 b4
  [316294.833129] 0060: 00 00 12 00 00 08 01 01 00 00 00 00 c2 c6 0b 74
  [316294.833130] 0070: 00 00 00 44 00 08 01 01 00 00 00 00 c3 09 6c fc
  [316294.833144] mlx5_core :44:00.1 enp68s0f1: ERR CQE on SQ: 0x1908
  [316294.996328] enp68s0f1: hw csum failure 
  [316295.000262] skb len=1500 headroom=78 headlen=1500 tailroom=22
  [316295.000262] mac=(64,14) net=(78,40) trans=118
  [316295.000262] shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0))
  [316295.000262] csum(0x81a5 ip_summed=2 complete_sw=0 valid=0 level=0)
  [316295.000262] hash(0x322a7dd7 sw=0 l4=1) proto=0x86dd pkttype=0 iif=0
  [316295.029909] dev name=enp68s0f1 feat=0x0x0010a1821fd14ba9 
  ...
  [316295.943994] Hardware name: ASUSTeK COMPUTER INC. 
RS500A-E10-RS12U/KRPA-U16 Series, BIOS 0703 03/06/2020
  [316295.943995] Call Trace:
  [316295.943997]  
  [316295.944002]  dump_stack+0x6d/0x9a
  [316295.944006]  netdev_rx_csum_fault.part.0+0x41/0x45
  [316295.944007]  __skb_gro_checksum_complete.cold+0xb/0x10
  [316295.944009]  tcp6_gro_receive+0xdc/0x1c0
  [316295.944010]  ipv6_gro_receive+0x1dc/0x460
  [316295.944012]  ? kmem_cache_alloc+0x16d/0x230
  [316295.944017]  dev_gro_receive+0x2fb/0x690
  [316295.996284]  ? mlx5e_build_rx_skb+0x38c/0xb60 [mlx5_core]
  [316296.010778]  napi_gro_receive+0x39/0x140
  [316296.010793]  mlx5e_handle_rx_cqe+0xa5/0x150 [mlx5_core]
  [316296.010808]  mlx5e_poll_rx_cq+0x7fe/0x910 [mlx5_core]
  [316296.010825]  mlx5e_napi_poll+0xda/0x610 [mlx5_core]
  [316296.010843]  ? mlx5_eq_comp_int+0x149/0x1b0 [mlx5_core]
  [316296.010850]  net_rx_action+0x13a/0x370
  [316296.010859]  __do_softirq+0xe1/0x2d6
  [316296.010862]  irq_exit+0xae/0xb0
  [316296.010863]  do_IRQ+0x5a/0xf0
  [316296.010865]  common_interrupt+0xf/0xf
  [316296.010866]  
  [316296.010868] RIP: 0010:cpuidle_enter_state+0xca/0x3e0
  [316296.010869] Code: ff e8 aa 7d 7e ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 ea 02 00 00 31 ff e8 2d 01 85 ff fb 66 0f 1f 44 00 00 <45> 85 
e4 0f 88 3f 02 00 00 49 63 d4 4c 8b 7d d0 4c 2b 7d c8 48 8d
  [316296.010870] RSP: 0018:9d84002cfe38 EFLAGS: 0246 ORIG_RAX: 
ffda
  [316296.010872] RAX: 91110b62ce00 RBX: 9110ac1d1c00 RCX: 
001f
  [316296.010872] RDX:  RSI: 334bfb91 RDI: 

  [316296.010873] RBP: 9d84002cfe78 R08: 00011fab2ae67109 R09: 
00011faebfd6b300
  [316296.010873] R10: 91110b62bac4 R11: 91110b62baa4 R12: 
0002
  [316296.010874] R13: 8f978700 R14: 0002 R15: 
9110ac1d1c00
  [316296.010876]  ? cpuidle_enter_state+0xa6/0x3e0
  [316296.010878]  cpuidle_enter+0x2e/0x40
  [316296.010880]  call_cpuidle+0x23/0x40
  [316296.010881]  do_idle+0x1e7/0x280
  [316296.010882]  cpu_startup_entry+0x20/0x30
  [316296.010885]  start_secondary+0x167/0x1c0
  [316296.010886]  secondary_startup_64+0xa4/0xb0

  # lspci -v -s

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

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

This bug will be solved by #1885322 which rebases 5.4.49, containing the
PCI patchset.

** This bug has been marked a duplicate of bug 1885322
   Focal update: v5.4.49 upstream stable release

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1887723] Re: mlx5_core: Error cqe on cqn

2020-07-21 Thread Martin Matuska

I can reproduce the bug on 5.4.0-40-generic

** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887723

Title:
  mlx5_core: Error cqe on cqn

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New

Bug description:
  I have encountered the following repeating error with kernel
  5.6.0-1018-oem. Network was disturbed and error kept repeating until
  for one hour until the system was hung.

  316294.820469] mlx5_core :44:00.1 enp68s0f1: Error cqe on cqn 0x816, ci 
0xc5, sqn 0x1908, opcode 0xd, syndrome 0x4, vendor syndrome 0x51
  [316294.833103] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833106] 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833110] 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [316294.833116] 0030: 00 00 00 00 04 00 51 04 0e 00 19 08 53 64 dc d2
  [316294.833118] WQE DUMP: WQ size 1024 WQ cur size 0, WQE index 0x364, len: 
128
  [316294.833120] : 00 53 64 0e 00 19 08 07 00 00 00 08 00 00 00 00
  [316294.833121] 0010: 00 00 00 00 c0 00 05 a0 00 00 00 00 00 42 00 a3
  [316294.833123] 0020: 8e bf 47 d7 86 14 ad f8 ef 46 08 00 45 00 12 34
  [316294.833124] 0030: 76 d8 40 00 40 06 77 97 c3 a8 4a 4a 5f 67 cc fa
  [316294.833126] 0040: 01 bb d8 2a 5c 7e 3d a0 b0 c5 3e 74 80 18 00 0b
  [316294.833127] 0050: 4c 7b 00 00 01 01 08 0a 63 59 a1 46 00 41 05 b4
  [316294.833129] 0060: 00 00 12 00 00 08 01 01 00 00 00 00 c2 c6 0b 74
  [316294.833130] 0070: 00 00 00 44 00 08 01 01 00 00 00 00 c3 09 6c fc
  [316294.833144] mlx5_core :44:00.1 enp68s0f1: ERR CQE on SQ: 0x1908
  [316294.996328] enp68s0f1: hw csum failure 
  [316295.000262] skb len=1500 headroom=78 headlen=1500 tailroom=22
  [316295.000262] mac=(64,14) net=(78,40) trans=118
  [316295.000262] shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0))
  [316295.000262] csum(0x81a5 ip_summed=2 complete_sw=0 valid=0 level=0)
  [316295.000262] hash(0x322a7dd7 sw=0 l4=1) proto=0x86dd pkttype=0 iif=0
  [316295.029909] dev name=enp68s0f1 feat=0x0x0010a1821fd14ba9 
  ...
  [316295.943994] Hardware name: ASUSTeK COMPUTER INC. 
RS500A-E10-RS12U/KRPA-U16 Series, BIOS 0703 03/06/2020
  [316295.943995] Call Trace:
  [316295.943997]  
  [316295.944002]  dump_stack+0x6d/0x9a
  [316295.944006]  netdev_rx_csum_fault.part.0+0x41/0x45
  [316295.944007]  __skb_gro_checksum_complete.cold+0xb/0x10
  [316295.944009]  tcp6_gro_receive+0xdc/0x1c0
  [316295.944010]  ipv6_gro_receive+0x1dc/0x460
  [316295.944012]  ? kmem_cache_alloc+0x16d/0x230
  [316295.944017]  dev_gro_receive+0x2fb/0x690
  [316295.996284]  ? mlx5e_build_rx_skb+0x38c/0xb60 [mlx5_core]
  [316296.010778]  napi_gro_receive+0x39/0x140
  [316296.010793]  mlx5e_handle_rx_cqe+0xa5/0x150 [mlx5_core]
  [316296.010808]  mlx5e_poll_rx_cq+0x7fe/0x910 [mlx5_core]
  [316296.010825]  mlx5e_napi_poll+0xda/0x610 [mlx5_core]
  [316296.010843]  ? mlx5_eq_comp_int+0x149/0x1b0 [mlx5_core]
  [316296.010850]  net_rx_action+0x13a/0x370
  [316296.010859]  __do_softirq+0xe1/0x2d6
  [316296.010862]  irq_exit+0xae/0xb0
  [316296.010863]  do_IRQ+0x5a/0xf0
  [316296.010865]  common_interrupt+0xf/0xf
  [316296.010866]  
  [316296.010868] RIP: 0010:cpuidle_enter_state+0xca/0x3e0
  [316296.010869] Code: ff e8 aa 7d 7e ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 ea 02 00 00 31 ff e8 2d 01 85 ff fb 66 0f 1f 44 00 00 <45> 85 
e4 0f 88 3f 02 00 00 49 63 d4 4c 8b 7d d0 4c 2b 7d c8 48 8d
  [316296.010870] RSP: 0018:9d84002cfe38 EFLAGS: 0246 ORIG_RAX: 
ffda
  [316296.010872] RAX: 91110b62ce00 RBX: 9110ac1d1c00 RCX: 
001f
  [316296.010872] RDX:  RSI: 334bfb91 RDI: 

  [316296.010873] RBP: 9d84002cfe78 R08: 00011fab2ae67109 R09: 
00011faebfd6b300
  [316296.010873] R10: 91110b62bac4 R11: 91110b62baa4 R12: 
0002
  [316296.010874] R13: 8f978700 R14: 0002 R15: 
9110ac1d1c00
  [316296.010876]  ? cpuidle_enter_state+0xa6/0x3e0
  [316296.010878]  cpuidle_enter+0x2e/0x40
  [316296.010880]  call_cpuidle+0x23/0x40
  [316296.010881]  do_idle+0x1e7/0x280
  [316296.010882]  cpu_startup_entry+0x20/0x30
  [316296.010885]  start_secondary+0x167/0x1c0
  [316296.010886]  secondary_startup_64+0xa4/0xb0

  # lspci -v -s :44:00.1
  44:00.1 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 
Lx]
Subsystem: Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
Flags: bus master, fast devsel, latency 0, IRQ 254, NUMA node 0
Memory at b000 (64-bit, prefetchable) [size=32M]
Expansion ROM at b530 [disabled] [size=1M]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c]

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

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

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394667/+files/PulseList.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394659/+files/IwConfig.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394666/+files/ProcModules.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1888390/+attachment/5394669/+files/UdevDb.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394670/+files/WifiSyslog.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1888390/+attachment/5394660/+files/Lspci.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1888390/+attachment/5394668/+files/RfKill.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394662/+files/ProcCpuinfo.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394658/+files/CurrentDmesg.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394664/+files/ProcEnviron.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1888390/+attachment/5394661/+files/Lsusb.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394665/+files/ProcInterrupts.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394663/+files/ProcCpuinfoMinimal.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

apport information

** Tags added: apport-collected

** Description changed:

  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  edgars 1716 F pulseaudio
+  /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-01-07 (195 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ MachineType: LENOVO 2350BH1
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-62-generic N/A
+  linux-backports-modules-5.3.0-62-generic  N/A
+  linux-firmware1.173.19
+ Tags:  bionic
+ Uname: Linux 5.3.0-62-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/08/2014
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G1ETA7WW (2.67 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 2350BH1
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.family: ThinkPad T430
+ dmi.product.name: 2350BH1
+ dmi.product.sku: LENOVO_MT_2350
+ dmi.product.version: ThinkPad T430
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1888390/+attachment/5394656/+files/AlsaInfo.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType:

[Kernel-packages] [Bug 1888390] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1888390/+attachment/5394657/+files/CRDA.txt

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1697567] Re: something prevents the cooler fan from spinning as fast as needed

2020-07-21 Thread teo1978

How the fuck can this still be unfixed?

This is a critical bug that causes a computer to suddenly switch off,
loosing data, and it potentially DAMAGES HARDWARE.

This has been known for at least 3 years, nothing has been done and...
OMG I now see the importance is set to medium, who is the IDIOT that set
the importance to medium??

Is there at least a workaround? I need to force my fan to spin at the
maximum speed, since the OS is not controlling it properly and my CPU is
BURNING.


Also, this recently got worse.
As I mentioned in an earlier comment, when I boot and the boot menu shows up, 
the fan used to spin much faster when the computer was hot.
That proved that either the OS, which loads afterwards, would start controlling 
the speed and keeping it too low, while during the boot menu screen the 
hardware was left uncontrolled and knew better, OR that grub used to load some 
sort of driver that did a better job than ubuntu does at controlling the fan 
speed.

Well, that doesn't happen anymore, since a recent update. Now, when my
computer gets too hot and switches itself off, or when I see it is
getting too hot and I restart it, during the boot screen the fan does
not spin faster, it goes at the same insufficient speed as it does
during normal OS operation, or even slower. I guess grub has been
updated to control the fan in the same broken way that used to only kick
in later in the boot process.

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

Title:
  something prevents the cooler fan from spinning as fast as needed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Something in Ubuntu keeps my laptop's cooler fan from going at the
  speed that would be needed to keep the temperature within its safe
  range.

  The proof that something is wrong is that the computer overheats to
  the point that, first, the CPU starts to slow down to protect itself
  (you can tell the CPU has less power because trivial processes that
  barely do any work suddenly are consuming great percentages of CPU)
  and eventually even the computer shuts down (abruptly) to prevent
  itself from burning **AND** the fan speed doesn't get even close to
  its maximum speed while all this is happening.

  Note: I keep thermald turned off because of issue 1600599. I also disabled 
intel_powerclamp and intel_rapl to rule out that they were just kicking in 
before it's actually necessary.
  This has mitigated the issue, I'm pretty sure, but it has not solved it 
completely.

  Yes, my fan is full of dust and doesn't do its job very well, but if
  that alone was the issue, the fan should reach its top speed well
  before the CPU reaches critical temperature.

  The definitive proof that the fan *can* go faster is that, when the
  computer is overheating, if I restart it, at the grub screen, the fan
  spins a lot faster. Then, as the OS boots, its speed drops. Then you
  can also hear as the speed slowly diminishes, as if it was gradually
  slowing down because it's managing to keep the temperature under
  control. Except that the temperature keeps going up.

  Even by just suspending and resuming, the fan speed gets a noticeable
  boost (not as huge as by rebooting, for some reason), which is utter
  nonsense, and then soon slows down again.

  The huge increase in fan speed at restart just before boot (note: only
  when the computer is hot) proves that not only the fan can spin faster
  than the OS lets it, but also that the hardware "KNOWS" how fast it
  should spin. Either the hardware, assuming that no driver has been
  loaded yet when presented the grub screen, or some kind of more
  primitive driver that is loaded together with grub, I don't know.
  SOMETHING does know how to control the fan speed properly, and
  something that is started during boot imposes a wrong, lower speed.

  
  I assume that the fan speed is not regulated by a simple fixed map from 
temperature values to fan speed values. That would completely explain the 
behaviour (the fan is not as efficient as it is supposed to be, hence the 
predetermined speed values function of temperature are not enough), but it 
would be incredibly stupid. Please tell me that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-79-generic 4.4.0-79.100
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2826 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jun 13 01:49:34 2017
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (1340 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64

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

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

apport-collect 1888390

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

** Tags added: 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/1888390

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

And christ, I just realized in my post-seizure state, that I have yet to
mentioned that I can connect to other networks, including a hotspot
created from my phone. I'm not sure if it's any help with this issue
though

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection 
(Lewisville) (rev 04)
Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] 
(rev 34)

I'm using a Lenovo Thinkpad T430 laptop.
And yeah, sorry for not supplying the correct information, I'm quite new to 
reporting bugs of this kind and still learning the ropes and copying out the 
exact dmesg output that I interpret as related (mostly due to appearing in the 
output just before the deauthentication) seems the proper thing to do.

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

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

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

2020-07-21 Thread Ubuntu Foundations Team Bug Bot

** Tags added: 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/1888410

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

2020-07-21 Thread Sebastien Bacher

Could you give details on the wifi card you have in your computer?

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Kernel-packages] [Bug 1690085]

2020-07-21 Thread yungease

Traveling with a musical instrument requires careful handling and
storing because of its fragility. It can easily be damaged with humidity
and other unexpected situations like bumps and extreme pressure.
https://sahiphopza.com/download-mp3/august-alsina-ft-rick-ross-
entanglements/ https://sahiphopza.com/ https://sahiphopza.com/download-
mp3/stogie-t-ft-benny-the-butcher-animals/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

2020-07-21 Thread Sebastien Bacher

The warning you are copying are not related to your connectivity issue,
but the problem you describe seems rather one with wpasupplicant or with
the driver, I'm reassigning to the kernel

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Kernel-packages] [Bug 1888405] Re: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols

2020-07-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "Patch for zvol_wait to ignore locked zvols" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  zfsutils-linux: zfs-volume-wait.service fails with locked encrypted
  zvols

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I was doing some experimentation with encrypted zvols and observed
  that the zfs-volume-wait.service systemd unit does not start if the
  encrypted zvol is locked.  The /sbin/zvol_wait should not wait for
  links when the volume has property keystatus=unavailable.  The
  attached patch seems to resolve the issue for me.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.1
Candidate: 0.8.3-1ubuntu12.2
Version table:
   0.8.3-1ubuntu12.2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.1 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Kernel-packages] [Bug 1888390] [NEW] apparmor error causing deauthentication for certain SSID's

You have been subscribed to a public bug:

dmesg output:
[   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
[  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
[  165.568883] wlan0: authenticated
[  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
[  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 
aid=3)
[  165.579888] wlan0: associated
[  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
Release Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic
Expected outcome: 
Connecting to the home network
Actual outcome:
deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

** Affects: linux (Ubuntu)
 Importance: Low
 Status: New


** Tags: bot-comment
-- 
apparmor error causing deauthentication for certain SSID's
https://bugs.launchpad.net/bugs/1888390
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

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

apport-collect 1888372

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

** Tags added: eoan

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

Title:
  Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The bug among with ist underlying system is being described in detail
  at https://askubuntu.com/questions/1260677/ubuntu-20-04-upgrade-
  getting-stuck-with-fsck-check.

  The system is currently only bootable in rescue mode. As being
  described a regular boot shows an endless spinner following the grub
  menu stage during the boot process.

  All packages are current to 20.04.

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

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

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

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

apport-collect 1888410

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=5800b7f7d2316d0defc5288eb62907460dd275e1
is the backport commit upstream

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1888410] Re: amdgpudrmfb fails to init on SolidRun Honeycomb

This also would be fixed by rebasing on 5.4.52 from upstream.

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  New

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-21 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => Triaged

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions

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

[Kernel-packages] [Bug 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed

2020-07-21 Thread Frank Heimes

A test build got created and is available from here:
https://people.canonical.com/~fheimes/lp1879707/

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

Title:
  [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of
  retries and failed

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New

Bug description:
  mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and 
failed,Failing CCW
   
  ---uname output---
  xx -  5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x 
s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   mke2fs to dasd(fba) devices
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  dasd(fba),Failing CCW,default ERP has run out of retries and failed between 
the following syslog events,
  mke2fs running, before mounting and starting IO to dasd(fba) devices

  May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START
  May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+subscriptions

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

[Kernel-packages] [Bug 1888372] Re: Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check

2020-07-21 Thread Brian Murray

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

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

Title:
  Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check

Status in linux package in Ubuntu:
  New

Bug description:
  The bug among with ist underlying system is being described in detail
  at https://askubuntu.com/questions/1260677/ubuntu-20-04-upgrade-
  getting-stuck-with-fsck-check.

  The system is currently only bootable in rescue mode. As being
  described a regular boot shows an endless spinner following the grub
  menu stage during the boot process.

  All packages are current to 20.04.

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

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

[Kernel-packages] [Bug 1888410] [NEW] amdgpudrmfb fails to init on SolidRun Honeycomb

Public bug reported:

https://patchwork.ozlabs.org/project/linux-
pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be backported
into the Ubuntu 5.4 kernel train in order for amdgpudrmfb to
successfully initialize. Otherwise, the last line seen on framebuffer is
`fb0: switching to amdgpudrmfb from EFI VGA` and then the boot freezes.

I have tested this as a patchest against the 5.7 kernel series, and will
also patch & build against the Ubuntu 5.4 kernel series.

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

** Patch added: 
"PCI-allow-pci_resize_resource-to-be-used-on-devices-on-the-root-bus.diff"
   
https://bugs.launchpad.net/bugs/1888410/+attachment/5394634/+files/PCI-allow-pci_resize_resource-to-be-used-on-devices-on-the-root-bus.diff

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

Title:
  amdgpudrmfb fails to init on SolidRun Honeycomb

Status in linux package in Ubuntu:
  New

Bug description:
  https://patchwork.ozlabs.org/project/linux-
  pci/patch/20200421162256.26887-1-a...@kernel.org/ needs to be
  backported into the Ubuntu 5.4 kernel train in order for amdgpudrmfb
  to successfully initialize. Otherwise, the last line seen on
  framebuffer is `fb0: switching to amdgpudrmfb from EFI VGA` and then
  the boot freezes.

  I have tested this as a patchest against the 5.7 kernel series, and
  will also patch & build against the Ubuntu 5.4 kernel series.

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

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

[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-21 Thread Treviño

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/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
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati

[Kernel-packages] [Bug 1888372] [NEW] Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check

You have been subscribed to a public bug:

The bug among with ist underlying system is being described in detail at
https://askubuntu.com/questions/1260677/ubuntu-20-04-upgrade-getting-
stuck-with-fsck-check.

The system is currently only bootable in rescue mode. As being described
a regular boot shows an endless spinner following the grub menu stage
during the boot process.

All packages are current to 20.04.

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


** Tags: bot-comment
-- 
Ubuntu 19.10 to 20.04 upgrade getting stuck with fsck check
https://bugs.launchpad.net/bugs/1888372
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1873961] Fix 2

--- Comment (attachment only) From z...@us.ibm.com 2020-07-21 10:56 
EDT---


** Attachment added: "Fix 2"
   https://bugs.launchpad.net/bugs/1873961/+attachment/5394633/+files/fix2.txt

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions

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

[Kernel-packages] [Bug 1873961] Fix 1

--- Comment (attachment only) From z...@us.ibm.com 2020-07-21 10:55 
EDT---


** Attachment added: "Fix 1"
   https://bugs.launchpad.net/bugs/1873961/+attachment/5394632/+files/fix1.txt

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions

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

[Kernel-packages] [Bug 1873961] Comment bridged from LTC Bugzilla

--- Comment From z...@us.ibm.com 2020-07-21 10:54 EDT---
I download iproute2-4.18.0.tar.gz from this upstream url:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Then pulled in 2 patches documented in comment 1 on top of 
iproute2-4.18.0.tar.gz, build and test the functionality.
It builds successfully, and it does reports correct tcp_flags mask with these 2 
patches.

Attach these 2 patches in the bug for reference.

The first patch declares global variable "const char *_SL_ = "\n";" in
lib/utils.c to be used by 2nd patch to fix the build break issue.

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions

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

[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-07-21 Thread jman6495

Has anyone built this package for 20.04 ?

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 
10 00 00 00 0f 05 <48> 3d

[Kernel-packages] [Bug 1879333] Re: [nvidia] Black screen on loading latest system update

2020-07-21 Thread mtbdrew

Occurred again today after the kernel update was installed and system
reset. When is this issue going to get fixed!

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

Title:
  [nvidia] Black screen on loading latest system update

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This bug has been around since 16.04 and still occurs with 18.04 when
  using nvidia drivers. When update required for the OS the black screen
  situation happens after the required reboot. Only way to regain
  desktop is to login via ssh terminal and run the commands listed here:

  https://askubuntu.com/questions/1129516/black-screen-at-boot-after-
  nvidia-driver-installation-on-ubuntu-18-04-2-lts

  sudo apt-get update

  sudo apt-get upgrade

  sudo apt-get purge nvidia*

  sudo apt autoremove

  sudo apt-get install dkms build-essential linux-headers-$(uname -r)

  echo "# Disable the default Nouveau kernel driver" | sudo tee -a
  /etc/modprobe.d/blacklist-nouveau.conf

  echo "# -" | sudo tee -a
  /etc/modprobe.d/blacklist-nouveau.conf

  echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d
  /blacklist-nouveau.conf

  echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-
  nouveau.conf

  cat /etc/modprobe.d/blacklist-nouveau.conf

  echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d
  /nouveau-kms.conf

  cat /etc/modprobe.d/nouveau-kms.conf

  sudo update-initramfs -u

  sudo service lightdm stop

  sudo apt-get install nvidia-driver-440

  lsmod | grep nvidia

  sudo lshw -c video | grep 'configuration'

  sudo reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon May 18 08:44:05 2020
  DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1]
   NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a]
  InstallationDate: Installed on 2019-09-26 (234 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau:

[Kernel-packages] [Bug 1888405] Re: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols

2020-07-21 Thread Colin Ian King

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

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfsutils-linux: zfs-volume-wait.service fails with locked encrypted
  zvols

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I was doing some experimentation with encrypted zvols and observed
  that the zfs-volume-wait.service systemd unit does not start if the
  encrypted zvol is locked.  The /sbin/zvol_wait should not wait for
  links when the volume has property keystatus=unavailable.  The
  attached patch seems to resolve the issue for me.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.1
Candidate: 0.8.3-1ubuntu12.2
Version table:
   0.8.3-1ubuntu12.2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.1 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

2020-07-21 Thread Patrik Nilsson

Repeated the test with Ugreen connected directly to the computer's USB
with "usb-storage.quirks=174c:55aa:u". It took 15 minutes and 2 seconds
to fail.

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

Title:
high speed data to usb disk makes the kernel think that is has been
unmounted

Status in linux package in Ubuntu:
Confirmed

Bug description:
Description:

When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to
be unmounted and is remounted with an other drive letter (/dev/sdX).
If this disk is the root ("/"), the computer hangs.

A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.

Symptoms and how to reproduce:

1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.

2) (Erasing disk, not mounted as root) If you erase a disk with dd
("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
list and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45
to 60 minutes.

3) Fill RAM with programs and make sure the swap to this disk is used.

Bug found in:

$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44

Hardware:

Tested with slower and faster computers. Tested directly connected to
a computer and via a hub. They all reproduce this bug.

Workaround:

None found.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: user 6813 F pulseaudio
/dev/snd/controlC0: user 6813 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
MachineType: ASUSTeK COMPUTER INC. GL503VM
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
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
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo vboxusers wireshark
WifiSyslog:

_MarkForUpload: False
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503VM.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL503VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1887703] Re: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller

2020-07-21 Thread Jeff Lane

Per tester, the patched kernel does not resolve the issue.

At least we know the diff.

Also, did some bisecting with the Intel drivers upstream and this is the
earliest version where the card starts working again:

2.10.19.82

So it breaks sometime around 2.8.20 and then starts working again around
2.10.19.82

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

Title:
[Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE
controller

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed

Bug description:
[IMPACT]

The Intel x710-TM4 is one of the latest 10GbE controllers from intel
using the i40e driver. This particular 4 port comes in a 2x2
arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via
the inbox version of the i40e driver, and hwinfo does show both sides
of the card but the kernel only sees the two SFP+ ports and cannot
address or use the two copper ports.

This is currently blocking certification for one of our hardware
partners.

After some investigation we see this works in a more recent version of
the driver. Intel suggests the commit in FIXES from 5.5 should make
this work.

This is a regression from the i40e driver in Bionic (5.3 HWE) that,
per the tester, does show all four ports.

[FIXES]

3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support

I have a branch here:

https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710

[TESTING]
Boot system, verify four ports are visible and can be addressed and pass data.

[IMPACT]

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

[Kernel-packages] [Bug 1888405] [NEW] zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols

2020-07-21 Thread James Dingwall

Public bug reported:

I was doing some experimentation with encrypted zvols and observed that
the zfs-volume-wait.service systemd unit does not start if the encrypted
zvol is locked.  The /sbin/zvol_wait should not wait for links when the
volume has property keystatus=unavailable.  The attached patch seems to
resolve the issue for me.

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

# apt-cache policy zfsutils-linux
zfsutils-linux:
  Installed: 0.8.3-1ubuntu12.1
  Candidate: 0.8.3-1ubuntu12.2
  Version table:
 0.8.3-1ubuntu12.2 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 *** 0.8.3-1ubuntu12.1 100
100 /var/lib/dpkg/status
 0.8.3-1ubuntu12 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Patch for zvol_wait to ignore locked zvols"
   https://bugs.launchpad.net/bugs/1888405/+attachment/5394630/+files/zfs-patch

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

Title:
  zfsutils-linux: zfs-volume-wait.service fails with locked encrypted
  zvols

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I was doing some experimentation with encrypted zvols and observed
  that the zfs-volume-wait.service systemd unit does not start if the
  encrypted zvol is locked.  The /sbin/zvol_wait should not wait for
  links when the volume has property keystatus=unavailable.  The
  attached patch seems to resolve the issue for me.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.1
Candidate: 0.8.3-1ubuntu12.2
Version table:
   0.8.3-1ubuntu12.2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.1 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

2020-07-21 Thread Patrik Nilsson

Ugreen is the adapter interface between USB and SATA, drive enclosure
for the 2.5" drive. It is the same device.

During my tests I have connected Ugreen directly to the computer or via
an external powered HUB. All tests give the same failing result. No
difference.

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

Title:
high speed data to usb disk makes the kernel think that is has been
unmounted

Status in linux package in Ubuntu:
Confirmed

Bug description:
Description:

A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.

Symptoms and how to reproduce:

1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.

3) Fill RAM with programs and make sure the swap to this disk is used.

Bug found in:

$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44

Hardware:

Tested with slower and faster computers. Tested directly connected to
a computer and via a hub. They all reproduce this bug.

Workaround:

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

[Kernel-packages] [Bug 1879308] Re: ubuntu_aufs_smoke_test failed on Focal OEM 5.6

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu_aufs_smoke_test failed on Focal OEM 5.6

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  Issue found on OEM 5.6 (5.6.0-1010.10-oem)

  Test failed with:
  mount: /tmp/aufs/aufs-root: unknown filesystem type 'aufs'.

  Need to check if 5.6 supports aufs.

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

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

[Kernel-packages] [Bug 1844410] Re: [TGL] Thunderbolt support (Tiger Lake)

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [TGL] Thunderbolt support (Tiger Lake)

Status in HWE Next:
  New
Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  TigerLake platforms fail to probe thunderbolt controller and leaving an
  error message:

[2.069944] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio1/input/input5
[   21.772011] thunderbolt: probe of :00:0d.2 failed with error -110

  It also introduces a nearly 20 second idle at boot.

  [Fix]

  Commit 57d8df68eb53 ("thunderbolt: Add support for Intel Tiger Lake")
  recently landed to v5.8-rc1 addressed this issue.

  [Test Case]

  Check thunderbolt controller probe messages from dmesg:

thunderbolt :00:0d.2: 0: unsupported switch device id 0x9a1b
thunderbolt :00:0d.2: 0: uid crc8 mismatch (expected: 0x8e, got: 0x59)

  [Regression Potential]

  Low. This only enables devices which are previously failed in device
  initialization.

  == Original Bug Description ==

  Description
  TBT enabling in TGL

  * 386e5e29d81c ("thunderbolt: Make tb_find_port() available to other files") 
v5.6-rc1
  * 4deb200d34a7 ("thunderbolt: Call tb_eeprom_get_drom_offset() from 
tb_eeprom_read_n()") v5.6-rc1
  * 210e9f56e9e1 ("thunderbolt: Populate PG field in hot plug acknowledgment 
packet") v5.6-rc1
  * b04079837b20 ("thunderbolt: Add initial support for USB4") v5.6-rc1
  * 690ac0d20d40 ("thunderbolt: Update Kconfig entries to USB4") v5.6-rc1
  * aa43a9dcf7fc ("thunderbolt: Make tb_switch_find_cap() available to other 
files") v5.6-rc1
  * cf29b9afb121 ("thunderbolt: Add support for Time Management Unit") v5.6-rc1
  * e6f818585713 ("thunderbolt: Add support for USB 3.x tunnels") v5.6-rc1

  Target Kernel: 5.6
  Target Release: 20.10

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

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

[Kernel-packages] [Bug 1885896] Re: Add generic LED class support for audio LED

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Add generic LED class support for audio LED

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Like GPIO controlled LED, COEF controlled LED also need LED class
  support, in order to be used by SoF driver.

  [Fix]
  Convert all HDA vendor-specific LED control to generic LED class.

  [Test]
  After applying the patch series, COEF controlled LED is exported under
  /sys/class/leds/, so SoF driver now can control the micmute LED.

  Also verified on GPIO based micmute LED, it also works fine.

  [Regression Potential]
  Low. Though there are 13 patches, most of them are straightforward
  conversion.

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

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

[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  SRU justification:
  [Impact]
  New realtek wifi card ID found on ThinkCentre.
  No driver is loaded to support it.

  [Fix]
  This wifi card is very similar as 0xc822 in rtw88.

  [Test]
  Verified on hardware, link status is OK, iperf test result is good.

  [Regression Potential]
  Low.
  Add new ID to supported driver.
  Test on hw, double confirmed by LP bugs.
  This patch is backported from original link due to the 5.8-rc1 driver
  file path changed, no function changed.

  Maintainer had merged:
  
https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351
  This git repo is moving by maintainer, not availible by now.
  
=

  
  01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f

  Looking for a working solution on a fresh install (USB BOOT) of
  Ubuntu. A work-around helped, for a while, but I would really like to
  disconnect my Wifi Dongel and use my brand new laptop!

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1277 F pulseaudio
   /dev/snd/pcmC0D0c:   christian   1277 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 07:58:06 2020
  InstallationDate: Installed on 2020-06-28 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81W8
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 
pci=nocrs 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
  StagingDrivers: r8712u
  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: SDK0R32866 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:rvrSDK0R32866WIN: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

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

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

[Kernel-packages] [Bug 1883938] Re: Focal update: v5.6.19 upstream stable release

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Focal update: v5.6.19 upstream stable release

Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Fix Released

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:

     v5.6.19 upstream stable release
     from git://git.kernel.org/

  ipv6: fix IPV6_ADDRFORM operation logic
  mlxsw: core: Use different get_trend() callbacks for different thermal zones
  net_failover: fixed rollback in net_failover_open()
  tun: correct header offsets in napi frags mode
  bridge: Avoid infinite loop when suppressing NS messages with invalid options
  vxlan: Avoid infinite loop when suppressing NS messages with invalid options
  net: ena: xdp: XDP_TX: fix memory leak
  net: ena: xdp: update napi budget for DROP and ABORTED
  genetlink: fix memory leaks in genl_family_rcv_msg_dumpit()
  net: dsa: qca8k: Fix "Unexpected gfp" kernel exception
  tipc: fix NULL pointer dereference in streaming
  bpf: Support llvm-objcopy for vmlinux BTF
  elfnote: mark all .note sections SHF_ALLOC
  Input: mms114 - fix handling of mms345l
  Input: axp20x-pek - always register interrupt handlers
  ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
  sched/fair: Don't NUMA balance for kthreads
  Input: synaptics - add a second working PNP_ID for Lenovo T470s
  csky: Fixup abiv2 syscall_trace break a4 & a5
  gfs2: Even more gfs2_find_jhead fixes
  drivers/net/ibmvnic: Update VNIC protocol version reporting
  staging: wfx: fix double free
  staging: mt7621-pci: properly power off dual-ported pcie phy
  perf probe: Accept the instance number of kretprobe event
  mm: add kvfree_sensitive() for freeing sensitive data objects
  selftests: fix flower parent qdisc
  fanotify: fix ignore mask logic for events on child and on dir
  driver core: Update device link status correctly for SYNC_STATE_ONLY links
  powerpc/xive: Clear the page tables for the ESB IO mapping
  spi: dw: Fix native CS being unset
  ath9k_htc: Silence undersized packet warnings
  smack: avoid unused 'sip' variable warning
  RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
  padata: add separate cpuhp node for CPUHP_PADATA_DEAD
  s390/pci: Log new handle in clp_disable_fh()
  x86/cpu/amd: Make erratum #1054 a legacy erratum
  KVM: x86: only do L1TF workaround on affected processors
  scsi: target: remove boilerplate code
  scsi: target: fix hang when multiple threads try to destroy the same iscsi 
session
  drm/amd/display: remove invalid dc_is_hw_initialized function
  drm/amd/display: Not doing optimize bandwidth if flip pending.
  aio: fix async fsync creds
  usercopy: mark dma-kmalloc caches as usercopy caches
  x86_64: Fix jiffies ODR violation
  x86: mm: ptdump: calculate effective permissions correctly
  x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
  x86/speculation: Prevent rogue cross-process SSBD shutdown
  x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
  x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
  x86/reboot/quirks: Add MacBook6,1 reboot quirk
  perf/x86/intel: Add more available bits for OFFCORE_RESPONSE of Intel Tremont
  KVM: x86: allow KVM_STATE_NESTED_MTF_PENDING in kvm_state flags
  KVM: x86/mmu: Set mmio_value to '0'

[Kernel-packages] [Bug 1885072] Re: [SRU][OEM-5.6/U] Fix r8117 firmware base issue

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU][OEM-5.6/U] Fix r8117 firmware base issue

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Realtek 8117 failed to work after loading firmware on 5.5+ kernel.

  [Fix]
  Firmware should reset ocp_base, but not on r8117. Correct the ocp_base in the 
driver.
  Then it works well.

  [Test]
  Verified on hardware, link status is OK, iperf test result is good.

  [Regression Potential]
  Low.
  Fixed issue, cherry-picked from maintainer's tree.
  Due to 5.4- kernel needs more patches, SRU the fix on 5.5+ kernel first.

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

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

[Kernel-packages] [Bug 1887724] Re: [amdgpu] Xorg freeze

2020-07-21 Thread Blaise Mariner

Great, thank you. I will try this out. For my reference, how would I re-
enable the built in wifi? Thanks again

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

Title:
  [amdgpu] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random freezing-- different freezing every time. I switched GUIs from
  Gnome to Cinnamon and it seems to freeze less, but still averaging
  about once a day. I cannot reproduce, is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Wed Jul 15 15:44:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [1028:0884]
  InstallationDate: Installed on 2020-06-04 (40 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=0ed970bf-fd17-4242-8a3e-5c1224ed5b72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 02YPPF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn02YPPF:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Dell Inc.
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  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/linux/+bug/1887724/+subscriptions

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

[Kernel-packages] [Bug 1886165] Re: [WD19TB] external DP failed with DRM error message

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20

---
linux-oem-5.6 (5.6.0-1020.20) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1020.20 -proposed tracker (LP: #1886753)

  * Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
(LP: #1886247)
- SAUCE: rtw88: 8822ce: add support for device ID 0xc82f

  * [WD19TB] external DP failed with DRM error message (LP: #1886165)
- drm/i915/tgl: Update TC DP vswing table
- drm/i915/tgl: Implement WA_16011163337
- SAUCE: drm/i915/bios: add intel_bios_hdmi_level_shift()
- drm/i915/tgl: Add HBR and HBR2+ voltage swing table
- drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
- drm/i915/tgl+: Use the correct DP_TP_* register instances in MST encoders
- drm/i915/tgl+: Fix TBT DPLL fractional divider for 38.4MHz ref clock

  * ubuntu_aufs_smoke_test failed on Focal OEM 5.6 (LP: #1879308)
- SAUCE: fs: Enable aufs

 -- Timo Aaltonen   Wed, 08 Jul 2020
11:44:53 +0300

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [WD19TB] external DP failed with DRM error message

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

Bug description:
  [SRU Justfication]

  TGL platform can't output external monitor on WD19TB docking. 

 
  There's no screen on the external monitor.

 
  error in dmesg:   

 


 
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underru 
  

  [Fix] 

 
  According to Intel's suggestion,  

 
  we need this: https://patchwork.freedesktop.org/series/78909/ 

 
  Also for dependency, the following patches are landed in drm-tip  

 
  and necessary for support TGL platform:   

 


 
  * commit f4ece33f51d8 ("drm/i915/tgl+: Fix TBT DPLL fractional divider for 
38.4MHz ref clock")
  * commit a6e96d6948c8 ("drm/i915/tgl+: Use the correct DP_TP_* register 
instances in MST encoders")
  * commit f822a79734e1 ("drm/i915/dc3co: Avoid full modeset when EXITLINE 
needs to be changed")
  * commit 1a7e82efaa8a ("drm/i915/tgl: Add HBR and HBR2+ voltage swing table")
  * commit 80907edcc6ed ("UBUNTU: SAUCE: drm/i915/bios: add 
intel_bios_hdmi_level_shift()")
  * commit 6df896896c8d ("drm/i915/tgl: Implement WA_16011163337")
  * commit cb730fe971f0 ("drm/i915/tgl: Update TC DP vswing table")

  [Test]

 
  The WD19TB can output HDMI/DP to external monitor.

 


 
  [Regression Potential]

 
  Medium, in order to support TGL platform, we also include two patches:

 
  drm/i915/bios: add intel_bios_hdmi_level_shift()  

 
  drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed

[Kernel-packages] [Bug 1879401] Re: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works

2020-07-21 Thread Nathan Bryant

Sure. pactl list cards output is identical on success and failure:

$ md5sum pactl-list-cards-*
1b3e54a38e363e16115a0428901f71ed  pactl-list-cards-fail.txt
1b3e54a38e363e16115a0428901f71ed  pactl-list-cards-success.txt


** Attachment added: "pactl-list-cards.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879401/+attachment/5394624/+files/pactl-list-cards.txt

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

Title:
  [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
  rarely works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting
  to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
  Thunderbolt device, it is just USB-C.

  It seemed like things used to work fine before I upgraded this system
  from Ubuntu 19.10 to 20.04, although I couldn't say for certain at
  this point. But I'm having a ton of difficulty getting audio output
  over HDMI. Getting it to work requires a lot of retries to
  reinitialize the device (either by suspending/resuming the laptop, or
  plugging/unplugging the HDMI cable and/or the multiport adapter). It
  does work sometimes, but my success rate is very low at this point.

  Even when it does work, it's brittle: any change to the output port
  (to speaker and back to HDMI, or from stereo to surround and back)
  will often break the audio. This fact seems to suggest that the
  problem doesn't have anything to do with the low-level initialization
  of the HDMI port; I'd be looking at some mid-layer code.

  To be clear, there doesn't seem to be any particular symptom, or
  anything of interest in the logs, other than an absence of sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Uname: Linux 5.6.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
   /dev/snd/pcmC0D9p:   nbryant1510 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 17:32:11 2020
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded.
   May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails 
after a while
  UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 8087:0026 Intel Corp. 
   Bus 003 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=caffa21a-82f2-4555-a416-67926241525a ro cma=64M

[Kernel-packages] [Bug 1886814] Comment bridged from LTC Bugzilla

--- Comment From andreas.kreb...@de.ibm.com 2020-07-21 08:57 EDT---
Stefan Liebler (our Glibc guy) is having a look. He managed to reproduce it on 
his system.

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

2020-07-21 Thread Kai-Heng Feng

Can you please swap the affected device with the Ugreen one:
[2.723884] usb 2-3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[2.744892] usb 2-3: New USB device found, idVendor=174c, idProduct=55aa,
bcdDevice= 1.00
[2.745705] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[2.746493] usb 2-3: Product: Ugreen Storage Device
[2.747282] usb 2-3: Manufacturer: Ugreen
[2.748056] usb 2-3: SerialNumber: DEF0

Because this one connects to the xHC directly.

USB Storage may draw more power, so the issue you are seeing can happen
when it connects under a USB Hub.

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

Title:
high speed data to usb disk makes the kernel think that is has been
unmounted

Status in linux package in Ubuntu:
Confirmed

Bug description:
Description:

A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.

Symptoms and how to reproduce:

1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.

3) Fill RAM with programs and make sure the swap to this disk is used.

Bug found in:

$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44

Hardware:

Tested with slower and faster computers. Tested directly connected to
a computer and via a hub. They all reproduce this bug.

Workaround:

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

[Kernel-packages] [Bug 1875150] Re: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged

2020-07-21 Thread Dominik

Very well. I’m now running the Logitech receiver on Mint 20 and the
kernel is 5.4.0-40-generic from Ubuntu and it works fine.

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

Title:
  Mouse and keyboard intermittently stop working until Logitech Unifying
  Receiver is replugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse is MX Anywhere 2, the keyboard is K750.

  If the system is booted with the Logitech Unifying Receiver plugged
  in, the keyboard and mouse will keep losing connection. This is most
  visible after a short inactivity, i.e. I start typing and nothing
  appears on screen for a couple of seconds, or I start moving the mouse
  and the cursor takes a couple of seconds to start moving. This also
  happens while I'm using the input device, as I was typing this
  paragraph the keyboard cut out twice for a second or two.

  Additionally, every second time the mouse reconnects, scrolling via
  the scroll wheel is painfully slow.

  When this is going on, dmesg gets once in some seconds:

  [  381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8

  I guess it happens when the mouse reconnects.

  This can be fixed by unplugging and replugging the Unifying Receiver.
  This fixes the problem until next boot.

  I tried a couple of older kernel versions and the same thing happened.
  I also just tried Fedora 32 beta and it didn't happen there.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  domin  2235 F pulseaudio
   /dev/snd/controlC0:  domin  2235 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 26 10:25:57 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-12 (926 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  MachineType: Apple Inc. MacBookPro6,2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b 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: Upgraded to focal on 2020-03-26 (30 days ago)
  WifiSyslog:
   
  dmi.bios.date: 08/07/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.005A.B00.1708072217
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1875150] Re: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged

2020-07-21 Thread Kai-Heng Feng

Fedora doesn't stick to a single kernel version so knowing the exact
kernel was used is important.

But anyway, I won't be able to help here.

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

Title:
  Mouse and keyboard intermittently stop working until Logitech Unifying
  Receiver is replugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse is MX Anywhere 2, the keyboard is K750.

  If the system is booted with the Logitech Unifying Receiver plugged
  in, the keyboard and mouse will keep losing connection. This is most
  visible after a short inactivity, i.e. I start typing and nothing
  appears on screen for a couple of seconds, or I start moving the mouse
  and the cursor takes a couple of seconds to start moving. This also
  happens while I'm using the input device, as I was typing this
  paragraph the keyboard cut out twice for a second or two.

  Additionally, every second time the mouse reconnects, scrolling via
  the scroll wheel is painfully slow.

  When this is going on, dmesg gets once in some seconds:

  [  381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8

  I guess it happens when the mouse reconnects.

  This can be fixed by unplugging and replugging the Unifying Receiver.
  This fixes the problem until next boot.

  I tried a couple of older kernel versions and the same thing happened.
  I also just tried Fedora 32 beta and it didn't happen there.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  domin  2235 F pulseaudio
   /dev/snd/controlC0:  domin  2235 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 26 10:25:57 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-12 (926 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  MachineType: Apple Inc. MacBookPro6,2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b 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: Upgraded to focal on 2020-03-26 (30 days ago)
  WifiSyslog:
   
  dmi.bios.date: 08/07/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.005A.B00.1708072217
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted

2020-07-21 Thread Patrik Nilsson

Kernel parameter does not change the behavior.

$ lsusb
Bus 002 Device 008: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s 
bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
[...]
Bus 002 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya 
Technology Corp.) Flash Drive
[...]

It is the SATA bridge that fails:

$ cat /etc/default/grub
[..]
GRUB_CMDLINE_LINUX_DEFAULT="usb-storage.quirks=174c:55aa:u"
[...]

Update grub. Reboot.

$ dmesg | grep -i uas
[2.491166] usbcore: registered new interface driver uas
[5.045577] usb 2-4.4.4.4.2: UAS is blacklisted for this device, using 
usb-storage instead

Kernel parameter tested with:
Linux 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
Linux 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux

Both fails.


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

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

Title:
  high speed data to usb disk makes the kernel think that is has been
  unmounted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  When the speed of data with a usb disk device is too high, the probes
  that check if the disk still exists is missed. This makes the disk to
  be unmounted and is remounted with an other drive letter (/dev/sdX).
  If this disk is the root ("/"), the computer hangs.

  A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
  easily. This has never happened with a mechanical USB-drive.

  Symptoms and how to reproduce:

  1) (Disk mounted as root) Computer hangs. Only way to get started
  again is a hard reset.

  2) (Erasing disk, not mounted as root) If you erase a disk with dd
  ("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
  list and reappears as an other drive letter. In my case the data is
  redirected to /dev/null and the fans speed up. The apparent data
  transfer speed is also increased. Usually this happens after about 45
  to 60 minutes.

  3) Fill RAM with programs and make sure the swap to this disk is used.

  Bug found in:

  $ uname -a
  Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  $ cat /proc/version_signature
  Ubuntu 5.4.0-40.44-generic 5.4.44

  Hardware:

  Tested with slower and faster computers. Tested directly connected to
  a computer and via a hub. They all reproduce this bug.

  Workaround:

  None found.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   6813 F pulseaudio
   /dev/snd/controlC0:  user   6813 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  MachineType: ASUSTeK COMPUTER INC. GL503VM
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  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
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:

  _MarkForUpload: False
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VM.314
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1875150] Re: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged

2020-07-21 Thread Dominik

Seriously? Here: https://is.gd/WbeePm

I’m just going to take a wild guess here and say perhaps it’s not the
kernel.

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

Title:
  Mouse and keyboard intermittently stop working until Logitech Unifying
  Receiver is replugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse is MX Anywhere 2, the keyboard is K750.

  If the system is booted with the Logitech Unifying Receiver plugged
  in, the keyboard and mouse will keep losing connection. This is most
  visible after a short inactivity, i.e. I start typing and nothing
  appears on screen for a couple of seconds, or I start moving the mouse
  and the cursor takes a couple of seconds to start moving. This also
  happens while I'm using the input device, as I was typing this
  paragraph the keyboard cut out twice for a second or two.

  Additionally, every second time the mouse reconnects, scrolling via
  the scroll wheel is painfully slow.

  When this is going on, dmesg gets once in some seconds:

  [  381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8
  [  769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8

  I guess it happens when the mouse reconnects.

  This can be fixed by unplugging and replugging the Unifying Receiver.
  This fixes the problem until next boot.

  I tried a couple of older kernel versions and the same thing happened.
  I also just tried Fedora 32 beta and it didn't happen there.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  domin  2235 F pulseaudio
   /dev/snd/controlC0:  domin  2235 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 26 10:25:57 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-12 (926 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  MachineType: Apple Inc. MacBookPro6,2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b 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: Upgraded to focal on 2020-03-26 (30 days ago)
  WifiSyslog:
   
  dmi.bios.date: 08/07/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.005A.B00.1708072217
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Tags added: fritz usb wlan

** Summary changed:

-  FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic 
+ FRITZ!WLAN USB Stick v2 does not work with Linux version 4.4.0-186-generic 
(Last working version 4.4.0-185-generic and 4.4.0-184-generic)

** Summary changed:

- FRITZ!WLAN USB Stick v2 does not work with Linux version 4.4.0-186-generic 
(Last working version 4.4.0-185-generic and 4.4.0-184-generic)
+ FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with Linux 
version 4.4.0-186-generic (Last working version 4.4.0-185-generic and 
4.4.0-184-generic)

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-21 Thread Julian Andres Klode

Andreas, I've not gotten it more isolated, the minimum I had was running
debian/tests/gnome-desktop-testing in a flatpak-builder source tree (apt
source/pull-lp-source flatpak-builder).

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "dmesg for the non working version"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394603/+files/dmesg.log

** Attachment removed: "dmesg of failing kernel - module not loaded/detected"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394601/+files/foo

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "version (for the non-working kernel)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394606/+files/version.log

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "uname -a (for the non-working kernel)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394605/+files/uname-a.log

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

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

This change was made by a bot.

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

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "lspci for the non working version"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394602/+files/lspci-vvnn.log

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

Title:
  FRITZ!WLAN USB Stick v2 (Product: FRITZ!WLAN N2.4) does not work with
  Linux version 4.4.0-186-generic (Last working version
  4.4.0-185-generic and 4.4.0-184-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "uname -a"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394597/+files/version.log

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

Title:
   FRITZ!WLAN USB Stick v2 does not work with inux version
  4.4.0-186-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04

2020-07-21 Thread Didi Kohen

I think I have the same issue (or a very similar one), the probe
workaround works, the udev one does not, can I help investigate this?

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

Title:
  Failed to init Intel sound card in 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing current 20.04 release on ThinkBook 13s IML with Intel
  audio card there is no sound available because sound card not detected
  (only dummy output available in sound settings):

  $ alsamixer 
  cannot open mixer: No such file or directory

  $ lspci -nnk |grep -A2 audio
  lspci: Unable to load libkmod resources: error -12
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]
Subsystem: Lenovo Device [17aa:3816]
Kernel driver in use: sof-audio-pci
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
Subsystem: Lenovo Device [17aa:3819]

  $ pacmd list-cards 
  0 card(s) available.

  $ dmesg |grep sof
  [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB)
  [2.142149] systemd[1]: Mounting Mount unit for software-boutique, 
revision 54...
  [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 
54.
  [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine 
driver found
  [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode
  [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5
  [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cnl.ri failed with error -2
  [2.817054] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cnl.ri failed err: -2
  [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2

  I've found similar bug reported here:
  https://bugs.archlinux.org/task/64720

  As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot
  options and after that sound card successfully detected and started
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb 26 19:22:05 2020
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200221)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CQCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 13s-IML
  dmi.modalias: 
dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML:
  dmi.product.family: ThinkBook 13s-IML
  dmi.product.name: 20RR
  dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML
  dmi.product.version: Lenovo ThinkBook 13s-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic

** Attachment added: "dmesg (Currently working kernel - module is loaded)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888385/+attachment/5394600/+files/dmesg.log

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

Title:
   FRITZ!WLAN USB Stick v2 does not work with inux version
  4.4.0-186-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Dear all,

  the USB WLAN Stick (FRITZ!WLAN USB Stick v2) worked flawlessly up to
  the Linux Kernel version 4.4.0-185-generic, so I assume some problem
  has been introduced moving from Linux version 4.4.0-185-generic to the
  Linux version 4.4.0-186-generic.

  Operating system and release can be found below.

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  Attached are the files for the currently working version
  (4.4.0-185-generic): dmesg, version signature, lspci and uname
  output).

  I provide too the dmesg output of the failing kernel version
  (4.4.0-185-generic). I am happy to provide more details. Apparently
  the module is not loaded anymore.

  Kind regards,
  Stephan

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

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

[Kernel-packages] [Bug 1888385] Re: FRITZ!WLAN USB Stick v2 does not work with inux version 4.4.0-186-generic