date:20231121

WIP: https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/104

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in firmware-sof source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  Triaged

Bug description:
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363

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


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

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

** This bug is no longer a duplicate of bug 2042660
   mantic/linux: 6.5.0-14.14 -proposed tracker

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

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

** Description changed:

  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops
  
  [Fix]
- Need 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus=de90f5165b1c
 to support Oasis and apply patch from 
https://lore.kernel.org/lkml/20230809140048.669797-3-sbind...@opensource.cirrus.com/
 to switch the AMP interface of Dell Oasis laptops from I2C to SPI.
+ Need to backport 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492
 to support dual speaker configuration on Dell Oasis series
  
  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture
  
  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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

** Also affects: linux-oem-6.5 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need to backport 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492
 to support dual speaker configuration on Dell Oasis series

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2033148] Re: New 6.2.0 kernel error

2023-11-21 Thread Launchpad Bug Tracker

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

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

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

Title:
  New 6.2.0 kernel error

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  You may already be aware of this error but if not I have been trying
  to build lineage-20 recently and it kept failing. After trying a
  number of potential solutions from the web the one that worked advised
  the in ubuntu 22.04.3 kernel version 6.x.x somehow is incompatible for
  the build causing a mmap error while building ART.

  I followed their advice and reverted to a previous kernel. I selected
  5.19.0-46 kernel and the build worked fine.

  See the last post in the following web site for the solution I followed.
  
https://stackoverflow.com/questions/60275623/android-dex2oat-builderror-dex2oat-failed-to-compile-a-boot-image

  Regards, James.

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


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

[Kernel-packages] [Bug 2044027] Re: [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after rebooting on ubuntu os only

2023-11-21 Thread Daniel van Vugt

** Summary changed:

- keyboard , mouse and black screen after rebooting on ubuntu os only
+ [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after 
rebooting on ubuntu os only

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

Title:
  [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
  rebooting on ubuntu os only

Status in linux package in Ubuntu:
  New

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2023-11-21 Thread Daniel van Vugt

Yes the solution in comment 10 is indirectly mentioned above in
[Workarounds], but it's not very obvious:

https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

$ dput ubuntu makedumpfile_1.6.7-1ubuntu2.5_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/makedumpfile_1.6.7-1ubuntu2.5_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/makedumpfile_1.6.7-1ubuntu2.5.dsc: Valid signature from
9B8EC849D5EF70ED
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading makedumpfile_1.6.7-1ubuntu2.5.dsc: done.
Uploading makedumpfile_1.6.7-1ubuntu2.5.debian.tar.xz: done.
Uploading makedumpfile_1.6.7-1ubuntu2.5_source.buildinfo: done.
Uploading makedumpfile_1.6.7-1ubuntu2.5_source.changes: done.
Successfully uploaded packages.

** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => Fix Released

** Changed in: makedumpfile (Ubuntu Focal)
Status: Confirmed => In Progress

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
In Progress

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:

__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

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

[Kernel-packages] [Bug 2019000] Re: Use new annotations model

This bug is awaiting verification that the linux-aws/5.4.0-1115.125
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-linux-aws' to 'verification-done-focal-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-focal-linux-aws' to 'verification-failed-focal-linux-aws'.


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-aws-v2 
verification-needed-focal-linux-aws

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

Title:
  Use new annotations model

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Confirmed
Status in linux-gcp source package in Kinetic:
  Invalid
Status in linux-kvm source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Starting with lunar we have introduced a new way to manage kernel
  configs, unifying the duplicated information defined in the
  annotations file + config chunks into an annotations-only model.

  [Test case]

  A kernel build can be considered a valid test case, in particular the
  specific command that is used to update the .config's for all the
  supported architectures and flavours:

   $ fakeroot debian/rules updateconfigs

  [Fix]

  Import the required changes in debian/ from lunar (with the required
  adjustments) to support the annotations-only model also in all the
  previous releases.

  [Regression potential]

  We may experience regressions during the updateconfigs step,
  especially with derivatives. Moreover, derivatives that want to
  transition to the new annotations model require to adjust the header
  in the annotations file as following (make sure to define the
  corresponding architectures and flavours):

  # FORMAT: 4
  # ARCH: amd64 arm64 armhf ppc64el s390x
  # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k 
arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae 
ppc64el-generic s390x-generic

  After adjusting the header a special command is provided to transition
  to the new annotations-only model:

   $ fakeroot debian/rules migrateconfigs

  This command should automatically import the old configs into the new
  annotations file.

  A kernel with this change applied can still support the old
  annotations+configs model, the transition to the new model is not
  mandatory.

  Basically without using `fakeroot debian/rules migrateconfigs` the
  updateconfigs step will continue to use the old model and the old
  scripts (that is the safest approach to avoid potential unexpected
  .config changes).

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


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

[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency

This bug is awaiting verification that the linux-azure/5.15.0-1053.61
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-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.


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-jammy-linux-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  Azure: Improve SQL DB latency

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  TCP pingpong threshold is 1 by default. But some applications, like SQL DB
  may prefer a higher pingpong threshold to activate delayed acks in quick
  ack mode for better performance.

  There is no single value that fits all applications.
  Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for
  optimal performance based on the application needs.

  [Test Case]

  Microsoft tested

  [Regression Potential]

  Should be zero since default behavior is unchanged.

  [Other Info]

  SF: #00357415

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


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

[Kernel-packages] [Bug 2044199] Re: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-11-21 Thread Paulo Abadie Guedes

Right after submitting this bug (and before doing anything else) I ran a
manual "apt update/apt upgrade", just in case.

To my surprise, the package installed cleanly (see attachment)
Really can't explain why it failed before. I didn't even rebooted the machine, 
so... no clue about why it worked now, after having failed previously.

Any ideas?
Anyway, hope this might be somehow useful for the developers/maintainers of 
this package.

Should it be closed right away?
Thanks!
Paulo

** Attachment added: "2023_11_21_Log_successfull_apt_upgrade.txt"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2044199/+attachment/5722008/+files/2023_11_21_Log_successfull_apt_upgrade.txt

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

Title:
  package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  Maybe the issue is related to power saving. The system tried to
  download and update a package (new kernel image), AFAIK, without my
  intervention. Then one of the DKMS steps failed, and the install
  procedure failed. the dmesg command shows nothing particularly
  interesting.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pag2341 F wireplumber
   /dev/snd/controlC0:  pag2341 F wireplumber
   /dev/snd/seq:pag2330 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Nov 21 19:12:16 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-09-13 (434 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vg1_ssd-lv1_root 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.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: dkms
  Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: Upgraded to lunar on 2023-06-05 (169 days ago)
  dmi.bios.date: 12/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11RFH.051.201229.HC
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550XCJ-XS2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLA664A0C-C01-G003-S0001+10.0.19041
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11RFH.051.201229.HC:bd12/29/2020:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP11RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-XS2BR:rvrSGLA664A0C-C01-G003-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH:
  dmi.product.family: Notebook 5 Series
  dmi.product.name: 550XCJ/550XCR
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH
  dmi.product.version: P11RFH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Kernel-packages] [Bug 2044199] [NEW] package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-11-21 Thread Paulo Abadie Guedes

Public bug reported:

Maybe the issue is related to power saving. The system tried to download
and update a package (new kernel image), AFAIK, without my intervention.
Then one of the DKMS steps failed, and the install procedure failed. the
dmesg command shows nothing particularly interesting.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38
ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pag2341 F wireplumber
 /dev/snd/controlC0:  pag2341 F wireplumber
 /dev/snd/seq:pag2330 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Nov 21 19:12:16 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2022-09-13 (434 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vg1_ssd-lv1_root 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.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: dkms
Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: Upgraded to lunar on 2023-06-05 (169 days ago)
dmi.bios.date: 12/29/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11RFH.051.201229.HC
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550XCJ-XS2BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLA664A0C-C01-G003-S0001+10.0.19041
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11RFH.051.201229.HC:bd12/29/2020:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP11RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-XS2BR:rvrSGLA664A0C-C01-G003-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH:
dmi.product.family: Notebook 5 Series
dmi.product.name: 550XCJ/550XCR
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH
dmi.product.version: P11RFH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: dkms (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 dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2044199

Title:
  package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  Maybe the issue is related to power saving. The system tried to
  download and update a package (new kernel image), AFAIK, without my
  intervention. Then one of the DKMS steps failed, and the install
  procedure failed. the dmesg command shows nothing particularly
  interesting.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pag2341 F wireplumber
   /dev/snd/controlC0:  pag2341 F wireplumber
   /dev/snd/seq:pag2330 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Nov 21 19:12:16 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-09-13 (434 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vg1_ssd-lv1_root 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.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: dkms
  Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return

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

2023-11-21 Thread bugproxy

--- Comment From eller...@au1.ibm.com 2023-11-21 19:17 EDT---
IMO you should just follow the Kconfig dependencies.

ie. if you enable COMPAT then you should also enable COMPAT_32BIT_TIME.

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

Title:
  Turning COMPAT_32BIT_TIME off on ppc64el

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This will prevent existing 32-bit powerpcle binaries to operate
  correctly, if they are still using 32bit time. And even exists?

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

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


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

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

2023-11-21 Thread Ubuntu SRU Bot

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

dm-writeboost/2.2.13-1ubuntu3 (amd64, arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.2 (amd64, arm64)
systemd/249.11-0ubuntu3.11 (amd64, arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2044192] [NEW] Patches needed for AmpereOne (arm64)

2023-11-21 Thread John Cabaj

Public bug reported:

[Impact]

* Google requested patches for AmpereOne machine t ype

[Fix]

* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 5.15 
and Focal 5.4 for now
* Cherry-picks from upstream

0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL 
programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL 
programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the 
core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer programming 
over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from erratum 
function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for unhandled 
register accesses")

[Test Case]

* Compile tested
* Boot tested
* To be tested by Google

[Where things could go wrong]

* Low chance of regression. Changes isolated to to timers.

[Other Info]

* SF #00372821

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

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

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

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

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

** Description changed:

  [Impact]
  
  * Google requested patches for AmpereOne machine t ype
  
  [Fix]
  
+ * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 and Focal 5.4 for now
  * Cherry-picks from upstream
  
  0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to 
the core code")
  8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer 
programming over to CVAL")
  72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
  ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from 
erratum function names")
  a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
  1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
  d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
  4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for 
unhandled register accesses")
  
  [Test Case]
  
  * Compile tested
  * Boot tested
  * To be tested by Google
  
  [Where things could go wrong]
  
  * Low chance of regression. Changes isolated to to timers.
  
  [Other Info]
  
  * SF #00372821

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

Title:
  Patches needed for AmpereOne (arm64)

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-gcp source package in Jammy:
  New

Bug description:
  [Impact]

  * Google requested patches for AmpereOne machine t ype

  [Fix]

  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 and Focal 5.4 for now
  * Cherry-picks from upstream

  0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55

[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi

2023-11-21 Thread sydbat

I think I solved it. Hopefully.

After much scouring of the Internets, I stumbled upon what is likely the
issue. It seems that quite some time ago (pre 6.0 kernel days) I had
installed a github driver for my dongle. I thought I had uninstalled
that driver and had been using the kernel driver, but it seems not. In
the modprobed folder is the .conf file for this driver. The kernel
driver was blacklisted, so I unblacklisted it, rebooted and I am now
typing this update from the current kernel 6.2.0-37. YAY!!

I guess this can now be closed.

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

Title:
  6.2.0-36 kills usb wifi

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30,
  2023). After reboot, USB WiFi dongle was no longer recognised.
  Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure
  what broke, or if it is a regression of some sort. Also, how to upload
  the bug as stated below, when booting into that kernel does not allow
  WiFi connection.

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


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

[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi

2023-11-21 Thread sydbat

Here is the log

** Attachment added: "log nov 21 2023.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042000/+attachment/5721864/+files/log%20nov%2021%202023.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/2042000

Title:
  6.2.0-36 kills usb wifi

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30,
  2023). After reboot, USB WiFi dongle was no longer recognised.
  Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure
  what broke, or if it is a regression of some sort. Also, how to upload
  the bug as stated below, when booting into that kernel does not allow
  WiFi connection.

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2023-11-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "lp1970672-focal.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

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

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

[Kernel-packages] [Bug 2042000] Re: 6.2.0-36 kills usb wifi

2023-11-21 Thread sydbat

Today (Nov 21 2023) the kernel updated to version 6.2.0-37 and the same
issue remains. Perhaps I need to try one of the mainline kernels Ubuntu
maintains and see if 6.3 or 6.4 has the same problem. I know that I was
able to use the 6.2 kernel this way several months ago and I had no
issue with my WiFi dongle. In fact, I had switched to the 6.2 kernel so
I could use this WiFi dongle. Then 6.2 became available through the
regular update method, and it worked fine until these last two kernel
updates. I will attach a log shortly.

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

Title:
  6.2.0-36 kills usb wifi

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed the kernel update from 6.2.0-35 to 6.2.0-36 today (Oct 30,
  2023). After reboot, USB WiFi dongle was no longer recognised.
  Rebooted into previous kernel (6.2.0-35) and have no issue. Not sure
  what broke, or if it is a regression of some sort. Also, how to upload
  the bug as stated below, when booting into that kernel does not allow
  WiFi connection.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

> Is there another way to test it? Why do we need so many out-of-archive
components?

That PPA contains prebuilt modules to ease the verification process. The
Intel MIPI IPU6 relies on both kernel drivers and a user space hal
framework, and the versions must match because Intel fails to keep
compatibility across releases, so you don't want to deal with these
mess, the PPAs have the right version for verification.

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already,

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

2023-11-21 Thread Ubuntu SRU Bot

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

glibc/2.38-1ubuntu6 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-11-21 Thread Andreas Hasenack

Hi,

this review is about the ipu6-driver portion of this SRU, which I will
paste below and add inline comments to:

> == ipu6-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.

The changes in ipu6-drivers are not adding a new firmware as far as I
can tell, could you please clarify?

Overall, after this update, what will be the status of MIPI cameras for
mantic users on intel meteor lake?

>
> [Fix]
>
> Based on upstream tag 
> https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an 
> additional patch to enable/fix compilation of additional sensor modules.

Since this includes a new upstream code drop, could you summarize the
highlights? Have you inspected them for backwards incompatible changes?

>
> [Test Case]
>
> This is verified on MTL Lattice and VSC platforms, as well as previous 
> generations e.g. TGL and ADL.
>
> To actually verify the camera framework:
> ```
> $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
> $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
> $ sudo apt install linux-oem-22.04d-exp
> $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
> $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
> $ sudo apt install linux-modules-usbio-oem-22.04d-exp
> $ sudo apt install gstreamer1.0-icamera v4l2-relayd
> ```
> And then browse https://webcamtests.com/ for testing.

Like my comment #24 above, is there a way to test this that does not
involve out-of-archive packages? If not, what is the benefit of this
update to mantic users?

>
> [Where problems could occur]
>
> This is a new platform. We've been verifying its functions and features, and
> are still polishing it.


That doesn't sound very reassuring :) Having said that, you think it's ready 
for a stable release update for mantic users? Mantic users will benefit from 
this update?

>
> [Other Info]
>
> While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
> linux/mantic and on, and yet the lastest stable driver was verified after 
> Mantic was released, it's being proposed to Noble instead.



** Changed in: ipu6-drivers (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Incomplete
Status in ivsc-driver source package in Mantic:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

> So can the tests be made using that kernel?

Yes and no. MIPI on MTL is only available on developing platforms, and
developing platforms may take additional fixes to construct a usable
system before you may take it for verification. The 6.5.0-14.14 is
already sufficient for IPU6 alone though.

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to Intel.

  These two fixes are therefore for

[Kernel-packages] [Bug 2044174] [NEW] Mantic update: v6.5.6 upstream stable release

2023-11-21 Thread Kamal Mostafa

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.5.6 upstream stable release
   from git://git.kernel.org/

NFS: Fix error handling for O_DIRECT write scheduling
NFS: Fix O_DIRECT locking issues
NFS: More O_DIRECT accounting fixes for error paths
NFS: Use the correct commit info in nfs_join_page_group()
NFS: More fixes for nfs_direct_write_reschedule_io()
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server
NFSv4.1: fix pnfs MDS=DS session trunking
media: v4l: Use correct dependency for camera sensor drivers
media: via: Use correct dependency for camera sensor drivers
gfs2: Fix another freeze/thaw hang
netfs: Only call folio_start_fscache() one time for each folio
btrfs: improve error message after failure to add delayed dir index item
btrfs: remove BUG() after failure to insert delayed dir index item
ext4: replace the traditional ternary conditional operator with with max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention
netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC
netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails
netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration
netfilter: nf_tables: fix memleak when more than 255 elements expired
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
bpf: Avoid dummy bpf_offload_netdev in __bpf_prog_dev_bound_init
ALSA: docs: Fix a typo of midi2_ump_probe option for snd-usb-audio
ALSA: seq: Avoid delivery of events for disabled UMP groups
ASoC: rt5640: Revert "Fix sleep in atomic context"
ASoC: rt5640: Fix sleep in atomic context
ASoC: rt5640: fix typos
ASoC: rt5640: Do not disable/enable IRQ twice on suspend/resume
ASoC: rt5640: Enable the IRQ on resume after configuring jack-detect
ASoC: rt5640: Fix IRQ not being free-ed for HDA jack detect mode
bpf: Fix a erroneous check after snprintf()
selftests/bpf: fix unpriv_disabled check in test_verifier
ALSA: hda/realtek: Splitting the UX3402 into two separate models
netfilter: conntrack: fix extension size table
netfilter: nf_tables: Fix entries val in rule reset audit log
Compiler Attributes: counted_by: Adjust name and identifier expansion
uapi: stddef.h: Fix header guard location
uapi: stddef.h: Fix __DECLARE_FLEX_ARRAY for C++
memblock tests: Fix compilation errors.
ASoC: SOF: ipc4-topology: fix wrong sizeof argument
net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_keyvalue_test()
net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_actionvalue_test()
net: microchip: sparx5: Fix possible memory leak in vcap_api_encode_rule_test()
net: microchip: sparx5: Fix possible memory leaks in test_vcap_xn_rule_creator()
net: microchip: sparx5: Fix possible memory leaks in vcap_api_kunit
selftests: tls: swap the TX and RX sockets in some tests
net/core: Fix ETH_P_1588 flow dissector
ALSA: seq: ump: Fix -Wformat-truncation warning
ASoC: hdaudio.c: Add missing check for devm_kstrdup
ASoC: imx-audmix: Fix return error with devm_clk_get()
octeon_ep: fix tx dma unmap len values in SG
iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set
ASoC: SOF: core: Only call sof_ops_free() on remove if the probe was successful
iavf: add iavf_schedule_aq_request() helper
iavf: schedule a request immediately after add/delete vlan
i40e: Fix VF VLAN offloading when port VLAN is configured
netfilter, bpf: Adjust timeouts of non-confirmed CTs in bpf_ct_insert_entry()
ionic: fix 16bit math issue when PAGE_SIZE >= 64KB
igc: Fix infinite initialization loop with early XDP redirect
scsi: iscsi_tcp: restrict to TCP sockets
powerpc/perf/hv-24x7: Update domain value check
powerpc/dexcr: Move HASHCHK trap handler
dccp: fix dccp_v4_err()/dccp_v6_err() again
x86/mm, kexec, ima: Use memblock_free_late() from ima_free_kexec_buffer()
net: hsr: Properly parse HSRv1 supervisor frames.
platform/x86: intel_scu_ipc: Check status after timeout in busy_loop()
platform/x86: intel_scu_ipc: Check status upon timeout in 
ipc_wait_for_interrupt()
platform/x86: intel_scu_ipc: Don't override scu in 
intel_scu_ipc_dev_simple_command()
platform/x86: intel_scu_ipc: Fail IPC send if still busy
x86/asm: Fix build of UML with KASAN
x86/srso: Fix srso_show_state() side effect

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-11-21 Thread Andreas Hasenack

Hi,

this review is about the ivsc-driver portion of this SRU, which I will
paste below and add inline comments to:

> == ivsc-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.

The patches added to the ivsc-driver package do not seem to be about a
missing firmware, like the impact section above claims:

+- ljca: try to find acpi device from hub device
+- mei-vsc: port mei api change in v6.2
+- mfd: ljca: Fix try_match_acpi_hid return value checking
+- misc: spi-vsc: Fix cvfd_ids array with terminator

Please clarify.


>
> [Fix]
>
> 4 commits from the latest trunk branch on upstream repository 
> https://github.com/intel/ivsc-driver.
>
> [Test Case]
>
> With all other changes in position, Intel VSC driver modules are to be loaded 
> as a soft dependency of some selected camera sensor modules. LJCA modules 
> should be loaded automatically on MTL platforms as well.
>
> To actually verify the camera framework:
> ```
> $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
> $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
> $ sudo apt install linux-oem-22.04d-exp
> $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
> $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
> $ sudo apt install linux-modules-usbio-oem-22.04d-exp
> $ sudo apt install gstreamer1.0-icamera v4l2-relayd
> ```

This is problematic: why do we have to add ppas, and install other
kernel modules? Can you come up with a test case that does NOT need
packages from an out-of-archive source? And specifically, using the
mantic kernel (6.5). Is there another way to test it? Why do we need so
many out-of-archive components?

If pure mantic with the updated ivsc-driver and ipu6-drivers packages
from this bug is not enough to support the MIPI camera, then what is the
benefit this SRU is bringing to mantic users?


> And then browse https://webcamtests.com/ for testing.
>
> [Where problems could occur]
>
> While it changes how LJCA modules match from ACPI ID, it's also tested and 
> verified on previous generations using IVSC, e.g. TGL, ADL.
>
> [Other Info]
>
> While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
> linux/mantic and on, and yet the lastest stable driver was verified after 
> Mantic was released, it's being proposed to Noble instead.

Not sure what you mean with the above. I see the same fixes proposed for
mantic landed in noble, so that's good. Maybe the comment above was
written before the noble packages were updated?


** Changed in: ivsc-driver (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

2023-11-21 Thread Andreas Hasenack

Also, the "linux" task of this bug, for mantic, is "fix committed". It's
this one I believe:

https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14

So can the tests be made using that kernel? It is claiming to have added
support for MIPI cameras, to some extent:

  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on 
Meteor
  Lake
- SAUCE: platform/x86: int3472: Add handshake GPIO function

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Incomplete
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

** Also affects: firmware-sof (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in firmware-sof source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  Triaged

Bug description:
  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363

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


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

[Kernel-packages] [Bug 2044165] [NEW] package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal script subprocess r

2023-11-21 Thread MrSurly

Public bug reported:

While updating my system, had a window pop up stating it was a bug, and
sent me to this page.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Nov 21 09:05:42 2023
ErrorMessage: installed linux-image-6.2.0-36-generic package pre-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-08-25 (1182 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: linux-signed-hwe-6.2
Title: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-12-15 (341 days ago)

** Affects: linux-signed-hwe-6.2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-36-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  While updating my system, had a window pop up stating it was a bug,
  and sent me to this page.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 21 09:05:42 2023
  ErrorMessage: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-08-25 (1182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-12-15 (341 days ago)

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


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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2023-11-21 Thread Andre Ruiz

Hi Christian

In my tests, I also saw the same issues with active-backup too.

Do you know a way to reproduce this issue? I'm having a hard time to
find a consistent reproducer, currently I need to deploy a complete
openstack, run a ser of load tests on it and eventually the problem
shows up, but it takes many hours and not on all hosts.

It would be much easier to have just one machine and trigger the issue
in some other way.

Also, this is fixed upstream, some changes between 1.8.x and 1.9.x of
upstream source drivers fixed the problem (they are at 1.12.x now, so it
has been fixed for quite a while now). The problem is that whatever the
fix is, is has not been imported to kernels 5.15 (jammy GA), 6.2 (jammy
HWE), 6.5 (cosmic GA). I could not reliably test upstream mainline 6.6
because there is no ubuntu currently shipping this package and the pure
upstream kernel breaks a lot of stuff in ubuntu.

I mention this because of your post in the intel mailing list. They will
probably not be able to help much.

Let me know if you find a consistent reproducer.

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu 
Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  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
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2023-11-21 Thread Heather Lemon

focal debdiff of backport patch

** Patch added: "lp1970672-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+attachment/5721783/+files/lp1970672-focal.debdiff

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

** Changed in: makedumpfile (Ubuntu Focal)
 Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)

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

** Changed in: makedumpfile (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

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

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)

This bug is awaiting verification that the linux-azure/6.5.0-1010.10
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.


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-mantic-linux-azure-v2 
verification-needed-mantic-linux-azure

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

Title:
  mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0
  Packet)

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The Microsoft MANA network driver does not accurately report some
  statistics and does not correctly handle some error conditions.

  [Fix]

  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  GSO packets may not be correctly reported. Some error conditions may
  cause incorrect statistics to be recorded, or flood the kernel log
  with error messages.

  [Other Info]

  SF: 00370665

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


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

[Kernel-packages] [Bug 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)

This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.


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-lunar-linux-azure-v2 
verification-needed-lunar-linux-azure

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

Title:
  mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0
  Packet)

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The Microsoft MANA network driver does not accurately report some
  statistics and does not correctly handle some error conditions.

  [Fix]

  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  GSO packets may not be correctly reported. Some error conditions may
  cause incorrect statistics to be recorded, or flood the kernel log
  with error messages.

  [Other Info]

  SF: 00370665

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


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

[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency

This bug is awaiting verification that the linux-azure/6.5.0-1010.10
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If the problem still exists, change the tag
'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-
linux-azure'.


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-mantic-linux-azure-v2 
verification-needed-mantic-linux-azure

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

Title:
  Azure: Improve SQL DB latency

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  TCP pingpong threshold is 1 by default. But some applications, like SQL DB
  may prefer a higher pingpong threshold to activate delayed acks in quick
  ack mode for better performance.

  There is no single value that fits all applications.
  Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for
  optimal performance based on the application needs.

  [Test Case]

  Microsoft tested

  [Regression Potential]

  Should be zero since default behavior is unchanged.

  [Other Info]

  SF: #00357415

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


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

[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency

This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.


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-lunar-linux-azure-v2 
verification-needed-lunar-linux-azure

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

Title:
  Azure: Improve SQL DB latency

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed
Status in linux-azure source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  TCP pingpong threshold is 1 by default. But some applications, like SQL DB
  may prefer a higher pingpong threshold to activate delayed acks in quick
  ack mode for better performance.

  There is no single value that fits all applications.
  Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for
  optimal performance based on the application needs.

  [Test Case]

  Microsoft tested

  [Regression Potential]

  Should be zero since default behavior is unchanged.

  [Other Info]

  SF: #00357415

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


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

[Kernel-packages] [Bug 2042096] Re: Azure: Update TDX with HCL support

This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.


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-lunar-linux-azure-v2 
verification-needed-lunar-linux-azure

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

Title:
  Azure: Update TDX with HCL support

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV
  VM support with HCL.

  The refreshed patches will fix 2 bugs for future Hyper-V versions:
  1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a 
host bug. The guest bug is fixed in the mainline version of the TDX patches.
  2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing 
hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the 
Hyper-V while it should pass a private input page; as a result, the hypercall 
always fails and Linux now falls back to the legacy native method of flusing 
TLB. This slows down the flush-TLB operation . The mainline version doesn't 
have the bug.

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  Azure instances with TDX on HCL hypervisors may not work correctly.

  [Other Info]

  SF: #00364214

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


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

[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models

Proposed firmware commit already in linux-firmware/mantic and noble.
Verifying functionality in Jammy.

** Description changed:

  > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
  firmware.
  
- We probably need following firmware first. To be included in
- https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/linux-
- firmware-staging/ version 20220329.git681281e4-0ubuntu3.23+exp.92.
+ We probably need following firmware first.
  
  $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
  commit c8424cf03defa4a83b8305d1af7b1321ab62
  Author: Stefan Binding 
  Date: Thu Jul 13 17:16:45 2023 +0100
  
- cirrus: Add CS35L41 firmware for Dell Oasis Models
+ cirrus: Add CS35L41 firmware for Dell Oasis Models
  
- Signed-off-by: Stefan Binding 
+ Signed-off-by: Stefan Binding 
  
-  WHENCE | 42 ++
-  cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
-  cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
-  cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
-  cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
-  5 files changed, 42 insertions(+)
+  WHENCE | 42 ++
+  cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
+  cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
+  cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
+  cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
+  5 files changed, 42 insertions(+)

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

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

Title:
  Missing CS35L41 firmware for Dell Oasis Models

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
  firmware.

  We probably need following firmware first.

  $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
  commit c8424cf03defa4a83b8305d1af7b1321ab62
  Author: Stefan Binding 
  Date: Thu Jul 13 17:16:45 2023 +0100

  cirrus: Add CS35L41 firmware for Dell Oasis Models

  Signed-off-by: Stefan Binding 

   WHENCE | 42 ++
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
   5 files changed, 42 insertions(+)

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


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

[Kernel-packages] [Bug 2044158] [NEW] Missing CS35L41 firmware for Dell Oasis Models

Public bug reported:

> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.

We probably need following firmware first.

$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding 
Date: Thu Jul 13 17:16:45 2023 +0100

cirrus: Add CS35L41 firmware for Dell Oasis Models

Signed-off-by: Stefan Binding 

 WHENCE | 42 ++
 cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
 cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
 cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
 cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
 5 files changed, 42 insertions(+)

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

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-firmware (Ubuntu Jammy)
 Importance: Undecided
 Status: Incomplete

** Affects: linux-firmware (Ubuntu Mantic)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-firmware (Ubuntu Noble)
 Importance: Undecided
 Status: Fix Released


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

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

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

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

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: New => Fix Released

** Changed in: linux-firmware (Ubuntu Noble)
   Status: New => Fix Released

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

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

Title:
  Missing CS35L41 firmware for Dell Oasis Models

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
  firmware.

  We probably need following firmware first.

  $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
  commit c8424cf03defa4a83b8305d1af7b1321ab62
  Author: Stefan Binding 
  Date: Thu Jul 13 17:16:45 2023 +0100

  cirrus: Add CS35L41 firmware for Dell Oasis Models

  Signed-off-by: Stefan Binding 

   WHENCE | 42 ++
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
   5 files changed, 42 insertions(+)

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


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

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2023-11-21 Thread Henrik Harmsen

Daniel, I tried setting that threshold to zero but it made the desktop apps 
unstable after coming back from resume (Nvidia 3080Ti). Maybe it doesn't work 
on desktop GPUs. So I went back to the solution I wrote about in comment 10. 
Maybe that solution should be used to solve this problem? It looks like it is 
already used in e.g. Tumbleweed.
Thanks.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Kernel-packages] [Bug 1878279]

2023-11-21 Thread bjorn

radupantiru@: Your MCFG says there's ECAM space at [mem
0xf800-0xfbff] for [bus 00-3f].  That space *should* be reserved
via a PNP0C01 or PNP0C02 device in the ACPI namespace, but it isn't, so
this is likely a BIOS defect.

Can you try the patch I attached here?
https://bugzilla.kernel.org/show_bug.cgi?id=218050#c6 .  If you can,
please attach the dmesg log here.

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2044153] [NEW] package linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1 failed to install/upgrade: installed linux-headers-6.2.0-37-generic package post-installation script su

2023-11-21 Thread nelsinchi

Public bug reported:

Setting up linux-headers-6.2.0-37-generic (6.2.0-37.38~22.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-37-generic
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/intel-i915-dkms.bak/1.23.7.17.230608.24/source/dkms.conf 
does not exist.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
dpkg: error processing package linux-headers-6.2.0-37-generic (--configure):
 installed linux-headers-6.2.0-37-generic package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of 
linux-headers-generic-hwe-22.04:
 linux-headers-generic-hwe-22.04 depends on linux-headers-6.2.0-37-generic; 
however:
  Package linux-headers-6.2.0-37-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-generic-hwe-22.04 (6.2.0.37.38~22.04.15) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.

  dpkg: dependency problems prevent configuration of 
linux-generic-hwe-22.04:
 linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.2.0.37.38~22.04.15); however:
  Package linux-headers-generic-hwe-22.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-22.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.17-2) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Processing triggers for gnome-menus (3.36.0-1ubuntu3) 
...
Processing triggers for libc-bin (2.35-0ubuntu3.4) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for linux-image-6.2.0-37-generic (6.2.0-37.38~22.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-37-generic
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/intel-i915-dkms.bak/1.23.7.17.230608.24/source/dkms.conf 
does not exist.
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
dpkg: error processing package linux-image-6.2.0-37-generic (--configure):
 installed linux-image-6.2.0-37-generic package post-installation script 
subprocess returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were 
encountered while processing:
 linux-headers-6.2.0-37-generic
 linux-headers-generic-hwe-22.04
 linux-generic-hwe-22.04
 linux-image-6.2.0-37-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Nov 21 11:04:17 2023
ErrorMessage: installed linux-headers-6.2.0-37-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-10-28 (23 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: linux-hwe-6.2
Title: package linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1 failed to 
install/upgrade: installed linux-headers-6.2.0-37-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1 failed to
  install/upgrade: installed linux-headers-6.2.0-37-generic package
  post-installation script subprocess returned error exit status 1

Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Setting up linux-headers-6.2.0-37-generic (6.2.0-37.38~22.04.1) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-37-generic

[Kernel-packages] [Bug 2044150] Re: Missing CS35L41 firmware for HP G11 mWS models

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: linux-firmware (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Upstream linux-firmware commit:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0

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


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

[Kernel-packages] [Bug 2043264] Re: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)

2023-11-21 Thread Mario Limonciello

Can you please try to reproduce using a mainline upstream build?

https://kernel.ubuntu.com/mainline/v6.7-rc2/

If you can reproduce please share a new kernel log from a boot it
occurs.

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

Title:
  [amdgpu] External monitor keeps blinking and not connected, with
  Kubuntu Linux (KDE)

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  --- en
  Always, almost every time I turn on my notebook, my LG external monitor keeps 
blinking and it takes a while to actually connect to the notebook and the 
external monitor screen to turn on. For the external monitor to work I change 
the video settings using Ctrl + P and turn the monitor off/on several times. In 
Kubuntu it is recognized but when it blinks the system thinks the monitor is 
off.
  I'm using Kubuntu 23.04, I've used other distributions on the same hardware 
and this problem hasn't happened. I believe it's something with KDE.

  
  --- pt-br
  Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica 
piscando e demora para realmente conectar ao notebook e a tela do monitor 
externo ligar. Para o monitor externo funcionar eu mudo as configurações de 
vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é 
reconhecido mas quando fica piscando o sistema acha que o monitor está 
desligado.
  Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware 
e esse problema não aconteceu. Eu acredito que seja algo com o KDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Nov 11 07:52:24 2023
  DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:3804]
  InstallationDate: Installed on 2022-10-23 (383 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 81V7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago)
  dmi.bios.date: 05/19/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BUCN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15API
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API:
  dmi.product.family: IdeaPad S145-15API
  dmi.product.name: 81V7
  dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API
  dmi.product.version: Lenovo IdeaPad S145-15API
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/linux/+bug/2043264/+subscriptions


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

[Kernel-packages] [Bug 2044150] Re: Missing CS35L41 firmware for HP G11 mWS models

Proposed upstream commit already included in linux-firmware/mantic and
noble.

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Upstream linux-firmware commit:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0

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


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

[Kernel-packages] [Bug 2044150] [NEW] Missing CS35L41 firmware for HP G11 mWS models

Public bug reported:

Upstream linux-firmware commit:
* 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0

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

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: linux-firmware (Ubuntu Mantic)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-firmware (Ubuntu Noble)
 Importance: Undecided
 Status: Fix Released


** Tags: oem-priority originate-from-2039011 stella

** Tags added: oem-priority originate-from-2039011 stella

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

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

** Changed in: linux-firmware (Ubuntu Noble)
   Status: New => Fix Released

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

** Changed in: linux-firmware (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Upstream linux-firmware commit:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0

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


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

[Kernel-packages] [Bug 2044147] [NEW] package nvidia-dkms-470 (not installed) failed to install/upgrade: le sous-processus paquet nvidia-dkms-470 script post-installation installé a renvoyé un état de

2023-11-21 Thread knomad

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-470 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126
Uname: Linux 5.15.0-1050-realtime x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Nov 21 16:27:35 2023
ErrorMessage: le sous-processus paquet nvidia-dkms-470 script post-installation 
installé a renvoyé un état de sortie d'erreur 10
InstallationDate: Installed on 2023-09-12 (70 days ago)
InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230810)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: nvidia-graphics-drivers-470
Title: package nvidia-dkms-470 (not installed) failed to install/upgrade: le 
sous-processus paquet nvidia-dkms-470 script post-installation installé a 
renvoyé un état de sortie d'erreur 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy uec-images

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

Title:
  package nvidia-dkms-470 (not installed) failed to install/upgrade: le
  sous-processus paquet nvidia-dkms-470 script post-installation
  installé a renvoyé un état de sortie d'erreur 10

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

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-470 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126
  Uname: Linux 5.15.0-1050-realtime x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Tue Nov 21 16:27:35 2023
  ErrorMessage: le sous-processus paquet nvidia-dkms-470 script 
post-installation installé a renvoyé un état de sortie d'erreur 10
  InstallationDate: Installed on 2023-09-12 (70 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-470
  Title: package nvidia-dkms-470 (not installed) failed to install/upgrade: le 
sous-processus paquet nvidia-dkms-470 script post-installation installé a 
renvoyé un état de sortie d'erreur 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2044148] [NEW] package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to install/upgrade: le sous-processus paquet nvidia-dkms-535 script post-installation installé a renvoy

2023-11-21 Thread knomad

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126
Uname: Linux 5.15.0-1050-realtime x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Nov 21 16:41:50 2023
ErrorMessage: le sous-processus paquet nvidia-dkms-535 script post-installation 
installé a renvoyé un état de sortie d'erreur 10
InstallationDate: Installed on 2023-09-12 (70 days ago)
InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230810)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: nvidia-graphics-drivers-535
Title: package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to 
install/upgrade: le sous-processus paquet nvidia-dkms-535 script 
post-installation installé a renvoyé un état de sortie d'erreur 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy uec-images

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

Title:
  package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to
  install/upgrade: le sous-processus paquet nvidia-dkms-535 script post-
  installation installé a renvoyé un état de sortie d'erreur 10

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

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126
  Uname: Linux 5.15.0-1050-realtime x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Tue Nov 21 16:41:50 2023
  ErrorMessage: le sous-processus paquet nvidia-dkms-535 script 
post-installation installé a renvoyé un état de sortie d'erreur 10
  InstallationDate: Installed on 2023-09-12 (70 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-535
  Title: package nvidia-dkms-535 535.129.03-0ubuntu0.22.04.1 failed to 
install/upgrade: le sous-processus paquet nvidia-dkms-535 script 
post-installation installé a renvoyé un état de sortie d'erreur 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2023-11-21 Thread Heather Lemon

Related LP
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
Confirmed

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2023-11-21 Thread Christian Rohmann

I ran into this issue on 22.04 LTS (using HWE kernel 6.2) on a 100G dual-port 
E810 NIC.
Also with LACP only, active-backup works without issues.

To bring this more to the attention of the driver devs, I posted to the
intel-wired-lan ML: https://lists.osuosl.org/pipermail/intel-wired-
lan/Week-of-Mon-20231120/038096.html

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  I'm having issues with an Intel E810-XXV card on a Dell server under Ubuntu 
Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  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
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  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: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease:

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2023-11-21 Thread Heather Lemon

Reposting this here as well https://wiki.ubuntu.com/MakedumpfileUpdates

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
Confirmed

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

[Kernel-packages] [Bug 2044139] Re: Kernel image 6.5 (web-)midi problems

2023-11-21 Thread Henning Sprang

I also found this interesting page that discloses that Ubuntu kernel versions 
like 6.5.0 are not solely based on this version number mainline kernels but 
really contain much later versions
https://people.canonical.com/~kernel/info/kernel-version-map.html

but there is no version of this for current kernels. So I dont know if
that is still the case for todays ubuntu kernels. (if so, this is
extremly confusing to always set the minor version to 0 despite it's
really anything later and such a map is needed to understand that)

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

Title:
  Kernel image 6.5 (web-)midi problems

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  After the update to mantis, I have a problem with (at least - i have
  not yet researched further issues) Web-Midi applications running in
  the browser.

  Up to Kernel 6.2 it works just fine (also when downgrading the kernel
  to 6.2 in mantis)to use https://app.electra.one/
  http://components.novationmusic.com/ with a web midi enabled browser
  (must be google chrome installed by deb or chromium installed from
  their nightly builds or via nixos - because the snap version doesn't
  properly allow web midi for some reason that I still need to
  investigate further).

  When using any 6.5 or later kernel as included in mantis, or also when
  building my own from kernel.org, the devices I want to be managed with
  are basically identified, but no further actions are possible.

  This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
  Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

  I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
  The same with the latest 6.6.1 kernel.

  I have not found any error output in dmesg or journalctl that seems to
  be related to the problem so far, and also no other way to try to
  trigger the problem but the above described web midi thing.

  All tests have been done with the ubuntu kernel config - and the
  mainline configs created with make oldconfig.

  So I might additionally test the default mainline configuration, and
  also later mainline versions like 6.6.2 and try to identify other
  erratic behaviours in midi usage (of controllers etc) and add
  information about it... also I did not yet try the normal "generic"
  kernels, just

  Also I found this thing right now:

  https://forum.cockos.com/showthread.php?t=283086

  at the end it says there has been a bug in the kernel in the midi
  code.

  But I'm not sure if that is the same issue. For one I have not seen similar 
error messages in my system, but mainly this post says the bug is fixed in 
6.5.6  https://lwn.net/Articles/946853/ - and I have tested 6.5.11 mainline 
form kernel.org with the problem still persisting. 
  It might be there is some more wrong with the 6.5+ kernels in the midi area.

  
  if there are any further tests or logs needed or helpful, please let me know.

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


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

[Kernel-packages] [Bug 2044139] [NEW] Kernel image 6.5 (web-)midi problems

2023-11-21 Thread Henning Sprang

Public bug reported:

After the update to mantis, I have a problem with (at least - i have not
yet researched further issues) Web-Midi applications running in the
browser.

Up to Kernel 6.2 it works just fine (also when downgrading the kernel to
6.2 in mantis)to use https://app.electra.one/
http://components.novationmusic.com/ with a web midi enabled browser
(must be google chrome installed by deb or chromium installed from their
nightly builds or via nixos - because the snap version doesn't properly
allow web midi for some reason that I still need to investigate
further).

When using any 6.5 or later kernel as included in mantis, or also when
building my own from kernel.org, the devices I want to be managed with
are basically identified, but no further actions are possible.

This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
The same with the latest 6.6.1 kernel.

I have not found any error output in dmesg or journalctl that seems to
be related to the problem so far, and also no other way to try to
trigger the problem but the above described web midi thing.

All tests have been done with the ubuntu kernel config - and the
mainline configs created with make oldconfig.

So I might additionally test the default mainline configuration, and
also later mainline versions like 6.6.2 and try to identify other
erratic behaviours in midi usage (of controllers etc) and add
information about it... also I did not yet try the normal "generic"
kernels, just

Also I found this thing right now:

https://forum.cockos.com/showthread.php?t=283086

at the end it says there has been a bug in the kernel in the midi code.

But I'm not sure if that is the same issue. For one I have not seen similar 
error messages in my system, but mainly this post says the bug is fixed in 
6.5.6  https://lwn.net/Articles/946853/ - and I have tested 6.5.11 mainline 
form kernel.org with the problem still persisting. 
It might be there is some more wrong with the 6.5+ kernels in the midi area.


if there are any further tests or logs needed or helpful, please let me know.

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

** Package changed: apport (Ubuntu) => linux-signed-lowlatency (Ubuntu)

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

Title:
  Kernel image 6.5 (web-)midi problems

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  After the update to mantis, I have a problem with (at least - i have
  not yet researched further issues) Web-Midi applications running in
  the browser.

  Up to Kernel 6.2 it works just fine (also when downgrading the kernel
  to 6.2 in mantis)to use https://app.electra.one/
  http://components.novationmusic.com/ with a web midi enabled browser
  (must be google chrome installed by deb or chromium installed from
  their nightly builds or via nixos - because the snap version doesn't
  properly allow web midi for some reason that I still need to
  investigate further).

  When using any 6.5 or later kernel as included in mantis, or also when
  building my own from kernel.org, the devices I want to be managed with
  are basically identified, but no further actions are possible.

  This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
  Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

  I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
  The same with the latest 6.6.1 kernel.

  I have not found any error output in dmesg or journalctl that seems to
  be related to the problem so far, and also no other way to try to
  trigger the problem but the above described web midi thing.

  All tests have been done with the ubuntu kernel config - and the
  mainline configs created with make oldconfig.

  So I might additionally test the default mainline configuration, and
  also later mainline versions like 6.6.2 and try to identify other
  erratic behaviours in midi usage (of controllers etc) and add
  information about it... also I did not yet try the normal "generic"
  kernels, just

  Also I found this thing right now:

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

Otherwise, this bug report is verified and ready for releases. (and all
kernels will rebuild with new driver anyway, thus version comparison
will soon become 'identical already installed' and thus all rc versions
will be flushed from the archive and the kernels)

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
  12f2b1f65e zdb: include cloned blocks in block statistics

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


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

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

(forked dkms buggy version comparison to
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2044137 )

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
  12f2b1f65e zdb: include cloned blocks in block statistics

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


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

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

dkms is supposed to use dpkg version comparison on ubuntu though =/

** Tags added: verification-done-mantic

** Tags added: verification-done

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Mantic:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
  12f2b1f65e zdb: include cloned blocks in block statistics

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


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

[Kernel-packages] [Bug 2044139] [NEW] Kernel image 6.5 (web-)midi problems

2023-11-21 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

After the update to mantis, I have a problem with (at least - i have not
yet researched further issues) Web-Midi applications running in the
browser.

Up to Kernel 6.2 it works just fine (also when downgrading the kernel to
6.2 in mantis)to use https://app.electra.one/
http://components.novationmusic.com/ with a web midi enabled browser
(must be google chrome installed by deb or chromium installed from their
nightly builds or via nixos - because the snap version doesn't properly
allow web midi for some reason that I still need to investigate
further).

When using any 6.5 or later kernel as included in mantis, or also when
building my own from kernel.org, the devices I want to be managed with
are basically identified, but no further actions are possible.

This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
The same with the latest 6.6.1 kernel.

I have not found any error output in dmesg or journalctl that seems to
be related to the problem so far, and also no other way to try to
trigger the problem but the above described web midi thing.

All tests have been done with the ubuntu kernel config - and the
mainline configs created with make oldconfig.

So I might additionally test the default mainline configuration, and
also later mainline versions like 6.6.2 and try to identify other
erratic behaviours in midi usage (of controllers etc) and add
information about it... also I did not yet try the normal "generic"
kernels, just

Also I found this thing right now:

https://forum.cockos.com/showthread.php?t=283086

at the end it says there has been a bug in the kernel in the midi code.

But I'm not sure if that is the same issue. For one I have not seen similar 
error messages in my system, but mainly this post says the bug is fixed in 
6.5.6  https://lwn.net/Articles/946853/ - and I have tested 6.5.11 mainline 
form kernel.org with the problem still persisting. 
It might be there is some more wrong with the 6.5+ kernels in the midi area.


if there are any further tests or logs needed or helpful, please let me know.

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

-- 
Kernel image 6.5 (web-)midi problems
https://bugs.launchpad.net/bugs/2044139
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-lowlatency in Ubuntu.

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

[Kernel-packages] [Bug 2044137] [NEW] dkms must use dpkg version comparison

Public bug reported:

From: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181

Extra step needed when testing these proposed packages against kernels 
providing the rc:
dkms and dpkg disagree on version sort order.

# dpkg prioritizes tilde
dpkg --compare-versions '2.2.0-0ubuntu1~23.10' gt '2.2.0~rc3-0ubuntu4' ; echo $?

# dkms determines dash comes first
dpkg-reconfigure zfs-dkms
[..]
zfs.ko.zst:
Running module version sanity check.
Error! Module version 2.2.0-0ubuntu1~23.10 for zfs.ko.zst
is not newer than what is already found in kernel 6.5.0-10-generic 
(2.2.0~rc3-0ubuntu4).
You may override by specifying --force.

Seems like dkms does not use dpkg version comparison, like it should on
Ubuntu.

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

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

Title:
  dkms must use dpkg version comparison

Status in dkms package in Ubuntu:
  New

Bug description:
  From: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181

  Extra step needed when testing these proposed packages against kernels 
providing the rc:
  dkms and dpkg disagree on version sort order.

  # dpkg prioritizes tilde
  dpkg --compare-versions '2.2.0-0ubuntu1~23.10' gt '2.2.0~rc3-0ubuntu4' ; echo 
$?

  # dkms determines dash comes first
  dpkg-reconfigure zfs-dkms
  [..]
  zfs.ko.zst:
  Running module version sanity check.
  Error! Module version 2.2.0-0ubuntu1~23.10 for zfs.ko.zst
  is not newer than what is already found in kernel 6.5.0-10-generic 
(2.2.0~rc3-0ubuntu4).
  You may override by specifying --force.

  Seems like dkms does not use dpkg version comparison, like it should
  on Ubuntu.

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


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

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+attachment/5721686/+files/lspci

** Tags added: se sts

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

Title:
  i915 regression introduced with 5.5 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

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


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

[Kernel-packages] [Bug 2044131] [NEW] i915 regression introduced with 5.5 kernel

Public bug reported:

There is a regression preventing a user to upgrade from 5.4 kernel to anything 
that's higher than 5.5. When using such kernel the image orientation is wrong 
(rotated by 90°C). Also the kernel log contains:
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:o>
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
wrz 15 09:19:49 desktop kernel: 

wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

(full stack trace attached)

The video hardware in use is:
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
(...)
Kernel driver in use: i915
Kernel modules: i915

The user wanted to upgrade from bionic to focal with HWE kernel (they
needed it due to some networking hardware they wanted to have supported
by the newer kernel).

The user was testing mainline stable kernels and noticed that the last
working kernel was the 5.4 series, while anything starting from 5.5 and
above is BROKEN (symptoms as described in the first paragraph above).

Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder timing 
minimum limits

To confirm I have reverted this change on top of the HWE kernel for
focal and the user have confirmed that this resolved the issue (test
build available at ppa:dgadomski/kernel-sf368743).

I am not fully sure what the purpose of this patch was, but I assume the
regression was not intended and the hardware should be still supported.

Attaching lshw and lspci output.

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


** Tags: se sts

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

Title:
  i915 regression introduced with 5.5 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+attachment/5721685/+files/lshw

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

Title:
  i915 regression introduced with 5.5 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

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


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

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

** Attachment added: "stacktrace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+attachment/5721684/+files/stacktrace

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

Title:
  i915 regression introduced with 5.5 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

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


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

[Kernel-packages] [Bug 2043118] Re: Regression CIFS mounted DFS

2023-11-21 Thread Heiko

Hi Matthew and Timo,

I've tried both these kernels in our test environment (uname -rv outputs
listed):

1) 5.15.0-88-generic #98+TEST2043118v20231110b1-Ubuntu SMP Fri Nov 10 10:00:22 
UTC 20
Works for us, that is: does not have the issue this bug report is about.

2) 6.6.0-060600rc5-generic #202310081731 SMP PREEMPT_DYNAMIC Thu Nov 16 
04:38:01 UTC 2023
Still has the failing CIFS-mounted DFS filesystem.

FWIW, running the 6.2.0-36-generic kernel from the jammy repositories,
executing "ls -l" to access the (autofs mounted) file system hangs.
Whereas doing the same while running the 6.6.0-060600rc5-generic it just
fails after about 10 secs.

Best regards,
Heiko

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

Title:
  Regression CIFS mounted DFS

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete

Bug description:
  On Ubuntu 22.04.3 LTS (jammy jellyfish) we mount a DFS file service
  using CIFS with kerberos authentication.  After the kernel upgrade
  from 5.15.0-86-generic to 5.15.0-88-generic (exact version:
  5.15.0-88.98) this stopped working. The mount seems to have worked,
  but files and directories are inaccessible. A non-DFS CIFS share
  mounted on the same client machine is not affected.

  In our case the filesystem is mounted using autofs with the following mapping:
  /dfs-share  -fstype=cifs,sec=krb5,vers=3,multiuser,noserverino 
://example.com/share

  Kernel log messages:
  CIFS: Attempting to mount \\example.com\share
  CIFS: VFS: BAD_NETWORK_NAME: \\example.com\share
  CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed
  CIFS: VFS: \\CLx-Ny.EXAMPLE.COM Send error in SessSetup = -126

  We confirmed that kernel version 5.15.0-88 causes this by booting
  different kernel versions repeatedly. When booting 5.15.0-86
  everything worked properly as before.

  Though not familiar with kernel coding, we found changes in the source
  code that seem to confirm that some code dealing with DFS has changed,
  moved, or removed.

  After:
  git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy


  This:
  git diff Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-88.98 -- fs/cifs/cifs_dfs_ref.c

  This suggests the function cifs_dfs_do_mount() has been (re)moved.

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


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

[Kernel-packages] [Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set

2023-11-21 Thread Frank Heimes

** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-z-systems
   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/2044104

Title:
  [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with
  zdev:early=0 set

Status in Ubuntu on IBM z Systems:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  Versions:
  Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x
  Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x

  When I configure a zfcp LUN persistently via chzdev, the initrd is
  being rebuilt even with parameter zdev:early=0

  root@a8315003:~# chzdev -e zfcp-lun 
0.0.1803:0x500507630910d430:0x40194092 zdev:early=0
  zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured
  Note: The initial RAM-disk must be updated for these changes to take effect:
 - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092
  update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic
  I: The initramfs will attempt to resume from /dev/dasdb1
  I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698)
  I: Set the RESUME variable to override this.
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Preparing boot device: dasda (c00a).
  Done.
  root@a8315003:~#

  == Comment: - Thorsten Diehl  - 2023-03-01 
06:55:47 ==
  @BOE-dev
  This behaviour is unexpected.
  https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  Activating a device early during the boot process

  Use the zdev:early device attribute to activate a device early during
  the boot process and to override any existing auto-configuration with
  a persistent device configuration.

  zdev:early=1
  The device is activated during the initial RAM disc phase according to 
the persistent configuration.

  zdev:early=0
  The device is activated as usual during the boot process. This is the 
default. If auto-configuration data is present, the device is activated during 
the initial RAM disc phase according to the auto-configuration. 

  I can't interprete a SCSI LUN as a device with auto configuration
  data. (At least, if the zfcp device hasn't NPIV enabled)

  == Comment: #5 - Peter Oberparleiter  - 
2023-03-01 11:18:28 ==
  (In reply to comment #2)
  > @BOE-dev
  > This behaviour is unexpected.
  > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  > Activating a device early during the boot process
  > 
  > Use the zdev:early device attribute to activate a device early during the
  > boot process and to override any existing auto-configuration with a
  > persistent device configuration.
  > 
  > zdev:early=1
  > The device is activated during the initial RAM disc phase according to
  > the persistent configuration.
  > 
  > zdev:early=0
  > The device is activated as usual during the boot process. This is the
  > default. If auto-configuration data is present, the device is activated
  > during the initial RAM disc phase according to the auto-configuration. 

  The documentation is incorrect for Ubuntu. Canonical specifically
  builds zdev in a way that every change to persistent device
  configuration causes an update to the initial RAM-disk. See also:

  https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35
  
https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8

  > I can't interprete a SCSI LUN as a device with auto configuration data. (At
  > least, if the zfcp device hasn't NPIV enabled)

  This is related to auto-configuration as implemented for DPM.

  == Comment: #6 - Thorsten Diehl  - 2023-03-03 
12:41:44 ==
  So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which 
make the parameter zdev:early=0 ineffective. Correct?
  If you confirm, you may also close this bug.

  Not nice - then we have to find an alternate solution.

  == Comment: #7 - Peter Oberparleiter  - 
2023-03-07 06:48:07 ==
  (In reply to comment #6)
  > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which
  > make the parameter zdev:early=0 ineffective. Correct?
  > If you confirm, you may also close this bug.
  > 
  > Not nice - then we have to find an alternate solution.

  chzdev -p on Ubuntu will by default rebuild the initrd. This is intended
  behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD 
build-time
  switch. You can suppress it by adding option --no-root-update to the command
  line.

  Specifying zdev:early=0 to chzdev has exactly the effect that it is supposed 
to
  have: it tells zdev not to enable that device during initrd processing,
  resulting in the corresponding udev rule not

[Kernel-packages] [Bug 2039970] Re: Kernels 6.x have a regression for Audio via HDMI

2023-11-21 Thread Maksim Beliaev

nailed down that the bug appeared in transition from 6.2 to 6.3

** Summary changed:

- Kernels 6.x have a regression for Audio via HDMI
+ Kernel 6.3 have a regression for Audio via HDMI

** Description changed:

  data collected for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039882
  
  [Dell Inspiron 16 7610]
  
- All kernels of 6.x looks to be missing some port of the bug fix from
- 5.19
+ kernel 6.3 looks to be missing some port of the bug fix from 5.19
  
  before and including kernel 5.15 there was a bug that after locking the
  screen and logging back audio via HDMI was disappearing. Later the bug
  was fixed and definitely not present in 5.19
  
  However, this bug is present in 6.x kernels included in Lunar and Mantic
  as well as in 6.5.7-060507.202310102154
  
  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 13:09:11 2023
  InstallationDate: Installed on 2022-06-19 (488 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_iommu=off nouveau.modeset=0 
nouveau.blacklist=1 fsck.mode=skip nomodset mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-19 (1 days ago)
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.1
  dmi.board.name: 1J0MWF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.1:bd05/10/2023:br1.16:svnDellInc.:pnInspiron167610:pvr:rvnDellInc.:rn1J0MWF:rvrA01:cvnDellInc.:ct10:cvr:sku0A83:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 16 7610
  dmi.product.sku: 0A83
  dmi.sys.vendor: Dell Inc.

** Description changed:

  data collected for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039882
  
  [Dell Inspiron 16 7610]
  
- kernel 6.3 looks to be missing some port of the bug fix from 5.19
+ kernel 6.3 looks to be missing some port of the bug fix from 5.19 or got
+ a regression
  
  before and including kernel 5.15 there was a bug that after locking the
  screen and logging back audio via HDMI was disappearing. Later the bug
  was fixed and definitely not present in 5.19
  
  However, this bug is present in 6.x kernels included in Lunar and Mantic
  as well as in 6.5.7-060507.202310102154
  
  Currently I rolled back to 5.19 to confirm that this issue is fixed in
  this kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 13:09:11 2023
  InstallationDate: Installed on 2022-06-19 (488 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_iommu=off nouveau.modeset=0 
nouveau.blacklist=1 fsck.mode=skip nomodset mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-19 (1 days ago)
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.1
  dmi.board.name: 1J0MWF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.1:bd05/10/2023:br1.16:svnDellInc.:pnInspiron167610:pvr:rvnDellInc.:rn1J0MWF:rvrA01:cvnDellInc.:ct10:cvr:sku0A83:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 16 7610
  dmi.product.sku: 0A83
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

2023-11-21 Thread D R S

Hi. I have an Acer E5-576G and tried to update to 5.15-89 today and I still get 
the same audio popping issue as the 5.15-88 through the 3.5 mm headphone jack. 
Rolled back once again to 5.15-87 and no problems.

I've noticed after looking at the bug reports that the issue seems to
happen to quite a few Acer computers.

Here's my configuration data:

System:
  Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria
base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Acer product: Aspire E5-576G v: V1.49
serial: 
  Mobo: KBL model: Ironman_SK v: V1.49 serial: 
UEFI: Insyde v: 1.49 date: 12/11/2018
Battery:
  ID-1: BAT1 charge: 41.8 Wh (100.0%) condition: 41.8/62.2 Wh (67.2%)
volts: 12.7 min: 11.1 model: PANASONIC AS16B5J status: Full
CPU:
  Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP
arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 1041 high: 1507 min/max: 400/3400 cores: 1: 800 2: 800
3: 800 4: 800 5: 1133 6: 1507 7: 1159 8: 1335 bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915
v: kernel bus-ID: 00:02.0
  Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI
driver: nvidia v: 535.129.03 bus-ID: 01:00.0
  Device-3: Chicony HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6
  Display: x11 server: X.Org v: 1.21.1.4 driver: X:
loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915
resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
v: kernel bus-ID: 03:00.0
  IF: wlp3s0 state: up mac: 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000
bus-ID: 04:00.1
  IF: enp4s0f1 state: down mac: 
  IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: 
  IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: 
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-5:4
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: 
bt-v: 2.1 lmp-v: 4.2
Drives:
  Local Storage: total: 24.79 TiB used: 8.27 TiB (33.4%)
  ID-1: /dev/sda vendor: SK Hynix model: HFS256G39TND-N210A
size: 238.47 GiB
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD Elements 25A3
size: 9.1 TiB
  ID-3: /dev/sdc type: USB vendor: Western Digital model: WD easystore 264D
size: 14.55 TiB
  ID-4: /dev/sdd type: USB vendor: Samsung model: HD103UI size: 931.51 GiB
Partition:
  ID-1: / size: 39.08 GiB used: 18.96 GiB (48.5%) fs: ext4 dev: /dev/sda4
  ID-2: /boot/efi size: 96 MiB used: 31.1 MiB (32.4%) fs: vfat
dev: /dev/sda1
  ID-3: /home size: 117.53 GiB used: 30 GiB (25.5%) fs: ext4 dev: /dev/sda5
Swap:
  ID-1: swap-1 type: partition size: 4 GiB used: 1024 KiB (0.0%)
dev: /dev/sda6
Sensors:
  System Temperatures: cpu: 47.0 C pch: 40.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 326 Uptime: 1h 1m Memory: 7.63 GiB used: 3.7 GiB (48.5%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.4.0 Packages: 2909 Shell: Bash
  v: 5.1.16 inxi: 3.3.13

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:

[Kernel-packages] [Bug 2044125] [NEW] Noble update: v6.6.1 upstream stable release

2023-11-21 Thread Paolo Pisati

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.6.1 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: 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/2044125

Title:
  Noble update: v6.6.1 upstream stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v6.6.1 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2044126] [NEW] Noble update: v6.6.2 upstream stable release

2023-11-21 Thread Paolo Pisati

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.6.2 upstream stable release
   from git://git.kernel.org/


Linux 6.6.2
btrfs: make found_logical_ret parameter mandatory for function 
queue_scrub_stripe()
btrfs: use u64 for buffer sizes in the tree search ioctls
Revert "mmc: core: Capture correct oemid-bits for eMMC cards"
Revert "PCI/ASPM: Disable only ASPM_STATE_L1 when driver, disables L1"
x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs
io_uring/net: ensure socket is marked connected on connect retry
selftests: mptcp: fix wait_rm_addr/sf parameters
selftests: mptcp: run userspace pm tests slower
eventfs: Check for NULL ef in eventfs_set_attr()
tracing/kprobes: Fix the order of argument descriptions
fbdev: fsl-diu-fb: mark wr_reg_wa() static
ALSA: hda/realtek: Add support dual speaker for Dell
fbdev: imsttfb: fix a resource leak in probe
fbdev: imsttfb: fix double free in probe()
arm64/arm: arm_pmuv3: perf: Don't truncate 64-bit registers
spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies
ASoC: dapm: fix clock get name
ASoC: hdmi-codec: register hpd callback on component probe
ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: trivial: fix error messages
ASoC: rt712-sdca: fix speaker route missing issue
drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE
drm/vc4: tests: Fix UAF in the mock helpers
fs: dlm: Simplify buffer size computation in dlm_create_debug_file()
module/decompress: use kvmalloc() consistently
drivers: perf: Do not broadcast to other cpus when starting a counter
net: ti: icss-iep: fix setting counter value
RISC-V: Don't fail in riscv_of_parent_hartid() for disabled HARTs
net/sched: act_ct: Always fill offloading tuple iifidx
netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses
netfilter: xt_recent: fix (increase) ipv6 literal buffer length
i2c: iproc: handle invalid slave state
net: enetc: shorten enetc_setup_xdp_prog() error message to fit 
NETLINK_MAX_FMTMSG_LEN
virtio/vsock: Fix uninit-value in virtio_transport_recv_pkt()
r8169: respect userspace disabling IFF_MULTICAST
vsock/virtio: remove socket from connected/bound list on shutdown
blk-core: use pr_warn_ratelimited() in bio_check_ro()
nbd: fix uaf in nbd_open
tg3: power down device only on SYSTEM_POWER_OFF
ice: Fix VF-VF direction matching in drop rule in switchdev
ice: Fix VF-VF filter rules in switchdev mode
ice: lag: in RCU, use atomic allocation
ice: Fix SRIOV LAG disable on non-compliant aggregate
riscv: boot: Fix creation of loader.bin
nvme: fix error-handling for io_uring nvme-passthrough
net/smc: put sk reference if close work was canceled
net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
octeontx2-pf: Free pending and dropped SQEs
selftests: pmtu.sh: fix result checking
net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs
Fix termination state for idr_for_each_entry_ul()
net: r8169: Disable multicast filter for RTL8168H and RTL8107E
dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses.
dccp: Call security_inet_conn_request() after setting IPv4 addresses.
net: page_pool: add missing free_percpu when page_pool_init fail
octeontx2-pf: Fix holes in error code
octeontx2-pf: Fix error codes
inet: shrink struct flowi_common
bpf: Check map->usercnt after timer->timer is assigned
rxrpc: Fix two connection reaping bugs
tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING
hsr: Prevent use after free in prp_create_tagged_frame()
llc: verify mac len before reading mac header
watchdog: ixp4xx: Make sure restart always works
watchdog: marvell_gti_wdt: Fix error code in probe()
Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
pwm: sti: Reduce number of allocations and drop usage of chip_data
drm/amdgpu: don't put MQDs in VRAM on ARM | ARM64
drm/amdgpu/gfx10,11: use memcpy_to/fromio for MQDs
regmap: prevent noinc writes from clobbering cache
cpupower: fix reference to nonexistent document
media: cec: meson: always include meson sub-directory in Makefile
media: platform: mtk-mdp3: fix uninitialized variable in mdp_path_config()
media: mediatek: vcodec: using encoder device to alloc/free encoder memory
media: imx-jpeg: notify source chagne event when the first picture parsed
media: mediatek: vcodec: Handle invalid encoder vsi
media: verisilicon: Fixes clock list for rk3588 av1 decoder
media: dvb-usb-v2: af9035: fix missing unlock
media: cadence:

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

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

** This bug has been marked a duplicate of bug 2042660
   mantic/linux: 6.5.0-14.14 -proposed tracker

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

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Won't Fix

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus=de90f5165b1c
 to support Oasis and apply patch from 
https://lore.kernel.org/lkml/20230809140048.669797-3-sbind...@opensource.cirrus.com/
 to switch the AMP interface of Dell Oasis laptops from I2C to SPI.

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2044116] Re: snapcraft login fails. Workaround with gnome-keyring-daemon --unlock hangs

2023-11-21 Thread Juerg Haefliger

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

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

Title:
  snapcraft login fails. Workaround with gnome-keyring-daemon --unlock
  hangs

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 Server in Rapsberry Pi:
  snapcraft login is not working

  When applying the workarounds https://snapcraft.io/docs/snapcraft-
  authentication, part "Using a keyring on a headless Linux system, the
  gnome-keyring-daemon --unlock hangs.

  Attached journal and results from snapcraft.

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


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

[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on

2023-11-21 Thread Anthony Wong

** Summary changed:

- Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
+ Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen 
on

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

Title:
  Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle
  screen on

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on.

  [Fix]
  Realtek r8168h/r8111's ASPM is blocked due to users report the regression on 
their platform[0].
  Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep 
deeper.

  [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814

  [where the issue could happen]
  Medium, may have the regression but the risk is limited in some Dell 
platforms.
  we will ask Realtek's effort once the regression is observed.

  [Misc]
  For Unstable, built with mantic configuration
  ~~~
  $ git push m_cbd
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-mantic-c281d2b48f02-DyYx
  remote: * 1/9 workers busy, 0 builds queued
  remote: 2023-11-20 16:19:03  kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK
  remote: 2023-11-20 16:21:38  kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK
  remote: 2023-11-20 16:18:54  kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK
  remote: 2023-11-20 16:22:08  kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK
  remote: 2023-11-20 16:14:16  kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK
  remote: 

  To cbd.kernel:mantic.git
   * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next
  ~~~

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


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

[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

2023-11-21 Thread Frank Heimes

resend updated version:
https://lists.ubuntu.com/archives/kernel-team/2023-November/thread.html#147088

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

Title:
  [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * Today no s390x-specific vfio-pci devices (zPCI) can be passed
 from a KVM host to a KVM guest (incl. secure execution guests
 in the context of confidential computing).

   * s390x PCI passthrough needs various changes in the s390x kernel zPCI
 code (incl. the new s390x-specific Kernel config option
 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0
 and got backported to 22.04/jammy as part of LP: #1853306.

   * Lunar an newer Ubuntu releases have the code already included from
 upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the
 config option is not set, hence zPCI pass-through is still not possible.

  [Fix]

   * To be able to make use of VFIO zPCI pass-through on s390x running newer
 Ubuntu releases (especially needed in the context of secure execution)
 the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs
 to be enabled and set to 'y'.

  [Test Case]

   * Hardware used: z14 or greater LPAR, PCI-attached devices
 (RoCE VFs, ISM devices, NVMe drive)

   * Setup: Both the kernel and QEMU features are needed for the feature
 to function (an upstream QEMU can be used to verify the kernel early),
 and the facility is only available on z14 or newer.
 When any of those pieces is missing,
 the interpretation facility will not be used.
 When both the kernel and QEMU features are included in their respective
 packages, and running in an LPAR on a z14 or newer machine,
 this feature will be enabled automatically.
 Existing supported devices should behave as before with no changes
 required by an end-user (e.g. no changes to libvirt domain definitions)
 -- but will now make use of the interpretation facility.
 Additionally, ISM devices will now be eligible for vfio-pci passthrough
 (where before QEMU would exit on error if attempting to provide an ISM
 device for vfio-pci passthrough, preventing the guest from starting)

   * Testing will include the following scenarios, repeated each for RoCE,
 ISM and NVMe:

 1) Testing of basic device passthrough (create a VM with a vfio-pci
device as part of the libvirt domain definition, passing through
a RoCE VF, an ISM device, or an NVMe drive. Verify that the device
is available in the guest and functioning)
 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device,
virsh detach-device to remove the device from the running guest,
verify the device is removed from the guest, then virsh attach-device
to hotplug the device to the guest again, verify the device functions
in the guest)
 3) Host power off testing: Power off the device from the host, verify
that the device is unplugged from the guest as part of the poweroff
 4) Guest power off testing: Power off the device from within the guest,
verify that the device is unusable in the guest,
power the device back on within the guest and verify that the device
is once again usable.
 5) Guest reboot testing: (create a VM with a vfio-pci device,
verify the device is in working condition, reboot the guest,
verify that the device is still usable after reboot)

  [Regression Potential]

   * The regression potential is moderate, since the code is upstream
 for quite a while and already enabled in jammy.

   * The general way on using passthrough has not changed, with this
 change (config option) it's now just possible to passthrough
 zPCI on top.

   * CCW devices are not affected.

   * And this is s390x-specific anyway, so no other architectures are
  affected.

  [Other]

   * The enabling of the kernel config option is exactly the same for L, M
 and U/N, but I submitted separate patches due to slightly different context
 and offsets.
  __

  === Description by mjros...@us.ibm.com  ===

  LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to
  enable enhanced interpretation of PCI passthrough on s390.  It also
  included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which
  is necessary to activate this kernel feature.

  For lunar and mantic, the kernel code did not require backporting due
  to the base kernel version already

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2044027/+attachment/5721661/+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/2044027

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

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

apport information

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

[Kernel-packages] [Bug 2044027] Re: keyboard , mouse and black screen after rebooting on ubuntu os only

apport information

** Tags added: apport-collected focal

** Description changed:

  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")
  
- note : secondary storage ,optical disks external devices like keyboard
- are working fine on ubuntu systems with all versions and all other os
- including windows os
+ note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  oem 843 F pulseaudio
+  /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
+  /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
+  /dev/snd/controlC0:  oem 843 F pulseaudio
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2023-11-20 (0 days ago)
+ InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
+ MachineType: TOSHIBA SATELLITE C855D-11X
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-30-generic N/A
+  linux-backports-modules-5.13.0-30-generic  N/A
+  linux-firmware 1.187.39
+ Tags:  focal
+ Uname: Linux 5.13.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 12/06/2012
+ dmi.bios.release: 6.30
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: 6.30
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: Pumori
+ dmi.board.vendor: AMD
+ dmi.board.version: Base Board Version
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: OEM Chassis Manufacturer
+ dmi.chassis.version: OEM Chassis Version
+ dmi.ec.firmware.release: 1.60
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
+ dmi.product.family: Type1Family
+ dmi.product.name: SATELLITE C855D-11X
+ dmi.product.sku: PSKCYE-009002N5
+ dmi.product.version: PSKCYE-009002N5
+ dmi.sys.vendor: TOSHIBA

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

Title:
  keyboard , mouse and black screen after rebooting on ubuntu os only

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later

[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel

2023-11-21 Thread Philip Roche

I have reproduced with @amalmostafa's updated script with a separate
disk too. I see no segfault and no EXT4 errors but the regression in
performance is still present but not as great as in my previous tests.

```
### Ubuntu 20.04 with 5.4 kernel and data disk

ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdb
fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, 
ioengine=libaio, iodepth=128
...
fio-3.16
Starting 8 processes
Jobs: 8 (f=8): [W(8)][100.0%][w=1162MiB/s][w=298k IOPS][eta 00m:00s]
fiojob1: (groupid=0, jobs=8): err= 0: pid=2391: Tue Nov 21 10:34:57 2023
  write: IOPS=284k, BW=1108MiB/s (1162MB/s)(320GiB/295713msec); 0 zone resets
slat (nsec): min=751, max=115304k, avg=8630.05, stdev=124263.77
clat (nsec): min=391, max=239001k, avg=3598764.23, stdev=2429948.87
 lat (usec): min=72, max=239002, avg=3607.70, stdev=2428.75
clat percentiles (usec):
 |  1.00th=[  668],  5.00th=[ 1434], 10.00th=[ 1778], 20.00th=[ 2212],
 | 30.00th=[ 2573], 40.00th=[ 2900], 50.00th=[ 3261], 60.00th=[ 3654],
 | 70.00th=[ 4080], 80.00th=[ 4686], 90.00th=[ 5669], 95.00th=[ 6587],
 | 99.00th=[ 9110], 99.50th=[10945], 99.90th=[26608], 99.95th=[43779],
 | 99.99th=[83362]
   bw (  MiB/s): min=  667, max= 1341, per=99.98%, avg=1107.88, stdev=13.07, 
samples=4728
   iops: min=170934, max=343430, avg=283618.08, stdev=3346.84, 
samples=4728
  lat (nsec)   : 500=0.01%, 750=0.01%, 1000=0.01%
  lat (usec)   : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01%
  lat (usec)   : 250=0.04%, 500=0.43%, 750=0.66%, 1000=0.51%
  lat (msec)   : 2=13.23%, 4=53.26%, 10=31.18%, 20=0.53%, 50=0.11%
  lat (msec)   : 100=0.03%, 250=0.01%
  cpu  : usr=3.10%, sys=7.36%, ctx=1105263, majf=0, minf=102
  IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
 submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
 complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
 issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0
 latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
  WRITE: bw=1108MiB/s (1162MB/s), 1108MiB/s-1108MiB/s (1162MB/s-1162MB/s), 
io=320GiB (344GB), run=295713-295713msec

Disk stats (read/write):
  sdb: ios=96/33256749, merge=0/50606838, ticks=19/30836895, in_queue=971080, 
util=100.00%
ubuntu@cloudimg:~$ 
ubuntu@cloudimg:~$ uname --kernel-release
5.4.0-164-generic
ubuntu@cloudimg:~$ cat /etc/cloud/build.info 
build_name: server
serial: 20231011
ubuntu@cloudimg:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

### Ubuntu 20.04 with 5.15 kernel and data disk

ubuntu@cloudimg:~$ uname --kernel-release 
5.15.0-89-generic
ubuntu@cloudimg:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
ubuntu@cloudimg:~$ cat /etc/cloud/build.info 
build_name: server
serial: 20231011

ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdb
fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, 
ioengine=libaio, iodepth=128
...
fio-3.16
Starting 8 processes
Jobs: 8 (f=8): [W(8)][100.0%][w=1071MiB/s][w=274k IOPS][eta 00m:00s]
fiojob1: (groupid=0, jobs=8): err= 0: pid=1008: Tue Nov 21 12:19:56 2023
  write: IOPS=258k, BW=1007MiB/s (1056MB/s)(320GiB/325284msec); 0 zone resets
slat (nsec): min=931, max=36726k, avg=7936.15, stdev=120427.45
clat (nsec): min=1963, max=155870k, avg=3959799.65, stdev=2129472.51
 lat (usec): min=55, max=155872, avg=3968.10, stdev=2128.87
clat percentiles (usec):
 |  1.00th=[  562],  5.00th=[ 1319], 10.00th=[ 1811], 20.00th=[ 2376],
 | 30.00th=[ 2835], 40.00th=[ 3294], 50.00th=[ 3720], 60.00th=[ 4113],
 | 70.00th=[ 4621], 80.00th=[ 5211], 90.00th=[ 6390], 95.00th=[ 7439],
 | 99.00th=[10159], 99.50th=[11863], 99.90th=[19268], 99.95th=[23462],
 | 99.99th=[36439]
   bw (  KiB/s): min=715896, max=1190887, per=100.00%, avg=1031613.99, 
stdev=9298.50, samples=5200
   iops:

[Kernel-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic

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

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

Title:
  btmgmt --index broken in Mantic

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

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


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

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

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

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

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Won't Fix

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus=de90f5165b1c
 to support Oasis and apply patch from 
https://lore.kernel.org/lkml/20230809140048.669797-3-sbind...@opensource.cirrus.com/
 to switch the AMP interface of Dell Oasis laptops from I2C to SPI.

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2044116] [NEW] snapcraft login fails. Workaround with gnome-keyring-daemon --unlock hangs

2023-11-21 Thread Marcel Guerreiro

Public bug reported:

Ubuntu 22.04 Server in Rapsberry Pi:
snapcraft login is not working

When applying the workarounds https://snapcraft.io/docs/snapcraft-
authentication, part "Using a keyring on a headless Linux system, the
gnome-keyring-daemon --unlock hangs.

Attached journal and results from snapcraft.

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


** Tags: server snapcraft ubuntu

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

Title:
  snapcraft login fails. Workaround with gnome-keyring-daemon --unlock
  hangs

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 Server in Rapsberry Pi:
  snapcraft login is not working

  When applying the workarounds https://snapcraft.io/docs/snapcraft-
  authentication, part "Using a keyring on a headless Linux system, the
  gnome-keyring-daemon --unlock hangs.

  Attached journal and results from snapcraft.

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


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

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

** Tags added: oem-priority originate-from-2033243 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/2044096

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  New

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus=de90f5165b1c
 to support Oasis and apply patch from 
https://lore.kernel.org/lkml/20230809140048.669797-3-sbind...@opensource.cirrus.com/
 to switch the AMP interface of Dell Oasis laptops from I2C to SPI.

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2044104] [NEW] [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set

2023-11-21 Thread bugproxy

Public bug reported:

Versions:
Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x
Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x

When I configure a zfcp LUN persistently via chzdev, the initrd is being
rebuilt even with parameter zdev:early=0

root@a8315003:~# chzdev -e zfcp-lun 
0.0.1803:0x500507630910d430:0x40194092 zdev:early=0
zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
   - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092
update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic
I: The initramfs will attempt to resume from /dev/dasdb1
I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698)
I: Set the RESUME variable to override this.
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: dasda (c00a).
Done.
root@a8315003:~#

== Comment: - Thorsten Diehl  - 2023-03-01 06:55:47 
==
@BOE-dev
This behaviour is unexpected.
https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
Activating a device early during the boot process

Use the zdev:early device attribute to activate a device early during
the boot process and to override any existing auto-configuration with a
persistent device configuration.

zdev:early=1
The device is activated during the initial RAM disc phase according to the 
persistent configuration.

zdev:early=0
The device is activated as usual during the boot process. This is the 
default. If auto-configuration data is present, the device is activated during 
the initial RAM disc phase according to the auto-configuration. 

I can't interprete a SCSI LUN as a device with auto configuration data.
(At least, if the zfcp device hasn't NPIV enabled)

== Comment: #5 - Peter Oberparleiter  - 
2023-03-01 11:18:28 ==
(In reply to comment #2)
> @BOE-dev
> This behaviour is unexpected.
> https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
> Activating a device early during the boot process
> 
> Use the zdev:early device attribute to activate a device early during the
> boot process and to override any existing auto-configuration with a
> persistent device configuration.
> 
> zdev:early=1
> The device is activated during the initial RAM disc phase according to
> the persistent configuration.
> 
> zdev:early=0
> The device is activated as usual during the boot process. This is the
> default. If auto-configuration data is present, the device is activated
> during the initial RAM disc phase according to the auto-configuration. 

The documentation is incorrect for Ubuntu. Canonical specifically builds
zdev in a way that every change to persistent device configuration
causes an update to the initial RAM-disk. See also:

https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35
https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8

> I can't interprete a SCSI LUN as a device with auto configuration data. (At
> least, if the zfcp device hasn't NPIV enabled)

This is related to auto-configuration as implemented for DPM.

== Comment: #6 - Thorsten Diehl  - 2023-03-03 
12:41:44 ==
So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which 
make the parameter zdev:early=0 ineffective. Correct?
If you confirm, you may also close this bug.

Not nice - then we have to find an alternate solution.

== Comment: #7 - Peter Oberparleiter  - 
2023-03-07 06:48:07 ==
(In reply to comment #6)
> So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which
> make the parameter zdev:early=0 ineffective. Correct?
> If you confirm, you may also close this bug.
> 
> Not nice - then we have to find an alternate solution.

chzdev -p on Ubuntu will by default rebuild the initrd. This is intended
behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD build-time
switch. You can suppress it by adding option --no-root-update to the command
line.

Specifying zdev:early=0 to chzdev has exactly the effect that it is supposed to
have: it tells zdev not to enable that device during initrd processing,
resulting in the corresponding udev rule not being copied to the initrd [1].

Unfortunately there is another Ubuntu-initrd script [2] that simply copies ALL
udev rules, including those created by zdev, into the initrd. As a result,
zdev's early-attribute handling is rendered useless and all devices are enabled,
even if a user specified zdev:early=0.

Since this bug report indicates that there is a use-case for this function in
Ubuntu, it might be worth asking Canonical if current processing could be
changed to provide a way for users to specify that a device should specifically
NOT be enabled within initrd processing.

Technically this could easily be done:

1) Have the generic udev initramfs script not copy zdev-generated Udev rules,
   OR
   have the zdev initramfs script remove those rules (somewhat of

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops