[Kernel-packages] [Bug 2037335] Re: kernel leaking TCP_MEM
Hello there, I think this may be the same issue as https://bugs.launchpad.net/ubuntu/+source/linux-signed- aws-6.2/+bug/2045560 I believe this might be related to the following kernel bug which impacts Linux 6.0.0+: https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/ A patch has been produced which fixes this issue (but has not yet made it into a Linux release): https://lore.kernel.org/all/20240421175248.1692552-1-eduma...@google.com/ Hope this helps! Jonathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037335 Title: kernel leaking TCP_MEM Status in linux-meta-aws-6.2 package in Ubuntu: New Bug description: We are running our Kafka brokers on Jammy on ARM64. Previous they were on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to 6.2.0-1012-aws and found the same problem. What we expected to happen: TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour period) What happened instead: TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million pages as configured currently). At this point, the broker is no longer able to properly create new connections and we start seeing "kernel: TCP: out of memory -- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker will eventually isolate itself from the rest of the cluster since it can't talk to the other brokers. Attached is a graph of the average TCP memory usage per kernel version for our production environment over the past 24 hours. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-aws 6.2.0.1012.12~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1012-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Sep 25 20:56:02 2023 Ec2AMI: ami-0b9c5aafc5b2a4725 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-east-1b Ec2Imageid: ami-0b9c5aafc5b2a4725 Ec2InstanceType: im4gn.4xlarge Ec2Instancetype: im4gn.4xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)
The bug report can be found here: https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/ The subsequently produced patch (not by me!) to fix this can be found here: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=3584718cf2ec I've also verified that the above patch does fix the problem at least in my case! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)
I've been digging into this and this appears to be a regression introduced by the following patch https://github.com/torvalds/linux/commit/3cd3399dd7a84 which was first released in Linux 6.0.0. The bug is not a memory leak but rather a bug in how memory usage is counted. Excess memory is not actually being consumed, though the bug is still fatal since the counter controls Linux's memory pressure logic. The (apparently) responsible patch is a performance optimisation which attempts to reduce the frequency of writes to the system-wide counter which (I suspect) is subtly misusing some atomic operation on ARM. If you undo this patch in a recent kernel, the bug disappears. I am currently working on a detailed bug report for the relevant Kernel maintainers. NB: It appears that the "5.15" kernel shipped by Rocky (and RHEL) includes a back-port of this bug, hence my seeing the bug in that kernel version on Rocky Linux. A non-RedHat-patched vanilla build of 5.15 does not exhibit the bug in my system either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)
As another "me too" situation, I'm seeing the same phenomenon, though on Rocky 9 rather than Ubuntu and on older kernels (5.14). Reporting details here on the off chance this provides some insight. Hardware: Ampere Altra Max 128 cores (aarch64), ConnectX6-DX NICs (2 x dual 100G port) Kernel versions tested: 5.15 (Rocky 9 native kernel) and 6.8 (elrepo kernel), both configured with 64 KB pages OS: Rocky Linux 9 Software: nginx serving ~90k HTTPS clients at ~350 GBit/s (a synthetic load test) Bare-metal (no virtualisation). In my test environment, ~90k HTTPS connections are opened (and reused via keepalive) and used to stream ~350 GBit/s of traffic to a cluster of load generators. In this scenario, TCP memory gradually creeps up until reaching the memory pressure threshold in /proc/sys/net/ipv4/tcp_mem (243890 pages, or 15.6 GB in this system). At this point memory usage growth actually increases slightly (and increased CPU load and response times are also observed). The system eventually reaches the ultimate limit (365832 pages, or 23.4 GB) at which point most connections fail and all requests receive very slow responses. Closing all connections or restarting nginx does not free up the memory, only a reboot resolves the situation -- as reported above already. Leaked memory appears to persist even if all connections are closed prior to hitting any of the above limits. Unfortunately I don't yet have any ideas on how to fix this but would be glad to hear (and will share) any insights about what might be going on here! ** Attachment added: "TCP memory consumption" https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+attachment/5763728/+files/boom.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 I have the same issue. When i start the computer normally it stalls after the showing the ubuntu logo. So I can only use ubuntu with version 6.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2051045] Re: Freeze
So i reported the bug for you. But my computer is still in the same bad shape. Will the new kernel fix it? Or will I have to format and reinstall ubuntu again? Em 30/01/2024 01:34, Daniel van Vugt escreveu: > Oh I missed that. Having a problem with recovery mode probably means > this isn't as simple as bug 2028165. Instead I'll move this to being > just some new bug in kernel 6.5. > > ** Summary changed: > > - Freeze > + Freeze in kernel 6.5 (but 6.2 works) > > ** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu) > > ** Changed in: linux-hwe-6.5 (Ubuntu) > Status: Incomplete => New > -- J.P. 3D Studio www.jonathanpaul.com.br -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051045 Title: Freeze in kernel 6.5 (but 6.2 works) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Freeze began after a system update ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 21:45:39 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-02-09 (713 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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-hwe-6.5/+bug/2051045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Just updated my pool today and then remembered hearing about this bug.
Guess I should have searched first. Looking forward to the proposed fix
getting released. Thanks for the patch. :)
For now, I'm using the suggestion of setting
`zfs_dmu_offset_next_sync=0` based on this:
https://www.reddit.com/r/zfs/comments/1826lgs/psa_its_not_block_cloning_its_a_data_corruption.
Plopped the kernel param into `/etc/default/grub` and did an `update-
grub` to make it persistent until the patch is out.
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2049768] Re: my computer doesnt start
Please Ignore this report. I figured the kernel 6.5 has a bug thats making my computer crash. Another person is helping me out. Em 01/02/2024 20:58, Seth Arnold escreveu: > ** Changed in: linux (Ubuntu) > Status: Incomplete => New > -- J.P. 3D Studio www.jonathanpaul.com.br -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: New Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740760/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740757/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740759/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740758/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740756/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740753/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740755/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740754/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740752/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740751/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740750/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740749/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740748/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740747/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740745/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740746/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740744/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049768] Re: my computer doesnt start
apport information ** Tags added: apport-collected jammy ** Description changed: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jonathan 1116 F pulseaudio + /dev/snd/controlC1: jonathan 1116 F pulseaudio + /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-09 (709 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr + ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-39-generic N/A + linux-backports-modules-6.2.0-39-generic N/A + linux-firmware20220329.git681281e4-0ubuntu3.24 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: jammy + Uname: Linux 6.2.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/30/2018 + dmi.bios.release: 8.15 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 080015 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: INTEL H55 + dmi.board.vendor: INTEL + dmi.board.version: INTEL + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2049768/+attachment/5740743/+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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: Incomplete Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.
[Kernel-packages] [Bug 1909005] Re: [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend
3 years is a long time not to fix a basic sleep problem... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019152/+attachment/5726878/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019152 Title: [btintel] Bluetooth crashes in Ubuntu 23.04 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth stops working. Mouse (logitech M720) stopped mid scroll. Never had any problems with this mouse under Ubuntu before. Workaround: Reboot fixes the problem. Switching in and out of airplane mode gets bluetooth working again Frequency: Second time this has happened since upgrade from 22.10 (about 2 weeks ago) Limited knowledge fault tracing: >sudo systemctl restart bluetooth doesn't make any difference >rfkill shows no bluetooth device >lspci ... 3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) ... Ubuntu settings - show bluetooth is off, but I didn't disable it and it can't be re-enabled. So I assume the driver has crashed, but I don't know how to find out more about this. Could collect some more info next time it happens if someone tells me what to do. >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04
Having a similar experience in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2 2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3 2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac major 2023-12-06T16:03:58,985191-06:00 iwlwifi :00:14.3: 0xE8F84E98 | umac minor 2023-12-06T16:03:58,985193-06:00 iwlwifi :00:14.3: 0x7C0B3384 | frame pointer 2023-12-06T16:03:58,985195-06:00 iwlwifi :00:14.3: 0xC0886BE0 | stack pointer 2023-12-06T16:03:58,985197-06:00 iwlwifi :00:14.3: 0x00ED019C | last host cmd 2023-12-06T16:03:58,985199-06:00 iwlwifi :00:14.3: 0x | isr status reg
[Kernel-packages] [Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
I also have lots of these after upgrading to 23.10, featuing Bcache and
Virtualbox
** Attachment added: "log.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039368/+attachment/5712911/+files/log.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/2039368
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since I upgraded from lunar to mantic I get a load of those errors (41
on a fresh boot) in dmesg:
```
[4.277343] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
[4.277728] index 4 is out of range for type 'btree_iter_set [4]'
[4.277925] CPU: 7 PID: 247 Comm: kworker/7:1 Not tainted 6.5.0-9-generic
#9-Ubuntu
[4.278132] Hardware name: Default string Default string/Default string,
BIOS WRX80SU8-F6 06/08/2023
[4.278531] Workqueue: events register_cache_worker [bcache]
[4.278754] Call Trace:
[4.278949]
[4.279143] dump_stack_lvl+0x48/0x70
[4.279337] dump_stack+0x10/0x20
[4.279526] __ubsan_handle_out_of_bounds+0xc6/0x110
[4.279721] bch_btree_iter_push+0x4e6/0x4f0 [bcache]
[4.279929] bch_btree_node_read_done+0xcb/0x410 [bcache]
[4.280142] bch_btree_node_read+0xf8/0x1e0 [bcache]
[4.280349] ? __pfx_closure_sync_fn+0x10/0x10 [bcache]
[4.280557] bch_btree_node_get.part.0+0x15c/0x330 [bcache]
[4.280764] ? __bch_btree_ptr_invalid+0x66/0xe0 [bcache]
[4.280975] ? __pfx_up_write+0x10/0x10
[4.281170] bch_btree_node_get+0x16/0x30 [bcache]
[4.281375] run_cache_set+0x596/0x850 [bcache]
[4.281578] ? srso_return_thunk+0x5/0x10
[4.281773] register_cache_set+0x1a2/0x210 [bcache]
[4.281984] register_cache+0x11a/0x1a0 [bcache]
[4.282187] register_cache_worker+0x22/0x80 [bcache]
[4.282387] process_one_work+0x223/0x440
[4.282573] worker_thread+0x4d/0x3f0
[4.282753] ? srso_return_thunk+0x5/0x10
[4.282931] ? _raw_spin_lock_irqsave+0xe/0x20
[4.283113] ? __pfx_worker_thread+0x10/0x10
[4.283286] kthread+0xf2/0x120
[4.283458] ? __pfx_kthread+0x10/0x10
[4.283631] ret_from_fork+0x47/0x70
[4.283800] ? __pfx_kthread+0x10/0x10
[4.283972] ret_from_fork_asm+0x1b/0x30
[4.284143]
```
This system has 4 bcache backing devices and 4 bcache cache devices,
though they are not associated for now and caching is disabled. It was
already like that when I upgraded, so the kernel only uses the backing
code, not the caching one.
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
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 14 23:16:33 2023
HibernationDevice: RESUME=none
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB:
0 amdgpudrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
To manage
[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
Working for me now as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in linux source package in Lunar: Invalid Status in nvidia-graphics-drivers-515 source package in Lunar: Fix Released Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013124] [NEW] package nvidia-kernel-common-525 525.85.12-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compu
Public bug reported: Sorry, I don't have further details. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-common-525 525.89.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 28 06:41:46 2023 DuplicateSignature: package:nvidia-kernel-common-525:525.85.12-0ubuntu1 Unpacking nvidia-kernel-common-525 (525.89.02-0ubuntu0.22.04.1) over (525.85.12-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2HR3dY/06-nvidia-kernel-common-525_525.89.02-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 ErrorMessage: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 InstallationDate: Installed on 2022-09-16 (193 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-525 Title: package nvidia-kernel-common-525 525.85.12-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2013124 Title: package nvidia-kernel-common-525 525.85.12-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Sorry, I don't have further details. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-common-525 525.89.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zavl icp zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 28 06:41:46 2023 DuplicateSignature: package:nvidia-kernel-common-525:525.85.12-0ubuntu1 Unpacking nvidia-kernel-common-525 (525.89.02-0ubuntu0.22.04.1) over (525.85.12-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2HR3dY/06-nvidia-kernel-common-525_525.89.02-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 ErrorMessage: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 InstallationDate: Installed on 2022-09-16 (193 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-525 Title: package nvidia-kernel-common-525 525.85.12-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-powerd', which is also in package nvidia-compute-utils-525 525.85.12-0ubuntu1 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-525/+bug/2013124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012559] [NEW] 6.2 kernel won't boot, may be nvidia related?
Public bug reported: After installing most recent Lunar updates, linux-image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "journalctl log from right before the first reboot attempt with the new kernel" https://bugs.launchpad.net/bugs/2012559/+attachment/5656653/+files/log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: New Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22
[Kernel-packages] [Bug 1966793] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628046/+files/RfKill.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628045/+files/ProcModules.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628049/+files/acpidump.txt ** Description changed: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： - [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu - [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 - [ 60.882514] Call Trace: - [ 60.882517] - [ 60.882521] show_stack+ 0x52/0x58 - [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f - [ 60.882541] dump_stack+ 0x10/0x12 - [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] - [ 60.882582] ？wait_woken+ 0x70/0x70 + [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu + [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 + [ 60.882514] Call Trace: + [ 60.882517] + [ 60.882521] show_stack+ 0x52/0x58 + [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f + [ 60.882541] dump_stack+ 0x10/0x12 + [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] + [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] - [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] - [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] - [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] - [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] - [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] - [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] - [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] - [ 60.882799] drv_start+0x4f/0xe0 [mac80211] + [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] + [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] + [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] + [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] + [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] + [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] + [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] + [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] - [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] - [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] - [ 60.883048] __dev_open+ 0xf0/0x1c0 - [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 - [ 60.883058] dev_change_ flags+0x26/ 0x60 - [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 - [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 - ]？_copy_from_用户+0x2e/ 0x60 - [60.883082] inet_ioctl+ 0x165/0x190 - [60.883088] sock_do_ioctl+0x42/ 0x100 - [60.883093]？do_readlinkat+ 0x10f/0x120 - [60.883099] sock_ioctl+ 0xef/0x310 - [60.883103]？do_syscall_ 64+0x69/ 0xc0 - [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 - [ 60.883116] do_syscall_ 64+0x59/ 0xc0 - [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 - [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 - [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 - ]？__x64_sys_ readlink+ 0x1e/0x30 + [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] + [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] + [ 60.883048] __dev_open+ 0xf0/0x1c0 + [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 + [ 60.883058] dev_change_ flags+0x26/ 0x60 + [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 + [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 + ]？_copy_from_用户+0x2e/ 0x60 + [60.883082] inet_ioctl+ 0x165/0x190 + [60.883088] sock_do_ioctl+0x42/ 0x100 + [60.883093]？do_readlinkat+ 0x10f/0x120 + [60.883099] sock_ioctl+ 0xef/0x310 + [60.883103]？do_syscall_ 64+0x69/ 0xc0 + [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 + [ 60.883116] do_syscall_ 64+0x59/ 0xc0 + [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 + [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 + [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 + ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 - [60.883142]？do_syscall_ 64+0x69/ 0xc0 - [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae - [ 60.883152] RIP: 0033:0x7f66c7592aff - [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 - 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 - [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff + [60.883142]？do_syscall_ 64+0x69/ 0xc0 + [ 60.883147] entry_SYSCALL_
[Kernel-packages] [Bug 1966793] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628048/+files/WifiSyslog.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628047/+files/UdevDb.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628040/+files/PaInfo.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628043/+files/ProcEnviron.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628044/+files/ProcInterrupts.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628042/+files/ProcCpuinfoMinimal.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906]
[Kernel-packages] [Bug 1966793] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628037/+files/Lsusb.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628041/+files/ProcCpuinfo.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628035/+files/Lspci.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628036/+files/Lspci-vt.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628039/+files/Lsusb-v.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628038/+files/Lsusb-t.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628034/+files/IwConfig.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628033/+files/CurrentDmesg.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1966793/+attachment/5628032/+files/AlsaInfo.txt -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125] ？do_syscall_ 64+0x69/ 0xc0 [ 60.883129] ？syscall_exit_to_user_mode + 0x27/0x50 [ 60.883133 ]？__x64_sys_ readlink+ 0x1e/0x30 [60.883137]？do_syscall_ 64+0x69/ 0xc0 [60.883142]？do_syscall_ 64+0x69/ 0xc0 [ 60.883147] entry_SYSCALL_ 64_after_ hwframe+ 0x44 /0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 252316 00 [0SP:0] 0.0 :7ffc16 8507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00 :14.3: 未能发送PER_PLATFORM_ANT_GAIN_ CMD (-5) [60.894910] iwlwifi :00:14.3: mac start retry 1 [61.068762] iwlwifi :00:14.3: 检测到微码软件错误。重新启动 0x0。 [61.068863] iwlwifi :00:14.3：启动 IWL 错误日志转储： [61.068866] iwlwifi :00:14.3：传输状态：0x004B，有效：6 [61.068871] iwlwifi :00:14.3：加载的固件版本：66.f1c864e0.0 QuZ-a0- jf-b0-66。ucode [61.068874] iwlwifi :00:14.3:0x0071 | NMI_INTERRUPT_ UMAC_FATAL [61.068878] iwlwifi :00:14.3:0x22F0 | trm_hw_status0 [61.068881] iwlwifi :00:14.3:0x | trm_hw_status1 [61.068883] iwlwifi :00:14.3:0x004C2726 | branchlink2 [61.068886] iwlwifi :00:14.3:0x004B974E | 中断 链接1 [61.068889] iwlwifi :00:14.3:0x004B974E | 中断 链接2 [61.068891] iwlwifi :00:14.3:0x004BD86E | 数据1 [61.068893] iwlwifi :00:14.3:0x1000 | 数据2 [ 61.068896 ] iwlwifi :00:14.3:0x | 数据3 [61.068898]iwlwifi :00:14.3:0x | 信标时间 [61.068901] iwlwifi :00:14.3:0x000215F2 | tsf 低 [61.068903] iwlwifi :00:14.3:0x | tsf 嗨 [61.068906] iwlwifi
[Kernel-packages] [Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Dependencies: firmware-sof-signed 2.0-1ubuntu3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-26 (187 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ProBook 440 G8 Notebook PC Package: linux-firmware 20220329.git681281e4-0ubuntu3.3 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=7e1db316-a53e-4323-852f-d184357ad5f0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy package-from-proposed Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/12/2022 dmi.bios.release: 8.20 dmi.bios.vendor: HP dmi.bios.version: T70 Ver. 01.08.20 dmi.board.name: 87E0 dmi.board.vendor: HP dmi.board.version: KBC Version 33.19.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 51.25 dmi.modalias: dmi:bvnHP:bvrT70Ver.01.08.20:bd03/12/2022:br8.20:efr51.25:svnHP:pnHPProBook440G8NotebookPC:pvr:rvnHP:rn87E0:rvrKBCVersion33.19.00:cvnHP:ct10:cvr:sku28K85UTR: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G8 Notebook PC dmi.product.sku: 28K85UTR dmi.sys.vendor: HP ** Tags added: apport-collected jammy package-from-proposed -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: 此问题存在于 HP ProBook 440 G8 描述：Ubuntu Jammy Jellyfish（开发分支） 版本：22.04 Wifi 适配器信息： 描述：无线接口 产品：Wi-Fi 6 AX201 供应商：Intel Corporation 物理 ID：14.3 总线信息：pci@:00:14.3 逻辑名称：wlp0s20f3 版本：20 序列号：28:d0:ea:21: 6a:a1 宽度：64 位 时钟：33MHz 功能：bus_master cap_list 以太网物理无线 配置：广播=yes driver=iwlwifi driverversion= 5.15.0- 23-generic firmware= 66.f1c864e0。0 QuZ-a0-jf-b0-66.u 延迟=0 链接=无组播=是无线=IEEE 802.11 资源：iomemory:600-5ff irq:16 内存：600324c000-600324 错误信息： [60.882505] CPU：6 PID：630 通讯：wpa_supplicant 未污染 5.15.0-23-generic #23-Ubuntu [60.882512] 硬件名称：HP HP ProBook 440 G8 Notebook PC/8807，BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+ 0x52/0x58 [ 60.882532] dump_stack_ lvl+0x4a/ 0x5f [ 60.882541] dump_stack+ 0x10/0x12 [ 60.882545] iwl_trans_ txq_send_ hcmd_sync+ 0x345 /0x350 [iwlwifi] [ 60.882582] ？wait_woken+ 0x70/0x70 [60.882589] iwl_trans_txq_send_hcmd + 0xaa/ 0x140 [iwlwifi] [ 60.882619] iwl_trans_ send_cmd+ 0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_ send_cmd_ pdu+0x6d/ 0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ ppag_send_ cmd+0x1b5/ 0x270 [iwlmvm] [ 60.882695] iwl_mvm_ up+0x656/ 0xa80 [iwlmvm] [ 60.882716] ? __iwl_err。cold+0x25/ 0x2a [iwlwifi] [ 60.882755] __iwl_mvm_ mac_start+ 0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_ mac_start+ 0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_ do_open + 0x488/0x9c0 [ mac80211] [60.882926]？ieee80211_ check_concurren t_iface+ 0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_ open+0x6c/ 0x90 [mac80211] [ 60.883048] __dev_open+ 0xf0/0x1c0 [ 60.883054] __dev_change_ flags+0x1a3/ 0x220 [ 60.883058] dev_change_ flags+0x26/ 0x60 [ 60.883061] devinet_ ioctl+0x598/ 0x6f0 [60.883068]？netdev_name_node_lookup_rcu + 0x6b / 0x80 [ 60.883075 ]？_copy_from_用户+0x2e/ 0x60 [60.883082] inet_ioctl+ 0x165/0x190 [60.883088] sock_do_ioctl+0x42/ 0x100 [60.883093]？do_readlinkat+ 0x10f/0x120 [60.883099] sock_ioctl+ 0xef/0x310 [60.883103]？do_syscall_ 64+0x69/ 0xc0 [ 60.883110] __x64_sys_ ioctl+0x91/ 0xc0 [ 60.883116] do_syscall_ 64+0x59/ 0xc0 [ 60.883120] ? do_syscall_ 64+0x69/ 0xc0 [ 60.883125]
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen
>We should also clarify "won't boot" is just an illusion. For me it doesn't finish booting. I suspect this is because it hangs attempting to switch to a graphical console to prompt for a decryption passphrase for my encrypted root filesystem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Confirmed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991598] Re: laptop not reliably going to sleep when lid closed on battery power
See: https://github.com/jikamens/remember-the-yubikey The relevant part here is that the unit file just starts up a shell script that checks if my YubiKey is plugged in, and if it isn't it exits. I don't keep my YubiKey plugged in when the laptop is closed and idle — and it certainly wasn't plugged in when I observed it staying up for hours despite being closed and idle before filing this ticket — so I doubt this is relevant. Also, if it WERE relevant, the problem wouldn't be intermittent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991598 Title: laptop not reliably going to sleep when lid closed on battery power Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: I have the shell configured to lock the screen when I close the lid and go to sleep after 20 idle minutes on battery power. Immediately before I opened my laptop and unlocked it to submit this bug, the laptop was unplugged from battery power and sitting with the lid closed for hours and never went to sleep. When I opened the lid I found it locked as it should have been, so that's apparently not the issue. The issue is that it just never went to sleep even though it was idle for hours. This is a regression from Jammy. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 21:24:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1144 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Framework laptop
One difference between my Framework laptop (where the problem is happening) and my ThinkPad is that the Framework laptop has a separate Windows boot partition. Don't know if that's relevant, but thought it worth mentioning just in case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Framework laptop Status in linux package in Ubuntu: New Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] [NEW] New Kinetic kernel (5.19.0-18-generic) won't boot on Framework laptop
Public bug reported: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991704 Title: New Kinetic kernel (5.19.0-18-generic) won't boot on Framework laptop Status in linux package in Ubuntu: New Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1984203] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607676/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607677/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607689/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607688/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607690/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607686/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607683/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607687/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607685/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607684/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607680/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607682/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607681/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607678/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607679/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607674/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607671/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607675/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607672/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607673/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984203] Re: /var/run/reboot-required not created after installing new kernel
apport information ** Tags added: apport-collected ** Description changed: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-01-02 (1316 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: Acer Predator G6-710 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.3 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 05/18/2016 + dmi.bios.release: 5.11 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: R01-A4 + dmi.board.name: Predator G6-710 + dmi.board.vendor: Acer + dmi.chassis.type: 3 + dmi.chassis.vendor: Acer + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: + dmi.product.family: Acer Desktop + dmi.product.name: Predator G6-710 + dmi.sys.vendor: Acer + modified.conffile..etc.apport.crashdb.conf: [modified] + mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1984203/+attachment/5607670/+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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path
Updated 20.04 VM to 5.13.0-41-generic #46~20.04.1-Ubuntu and nfs bug is fixed. Updated 18.04 machine to 5.4.0-110-generic #124~18.04.1-Ubuntu and nfs bug is fixed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path
Great thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path
** Summary changed: - Regression: nfs cannot access/list wildcard file unless its cached + Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Do these changes also effect the linux-hwe branches? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
How do I add 18.04 Bionic to the affects list? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Looks like this patch solves the problem as we have a symlink in the test path. This needs to be applied to Ubuntu's hwe-5.4 and hwe-5.13 kernels. Probably anywhere else the above commits got backported to. [PATCH] NFS: LOOKUP_DIRECTORY is also ok with symlinks https://lore.kernel.org/all/f7a7d0e1-41ab-f648-97a3-9fd92e0e2...@leemhuis.info/T/#m5d587247611e36afcfcd157125e910d4f7075cb7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached
I checked out the focal kernel and reverted the following commits. And the problem went away, reverting just the 1st one wasn't enough to fix the issue. - NFSv4: nfs_atomic_open() can race when looking up a non-regular file - NFSv4: Handle case where the lookup of a directory fails git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git linux-ubuntu-focal cd linux-ubuntu-focal git checkout Ubuntu-hwe-5.13-5.13.0-40.45_20.04.1 -b Ubuntu-hwe-5.13-5.13.0-40.45_20.04.1 vim debian/changelog # modify version in head of file LANG=C fakeroot debian/rules clean LANG=C fakeroot debian/rules binary-headers binary-generic binary-perarch skipmodule=true ** Also affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - nfs cannot access/list wildcard file unless its cached + Regression: nfs cannot access/list wildcard file unless its cached -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached
Looks like a nfs patch for https://bugs.launchpad.net/bugs/cve/2022-24448 was introduced in 5.13.0-40 and linux-image-5.4.0-109. So could be cause of regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24448 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached
Also noticed the issue on a 20.04 server which got updated to kernel 5.13.0-40. Downgrading to 5.13.0-39 fixed the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached
Attaching tcpdump for machine seeing errors $ sudo tcpdump -w /tmp/data.pcap -i bond0 host 10.0.0.23 ** Attachment added: "data.pcap" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+attachment/5586399/+files/data.pcap -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] [NEW] nfs cannot access/list wildcard file unless its cached
Public bug reported: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: nfs cannot access/list wildcard file unless its cached Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The
[Kernel-packages] [Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I haven't seen a posted workaround for this anywhere so here is what I found to work on both v20.04 and v22.04: For those loading iwlwifi-QuZ-a0-jf-b0-XX.ucode, use the 55 version as shown: /lib/iwlwifi-QuZ-a0-jf-b0-55.ucode I just moved all newer firmware that are higher than 55 out of the /lib/firmware directory. In v20.04, after removing newer firmware, it just auto loads and starts working. In v22.04, you must reboot after removing the firmware that is higher than 55. So something changed after v55 that broke the wireless functionality on the 440 G8 with AX201. Here is a before and after hardware snapshot: - *-network DISABLED + *-network description: Wireless interface product: Wi-Fi 6 AX201 vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: 28:d0:ea:15:fc:c0 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless - configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-27-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u latency=0 link=no multicast=yes wireless=IEEE 802.11 + configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-28-generic firmware=55.d9698065.0 QuZ-a0-jf-b0-55.u ip=192.168.247.110 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff irq:16 memory:600324c000-600324 -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Confirmed Bug description: This problem exists on an HP ProBook 440 G8 Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Wifi Adapter information : description: Wireless interface product: Wi-Fi 6 AX201 vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: 28:d0:ea:21:6a:a1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-23-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff irq:16 memory:600324c000-600324 Error Information: [ 60.882505] CPU: 6 PID: 630 Comm: wpa_supplicant Not tainted 5.15.0-23-generic #23-Ubuntu [ 60.882512] Hardware name: HP HP ProBook 440 G8 Notebook PC/8807, BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+0x52/0x58 [ 60.882532] dump_stack_lvl+0x4a/0x5f [ 60.882541] dump_stack+0x10/0x12 [ 60.882545] iwl_trans_txq_send_hcmd_sync+0x345/0x350 [iwlwifi] [ 60.882582] ? wait_woken+0x70/0x70 [ 60.882589] iwl_trans_txq_send_hcmd+0xaa/0x140 [iwlwifi] [ 60.882619] iwl_trans_send_cmd+0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_send_cmd_pdu+0x6d/0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ppag_send_cmd+0x1b5/0x270 [iwlmvm] [ 60.882695] iwl_mvm_up+0x656/0xa80 [iwlmvm] [ 60.882716] ? __iwl_err.cold+0x25/0x2a [iwlwifi] [ 60.882755] __iwl_mvm_mac_start+0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_mac_start+0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_do_open+0x488/0x9c0 [mac80211] [ 60.882926] ? ieee80211_check_concurrent_iface+0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_open+0x6c/0x90 [mac80211] [ 60.883048] __dev_open+0xf0/0x1c0 [ 60.883054] __dev_change_flags+0x1a3/0x220 [ 60.883058] dev_change_flags+0x26/0x60 [ 60.883061] devinet_ioctl+0x598/0x6f0 [ 60.883068] ? netdev_name_node_lookup_rcu+0x6b/0x80 [ 60.883075] ? _copy_from_user+0x2e/0x60 [ 60.883082] inet_ioctl+0x165/0x190 [ 60.883088] sock_do_ioctl+0x42/0x100 [ 60.883093] ? do_readlinkat+0x10f/0x120 [ 60.883099] sock_ioctl+0xef/0x310 [ 60.883103] ? do_syscall_64+0x69/0xc0 [ 60.883110] __x64_sys_ioctl+0x91/0xc0 [ 60.883116] do_syscall_64+0x59/0xc0 [ 60.883120] ? do_syscall_64+0x69/0xc0 [ 60.883125] ? do_syscall_64+0x69/0xc0 [ 60.883129] ? syscall_exit_to_user_mode+0x27/0x50 [ 60.883133] ? __x64_sys_readlink+0x1e/0x30 [ 60.883137] ? do_syscall_64+0x69/0xc0 [ 60.883142] ? do_syscall_64+0x69/0xc0 [ 60.883147] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10
[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
You referenced the original report, patch, and promotion to Linux Next for review. The new information is that the resolution for the issue you referenced was reviewed and promoted by Greg KH from Linux Next to his queue for Linus https://lore.kernel.org/all/yayq%2fxdb%2fphss7%...@kroah.com/ in the production kernel back on December 5, 2021. BTW it was accepted into Linus's mainline queue with commit https://lore.kernel.org/all/163872600645.987.7156724710444619664.pr-tracker-...@kernel.org/ later that day. Interestingly Greg mentioned merging these changes into the stable queue. If he actually did so (I didn't notice where) it might help to make sure that 21.10 and 22.04 are immediately rebased to include the mainline included patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. Status in linux package in Ubuntu: Confirmed Bug description: Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f. This patch was included in the Ubuntu kernel as Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 and up. The patch is incomplete, which causes an issue with some xHC controllers. An additional patch was made to the upstream mainline kernel, which fixes the issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the second patch. Discussion of the first patch (already in Ubuntu kernel) can be found on the kernel.org mailing list: https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com Discussion of the second patch (not yet in Ubuntu kernel): https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/ Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15 kernels). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: amedee 4158 F pulseaudio /dev/snd/controlC3: amedee 4158 F pulseaudio /dev/snd/controlC0: amedee 4158 F pulseaudio /dev/snd/controlC1: amedee 4158 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 22:23:43 2022 HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973 InstallationDate: Installed on 2022-01-30 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15a dmi.board.asset.tag: Default string dmi.board.name: Z370 AORUS Gaming K3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 AORUS Gaming K3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
This appears to be the resolution upstream: https://lore.kernel.org/linux-usb/yay1eiy%2ff7ezp...@kroah.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. Status in linux package in Ubuntu: Confirmed Bug description: Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f. This patch was included in the Ubuntu kernel as Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 and up. The patch is incomplete, which causes an issue with some xHC controllers. An additional patch was made to the upstream mainline kernel, which fixes the issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the second patch. Discussion of the first patch (already in Ubuntu kernel) can be found on the kernel.org mailing list: https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com Discussion of the second patch (not yet in Ubuntu kernel): https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/ Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15 kernels). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: amedee 4158 F pulseaudio /dev/snd/controlC3: amedee 4158 F pulseaudio /dev/snd/controlC0: amedee 4158 F pulseaudio /dev/snd/controlC1: amedee 4158 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 22:23:43 2022 HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973 InstallationDate: Installed on 2022-01-30 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15a dmi.board.asset.tag: Default string dmi.board.name: Z370 AORUS Gaming K3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 AORUS Gaming K3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
I have also experienced this upstream bug which causes the USB hubs to drop all attached devices. This means that external drive devices all disappear almost as quickly as they appear. Basically it's a show stopper since I can't use my USB attached data drives at all any more. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. Status in linux package in Ubuntu: Confirmed Bug description: Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f. This patch was included in the Ubuntu kernel as Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 and up. The patch is incomplete, which causes an issue with some xHC controllers. An additional patch was made to the upstream mainline kernel, which fixes the issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the second patch. Discussion of the first patch (already in Ubuntu kernel) can be found on the kernel.org mailing list: https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com Discussion of the second patch (not yet in Ubuntu kernel): https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/ Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15 kernels). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: amedee 4158 F pulseaudio /dev/snd/controlC3: amedee 4158 F pulseaudio /dev/snd/controlC0: amedee 4158 F pulseaudio /dev/snd/controlC1: amedee 4158 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 22:23:43 2022 HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973 InstallationDate: Installed on 2022-01-30 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15a dmi.board.asset.tag: Default string dmi.board.name: Z370 AORUS Gaming K3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 AORUS Gaming K3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
Works for me as well. (Does Ubuntu have some sort of karma system similar to Fedora's, i.e., is there another web site somewhere we should be going to to indicate that the fix works for us?) -- 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/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956542] Re: usb devices connected via usb 3.*-Hub are not detected
Dear Matthew, I do not know if it is exactly the same situation here, but after a recent upgrade (early January) I noticed that my external Realtex USB 3.0 hub only gets recognised as VIA Labs USB 2.0 hub and usually does not work at all then. usb 1-1: new high-speed USB device number 6 using xhci_hcd usb 1-1: New USB device found, idVendor=2109, idProduct=2813, bcdDevice=90.11 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1: Product: USB2.0 Hub usb 1-1: Manufacturer: VIA Labs, Inc. hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected When I attach it to a USB 2.0 port, it works. I tested with 5.13.0-22-generic and it was the same. Best, Jonathan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956542 Title: usb devices connected via usb 3.*-Hub are not detected Status in linux package in Ubuntu: Confirmed Bug description: usb devices connected via an usb 3.x-hub are not detected. [53443.604120] usb 4-4.2: new SuperSpeed USB device number 6 using xhci_hcd [53443.707572] usb 4-4.2: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53443.707583] usb 4-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53443.707587] usb 4-4.2: Product: USB3.0 Hub [53443.707589] usb 4-4.2: Manufacturer: VIA Labs, Inc. [53443.709682] hub 4-4.2:1.0: USB hub found [53443.709913] hub 4-4.2:1.0: 4 ports detected [53443.795224] usb 4-4.3: new SuperSpeed USB device number 7 using xhci_hcd [53443.829875] usb 4-4.3: New USB device found, idVendor=0557, idProduct=2410, bcdDevice= 1.19 [53443.829885] usb 4-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53443.829890] usb 4-4.3: Product: 4-Port USB 3.0 Hub [53443.829893] usb 4-4.3: Manufacturer: Generic [53443.840170] hub 4-4.3:1.0: USB hub found [53443.841600] hub 4-4.3:1.0: 4 ports detected [53444.147800] usb 4-4.2.4: new SuperSpeed USB device number 8 using xhci_hcd [53444.251729] usb 4-4.2.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53444.251736] usb 4-4.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53444.251739] usb 4-4.2.4: Product: USB3.0 Hub [53444.251742] usb 4-4.2.4: Manufacturer: VIA Labs, Inc. [53444.257750] hub 4-4.2.4:1.0: USB hub found [53444.257909] hub 4-4.2.4:1.0: 4 ports detected [53444.330559] usb 4-4.3.2: new SuperSpeed USB device number 9 using xhci_hcd [53444.350917] usb 4-4.3.2: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 1.00 [53444.350926] usb 4-4.3.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [53444.353872] hub 4-4.3.2:1.0: USB hub found [53444.354204] hub 4-4.3.2:1.0: 4 ports detected [53444.647364] usb 4-4.2.4.2: new SuperSpeed USB device number 10 using xhci_hcd [53444.765499] usb 4-4.2.4.2: New USB device found, idVendor=0bda, idProduct=0301, bcdDevice= 1.30 [53444.765507] usb 4-4.2.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [53444.765510] usb 4-4.2.4.2: Product: USB3.0 Card Reader [53444.765512] usb 4-4.2.4.2: Manufacturer: Realtek [53444.765514] usb 4-4.2.4.2: SerialNumber: 201210233001 [53444.777193] usb-storage 4-4.2.4.2:1.0: USB Mass Storage device detected [53444.778469] scsi host7: usb-storage 4-4.2.4.2:1.0 [53444.903836] usb 4-4.2.4.4: new SuperSpeed USB device number 11 using xhci_hcd [53445.010197] usb 4-4.2.4.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53445.010203] usb 4-4.2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53445.010205] usb 4-4.2.4.4: Product: USB3.0 Hub [53445.010207] usb 4-4.2.4.4: Manufacturer: VIA Labs, Inc. [53445.014033] hub 4-4.2.4.4:1.0: USB hub found [53445.015233] hub 4-4.2.4.4:1.0: 4 ports detected [53445.447869] usb 4-4.2.4.4.4: new SuperSpeed USB device number 12 using xhci_hcd [53445.555240] usb 4-4.2.4.4.4: New USB device found, idVendor=2109, idProduct=0813, bcdDevice=90.11 [53445.555248] usb 4-4.2.4.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [53445.555251] usb 4-4.2.4.4.4: Product: USB3.0 Hub [53445.555254] usb 4-4.2.4.4.4: Manufacturer: VIA Labs, Inc. [53445.557571] hub 4-4.2.4.4.4:1.0: USB hub found [53445.557780] hub 4-4.2.4.4.4:1.0: 4 ports detected Connecting various devices to this 13-port-hub does not lead to device detection. The devices connected are just ignored. Some devices are detected, but it might take some time (up to two minutes until they are): Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc Jan 6 02:11:37 ivory bluetoothd[8177]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Jan 6 02:11:37 ivory bluetoothd
[Kernel-packages] [Bug 1945676] Re: Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3
ubuntu@localhost:~$ snap change 6 Status Spawn Ready Summary Donetoday at 16:03 UTC today at 16:04 UTC Ensure prerequisites for "pi-kernel" are available Undone today at 16:03 UTC today at 16:04 UTC Download snap "pi-kernel" (352) from channel "18-pi3/beta" Donetoday at 16:03 UTC today at 16:04 UTC Fetch and check assertions for snap "pi-kernel" (352) Undone today at 16:03 UTC today at 16:04 UTC Mount snap "pi-kernel" (352) Undone today at 16:03 UTC today at 16:04 UTC Run pre-refresh hook of "pi-kernel" snap if present Undone today at 16:03 UTC today at 16:04 UTC Stop snap "pi-kernel" services Undone today at 16:03 UTC today at 16:04 UTC Remove aliases for snap "pi-kernel" Undone today at 16:03 UTC today at 16:04 UTC Make current revision for snap "pi-kernel" unavailable Error today at 16:03 UTC today at 16:04 UTC Update assets from kernel "pi-kernel" (352) Holdtoday at 16:03 UTC today at 16:04 UTC Copy snap "pi-kernel" data Holdtoday at 16:03 UTC today at 16:04 UTC Setup snap "pi-kernel" (352) security profiles Holdtoday at 16:03 UTC today at 16:04 UTC Make snap "pi-kernel" (352) available to the system Holdtoday at 16:03 UTC today at 16:04 UTC Automatically connect eligible plugs and slots of snap "pi-kernel" Holdtoday at 16:03 UTC today at 16:04 UTC Set automatic aliases for snap "pi-kernel" Holdtoday at 16:03 UTC today at 16:04 UTC Setup snap "pi-kernel" aliases Holdtoday at 16:03 UTC today at 16:04 UTC Run post-refresh hook of "pi-kernel" snap if present Holdtoday at 16:03 UTC today at 16:04 UTC Start snap "pi-kernel" (352) services Holdtoday at 16:03 UTC today at 16:04 UTC Clean up "pi-kernel" (352) install Holdtoday at 16:03 UTC today at 16:04 UTC Run configure hook of "pi-kernel" snap if present Holdtoday at 16:03 UTC today at 16:04 UTC Run health check of "pi-kernel" snap Donetoday at 16:03 UTC today at 16:04 UTC Consider re-refresh of "pi-kernel" .. Update assets from kernel "pi-kernel" (352) 2021-09-30T16:04:01Z ERROR gadget does not consume any of the kernel assets needing synced update "dtbs" ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945676 Title: Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3 Status in linux package in Ubuntu: New Bug description: ubuntu@localhost:~$ sudo snap refresh pi-kernel --channel=18-pi3/beta error: cannot perform the following tasks: - Update assets from kernel "pi-kernel" (352) (gadget does not consume any of the kernel assets needing synced update "dtbs") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945676] Re: Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3
ubuntu@localhost:~$ sudo snap refresh pi snap "pi" has no updates available ubuntu@localhost:~$ sudo snap refresh pi-kernel snap "pi-kernel" has no updates available ubuntu@localhost:~$ snap list Name Version RevTracking Publisher Notes core18 20210722 2126 latest/stable canonical✓ base pi 18-1 68 18-pi3/stable canonical✓ gadget pi-kernel 4.15.0-1096.102 34818-pi3/stable canonical✓ kernel snapd 2.51.7 13173 latest/stable canonical✓ snapd ubuntu@localhost:~$ snap version snap2.51.7 snapd 2.51.7 series 16 kernel 4.15.0-1096-raspi2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945676 Title: Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3 Status in linux package in Ubuntu: New Bug description: ubuntu@localhost:~$ sudo snap refresh pi-kernel --channel=18-pi3/beta error: cannot perform the following tasks: - Update assets from kernel "pi-kernel" (352) (gadget does not consume any of the kernel assets needing synced update "dtbs") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945676] [NEW] Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3
Public bug reported: ubuntu@localhost:~$ sudo snap refresh pi-kernel --channel=18-pi3/beta error: cannot perform the following tasks: - Update assets from kernel "pi-kernel" (352) (gadget does not consume any of the kernel assets needing synced update "dtbs") ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Juerg Haefliger (juergh) 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/1945676 Title: Failed to refresh to pi-kernel 4.15.0-1096.102 rev 351/352 track 18-pi3 Status in linux package in Ubuntu: New Bug description: ubuntu@localhost:~$ sudo snap refresh pi-kernel --channel=18-pi3/beta error: cannot perform the following tasks: - Update assets from kernel "pi-kernel" (352) (gadget does not consume any of the kernel assets needing synced update "dtbs") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913768] Re: HP Touchpad Not Detected
No touchpad listed on HP 15-dw3165st with Ubuntu 18.04 ** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1913768/+attachment/5518840/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1913768 Title: HP Touchpad Not Detected Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Touchpad is not working and is not shown in output of command: cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 22:02:57 2021 InstallationDate: Installed on 2021-01-29 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1913768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938269] Re: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour
dawson-i similar information for dawson-i: 14:56:57 Interface wlan0 using module iwlwifi 14:56:57 Parameters: 14:56:57 lar_disable: N 14:56:57 fw_monitor: N 14:56:57 11n_disable: 0 14:56:57 power_save: N 14:56:57 swcrypto: 0 14:56:57 antenna_coupling: 0 14:56:57 power_level: 0 14:56:57 amsdu_size: 0 14:56:57 uapsd_disable: 3 14:56:57 d0i3_timeout: 1000 14:56:57 fw_restart: Y 14:56:57 d0i3_disable: Y 14:56:57 led_mode: 0 14:56:57 disable_11ac: N 14:56:57 bt_coex_active: Y 14:56:57 nvm_file: (null) 14:56:57 14:56:57 Checking kernel ring buffer for iwlwifi messages: 14:56:57 kern :info : [Fri Jul 23 13:40:10 2021] iwlwifi :01:00.0: enabling device ( -> 0002) 14:56:57 kern :info : [Fri Jul 23 13:40:10 2021] iwlwifi :01:00.0: loaded firmware version 34.0.1 op_mode iwlmvm 14:56:57 kern :info : [Fri Jul 23 13:40:10 2021] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 14:56:57 kern :info : [Fri Jul 23 13:40:10 2021] iwlwifi :01:00.0: base HW address: ac:ed:5c:db:45:39 14:56:57 kern :err : [Fri Jul 23 13:40:26 2021] iwlwifi :01:00.0: BIOS contains WGDS but no WRDS ** Description changed: Several amd64 devices have shown an marked increase in failures to complete automated testing with this kernel snap that is currently on 18/beta channel. The devices tested are: dawson-j device type: NUC7PJYH, NUC7CJYH processor: Pentium Silver J5005 1.50GHz, Celeron J4005 2.00GHz ethernet: Realtek 10ec:8168 wireless: Intel 8086:31dc dawson-i device-type: NUC7i3DNHE, NUC7i5DNHE processor: i3-7100U 2.40GHz, i5-7300U 2.60GHz ethernet: Intel 8086:156f wireless: Intel 8086:24fd dearest-team device-type: Inspiron 5758 processor: i5-5200U 2.20GHz ethernet: Realtek 10ec:8136 wireless: Intel 8086:08b3 Symptoms shown by these devices are not the controller side that manages the test run loses connection with the device while carrying out WiFi - connection tests. + connection tests. The failure rate does not appear to be 100%, there + have been some runs that have completed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938269 Title: pc-kernel snap 4.15.0-152.159 (UC18) regression in network behaviour Status in linux package in Ubuntu: New Bug description: Several amd64 devices have shown an marked increase in failures to complete automated testing with this kernel snap that is currently on 18/beta channel. The devices tested are: dawson-j device type: NUC7PJYH, NUC7CJYH processor: Pentium Silver J5005 1.50GHz, Celeron J4005 2.00GHz ethernet: Realtek 10ec:8168 wireless: Intel 8086:31dc dawson-i device-type: NUC7i3DNHE, NUC7i5DNHE processor: i3-7100U 2.40GHz, i5-7300U 2.60GHz ethernet: Intel 8086:156f wireless: Intel 8086:24fd dearest-team device-type: Inspiron 5758 processor: i5-5200U 2.20GHz ethernet: Realtek 10ec:8136 wireless: Intel 8086:08b3 Symptoms shown by these devices are not the controller side that manages the test run loses connection with the device while carrying out WiFi connection tests. The failure rate does not appear to be 100%, there have been some runs that have completed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
