date:20211101

[Kernel-packages] [Bug 1949329] [NEW] [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

Public bug reported:

This bug is for tracking purpose.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: alsa-lib (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: alsa-lib (Ubuntu Focal)
 Importance: High
 Status: In Progress

** Affects: alsa-lib (Ubuntu Hirsute)
 Importance: High
 Status: In Progress

** Affects: alsa-lib (Ubuntu Impish)
 Importance: High
 Status: In Progress

** Affects: alsa-lib (Ubuntu Jammy)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress


** Tags: oem-priority originate-from-1943203 somerville

** Also affects: alsa-lib (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: alsa-lib (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: alsa-lib (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: alsa-lib (Ubuntu Jammy)
   Importance: Undecided
 Assignee: Hui Wang (hui.wang)
   Status: New

** Changed in: alsa-lib (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: alsa-lib (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: alsa-lib (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: alsa-lib (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: alsa-lib (Ubuntu Focal)
   Status: New => In Progress

** Changed in: alsa-lib (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: alsa-lib (Ubuntu Impish)
   Status: New => In Progress

** Changed in: alsa-lib (Ubuntu Jammy)
   Status: New => In Progress

** Tags added: oem-priority originate-from-1943203 somerville

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

This is the debdiff for focal.

Thanks.


** Patch added: "alsa-lib_1.2.2-2.1ubuntu2.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537417/+files/alsa-lib_1.2.2-2.1ubuntu2.5.debdiff

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

This is the debdiff for impish

Thanks.


** Patch added: "alsa-lib_1.2.4-1.1ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537419/+files/alsa-lib_1.2.4-1.1ubuntu4.debdiff

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

This is the debdiff for hirsute.

Thanks.


** Patch added: "alsa-lib_1.2.4-1.1ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1949329/+attachment/5537418/+files/alsa-lib_1.2.4-1.1ubuntu3.debdiff

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

And I can't download the docker image of Jammy, Maybe the Jammy share
the same libasound2 with Impish?

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Hui Wang

** Description changed:

- This bug is for tracking purpose.
+ [Impact]
+ In the Dell project, we tried to enable the audio on a machine, the machine 
has the soundwire audio design, it needs to load the ucm correctly, then users 
could see the audio devices from gnome. But on this machine, the ucm can't be 
loaded, through debugging, we found this machine has no headset, the Regex 
returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let 
Regex returns a correct value, the ucm could be loaded successfully.
+ 
+ [Fix]
+ Backport a commit from upstream, this commit is merged to upstream from v1.2.5
+ 
+ [Test]
+ After installed the patched libasound2, reboot, we could see the ucm is 
loaded succesfully on this machine, and open the gnome-sound-setting, we could 
see the internal mic and internal speaker, and all of them could work normally.
+ 
+ [Where problems will occur]
+ This change affect the Regex parser in the ucm, so if it could introduce 
regression, it will be on the ucm. It could make the audio not work (fail to 
load ucm and users can't see any audio devices from gnome) on the machines 
which need ucm. But this possibility is very low, since this commit is 
backported from upstream and we already tested this backporting on 2 lenovo 
machines and 2 Dell machines which all need ucm to work.

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress
Status in alsa-lib source package in Impish:
  In Progress
Status in alsa-lib source package in Jammy:
  In Progress

Bug description:
  [Impact]
  In the Dell project, we tried to enable the audio on a machine, the machine 
has the soundwire audio design, it needs to load the ucm correctly, then users 
could see the audio devices from gnome. But on this machine, the ucm can't be 
loaded, through debugging, we found this machine has no headset, the Regex 
returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let 
Regex returns a correct value, the ucm could be loaded successfully.

  [Fix]
  Backport a commit from upstream, this commit is merged to upstream from v1.2.5

  [Test]
  After installed the patched libasound2, reboot, we could see the ucm is 
loaded succesfully on this machine, and open the gnome-sound-setting, we could 
see the internal mic and internal speaker, and all of them could work normally.

  [Where problems will occur]
  This change affect the Regex parser in the ucm, so if it could introduce 
regression, it will be on the ucm. It could make the audio not work (fail to 
load ucm and users can't see any audio devices from gnome) on the machines 
which need ucm. But this possibility is very low, since this commit is 
backported from upstream and we already tested this backporting on 2 lenovo 
machines and 2 Dell machines which all need ucm to work.

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


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

[Kernel-packages] [Bug 1949278] Re: Sometimes getting console with purple text (xorg not starting)

2021-11-01 Thread Juerg Haefliger

** Package changed: linux-meta-raspi (Ubuntu) => linux-raspi (Ubuntu)

** Changed in: linux-raspi (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  Sometimes getting console with purple text (xorg not starting)

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Affected HW: Raspberry Pi 4B

  Sometimes I'm getting console with purple text and boot freezes.
  Able to switch to another console (with regular white on black font) and 
start display manager manually.

  Experiencing same problem with kernels 5.13.0-1010-raspi,
  5.13.0-1008-raspi, 5.11.0-1021-raspi.

  First time got this issue after upgrade to 21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp2', '/dev/dsp1', 
'/dev/dsp', '/dev/snd/controlC2', '/dev/snd/pcmC2D0p', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', 
'/dev/sequencer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.10
  ImageMediaBuild: 20210421.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  Package: linux-meta-raspi (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:61:DD:84 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
root=/dev/mmcblk0p2 rootwait rootfstype=ext4 fixrtc pty.legacy_count=6 
zswap.enabled=1 net.ifnames=0
  ProcVersionSignature: Ubuntu 5.11.0-1021.22-raspi 5.11.22
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-1021-raspi N/A
   linux-backports-modules-5.11.0-1021-raspi  N/A
   linux-firmware 1.201.1
  StagingDrivers: bcm2835_codec vc_sm_cma snd_bcm2835 bcm2835_v4l2 bcm2835_isp 
bcm2835_mmal_vchiq
  Tags:  arm64-image raspi-image impish staging
  Uname: Linux 5.11.0-1021-raspi aarch64
  UpgradeStatus: Upgraded to impish on 2021-08-31 (60 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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


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

[Kernel-packages] [Bug 1947568] Re: cannot promote clone: "not a cloned filesystem"

2021-11-01 Thread James Dingwall

This appears to be an issue with mismatched user/kernel zfs components.
After adding ppa:jonathonf/zfs
(https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) and updating the
user components my `zfs promote` problem has been resolved.

# zfs version
zfs-2.1.1-0york0~20.04
zfs-kmod-2.0.2-1ubuntu5.1

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

Title:
  cannot promote clone: "not a cloned filesystem"

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have a zvol containing a Windows image for a virtual machine.  After
  restarting the system a node under /dev/zvol/... was not created for
  the virtual disk and no amount of prompting by `udevadm trigger`
  helped.  Instead I created a snapshot from the most recent hourly
  backup:

  # zfs clone rpool/vm/windows/windows10/hda@hourly07 
rpool/vm/windows/windows10/hda-new
  # zfs promote rpool/vm/windows/windows10/hda-new
  cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem
  (didn't work here but carried on assuming something can be sorted later)
  # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old
  # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda

  Entries in /dev appeared and I could start the virtual machine.
  Trying to promote the clone gives 'not a cloned filesystem' message.
  I later renamed the old zvol and tried to cleanup:

  # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted
  #  zfs destroy rpool/to-be-deleted@hourly07
  cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones
  use '-R' to destroy the following datasets:
  rpool/vm/windows/windows10/hda@hourly09
  rpool/vm/windows/windows10/hda@hourly10
  rpool/vm/windows/windows10/hda
  # zfs promote rpool/vm/windows/windows10/hda
  cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem

  # zfs get origin rpool/vm/windows/windows10/hda
  NAMEPROPERTY  VALUE SOURCE
  rpool/vm/windows/windows10/hda  originrpool/to-be-deleted@hourly07  -

  # zfs get clones rpool/to-be-deleted@hourly07
  NAME  PROPERTY  VALUE   SOURCE
  rpool/to-be-deleted@hourly07  clonesrpool/vm/windows/windows10/hda  -

  The dependency between seems to be as expected.  This small test fails
  in the same way:

  # zfs create -V1G rpool/vm/test
  # zfs snapshot rpool/vm/test@test2
  # zfs clone rpool/vm/test@test2 rpool/vm/test3
  # zfs promote rpool/vm/test3
  cannot promote 'rpool/vm/test3': not a cloned filesystem
  # zfs get origin rpool/vm/test3
  NAMEPROPERTY  VALUESOURCE
  rpool/vm/test3  originrpool/vm/test@test2  -
  # zfs get clones rpool/vm/test@test2
  NAME PROPERTY  VALUE   SOURCE
  rpool/vm/test@test2  clonesrpool/vm/test3  -

  All the zpool members are ONLINE and no errors are reported.

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

  # uname -r
  5.11.0-37-generic

  # modinfo zfs | grep -i version
  version:2.0.2-1ubuntu5.1
  srcversion: F267DF7B3FFB43AFE76257D
  vermagic:   5.11.0-37-generic SMP mod_unload modversions

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

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


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

[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string

2021-11-01 Thread Sebastien Bacher

Yes, there was no change in the J serie yet. Uploaded now to current and
stables

** Changed in: alsa-lib (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: alsa-lib (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Changed in: alsa-lib (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Changed in: alsa-lib (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] alsa-lib: ucm: Regex returns correct value without matching a
  string

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-lib source package in Impish:
  Fix Committed
Status in alsa-lib source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  In the Dell project, we tried to enable the audio on a machine, the machine 
has the soundwire audio design, it needs to load the ucm correctly, then users 
could see the audio devices from gnome. But on this machine, the ucm can't be 
loaded, through debugging, we found this machine has no headset, the Regex 
returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let 
Regex returns a correct value, the ucm could be loaded successfully.

  [Fix]
  Backport a commit from upstream, this commit is merged to upstream from v1.2.5

  [Test]
  After installed the patched libasound2, reboot, we could see the ucm is 
loaded succesfully on this machine, and open the gnome-sound-setting, we could 
see the internal mic and internal speaker, and all of them could work normally.

  [Where problems will occur]
  This change affect the Regex parser in the ucm, so if it could introduce 
regression, it will be on the ucm. It could make the audio not work (fail to 
load ucm and users can't see any audio devices from gnome) on the machines 
which need ucm. But this possibility is very low, since this commit is 
backported from upstream and we already tested this backporting on 2 lenovo 
machines and 2 Dell machines which all need ucm to work.

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


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

Re: [Kernel-packages] [Bug 1948898] [NEW] Bluetooth HCI reset fail during airplane mode switch stress tests

2021-11-01 Thread You-Sheng Yang

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

Title:
  Bluetooth HCI reset fail during airplane mode switch stress tests

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  Bug 1928838 fixed possible kernel panic when doing rfkill block on
  Intel Bluetooth controller. The fix was also upstreamed in v5.14-rc1
  as commit 0ea9fd001a14e ("Bluetooth: Shutdown controller after
  workqueues are flushed or cancelled") and was backported to v5.10.51,
  v5.12.18, and v5.13.3. However, as indicated in
  https://lore.kernel.org/linux-bluetooth/8735ryk0o7@baylibre.com/ ,
  it caused a regression to mtkbtsdio and was then fixed in upstream
  commit 0ea53674d07f (" Bluetooth: Move shutdown callback before
  flushing tx and rx queue") since v5.15-rc1 and has been backported to
  v5.14.3. Current statuses:

  * v5.10.x:
* 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
* 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
  * v5.11.x: N/A
  * v5.12.x:
* 0ea9fd001a14e: backported(v5.12.18)
  * v5.13.x:
* 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
* 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
  * v5.14.x:
* 0ea9fd001a14e: committed(v5.14-rc1)
* 0ea53674d07f: backported(v5.14.3)
  * v5.15.x:
* 0ea53674d07f: committed(v5.15-rc1)

  As a result, this affects 5.10/11/13 kernels.

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


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

Re: [Kernel-packages] [Bug 1939402] Re: Touchpad not working correctly after Ubuntu Update

2021-11-01 Thread SadashivRao VitthalRao Gaikwad

Ran the above command: sudo dmesg > dmesg.txt
Attached below is the text file.

Update: The touchpad started working normally since the start of this
month.

I used to run these two commands in my terminal:
1. sudo modprobe -r psmouse
2. sudo modprobe psmouse
after every boot up and the touch pad would then work fine.

On Wed, Aug 11, 2021 at 7:50 AM Daniel van Vugt <1939...@bugs.launchpad.net>
wrote:

> Please run this command:
>
>   sudo dmesg > dmesg.txt
>
> and attach the resulting text file here. We need to know more details
> about the model of machine.
>
> ** Changed in: linux-signed-hwe-5.11 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1939402
>
> Title:
>   Touchpad not working correctly after Ubuntu Update
>
> Status in linux-signed-hwe-5.11 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   xinput list
>
>   When I run this command I do not see the touchpad listed.
>
>   cat /proc/bus/input/devices
>
>   In this command too I do not see the Touchpad.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
>   ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
>   Uname: Linux 5.11.0-25-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Aug 10 18:04:56 2021
>   InstallationDate: Installed on 2021-06-26 (45 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   SourcePackage: linux-signed-hwe-5.11
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions
>
>

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

Title:
  Touchpad not working correctly after Ubuntu Update

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Expired

Bug description:
  xinput list

  When I run this command I do not see the touchpad listed.

  cat /proc/bus/input/devices

  In this command too I do not see the Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 10 18:04:56 2021
  InstallationDate: Installed on 2021-06-26 (45 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions


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

Re: [Kernel-packages] [Bug 1948813] Re: cant connect to second monitor

2021-11-01 Thread Andres Lopez Rubio

Thanks,


After that the  computer was not booting due to an error related to the
video card, I managed to do a new install instead


Andrés López Rubio


On Tue, Oct 26, 2021 at 8:45 PM Daniel van Vugt <1948...@bugs.launchpad.net>
wrote:

> Thanks for the bug report. The problem appears to be that the nvidia-470
> kernel driver loaded and then quickly unloaded two seconds later. I
> don't know why that would happen... Maybe look in the 'Additional
> Drivers' app and uninstall the 470 driver, try 460 or 465 instead?
>
> ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
> (Ubuntu)
>
> ** Summary changed:
>
> - cant connect to second monitor
> + Nvidia-470 kernel driver loads then unloads during boot on GTX 1050
> Mobile. No driver loaded in the end.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1948813
>
> Title:
>   Nvidia-470 kernel driver loads then unloads during boot on GTX 1050
>   Mobile. No driver loaded in the end.
>
> Status in nvidia-graphics-drivers-470 package in Ubuntu:
>   New
>
> Bug description:
>   I lost projecting to my second monitor while updating in ubuntu 20
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
>   Uname: Linux 5.4.0-89-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.21
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Oct 26 07:55:42 2021
>   DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript:
> '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   DkmsStatus:
>bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed
>nvidia, 470.74, 5.4.0-89-generic, x86_64: installed
>virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed
>virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed
>   GraphicsCard:
>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
> [VGA controller])
>  Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile)
> [1025:1264]
>NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev
> ff) (prog-if ff)
>   InstallationDate: Installed on 2021-09-21 (34 days ago)
>   InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
> (20200806.1)
>   MachineType: Acer Nitro AN515-52
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic
> root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago)
>   dmi.bios.date: 08/05/2019
>   dmi.bios.vendor: Insyde Corp.
>   dmi.bios.version: V1.28
>   dmi.board.asset.tag: Type2 - Board Serial Number
>   dmi.board.name: Freed_CFS
>   dmi.board.vendor: CFL
>   dmi.board.version: V1.28
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.28
>   dmi.modalias:
> dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
>   dmi.product.family: Acer Nitro 5
>   dmi.product.name: Nitro AN515-52
>   dmi.product.sku: 
>   dmi.product.version: V1.28
>   dmi.sys.vendor: Acer
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.105-3~20.04.2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
>   version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948813/+subscriptions
>
>

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

Title:
  Nvidia-470 kernel driver loads then unloads during boot on GTX 1050
  Mobile. No driver loaded in the end.

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  I lost projecting to my second monitor while updating in ubuntu 20

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  Uname: Linux 5.4.0-89-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/lo

Re: [Kernel-packages] [Bug 1914837] Re: enabling wifi crashes thinkpad x1 extreme (gen2)

2021-11-01 Thread Sec

On Wed, Oct 27, 2021 at 08:00 -, Juerg Haefliger wrote:
> Apologies for the long delay. Is this still an issue for you?

I have upgraded to ubuntu 21.04 and haven't had this problem
since the upgrade.

Thanks,
Sec
-- 
   Error reduces
 Your expensive computer
   To a simple stone

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

Title:
  enabling wifi crashes thinkpad x1 extreme (gen2)

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  On enabling the wifi interface, the laptop crashes (lockup, without
  further error messages) soon thereafter (10-20s)

  Fix is to replace /lib/firmware/iwlwifi-cc-a0-46.ucode with the
  corresponding file from
  https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

  # - download archive for AX200: 
  cd /tmp
  curl -O 
https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi/iwlwifi-cc-46.3cfab8da.0.tgz
  # - extract
  tar xvzf iwlwifi-cc-46.3cfab8da.0.tgz
  # - copy firmware
  cp iwlwifi-cc-46.3cfab8da.0/iwlwifi-cc-a0-46.ucode /lib/firmware/

  My laptop is as follows:

  System Information
  Manufacturer: LENOVO
  Product Name: 20QVCTO1WW
  Version: ThinkPad X1 Extreme 2nd
  SKU Number: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.9 [modified: 
lib/firmware/iwlwifi-cc-a0-46.ucode]
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sec1368 F pulseaudio
   /dev/snd/controlC0:  sec1368 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Feb  5 23:25:14 2021
  Dependencies:
   
  InstallationDate: Installed on 2019-09-23 (500 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00bd Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b67c Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20QVCTO1WW
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash nmi_watchdog=0 vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  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
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to focal on 2020-05-31 (250 days ago)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.11/5.11.0.1022.24~20.04.21)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gcp-5.11 
(5.11.0.1022.24~20.04.21) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-gcp-5.11

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.90.101~18.04.80)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-hwe-5.4 
(5.4.0.90.101~18.04.80) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

snapd/2.51.1+18.04 (amd64, ppc64el)
virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
asic0x/1.0.1-1 (s390x)
kpatch/0.5.0-0ubuntu1.1 (amd64)
acpi-call/1.1.0-4 (s390x, ppc64el)
virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
lxd/3.0.3-0ubuntu1~18.04.1 (i386)
lxc/3.0.3-0ubuntu1~18.04.1 (i386, arm64, s390x, amd64, ppc64el)
v4l2loopback/0.10.0-1ubuntu1.2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-hwe-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop/5.4.0.1026.29)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gkeop (5.4.0.1026.29) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-gkeop

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1006.6)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1006.6) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-oem-5.14/5.14.0-1006.6 (amd64)
virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64)
lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64)
virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oem-5.14

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.4.0.1057.57)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1057.57) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1059.42)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1059.42) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

glibc/2.27-3ubuntu1.4 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64, arm64)
kpatch/0.5.0-0ubuntu1.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-aws-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.11.0.1021.22)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1021.22) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
systemd/247.3-3ubuntu3.6 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1055.65)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1055.65) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
glibc/2.31-0ubuntu9.2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-gke

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.13.0.1009.11)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oracle (5.13.0.1009.11) for 
impish have finished running.
The following regressions have been reported in tests triggered by the package:

langford/unknown (arm64)
bbswitch/unknown (arm64)
dm-writeboost/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1939402] Re: Touchpad not working correctly after Ubuntu Update

2021-11-01 Thread SadashivRao VitthalRao Gaikwad

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1939402/+attachment/5537445/+files/dmesg.txt

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

Title:
  Touchpad not working correctly after Ubuntu Update

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Expired

Bug description:
  xinput list

  When I run this command I do not see the touchpad listed.

  cat /proc/bus/input/devices

  In this command too I do not see the Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 10 18:04:56 2021
  InstallationDate: Installed on 2021-06-26 (45 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions


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

[Kernel-packages] [Bug 1949026] Autopkgtest regression report (nvidia-graphics-drivers-470/470.82.00-0ubuntu0.21.04.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-470 
(470.82.00-0ubuntu0.21.04.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#nvidia-graphics-drivers-470

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  System hangs on purple screen

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * In some race condition, the GDM starts before gdm-udev rule be applied.
   * That's because somehow the nvidia driver takes more times to do the 
runtime resume. Thus, apply the workaround to postpone to enable RTD3.

  [Test Plan]

   1. In problematic machine, warn/cold boot the system.
   2.1 System hangs on GDM login shell
   2.2 After apply this patch, the system can enter the login screen.

  [Where problems could occur]

   * Postpone to enable RTD3 when binding driver should not impact the
  functionality since the power consumption usually not be consider in
  booting stage.

  ---

  We are facing an issue that GDM starts with Wayland instead of Xorg,
  despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.

  The issue happens because gdm-disable-wayland is executed after GDM has
  started. The reason why the udev rules takes so long is because the the
  runtime suspended NVIDIA GFX takes more than 1 second to runtime resume,
  hence the driver starts the probing routine rather late.

  The proper solution is to impose a barrier like
  systemd-udev-settle.service before GDM, but limits to the GFX device
  only to avoid waiting for all udev rules are finished.

  Since such mechanism isn't available right now, workaround the issue by
  enabling runtime PM after driver is bound to avoid the runtime resume
  delay, and hope GDM always starts after the probing is done.

  Please backport below patch to supported nvidia-drivers:
  
https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1949026/+subscriptions


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

[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests

2021-11-01 Thread You-Sheng Yang

** Attachment added: "btmon.5.13.0-1017-oem_BIOS-0.12.71_AX210"
   
https://bugs.launchpad.net/bugs/1948898/+attachment/5537450/+files/btmon.5.13.0-1017-oem_BIOS-0.12.71_AX210

** Attachment added: "dmesg.5.13.0-1017-oem"
   
https://bugs.launchpad.net/bugs/1948898/+attachment/5537451/+files/dmesg.5.13.0-1017-oem

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

Title:
  Bluetooth HCI reset fail during airplane mode switch stress tests

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  Bug 1928838 fixed possible kernel panic when doing rfkill block on
  Intel Bluetooth controller. The fix was also upstreamed in v5.14-rc1
  as commit 0ea9fd001a14e ("Bluetooth: Shutdown controller after
  workqueues are flushed or cancelled") and was backported to v5.10.51,
  v5.12.18, and v5.13.3. However, as indicated in
  https://lore.kernel.org/linux-bluetooth/8735ryk0o7@baylibre.com/ ,
  it caused a regression to mtkbtsdio and was then fixed in upstream
  commit 0ea53674d07f (" Bluetooth: Move shutdown callback before
  flushing tx and rx queue") since v5.15-rc1 and has been backported to
  v5.14.3. Current statuses:

  * v5.10.x:
* 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
* 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
  * v5.11.x: N/A
  * v5.12.x:
* 0ea9fd001a14e: backported(v5.12.18)
  * v5.13.x:
* 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
* 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
  * v5.14.x:
* 0ea9fd001a14e: committed(v5.14-rc1)
* 0ea53674d07f: backported(v5.14.3)
  * v5.15.x:
* 0ea53674d07f: committed(v5.15-rc1)

  As a result, this affects 5.10/11/13 kernels.

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


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

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-450-server/450.156.00-0ubuntu0.21.04.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-450-server 
(450.156.00-0ubuntu0.21.04.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#nvidia-graphics-drivers-450-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.ne

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-450-server/450.156.00-0ubuntu0.21.10.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-450-server 
(450.156.00-0ubuntu0.21.10.1) for impish have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#nvidia-graphics-drivers-450-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.net/

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-418-server/418.226.00-0ubuntu0.21.04.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-418-server 
(418.226.00-0ubuntu0.21.04.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#nvidia-graphics-drivers-418-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.ne

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1057.61~18.04.37)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-oracle-5.4 
(5.4.0.1057.61~18.04.37) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1055.58~18.04.20)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gke-5.4 
(5.4.0.1055.58~18.04.20) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-gke-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.13.0.1010.16)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi (5.13.0.1010.16) for 
impish have finished running.
The following regressions have been reported in tests triggered by the package:

adv-17v35x/unknown (arm64)
dm-writeboost/unknown (arm64)
bbswitch/0.8-10 (arm64)
v4l2loopback/0.12.5-1ubuntu3 (arm64)
glibc/unknown (arm64)
lxc/unknown (arm64)
digimend-dkms/unknown (arm64)
lttng-modules/unknown (arm64)
dpdk-kmods/unknown (arm64)
jool/unknown (arm64)
glibc/2.34-0ubuntu3 (armhf)
west-chamber/unknown (arm64)
acpi-call/unknown (arm64)
evdi/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
xtables-addons/unknown (arm64)
rtl8812au/unknown (arm64)
xtrx-dkms/unknown (arm64)
systemd/248.3-1ubuntu8 (armhf)
wireguard-linux-compat/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#linux-meta-raspi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.13/5.13.0.21.21~20.04.8)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-hwe-5.13 
(5.13.0.21.21~20.04.8) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.13/5.13.0-21.21~20.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-hwe-5.13

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-495/495.44-0ubuntu0.21.04.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-495 
(495.44-0ubuntu0.21.04.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#nvidia-graphics-drivers-495

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1022.20)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1022.20) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/unknown (arm64)
mali-midgard/unknown (arm64)
openrazer/unknown (arm64)
dpdk-kmods/unknown (arm64)
wireguard-linux-compat/1.0.20210219-1 (arm64)
glibc/2.33-0ubuntu5 (arm64)
systemd/247.3-3ubuntu3.6 (arm64, armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-raspi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1026.27~18.04.27)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gkeop-5.4 
(5.4.0.1026.27~18.04.27) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-gkeop-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1046.81)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1046.81) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

openafs/unknown (arm64)
r8168/unknown (arm64)
acpi-call/unknown (arm64)
nat-rtsp/unknown (arm64)
zfs-linux/unknown (arm64)
systemd/unknown (arm64)
snapd/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
dm-writeboost/unknown (arm64)
openrazer/unknown (arm64)
xtables-addons/unknown (arm64)
glibc/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-raspi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-495/495.44-0ubuntu0.21.10.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-495 
(495.44-0ubuntu0.21.10.1) for impish have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build2 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#nvidia-graphics-drivers-495

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
P

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1046.49)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1046.49) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

xtables-addons/unknown (arm64)
linux-raspi-5.4/5.4.0-1046.50~18.04.1 (armhf)
rtl8812au/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
glibc/unknown (arm64)
dpdk/unknown (arm64)
rtl8821ce/unknown (arm64)
v4l2loopback/unknown (arm64)
r8168/unknown (arm64)
langford/unknown (arm64)
lime-forensics/unknown (arm64)
lttng-modules/unknown (arm64)
spl-linux/unknown (arm64)
ktap/unknown (arm64)
systemd/unknown (arm64)
acpi-call/1.1.0-4 (arm64)
bbswitch/0.8-4ubuntu1 (arm64)
zfs-linux/unknown (arm64)
asic0x/unknown (arm64)
linux-raspi-5.4/unknown (arm64)
fwts/unknown (arm64)
dm-writeboost/unknown (arm64)
nat-rtsp/unknown (arm64)
lxc/3.0.3-0ubuntu1~18.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

2021-11-01 Thread Adriano Nisticò

HW: HP 17-CN0004NL
UBUNTU 21.10 kernel 5.13.0
This bug DOES NOT happen on 5.11.0-38-generic. Confirmed device RTL8821CE

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

Title:
  rtw88_8821ce causes freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-470/470.82.00-0ubuntu0.21.04.1)

2021-11-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-470 
(470.82.00-0ubuntu0.21.04.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#nvidia-graphics-drivers-470

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the NVIDIA drivers October 2021

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, and Impish.

  [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]

  == 470 ==
    * New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
    configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
    * Initial release (LP: #1948025).

  == 460-server ==

* New upstream release (LP: #1948025).

  
  == 450-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

  
  == 418-server ==

* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.14.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packa

[Kernel-packages] [Bug 1949353] [NEW] [SRU] Revert 'e1000e: add handshake with the Intel CSME to support S0ix'

2021-11-01 Thread Bin Li

Public bug reported:

[SRU Justification]

https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=258514

>From the 5.13.0-1012-oem kernel we found NO Ethernet connecting after resume 
>from suspend, on 5.13.0-1010-oem we don't met this issue, so this is a 
>regression on I219 in lots of platforms.
And this blocked our OEM projects, could we revert the patches in short term? 
When the firmware or the related patches are ready, we merge it again.

Oct 25 22:45:44 p15s-ThinkPad-P15s-Gen-2i kernel: e1000e :00:1f.6 
enp0s31f6: Detected Hardware Unit Hang:
TDH <3>
TDT <7>
next_to_use <7>
next_to_clean <3>
  buffer_info[next_to_clean]:
time_stamp 
next_to_watch <3>
jiffies 
next_to_watch.status <0>
  MAC Status <40080283>
  PHY Status <796d>
  PHY 1000BASE-T Status <3800>
  PHY Extended Status <3000>
  PCI Status <10>


[Impact]

These doesn't improve power consumption on some e1000e platforms.

[Fix]

I tried to revert these 3 patches on 5.13.0-1019.23, it works fine.

commit f65d71bdcb52e8d82dd0a3e71ae4359c0972fe3b
Author: Sasha Neftin 
Date:   Wed Aug 18 15:10:49 2021 +0800

e1000e: Additional PHY power saving in S0ix

BugLink: https://bugs.launchpad.net/bugs/1937252

After transferring the MAC-PHY interface to the SMBus set the PHY
to S0ix low power idle mode

commit c97933898708a37678ba1fc6f1f5704fbe92774c
Author: Sasha Neftin 
Date:   Wed Aug 18 15:10:48 2021 +0800

e1000e: Add polling mechanism to indicate CSME DPG exit

BugLink: https://bugs.launchpad.net/bugs/1937252

Per guidance from the CSME architecture team, it may take
up to 1 second for unconfiguring dynamic power gating mode.
Practically it can take more time. Wait up to 2.5 seconds to indicate
dynamic power gating exit from the S0ix configuration. Detect
scenarios that take more than 1 second but less than 2.5 seconds
will emit warning message.

commit 66069cb4ebaf0eccfdec934ebfd92d3fdb136adc
Author: Sasha Neftin 
Date:   Wed Aug 18 15:10:47 2021 +0800

e1000e: Add handshake with the CSME to support S0ix

BugLink: https://bugs.launchpad.net/bugs/1937252

On the corporate system, the driver will ask from the CSME
(manageability engine) to perform device settings are required
to allow S0ix residency.
This patch provides initial support.


[Test Case]
Do suspend and resume 10 times, it works fine.

for i in {1..10}; do
echo $i
rtcwake -m no -s 20 && echo mem > /sys/power/state
if dmesg | grep -q "Detected Hardware Unit Hang"; then
exit
fi
sleep 15
done

[Where problems could occur]

00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (13) 
I219-LM [8086:15fb] (rev 20)
CPU: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz

** Affects: oem-priority
 Importance: Critical
 Status: New

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


** Tags: oem-priority originate-from-1948738 sutton

** Tags added: oem-priority originate-from-1948738 sutton

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

Title:
  [SRU] Revert 'e1000e: add handshake with the Intel CSME to support
  S0ix'

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  [SRU Justification]

  https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=258514

  From the 5.13.0-1012-oem kernel we found NO Ethernet connecting after resume 
from suspend, on 5.13.0-1010-oem we don't met this issue, so this is a 
regression on I219 in lots of platforms.
  And this blocked our OEM projects, could we revert the patches in short term? 
When the firmware or the related patches are ready, we merge it again.

  Oct 25 22:45:44 p15s-ThinkPad-P15s-Gen-2i kernel: e1000e :00:1f.6 
enp0s31f6: Detected Hardware Unit Hang:
  TDH <3>
  TDT <7>
  next_to_use <7>
  next_to_clean <3>

[Kernel-packages] [Bug 1949353] Re: [SRU] Revert 'e1000e: add handshake with the Intel CSME to support S0ix'

2021-11-01 Thread Bin Li

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

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

Title:
  [SRU] Revert 'e1000e: add handshake with the Intel CSME to support
  S0ix'

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  [SRU Justification]

  https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=258514

  From the 5.13.0-1012-oem kernel we found NO Ethernet connecting after resume 
from suspend, on 5.13.0-1010-oem we don't met this issue, so this is a 
regression on I219 in lots of platforms.
  And this blocked our OEM projects, could we revert the patches in short term? 
When the firmware or the related patches are ready, we merge it again.

  Oct 25 22:45:44 p15s-ThinkPad-P15s-Gen-2i kernel: e1000e :00:1f.6 
enp0s31f6: Detected Hardware Unit Hang:
  TDH <3>
  TDT <7>
  next_to_use <7>
  next_to_clean <3>
buffer_info[next_to_clean]:
  time_stamp 
  next_to_watch <3>
  jiffies 
  next_to_watch.status <0>
MAC Status <40080283>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>


  [Impact]

  These doesn't improve power consumption on some e1000e platforms.

  [Fix]

  I tried to revert these 3 patches on 5.13.0-1019.23, it works fine.

  commit f65d71bdcb52e8d82dd0a3e71ae4359c0972fe3b
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:49 2021 +0800

  e1000e: Additional PHY power saving in S0ix
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  After transferring the MAC-PHY interface to the SMBus set the PHY
  to S0ix low power idle mode

  commit c97933898708a37678ba1fc6f1f5704fbe92774c
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:48 2021 +0800

  e1000e: Add polling mechanism to indicate CSME DPG exit
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  Per guidance from the CSME architecture team, it may take
  up to 1 second for unconfiguring dynamic power gating mode.
  Practically it can take more time. Wait up to 2.5 seconds to indicate
  dynamic power gating exit from the S0ix configuration. Detect
  scenarios that take more than 1 second but less than 2.5 seconds
  will emit warning message.

  commit 66069cb4ebaf0eccfdec934ebfd92d3fdb136adc
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:47 2021 +0800

  e1000e: Add handshake with the CSME to support S0ix
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  On the corporate system, the driver will ask from the CSME
  (manageability engine) to perform device settings are required
  to allow S0ix residency.
  This patch provides initial support.

  
  [Test Case]
  Do suspend and resume 10 times, it works fine.

  for i in {1..10}; do
  echo $i
  rtcwake -m no -s 20 && echo mem > /sys/power/state
  if dmesg | grep -q "Detected Hardware Unit Hang"; then
  exit
  fi
  sleep 15
  done

  [Where problems could occur]

  00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection 
(13) I219-LM [8086:15fb] (rev 20)
  CPU: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1949353/+subscriptions


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

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

2021-11-01 Thread Ubuntu Kernel Bot

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

apport-collect 1949353

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

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

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

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

** Tags added: impish

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

Title:
  [SRU] Revert 'e1000e: add handshake with the Intel CSME to support
  S0ix'

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [SRU Justification]

  https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=258514

  From the 5.13.0-1012-oem kernel we found NO Ethernet connecting after resume 
from suspend, on 5.13.0-1010-oem we don't met this issue, so this is a 
regression on I219 in lots of platforms.
  And this blocked our OEM projects, could we revert the patches in short term? 
When the firmware or the related patches are ready, we merge it again.

  Oct 25 22:45:44 p15s-ThinkPad-P15s-Gen-2i kernel: e1000e :00:1f.6 
enp0s31f6: Detected Hardware Unit Hang:
  TDH <3>
  TDT <7>
  next_to_use <7>
  next_to_clean <3>
buffer_info[next_to_clean]:
  time_stamp 
  next_to_watch <3>
  jiffies 
  next_to_watch.status <0>
MAC Status <40080283>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>


  [Impact]

  These doesn't improve power consumption on some e1000e platforms.

  [Fix]

  I tried to revert these 3 patches on 5.13.0-1019.23, it works fine.

  commit f65d71bdcb52e8d82dd0a3e71ae4359c0972fe3b
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:49 2021 +0800

  e1000e: Additional PHY power saving in S0ix
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  After transferring the MAC-PHY interface to the SMBus set the PHY
  to S0ix low power idle mode

  commit c97933898708a37678ba1fc6f1f5704fbe92774c
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:48 2021 +0800

  e1000e: Add polling mechanism to indicate CSME DPG exit
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  Per guidance from the CSME architecture team, it may take
  up to 1 second for unconfiguring dynamic power gating mode.
  Practically it can take more time. Wait up to 2.5 seconds to indicate
  dynamic power gating exit from the S0ix configuration. Detect
  scenarios that take more than 1 second but less than 2.5 seconds
  will emit warning message.

  commit 66069cb4ebaf0eccfdec934ebfd92d3fdb136adc
  Author: Sasha Neftin 
  Date:   Wed Aug 18 15:10:47 2021 +0800

  e1000e: Add handshake with the CSME to support S0ix
  
  BugLink: https://bugs.launchpad.net/bugs/1937252
  
  On the corporate system, the driver will ask from the CSME
  (manageability engine) to perform device settings are required
  to allow S0ix residency.
  This patch provides initial support.

  
  [Test Case]
  Do suspend and resume 10 times, it works fine.

  for i in {1..10}; do
  echo $i
  rtcwake -m no -s 20 && echo mem > /sys/power/state
  if dmesg | grep -q "Detected Hardware Unit Hang"; then
  exit
  fi
  sleep 15
  done

  [Where problems could occur]

  00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection 
(13) I219-LM [8086:15fb] (rev 20)
  CPU: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1949353/+subscriptions


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

[Kernel-packages] [Bug 1949321] Re: Fix System hangs on black screen when reboot

2021-11-01 Thread Timo Aaltonen

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

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

Title:
  Fix System hangs on black screen when reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New
Status in linux-oem-5.14 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  New
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.10 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  System hangs on black screen when reboot

  [Fix]
  Looks like our VBIOS/GOP generally fail to turn the DP dual mode adater
  TMDS output buffers back on after a reboot. This leads to a black screen
  after reboot if we turned the TMDS output buffers off prior to reboot.
  And if i915 decides to do a fastboot the black screen will persist even
  after i915 takes over.
  
  Apparently this has been a problem ever since commit b2ccb822d376 
("drm/i915:Enable/disable TMDS output buffers in DP++ adaptor as needed") if 
one rebooted while the display was turned off. And things became worse with 
commit fe0f1e3bfdfe ("drm/i915: Shut down displays gracefully on reboot") since 
now we always turn the display off before a reboot.
  
  This was reported on a RKL, but I confirmed the same behaviour on my
  SNB as well. So looks pretty universal.
  
  Let's fix this by explicitly turning the TMDS output buffers back on
  in the encoder->shutdown() hook. Note that this gets called after irqs
  have been disabled, so the i2c communication with the DP dual mode
  adapter has to be performed via polling (which the gmbus code is
  perfectly happy to do for us).
  
  We also need a bit of care in handling DDI encoders which may or may
  not be set up for HDMI output. Specifically ddc_pin will not be
  populated for a DP only DDI encoder, in which case we don't want to
  call intel_gmbus_get_adapter(). We can handle that by simply doing
  the dual mode adapter type check before calling
  intel_gmbus_get_adapter().
  Ref: https://patchwork.freedesktop.org/series/96433/

  [Test]
  1. install kernel
  2. reboot
  3. check the monitor works well.

  [Regression Potential]
  Medium, patch has sent to patchwork but may have a upgraded version in the 
furtue.

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


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

[Kernel-packages] [Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]

2021-11-01 Thread Timo Aaltonen

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Fix Screen freeze after resume from suspend with iGPU [1002:6987]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.13 source package in Hirsute:
  New
Status in linux-oem-5.14 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  New

Bug description:
  [Impact]
  Screen freeze after resume from suspend

  [Fix]
  Perform proper cleanups on UVD/VCE suspend: powergate enablement,
  clockgating enablement and dpm disablement. This can fix some hangs
  observed on suspending when UVD/VCE still using(e.g. issue
  "pm-suspend" when video is still playing).

  [Test]
  1. Plug AMD RX640/Radeon 540 into the system
  2. Connect with DP monitor to iGPU
  3. Power on
  4. Suspend the system
  5. Resume from suspend
  6. Do something for a while (terminal, nautilus, gnome-control-center, etc).
  7.  System could resume normally

  [Regression Potential]
  Low

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


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

[Kernel-packages] [Bug 1945576] Re: Intel I225-IT ethernet controller: igc: probe of 0000:02:00.0 failed with error -1

2021-11-01 Thread Timo Aaltonen

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Intel I225-IT ethernet controller: igc: probe of :02:00.0 failed
  with error -1

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-intel package in Ubuntu:
  Invalid
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-intel source package in Focal:
  Won't Fix
Status in linux-intel-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-intel source package in Hirsute:
  Invalid
Status in linux-intel-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-intel source package in Impish:
  Invalid
Status in linux-intel-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Environment]
  Device : Aaeon Up xtreme i11
  Platform: Intel TigerLake-UP3
  I225-IT NVM version: 1.79
  I225-IT Stepping: B3
  Ubuntu version: 20.04.3 LTS with kernel 5.11.0-27-generic

  [Description]
  It can work under Windows10.
  But uner Ubuntu, we can't find the interface by ifconfig command and the 
system dmesg will has the error of igc driver module :
   igc: probe of :02:00.0 failed with error -1

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


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

[Kernel-packages] [Bug 1948767] Re: Fail to detect audio output from external monitor

2021-11-01 Thread Timo Aaltonen

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Fail to detect audio output from external monitor

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response 
timeout" and fail to detect the HDMI/DP audio output device when connects to 
external monitor. It will work magically when re-loading the driver.

  [Fix]
  Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec 
configuration errors) from 5.15.0 rc. It adds the capability for retrying the 
probe upon codec probe errors on the certain AMD platforms. 

  [Test]
  1. Connect the external monitor to particular affected AMD systems with HDMI 
or DisplayPort.
  2. Go to Audio Settings to check if the HDMI/DP audio output device exist or 
not.

  [Where problems could occur]
  Should be low risk, it adds the chance for retrying codec probe and won't 
affect machines which used to work.

  == Original Bug Description ==

  Can not detect DP audio output
  [Steps to reproduce]
  1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
  2) switch to on-demand mode
  3) connect an external monitor via DP Port
  4) check sound setting --> Output Device
  5) switch to performance mode
  6) check sound setting --> Output Device

  [Expected result]
  System can detect DP audio output when external monitor connected

  [Actual result]
  Can not detect DP audio output
  This issue can be reproduce in on-demand and performance mode.
  [Failure rate]
  1/1

  [Additional information]
  CID: 202101-28624
  SKU: PRH-DVT-C6
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
  system-manufacturer: Dell Inc.
  system-product-name: OptiPlex 5490 AIO
  bios-version: 1.4.1
  CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4c8a] (rev 04)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
  kernel-version: 5.14.0-2006-oem
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1081 F pulseaudio
u  1592 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X88
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-10-27 (1 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. OptiPlex 5490 AIO
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem 
root=UUID=d0e48268-091a-436d-8b79-2420e385c5c8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1020-oem N/A
   linux-backports-modules-5.10.0-1020-oem  N/A
   linux-firmware   1.187.10
  Tags:  focal
  Uname: Linux 5.10.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd08/17/2021:br1.4:svnDellInc.:pnOptiPlex5490AIO:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr:
  dmi.product.family: OptiPlex
  dmi.pr

[Kernel-packages] [Bug 1947859] Re: linux-azure: Updata MANA to 5.15-rc6

2021-11-01 Thread Tim Gardner

wget 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-modules-extra-5.11.0-1021-azure_5.11.0-1021.22_amd64.deb
dpkg -x linux-modules-extra-5.11.0-1021-azure_5.11.0-1021.22_amd64.deb .
find lib -name mana.ko
lib/modules/5.11.0-1021-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko

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

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

Title:
  linux-azure: Updata MANA to 5.15-rc6

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure source package in Impish:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of MANA EQ-sharing patch set
  which is essentially everything up through v5.15-rc6.

  3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
  Network Adapter (MANA). This saves MSI-X interrupts and allows the
  host to offer more virtual ports (network interfaces) to the VM. With
  the patches, the MANA driver supports up to 256 virtual ports per VF
  (it was 16/VF), and support up to 64 queues per vPort (it was 16).

  [Test Case]

  Microsoft to test and verify.

  [Where things might go wrong]

  More virtual ports may cause issues in older kernels.

  [Other Info]

  SF: #00321275

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


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

[Kernel-packages] [Bug 1947859] Re: linux-azure: Updata MANA to 5.15-rc6

2021-11-01 Thread Tim Gardner

wget 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-modules-extra-5.13.0-1007-azure_5.13.0-1007.8_amd64.deb
dpkg -x linux-modules-extra-5.13.0-1007-azure_5.13.0-1007.8_amd64.deb  .
find lib -name mana.ko
lib/modules/5.13.0-1007-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko


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

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

Title:
  linux-azure: Updata MANA to 5.15-rc6

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure source package in Impish:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of MANA EQ-sharing patch set
  which is essentially everything up through v5.15-rc6.

  3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
  Network Adapter (MANA). This saves MSI-X interrupts and allows the
  host to offer more virtual ports (network interfaces) to the VM. With
  the patches, the MANA driver supports up to 256 virtual ports per VF
  (it was 16/VF), and support up to 64 queues per vPort (it was 16).

  [Test Case]

  Microsoft to test and verify.

  [Where things might go wrong]

  More virtual ports may cause issues in older kernels.

  [Other Info]

  SF: #00321275

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


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

[Kernel-packages] [Bug 1949357] [NEW] linux-azure: Include mana.ko in linux-modules

2021-11-01 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

The new networking module mana.ko is not included with linux-modules,
rather it is packaged in linux-modules-extra. Instance types that have
mana.ko as a boot dependency will not work since Azure images are not
created using linux-image-extra.

[Test Plan]

Download linux-modules and check for mana.ko

[Where problems could occur]

mana.ko could go missing

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Focal)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Impish)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-azure (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Hirsute)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Impish)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  linux-azure: Include mana.ko in linux-modules

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The new networking module mana.ko is not included with linux-modules,
  rather it is packaged in linux-modules-extra. Instance types that have
  mana.ko as a boot dependency will not work since Azure images are not
  created using linux-image-extra.

  [Test Plan]

  Download linux-modules and check for mana.ko

  [Where problems could occur]

  mana.ko could go missing

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


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

[Kernel-packages] [Bug 1949358] [NEW] Kernel 5.11.0-38 - keyboard not working properly after hibernation

2021-11-01 Thread Daniel Bacellar

Public bug reported:

As in the previous kernel 5.11's since .37, keyboard also gets crazy after 
hibernation with kernel 5.11.0-38. 
My pc is a ENVY x360 13-ar0002ns convert, 13.3, touch screen, AMD RYZEN 5-3500U 
Vega running linux Mint 20 Ulyanna. 
Tks

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

Title:
  Kernel 5.11.0-38 - keyboard not working properly after hibernation

Status in linux package in Ubuntu:
  New

Bug description:
  As in the previous kernel 5.11's since .37, keyboard also gets crazy after 
hibernation with kernel 5.11.0-38. 
  My pc is a ENVY x360 13-ar0002ns convert, 13.3, touch screen, AMD RYZEN 
5-3500U Vega running linux Mint 20 Ulyanna. 
  Tks

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


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

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

2021-11-01 Thread Ubuntu Kernel Bot

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

apport-collect 1949358

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

Title:
  Kernel 5.11.0-38 - keyboard not working properly after hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As in the previous kernel 5.11's since .37, keyboard also gets crazy after 
hibernation with kernel 5.11.0-38. 
  My pc is a ENVY x360 13-ar0002ns convert, 13.3, touch screen, AMD RYZEN 
5-3500U Vega running linux Mint 20 Ulyanna. 
  Tks

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


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

[Kernel-packages] [Bug 1949359] [NEW] crash-utility segfault in ubuntu20.04

2021-11-01 Thread jianpingzhao

Public bug reported:

[environment]
* ubuntu version
```
jeff-kvm@ubuntu:/var/crash$ uname -r
5.13.0-17-generic
```
* crash version
```
jeff-kvm@ubuntu:/var/crash$ crash -v

crash 7.2.8
...
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".

```


[Description of problem:]
```
root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

crash 7.2.8
Copyright (C) 2002-2020  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...

WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
values

please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
```
And we can see the following error report(see dmesg):
```
[ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
[ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
```
And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
```


 7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
 7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
 7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
 7cdb1000-7cdb5000 r--p  00:00 0  [vvar]
 7cdb5000-7cdb7000 r-xp  00:00 0  [vdso]
 ff60-ff601000 --xp  00:00 0  
[vsyscall]
...
ProcStatus:
```
 it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000


[How to reproducible]
always
Steps to Reproduce:
1. Generate a vmcore with the sysrq
2. crash vmlinux vmcore
3.

Actual results:

Segmentation fault (core dumped)

Expected results:

crash can work as expected.

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


** Tags: crash segfault

** Tags added: crash

** Tags added: segfault

** Description changed:

- ### environment
+ [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v
  
  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".
+ 
  ```
- ### Description of problem:
+ 
+ 
+ [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic
  
  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program h

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

2021-11-01 Thread Ubuntu Kernel Bot

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

apport-collect 1949359

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.

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


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

[Kernel-packages] [Bug 1949357] Re: linux-azure: Include mana.ko in linux-modules

2021-11-01 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2021-November/125343.html

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

Title:
  linux-azure: Include mana.ko in linux-modules

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The new networking module mana.ko is not included with linux-modules,
  rather it is packaged in linux-modules-extra. Instance types that have
  mana.ko as a boot dependency will not work since Azure images are not
  created using linux-image-extra.

  [Test Plan]

  Download linux-modules and check for mana.ko

  [Where problems could occur]

  mana.ko could go missing

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


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

[Kernel-packages] [Bug 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"

2021-11-01 Thread Eric Desrochers

This has been tested on Cisco Hardware by Field Engineering and the bug
is no longer reproducible.

- Eric

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

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

Title:
  kernel bug found when disconnecting one fiber channel interface on
  Cisco Chassis with fnic DRV_VERSION "1.6.0.47"

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

Bug description:
  [Impact]

  It has been brought to my attention the following:

  "
  We have been experiencing node lockups and degradation when testing fiber 
channel fail over for multi-path PURESTORAGE drives.

  Testing usually consists of either failing over the fabric or the
  local I/O module for the Cisco chassis which houses a number of
  individual blades.

  After rebooting a local Chassis I/O module we see commands like multipath -ll 
hanging.
  Resetting the blades individual fiber channel interface results in the 
following messages.
  "

  6051160.241383]  rport-9:0-1: blocked FC remote port time out: removing 
target and saving binding
  [6051160.252901] BUG: kernel NULL pointer dereference, address: 
0040
  [6051160.262267] #PF: supervisor read access in kernel mode
  [6051160.269314] #PF: error_code(0x) - not-present page
  [6051160.276016] PGD 0 P4D 0
  [6051160.279807] Oops:  [#1] SMP NOPTI
  [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P   O 
 5.4.0-77-generic #86-Ubuntu
  [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, 
BIOS B200M5.4.1.1d.0.0609200543 06/09/2020
  [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport 
[scsi_transport_fc]
  [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic]
  [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 
48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 
78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01
  [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082
  [6051160.353115] RAX:  RBX: 90abdd4c4b00 RCX: 
90d8ab2c2bb0
  [6051160.361983] RDX: 90d8b5467400 RSI:  RDI: 
90d8ab3b4b40
  [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 
90d8b8850800
  [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 
90d8ab2c31f8
  [6051160.388242] R13:  R14: 0246 R15: 
90d8ab2c27b8
  [6051160.396953] FS:  () GS:90d8c088() 
knlGS:
  [6051160.406838] CS:  0010 DS:  ES:  CR0: 80050033
  [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 
007626e0
  [6051160.423146] DR0:  DR1:  DR2: 

  [6051160.431884] DR3:  DR6: fffe0ff0 DR7: 
0400
  [6051160.440615] PKRU: 5554
  [6051160.444337] Call Trace:
  [6051160.447841]  fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc]
  [6051160.455263]  fc_timeout_deleted_rport.cold+0x1bc/0x2c7 
[scsi_transport_fc]
  [6051160.463623]  process_one_work+0x1eb/0x3b0
  [6051160.468784]  worker_thread+0x4d/0x400
  [6051160.473660]  kthread+0x104/0x140
  [6051160.478102]  ? process_one_work+0x3b0/0x3b0
  [6051160.483439]  ? kthread_park+0x90/0x90
  [6051160.488213]  ret_from_fork+0x1f/0x40
  [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) 
zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter 
ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle 
iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock 
unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag 
inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter 
bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common 
skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp 
kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca 
ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid 
sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor
  [6051160.492928]  async_tx xor raid6_pq libcrc32c raid1 raid0 multipath 
linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper 
crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect 
ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid 
cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi
  [6051160.632623] CR2: 00

Re: [Kernel-packages] [Bug 1939402] Re: Touchpad not working correctly after Ubuntu Update

2021-11-01 Thread mehmet

Please find the attached dmesg file.

Thanks,

On Mon, Nov 1, 2021 at 1:11 PM SadashivRao VitthalRao Gaikwad <
1939...@bugs.launchpad.net> wrote:

> Ran the above command: sudo dmesg > dmesg.txt
> Attached below is the text file.
>
> Update: The touchpad started working normally since the start of this
> month.
>
> I used to run these two commands in my terminal:
> 1. sudo modprobe -r psmouse
> 2. sudo modprobe psmouse
> after every boot up and the touch pad would then work fine.
>
> On Wed, Aug 11, 2021 at 7:50 AM Daniel van Vugt <
> 1939...@bugs.launchpad.net>
> wrote:
>
> > Please run this command:
> >
> >   sudo dmesg > dmesg.txt
> >
> > and attach the resulting text file here. We need to know more details
> > about the model of machine.
> >
> > ** Changed in: linux-signed-hwe-5.11 (Ubuntu)
> >Status: New => Incomplete
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1939402
> >
> > Title:
> >   Touchpad not working correctly after Ubuntu Update
> >
> > Status in linux-signed-hwe-5.11 package in Ubuntu:
> >   Incomplete
> >
> > Bug description:
> >   xinput list
> >
> >   When I run this command I do not see the touchpad listed.
> >
> >   cat /proc/bus/input/devices
> >
> >   In this command too I do not see the Touchpad.
> >
> >   ProblemType: Bug
> >   DistroRelease: Ubuntu 20.04
> >   Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
> >   ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
> >   Uname: Linux 5.11.0-25-generic x86_64
> >   ApportVersion: 2.20.11-0ubuntu27.18
> >   Architecture: amd64
> >   CasperMD5CheckResult: skip
> >   CurrentDesktop: ubuntu:GNOME
> >   Date: Tue Aug 10 18:04:56 2021
> >   InstallationDate: Installed on 2021-06-26 (45 days ago)
> >   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> > (20210209.1)
> >   SourcePackage: linux-signed-hwe-5.11
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions
> >
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1939402
>
> Title:
>   Touchpad not working correctly after Ubuntu Update
>
> Status in linux-signed-hwe-5.11 package in Ubuntu:
>   Expired
>
> Bug description:
>   xinput list
>
>   When I run this command I do not see the touchpad listed.
>
>   cat /proc/bus/input/devices
>
>   In this command too I do not see the Touchpad.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
>   ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
>   Uname: Linux 5.11.0-25-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Aug 10 18:04:56 2021
>   InstallationDate: Installed on 2021-06-26 (45 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   SourcePackage: linux-signed-hwe-5.11
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions
>
>


** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1939402/+attachment/5537472/+files/dmesg.txt

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

Title:
  Touchpad not working correctly after Ubuntu Update

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Expired

Bug description:
  xinput list

  When I run this command I do not see the touchpad listed.

  cat /proc/bus/input/devices

  In this command too I do not see the Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 10 18:04:56 2021
  InstallationDate: Installed on 2021-06-26 (45 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions


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

[Kernel-packages] [Bug 1896448] Re: ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle / B-5.4-azure / B-5.4

2021-11-01 Thread Kleber Sacilotto de Souza

rtnetlink.sh from selftests/net is still failing on the 5.4 kernels in
Bionic, however the issues covered by this bug report are now fixed.

08:26:14 DEBUG| [stdout] # selftests: net: rtnetlink.sh
08:26:14 DEBUG| [stdout] # PASS: policy routing
08:26:14 DEBUG| [stdout] # PASS: route get
08:26:20 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
08:26:21 DEBUG| [stdout] # PASS: promote_secondaries complete
08:26:21 DEBUG| [stdout] # PASS: tc htb hierarchy
08:26:21 DEBUG| [stdout] # PASS: gre tunnel endpoint
08:26:21 DEBUG| [stdout] # PASS: gretap
08:26:21 DEBUG| [stdout] # SKIP: ip6gretap: external mode: iproute2 too old
08:26:21 DEBUG| [stdout] # PASS: ip6gretap
08:26:22 DEBUG| [stdout] # PASS: erspan
08:26:22 DEBUG| [stdout] # SKIP: ip6erspan: external mode: iproute2 too old
08:26:22 DEBUG| [stdout] # PASS: ip6erspan
08:26:22 DEBUG| [stdout] # PASS: bridge setup
08:26:25 DEBUG| [stdout] # PASS: ipv6 addrlabel
08:26:25 DEBUG| [stdout] # PASS: set ifalias 
bb405219-54ca-4a70-a0c0-586320bfa917 for test-dummy0
08:26:25 DEBUG| [stdout] # PASS: vrf
08:26:25 DEBUG| [stdout] # FAIL: vxlan
08:26:25 DEBUG| [stdout] # PASS: fou
08:26:25 DEBUG| [stdout] # PASS: macsec
08:26:25 DEBUG| [stdout] # PASS: ipsec
08:28:27 DEBUG| [stdout] # PASS: ipsec_offload
08:28:27 DEBUG| [stdout] # SKIP: fdb get tests: iproute2 too old
08:28:27 DEBUG| [stdout] # SKIP: fdb get tests: iproute2 too old
08:28:27 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

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

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

Title:
  ip6gretap / erspan / ip6erspan in rtnetlink.sh from net of
  ubuntu_kernel_selftests failed on B-5.4-aws / B-5.4-gke / B-5.4-oracle
  / B-5.4-azure / B-5.4

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]
  When running the net/rtnetlink.sh selftest from v5.4 on older Ubuntu releases 
(e.g. Bionic 18.04), some of the iproute2 CLI options are not available causing 
the testcase to fail.

  [ Fix ]
  SAUCE patch to detect whether some options not present on older iproute2 
versions are available, skipping or adapting the tests.

  [ Test ]
  Run net/rtnetlink.sh on 5.4 kernels with both Focal and Bionic userspace. The 
test should complete without introducing regressions on Focal and without 
breaking on Bionic.

  [ Where problems could occur ]
  If the checks for the available interfaces are not done correctly, we could 
end up having a smaller coverage on Focal or the tests would still break in 
Bionic.

  [ Original bug description ]
  Issue found on 5.4.0-1025.25~18.04.1, this issue was not spotted before 
fixing the false-negative return value of this rtnetlink.sh test (bug 1890136)

   # Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ hoplimit TTL ]
   # [ encaplimit ELIM ]
   # [ tclass TCLASS ]
   # [ flowlabel FLOWLABEL ]
   # [ dscp inherit ]
   # [ fwmark MARK ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ erspan IDX ]
   #
   # Where: ADDR := IPV6_ADDRESS
   # TTL := { 0..255 } (default=64)
   # KEY := { DOTTED_QUAD | NUMBER }
   # ELIM := { none | 0..255 }(default=4)
   # TCLASS := { 0x0..0xff | inherit }
   # FLOWLABEL := { 0x0..0xf | inherit }
   # MARK := { 0x0..0x | inherit }
   # Cannot find device "ip6gretap00"
   # FAIL: ip6gretap

   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsum ]
   # [ external ]
   # [ fwmark MARK ]
   # [ erspan IDX ]
   #
   # Where: ADDR := { IP_ADDRESS | any }
   # TOS := { NUMBER | inherit }
   # TTL := { 1..255 | inherit }
   # KEY := { DOTTED_QUAD | NUMBER }
   # MARK := { 0x0..0x }
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Cannot find device "erspan00"
   # Usage: ... { gre | gretap | erspan } [ remote ADDR ]
   # [ local ADDR ]
   # [ [i|o]seq ]
   # [ [i|o]key KEY ]
   # [ [i|o]csum ]
   # [ ttl TTL ]
   # [ tos TOS ]
   # [ [no]pmtudisc ]
   # [ [no]ignore-df ]
   # [ dev PHYS_DEV ]
   # [ noencap ]
   # [ encap { fou | gue | none } ]
   # [ encap-sport PORT ]
   # [ encap-dport PORT ]
   # [ [no]encap-csum ]
   # [ [no]encap-csum6 ]
   # [ [no]encap-remcsu

[Kernel-packages] [Bug 1949370] [NEW] Missing modules in linux-modules

2021-11-01 Thread Juerg Haefliger

Public bug reported:

With the introduction of linux-modules-extra, some modules that were
previously provided by linux-modules are now provided by linux-modules-
extra. Since this is a non-essential package which doesn't get install
automatically, we might be missing some 'important' modules. At the
minimum, add all the modules that are required by the raspi DTBs and
overlays.

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

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

** Changed in: linux-raspi (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

** Summary changed:

- MIssing modules in linux-modules
+ Missing modules in linux-modules

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

Title:
  Missing modules in linux-modules

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Impish:
  New

Bug description:
  With the introduction of linux-modules-extra, some modules that were
  previously provided by linux-modules are now provided by linux-
  modules-extra. Since this is a non-essential package which doesn't get
  install automatically, we might be missing some 'important' modules.
  At the minimum, add all the modules that are required by the raspi
  DTBs and overlays.

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


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

[Kernel-packages] [Bug 1949358] Re: Kernel 5.11.0-38 - keyboard not working properly after hibernation

2021-11-01 Thread Daniel Bacellar

Command not found: "apport-collect 1949358"

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

Title:
  Kernel 5.11.0-38 - keyboard not working properly after hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As in the previous kernel 5.11's since .37, keyboard also gets crazy after 
hibernation with kernel 5.11.0-38. 
  My pc is a ENVY x360 13-ar0002ns convert, 13.3, touch screen, AMD RYZEN 
5-3500U Vega running linux Mint 20 Ulyanna. 
  Tks

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


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

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

2021-11-01 Thread Kleber Sacilotto de Souza

Proposed fix for the reuseport_bpf_numa testcase sent upstream:

https://lore.kernel.org/netdev/20211101145317.286118-1-kleber.so...@canonical.com/T/#u

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on
  ppc64le

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  This issue was extracted from the comment in bug 1812638, since that
  bug will be specific for i386

  This reuseport_bpf_numa in net will fail on PowerPC with:

  The output on B-5.3 P8 is:
   # selftests: net: reuseport_bpf_numa
   #  IPv4 UDP 
   # send node 0, receive socket 0
   # send node 1, receive socket 7
   # ./reuseport_bpf_numa: node id/receive socket mismatch
   not ok 3 selftests: net: reuseport_bpf_numa # exit=1

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


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

[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

2021-11-01 Thread Paul Decoursey

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

I am seeing this as well on my Razer Blade 15 Advanced (2021).  Only
happens after it wakes from sleep.

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

Title:
  i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report
  (16/65535)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  

  Lots of these things

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 2908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 17 20:07:13 2018
  InstallationDate: Installed on 2018-10-10 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ

2021-11-01 Thread dann frazier

The above test failures all seemed to pass upon re-run.

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

Title:
  linux-version sort: argv and stdin behaviors differ

Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-base source package in Focal:
  Fix Committed
Status in linux-base source package in Groovy:
  Fix Committed
Status in linux-base source package in Hirsute:
  Fix Committed
Status in linux-base source package in Impish:
  Fix Released
Status in linux-base package in Debian:
  New

Bug description:
  [Impact]
  `linux-version sort` provides 2 ways to sort kernel version strings: users 
can provide these strings either via the command line or via stdin. Currently 
these methods give different answers for certain version strings (see Test 
Case). The stdin behavior is decidedly incorrect, and this is the mode 
flash-kernel uses. As a real world example, a user with an arm64 u-boot system 
might end up booting 5.8.0-50-generic instead of the expected 
5.8.0-50-generic-64k if both are installed. There maybe additional issues 
caused by this; for example, I found this with our automation that tests 
kernels on various arm64 platforms in version increasing order. Only after 
consulting logs did we realize that 64k kernels were not ever getting booted 
because the tooling (which uses argv mode) disagreed with the kernel installer 
(flash-kernel using stdin mode) about which kernel should be the default.

  It's possible this internal discrepancy can cause other issues due to
  tools disagreeing about which kernel is the latest, but the flash-
  kernel example is the only one I'm aware of at this point.

  [Test Case]
  Using argv:
  $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k
  5.8.0-50-generic
  5.8.0-50-generic-64k

  Using stdin (incorrect):
  $ cat versions.txt
  5.8.0-50-generic
  5.8.0-50-generic-64k
  $ cat versions.txt | linux-version sort
  5.8.0-50-generic-64k
  5.8.0-50-generic

  [Where Problems Could Occur]
  An obvious place where problems could occur is if someone is relying on 
rebooting into the kernel that is incorrectly being sorted greatest. For those 
using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic 
vs. generic-64k case used in the examples above. The generic-64k flavor is 
available in >= 20.10, as well as 20.04-hwe. ARM server users - those most 
likely to want the generic-64k flavor - are very unlikely to be using 
flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and 
are unaffected by this change. We found this on an HP m400 platform which is 
the only Ubuntu certified u-boot-based arm64 server.

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


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

[Kernel-packages] [Bug 1949276] Re: linux-image-raspi PWM not available

2021-11-01 Thread Alex Kurichenko

After installing linux-modules-extra-raspi all required modules are present and 
PWM works as expected
Thank you for help!

The issue can be closed

** Changed in: linux-raspi (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  linux-image-raspi PWM not available

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm using Raspberry Pi 4b with Ubuntu 21.10.
  Seems like all 5.13 kernels don't have PWM support.

  Steps to reproduce:
  - Enable PWM in config.txt:
  `dtoverlay=pwm-2chan,pin=12,func=4,pin2=13,func2=4`

  - Check /sys/class/pwm

  Expected result:
  PWM exists
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0

  - What I currently get:

  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  root@raspberrypi:~#

  ---
  With 5.11.0-1021-raspi everything works as expected:

  root@raspberrypi:~# uname -a
  Linux raspberrypi 5.11.0-1021-raspi #22-Ubuntu SMP PREEMPT Wed Oct 6 17:30:38 
UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  root@raspberrypi:~# ls -l /sys/class/pwm/
  total 0
  lrwxrwxrwx 1 root root 0 окт 31 00:49 pwmchip0 -> 
../../devices/platform/soc/fe20c000.pwm/pwm/pwmchip0

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.10
  ImageMediaBuild: 20210421.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 24ae:2010 Shenzhen Rapoo Technology Co., Ltd. Rapoo 
2.4G Wireless Device
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:61:DD:84 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
root=/dev/mmcblk0p2 rootwait rootfstype=ext4 fixrtc pty.legacy_count=6 
zswap.enabled=1 net.ifnames=0
  ProcVersionSignature: Ubuntu 5.13.0-1010.11-raspi 5.13.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1010-raspi N/A
   linux-backports-modules-5.13.0-1010-raspi  N/A
   linux-firmware 1.201.1
  StagingDrivers: bcm2835_mmal_vchiq bcm2835_v4l2 vc_sm_cma bcm2835_codec 
bcm2835_isp snd_bcm2835
  Tags:  arm64-image raspi-image impish staging
  Uname: Linux 5.13.0-1010-raspi aarch64
  UpgradeStatus: Upgraded to impish on 2021-08-31 (60 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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


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

[Kernel-packages] [Bug 1949394] [NEW] elantech trackpad don`t work

2021-11-01 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

since i installed linux on my gigabyte p56,the trackpad simply doesn`t
work. When i made a search, i discovered that once i reboot on windows
and then reboot back to linux, it came to life, but in normal
circumstances it is dead. I`ve found a patch that is suggested to work,
but once that doing it i`ll have to do it each time that update the
core, i ask to include the pacth on the main code, if its possible.

The patch and the problem was related on the dollowing link:
https://bugzilla.kernel.org/show_bug.cgi?id=81331#c171

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

-- 
elantech trackpad don`t work
https://bugs.launchpad.net/bugs/1949394
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 1949394] Re: elantech trackpad don`t work

2021-11-01 Thread Paul White

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

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

Title:
  elantech trackpad don`t work

Status in linux package in Ubuntu:
  New

Bug description:
  since i installed linux on my gigabyte p56,the trackpad simply doesn`t
  work. When i made a search, i discovered that once i reboot on windows
  and then reboot back to linux, it came to life, but in normal
  circumstances it is dead. I`ve found a patch that is suggested to
  work, but once that doing it i`ll have to do it each time that update
  the core, i ask to include the pacth on the main code, if its
  possible.

  The patch and the problem was related on the dollowing link:
  https://bugzilla.kernel.org/show_bug.cgi?id=81331#c171

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


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

[Kernel-packages] [Bug 1949394] Re: elantech trackpad don`t work

2021-11-01 Thread hernane

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=81331
   Importance: Unknown
   Status: Unknown

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

Title:
  elantech trackpad don`t work

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  since i installed linux on my gigabyte p56,the trackpad simply doesn`t
  work. When i made a search, i discovered that once i reboot on windows
  and then reboot back to linux, it came to life, but in normal
  circumstances it is dead. I`ve found a patch that is suggested to
  work, but once that doing it i`ll have to do it each time that update
  the core, i ask to include the pacth on the main code, if its
  possible.

  The patch and the problem was related on the dollowing link:
  https://bugzilla.kernel.org/show_bug.cgi?id=81331#c171

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


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

[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in

2021-11-01 Thread Tim Gardner

** Summary changed:

- linux-azure: Include mana.ko in linux-modules
+ linux-azure: make mana.ko built-in

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

Title:
  linux-azure: make mana.ko built-in

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The new networking module mana.ko is not included with linux-modules,
  rather it is packaged in linux-modules-extra. Instance types that have
  mana.ko as a boot dependency will not work since Azure images are not
  created using linux-image-extra.

  [Test Plan]

  Download linux-modules and check for mana.ko

  [Where problems could occur]

  mana.ko could go missing

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


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

[Kernel-packages] [Bug 1916303] Re: [RFE] kdump memory estimator

2021-11-01 Thread Guilherme G. Piccoli

V3 posted: https://salsa.debian.org/debian/kdump-
tools/-/merge_requests/16

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

Title:
  [RFE] kdump memory estimator

Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  It would be nice to have a way to estimate memory in the kdump
  environment - not always the default crashkernel reservation fulfill
  users' requirements, specially in big servers with huge memory and
  multiple I/O devices.

  Taking CPUs/RAM/devices into account and using early boot memory information 
+ heuristic, it's possible to infer how much memory is going to be needed by 
kdump - see proposal [0].
  This LP is to track the Debian progress of the issue and the future port to 
Ubuntu kdump packages.

  [0] https://salsa.debian.org/debian/makedumpfile/-/merge_requests/7

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


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

[Kernel-packages] [Bug 1949395] Re: [RFE] Add zstd support for makedumpfile and use it by default

2021-11-01 Thread Guilherme G. Piccoli

Results of the simple experiment:


$ time makedumpfile -l -d 31 -F /proc/vmcore  | cat > dump.l
Copying data  : [100.0 %] /   eta: 
0s
makedumpfile Completed.

real0m0.417s


$ time makedumpfile -c -d 31 -F /proc/vmcore  | cat > dump.c
Copying data  : [100.0 %] |   eta: 
0s
makedumpfile Completed.

real0m1.866s


$ time makedumpfile -z -d 31 -F /proc/vmcore  | cat > dump.z
Copying data  : [100.0 %] /   eta: 
0s
makedumpfile Completed.

real0m0.802s


$ ls -lh dump.*
-rw-r--r-- 1 root root 29M Nov  1 14:04 dump.c
-rw-r--r-- 1 root root 43M Nov  1 14:05 dump.l
-rw-r--r-- 1 root root 26M Nov  1 14:05 dump.z

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

Title:
  [RFE] Add zstd support for makedumpfile and use it by default

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Recently makedumpfile had zstd[0] support added upstream[1]. My
  suggestion here is to backport this work for Debian/Ubuntu and use it
  as default (starting for example in 22.04), since it has a better
  compression time and similar or even better compression rate. In [1]
  there are good experiments, but I did a simple experiment in a small
  VM (2G of RAM, idle) using Debian 11 (results in the first comment].

  I'll open a Debian bug as well.
  Thanks in advance,

  
  Guilherme

  
  [0] https://en.wikipedia.org/wiki/Zstandard
  [1] http://lists.infradead.org/pipermail/kexec/2021-September/023011.html

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


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

[Kernel-packages] [Bug 1949395] [NEW] [RFE] Add zstd support for makedumpfile and use it by default

2021-11-01 Thread Guilherme G. Piccoli

Public bug reported:

Recently makedumpfile had zstd[0] support added upstream[1]. My
suggestion here is to backport this work for Debian/Ubuntu and use it as
default (starting for example in 22.04), since it has a better
compression time and similar or even better compression rate. In [1]
there are good experiments, but I did a simple experiment in a small VM
(2G of RAM, idle) using Debian 11 (results in the first comment].

I'll open a Debian bug as well.
Thanks in advance,


Guilherme


[0] https://en.wikipedia.org/wiki/Zstandard
[1] http://lists.infradead.org/pipermail/kexec/2021-September/023011.html

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

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

Title:
  [RFE] Add zstd support for makedumpfile and use it by default

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Recently makedumpfile had zstd[0] support added upstream[1]. My
  suggestion here is to backport this work for Debian/Ubuntu and use it
  as default (starting for example in 22.04), since it has a better
  compression time and similar or even better compression rate. In [1]
  there are good experiments, but I did a simple experiment in a small
  VM (2G of RAM, idle) using Debian 11 (results in the first comment].

  I'll open a Debian bug as well.
  Thanks in advance,

  
  Guilherme

  
  [0] https://en.wikipedia.org/wiki/Zstandard
  [1] http://lists.infradead.org/pipermail/kexec/2021-September/023011.html

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


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

[Kernel-packages] [Bug 1949397] [NEW] Hirsute update: upstream stable patchset 2021-11-01

2021-11-01 Thread Kamal Mostafa

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2021-11-01
   from git://git.kernel.org/

PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
PCI: aardvark: Fix reporting CRS value
console: consume APC, DM, DCS
ARM: Qualify enabling of swiotlb_init()
ARM: 9077/1: PLT: Move struct plt_entries definition to header
ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
ARM: 9079/1: ftrace: Add MODULE_PLTS support
ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
sctp: validate chunk size in __rcv_asconf_lookup
sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
coredump: fix memleak in dump_vma_snapshot()
um: virtio_uml: fix memory leak on init failures
dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
perf test: Fix bpf test sample mismatch reporting
perf tools: Allow build-id with trailing zeros
thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
9p/trans_virtio: Remove sysfs file on probe failure
prctl: allow to setup brk for et_dyn executables
nilfs2: use refcount_dec_and_lock() to fix potential UAF
profiling: fix shift-out-of-bounds bugs
PM: sleep: core: Avoid setting power.must_resume to false
pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
dmaengine: idxd: fix wq slot allocation index check
platform/chrome: sensorhub: Add trace events for sample
platform/chrome: cros_ec_trace: Fix format warnings
ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
ceph: cancel delayed work instead of flushing on mdsc teardown
Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
thermal/core: Fix thermal_cooling_device_register() prototype
drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
parisc: Move pci_dev_is_behind_card_dino to where it is used
iommu/amd: Relocate GAMSup check to early_enable_iommus
dmaengine: idxd: depends on !UML
dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
dmaengine: ioat: depends on !UML
dmaengine: xilinx_dma: Set DMA mask for coherent APIs
ceph: request Fw caps before updating the mtime in ceph_write_iter
ceph: remove the capsnaps when removing caps
ceph: lockdep annotations for try_nonblocking_invalidate
btrfs: update the bdev time directly when closing
btrfs: fix lockdep warning while mounting sprout fs
nilfs2: fix memory leak in nilfs_sysfs_create_device_group
nilfs2: fix NULL pointer in nilfs_##name##_attr_release
nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
habanalabs: add validity check for event ID received from F/W
pwm: img: Don't modify HW state in .remove() callback
pwm: rockchip: Don't modify HW state in .remove() callback
pwm: stm32-lp: Don't modify HW state in .remove() callback
blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
rtc: rx8010: select REGMAP_I2C
sched/idle: Make the idle timer expire in hard interrupt context
drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
RDMA/mlx5: Fix xlt_chunk_align calculation
staging: rtl8723bs: fix wpa_set_auth_algs() function
dmaengine: idxd: have command status always set
dmaengine: idxd: clear block on fault flag when clear wq
arm64: mm: limit linear region to 51 bits for KVM in nVHE mode
s390: add kmemleak annotation in stack_alloc()
ceph: fix memory leak on decode error in ceph_handle_caps
btrfs: delay blkdev_put until after the device remove
thermal/drivers/rcar_gen3_thermal: Store TSC id as unsigned int
habanalabs: fix nullifying of destroyed mmu pgt pool
block: genhd: don't call blkdev_show() with major_names_lock held
io_uring: fix off-by-one in BUILD_BUG_ON check of __REQ_F_LAST_BIT

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

** Affects: linux (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

[Kernel-packages] [Bug 1949397] Re: Hirsute update: upstream stable patchset 2021-11-01

2021-11-01 Thread Kamal Mostafa

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     upstream stable patchset 2021-11-01
+ 
+ Ported from the following upstream stable releases:
+ v5.10.69, v5.14.8
+ 
     from git://git.kernel.org/
  
  PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
  PCI: aardvark: Fix reporting CRS value
  console: consume APC, DM, DCS
  ARM: Qualify enabling of swiotlb_init()
  ARM: 9077/1: PLT: Move struct plt_entries definition to header
  ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
  ARM: 9079/1: ftrace: Add MODULE_PLTS support
  ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
  sctp: validate chunk size in __rcv_asconf_lookup
  sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
  staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
  coredump: fix memleak in dump_vma_snapshot()
  um: virtio_uml: fix memory leak on init failures
  dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
  perf test: Fix bpf test sample mismatch reporting
  perf tools: Allow build-id with trailing zeros
  thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
  9p/trans_virtio: Remove sysfs file on probe failure
  prctl: allow to setup brk for et_dyn executables
  nilfs2: use refcount_dec_and_lock() to fix potential UAF
  profiling: fix shift-out-of-bounds bugs
  PM: sleep: core: Avoid setting power.must_resume to false
  pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
  pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
  dmaengine: idxd: fix wq slot allocation index check
  platform/chrome: sensorhub: Add trace events for sample
  platform/chrome: cros_ec_trace: Fix format warnings
  ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
  ceph: cancel delayed work instead of flushing on mdsc teardown
  Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
  tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
  thermal/core: Fix thermal_cooling_device_register() prototype
  drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
  drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
  dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
  parisc: Move pci_dev_is_behind_card_dino to where it is used
  iommu/amd: Relocate GAMSup check to early_enable_iommus
  dmaengine: idxd: depends on !UML
  dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
  dmaengine: ioat: depends on !UML
  dmaengine: xilinx_dma: Set DMA mask for coherent APIs
  ceph: request Fw caps before updating the mtime in ceph_write_iter
  ceph: remove the capsnaps when removing caps
  ceph: lockdep annotations for try_nonblocking_invalidate
  btrfs: update the bdev time directly when closing
  btrfs: fix lockdep warning while mounting sprout fs
  nilfs2: fix memory leak in nilfs_sysfs_create_device_group
  nilfs2: fix NULL pointer in nilfs_##name##_attr_release
  nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
  habanalabs: add validity check for event ID received from F/W
  pwm: img: Don't modify HW state in .remove() callback
  pwm: rockchip: Don't modify HW state in .remove() callback
  pwm: stm32-lp: Don't modify HW state in .remove() callback
  blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
  blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
  rtc: rx8010: select REGMAP_I2C
  sched/idle: Make the idle timer expire in hard interrupt context
  drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
  RDMA/mlx5: Fix xlt_chunk_align calculation
  staging: rtl8723bs: fix wpa_set_auth_algs() function
  dmaengine: idxd: have command status always set
  dmaengine: idxd: clear block on fault flag when clear wq
  arm64: mm: limit linear region to 51 bits for KVM in nVHE mode
  s390: add kmemleak annotation in stack_alloc()
  ceph: fix memory leak on decode error in ceph_handle_caps
  btrfs: delay blkdev_put until after the device remove
  thermal/drivers/rcar_gen3_thermal: Store TSC id as unsigned int
  habanalabs: fix nullifying of destroyed mmu pgt pool
  block: genhd: don't call blkdev_show() with major_names_lock held
  io_uring: fix off-by-one in BUILD_BUG_ON check of __REQ_F_LAST_BIT
+ UBUNTU: upstream stable to v5.10.69, v5.14.8

-- 
You rece

[Kernel-packages] [Bug 1923515] Re: [Dell XPS 15 9500] New touchpad detected as "PS/2 Logitech Wheel Mouse"

2021-11-01 Thread Brian Saghy

Update: I got this working today with kernel v5.15. I may have had a few
missing modules missing from my config (I failed to diff old vs new to
specify which ones - I think some I2C related things) but my touchpad is
now recognized and working again!

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

Title:
  [Dell XPS 15 9500] New touchpad detected as "PS/2 Logitech Wheel
  Mouse"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been using Ubuntu 20.04 on a Dell XPS 15 9550. The laptop's
  touchpad had a hardware defect common to the model (nicknamed
  "wobble") so Dell sent a tech to replace it. The new touchpad looks
  identical to the original but the kernel doesn't correctly detect it.
  The device does work, but appears to the kernel as a "PS/2 Logitech
  Wheel Mouse," which prevents the use of features like two-finger
  scrolling, disabling tap to click, and palm detection.

  A good summary of my troubleshooting steps are here:
  
https://askubuntu.com/questions/1330555/touchpad-detected-as-ps-2-logitech-wheel-mouse-dell-xps-15-ubuntu-20-04

  Importantly, I've tried a mainline kernel downloaded from Ubuntu
  (5.11.12 and a 5.12.0 release candidate, whereas the current version
  is a 5.8.0). I've also tried two bootable USB drives containing Ubuntu
  20.04 and 21.04 (release candidate). Nothing has changed the device
  detection or behavior. The issue is identical in the default Ubuntu
  desktop and in Plasma. There are no touchpad settings in the UEFI
  BIOS.

  Per the touchpad detection instructions, I've attached the output of 
/proc/bus/input/devices, Xorg.0.log, and the `xinput --list` command. My 
suspicion is that Dell has ordered a brand new touchpad model for which there 
is no kernel driver; looking at the logs, the previous model was an elantech, 
but I'm not sure if the new one is as well.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edholden   1571 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-11 (183 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 15 9500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=a8be5c03-8499-4474-932d-725877e9cc6c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.10
  Tags:  focal
  Uname: Linux 5.8.0-48-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: 12/24/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0RDX6T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RDX6T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

2021-11-01 Thread Gerry Paradis

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

Same thing with Ubuntu on Xorg

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

Title:
  Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1949397] Re: Hirsute update: upstream stable patchset 2021-11-01

2021-11-01 Thread Kelsey Skunberg

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Hirsute update: upstream stable patchset 2021-11-01

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2021-11-01

  Ported from the following upstream stable releases:
  v5.10.69, v5.14.8

     from git://git.kernel.org/

  PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
  PCI: aardvark: Fix reporting CRS value
  console: consume APC, DM, DCS
  ARM: Qualify enabling of swiotlb_init()
  ARM: 9077/1: PLT: Move struct plt_entries definition to header
  ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
  ARM: 9079/1: ftrace: Add MODULE_PLTS support
  ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
  sctp: validate chunk size in __rcv_asconf_lookup
  sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
  staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
  coredump: fix memleak in dump_vma_snapshot()
  um: virtio_uml: fix memory leak on init failures
  dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
  perf test: Fix bpf test sample mismatch reporting
  perf tools: Allow build-id with trailing zeros
  thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
  9p/trans_virtio: Remove sysfs file on probe failure
  prctl: allow to setup brk for et_dyn executables
  nilfs2: use refcount_dec_and_lock() to fix potential UAF
  profiling: fix shift-out-of-bounds bugs
  PM: sleep: core: Avoid setting power.must_resume to false
  pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
  pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
  dmaengine: idxd: fix wq slot allocation index check
  platform/chrome: sensorhub: Add trace events for sample
  platform/chrome: cros_ec_trace: Fix format warnings
  ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
  ceph: cancel delayed work instead of flushing on mdsc teardown
  Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
  tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
  thermal/core: Fix thermal_cooling_device_register() prototype
  drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
  drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
  dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
  parisc: Move pci_dev_is_behind_card_dino to where it is used
  iommu/amd: Relocate GAMSup check to early_enable_iommus
  dmaengine: idxd: depends on !UML
  dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
  dmaengine: ioat: depends on !UML
  dmaengine: xilinx_dma: Set DMA mask for coherent APIs
  ceph: request Fw caps before updating the mtime in ceph_write_iter
  ceph: remove the capsnaps when removing caps
  ceph: lockdep annotations for try_nonblocking_invalidate
  btrfs: update the bdev time directly when closing
  btrfs: fix lockdep warning while mounting sprout fs
  nilfs2: fix memory leak in nilfs_sysfs_create_device_group
  nilfs2: fix NULL pointer in nilfs_##name##_attr_release
  nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
  habanalabs: add validity check for event ID received from F/W
  pwm: img: Don't modify HW state in .remove() callback
  pwm: rockchip: Don't modify HW state in .remove() callback
  pwm: stm32-lp: Don't modify HW state in .remove() callback
  blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
  blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
  rtc: rx8010: select REGMAP_I2C
  sched/idle: Make the idle timer expire in hard interrupt context
  drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
  RDMA/mlx5: Fix xlt_chunk_align calculation
  staging: rtl8723bs: fix wpa_set_auth_algs() function
  dmaengine: idxd: have command status always set
  dmaengine: idxd: clear block on fault flag when clear wq
  arm64: mm: limit linear region to 51 bits for KVM in nVHE mode
  s390: add kmemleak annotation in stack_alloc()
  ceph: fix memory leak on decode err

[Kernel-packages] [Bug 1949359] Re: crash-utility segfault in ubuntu20.04

2021-11-01 Thread jianpingzhao

apport information

** Tags added: apport-collected focal

** Description changed:

  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v
  
  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".
  
  ```
  
  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic
  
  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...
  
  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values
  
  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  
  
   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000
  
  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.
  
  Actual results:
  
  Segmentation fault (core dumped)
  
  Expected results:
  
  crash can work as expected.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-09-16 (46 days ago)
+ InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-17-generic 
root=UUID=01b5bca7-25cc-400f-a6ce-fae7939734cc ro find_preseed=/preseed.cfg 
auto noprompt priority=criti

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package:

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: li

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package:

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  P

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Pac

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Packa

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform

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

2021-11-01 Thread jianpingzhao

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1949359/+attachment/5537530/+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/1949359

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Pac

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

2021-11-01 Thread jianpingzhao

apport information

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual

[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

2021-11-01 Thread Daniel van Vugt

If the bug is the same for Xorg and Wayland then that suggests you need
a kernel fix (the 'linux' source package). Can you please try some
slightly older kernels and see which was the last working version for
you?

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

** This bug is no longer a duplicate of bug 1929650
   Screen doesn't turn off when using Wayland on some devices

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

Title:
  Power Savings doesn't turn monitor off in Wayland on NUC8i5INH

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  On previous versions of Ubuntu, after 5 minutes, my monitor would turn
  off as per settings. Since I reinstalled fresh 21.10, this is not
  happening. Screen becomes black and stays powered on.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 30 08:11:02 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / 
E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 
MCM] [8086:2079]
  InstallationDate: Installed on 2021-10-14 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: Intel(R) Client Systems NUC8i5INH
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: INWHL357.0043.2021.0817.1957
  dmi.board.name: NUC8i5INB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K29935-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: IN
  dmi.product.name: NUC8i5INH
  dmi.product.sku: BXNUC8i5INHPA
  dmi.product.version: K47340-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Kernel-packages] [Bug 1939402] Re: [Dell Inspiron N5010] Touchpad not working correctly after Ubuntu Update

2021-11-01 Thread Daniel van Vugt

Fix released per comment #4:

> Update: The touchpad started working normally since the start of this
month.

** Summary changed:

- Touchpad not working correctly after Ubuntu Update
+ [Dell Inspiron N5010] Touchpad not working correctly after Ubuntu Update

** Changed in: linux-signed-hwe-5.11 (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  [Dell Inspiron N5010] Touchpad not working correctly after Ubuntu
  Update

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Fix Released

Bug description:
  xinput list

  When I run this command I do not see the touchpad listed.

  cat /proc/bus/input/devices

  In this command too I do not see the Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 10 18:04:56 2021
  InstallationDate: Installed on 2021-06-26 (45 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939402/+subscriptions


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

[Kernel-packages] [Bug 1948813] Re: Nvidia-470 kernel driver loads then unloads during boot on GTX 1050 Mobile. No driver loaded in the end.

2021-11-01 Thread Daniel van Vugt

OK, if you've done a new install (of the OS I assume) then we can't
investigate the old issue further.

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

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

Title:
  Nvidia-470 kernel driver loads then unloads during boot on GTX 1050
  Mobile. No driver loaded in the end.

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix

Bug description:
  I lost projecting to my second monitor while updating in ubuntu 20

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  Uname: Linux 5.4.0-89-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 07:55:42 2021
  DistUpgraded: 2021-10-15 08:30:35,667 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 5.4.0-89-generic, x86_64: installed
   nvidia, 470.74, 5.4.0-89-generic, x86_64: installed
   virtualbox, 6.1.26, 5.4.0-88-generic, x86_64: installed
   virtualbox, 6.1.26, 5.4.0-89-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev ff) 
(prog-if ff)
  InstallationDate: Installed on 2021-09-21 (34 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Acer Nitro AN515-52
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=c4de9279-4774-410d-be28-7e7083e0c939 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-15 (10 days ago)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

[Kernel-packages] [Bug 1946393] Re: Fix byte count on fragmented packets in tc ct action

2021-11-01 Thread Bodong Wang

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

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

Title:
  Fix byte count on fragmented packets in tc ct action

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug
   
  First fragmented packets (frag offset = 0) byte len is zeroed 
  when stolen by ip_defrag(). And since act_ct update the stats
  only afterwards (at end of execute), bytes aren't correctly
  accounted for such packets. 
   
  * How to test
   
  Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
  Enable HW offload and configure connection tracking OpenFlow rules as below
  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"

  Run fragmented icmp ping traffic (e.g ping -s 2000)

  dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on 
frag=first rule:
  
ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first),
 packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1)

  bytes would be zero if bug occurs.

  * What it could break.
   
  NA

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


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

[Kernel-packages] [Bug 1946266] Re: Add psample tunnel support and also two fixes for psample issues.

2021-11-01 Thread Bodong Wang

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

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

Title:
  Add psample tunnel support and also two fixes for psample issues.

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug(s)
  Fix psample compilation issue and add tunnel support

  * brief explanation of fixes
  Enhance psample

  * How to test
  Add tc rule with tunnel and sample actions and run traffic. Verify sample 
traffic on the sample interface.

  * What it could break.
  psample could be broke as new function is enabled

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


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

[Kernel-packages] [Bug 1944390] Re: Fix ignoring ct state match of OVS offload to TC/HW

2021-11-01 Thread Bodong Wang

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

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

Title:
  Fix ignoring ct state match of OVS offload to TC/HW

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug
   
  When using OVS with tc to offload connection tracking flows, if user matches 
on ct_state other then trk and est, such as ct_state +rpl, it will be silently 
ignored by TC/HW and might result in wrong actions being executed.
   
  * How to test
   
  Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
  Enable HW offload and configure connection tracking OpenFlow rules which match
  on ct_state +rpl and do different actions based on that match.

  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, 
actions=$dev1"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, 
actions=$dev2"

  With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl 
match, and without they don't have,
  meaning the match is ignored.
   
  * What it could break.

  NA

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


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

[Kernel-packages] [Bug 1881322] Re: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04

2021-11-01 Thread pavan

Hi

We have updated this method and but still, it's not working.

Any Other fix we have.

We have bought 15 laptops Lenovo v14 11 Generation.

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

Title:
  Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing
  Ubuntu 20.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 20.04 is installed in a brand new Lenovo V15-IIL alongside
  Windows 10. According to lenovo's support page, the driver for windows
  is Synaptics 19.5.10.149_Elan 22.4.18.1. In windows the touchpad works
  fine.

  This model has two options in BIOS regarding Fn Keys, a "Smart Fn key"
  that toogles the Fn key on/off each time you press it and a "Foolproof
  Fn Key" that maps the Fn key to Ctrl when you press a combinations of
  keys that does not have a Fn assigned. When I enable the "foolproof fn
  key" in the BIOS, the Fn + F1...F12 and the sound driver stop working
  (i dont have sound, i can't change the volume and the volume icon in
  the GUI does not show). Fn+F6 (to enable/disable touchpad) can't
  enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fdadam 1434 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 13:08:24 2020
  InstallationDate: Installed on 2020-05-28 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius 
DX-120 Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=fd0c8ed1-6032-467c-9902-3094e6740be8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.product.name: 82C5
  dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
  dmi.product.version: Lenovo V15-IIL
  dmi.sys.vendor: LENOVO

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


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

96 matches

Mail list logo