date:20210208

You have been subscribed to a public bug:

Mellanox Connect-X 5 network card

When using geneve overlay networks over a vlan interface, txvlan offload
currently has to be disabled as it interferes with the network traffic
causing general wonkyness.

Mellanox engineering pointed us at:

  https://www.spinics.net/lists/netdev/msg711911.html

as a likely fix for this issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb  3 15:34:23 2021
ProcEnviron:
 TERM=screen-256color-bce
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress

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


** Tags: amd64 apport-bug focal patch ps5 uec-images
-- 
geneve overlay network on vlan interface broken with offload enabled
https://bugs.launchpad.net/bugs/1914447
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 1914447] Re: geneve overlay network on vlan interface broken with offload enabled

2021-02-08 Thread Stefan Bader

Thanks for the feedback Frode. Just to explain further modifications to
this bug report. For SRU this will be targeted at the 20.10/Groovy 5.8
kernel. When it lands there it will automatically be included in the
next 20.04/Focal HWE kernel.

The patch comes from upstream v5.11-rc3, so it should be included in the
final 21.04/Hirsute kernel.

** Package changed: linux-hwe-5.8 (Ubuntu) => linux (Ubuntu)

** No longer affects: linux (Ubuntu Focal)

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

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

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

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Stefan Bader (smb)

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  geneve overlay network on vlan interface broken with offload enabled

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Groovy:
  In Progress

Bug description:
  Mellanox Connect-X 5 network card

  When using geneve overlay networks over a vlan interface, txvlan
  offload currently has to be disabled as it interferes with the network
  traffic causing general wonkyness.

  Mellanox engineering pointed us at:

https://www.spinics.net/lists/netdev/msg711911.html

  as a likely fix for this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  3 15:34:23 2021
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

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

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

[Kernel-packages] [Bug 1915003] Re: Always update the initramfs when changing power profile

2021-02-08 Thread Alex Tu

** Also affects: nvidia-drivers-ubuntu
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  New
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

Bug description:
  The different power profiles require loading the nvidia drivers with
  different options (or blacklisting them, in case of intel mode).

  We need to call update-initramfs whenever we switch to a different
  profile, or things may fall out sync, resulting in a failure.

  The update-initramfs command takes a few seconds, therefore we also
  need to provide feedback, so that users know that they have to wait
  for the operation to complete. For this reason, prime-select will
  provide a spinner on the command line, and nvidia-settings will show a
  progress dialog.

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

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

[Kernel-packages] [Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled

2021-02-08 Thread Stefan Bader

** Description changed:

+ [SRU Justification]
+ 
+ Impact: In upstream v5.2 geneve tunnel stateless offload support was
+ added to the mlx5 driver. This had some issue with VLANs where the VLAN
+ ID was set by the driver even when offload support was enabled.
+ 
+ Fix: Upstream (v5.11-rc3) commit
+ 378d3783412e38dc3a2b9d524f551c0008ea314a "net/mlx5e: Fix SWP offsets
+ when vlan inserted by driver" was backported (dropping some code because
+ it did not yet exist in 5.8) and verified to address the problem.
+ 
+ Testcase: Enable geneve tunnel offload support on a mlx5(e) card over
+ VLAN.
+ 
+ Regression potential: The modified code path is sending packets tagged
+ for VLAN(s), so outgoing traffic into VLAN(s) would most likely be
+ impacted.
+ 
+ --- original description ---
+ 
  Mellanox Connect-X 5 network card
  
  When using geneve overlay networks over a vlan interface, txvlan offload
  currently has to be disabled as it interferes with the network traffic
  causing general wonkyness.
  
  Mellanox engineering pointed us at:
  
-   https://www.spinics.net/lists/netdev/msg711911.html
+   https://www.spinics.net/lists/netdev/msg711911.html
  
  as a likely fix for this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  3 15:34:23 2021
  ProcEnviron:
-  TERM=screen-256color-bce
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color-bce
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

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

Title:
  geneve overlay network on vlan interface broken with offload enabled

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Groovy:
  In Progress

Bug description:
  [SRU Justification]

  Impact: In upstream v5.2 geneve tunnel stateless offload support was
  added to the mlx5 driver. This had some issue with VLANs where the
  VLAN ID was set by the driver even when offload support was enabled.

  Fix: Upstream (v5.11-rc3) commit
  378d3783412e38dc3a2b9d524f551c0008ea314a "net/mlx5e: Fix SWP offsets
  when vlan inserted by driver" was backported (dropping some code
  because it did not yet exist in 5.8) and verified to address the
  problem.

  Testcase: Enable geneve tunnel offload support on a mlx5(e) card over
  VLAN.

  Regression potential: The modified code path is sending packets tagged
  for VLAN(s), so outgoing traffic into VLAN(s) would most likely be
  impacted.

  --- original description ---

  Mellanox Connect-X 5 network card

  When using geneve overlay networks over a vlan interface, txvlan
  offload currently has to be disabled as it interferes with the network
  traffic causing general wonkyness.

  Mellanox engineering pointed us at:

    https://www.spinics.net/lists/netdev/msg711911.html

  as a likely fix for this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  3 15:34:23 2021
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

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

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

[Kernel-packages] [Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled

2021-02-08 Thread Andrew Cloke

Waiting to close as "Fix Released" once the 5.10 kernel has landed in
hirsute. 5.10 kernel is currently in hirsute -proposed.

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

Title:
  5.10 kernel fails to boot with secure boot disabled

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Canonical requests to test the secure boot for the 5.10 kernel but
  kernel fails to boot with secure boot disabled.

  The 5.10 kernel can be found in:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap

  They can be installed by installing the linux-generic-wip package with
  this PPA enabled. As usual, they are only signed using a key specific to
  that PPA. This key can be retrieved from the signing tarballs for the
  kernels, e.g.:

  http://ppa.launchpad.net/canonical-kernel-
  
team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz

  Our tester installed the 5.10 kernel via aptitude.
  If booting directly from the bootmenu, it stucks at:
  "kexec_core: Starting new kernel"

  If booting recovery kernel for 5.10.0, it proceeds farther and after 
kexec_core, it failed at: 
  "
  [0.029830] LSM: Security Framework initializing
  [0.029916] Yama: b
  "

  Two attempts with a different scenario; running with 5.8 kernel and boot via 
commandline for 5.10:
  kexec -l /boot/vmlinux-5.10.0-0-generic 
--initrd=/boot/initrd.img-5.10.0-0-generic 
--append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash"
  kexec -e

  Both attempts also failed while rebooting, once with the same error as
  the error from booting with bootmenu; the other failure occurred a lot
  earlier.

  Wondering what new CONFIGs and/or features for the 5.10 kernel?

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

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

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

2021-02-08 Thread Pat Viafore

As an update to this bug:

The work to SRU has stalled, as we have found a regression
(https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1902260).
Once a fix is SRU'd to Groovy, I'll pick up the fix and SRU it back to
Focal.

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

Title:
  initramfs does not get loaded

Status in cloud-images:
  Confirmed
Status in grub2 package in Ubuntu:
  Won't Fix
Status in linux-azure package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Triaged
Status in grub2 source package in Focal:
  Confirmed
Status in linux-azure source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions

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

[Kernel-packages] [Bug 1915036] [NEW] Unable to suspend under nouveau driver on kernel 5.8.0-41.46

2021-02-08 Thread Julian Fairfax

Public bug reported:

cat /proc/version_signature:
Ubuntu 5.8.0-41.46-generic 5.8.18

sudo lspci -vnvn:
00:00.0 Host bridge [0600]: NVIDIA Corporation MCP89 HOST Bridge [10de:0d60] 
(rev a1)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Subsystem: NVIDIA Corporation Device [10de:]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
Address: fee01004  Data: 4021
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed-
Mapping Address Base: fee0
Capabilities: [80] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <512ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 0.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg+
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState+
RootCap: CRSVisible-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Kernel driver in use: pcieport

00:17.0 PCI bridge [0604]: NVIDIA Corporation MCP89 PCI Express Bridge 
[10de:0d76] (rev a1) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Subsystem: NVIDIA Corporation MCP89 PCI Express 
Bridge [10de:]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 

01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43224 
802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Apple Inc. AirPort Extreme [106b:0093]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
SlotPowerLimit 0.000W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <4us, L1 <64us
ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommC

[Kernel-packages] [Bug 1915036] 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/1915036

Title:
  Unable to suspend under nouveau driver on kernel 5.8.0-41.46

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cat /proc/version_signature:
  Ubuntu 5.8.0-41.46-generic 5.8.18

  sudo lspci -vnvn:
  00:00.0 Host bridge [0600]: NVIDIA Corporation MCP89 HOST Bridge [10de:0d60] 
(rev a1)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Subsystem: NVIDIA Corporation Device [10de:]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
Address: fee01004  Data: 4021
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed-
Mapping Address Base: fee0
Capabilities: [80] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <512ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 0.000W; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg+
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState+
RootCap: CRSVisible-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Kernel driver in use: pcieport

  00:17.0 PCI bridge [0604]: NVIDIA Corporation MCP89 PCI Express Bridge 
[10de:0d76] (rev a1) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Subsystem: NVIDIA Corporation MCP89 PCI Express 
Bridge [10de:]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 

  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43224 
802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Apple Inc. AirPort Extreme [106b:0093]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
SlotPowerLimit 0.000W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-

[Kernel-packages] [Bug 1915003] Re: Always update the initramfs when changing power profile

2021-02-08 Thread Alberto Milone

** Changed in: nvidia-settings (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

Bug description:
  The different power profiles require loading the nvidia drivers with
  different options (or blacklisting them, in case of intel mode).

  We need to call update-initramfs whenever we switch to a different
  profile, or things may fall out sync, resulting in a failure.

  The update-initramfs command takes a few seconds, therefore we also
  need to provide feedback, so that users know that they have to wait
  for the operation to complete. For this reason, prime-select will
  provide a spinner on the command line, and nvidia-settings will show a
  progress dialog.

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

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

[Kernel-packages] [Bug 1915051] [NEW] dkms-autopkgtest: Also select binary packages that depends on dkms for testing

2021-02-08 Thread Marcelo Cerri

Public bug reported:

[Impact]

The current version of dkms-autopkgtest in 20.04 and later only selects
binary packages with names ending with "-dkms" for its automatic DKMS
test. With that packages suchs bcml-kernel-source and nvidia drivers are
not being tested automatically by autopkgtest.

[Test Case]

Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
0ubuntu5) and the 5.8 kernel and even with this version of the driver
failing to build with the 5.8 kernel, the test succeeds. The expected
behavior, is that that dkms-autopkgtest should fail in this case.

[Where problems could occur]

The main issue that we can have here is selecting additional packages
for the DKMS test that are not DKMS packages.

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

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

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

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

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

2021-02-08 Thread Marcelo Cerri

** Also affects: dkms (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: dkms (Ubuntu Focal)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: dkms (Ubuntu Groovy)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: dkms (Ubuntu Hirsute)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: dkms (Ubuntu Focal)
   Status: New => Triaged

** Changed in: dkms (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: dkms (Ubuntu Focal)
   Status: Triaged => In Progress

** Changed in: dkms (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: dkms (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: dkms (Ubuntu Hirsute)
   Importance: Undecided => High

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

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  In Progress
Status in dkms source package in Focal:
  In Progress
Status in dkms source package in Groovy:
  In Progress
Status in dkms source package in Hirsute:
  In Progress

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

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

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

2021-02-08 Thread rubo77

You can close VLC or just jump to another time location in the video
then the log-spam will stop too.

Workaround:
https://unix.stackexchange.com/a/633378/20661

-- 
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 hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

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

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

[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing

2021-02-08 Thread Marcelo Cerri

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982315

** Bug watch added: Debian Bug tracker #982315
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982315

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

Title:
  dkms-autopkgtest: Also select binary packages that depends on dkms for
  testing

Status in dkms package in Ubuntu:
  In Progress
Status in dkms source package in Focal:
  In Progress
Status in dkms source package in Groovy:
  In Progress
Status in dkms source package in Hirsute:
  In Progress

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later only
  selects binary packages with names ending with "-dkms" for its
  automatic DKMS test. With that packages suchs bcml-kernel-source and
  nvidia drivers are not being tested automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom-
  0ubuntu5) and the 5.8 kernel and even with this version of the driver
  failing to build with the 5.8 kernel, the test succeeds. The expected
  behavior, is that that dkms-autopkgtest should fail in this case.

  [Where problems could occur]

  The main issue that we can have here is selecting additional packages
  for the DKMS test that are not DKMS packages.

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

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

[Kernel-packages] [Bug 1915063] [NEW] Windows 10 wil not install using qemu-system-x86_64

Public bug reported:

Steps to reproduce
install virt-manager and ovmf if nopt already there
copy windows and virtio iso files to /var/lib/libvirt/images

Use virt-manager from local machine to create your VMs with the disk, CPUs and 
memory required
Select customize configuration then select OVMF(UEFI) instead of seabios
set first CDROM to the windows installation iso (enable in boot options)
add a second CDROM and load with the virtio iso
change spice display to VNC

  Always get a security error from windows and it fails to launch the installer 
(works on RHEL and Fedora)
I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of no 
help

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

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help

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

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

[Kernel-packages] [Bug 1915063] 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 1915063

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

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help

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

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

[Kernel-packages] [Bug 1912946] Re: [ThinkPad E14 Gen2] Closing the lid does not trigger system suspend

2021-02-08 Thread Evgenii Shatokhin

Fn keys, reaction to lid close and reporting of battery state start
working OK after suspend-to-ram and waking up the system. So, as a
temporary workaround, I added 2-second suspend operation to run at each
boot, as suggested here:
https://forums.lenovo.com/topic/findpost/27/5027791/5148559:

/etc/crontab:
--
<...>
@reboot root rtcwake -m mem -s 2
--

Ugly, but it works for me.


As alternative workaround, it was suggested to use a custom ACPI DSDT
table: https://github.com/masksshow/Thinkpad-E14-15-AMD-Gen-2-FIX.

Looks like the script from that github repo does the following:
* Dumps ACPI DSDT table and decodes it
* Replaces "Name (H8DR, 0x00)" with "Name (H8DR, One)" there
* Encodes the corrected table
* Instructs GRUB to use it at boot.

I haven't tried that.

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

Title:
  [ThinkPad E14 Gen2] Closing the lid does not trigger system suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  According to the system settings (see the attached screenshot), the
  laptop should go to sleep (suspend to RAM) when I close the lid.
  However, closing the lid has no visible effect.

  'systemctl suspend' works OK, choosing 'Leave' -> 'Sleep' in the menu
  works too.

  After suspend and resume, closing the lid starts working as expected
  and is triggering suspend to RAM. So this might be related to BIOS,
  ACPI or something similar.

  I am filing this bug against 'linux' package because, perhaps, a quirk
  could be added in the kernel as a workaround. IIRC, the kernel had a
  number of quirks to work around BIOS/ACPI problems.

  A similar issue exists with Fn keys on this machine: they do not work
  after a boot but start working after I have suspended and resumed the
  system (checked with Fn+F5/F6 - brightness down/up). Others
  encountered that too (see [1], [2] below). I suspect it is caused by
  the same bug in BIOS or ACPI.

  ThinkPad E14 Gen2 with AMD Ryzen 5 4500U
  Machine type model: 20T60030RT

  UEFI BIOS ver: R1AET33W (1.09), the latest version at the moment
  Embedded controller FW ver. R1AHT33W (1.09)

  SecureBoot: off

  OS: Ubuntu 20.10 amd64

  Kernel 5.8.0-40-generic.
  I have also tried the builds of the newer mainline kernels:
  * 5.9.0-050900-generic from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/
  * 5.10.0-051000-generic from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/amd64/
  The issues with lid closing and Fn keys show up there too.
  

  [1] 
https://askubuntu.com/questions/1289640/fn-key-doesnt-work-in-ubuntu-20-04-on-lenovo-thinkpad-e14
  [2] 
https://forums.lenovo.com/t5/Other-Linux-Discussions/Linux-Fn-keys-not-working-Thinkpad-E14-AMD-Gen-2/m-p/5027791

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-40-generic 5.8.0-40.45
  ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alina  1059 F pulseaudio
alina  1062 F pipewire-media-
   /dev/snd/controlC0:  alina  1062 F pipewire-media-
   /dev/snd/seq:alina  1058 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Jan 24 17:09:34 2021
  InstallationDate: Installed on 2021-01-18 (6 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20T60030RT
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=1b0f22fc-c314-411c-87c4-ef7e71326576 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-40-generic N/A
   linux-backports-modules-5.8.0-40-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T60030RT
  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: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET33W(1.09):bd10/26/2020:br1.9:efr1.9:svnLENOVO:pn20T60030RT:pvrThinkPadE14Gen2:rvnLENOVO:rn20T60030RT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T60030RT
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2021-02-08 Thread Ruiter Gripp

** Also affects: linux-signed-hwe-5.8 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64

apport information

** Tags added: apport-collected focal

** Description changed:

  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images
  
  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC
  
Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.14
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-01-20 (19 days ago)
+ InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
+ MachineType: LENOVO 30E102Z
+ NonfreeKernelModules: nvidia_modeset nvidia
+ 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 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
+ RelatedPackageVersions:
+  linux-restricted-modules-5.6.0-1042-oem N/A
+  linux-backports-modules-5.6.0-1042-oem  N/A
+  linux-firmware  1.187.8
+ RfKill:
+  
+ Tags:  focal
+ Uname: Linux 5.6.0-1042-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/29/2020
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: S07KT08A
+ dmi.board.name: 1046
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
+ dmi.product.family: INVALID
+ dmi.product.name: 30E102Z
+ dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
+ dmi.product.version: ThinkStation P620
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461380/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1915063/+attachment/5461382/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1915063] AudioDevicesInUse.txt

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461381/+files/AudioDevicesInUse.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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1915063] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461388/+files/Lsusb-t.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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1915063/+attachment/5461387/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1915063] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461386/+files/Lspci-vt.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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461383/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461393/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461391/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1915063] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461397/+files/acpidump.txt

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

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

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461396/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461390/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461394/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461384/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1915063/+attachment/5461395/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1915063] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461389/+files/Lsusb-v.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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1915063/+attachment/5461392/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1915063/+attachment/5461385/+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/1915063

Title:
  Windows 10 wil not install using qemu-system-x86_64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  install virt-manager and ovmf if nopt already there
  copy windows and virtio iso files to /var/lib/libvirt/images

  Use virt-manager from local machine to create your VMs with the disk, CPUs 
and memory required
  Select customize configuration then select OVMF(UEFI) instead of seabios
  set first CDROM to the windows installation iso (enable in boot options)
  add a second CDROM and load with the virtio iso
change spice display to VNC

Always get a security error from windows and it fails to launch the 
installer (works on RHEL and Fedora)
  I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of 
no help
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (19 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201030-14:39
  MachineType: LENOVO 30E102Z
  NonfreeKernelModules: nvidia_modeset nvidia
  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 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem 
root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1042-oem N/A
   linux-backports-modules-5.6.0-1042-oem  N/A
   linux-firmware  1.187.8
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.6.0-1042-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S07KT08A
  dmi.board.name: 1046
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: INVALID
  dmi.product.name: 30E102Z
  dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620
  dmi.product.version: ThinkStation P620
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled

2021-02-08 Thread pauldoo

A code fix has been identified, and I confirm that it works on my Lenovo
E595 when I build my own kernel with the fix included.  See the Kernel
bugzilla for details: https://bugzilla.kernel.org/show_bug.cgi?id=207841

What are the next steps to getting this upstreamed and/or included in
the Ubuntu 20.04 kernels?

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

Title:
  Fn Lock light does not come on to indicate when Fn Lock is enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo E595 running Ubuntu 20.04. The "Fn Lock" feature on
  the keyboard works in terms of how it modifies subsequent presses of
  the F1-F12 keys, but the little light on the Esc key doesn't show the
  current state.

  Example:
  1. I press F5 a few times, and the screen brightness is adjusted.
  2. I press Fn+Esc, and "Fn Lock" is now on, but the light hasn't changed.
  3. I press F5 again, or several times, and it acts as a normal F5 (ie my 
browser might refresh the page).
  4. I press Fn+Esc again, and "Fn Lock" is now off, but again the light hasn't 
changed.

  So, "Fn Lock" works in the sense that it modifies what keypresses do,
  but the little light on the Esc key doesn't come on. Under Windows the
  light does toggle, to show the current status.

  The behaviour is the same on Xorg and Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.31.36
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2138 F pulseaudio
   /dev/snd/controlC0:  paul   2138 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 21:37:47 2020
  InstallationDate: Installed on 2020-05-13 (14 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20NFCTO1WW
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=UUID=f7c34228-ee6f-4043-931c-f4752ad503c8 ro quiet splash nomodeset 
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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET36W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NFCTO1WW
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E595
  dmi.product.name: 20NFCTO1WW
  dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595
  dmi.product.version: ThinkPad E595
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1910749] Re: stop building nvidia dkms on kernels with no lrm

This bug was fixed in the package linux-gke-5.0 - 5.0.0-1051.53

---
linux-gke-5.0 (5.0.0-1051.53) bionic; urgency=medium

  * bionic/linux-gke-5.0: 5.0.0-1051.53 -proposed tracker (LP: #1913777)

  * stop building nvidia dkms on kernels with no lrm (LP: #1910749)
- [Packaging]: Stop building nvidia dkms

  [ Ubuntu: 5.0.0-65.71 ]

  * bionic/linux-hwe-5.0: 5.0.0-65.71 -proposed tracker (LP: #1913774)
  * CVE-2020-28374
- scsi: target: Fix XCOPY NAA identifier lookup
  * stop building nvidia dkms on kernels with no lrm (LP: #1910749)
- [Packaging]: Stop building nvidia dkms

  [ Ubuntu: 5.0.0-64.70 ]

  * bionic/linux-hwe-5.0: 5.0.0-64.70 -proposed tracker (LP: #1910077)
  * Update kernel packaging to support forward porting kernels (LP: #1902957)
- [Debian] Update for leader included in BACKPORT_SUFFIX

 -- Thadeu Lima de Souza Cascardo   Tue, 02 Feb
2021 08:51:11 -0300

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

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

** Changed in: linux-hwe-5.0 (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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1910749

Title:
  stop building nvidia dkms on kernels with no lrm

Status in linux package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-hwe-5.0 package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-hwe-5.0 source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  Fix Released
Status in linux-hwe-5.0 source package in Bionic:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-oracle source package in Bionic:
  New

Bug description:
  [Impact]
  Building these modules wastes build time, and also may potentially lead to 
unnecessary updates.

  [Fix]
  Set do_dkms_nvidia = false on amd64.mk.

  [Test case]
  Build test the kernel.

  [Potential regression]
  Missing signed bits for these modules, in case someone uses them without LRMs.

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

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

[Kernel-packages] [Bug 1910749] Re: stop building nvidia dkms on kernels with no lrm

This bug was fixed in the package linux-hwe-5.0 - 5.0.0-65.71

---
linux-hwe-5.0 (5.0.0-65.71) bionic; urgency=medium

  * bionic/linux-hwe-5.0: 5.0.0-65.71 -proposed tracker (LP: #1913774)

  * CVE-2020-28374
- scsi: target: Fix XCOPY NAA identifier lookup

  * stop building nvidia dkms on kernels with no lrm (LP: #1910749)
- [Packaging]: Stop building nvidia dkms

 -- Thadeu Lima de Souza Cascardo   Mon, 01 Feb
2021 19:04:45 -0300

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

Title:
  stop building nvidia dkms on kernels with no lrm

Status in linux package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-hwe-5.0 package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-hwe-5.0 source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux-oracle source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  Fix Released
Status in linux-hwe-5.0 source package in Bionic:
  Fix Released
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-oracle source package in Bionic:
  New

Bug description:
  [Impact]
  Building these modules wastes build time, and also may potentially lead to 
unnecessary updates.

  [Fix]
  Set do_dkms_nvidia = false on amd64.mk.

  [Test case]
  Build test the kernel.

  [Potential regression]
  Missing signed bits for these modules, in case someone uses them without LRMs.

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

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

[Kernel-packages] [Bug 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation

This bug was fixed in the package linux-hwe-5.8 - 5.8.0-43.49~20.04.1

---
linux-hwe-5.8 (5.8.0-43.49~20.04.1) focal; urgency=medium

  * focal/linux-hwe-5.8: 5.8.0-43.49~20.04.1 -proposed tracker (LP:
#1914688)

  [ Ubuntu: 5.8.0-43.49 ]

  * groovy/linux: 5.8.0-43.49 -proposed tracker (LP: #1914689)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Exploitable vulnerabilities in AF_VSOCK implementation (LP: #1914668)
- vsock: fix the race conditions in multi-transport support

 -- Kleber Sacilotto de Souza   Fri, 05 Feb
2021 10:18:10 +0100

** Changed in: linux-hwe-5.8 (Ubuntu Focal)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Groovy)
   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/1914668

Title:
  Exploitable vulnerabilities in AF_VSOCK implementation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  https://www.openwall.com/lists/oss-security/2021/02/04/5

  The following mainline patch is required for all kernels >= v5.8:
  {focal hwe-5.8, groovy, hirsute}:

  [linux] c518adafa39f vsock: fix the race conditions in multi-transport
  support

  or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
  multi-transport support

  
  [Impact]

   * Patches an exploitable vulnerability.

  [Test Case]

   * See disclosure article.

  [Regression Potential]

   * Low: straightforward race condition fix; upstream cherry-pick.

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

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

[Kernel-packages] [Bug 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation

This bug was fixed in the package linux - 5.8.0-43.49

---
linux (5.8.0-43.49) groovy; urgency=medium

  * groovy/linux: 5.8.0-43.49 -proposed tracker (LP: #1914689)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * Exploitable vulnerabilities in AF_VSOCK implementation (LP: #1914668)
- vsock: fix the race conditions in multi-transport support

 -- Khalid Elmously   Thu, 04 Feb 2021
21:41:23 -0500

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

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

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

Title:
  Exploitable vulnerabilities in AF_VSOCK implementation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  https://www.openwall.com/lists/oss-security/2021/02/04/5

  The following mainline patch is required for all kernels >= v5.8:
  {focal hwe-5.8, groovy, hirsute}:

  [linux] c518adafa39f vsock: fix the race conditions in multi-transport
  support

  or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
  multi-transport support

  
  [Impact]

   * Patches an exploitable vulnerability.

  [Test Case]

   * See disclosure article.

  [Regression Potential]

   * Low: straightforward race condition fix; upstream cherry-pick.

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

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

[Kernel-packages] [Bug 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation

This bug was fixed in the package linux-riscv - 5.8.0-16.18

---
linux-riscv (5.8.0-16.18) groovy; urgency=medium

  * groovy/linux-riscv: 5.8.0-16.18 -proposed tracker (LP: #1914687)

  [ Ubuntu: 5.8.0-43.49 ]

  * groovy/linux: 5.8.0-43.49 -proposed tracker (LP: #1914689)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Exploitable vulnerabilities in AF_VSOCK implementation (LP: #1914668)
- vsock: fix the race conditions in multi-transport support

  [ Ubuntu: 5.8.0-41.46 ]

  * groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219)
  * Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme
drive fails after some time (LP: #1910866)
- Revert "nvme-pci: remove last_sq_tail"
  * initramfs unpacking failed (LP: #1835660)
- SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around 
initrds.
  * overlay: permission regression in 5.4.0-51.56 due to patches related to
CVE-2020-16120 (LP: #1900141)
- ovl: do not fail because of O_NOATIME

  [ Ubuntu: 5.8.0-40.45 ]

  * Packaging resync (LP: #1786013)
- update dkms package versions

 -- Stefan Bader   Fri, 05 Feb 2021 09:13:11
+0100

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

Title:
  Exploitable vulnerabilities in AF_VSOCK implementation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in linux-hwe-5.8 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  https://www.openwall.com/lists/oss-security/2021/02/04/5

  The following mainline patch is required for all kernels >= v5.8:
  {focal hwe-5.8, groovy, hirsute}:

  [linux] c518adafa39f vsock: fix the race conditions in multi-transport
  support

  or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
  multi-transport support

  
  [Impact]

   * Patches an exploitable vulnerability.

  [Test Case]

   * See disclosure article.

  [Regression Potential]

   * Low: straightforward race condition fix; upstream cherry-pick.

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

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

[Kernel-packages] [Bug 1915082] [NEW] [Macbook7, 1] backlight not working

Public bug reported:

Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 18.04.
Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia drivers.
The apple_backlight directory appears in /sys/class/backlight and while
different brightness values can be set, they have no effect on the backlight's
emitted brightness.
The backlight remains at full brightness.

I have tested the following kernel parameters but they have no effect.

acpi_backlight=vendor
video.use_bios_initial_backlight=0
acpi_osi=
video.use_native_backlight=1

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

** Attachment added: "acpi_backlight=vendor ls sys-class-backlight"

https://bugs.launchpad.net/bugs/1915082/+attachment/5461419/+files/acpi_backlight%3Dvendor%20ls%20sys-class-backlight

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

Title:
[Macbook7,1] backlight not working

Status in linux package in Ubuntu:
Incomplete

Bug description:
Backlight controls do not have any effect on a Macbook7,1 running Ubuntu
18.04.
Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia
drivers.
The apple_backlight directory appears in /sys/class/backlight and while
different brightness values can be set, they have no effect on the backlight's
emitted brightness.
The backlight remains at full brightness.

I have tested the following kernel parameters but they have no effect.

acpi_backlight=vendor
video.use_bios_initial_backlight=0
acpi_osi=
video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ls sys-class-backlight"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461428/+files/ls%20sys-class-backlight

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "dsdt.dsl"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461423/+files/dsdt.dsl

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt3.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461433/+files/ssdt3.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461420/+files/acpidump.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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "results.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461429/+files/results.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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "dsdt.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461422/+files/dsdt.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "fwts method"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461425/+files/fwts%20method

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt1.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461430/+files/ssdt1.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461431/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt5.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461435/+files/ssdt5.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt6.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461436/+files/ssdt6.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "fwts"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461424/+files/fwts

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt2.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461432/+files/ssdt2.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt4.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461434/+files/ssdt4.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "grep -r . proc-acpi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461426/+files/grep%20-r%20.%20proc-acpi

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "dmidecode"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461421/+files/dmidecode

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461427/+files/lspci-vnvn.log

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt7.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461437/+files/ssdt7.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1914949] Re: Resume from suspend not working with i915 driver (linux 5.4 and 5.8)

2021-02-08 Thread Dirk Schulze

** Description changed:

- Using kernel 5.4.0-65, the system does not wake up anymore from suspend to
ram (S3). The screen stays black, only the backlight comes on.
+ Using kernel 5.4.0-65, the system does not wake up anymore from suspend to
ram (S3). The screen stays black, only the backlight comes on.
Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it
shows that this PCI device is the problem:

00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 18)

This is a 1st gen Intel HD graphics (Ironlake)

Testing various versions of kernels 5.4.0.x , I found that the problem seems
to be introduced with 5.4.0-59
Versions after -59 don't wake up, and versions until 5.4.0-58 work fine.
Testing 5.8.0-41, it doesn't wake up.
Testing mainline 5.11.0-051100rc6-generic, it works fine.
- ---
+
+ More testing showed that it is also related to PulseAudio:
+ I have removed this line from /etc/pulse/default.pa:
+ load-module module-suspend-on-idle
+ If I add it again, the system wakes up normally.
+
+ I don't know what this means -- was the pm_trace wrong about the VGA
controller? Is the kernel not suspending the sound device properly before going
to sleep?
+ All the kernels before 5.4.0-59 did not have a problem with this PulseAudio
configuration.
+
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20
HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be
InstallationDate: Installed on 2018-09-11 (879 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic
root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
RelatedPackageVersions:
- linux-restricted-modules-5.4.0-65-generic N/A
- linux-backports-modules-5.4.0-65-generic N/A
- linux-firmware1.187.9
+ linux-restricted-modules-5.4.0-65-generic N/A
+ linux-backports-modules-5.4.0-65-generic N/A
+ linux-firmware1.187.9
Tags: ulyana
Uname: Linux 5.4.0-65-generic x86_64
UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht
installiert ist.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 05/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: HM55-HT
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.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT: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.sku: 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.

** Summary changed:

- Resume from suspend not working with i915 driver (linux 5.4 and 5.8)
+ Resume from suspend not working with i915 driver and PulseAudio (linux 5.4
and 5.8)

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

Title:
Resume from suspend not working with i915 driver and PulseAudio (linux
5.4 and 5.8)

Status in linux package in Ubuntu:
Confirmed

Bug description:
Using kernel 5.4.0-65, the system does not wake up anymore from suspend to
ram (S3). The screen stays black, only the backlight comes on.
Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it
shows that this PCI device is the problem:

00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 18)

This is a 1st gen Intel HD graphics (Ironlake)

More testing showed that it is also related to PulseAudio:
I have removed this line from /etc/pulse/default.pa:
load-module module-suspend-on-idle
If I add it again, the system wakes up normally.

I don't know what this means -- was the pm_trace wrong about the VGA
controller? Is the kernel not suspending the sound device properly before going
to sleep?
All the kern

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

** Attachment added: "ssdt8.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+attachment/5461438/+files/ssdt8.dat

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1915082] 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 1915082

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

2021-02-08 Thread Francis Ginther

Testing of the 460-server driver has passed on bionic, focal and groovy.

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

Title:
  Introduce the new NVIDIA 460-server series and update the 460 series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 460-server series and update the 460 series.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 460-server ==

    * Initial release:
  - Added support for the following GPUs:
  NVIDIA A40
  NVIDIA RTX A6000
  - Added support for CUDA 11.2.

  == 460 ==

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3080 Laptop GPU
  GeForce RTX 3070 Laptop GPU
  GeForce RTX 3060 Laptop GPU
  GeForce GT 1010
  - Updated the NVIDIA driver to restore functionality of some
    features, including runtime power management, hotplugging
    audio-capable display devices, and S0ix-based system suspend,
    with recent kernels such as Linux 5.10.
  - Fixed a bug that caused bindless texture samplers to be
    incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS
    limit.
  - Fixed a bug that could cause the GPU to hang when attempting to
    perform link training on an HDMI 2.1 Fixed Rate Link (FRL)
    display, while the display is powered off.
  - Fixed a bug that could intermittently cause NvFBC applications
    to fail with the error message "Unable to send exported fds".

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

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

[Kernel-packages] [Bug 1915082] Re: [Macbook7, 1] backlight not working

apport information

** Tags added: apport-collected hera

** Description changed:

  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.
  
  I have tested the following kernel parameters but they have no effect.
  
  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.23
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jordan 1659 F pulseaudio
+ CurrentDesktop: Pantheon
+ DistroRelease: elementary OS 5.1.7
+ InstallationDate: Installed on 2021-01-30 (9 days ago)
+ InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
+ MachineType: Apple Inc. MacBook7,1
+ NonfreeKernelModules: nvidia wl
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-65-generic N/A
+  linux-backports-modules-5.4.0-65-generic  N/A
+  linux-firmware1.173.19
+ Tags:  hera
+ Uname: Linux 5.4.0-65-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: sudo
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/02/18
+ dmi.bios.vendor: Apple Inc.
+ dmi.bios.version: MB71.88Z.003F.B00.1802022149
+ dmi.board.name: Mac-F22C89C8
+ dmi.board.vendor: Apple Inc.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Apple Inc.
+ dmi.chassis.version: Mac-F22C89C8
+ dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
+ dmi.product.family: MacBook
+ dmi.product.name: MacBook7,1
+ dmi.product.version: 1.0
+ dmi.sys.vendor: Apple Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461451/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/+b

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461453/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461457/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1915082/+attachment/5461452/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461458/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461461/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461460/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1915082/+attachment/5461456/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461459/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461454/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1915082/+attachment/5461455/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1915082/+attachment/5461463/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

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

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

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

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1915082/+attachment/5461462/+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/1915082

Title:
  [Macbook7,1] backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight controls do not have any effect on a Macbook7,1 running Ubuntu 
18.04.
  Ubuntu is installed in Legacy BIOS mode and uses the proprietary Nvidia 
drivers.
  The apple_backlight directory appears in /sys/class/backlight and while 
different brightness values can be set, they have no effect on the backlight's 
emitted brightness.
  The backlight remains at full brightness.

  I have tested the following kernel parameters but they have no effect.

  acpi_backlight=vendor
  video.use_bios_initial_backlight=0
  acpi_osi=
  video.use_native_backlight=1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1659 F pulseaudio
  CurrentDesktop: Pantheon
  DistroRelease: elementary OS 5.1.7
  InstallationDate: Installed on 2021-01-30 (9 days ago)
  InstallationMedia: elementary OS 5.1 "hera" - stable amd64 (20200814)
  MachineType: Apple Inc. MacBook7,1
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=UUID=6cdd2f7b-d747-4fbc-8062-317304a148a6 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.173.19
  Tags:  hera
  Uname: Linux 5.4.0-65-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/02/18
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB71.88Z.003F.B00.1802022149
  dmi.board.name: Mac-F22C89C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22C89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB71.88Z.003F.B00.1802022149:bd02/02/18:svnAppleInc.:pnMacBook7,1:pvr1.0:rvnAppleInc.:rnMac-F22C89C8:rvr:cvnAppleInc.:ct10:cvrMac-F22C89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook7,1
  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/1915082/+subscriptions

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

[Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA

2021-02-08 Thread Jonathan Dumont

Dear all;

I had the same issue with Kubuntu 20.04LTS, yesterday and during the
installation the bluetooth was working perfectly on my Asus UX305ua
than, this morning, no bluetooth adapter found. I solved it by simply
plugin in (power supply) my laptop. It appear to be an issue with the
power management (energy saving). Something disable the bluetooth
adapter to save energy.

So if you have this issue could you try to replicated the issue by
1. pluging the power cord
2. spinning an ubuntu live-cd

This might help the maintainer/developer to help us :)

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

Title:
  Bluetooth doesn't work on ASUS Zenbook UX301LAA

Status in linux package in Ubuntu:
  Triaged

Bug description:
  It's not possible to make bluetooth work. Pressing Fn+F2 doesn't
  change anything. Sometimes a grey (inactive) bluetooth icon appears
  but disappears instantly after attempt to turn it on.

  WORKAROUND: Set "XHCI Pre-Boot Mode" BIOS option to "Disabled".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-21-generic 4.2.0-21.25
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shadowlmd   2409 F pulseaudio
   /dev/snd/controlC1:  shadowlmd   2409 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec  5 18:03:20 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb
  InstallationDate: Installed on 2015-10-22 (43 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed 
root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-21-generic N/A
   linux-backports-modules-4.2.0-21-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  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/1523108/+subscriptions

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

[Kernel-packages] [Bug 1915003] Re: Always update the initramfs when changing power profile

2021-02-08 Thread Yuan-Chen Cheng

IMHO, shall we have a kernel boot parameter so that the script in the
initrd check and decide what to load and/or parameter to added.

If that's too much work, maybe put that as a long-term goal.

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

Title:
  Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

Bug description:
  The different power profiles require loading the nvidia drivers with
  different options (or blacklisting them, in case of intel mode).

  We need to call update-initramfs whenever we switch to a different
  profile, or things may fall out sync, resulting in a failure.

  The update-initramfs command takes a few seconds, therefore we also
  need to provide feedback, so that users know that they have to wait
  for the operation to complete. For this reason, prime-select will
  provide a spinner on the command line, and nvidia-settings will show a
  progress dialog.

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

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

[Kernel-packages] [Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working

[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/1891100

Title:
  hp notebook 15-da0001nk sound mute led not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , 
the system run flawlessly except the Sound Mute LED on the F6 key. I try many 
solution after a humble search on the net but without success. The output of 
pactl list sinks/lscpi is attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  djalel 2167 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  MachineType: HP HP Laptop 15-da0xxx
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=a4fd6950-d770-40a6-9863-f35146cfaf67 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/02/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd06/02/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.47:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 4BY81EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

2021-02-08 Thread Aksahat

`linux-image-5.8.0-43-generic` has been released and I have updated
myself to it. Still patch doesn't work whereas it works on linux-
oem-20.04

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
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.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1915117] [NEW] [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

Public bug reported:

Ubuntu version: 20.10 (updated from 20.04)
Kernel: 5.8.0-41-generic #46-Ubuntu
Manufacturer: Acer
Product Name: Swift SF314-54
BIOS Revision: 1.11

Audio card: Realtek High Definition Audio
Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio 
[8086:9d71] (rev 21)

Summary
===

After upgrading from linux kernel 5.4 to 5.8, there is no more sound
card available. However, if I select kernel 5.4 in GRUB, the sound card
is available.

Steps to reproduce
==

1. Install 20.04 or 20.10 with a kenel 5.4
2. Check that sound output works as excepted (Settings > Sound > Output > Test)
3. Check that `alsa-info` command returns information
4. Upgrade kernel to 5.8

Expected results


Sound output still works.

Actual results
==

2. Sound card is available, and sound can be output to the internal speakers.
4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-41-generic 5.8.0-41.46
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  9 14:42:00 2021
InstallationDate: Installed on 2019-01-20 (751 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Swift SF314-54
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-41-generic N/A
 linux-backports-modules-5.8.0-41-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
dmi.bios.date: 11/21/2018
dmi.bios.release: 1.11
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.11
dmi.board.name: Strongbow_KL
dmi.board.vendor: KBL
dmi.board.version: V1.11
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.ec.firmware.release: 1.6
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-54
dmi.product.sku: 
dmi.product.version: V1.11
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

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

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-

[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

** Attachment added: "pactl-list-20.10-kernel-5.4.0-65-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461560/+files/pactl-list-20.10-kernel-5.4.0-65-generic.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/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

As a point of comparison, below are attached logs when using the same
device with the same Ubuntu (20.10) but with an older 5.4.0-65-generic
kernel.

** Attachment added: "alsa-info.20.10-kernel-5.4.0-65-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461558/+files/alsa-info.20.10-kernel-5.4.0-65-generic.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/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

I've also tried booting a live USB with the latest alpha version from
21.04, based on kernel 5.8.0-36-generic, and the results are the same:
no sound card detected, "Dummy Output" displayed in Sound Settings. See
attached archive with same logs (dmesg, pactl, alsa-info).

** Attachment added: "21.04-kernel-5.8.0-36-audio-logs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461562/+files/21.04-kernel-5.8.0-36-audio-logs.tar.xz

** Description changed:

  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11
  
  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)
  
  Summary
  ===
  
  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound card
  is available.
  
  Steps to reproduce
  ==
  
  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8
  
  Expected results
  
  
  Sound output still works.
  
  Actual results
  ==
  
- No more sound card detected (Sound Settings display "Dummy Output" in
- the list of output devices).
+ 2. Sound card is available, and sound can be output to the internal speakers.
+ 4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-41-generic N/A
-  linux-backports-modules-5.8.0-41-generic  N/A
-  linux-firmware1.190.3
+  linux-restricted-modules-5.8.0-41-generic N/A
+  linux-backports-modules-5.8.0-41-generic  N/A
+  linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generi

[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

** Attachment added: "dmesg-20.10-kernel-5.4.0-65-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461559/+files/dmesg-20.10-kernel-5.4.0-65-generic.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/1915117

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

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