[Kernel-packages] [Bug 2020091] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


[Kernel-packages] [Bug 2020091] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


[Kernel-packages] [Bug 2020141] Re: Ubuntu 22.04 Screen Flickering Left Hand of the screen

2023-05-18 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  Ubuntu 22.04 Screen Flickering Left Hand of the screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Machine:
  Hardware Model: Lenovo IdeaPad 5 Pro 14iTL6
  16gb RAM
  1TB SSD
  Graphics: Mesa Intel XE Graphics (TGL GT2) (Intel IRIS XE Graphics)
  OS: Ubuntu 22.04 64-bit Wayland
  Gnome Version: 42.5

  Kernel Version: 5.19.0.-41-generic

  Bug Description:
  Just bought a laptop and installed Ubuntu 22.04. 
  The screen flickering happens on left-hand side of the screen whenever I'm 
typing, scrolling or coding. Or while something is loading. It doesn't happen 
if it's idle or just watching videos.

   
  Hope someone can help me as it affect my productivity and it's very annoying 
given that I just bought this laptop.

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


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


[Kernel-packages] [Bug 1864425] Re: preadv203, preadv203_64 in ubuntu_ltp_syscalls failed on X-i386 / B-i386 with ENOSPC on btrfs

2023-05-18 Thread Po-Hsu Lin
** Summary changed:

- preadv203, preadv203_64 in ubuntu_ltp_syscalls failed on X-i386 / B-i386 with 
ENOSPC
+ preadv203, preadv203_64 in ubuntu_ltp_syscalls failed on X-i386 / B-i386 with 
ENOSPC on btrfs

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

Title:
  preadv203, preadv203_64 in ubuntu_ltp_syscalls failed on X-i386 /
  B-i386 with ENOSPC on btrfs

Status in ubuntu-kernel-tests:
  New
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  Issue spotted on i386 node pepe with X-4.15, passed with AMD64 / ARM64
  / P8

  Test failed with:
safe_macros.c:452: BROK: preadv203.c:258: write(486,0xbfed17a1,4294967295) 
failed: ENOSPC (28)

  <<>>
  tag=preadv203 stime=1582530626
  cmdline="preadv203"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_supported_fs_types.c:59: INFO: Kernel supports ext2
  tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports ext3
  tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports ext4
  tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports xfs
  tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports vfat
  tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported
  tst_test.c:1280: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.13 (17-May-2015)
  tst_test.c:1219: INFO: Timeout per run is 0h 05m 00s
  preadv203.c:145: INFO: Number of full_reads 3256, short reads 10, zero len 
reads 0, EAGAIN(s) 78150
  preadv203.c:194: INFO: Cache dropped 25 times
  preadv203.c:180: INFO: Number of writes 600
  preadv203.c:223: PASS: Got some EAGAIN
  tst_test.c:1280: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.13 (17-May-2015)
  tst_test.c:1219: INFO: Timeout per run is 0h 05m 00s
  preadv203.c:145: INFO: Number of full_reads 10445, short reads 10, zero len 
reads 0, EAGAIN(s) 50575
  preadv203.c:194: INFO: Cache dropped 11 times
  preadv203.c:180: INFO: Number of writes 120
  preadv203.c:223: PASS: Got some EAGAIN
  tst_test.c:1280: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.13 (17-May-2015)
  tst_test.c:1219: INFO: Timeout per run is 0h 05m 00s
  preadv203.c:145: INFO: Number of full_reads 2246, short reads 10, zero len 
reads 0, EAGAIN(s) 122001
  preadv203.c:194: INFO: Cache dropped 19 times
  preadv203.c:180: INFO: Number of writes 540
  preadv203.c:223: PASS: Got some EAGAIN
  tst_test.c:1280: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1219: INFO: Timeout per run is 0h 05m 00s
  preadv203.c:145: INFO: Number of full_reads 3511, short reads 10, zero len 
reads 0, EAGAIN(s) 17250
  preadv203.c:194: INFO: Cache dropped 5 times
  preadv203.c:180: INFO: Number of writes 60
  preadv203.c:223: PASS: Got some EAGAIN
  tst_test.c:1280: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with btrfs opts='' extra opts=''
  tst_test.c:1219: INFO: Timeout per run is 0h 05m 00s
  safe_macros.c:452: BROK: preadv203.c:258: write(487,0xbffe7841,4294967295) 
failed: ENOSPC (28)

  Summary:
  passed   4
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=13 termination_type=exited termination_id=2 corefile=no
  cutime=21 cstime=239
  <<>>
  <<>>
  tag=preadv203_64 stime=1582530639
  cmdline="preadv203_64"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0'
  tst_supported_fs_types.c:59: INFO: Kernel supports ext2
  tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports ext3
  tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports ext4
  tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports xfs
  tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:59: INFO: Kernel supports vfat
  tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported
  tst_test.c:1280: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  

[Kernel-packages] [Bug 2016829] Re: Completely support vxlan and erspan for flower

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-bluefield/5.4.0-1063.69
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/2016829

Title:
  Completely support vxlan and erspan for flower

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Committed

Bug description:
  * Explain the bug(s)

  vxlan and erspan are already supported for flower to allow flower to
  match vxlan and erspan options. It needs to support vxlan and erspan
  to act_tunnel_key and related bug fixes for the sake of completeness
  and to avoid bug in the future.

  * Brief explanation of fixes

  Cherry-pick. No adaptation. Add vxlan/erspan support for act_tunnel_key and 
bug fixes.
  c96adff95619 cls_flower: call nla_ok() before nla_next()
  8e1b3ac47866 net: sched: initialize with 0 before setting erspan md->u
  e20d4ff2acd7 net: sched: add erspan option support to act_tunnel_key
  fca3f91cc38a net: sched: add vxlan option support to act_tunnel_key

  * How to test

  For vxlan support:
It is to allow setting vxlan options using the
  act_tunnel_key action. Different from geneve options,
  only one option can be set. And also, geneve options
  and vxlan options can't be set at the same time.
  gbp is the only param for vxlan options:

# ip link add name vxlan0 type vxlan dstport 0 external
# tc qdisc add dev eth0 ingress
# tc filter add dev eth0 protocol ip parent : \
 flower indev eth0 \
ip_proto udp \
action tunnel_key \
set src_ip 10.0.99.192 \
dst_ip 10.0.99.193 \
dst_port 6081 \
id 11 \
vxlan_opts 01020304 \
 action mirred egress redirect dev vxlan0

  For erspan support:
It is to allow setting erspan options using the
  act_tunnel_key action. Different from geneve options,
  only one option can be set. And also, geneve options,
  vxlan options or erspan options can't be set at the
  same time.

  Options are expressed as ver:index:dir:hwid, when ver
  is set to 1, index will be applied while dir and hwid
  will be ignored, and when ver is set to 2, dir and
  hwid will be used while index will be ignored.

# ip link add name erspan1 type erspan external
# tc qdisc add dev eth0 ingress
# tc filter add dev eth0 protocol ip parent : \
 flower indev eth0 \
ip_proto udp \
action tunnel_key \
set src_ip 10.0.99.192 \
dst_ip 10.0.99.193 \
dst_port 6081 \
id 11 \
  erspan_opts 1:2:0:0 \
 action mirred egress redirect dev erspan1

  * What it could break.

  Nothing.

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


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


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

2023-05-18 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 2019152

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

Title:
  [btintel] Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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


[Kernel-packages] [Bug 2019152] Re: Bluetooth crashes in Ubuntu 23.04

2023-05-18 Thread Daniel van Vugt
Indeed it appears to be a kernel/hardware problem:

May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: Hardware error 0x0c
May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: command 0x0c1a tx timeout
May 18 11:26:13 phil-Apollo kernel: Bluetooth: hci0: Opcode 0x c1a failed: -110
May 18 11:26:13 phil-Apollo systemd-sleep[440195]: System returned from sleep 
state.
May 18 11:26:13 phil-Apollo bluetoothd[625]: Controller resume with wake event 
0x0
May 18 11:26:13 phil-Apollo kernel: PM: suspend exit
May 18 11:26:13 phil-Apollo kernel: BUG: kernel NULL pointer dereference, 
address: 0070
May 18 11:26:13 phil-Apollo kernel: #PF: supervisor read access in kernel mode
May 18 11:26:13 phil-Apollo kernel: #PF: error_code(0x) - not-present page
May 18 11:26:13 phil-Apollo kernel: PGD 0 P4D 0 
May 18 11:26:13 phil-Apollo kernel: Oops:  [#1] PREEMPT SMP PTI
May 18 11:26:13 phil-Apollo kernel: CPU: 1 PID: 437412 Comm: kworker/u17:0 
Tainted: GW  6.2.0-20-generic #20-Ubuntu
May 18 11:26:13 phil-Apollo kernel: Hardware name: Entroware Apollo/Apollo, 
BIOS 1.05.02E 03/26/2018
May 18 11:26:13 phil-Apollo kernel: Workqueue: hci0 hci_error_reset [bluetooth]
May 18 11:26:13 phil-Apollo kernel: RIP: 0010:btintel_hw_error+0xa6/0x150 
[btintel]
May 18 11:26:13 phil-Apollo kernel: Code: 89 df 41 b8 c4 09 00 00 48 8d 4d e7 
ba 01 00 00 00 be 22 fc 00 00 e8 19 2d 3b 00 48 89 c3 48 3d 00 f0 ff ff 0f 87 
88 00 00 00 <83> 78 70 0d 75 50 48 8b 80 d0 00 00 00 4c 89 e6 48 c7 c7 84 34 7e
May 18 11:26:13 phil-Apollo kernel: RSP: 0018:b1394e23be30 EFLAGS: 00010207
May 18 11:26:13 phil-Apollo kernel: RAX:  RBX:  
RCX: 
May 18 11:26:13 phil-Apollo kernel: RDX:  RSI:  
RDI: 
May 18 11:26:13 phil-Apollo kernel: RBP: b1394e23be50 R08:  
R09: 
May 18 11:26:13 phil-Apollo kernel: R10:  R11:  
R12: 9320b2e14030
May 18 11:26:13 phil-Apollo kernel: R13:  R14: 9320b2e14730 
R15: 9321fea253c0
May 18 11:26:13 phil-Apollo kernel: FS:  () 
GS:9322f6c4() knlGS:
May 18 11:26:13 phil-Apollo kernel: CS:  0010 DS:  ES:  CR0: 
80050033
May 18 11:26:13 phil-Apollo kernel: CR2: 0070 CR3: 46410003 
CR4: 003706e0
May 18 11:26:13 phil-Apollo kernel: Call Trace:
May 18 11:26:13 phil-Apollo kernel:  
May 18 11:26:13 phil-Apollo kernel:  hci_error_reset+0x32/0xa0 [bluetooth]
May 18 11:26:13 phil-Apollo kernel:  process_one_work+0x222/0x430
May 18 11:26:13 phil-Apollo kernel:  worker_thread+0x50/0x3e0
May 18 11:26:13 phil-Apollo kernel:  ? __pfx_worker_thread+0x10/0x10
May 18 11:26:13 phil-Apollo kernel:  kthread+0xe6/0x110
May 18 11:26:13 phil-Apollo kernel:  ? __pfx_kthread+0x10/0x10
May 18 11:26:13 phil-Apollo kernel:  ret_from_fork+0x29/0x50
May 18 11:26:13 phil-Apollo kernel:  

** Summary changed:

- Bluetooth crashes in Ubuntu 23.04
+ [btintel] Bluetooth crashes in Ubuntu 23.04

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

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

Title:
  [btintel] Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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


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

2023-05-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


[Kernel-packages] [Bug 2020091] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Seth Arnold
I'm very confused about this report, hopefully you can clarify a few
things:

Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7

Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
Setting up linux-headers-6.3.1-060301-generic (6.3.1-060301.202304302031) ...


Which kernels exactly are you running? Which kernels are installed? What 
kernels are configured to boot?

Which DKMS packages have you installed? Where did you get them? Are you
sure they're supposed to work with this wide range of kernels?

Thanks

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


[Kernel-packages] [Bug 2020091] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


[Kernel-packages] [Bug 2020091] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  I am unable update to while I type in terminal
  sudo apt-get update && sudo apt-get upgrade
  Please help me to solve my problem.
 Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ganesh  882 F wireplumber
   /dev/snd/seq:ganesh  879 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu May 18 18:37:00 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (99 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=3757a187-5a56-49cb-b5b3-1ee6159919aa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (25 days ago)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/31/2022:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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


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

2023-05-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installing 23.04 on top of 22.10 on a MacAir 2015

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jltm3151251 F wireplumber
   /dev/snd/controlC0:  jltm3151251 F wireplumber
   /dev/snd/seq:jltm3151248 F pipewire
  CasperMD5CheckResult: pass
  Date: Thu May 18 20:13:43 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-08-08 (648 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IwConfig:
   lono wireless extensions.
   
   anbox0no wireless extensions.
   
   enx3c18a09515c9  no wireless extensions.
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=2c9e2dbc-1875-4943-a51b-05dfa13489c7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-05-19 (0 days ago)
  dmi.bios.date: 01/12/2023
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 481.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-937CB26E2E02BB01
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir7,2
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-937CB26E2E02BB01
  dmi.modalias: 
dmi:bvnAppleInc.:bvr481.0.0.0.0:bd01/12/2023:br0.1:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookAir7,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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


[Kernel-packages] [Bug 2019499] Re: interrupt sound if the disk is writing data (btrfs+compress-zstd)

2023-05-18 Thread Daniel van Vugt
** 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/2019499

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Confirmed
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


[Kernel-packages] [Bug 1754284] Re: Fullscreen windows are tearing in Xorg sessions

2023-05-18 Thread Daniel van Vugt
** No longer affects: mutter (Ubuntu)

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

Title:
  Fullscreen windows are tearing in Xorg sessions

Status in Mutter:
  New
Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
  sessions.

  This is probably to do with composite unredirecting... In compiz we
  have a workaround to avoid this tearing by disallowing unredirect
  ("bypass") in known problematic video players. But I'm not sure if
  mutter has such a workaround/whitelist/blacklist we can use.

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


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


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

2023-05-18 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 2020141

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

Title:
  Ubuntu 22.04 Screen Flickering Left Hand of the screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Machine:
  Hardware Model: Lenovo IdeaPad 5 Pro 14iTL6
  16gb RAM
  1TB SSD
  Graphics: Mesa Intel XE Graphics (TGL GT2) (Intel IRIS XE Graphics)
  OS: Ubuntu 22.04 64-bit Wayland
  Gnome Version: 42.5

  Kernel Version: 5.19.0.-41-generic

  Bug Description:
  Just bought a laptop and installed Ubuntu 22.04. 
  The screen flickering happens on left-hand side of the screen whenever I'm 
typing, scrolling or coding. Or while something is loading. It doesn't happen 
if it's idle or just watching videos.

   
  Hope someone can help me as it affect my productivity and it's very annoying 
given that I just bought this laptop.

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


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


[Kernel-packages] [Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

2023-05-18 Thread Bug Watch Updater
** Changed in: bluez (Fedora)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

Status in GNOME Bluetooth:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in bluez package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: gnome-bluetooth

  Gnome's bluetooth applet should get a bluetooth device's on/off status
  through dbus from SetProperty setting sent by bluetoothd. This
  information was given in
  http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a
  setting controlling this feature: RememberPowered=true in
  /etc/bluetooth/main.conf

  Questions:
  Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't 
do anything for it? Does bluez's SetProperty actually find the last (if even 
saved) bluetooth status?

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 20:54:15 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: gnome-bluetooth 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: gnome-bluetooth
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions


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


[Kernel-packages] [Bug 446657]

2023-05-18 Thread updates
FEDORA-2022-f38f479b8f has been submitted as an update to Fedora 35.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-f38f479b8f

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

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

Status in GNOME Bluetooth:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in bluez package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: gnome-bluetooth

  Gnome's bluetooth applet should get a bluetooth device's on/off status
  through dbus from SetProperty setting sent by bluetoothd. This
  information was given in
  http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a
  setting controlling this feature: RememberPowered=true in
  /etc/bluetooth/main.conf

  Questions:
  Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't 
do anything for it? Does bluez's SetProperty actually find the last (if even 
saved) bluetooth status?

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 20:54:15 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: gnome-bluetooth 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: gnome-bluetooth
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions


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


[Kernel-packages] [Bug 2020143] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

2023-05-18 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Installing 23.04 on top of 22.10 on a MacAir 2015

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jltm3151251 F wireplumber
   /dev/snd/controlC0:  jltm3151251 F wireplumber
   /dev/snd/seq:jltm3151248 F pipewire
  CasperMD5CheckResult: pass
  Date: Thu May 18 20:13:43 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-08-08 (648 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IwConfig:
   lono wireless extensions.
   
   anbox0no wireless extensions.
   
   enx3c18a09515c9  no wireless extensions.
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=2c9e2dbc-1875-4943-a51b-05dfa13489c7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-05-19 (0 days ago)
  dmi.bios.date: 01/12/2023
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 481.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-937CB26E2E02BB01
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir7,2
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-937CB26E2E02BB01
  dmi.modalias: 
dmi:bvnAppleInc.:bvr481.0.0.0.0:bd01/12/2023:br0.1:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookAir7,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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


[Kernel-packages] [Bug 2020143] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess

2023-05-18 Thread Jose Luis Tejada
Public bug reported:

Installing 23.04 on top of 22.10 on a MacAir 2015

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jltm3151251 F wireplumber
 /dev/snd/controlC0:  jltm3151251 F wireplumber
 /dev/snd/seq:jltm3151248 F pipewire
CasperMD5CheckResult: pass
Date: Thu May 18 20:13:43 2023
ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-08-08 (648 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
IwConfig:
 lono wireless extensions.
 
 anbox0no wireless extensions.
 
 enx3c18a09515c9  no wireless extensions.
MachineType: Apple Inc. MacBookAir7,2
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=2c9e2dbc-1875-4943-a51b-05dfa13489c7 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-05-19 (0 days ago)
dmi.bios.date: 01/12/2023
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 481.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-937CB26E2E02BB01
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir7,2
dmi.chassis.asset.tag: Chassis Board Asset Tag#
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-937CB26E2E02BB01
dmi.modalias: 
dmi:bvnAppleInc.:bvr481.0.0.0.0:bd01/12/2023:br0.1:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookAir7,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Installing 23.04 on top of 22.10 on a MacAir 2015

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jltm3151251 F wireplumber
   /dev/snd/controlC0:  jltm3151251 F wireplumber
   /dev/snd/seq:jltm3151248 F pipewire
  CasperMD5CheckResult: pass
  Date: Thu May 18 20:13:43 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-08-08 (648 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IwConfig:
   lono wireless extensions.
   
   anbox0no wireless extensions.
   
   enx3c18a09515c9  no wireless extensions.
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=2c9e2dbc-1875-4943-a51b-05dfa13489c7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed 

[Kernel-packages] [Bug 2020141] [NEW] Ubuntu 22.04 Screen Flickering Left Hand of the screen

2023-05-18 Thread Randolph Pe Benito
Public bug reported:

Machine:
Hardware Model: Lenovo IdeaPad 5 Pro 14iTL6
16gb RAM
1TB SSD
Graphics: Mesa Intel XE Graphics (TGL GT2) (Intel IRIS XE Graphics)
OS: Ubuntu 22.04 64-bit Wayland
Gnome Version: 42.5

Kernel Version: 5.19.0.-41-generic

Bug Description:
Just bought a laptop and installed Ubuntu 22.04. 
The screen flickering happens on left-hand side of the screen whenever I'm 
typing, scrolling or coding. Or while something is loading. It doesn't happen 
if it's idle or just watching videos.

 
Hope someone can help me as it affect my productivity and it's very annoying 
given that I just bought this laptop.

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


** Tags: screen-flickering ubuntu22.04

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

Title:
  Ubuntu 22.04 Screen Flickering Left Hand of the screen

Status in linux package in Ubuntu:
  New

Bug description:
  Machine:
  Hardware Model: Lenovo IdeaPad 5 Pro 14iTL6
  16gb RAM
  1TB SSD
  Graphics: Mesa Intel XE Graphics (TGL GT2) (Intel IRIS XE Graphics)
  OS: Ubuntu 22.04 64-bit Wayland
  Gnome Version: 42.5

  Kernel Version: 5.19.0.-41-generic

  Bug Description:
  Just bought a laptop and installed Ubuntu 22.04. 
  The screen flickering happens on left-hand side of the screen whenever I'm 
typing, scrolling or coding. Or while something is loading. It doesn't happen 
if it's idle or just watching videos.

   
  Hope someone can help me as it affect my productivity and it's very annoying 
given that I just bought this laptop.

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


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


[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries

2023-05-18 Thread Dimitri John Ledkov
> It would be really helpful if at least the existing x32 support in
Ubuntu (I mean x32 packages, gcc/clang archs) would be maintained.

although ubuntu does build and provide many cross-toolchains to "-ports"
arches, they are not guarantedd to be available of provided. I
understand that self building toolchains is difficult, but it is also a
large liability for us to do so.

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

Title:
  Kernels after 5.16 cannot execute x32-ABI binaries

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The kernel configuration option CONFIG_X86_X32_ABI is outcommented for
  kernel 5.17 and higher (amd64). x32 binaries are now reporting:

  cannot execute binary file: Exec format error

  The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC
  intensive tasks) because it saves CPU time and critical resources like
  energy.

  So, the following approach (e.g. Debian) looks more appropriate:

  1. Include the x32-relevant code, but disable its use on standard
  boots:

  CONFIG_X86_X32=y
  CONFIG_X86_X32_DISABLED=y

  2. Users that must run x32 binaries can easily add the GRUB cmdline
  option

  syscall.x32=y

  to enable x32 binaries.

  This could be a good compromise between kernel complexity and resource 
efficiency.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-24 (1 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 10/13/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B650-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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


[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices

2023-05-18 Thread Don Brace
I cloned your repo and found the driver, however I could not find
5.15.0-74.81 to install.

Any thoughts? 5.15.0-74 does not even have smartpqi.

5.19 has the older driver.

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

Title:
  smartpqi: Update 22.04 driver to include recent bug fixes and support
  current generation devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  These patches provide bug fixes and add support for the latest generation of 
OEM PCI devices to ensure customers are able to use Jammy on the recent 
generations of server hardware. This will bring us in line with the other major 
linux distros.

  [Fix]
  There are some outstanding patches already in Linus's tree that can be 
applied to 22.04.
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  The following patches apply to
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

  f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
  e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
  6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
  2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
  cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
  6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
  69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
  85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
  2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
  44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
  331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
  904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
  297bdc540f0e scsi: smartpqi: Close write read holes
  dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
  1d393227fc76 scsi: smartpqi: Add controller fw version to console log
  4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
  8946ea283808 scsi: smartpqi: Fix typo in comment
  c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
  31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
  62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
  291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
  c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
  5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
  c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
  00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
  5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
  27655e9db479 scsi: smartpqi: Update volume size after expansion
  b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
  42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
  9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
  b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
  94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
  70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
  2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
  c57ee4ccb358 scsi: smartpqi: Add PCI IDs
  c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
  64fc9015fbeb scsi: smartpqi: Switch to attribute groups
  0ca190805784 scsi: smartpqi: Call scsi_done() directly

  I added the above SHA1 IDs to a file called:
  backport_linus_6.1_into_22.04

  git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
  git am -s /tmp/patches/*.diff

  All patches applied without any conflicts.

  [Test Plan]
  The upstream driver has undergone extensive testing by Microchip's test team 
before submitting those patches to the upstream kernel. All patches are tested 
and accepted in the upstream kernel at this time.

  One should be able to load the smartpqi driver and verify the version
  is at 2.1.18-045

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3

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


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


[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix

2023-05-18 Thread Frank Heimes
This bug doesn't affect riscv-5.15.
Hence I'm updating the focal verification again to done to unblock the process.

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

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

Title:
  Kernel livepatch ftrace graph fix

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  * Additional patch required to support Livepatch for s390x
  * Fixes Livepatch transition issues when using ftrace graph tracing

  [Test Case]
  * Compile test
  * Boot test
  * Test a Livepatch (patch to /proc/meminfo module)
  * Test Livepatch from ftrace graphed function (via 
https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh)

  [Where things could go wrong]
  * Functionality already exists upstream, once kernel is boot and Livepatch 
tested - should have no regressions

  [Other info]
  * Additional required patch was identified 
(https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1)
 due to ftrace graph livepatch transition issue 
(https://github.com/SUSE/qa_test_klp/issues/17).

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


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


[Kernel-packages] [Bug 2013422] Re: net: sched: allow flower to match vxlan options

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-bluefield - 5.4.0-1062.68

---
linux-bluefield (5.4.0-1062.68) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1062.68 -proposed tracker (LP:
#2016751)

  * CVE-2023-1829
- [Config] bluefield: Make sure CONFIG_NET_CLS_TCINDEX is not available

  * net/sched: cls_api: Support hardware miss to tc action (LP: #2012571)
- Revert "net/sched: flower: fix fl_change() error recovery path"
- Revert "net/sched: flower: Support hardware miss to tc action"
- Revert "net/sched: flower: Move filter handle initialization earlier"
- Revert "net/sched: cls_api: Support hardware miss to tc action"
- Revert "UBUNTU: SAUCE: net/sched: Provide act to offload action"

  [ Ubuntu: 5.4.0-148.165 ]

  * focal/linux: 5.4.0-148.165 -proposed tracker (LP: #2016777)
  * CVE-2023-1829
- net/sched: Retire tcindex classifier
- [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available

 -- Bartlomiej Zolnierkiewicz 
Thu, 27 Apr 2023 16:48:23 +0200

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

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

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

Title:
  net: sched: allow flower to match vxlan options

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released

Bug description:
  * Explain the bug(s)

  In upstream, TCA_POLICE_PKTRATE64 was introduced after
  TCA_FLOWER_KEY_ENC_OPT_VXLAN_GBP. linux-bluefiled only has
  TCA_POLICE_PKTRATE64 related support and does not have VXLAN support
  which will cause "ovs" project compile error because of lacking of
  VXALN GBP related support.

  * Brief explanation of fixes

  Cherry-pick. No adaptation. Add VXLAN support for flower to allow flower to 
match vxlan options
  d8f9dfae49ce net: sched: allow flower to match vxlan options

  * How to test

  1) Compile "ovs" project, build succesfully.
  2) VXLAN option can be used as match condition in tc. eg:
# ip link add name vxlan0 type vxlan dstport 0 external
# tc qdisc add dev vxlan0 ingress
# tc filter add dev vxlan0 protocol ip parent : \
flower \
  enc_src_ip 10.0.99.192 \
  enc_dst_ip 10.0.99.193 \
  enc_key_id 11 \
  vxlan_opts 01020304/ \
  ip_proto udp \
  action mirred egress redirect dev eth0

  * What it could break.

  Nothing.

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


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


[Kernel-packages] [Bug 2012571] Re: net/sched: cls_api: Support hardware miss to tc action

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-bluefield - 5.4.0-1062.68

---
linux-bluefield (5.4.0-1062.68) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1062.68 -proposed tracker (LP:
#2016751)

  * CVE-2023-1829
- [Config] bluefield: Make sure CONFIG_NET_CLS_TCINDEX is not available

  * net/sched: cls_api: Support hardware miss to tc action (LP: #2012571)
- Revert "net/sched: flower: fix fl_change() error recovery path"
- Revert "net/sched: flower: Support hardware miss to tc action"
- Revert "net/sched: flower: Move filter handle initialization earlier"
- Revert "net/sched: cls_api: Support hardware miss to tc action"
- Revert "UBUNTU: SAUCE: net/sched: Provide act to offload action"

  [ Ubuntu: 5.4.0-148.165 ]

  * focal/linux: 5.4.0-148.165 -proposed tracker (LP: #2016777)
  * CVE-2023-1829
- net/sched: Retire tcindex classifier
- [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available

 -- Bartlomiej Zolnierkiewicz 
Thu, 27 Apr 2023 16:48:23 +0200

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

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

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

Title:
  net/sched: cls_api: Support hardware miss to tc action

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released

Bug description:
  * Explain the bug(s)
   
  Currently tc miss interface only supports resuming from a specific tc chain.
  If a packet modification is done before a missable action such as CT and
  there is a miss in CT after it, this may cause a miss match when resuming
  re-executing the same chain in software, and wrong packet count.
  This use case for example is a stateless (static) nat.
   
  * brief explanation of fixes
   
  Add support for missing to a specific action instance, and support
  of per action hardware stats to update what was actually done in hardware.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.
  Enable HW offload and configure regular connection tracking OpenFlow rules
  with packet modification before the CT action (such as statless nat):

   
  e.g:

  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
 ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk 
actions=mod_nw_dst=1.1.1.2,ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new 
actions=ct(commit),output:2"
  ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, 
actions=output:2"
  ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk 
actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, 
actions=mod_nw_src=1.1.1.2,output:1"

   
  Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2

  For VF2, add route and static neighbour to floating (router) ip
  5.5.5.5

  
  Then run a TCP connection, e.g:

  on mlx5 VF1 iperf -s   #(which will listen on 1.1.1.2)
  on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 
5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2)

  
  Optional: In different terminal, while traffic is running, check for offload:
  tcpdump -nnepi  tcp
  and see no iperf tcp packets.

  Dump conntrack with relevant ip:
  cat /proc/net/nf_conntrack | grep -i  1.1.1.1

  See tuples were offloaded:
  ipv4 2 tcp  6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 
packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3

  
  * What it could break.
  offload for modifications + ct and tc packet count.

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


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


[Kernel-packages] [Bug 2015293] Re: netfilter: ctnetlink: Support offloaded conntrack entry deletion

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-bluefield - 5.4.0-1062.68

---
linux-bluefield (5.4.0-1062.68) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1062.68 -proposed tracker (LP:
#2016751)

  * CVE-2023-1829
- [Config] bluefield: Make sure CONFIG_NET_CLS_TCINDEX is not available

  * net/sched: cls_api: Support hardware miss to tc action (LP: #2012571)
- Revert "net/sched: flower: fix fl_change() error recovery path"
- Revert "net/sched: flower: Support hardware miss to tc action"
- Revert "net/sched: flower: Move filter handle initialization earlier"
- Revert "net/sched: cls_api: Support hardware miss to tc action"
- Revert "UBUNTU: SAUCE: net/sched: Provide act to offload action"

  [ Ubuntu: 5.4.0-148.165 ]

  * focal/linux: 5.4.0-148.165 -proposed tracker (LP: #2016777)
  * CVE-2023-1829
- net/sched: Retire tcindex classifier
- [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available

 -- Bartlomiej Zolnierkiewicz 
Thu, 27 Apr 2023 16:48:23 +0200

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

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

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

Title:
  netfilter: ctnetlink: Support offloaded conntrack entry deletion

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released

Bug description:
  * Explain the bug(s)
   
  conntrack -D or conntrack -F doesn't delete offloaded tuples.
   
  * brief explanation of fixes
   
  Add support for to delete offloaded tuples via netlink interface and
  userspace conntrack utility.
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.

  Enable HW offload and configure regular connection tracking OpenFlow
  rules:


  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 a UDP connection, e.g:
  on mlx5 VF1 iperf -s -u
  on mlx5 VF2 iperf -c  -u -t 10 
   

  Optional: In different terminal, while traffic is running, check for
  offload:

  tcpdump -nnepi  udp
  and see no iperf udp packets.
   

  Dump conntrack with relevant ip:

  cat /proc/net/nf_conntrack | grep -i 
   

  See tuples were offloaded:
  ipv4 2 udp 17 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 
bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3
   
  Flush the tuples:
  conntrack -F
   
  Verify tuples are deleted:
  cat /proc/net/nf_conntrack | grep -i 


  Before fix, the above tuple shows again,

  after fix, it's deleted, and shows nothing.

   
  * What it could break.


  Conntrack -F / -D not working on offloaded tuples.

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


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


[Kernel-packages] [Bug 2013758] Re: Add support for 200G/400G speed to bond

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-bluefield - 5.4.0-1062.68

---
linux-bluefield (5.4.0-1062.68) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1062.68 -proposed tracker (LP:
#2016751)

  * CVE-2023-1829
- [Config] bluefield: Make sure CONFIG_NET_CLS_TCINDEX is not available

  * net/sched: cls_api: Support hardware miss to tc action (LP: #2012571)
- Revert "net/sched: flower: fix fl_change() error recovery path"
- Revert "net/sched: flower: Support hardware miss to tc action"
- Revert "net/sched: flower: Move filter handle initialization earlier"
- Revert "net/sched: cls_api: Support hardware miss to tc action"
- Revert "UBUNTU: SAUCE: net/sched: Provide act to offload action"

  [ Ubuntu: 5.4.0-148.165 ]

  * focal/linux: 5.4.0-148.165 -proposed tracker (LP: #2016777)
  * CVE-2023-1829
- net/sched: Retire tcindex classifier
- [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available

 -- Bartlomiej Zolnierkiewicz 
Thu, 27 Apr 2023 16:48:23 +0200

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

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

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

Title:
  Add support for 200G/400G speed to bond

Status in linux-bluefield package in Ubuntu:
  Fix Released
Status in linux-bluefield source package in Focal:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  * 5.4 kernel can't work with bond for 200G/400G NIC

  [Fix]

  * cherry pick the commits to support 200G/400G

  [Test Plan]

  * Test on 200G/400G bond

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


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


[Kernel-packages] [Bug 2015515] Re: net: sched: allow flower to match erspan options

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-bluefield - 5.4.0-1062.68

---
linux-bluefield (5.4.0-1062.68) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1062.68 -proposed tracker (LP:
#2016751)

  * CVE-2023-1829
- [Config] bluefield: Make sure CONFIG_NET_CLS_TCINDEX is not available

  * net/sched: cls_api: Support hardware miss to tc action (LP: #2012571)
- Revert "net/sched: flower: fix fl_change() error recovery path"
- Revert "net/sched: flower: Support hardware miss to tc action"
- Revert "net/sched: flower: Move filter handle initialization earlier"
- Revert "net/sched: cls_api: Support hardware miss to tc action"
- Revert "UBUNTU: SAUCE: net/sched: Provide act to offload action"

  [ Ubuntu: 5.4.0-148.165 ]

  * focal/linux: 5.4.0-148.165 -proposed tracker (LP: #2016777)
  * CVE-2023-1829
- net/sched: Retire tcindex classifier
- [Config]: Make sure CONFIG_NET_CLS_TCINDEX is not available

 -- Bartlomiej Zolnierkiewicz 
Thu, 27 Apr 2023 16:48:23 +0200

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

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

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

Title:
  net: sched: allow flower to match erspan options

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released

Bug description:
  * Explain the bug(s)

  In upstream, TCA_POLICE_PKTRATE64 was introduced after
  TCA_FLOWER_KEY_ENC_OPTS_ERSPAN. linux-bluefiled only has
  TCA_POLICE_PKTRATE64 related support and does not have ERSPAN support
  which might cause "ovs" project compile error because of lacking of
  ERSPAN related support if ovs supports ERSPAN.

  * Brief explanation of fixes

  Cherry-pick. No adaptation. Add ERSPAN support for flower to allow flower to 
match ERSPAN options
  79b1011cb33d net: sched: allow flower to match erspan options

  * How to test

  The options can be described in the form:
  VER:INDEX:DIR:HWID/VER:INDEX_MASK:DIR_MASK:HWID_MASK. When ver is set to 1, 
index will be applied while dir and hwid will be ignored, and when ver is set 
to 2, dir and hwid will be used while index will be ignored.
  Different from geneve, only one option can be set. And also, geneve options, 
vxlan options or erspan options can't be set at the same time.
  Here's an example:
# ip link add name erspan1 type erspan external
# tc qdisc add dev erspan1 ingress
# tc filter add dev erspan1 protocol ip parent : \
flower \
  enc_src_ip 10.0.99.192 \
  enc_dst_ip 10.0.99.193 \
  enc_key_id 11 \
  erspan_opts 1:12:0:0/1::0:0 \
  ip_proto udp \
  action mirred egress redirect dev eth0

  * What it could break.

  Nothing.

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


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


[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints

2023-05-18 Thread Frank Heimes
This bug doesn't affect riscv-5.15, it's an s390x inline assembler thing only.
Hence I'm updating the focal verification again to done to unblock the process.

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

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

Title:
  kernel: fix __clear_user() inline assembly constraints

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


[Kernel-packages] [Bug 2019499] PaInfo.txt

2023-05-18 Thread Pôbiš
apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2019499/+attachment/5673958/+files/PaInfo.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/2019499

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2019499/+attachment/5673956/+files/Lsusb-t.txt

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


[Kernel-packages] [Bug 2019499] Dependencies.txt

2023-05-18 Thread Pôbiš
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2019499/+attachment/5673952/+files/Dependencies.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/2019499

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


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

2023-05-18 Thread Pôbiš
apport information

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   /dev/snd/controlC0:  msi1823 F wireplumber
   /dev/snd/seq:msi1820 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: MSI MS-7721
  Package: pipewire 0.3.65-3
  PackageArchitecture: amd64
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
  UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E45 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

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


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


[Kernel-packages] [Bug 2019499] Re: interrupt sound if the disk is writing data (btrfs+compress-zstd)

2023-05-18 Thread Pôbiš
apport information

** Tags added: apport-collected

** Description changed:

  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write
  
  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.
  
  sound OK if write to ext4 or ramdisc.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  msi1823 F wireplumber
+  /dev/snd/controlC0:  msi1823 F wireplumber
+  /dev/snd/seq:msi1820 F pipewire
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 23.04
+ IwConfig:
+  lono wireless extensions.
+  
+  enp1s0no wireless extensions.
+ MachineType: MSI MS-7721
+ Package: pipewire 0.3.65-3
+ PackageArchitecture: amd64
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz 
root=UUID=ff1c0bd0-6d01-489e-b64e-bede8c284895 radeon.cik_support=1 
amdgpu.cik_support=1 radeon.si_support=1 amdgpu.si_support=1
+ ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-6.2.0-20-generic N/A
+  linux-backports-modules-6.2.0-20-generic  N/A
+  linux-firmware20230323.gitbcdcfbcf-0ubuntu1
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  lunar
+ Uname: Linux 6.2.0-20-generic x86_64
+ UpgradeStatus: Upgraded to lunar on 2022-06-18 (333 days ago)
+ UserGroups: adm cdrom dialout dip disk lpadmin lxd plugdev sambashare sudo 
vboxsf vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 12/15/2014
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: V25.6
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: A78M-E45 (MS-7721)
+ dmi.board.vendor: MSI
+ dmi.board.version: 5.0
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: MSI
+ dmi.chassis.version: 5.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.6:bd12/15/2014:br4.6:svnMSI:pnMS-7721:pvr5.0:rvnMSI:rnA78M-E45(MS-7721):rvr5.0:cvnMSI:ct3:cvr5.0:skuTobefilledbyO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: MS-7721
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: 5.0
+ dmi.sys.vendor: MSI

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  msi1823 F wireplumber
   

[Kernel-packages] [Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

2023-05-18 Thread Avamander
@timmins 
Because things like that only occurred during OOM conditions and never any time 
else. Including never during much higher I/O loads. I'm also quite certain it 
wasn't limited to sdb, but I haven't let such an OOM condition occur in a long 
while, this being one of the reasons.

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

Title:
  Low memory situations result in root partition being remounted read-
  only

Status in cryptsetup:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Instead of killing something with a high niceness low memory
  situations seem to hang something super-ultra-so-very vital, writes
  fail and the root partition is remounted read-only. After that
  systemd-journald starts stupidly spamming and earlier logs are
  rendered unusable.

  I'd post more logs but https://github.com/systemd/systemd/issues/2339
  hasn't been fixed in years.

  This has happened at least four times, across many kernel versions.
  With Ubuntu 18.10, 19.04 and 19.10.

  ```
  [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 
00 10 00
  [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 
0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
  [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871518)
  [827788.409154] Buffer I/O error on device dm-1, logical block 3871518
  [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871519)
  [827788.409164] Buffer I/O error on device dm-1, logical block 3871519
  [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 
00 08 00
  [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871598)
  [827788.409180] Buffer I/O error on device dm-1, logical block 3871598
  [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 
00 38 00
  [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 
0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0
  [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871564)
  [827788.409195] Buffer I/O error on device dm-1, logical block 3871564
  [827788.409196] Buffer I/O error on device dm-1, logical block 3871565
  [827788.409198] Buffer I/O error on device dm-1, logical block 3871566
  [827788.409199] Buffer I/O error on device dm-1, logical block 3871567
  [827788.409201] Buffer I/O error on device dm-1, logical block 3871568
  [827788.409202] Buffer I/O error on device dm-1, logical block 3871569
  [827788.409203] Buffer I/O error on device dm-1, logical block 3871570
  [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 
00 08 00
  [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871558)
  [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 
00 08 00
  [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871562)
  [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 
00 08 00
  [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871601)
  [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 
00 30 00
  [827818.628279] 

Re: [Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

2023-05-18 Thread koba
@Andreas,
I'm waiting for l and k proposed kernel.

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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


[Kernel-packages] [Bug 1868189] Re: Low memory situations result in root partition being remounted read-only

2023-05-18 Thread Tim Shearer
Apols for resurrecting an ancient topic, wondering what makes you
suspect this is related to a low memory condition rather than a hardware
problem (drive not responding to the SATA write)?

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

Title:
  Low memory situations result in root partition being remounted read-
  only

Status in cryptsetup:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Instead of killing something with a high niceness low memory
  situations seem to hang something super-ultra-so-very vital, writes
  fail and the root partition is remounted read-only. After that
  systemd-journald starts stupidly spamming and earlier logs are
  rendered unusable.

  I'd post more logs but https://github.com/systemd/systemd/issues/2339
  hasn't been fixed in years.

  This has happened at least four times, across many kernel versions.
  With Ubuntu 18.10, 19.04 and 19.10.

  ```
  [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 
00 10 00
  [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 
0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
  [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871518)
  [827788.409154] Buffer I/O error on device dm-1, logical block 3871518
  [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871519)
  [827788.409164] Buffer I/O error on device dm-1, logical block 3871519
  [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 
00 08 00
  [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871598)
  [827788.409180] Buffer I/O error on device dm-1, logical block 3871598
  [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 
00 38 00
  [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 
0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0
  [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871564)
  [827788.409195] Buffer I/O error on device dm-1, logical block 3871564
  [827788.409196] Buffer I/O error on device dm-1, logical block 3871565
  [827788.409198] Buffer I/O error on device dm-1, logical block 3871566
  [827788.409199] Buffer I/O error on device dm-1, logical block 3871567
  [827788.409201] Buffer I/O error on device dm-1, logical block 3871568
  [827788.409202] Buffer I/O error on device dm-1, logical block 3871569
  [827788.409203] Buffer I/O error on device dm-1, logical block 3871570
  [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 
00 08 00
  [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871558)
  [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 
00 08 00
  [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871562)
  [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 
00 08 00
  [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 
0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 
writing to inode 1577543 (offset 0 size 0 starting block 3871601)
  [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_TIMEOUT
  [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 
00 30 00
  [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 
0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0
  

[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

2023-05-18 Thread Vadim Sukhomlinov
I verified that on 22.04 5.15.0-72.79 fixes this issue. Thanks!

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

Title:
  [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
  multiple times on Ubuntu 22.04.1 OS during boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  When booted into Ubuntu 22.04.1 OS after installation, observed "Array
  Index out of bounds" Call Trace multiple times in dmesg.

  Call Trace is as follow:
  [ 6.125704] UBSAN: array-index-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
  [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
  [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic 
#59-Ubuntu
  [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022
  [ 6.125710] Workqueue: events work_for_cpu_fn
  [ 6.125716] Call Trace:
  [ 6.125718] 
  [ 6.125720] show_stack+0x52/0x5c
  [ 6.125725] dump_stack_lvl+0x4a/0x63
  [ 6.125731] dump_stack+0x10/0x16
  [ 6.125732] ubsan_epilogue+0x9/0x49
  [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas]
  [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas]
  [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas]
  [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas]
  [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas]
  [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas]
  [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas]
  [ 6.125779] local_pci_probe+0x48/0x90
  [ 6.125783] work_for_cpu_fn+0x17/0x30
  [ 6.125785] process_one_work+0x228/0x3d0
  [ 6.125786] worker_thread+0x223/0x420
  [ 6.125787] ? process_one_work+0x3d0/0x3d0
  [ 6.125788] kthread+0x127/0x150
  [ 6.125790] ? set_kthread_struct+0x50/0x50
  [ 6.125791] ret_from_fork+0x1f/0x30
  [ 6.125796] 
  [ 6.125796] 


  Steps to reproduce:
  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  5. Multiple Call Traces of "array-index-out-of-bounds" are seen

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

  [PATCH v3 0/6] Replace one-element arrays with flexible-array members
  
https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/

  48658213 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_PD_CFG_SEQ_NUM_SYNC

  41e83026 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_FW_RAID_MAP

  ee92366a scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_PD_CFG_SEQ_NUM_SYNC

  eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_DRV_RAID_MAP

  204a29a1 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP_DYNAMIC

  ac23b92b scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP

  [Test Plan]

  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  OS should boot without the Call Trace listed in the Impact field

  [Where problems could occur]

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157

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


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


[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

2023-05-18 Thread Andreas Hasenack
Hi @kobako

> I SRUed for L/K/J/OEM-6.1 and got ACKed.
> https://lists.ubuntu.com/archives/kernel-team/2023-April/138680.html
>
> i verified on machines, one equipped mute-led and another is w/o.
> Is there any issues you are facing?

I see you tested alsa-ucm-conf with an oem-specific kernel, but what
about the normal non-oem kernel that exists in jammy, kinetic, and
lunar? Does this alsa-ucm-conf change have any effect on those non-oem
kernels? We ask because alsa-ucm-conf will be delivered to all ubuntu
users, and not just those who are on dell machines with the oem kernel.

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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


[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2008157

Title:
  [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
  multiple times on Ubuntu 22.04.1 OS during boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  When booted into Ubuntu 22.04.1 OS after installation, observed "Array
  Index out of bounds" Call Trace multiple times in dmesg.

  Call Trace is as follow:
  [ 6.125704] UBSAN: array-index-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
  [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
  [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic 
#59-Ubuntu
  [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022
  [ 6.125710] Workqueue: events work_for_cpu_fn
  [ 6.125716] Call Trace:
  [ 6.125718] 
  [ 6.125720] show_stack+0x52/0x5c
  [ 6.125725] dump_stack_lvl+0x4a/0x63
  [ 6.125731] dump_stack+0x10/0x16
  [ 6.125732] ubsan_epilogue+0x9/0x49
  [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas]
  [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas]
  [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas]
  [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas]
  [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas]
  [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas]
  [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas]
  [ 6.125779] local_pci_probe+0x48/0x90
  [ 6.125783] work_for_cpu_fn+0x17/0x30
  [ 6.125785] process_one_work+0x228/0x3d0
  [ 6.125786] worker_thread+0x223/0x420
  [ 6.125787] ? process_one_work+0x3d0/0x3d0
  [ 6.125788] kthread+0x127/0x150
  [ 6.125790] ? set_kthread_struct+0x50/0x50
  [ 6.125791] ret_from_fork+0x1f/0x30
  [ 6.125796] 
  [ 6.125796] 


  Steps to reproduce:
  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  5. Multiple Call Traces of "array-index-out-of-bounds" are seen

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

  [PATCH v3 0/6] Replace one-element arrays with flexible-array members
  
https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/

  48658213 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_PD_CFG_SEQ_NUM_SYNC

  41e83026 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_FW_RAID_MAP

  ee92366a scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_PD_CFG_SEQ_NUM_SYNC

  eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_DRV_RAID_MAP

  204a29a1 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP_DYNAMIC

  ac23b92b scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP

  [Test Plan]

  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  OS should boot without the Call Trace listed in the Impact field

  [Where problems could occur]

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157

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


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


[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2004262

Title:
  Intel E810 NICs driver in causing hangs when booting and bonds
  configured

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]
* Intel E810-family NICs cause system hangs when booting with bonding 
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock 
where the RDMA driver waits for the RNL lock to complete removal

  [Test Plan]
* Users have reported that after setting up bonding on switch and server 
side, the system will hang when starting network services

  [Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device, 
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under 
RTNL lock

  [Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
  have been added to a bond
* We should look out for auxiliary devices that haven't been properly
  unplugged, or that cause further issues with
  ice_plug_aux_dev()/ice_unplug_aux_dev()

  
  [Original Description]
  jammy 22.04.1
  linux-image-generic 5.15.0-58-generic
  Intel E810-XXV Dual Port NICs in Dell PowerEdge 650

  - 5.15 in jammy -> reproducible
  - 5.19 in hwe-edge -> reproducible
  - 6.2.rc6 in the mainline build -> works
  - Intel's ice driver 1.10.1.2.2 -> works

  After beonding is enabled on switch and server side, the system will
  hang at initialing ubuntu.  The kernel loads but around starting the
  Network Services the system can hang for sometimes 5 minutes, and in
  other cases, indefinitely.

  The message of:

  echo 0 > /proc/sys/kernel/hung_task_timeout_sec”  systemd-resolve
  blocked for more than 120 seconds

  appears, and eventually the Network services just attempts to start
  and never does.  This is with or without DHCP enabled.

  Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
  linux-oem kernels and all exhibit the same failure.

  To work around this. installing the Intel 'ice' driver of version
  1.10.1.2.2 works.  The system doesn't even remotely hang at startup
  and all networking functions remain working (ping, DNS, general
  accessibility).

  The driver can be found at 
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 13:08 seq
   crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5json:
   {
     "result": "skip"
   }DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: 
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R650
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags:  jammy 
uec-images
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/1937133

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On s390x LPAR instances, this test will fail with:
  #   File "linux/tools/testing/selftests/net/devlink_port_split.py", line 
64, in get_if_names
  # if ports[port]['flavour'] == 'physical':
  # KeyError: 'flavour'
not ok 1 selftests: net: devlink_port_split.py # exit=1

  This is because the mlx4 driver in use on this instance does not set
  attributes, therefore `devlink -j port show` command output does not
  contain this "flavour" key.

  [Fix]
  * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no
suitable device available

  This patch can be cherry-picked into our J/K/L kernels.

  [Test]
  Run the patched devlink_port_split.py on s390x LPAR, and it won't
  fail with # KeyError: 'flavour' but marked as SKIP instead.

  [Where problems could occur]
  If this change is incorrect, it may affect the test result, however it's
  limited to testing tools, no actual impact to kernel functions.


  [Original Bug Report]
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25

  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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


[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal

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

Title:
  Connection timeout due to conntrack limits

Status in linux package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-gcp source package in Kinetic:
  New
Status in linux source package in Lunar:
  In Progress
Status in linux-gcp source package in Lunar:
  New

Bug description:
  Customers of GKE 1.25 and 1.26 are affected by the conntrack
  performance issue that causes random connection timeouts. The fix has
  been committed to to the upstream's net git repo and to prodkernel and
  needs to be backported to Ubuntu versions with kernel 5.15.

  https://partnerissuetracker.corp.google.com/issues/272090522

  Fix:

  
https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1

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


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


[Kernel-packages] [Bug 2011926] Re: Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs"

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2011926

Title:
  Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue
  pfifo child qdiscs"

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

Bug description:
  Upstream commit: af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3

  Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo 
child qdiscs"
  taprio_attach() has this logic at the end, which should have been
  removed with the blamed patch (which is now being reverted):

/* access to the child qdiscs is not needed in offload mode */
if (FULL_OFFLOAD_IS_ENABLED(q->flags)) {
kfree(q->qdiscs);
q->qdiscs = NULL;
}

  because otherwise, we make use of q->qdiscs[] even after this array was
  deallocated, namely in taprio_leaf(). Therefore, whenever one would try
  to attach a valid child qdisc to a fully offloaded taprio root, one
  would immediately dereference a NULL pointer.

  $ tc qdisc replace dev eno0 handle 8001: parent root taprio \
num_tc 8 \
map 0 1 2 3 4 5 6 7 \
queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \
max-sdu 0 0 0 0 0 200 0 0 \
base-time 200 \
sched-entry S 80 2 \
sched-entry S a0 2 \
sched-entry S 5f 6 \
flags 2
  $ max_frame_size=1500
  $ data_rate_kbps=2
  $ port_transmit_rate_kbps=100
  $ idleslope=$data_rate_kbps
  $ sendslope=$(($idleslope - $port_transmit_rate_kbps))
  $ locredit=$(($max_frame_size * $sendslope / $port_transmit_rate_kbps))
  $ hicredit=$(($max_frame_size * $idleslope / $port_transmit_rate_kbps))
  $ tc qdisc replace dev eno0 parent 8001:7 cbs \
idleslope $idleslope \
sendslope $sendslope \
hicredit $hicredit \
locredit $locredit \
offload 0

  Unable to handle kernel NULL pointer dereference at virtual address 
0030
  pc : taprio_leaf+0x28/0x40
  lr : qdisc_leaf+0x3c/0x60
  Call trace:
   taprio_leaf+0x28/0x40
   tc_modify_qdisc+0xf0/0x72c
   rtnetlink_rcv_msg+0x12c/0x390
   netlink_rcv_skb+0x5c/0x130
   rtnetlink_rcv+0x1c/0x2c

  The solution is not as obvious as the problem. The code which deallocates
  q->qdiscs[] is in fact copied and pasted from mqprio, which also
  deallocates the array in mqprio_attach() and never uses it afterwards.

  Therefore, the identical cleanup logic of priv->qdiscs[] that
  mqprio_destroy() has is deceptive because it will never take place at
  qdisc_destroy() time, but just at raw ops->destroy() time (otherwise
  said, priv->qdiscs[] do not last for the entire lifetime of the mqprio
  root), but rather, this is just the twisted way in which the Qdisc API
  understands error path cleanup should be done (Qdisc_ops :: destroy() is
  called even when Qdisc_ops :: init() never succeeded).

  Side note, in fact this is also what the comment in mqprio_init()
  says:

  /* pre-allocate qdisc, attachment can't fail */

  Or reworded, mqprio's priv->qdiscs[] scheme is only meant to serve as
  data passing between Qdisc_ops :: init() and Qdisc_ops :: attach().

  [ this comment was also copied and pasted into the initial taprio
commit, even though taprio_attach() came way later ]

  The problem is that taprio also makes extensive use of the q->qdiscs[]
  array in the software fast path (taprio_enqueue() and taprio_dequeue()),
  but it does not keep a reference of its own on q->qdiscs[i] (you'd think
  that since it creates these Qdiscs, it holds the reference, but nope,
  this is not completely true).

  To understand the difference between taprio_destroy() and mqprio_destroy()
  one must look before commit 13511704f8d7 ("net: taprio offload: enforce
  qdisc to netdev queue mapping"), because that just muddied the waters.

  In the "original" taprio design, taprio always attached itself (the root
  Qdisc) to all netdev TX queues, so that dev_qdisc_enqueue() would go
  through taprio_enqueue().

  It also called qdisc_refcount_inc() on itself for as many times as there
  were netdev TX queues, in order to counter-balance what tc_get_qdisc()
 

[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2013088

Title:
  kernel: fix __clear_user() inline assembly constraints

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

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


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


[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal

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

Title:
  expoline.o is packaged unconditionally for s390x

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While this works as expected on Jammy, it won't
  work on some derivatives of it: for example focal:hwe-5.15. On Focal,
  this config can't be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

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


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


[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2013603

Title:
  Kernel livepatch ftrace graph fix

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  * Additional patch required to support Livepatch for s390x
  * Fixes Livepatch transition issues when using ftrace graph tracing

  [Test Case]
  * Compile test
  * Boot test
  * Test a Livepatch (patch to /proc/meminfo module)
  * Test Livepatch from ftrace graphed function (via 
https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh)

  [Where things could go wrong]
  * Functionality already exists upstream, once kernel is boot and Livepatch 
tested - should have no regressions

  [Other info]
  * Additional required patch was identified 
(https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1)
 due to ftrace graph livepatch transition issue 
(https://github.com/SUSE/qa_test_klp/issues/17).

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


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


[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2015372

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Intel has introduced support for their new Emerald Rapids CPU.
  This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
  and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.

  More information about each commit is addressed inline.

  [Commits]

  1. 9c252ecf3036:
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Adjusted the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  2. 5a8a05f165fb18d37526062419774d9088c2a9b9
  "perf/x86/intel/cstate: Add Emerald Rapids"
  Small context adjustment in intel_cstates_match array
  because of missing SPR, RPL and MDL cpu models introduced in
  528c9f1daf20d

  3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  "perf/x86/rapl: Add support for Intel Emerald Rapids"

  Context adjustment due to missing 
  - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
  - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
  - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
  - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"

  4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick

  5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick

  6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick

  7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick

  8. e4b2bc6616e21
  clean cherry-pick

  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  Very low, these are minimal new features, which actually reuse a lot of the 
existing cpu structures/functions.

  

  The following changes since commit
  8feeaa9039a290b978e7855ab82955cd9348fc13

  "platform/x86: intel-uncore-freq: add Emerald Rapids support"

  are available in the Git repository at:

    git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy
  lp2015372

  for you to fetch changes up to commit
  7d88565e6777082265b373733fd93eb3e0914e12

  "EDAC/i10nm: Add Intel Emerald Rapids server support"

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


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


[Kernel-packages] [Bug 2015097] Re: Kernel crash during Mellanox performance testing

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2015097

Title:
  Kernel crash during Mellanox performance testing

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * When performance testing using Mellanox driver, an early decrement
  within an if condition rather than as a result of an if condition is
  causing null pointer crashes.

  [Fix]

  * Clean cherry-pick from upstream 
(https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/)
  * Change landed v5.19 upstream, Kinetic onward not affected

  [Test Case]

  * Compile test
  * Boot test
  * Performance test

  [Where things could go wrong]

  * Regression risk is low, localized fix, purely fixes incorrect logic

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


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


[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2015498

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


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


[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-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/2015855

Title:
  Add split lock detection for EMR

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU. 
  It was backported to Jammy in #lp2015372
   
  The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
  So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.

  With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
  “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”

  Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
  “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.

  This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
   
  [Testing]
   Kernel was built on cbd and boot tested on a VM.
  Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855

  [Regression potential]
   Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
  1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
  2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

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


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


[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit

2023-05-18 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-riscv-5.15 verification-needed-focal

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

Title:
   selftest: fib_tests: Always cleanup before exit

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Copied from the commit message:
  Usage of `set -e` before executing a command causes immediate exit
  on failure, without cleanup up the resources allocated at setup.
  This can affect the next tests that use the same resources,
  leading to a chain of failures.

  A simple fix is to always call cleanup function when the script exists.
  This approach is already used by other existing tests.

  [Fix]
  * b60417a9f2 selftest: fib_tests: Always cleanup before exit

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run the patched fib_tests.sh on KVM kernels, which is expected to fail 
  due to bug 2007458.
  Check with `ip netns`, the ns1 added during setup() should be removed.

  [Where problems could occur]
  Test robustness improvement, this should not break things.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673905/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff

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

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

2023-05-18 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2019736] Re: Fix hangs when connected to Freesync displays

2023-05-18 Thread Timo Aaltonen
6.1.0-1014 will have 6.1.29


** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Fix hangs when connected to Freesync displays

Status in Linux:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  New
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  New
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  New
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

   * Selecting certain resolutions causes hangs when an AMD GPU is
  connected to a display that supports FreeSync

  [ Test Plan ]

   * Verify display with freesync doesn't hang anymore

  [ Where problems could occur ]

   * AMD GPU could stop displaying

  [ Other Info ]

   * This issue was reported upstream to AMD here:  
https://gitlab.freedesktop.org/drm/amd/-/issues/2162
   * It has been fixed in kernel 6.4-rc1:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da5e14909776edea4462672fb4a3007802d262e7

   * AMD will CC it to stable to fix any remaining affected open stable
  releases, but as 5.19 is EOL upstream, want to ensure that Canonical
  picks up this patch in the 5.19 series as well.

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


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


[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.157-0ubuntu6

---
nvidia-graphics-drivers-390 (390.157-0ubuntu6) mantic; urgency=medium

  [ Andrea Righi ]
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/disable-acpi-support-in-linux-6.0.patch,
debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch:
- Better support for linux 6.2 (LP: #2019869).

  [ Paolo Pisati ]
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_6.3.patch:
- Support linux 6.3 ABI (LP: #2019979).

 -- Alberto Milone   Thu, 18 May 2023
10:42:02 +

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

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  New
Status in nvidia-graphics-drivers-390 source package in Lunar:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

2023-05-18 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.157-0ubuntu6

---
nvidia-graphics-drivers-390 (390.157-0ubuntu6) mantic; urgency=medium

  [ Andrea Righi ]
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/disable-acpi-support-in-linux-6.0.patch,
debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch:
- Better support for linux 6.2 (LP: #2019869).

  [ Paolo Pisati ]
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_6.3.patch:
- Support linux 6.3 ABI (LP: #2019979).

 -- Alberto Milone   Thu, 18 May 2023
10:42:02 +

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

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

2023-05-18 Thread Vinay HM
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
  multiple times on Ubuntu 22.04.1 OS during boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  When booted into Ubuntu 22.04.1 OS after installation, observed "Array
  Index out of bounds" Call Trace multiple times in dmesg.

  Call Trace is as follow:
  [ 6.125704] UBSAN: array-index-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
  [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
  [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic 
#59-Ubuntu
  [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022
  [ 6.125710] Workqueue: events work_for_cpu_fn
  [ 6.125716] Call Trace:
  [ 6.125718] 
  [ 6.125720] show_stack+0x52/0x5c
  [ 6.125725] dump_stack_lvl+0x4a/0x63
  [ 6.125731] dump_stack+0x10/0x16
  [ 6.125732] ubsan_epilogue+0x9/0x49
  [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas]
  [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas]
  [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas]
  [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas]
  [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas]
  [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas]
  [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas]
  [ 6.125779] local_pci_probe+0x48/0x90
  [ 6.125783] work_for_cpu_fn+0x17/0x30
  [ 6.125785] process_one_work+0x228/0x3d0
  [ 6.125786] worker_thread+0x223/0x420
  [ 6.125787] ? process_one_work+0x3d0/0x3d0
  [ 6.125788] kthread+0x127/0x150
  [ 6.125790] ? set_kthread_struct+0x50/0x50
  [ 6.125791] ret_from_fork+0x1f/0x30
  [ 6.125796] 
  [ 6.125796] 


  Steps to reproduce:
  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  5. Multiple Call Traces of "array-index-out-of-bounds" are seen

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

  [PATCH v3 0/6] Replace one-element arrays with flexible-array members
  
https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/

  48658213 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_PD_CFG_SEQ_NUM_SYNC

  41e83026 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_FW_RAID_MAP

  ee92366a scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_PD_CFG_SEQ_NUM_SYNC

  eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_DRV_RAID_MAP

  204a29a1 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP_DYNAMIC

  ac23b92b scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP

  [Test Plan]

  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  OS should boot without the Call Trace listed in the Impact field

  [Where problems could occur]

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Summary changed:

- nvidia-dkms-390|470|510 FTBS with linux 6.3
+ nvidia-dkms-390|470|510|515 FTBS with linux 6.3

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470|510 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Patch added: "nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673845/+files/nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff

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

Title:
  nvidia-dkms-390|470|510 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2019152] Re: Bluetooth crashes in Ubuntu 23.04

2023-05-18 Thread Phil Buckley
I've attached the journal.txt as requested.

One more point to add - enabling/disabling flight mode within Ubuntu
does not resolve the problem; but if I enable/disable on the laptop
(there's a key sequence on this Entroware Apollo) then it gets Bluetooth
working again. This might suggest that resetting the hardware is
necessary to resolve which might indicate that the linux bluetooth
support has crashed the silicon.

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

Title:
  Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- nvidia-dkms-390|470 FTBS with linux 6.3
+ nvidia-dkms-390|470|510 FTBS with linux 6.3

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

Title:
  nvidia-dkms-390|470|510 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

2023-05-18 Thread Matthew Ruffell
Its not necessary Loic, linux-hwe is a derivative of the kinetic kernel,
and it will be automatically built and pushed to -proposed in due
course, likely over the next few days.

It will be a part of the 5.19.0-44 HWE kernel. I'll keep an eye on it, I
don't think the HWE kernel is moving to the 6.2 kernel just yet.

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

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

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

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


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


[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

2023-05-18 Thread Matthew Ruffell
** No longer affects: linux-hwe-5.19 (Ubuntu)

** No longer affects: linux-hwe-5.19 (Ubuntu Jammy)

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

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

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

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


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


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

2023-05-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic
  werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  And it says Apport above all.
  Ubuntu 23 is terible one disaster after another

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  AptOrdering:
   libqt5websockets5:amd64: Install
   qownnotes:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arnold 3640 F wireplumber
   /dev/snd/seq:arnold 3637 F pipewire
  CasperMD5CheckResult: unknown
  Date: Thu May 18 12:23:51 2023
  ErrorMessage: subproces van pakket linux-headers-6.2.0-20-generic werd script 
post-installation geïnstalleerd gaf de foutwaarde 1 terug
  InstallationDate: Installed on 2019-02-28 (1539 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ProBook 440 G5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=67b23de9-493d-4cf1-a3b1-73caf37dcf5b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic werd 
script post-installation geïnstalleerd gaf de foutwaarde 1 terug
  UpgradeStatus: Upgraded to lunar on 2023-04-30 (17 days ago)
  dmi.bios.date: 03/12/2018
  dmi.bios.release: 2.5
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.02.05
  dmi.board.name: 837B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.2A.00
  dmi.chassis.asset.tag: 5CD8284LKH
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.42
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.02.05:bd03/12/2018:br2.5:efr2.42:svnHP:pnHPProBook440G5:pvr:rvnHP:rn837B:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr:sku1MJ81AV:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G5
  dmi.product.sku: 1MJ81AV
  dmi.sys.vendor: HP

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


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


[Kernel-packages] [Bug 2020071] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic werd script post-installation ge

2023-05-18 Thread Arnold van Hofwegen
Public bug reported:

And it says Apport above all.
Ubuntu 23 is terible one disaster after another

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
AptOrdering:
 libqt5websockets5:amd64: Install
 qownnotes:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  arnold 3640 F wireplumber
 /dev/snd/seq:arnold 3637 F pipewire
CasperMD5CheckResult: unknown
Date: Thu May 18 12:23:51 2023
ErrorMessage: subproces van pakket linux-headers-6.2.0-20-generic werd script 
post-installation geïnstalleerd gaf de foutwaarde 1 terug
InstallationDate: Installed on 2019-02-28 (1539 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: HP HP ProBook 440 G5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=67b23de9-493d-4cf1-a3b1-73caf37dcf5b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic werd 
script post-installation geïnstalleerd gaf de foutwaarde 1 terug
UpgradeStatus: Upgraded to lunar on 2023-04-30 (17 days ago)
dmi.bios.date: 03/12/2018
dmi.bios.release: 2.5
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.02.05
dmi.board.name: 837B
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.2A.00
dmi.chassis.asset.tag: 5CD8284LKH
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 2.42
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.02.05:bd03/12/2018:br2.5:efr2.42:svnHP:pnHPProBook440G5:pvr:rvnHP:rn837B:rvrKBCVersion02.2A.00:cvnHP:ct10:cvr:sku1MJ81AV:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G5
dmi.product.sku: 1MJ81AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic
  werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  And it says Apport above all.
  Ubuntu 23 is terible one disaster after another

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  AptOrdering:
   libqt5websockets5:amd64: Install
   qownnotes:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arnold 3640 F wireplumber
   /dev/snd/seq:arnold 3637 F pipewire
  CasperMD5CheckResult: unknown
  Date: Thu May 18 12:23:51 2023
  ErrorMessage: subproces van pakket linux-headers-6.2.0-20-generic werd script 
post-installation geïnstalleerd gaf de foutwaarde 1 terug
  InstallationDate: Installed on 2019-02-28 (1539 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ProBook 440 G5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=67b23de9-493d-4cf1-a3b1-73caf37dcf5b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: subproces van pakket linux-headers-6.2.0-20-generic werd 
script post-installation geïnstalleerd gaf de foutwaarde 1 terug
  UpgradeStatus: Upgraded to lunar on 2023-04-30 (17 days ago)
  dmi.bios.date: 03/12/2018
  dmi.bios.release: 2.5
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.02.05
  dmi.board.name: 837B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.2A.00
  dmi.chassis.asset.tag: 5CD8284LKH
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.42
  dmi.modalias: 

[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

2023-05-18 Thread Loïc Minier
I've tested 5.19.0-42.43~22.04.1 from jammy-proposed which had a few
vmwgfx changes listed in its changelog, but it didn't work; I didn't see
the same revert as in 5.19.0-44.45 or a reference to that bug, so I'll
open a jammy task to land this fix there too.

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

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

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

** No longer affects: linux-hwe-5.19 (Ubuntu Kinetic)

** No longer affects: linux (Ubuntu Jammy)

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

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

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

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


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


[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

2023-05-18 Thread Loïc Minier
Is it worth having a separate task for linux-hwe in jammy?

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-hwe-5.19 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2019979/+attachment/5673813/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-390|470 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2020062] [NEW] No HDMI/DP audio output on dock(Nvidia GPU)

2023-05-18 Thread AceLan Kao
Public bug reported:

[Impact]
When the machine is docked with an external monitor, it is able to output 
display, but the HDMI/DP audio output option is lost in DGFF Hybrid 
Discrete/Discrete mode(Nvidia GPU).

[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/

[Test]
Verified on the target machine.

{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux (Ubuntu Lunar)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Lunar)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.1 (Ubuntu Lunar)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Mantic)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.1 (Ubuntu Mantic)
 Importance: Undecided
 Status: Invalid


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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

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

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

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

** Description changed:

  [Impact]
+ When the machine is docked with an external monitor, it is able to output 
display, but the HDMI/DP audio output option is lost in DGFF Hybrid 
Discrete/Discrete mode(Nvidia GPU).
  
  [Fix]
+ Nvidia provides a patch to fix it
+ 
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
  
  [Test]
+ Verified on the target machine.
  
  {Where problems could occur]
+ The patch just adds IDs, and won't lead to any regression.

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

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

Title:
  No  HDMI/DP audio output on dock(Nvidia GPU)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  

[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Summary changed:

- nvidia-dkms-390 FTBS with linux 6.3
+ nvidia-dkms-390|470 FTBS with linux 6.3

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

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

Title:
  nvidia-dkms-390|470 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-390 FTBS with linux 6.3

2023-05-18 Thread Paolo Pisati
** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5673790/+files/nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff

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

Title:
  nvidia-dkms-390 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

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


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


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

2023-05-18 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 2019499

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)

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


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


[Kernel-packages] [Bug 2019499] Re: interrupt sound if the disk is writing data (btrfs+compress-zstd)

2023-05-18 Thread Daniel van Vugt
It sounds like btrfs+compress-zstd is just blocking too much if there is
no problem with ext4.

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

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

Title:
  interrupt sound if the disk is writing data (btrfs+compress-zstd)

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data 
(btrfs+compress-zstd)
  before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) 
only when ending write

  interrupt sound
  net download (15M/bit max) or copy and write to btrfs+compress-zstd. download 
app: (firefox, uget, seamonkey, yt-dlp, synaptic)
  playing app: (vlc, rhythmbox, smplayer)
  interrupted sound even if the file is played from another disc.

  sound OK if write to ext4 or ramdisc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire-bin 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun May 14 13:52:08 2023
  ExecutablePath: /usr/bin/pipewire
  ProcEnviron:
   LANG=sk_SK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago)

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


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


[Kernel-packages] [Bug 2019481] Re: System boots to a black screen when nvidia-390 is installed

2023-05-18 Thread Daniel van Vugt
Possibly related: bug 2019869, bug 2019979

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

Title:
  System boots to a black screen when nvidia-390 is installed

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Upon installing the 3rd party nVidia version 390 drivers for the Dell
  E6520 laptop, after reboot hangs with a black screen and a blinking
  cursor in the upper left hand corner.  Booting to a terminal prompt
  and using "sudo apt remove *nvidia*" and rebooting solves the issue.
  This did NOT happen in 22.04 LTS on this laptop with no other hardware
  or BIOS changes.  This install of 23.04 was a clean install, the 22.04
  install was wiped.

  vendor   : NVIDIA Corporation
  model: GF119M [NVS 4200M]
  driver   : nvidia-driver-390 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  If I install that driver the system will not boot, removing it solves
  the issue.  I've wiped and reinstalled 23.04 4x, both with full
  options and minimal, the problem always returns.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 13 10:46:41 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:1494]
  InstallationDate: Installed on 2023-05-13 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Latitude E6520
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=f7260292-99f4-4e45-a79a-97643cc0cb92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd03/06/2018:br4.6:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:sku:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Kernel-packages] [Bug 2019481] Re: Xorg freeze

2023-05-18 Thread Daniel van Vugt
Thanks for the bug report.

Please reproduce the problem again so we can collect the full system
log, then reboot to a terminal and run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Although your Xorg log already mentions:

[20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at 
PCI:1:0:0.  Please
[20.820] (EE) NVIDIA(GPU-0): check your system's kernel log for 
additional error
[20.820] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common 
Problems in the
[20.820] (EE) NVIDIA(GPU-0): README for additional information.
[20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics 
device!

we still need to see what happened before that.


** Summary changed:

- Xorg freeze
+ System boots to a black screen when nvidia-390 is installed

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

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

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

Title:
  System boots to a black screen when nvidia-390 is installed

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Upon installing the 3rd party nVidia version 390 drivers for the Dell
  E6520 laptop, after reboot hangs with a black screen and a blinking
  cursor in the upper left hand corner.  Booting to a terminal prompt
  and using "sudo apt remove *nvidia*" and rebooting solves the issue.
  This did NOT happen in 22.04 LTS on this laptop with no other hardware
  or BIOS changes.  This install of 23.04 was a clean install, the 22.04
  install was wiped.

  vendor   : NVIDIA Corporation
  model: GF119M [NVS 4200M]
  driver   : nvidia-driver-390 - distro non-free recommended
  driver   : xserver-xorg-video-nouveau - distro free builtin

  If I install that driver the system will not boot, removing it solves
  the issue.  I've wiped and reinstalled 23.04 4x, both with full
  options and minimal, the problem always returns.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 13 10:46:41 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:1494]
  InstallationDate: Installed on 2023-05-13 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Latitude E6520
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=f7260292-99f4-4e45-a79a-97643cc0cb92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd03/06/2018:br4.6:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:sku:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

2023-05-18 Thread Valentijn Sessink
This is a successful docking attempt.

I rebooted my laptop with the dock attached. At about 06:30:30, I decide
to remove the dock, in order to try to replicate the behaviour. At
06:30:37 I'm plugging it in again.

I have not redacted these logs, no obfuscation etc, so yeah, you can see
all the slack.desktop etcetera messages. I hope someone can make
something of this. I can't. I'm just seeing my desktop crash randomly
and I don't know where it comes from.

Best regards,

Valentijn

** Attachment added: "successful docking"
   
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+attachment/5673745/+files/right

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr
  0x4b0 for 1 bytes NAKed)

Status in GNOME Shell:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions


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


[Kernel-packages] [Bug 2019152] Re: Bluetooth crashes in Ubuntu 23.04

2023-05-18 Thread Daniel van Vugt
Next time the problem happens, before rebooting please run:

  journalctl -b0 > journal.txt

or after rebooting:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


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

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

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

Title:
  Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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


[Kernel-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

2023-05-18 Thread Valentijn Sessink
Here are two full logs. One where things go wrong. I'm walking upstairs
at 06:15 and at 06:16:17, the first logs indicate that the dock is
connected ("usb 1-4: new high-speed USB device number 53 using
xhci_hcd"), the "Cypress Semiconductor؀ USB Billboard" shows up 0.7
seconds later.

Please note that the "pci :05:00.0: BAR 13: no space for [io  size
0x4000]" seem harmless, they also do occur on a successful docking
attempt.

At 06:16:22, Thunderbird starts complaining, "Couldn't map window ",
and 06:16:23 gnome-shell complains that an assertion about monitors
failed. I didn't check the source code.

Apparently, I'm impatient today, so I'm unplugging the dock again at
06:16:54, replugging it 06:17:04 because I saw a login screen i.e. my
session had crashed anyway and probably removing it again after a few
seconds. So all info after 06:17:14 or so should be regarded as "utter
mess, please ignore". I tried a few things afterwards, but basically
switching to tty2 and rebooted the system (at 06:20).

I'll add a successful docking attempt log file in the next comment.


** Attachment added: "crash when docking"
   
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+attachment/5673744/+files/wrong

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr
  0x4b0 for 1 bytes NAKed)

Status in GNOME Shell:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions


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


[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend

2023-05-18 Thread wateenellende
Have a HP Pavilion 14-ec0660nd with Radeon 5700U and had the same
screen-won't-wake-up syndrome.

Installing AMD drivers downloaded from AMD seems to have fixed it.

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

Title:
  Ubuntu 22.04 not waking up after second suspend

Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  After the first suspend it wakes up just fine - it's the second
  suspend after which the screen stays blank and keyboard doesn't react
  (although the power LED starts glowing). It happens if I close the
  laptop's lid or do a manual suspend via the system menu. It happens
  only recently (I think after some kernel update, but I'm not sure
  about this) - before it worked fine for month (since I installed
  Ubuntu).

  I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the
  only OS (if that's important).

  What I tried:

  * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896)
  * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896)
  * I looked through the logs in /var/log but couldn't find anything obvious to 
me (but I'm not a Linux guru).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 11:02:36 2023
  InstallationDate: Installed on 2022-06-14 (258 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  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.19/+bug/2008774/+subscriptions


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