[Bug 2086212] Re: IDPF driver should be module, not built-in
** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gke (Ubuntu Noble) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086212 Title: IDPF driver should be module, not built-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2086212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086212] [NEW] IDPF driver should be module, not built-in
Public bug reported: SRU Justification [Impact] Google requested the IDPF driver be changed from a built-in module to a loadable module in the linux-modules package. [Fix] Add drivers/net/ethernet/intel/idpf/* to the inclusion-list and change CONFIG_IDPF to build the driver as a loadable module rather than a built-in. [Test Plan] List files in the linux-modules package and verify that idpf.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to linux-modules. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086212 Title: IDPF driver should be module, not built-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2086212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086079] [NEW] fix blk_mq_hw_ctx active request
Public bug reported:
SRU Justification
[Impact]
Google has requested this commit be backported to the 5.15 GKE images.
It is already included in 6.* GKE kernels, and resolves some networking
issues for them.
[Fix]
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ddad59331a4e16088468ca0ad228a9fe32d7955a
("blk-mq: fix blk_mq_hw_ctx active request accounting")
[Test Case]
Compile and boot tested
[Where problems could occur]
This patch affects multiqueue block IO queueing. Google will need to
confirm that this patch resolves their related networking problems.
** Affects: linux-gke (Ubuntu)
Importance: Undecided
Assignee: Ian Whitfield (ijwhitfield)
Status: New
** Affects: linux-gke (Ubuntu Jammy)
Importance: Undecided
Assignee: Ian Whitfield (ijwhitfield)
Status: New
** Also affects: linux-gke (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-gke (Ubuntu)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
** Changed in: linux-gke (Ubuntu Jammy)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086079
Title:
fix blk_mq_hw_ctx active request
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2086079/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085904] Re: Enable IOMMU Passthrough by default
** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085904 Title: Enable IOMMU Passthrough by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2085904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085904] [NEW] Enable IOMMU Passthrough by default
Public bug reported: SRU Justification [Impact] C3 bare metal instances run into a problem on 6.8 kernels due to Intel IOMMU being enabled by default. After performing enough disk-intensive work on the instance, the system becomes unusable and reports I/O errors at the command line until rebooted, losing data in the process. The root issue is being worked on long-term, but in the meantime we will apply a workaround to the issue for affected customers. This fix has a negative impact on security, so it is limited to Jammy kernels for which this issue is a regression. Noble kernels have always had this problem and therefore will be waiting for the long-term fix. [Fix] Change the kernel config to use IOMMU passthrough by default. [Test Plan] Perform up to 50 kernel builds on the instance in sequence. Failures on affected instances are usually detected after only 1 or 2. [Regression potential] Regression potential is especially low for Jammy as we are essentially reverting a breaking change. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085904 Title: Enable IOMMU Passthrough by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2085904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081803] Re: kernel >= 6.8.0-44.44 vmwgfx regression in Ubuntu 24.04.1 Desktop VM guest (VMWare Workstation Pro 17.5.2/17.6)
The real issue here seems to be the lack of Autofit configuration on a per-VM basis. I've added back some of the modes and added some additional ones which users will likely have [1]. As for the resolutions that exceed the monitor resolution the only thing that limits the size of a virtual display is the max GPU texture size which is usually 16K x 16K or larger. We can always add scroll bars to the window when the resolution exceeds the monitor size even though its probably not very useful. Alternatively if you have multiple (4 or 9) monitors arranged in a cube you can create a window with a resolution that will fit on the extended displays but exceeds the resolution of any single monitor. https://patchwork.freedesktop.org/patch/621992/ ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081803 Title: kernel >= 6.8.0-44.44 vmwgfx regression in Ubuntu 24.04.1 Desktop VM guest (VMWare Workstation Pro 17.5.2/17.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hello Michael, I sent you an email to ask for confirmation regarding these other kernels that require verification, I did verify the linux/6.8.0-48.48 kernel in -proposed but I have not tested these other kernels. What would be the best way to get this issue resolved regarding the other kernels? Thanks, Ian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003266] Re: 22.04 package lacks GSSAPI support
I was able to confirm that the envvar works with other Kerberos- connected applications (e.g. `curl --negotiate -u : $ENDPOINT`). Setting the envvar before running `kinit` works fine as well. The command I'm running is `mount ~/mountpoint`, no sudo added. `/home/username/mountpoint` is defined in `/etc/fstab`. davfs2 (the neon consumer) does call seteuid and setgid, though I don't know if that'd matter with these envvars. (https://github.com/volga629/davfs2/blob/8bad5be1e370d527f89144cfbfe64f6a0a014390/src/mount_davfs.c#L428-L431) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003266] Re: 22.04 package lacks GSSAPI support
@ahasenack: no additional output after setting that environment variable (either stderr or a file) and running the appropriate `mount` command. I believe this may be due to neon using a secure context, which should drop that envvar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084716] Re: Disable Multi-Gen LRU in the 6.8 kernel
** Also affects: linux-gke (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-gke (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Noble) Assignee: (unassigned) => Ian Whitfield (ijwhitfield) ** Changed in: linux-gke (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084716 Title: Disable Multi-Gen LRU in the 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2084716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084716] [NEW] Disable Multi-Gen LRU in the 6.8 kernel
Public bug reported: [Impact] Due to upstream Kubernetes issue #127844, Multi-Gen LRU has been requested by Google to be disabled until a permanent fix is implemented. This feature unintentionally changed the output of kubelet's memory usage calculations in an unexpected way. [Fix] Disabled Multi-Gen LRU in the kernel config. [Test Case] Compile and boot test. [Where things could go wrong] If this fix is unsuccessful, memory usage calculations will not return to as they were before GKE 1.30. [Other Info] Upstream issue: https://github.com/kubernetes/kubernetes/issues/127844 ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Noble) Importance: Medium Assignee: Ian Whitfield (ijwhitfield) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084716 Title: Disable Multi-Gen LRU in the 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2084716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003266] Re: 22.04 package lacks GSSAPI support
A brief update here: I'm testing the new version (0.32.2-1ubuntu0.1) of the package, and I can confirm that I see the expected GSSAPI strings in the neon27 binary. That said, trying to use Kerberos behavior in a neon27 consumer (davfs2) doesn't seem to be working. I'm not sure if that's a configuration issue, or if it's a problem with the library. I'm working on figuring that out now. (davfs2 logs show that it tries Negotiate auth, then skips to Basic auth without further logging output, making this more difficult to diagnose.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081803] Re: kernel >= 6.8.0-44.44 vmwgfx regression in Ubuntu 24.04.1 Desktop VM guest (VMWare Workstation Pro 17.5.2/17.6)
This is the expected behavior. If you'd like to discuss a feature request/change you can do it here: https://community.broadcom.com/vmware-cloud- foundation/communities/community- home/digestviewer?communitykey=fb707ac3-9412-4fad-b7af-018f5da56d9f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081803 Title: kernel >= 6.8.0-44.44 vmwgfx regression in Ubuntu 24.04.1 Desktop VM guest (VMWare Workstation Pro 17.5.2/17.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
I was able to successfully update using the proposed(6.8.0-48.48) kernel. Attaching screenshot of successful update. ** Attachment added: "proposedkernelsuccessfulupdate.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+attachment/5824940/+files/proposedkernelsuccessfulupdate.png ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081891] Re: linux-gcp: mlx5_ib needed in the linux-modules package
Description updated to reflect this patch being needed for Oracular now. ** Description changed: SRU Justification [Impact] Google requested the mlx5_ib driver be moved to the linux-modules package from the linux-modules-extra package, so that it is included by default in some of their images where the hardware support is needed. - This change is relevant for noble:linux-gcp and jammy:linux-gcp-6.8 + This change is relevant for noble:linux-gcp, oracular:linux-gcp, and + jammy:linux-gcp-6.8 [Fix] Add drivers/infiniband/hw/mlx5/mlx5_ib.ko to debian.gcp(-6.8)/control.d/gcp.inclusion-list. [Test Plan] List files in the linux-modules package and verify that mlx5_ib.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081891 Title: linux-gcp: mlx5_ib needed in the linux-modules package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2081891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083566] [NEW] LTS upgrade fails for Ubuntu Studio
Public bug reported: Ubuntu Studio notifies about an LTS upgrade along with support expiry in 197 days, which then fails with the error 'Could not determine the upgrade'. This is against a 5 day old install of 22.04 which has had nothing additional installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 5.15.0-122.132-lowlatency 5.15.163 Uname: Linux 5.15.0-122-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:124:187957:2024-10-02 23:36:12.842945778 +0100:2024-10-02 23:36:12.841945818 +0100:/var/crash/_usr_bin_do-release-upgrade.0.crash 640:1000:124:103471:2024-09-25 20:10:57.488366203 +0100:2024-10-02 23:39:41.247184504 +0100:/var/crash/_usr_bin_fcitx-dbus-watcher.1000.crash CurrentDesktop: KDE Date: Wed Oct 2 23:51:40 2024 InstallationDate: Installed on 2024-09-25 (7 days ago) InstallationMedia: Ubuntu-Studio 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-10-02 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083566 Title: LTS upgrade fails for Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083557] [NEW] Create 64K page size AWS kernel for ARM
Public bug reported: [Impact] * Offering a 64k page size kernel for AWS cloud instances would provide feature match with other clouds and improved optionality for users. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression as no logic is changed * Should be verified by checking built packages [Other Info] * SF #00392971 ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083557 Title: Create 64K page size AWS kernel for ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2083557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081891] [NEW] linux-gcp: mlx5_ib needed in the linux-modules package
Public bug reported: SRU Justification [Impact] Google requested the mlx5_ib driver be moved to the linux-modules package from the linux-modules-extra package, so that it is included by default in some of their images where the hardware support is needed. This change is relevant for noble:linux-gcp and jammy:linux-gcp-6.8 [Fix] Add drivers/infiniband/hw/mlx5/mlx5_ib.ko to debian.gcp(-6.8)/control.d/gcp.inclusion-list. [Test Plan] List files in the linux-modules package and verify that mlx5_ib.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081891 Title: linux-gcp: mlx5_ib needed in the linux-modules package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2081891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
Reverting 0a46ef234756dca04623b7591e8ebb3440622f0b on Linux 6.10.10 allows the test to run to completion w/o any lockups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2080853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
$ git bisect bad 0a46ef234756dca04623b7591e8ebb3440622f0b is the first bad commit commit 0a46ef234756dca04623b7591e8ebb3440622f0b (HEAD) Author: Jan Kara Date: Thu Mar 21 17:26:50 2024 +0100 ext4: do not create EA inode under buffer lock ext4_xattr_set_entry() creates new EA inodes while holding buffer lock on the external xattr block. This is problematic as it nests all the allocation locking (which acquires locks on other buffers) under the buffer lock. This can even deadlock when the filesystem is corrupted and e.g. quota file is setup to contain xattr block as data block. Move the allocation of EA inode out of ext4_xattr_set_entry() into the callers. Reported-by: syzbot+a43d4f48b8397d0e4...@syzkaller.appspotmail.com Signed-off-by: Jan Kara Link: https://lore.kernel.org/r/20240321162657.27420-2-j...@suse.cz Signed-off-by: Theodore Ts'o fs/ext4/xattr.c | 113 ++--- 1 file changed, 53 insertions(+), 60 deletions(-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2080853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
The vm size fixes were released in stress-ng V0.18.04 and I sync'd this into Ubuntu oracular last week. ** Changed in: stress-ng (Ubuntu Oracular) Status: Confirmed => Fix Released ** Changed in: stress-ng (Ubuntu Noble) Importance: Undecided => High ** Changed in: stress-ng (Ubuntu Oracular) Importance: Undecided => High ** Changed in: stress-ng (Ubuntu Noble) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng (Ubuntu Oracular) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
I do monthly releases, so 1st week of October is the next release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
** Description changed: How to reproduce this issue: Kernel: 6.11.0-7, AMD64 virtual machine, oracular, updated 16th Sept 2024 @ 14:15 UK TZ 8 thread virtual machine (important, must be multiple CPU threads to trigger the regression) 20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1 sudo mkfs.ext4 /dev/vdb1 -O ea_inode sudo mount /dev/vdb1 /mnt git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) - ..wait a couple of minutes, you will see that the number of running processes is not 8 as expected (from the --vmstat output of stress-ng) - cannot ^C stop stress-ng because of a kernel lockup, use another tty and + cannot stop stress-ng because of a kernel lockup; so use another tty and check dmesg, I get the following: [ 247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds. [ 247.030830] Not tainted 6.11.0-7-generic #7-Ubuntu [ 247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548 tgid:1548 ppid:2 flags:0x4000 [ 247.034176] Call Trace: [ 247.034178] [ 247.034182] __schedule+0x277/0x6c0 [ 247.034199] schedule+0x29/0xd0 [ 247.034203] jbd2_journal_wait_updates+0x77/0xf0 [ 247.034207] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034213] jbd2_journal_commit_transaction+0x290/0x1a10 [ 247.034223] kjournald2+0xa8/0x250 [ 247.034228] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034233] ? __pfx_kjournald2+0x10/0x10 [ 247.034236] kthread+0xe1/0x110 [ 247.034241] ? __pfx_kthread+0x10/0x10 [ 247.034244] ret_from_fork+0x44/0x70 [ 247.034247] ? __pfx_kthread+0x10/0x10 [ 247.034251] ret_from_fork_asm+0x1a/0x30 [ 247.034257] NOTE: this works fine for Limux 6.8.0-31, so this looks like a regression for 6.11.0-7 Attached is the full kernel log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2080853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
Seems to occur on 6.10 too. ** Bug watch added: Linux Kernel Bug Tracker #219283 https://bugzilla.kernel.org/show_bug.cgi?id=219283 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=219283 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2080853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080853] [NEW] oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
Public bug reported: How to reproduce this issue: Kernel: 6.11.0-7, AMD64 virtual machine, oracular, updated 16th Sept 2024 @ 14:15 UK TZ 8 thread virtual machine (important, must be multiple CPU threads to trigger the regression) 20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1 sudo mkfs.ext4 /dev/vdb1 -O ea_inode sudo mount /dev/vdb1 /mnt git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ..wait a couple of minutes, you will see that the number of running processes is not 8 as expected (from the --vmstat output of stress-ng) cannot ^C stop stress-ng because of a kernel lockup, use another tty and check dmesg, I get the following: [ 247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds. [ 247.030830] Not tainted 6.11.0-7-generic #7-Ubuntu [ 247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548 tgid:1548 ppid:2 flags:0x4000 [ 247.034176] Call Trace: [ 247.034178] [ 247.034182] __schedule+0x277/0x6c0 [ 247.034199] schedule+0x29/0xd0 [ 247.034203] jbd2_journal_wait_updates+0x77/0xf0 [ 247.034207] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034213] jbd2_journal_commit_transaction+0x290/0x1a10 [ 247.034223] kjournald2+0xa8/0x250 [ 247.034228] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034233] ? __pfx_kjournald2+0x10/0x10 [ 247.034236] kthread+0xe1/0x110 [ 247.034241] ? __pfx_kthread+0x10/0x10 [ 247.034244] ret_from_fork+0x44/0x70 [ 247.034247] ? __pfx_kthread+0x10/0x10 [ 247.034251] ret_from_fork_asm+0x1a/0x30 [ 247.034257] NOTE: this works fine for Limux 6.8.0-31, so this looks like a regression for 6.11.0-7 Attached is the full kernel log. ** Affects: linux (Ubuntu) Importance: High Status: New ** Attachment added: "kernel log" https://bugs.launchpad.net/bugs/2080853/+attachment/5817945/+files/kern.log ** Description changed: How to reproduce this issue: Kernel: 6.11.0-7, AMD64 virtual machine, oracular, updated 16th Sept 2024 @ 14:15 UK TZ 8 thread virtual machine (important, must be multiple CPU threads to trigger the regression) 20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1 sudo mkfs.ext4 /dev/vdb1 -O ea_inode sudo mount /dev/vdb1 /mnt git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) - sudo ./stress-ng --xattr 8 -t 120 --vmstat 1 ..wait a couple of minutes, you will see that the number of running processes is not 8 as expected (from the --vmstat output of stress-ng) cannot ^C stop stress-ng because of a kernel lockup, use another tty and check dmesg, I get the following: [ 247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds. [ 247.030830] Not tainted 6.11.0-7-generic #7-Ubuntu [ 247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548 tgid:1548 ppid:2 flags:0x4000 [ 247.034176] Call Trace: [ 247.034178] [ 247.034182] __schedule+0x277/0x6c0 [ 247.034199] schedule+0x29/0xd0 [ 247.034203] jbd2_journal_wait_updates+0x77/0xf0 [ 247.034207] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034213] jbd2_journal_commit_transaction+0x290/0x1a10 [ 247.034223] kjournald2+0xa8/0x250 [ 247.034228] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034233] ? __pfx_kjournald2+0x10/0x10 [ 247.034236] kthread+0xe1/0x110 [ 247.034241] ? __pfx_kthread+0x10/0x10 [ 247.034244] ret_from_fork+0x44/0x70 [ 247.034247] ? __pfx_kthread+0x10/0x10 [ 247.034251] ret_from_fork_asm+0x1a/0x30 [ 247.034257] - - NOTE: this works fine for Limux 6.8.0-31, so this looks like a regression for 6.11.0-7 + NOTE: this works fine for Limux 6.8.0-31, so this looks like a + regression for 6.11.0-7 Attached is the full kernel log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080443] [NEW] Create 64K page size GCP kernel for ARM
Public bug reported: [Impact] * 64k page size flavor was requested by Google [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression as no logic is changed * Should be verified by checking built packages [Other Info] * SF #00384132 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080443 Title: Create 64K page size GCP kernel for ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080242] [NEW] cannot upgrade from 22.04 to 24.04 LTS
Public bug reported: Confirmed bug #2075274 cannot upgrade from 22.04 to 24.04 LTS. Reporting that even after 29.8.24 I still have been unable to upgrade using the ubuntu-release-upgrader ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Sep 10 13:34:30 2024 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-10 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-10 13:31:35 Requested-By: inski (1000) End-Date: 2024-09-10 13:31:35 VarLogDistupgradeApttermlog: Log started: 2024-09-10 13:31:35 Log ended: 2024-09-10 13:31:35 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080242 Title: cannot upgrade from 22.04 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080239] [NEW] Software Updater "up to date" message is misleading with phasing
Public bug reported: Software Update is confusing some users by: - Claiming that software is up-to-date, and offering a release-upgrade - Failing to install the selected release-upgrade due to phased updates. Example showing the issue in Ubuntu 22.04: https://askubuntu.com/questions/1526235/upgrade-button-from-software- updater-doesnt-work/1526256 Software Update "upgrade" selection (and do-release-upgrade) might ignore phasing, as those phasing packages may be replaced. Alternately, Software Update should be aware of phasing. It should not offer a release-upgrade during phasing, or might offer an alternative message "available soon". ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080239 Title: Software Updater "up to date" message is misleading with phasing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2080239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
Good idea. I'll put that in for the next release, maybe under the -v verbose mode option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
My bad, I left some debug in the code to force it to fail. I've pushed a fix: commit 8cc021b51b2e6ff3d7c7c670c7c42aa4e58dfe87 (HEAD -> master, origin/master, origin/HEAD) Author: Colin Ian King Date: Fri Sep 6 16:35:16 2024 +0100 stress-vm: remove debugging setting if in statement Remove 1 | in if statement, accidentially left in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
I've fixed this and pushed the fix upstream: commit 3f6556fecb4386ee0eaecc8e187c659c15ae2039 (HEAD -> master) Author: Colin Ian King Date: Fri Sep 6 15:43:41 2024 +0100 stress-*: fix vm memory % size parameter handling I'll try and get a new release of stress-ng out fairly soon once I've re-run the regressions tests. If you can test stress-ng from the current git repo tip (commit 3f6556fecb4386ee0eaecc8e187c659c15ae2039) and let me know if this fixes this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078871] Re: Using a percentage of memory no longer works
I've added more debug into the vm stressor to see how much memory is being allocated and the cause of the mmap failure with the upstream stress-ng commit: commit bca728b8f636935d5e13151b0886eadcd679d9a1 (HEAD -> master, origin/master, origin/HEAD) Author: Colin Ian King Date: Thu Sep 5 18:20:14 2024 +0100 Perhaps you can build stress-ng from source in the container and re-run the built version to see if this gives more insight to why it's failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078871 Title: Using a percentage of memory no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/2078871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1998738] Re: dev test from ubuntu_stress_smoke_tests cause kernel oops on F-5.4 xilinx ZCU106
The dev test could randomly hit the kernel bug due to the chaotic racy access of devices by this stressor. One could try and use --no-rand-seed to use the same base random seed for more repeatable testing. The dev stressor does report the device being accessed in argv[], this can be observed when using ps -ef, for example one will see output something like: root 596457 596449 57 00:05 pts/000:00:03 stress-ng-dev:/dev/input/mice root 596458 596451 36 00:05 pts/000:00:02 stress-ng-dev:/dev/input/event2 root 596459 596450 25 00:05 pts/000:00:01 stress-ng-dev:/dev/input/mouse2 root 596461 596453 3 00:05 pts/000:00:00 stress-ng-dev:/dev/psaux root 596462 596452 21 00:05 pts/000:00:01 stress-ng-dev:/dev/vhost-vsock root 596474 596454 5 00:05 pts/000:00:00 stress-ng-dev:/dev/input/mouse2 root 596483 596455 55 00:05 pts/000:00:03 stress-ng-dev:/dev/input/event2 root 596484 596456 22 00:05 pts/000:00:01 stress-ng-dev:/dev/psaux ...showing the stress-ng-dev stressor followed by the name of the device being exercised. If these processes are hung then it will show which device was being accessed when the process hung. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1998738 Title: dev test from ubuntu_stress_smoke_tests cause kernel oops on F-5.4 xilinx ZCU106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1998738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061695] Re: package matlab-support 0.0.23 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1
I tried to upgrade from Kubuntu 22.04 to 24.04.1. The process hung producing many copies of the following error messages. No MATLAB installation found No MATLAB executables were found in the directories you specified. This package requires at least one local installation of MATLAB. Redundant argument in sprintf at /usr/share/perl5/Debconf/Element/Noninteractive/Error.pm line 54, line 1168970. mail: cannot send message: Process exited with a non-zero status I aborted the upgrade and fortunately I was able to get back in to Kunbuntu. I ]uninstalled matlab-support and restarted the dist-upgrade. Every thing went OK. Subsequently reinstalling matlab-support worked OK. Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-41-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 matlab-support version 0.1 (after reinstallation: I have no record of what it was under 22.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061695 Title: package matlab-support 0.0.23 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/2061695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078794] [NEW] Multiload appears as a small bar in panel
Public bug reported: I've just upgraded from Xubuntu 22.04 to 24.04.1. Multiload no longer works properly. In the panel, it appears a small horizontal bar, I think I can just about see something happening but it is difficult to know for sure. When I right click on it the menu pops up for a fraction of a second then disappears. I've tried purging multiload and re-installing but that did not work. Xfce: 4.18 GKT: 3.24.41 kernel: 6.8.0-41-generic CPU: Intel Celeron N3060 GPU: Mesa Intel HD Graphics 400 ** Affects: indicator-multiload (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078794 Title: Multiload appears as a small bar in panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/2078794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067340] Re: can't open pdfs
Same is true for .jpg files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067340 Title: can't open pdfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2067340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067340] Re: can't open pdfs
I've just upgraded from Kubuntu 22.04 to 24.04.1 and this bug appeared. The pdf is being saved to the Dowonload/thunderbird.tmp folder but no pdf viewer is started. This sort of problem was discussed in 2019: https://forum.snapcraft.io/t/cannot-open-pdf-attachment-with- thunderbird/11845 but it read as if it would be fixed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067340 Title: can't open pdfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2067340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
Also able to crash current Oracular amd64 generic kernel with stress-ng apparmor stressor, see attached image ** Attachment added: "image of oracular crash" https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+attachment/5810324/+files/Screenshot%20from%202024-08-29%2010-27-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
If there are any other kernels or things you would like me to test for this issue, don't hesitate to let me know. Thanks, Ian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Attachment added: "image (2).png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+attachment/5808751/+files/image%20%282%29.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hi Michael, I installed a brand new 24.04 and applied your kernel updates, the linux-cloud-tools and linux-tools were unable to be installed, but this shouldn't have affected the process. After a reboot I used the firmware-nic-is-intel ./setup file after and I encountered no issues during the update process, and it was much more quick than when the process would fail. Regression risk would be low. I am also attaching a screenshot of the success in updating the firmware. Thanks Michael! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
** Tags removed: verification-needed-focal-linux-hwe-5.15 ** Tags added: verification-done-focal-linux-hwe-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
Linux-hwe-6.8.0.41 doesnt exhibit the problem in jammy, but then again neither did 6.8.0.40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
Thought I may as well install Virtualbox and test it whilst I was here. Booted to kernel 117, Installed VB 6.1.50 from repos. Created VM with no disc, started it, got the Guru-mediation error. Rebooted to 119 kernel, VM started just fine. I can confirm kernel 119 fixes the problem for focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4
linux-hwe-5.15.0-119 does seem to be in the focal-proposed2 repos now. Added proposed2 to a test system and 119 was installed on update. Couldnt test virtualbox though as not installed on the system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075274] Re: cannot upgrade from 22.04 to 24.04 LTS
Kubuntu desktop is the preferred desktop and in use at the time of this report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075274 Title: cannot upgrade from 22.04 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2075274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075274] [NEW] cannot upgrade from 22.04 to 24.04 LTS
Public bug reported: An resolvable problem occurred while calculating the upgrade using the GUI upgrade prompt ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-1027.27~22.04.1-oracle 6.5.13 Uname: Linux 6.5.0-1027-oracle x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Jul 30 23:53:51 2024 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-07-30 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-07-30 23:51:04 Requested-By: inski (1000) End-Date: 2024-07-30 23:51:04 VarLogDistupgradeApttermlog: Log started: 2024-07-30 23:51:04 Log ended: 2024-07-30 23:51:04 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2024-07-27T12:35:03.312636 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075274 Title: cannot upgrade from 22.04 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2075274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Attachment added: "kernel-install-2.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+attachment/5800571/+files/kernel-install-2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Attachment added: "kernel-install-1.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+attachment/5800570/+files/kernel-install-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hello Michael, I was able to install the kernel you have given me, however two of the packages has dependency issues that prevented their install, the linux- cloud-tools-6.8.0-40 & linux-tools-6.8.0-40. I have attached screenshots showing the errors after install of the other kernel packages. After a reboot, this kernel enabled me to successfully update the firmware in a timely manner. (Screenshot attached) In my experience working with both the kernel I had patched and the kernel given to me, I had not run into any issues or anything that hints that the kernel may be broken. ** Attachment added: "successful-firmware-upgrade.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+attachment/5800569/+files/successful-firmware-upgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
There are currently some difficulties with the SUT infrastructure due to the typhoon in Taiwan so I am unable to at this moment, but will once services are back. I am not entirely sure what your regression risk question is asking, are you asking how many releases back this issue spans? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074003] [NEW] autofs fails to renew Kerberos ticket
Public bug reported: Autofs 5.1.9 contains a bug such that when map sources are held on an LDAP server with Kerberos authentication it fails to connect to the server after the first Kerberos ticket has expired. It's been fixed by a patch in Fedora, but Noble currently has the broken version. The gory details are here: https://bugzilla.redhat.com/show_bug.cgi?id=2214399 The patch landed in Fedora version 5.1.9-7.fc40 and is called 'autofs-5.1.9-fix-always-recreate-credential-cache.patch' The detail is that on line 679 of modules/cyrus-sasl.c there's a call to monotonic_time(NULL) which needs instead to be the vanilla time(NULL) to fetch the current wall-clock time. Thanks ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074003 Title: autofs fails to renew Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2074003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073852] Re: apparmor: access to uninitialized variable size may cause loop bounds overflow
** Summary changed: - apparmor: access to uniniatliaed variable size may cause loop bounds overflow + apparmor: access to uninitialized variable size may cause loop bounds overflow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073852 Title: apparmor: access to uninitialized variable size may cause loop bounds overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073852] [NEW] apparmor: access to uniniatliaed variable size may cause loop bounds overflow
Public bug reported:
Function unpack_secmark on a failed aa_unpack_array call may not set
variable size and so the fail path is executing a loop using an
undefined bounds on size.
VISIBLE_IF_KUNIT bool aa_unpack_array(struct aa_ext *e, const char *name, u16
*size)
{
void *pos = e->pos;
if (aa_unpack_nameX(e, AA_ARRAY, name)) {
if (!aa_inbounds(e, sizeof(u16)))
goto fail;
^^ *size not set
*size = le16_to_cpu(get_unaligned((__le16 *) e->pos));
e->pos += sizeof(u16);
return true;
}
fail:
e->pos = pos;
return false;
}
static bool unpack_secmark(struct aa_ext *e, struct aa_ruleset *rules)
{
void *pos = e->pos;
u16 size;
int i;
if (aa_unpack_nameX(e, AA_STRUCT, "secmark")) {
if (!aa_unpack_array(e, NULL, &size))
goto fail;
^^^ size is not set
rules->secmark = kcalloc(size, sizeof(struct aa_secmark),
GFP_KERNEL);
if (!rules->secmark)
goto fail;
rules->secmark_count = size;
for (i = 0; i < size; i++) {
if (!unpack_u8(e, &rules->secmark[i].audit, NULL))
goto fail;
if (!unpack_u8(e, &rules->secmark[i].deny, NULL))
goto fail;
if (!aa_unpack_strdup(e, &rules->secmark[i].label,
NULL))
goto fail;
}
if (!aa_unpack_nameX(e, AA_ARRAYEND, NULL))
goto fail;
if (!aa_unpack_nameX(e, AA_STRUCTEND, NULL))
goto fail;
}
return true;
fail:
if (rules->secmark) {
for (i = 0; i < size; i++)
kfree(rules->secmark[i].label);
^^ for-loop on unbounded size
kfree(rules->secmark);
rules->secmark_count = 0;
rules->secmark = NULL;
}
e->pos = pos;
return false;
}
** Affects: linux (Ubuntu)
Importance: High
Assignee: John Johansen (jjohansen)
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073852
Title:
apparmor: access to uniniatliaed variable size may cause loop bounds
overflow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073852/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056451] Re: hfs: concurrent create/unlink can trip -EEXIST on non-existent files
Any update on this? It's been 3 months.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056451 Title: hfs: concurrent create/unlink can trip -EEXIST on non-existent files To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2072443] Re: sudo doesn't work with chown in ubuntu24.04 LTS
Thank you Chris for your time and effort. I did some more digging and found that I had 2 partitions on a hard drive which shared the same 9 initial characters in their UUID. These were 01D60603D though I doubt that that matters. The bug went away when I had one of the partitions reassigned to a totally different UUID which raises the question of exactly how many characters are used of the UUID in the identification process. Have a Great Day Ian Ashworth On 2024-07-08 01:13, Chris Guiver wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Bug reporting is about finding & fixing problems thus preventing future > users from hitting the same bug. > > I suspect a Support site would be more appropriate, eg. > https://answers.launchpad.net/ubuntu. You can also find help with your > problem in the support forum of your local Ubuntu community > http://loco.ubuntu.com/ or asking at https://askubuntu.com or > https://ubuntuforums.org, or for more support options please look at > https://discourse.ubuntu.com/t/community-support/709 > > > Please note your description contradicts, ie. you state you're using both > Ubuntu 24.04 LTS and Ubuntu 20.04 LTS according to your `lsb_release` results > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072443 Title: sudo doesn't work with chown in ubuntu24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
Fair point. Where can I find the source? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072443] [NEW] sudo doesn't work with chown in ubuntu24.04 LTS
Public bug reported: I have just upgraded from Ubuntu 22.04LTS and was trying to set up my system when I came across this challenge. Used both GUI and CLI to check ownership of several files and directories. Found root as owner. Used CLI to change both group and owner separately and together. ' sudo chown -v ian:ian /media/ian/Data/tempstore/Pictures/' [sudo] password for ian: changed ownership of '/media/ian/Data/tempstore/Pictures/' from root:root to ian:ian' Unfortunately when checked no changes had taken place on the directory or any files in later attempts. I tried using libre office to change a file contents in the directory 'Pictures' and it saved the changes just fine even though I wasn't a superuser but digikam wouldn't add new files from that or any other directory - message was 'No new files to add' or similar. I would have included screen shots but couldn't get them to upload. Sorry. lsb_release -rd gives 'Description: Ubuntu 20.04 LTS Release: 24.04' This could be in one or more of several packages from low level disk handling upwards so no suspected package for bug source. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072443 Title: sudo doesn't work with chown in ubuntu24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=219007 ** Bug watch added: Linux Kernel Bug Tracker #219007 https://bugzilla.kernel.org/show_bug.cgi?id=219007 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071756 Title: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071756] Re: dev test from ubuntu_stress_smoke_tests cause VM crash with N-oem-6.10
Reproducer:
#include
#include
int main(void)
{
pid_t pid = fork();
while (1) {
int fd;
fd = openat(AT_FDCWD, "/dev/dri/card1",
O_WRONLY|O_NONBLOCK|O_SYNC);
close(fd);
}
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071756
Title:
dev test from ubuntu_stress_smoke_tests cause VM crash with
N-oem-6.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069717] [NEW] Upgrading from Ubuntu 23.10 to 24.04 fails on DisplayLink Module / evdi
Public bug reported: During upgrade using `sudo do-realease-upgrade` Upgrade failed and system became unbootable. Booting into recovery mode discovered that kernel make fails (linux- image-6.8.0-35-generic) for module evdi which is the Dell DisplayLink Driver Solution: 1) Boot into recovery mode 2) Follow these instructions to remove module evdi https://askubuntu.com/questions/1467898/dkms-errors-when-updating-upgrading-ubuntu/1468704#1468704 3) dpkg --configure -a 4) sudo apt update && sudo apt upgrade The system then recovered although the DisplayLink driver was no longer present As the Dell XPS range are officially covered laptops (not sure if by Dell or Ubuntu) I thought this may be useful to resolve Further suggestion: removing the evdi module automatically during upgrade would at least ensure this issue does not stop the upgrade completing. DisplayLink can be reinstalled by those who need it ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069717 Title: Upgrading from Ubuntu 23.10 to 24.04 fails on DisplayLink Module / evdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
Given it's a case of adding debug into the calling paths of aafs_create() and into aafs_create to see why the ptr is null I don't think finding reproducers is necessary the fast path to solving this. I suspect this is a race condition hence it's not easily reproducible in some configurations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
I disassembled the offending code, the error is in the following code: r13 is zero so the mov 0x40 is accessing data from the NULL ptr in r13 8172898f: 4d 8b 55 40 mov0x40(%r13),%r10 < here 81728993: 4d 8d ba c0 00 00 00lea0xc0(%r10),%r15 8172899a: 4c 89 55 c0 mov%r10,-0x40(%rbp) 8172899e: 4c 89 ffmov%r15,%rdi 817289a1: e8 6a d3 af 00 call 0x82225d10 <--- down_write() So looking at aafs_create() in security/apparmor/apparmorfs.c I'm presuming the dir from d_inode(parent) is null and this is tripping this issue. Would be good to get John the apparmor maintainer to look at this. Normally I'd help debug this further, but I don't know how to get access to the RT kernel source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068749] Re: modprobe of speakup modules on ARM RT kernel ends up in a lockup of module loading
Thanks for investigating this. Much appreciated \o/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068749 Title: modprobe of speakup modules on ARM RT kernel ends up in a lockup of module loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2068749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
Same issue on ARM64 with 6.8.1-1002-realtime too: stress-ng: error: [4568] klog-check: alert: [445.413206] 'Unable to handle kernel access to user memory outside uaccess routines at virtual address 0040' stress-ng: error: [4568] klog-check: alert: [445.413235] 'Mem abort info:' stress-ng: error: [4568] klog-check: alert: [445.413239] ' ESR = 0x9604' stress-ng: error: [4568] klog-check: alert: [445.413244] ' EC = 0x25: DABT (current EL), IL = 32 bits' stress-ng: error: [4568] klog-check: alert: [445.413251] ' SET = 0, FnV = 0' stress-ng: error: [4568] klog-check: alert: [445.413256] ' EA = 0, S1PTW = 0' stress-ng: error: [4568] klog-check: alert: [445.413260] ' FSC = 0x04: level 0 translation fault' stress-ng: error: [4568] klog-check: alert: [445.413265] 'Data abort info:' stress-ng: error: [4568] klog-check: alert: [445.413268] ' ISV = 0, ISS = 0x0004, ISS2 = 0x' stress-ng: error: [4568] klog-check: alert: [445.413273] ' CM = 0, WnR = 0, TnD = 0, TagAccess = 0' stress-ng: error: [4568] klog-check: alert: [445.413279] ' GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0' stress-ng: error: [4568] klog-check: alert: [445.413286] 'user pgtable: 4k pages, 48-bit VAs, pgdp=000128037000' stress-ng: error: [4568] klog-check: alert: [445.413295] '[0040] pgd=, p4d=' stress-ng: error: [4568] klog-check: emergency: [445.413316] 'Internal error: Oops: 9604 [#1] PREEMPT_RT SMP' stress-ng: info: [4568] klog-check: warning: [445.413385] 'Modules linked in: nhpoly1305_neon nhpoly1305 libpoly1305 michael_mic md4 streebog_generic rmd160 crc32_generic cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_generic cast5_generic cast_common camellia_generic blowfish_generic blowfish_common aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg tls qrtr cfg80211 binfmt_misc nls_iso8859_1 dm_multipath efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_arm64 sha1_ce arm_smccc_trng virtio_rng xhci_pci xhci_pci_renesas aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher' stress-ng: info: [4568] klog-check: warning: [445.413741] 'CPU: 18 PID: Comm: stress-ng-appar Not tainted 6.8.1-1002-realtime #2-Ubuntu' stress-ng: info: [4568] klog-check: warning: [445.413759] 'Hardware name: QEMU KVM Virtual Machine, BIOS 2023.05-2ubuntu0.1 02/12/2024' stress-ng: info: [4568] klog-check: warning: [445.413767] 'pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)' stress-ng: info: [4568] klog-check: warning: [445.413778] 'pc : aafs_create.constprop.0+0xc0/0x170' stress-ng: info: [4568] klog-check: warning: [445.413802] 'lr : aafs_create.constprop.0+0x70/0x170' stress-ng: info: [4568] klog-check: warning: [445.413811] 'sp : 800085513b10' stress-ng: info: [4568] klog-check: warning: [445.413815] 'x29: 800085513b10 x28: 14ec8bf7967c x27: ' stress-ng: info: [4568] klog-check: warning: [445.413831] 'x26: x25: 14ec804e1600 x24: ' stress-ng: info: [4568] klog-check: warning: [445.413846] 'x23: x22: x21: 41ed' stress-ng: info: [4568] klog-check: warning: [445.413860] 'x20: a043069917f8 x19: a04304f2bb98 x18: 8000840f5068' stress-ng: info: [4568] klog-check: warning: [445.413876] 'x17: x16: x15: ' stress-ng: info: [4568] klog-check: warning: [445.413890] 'x14: 0001 x13: 67652d6f69647561 x12: ' stress-ng: info: [4568] klog-check: warning: [445.413905] 'x11: x10: 8478 x9 : a04303752a9c' stress-ng: info: [4568] klog-check: warning: [445.413919] 'x8 : 8000855139c8 x7 : x6 : a04306597118' stress-ng: info: [4568] klog-check: warning: [445.413934] 'x5 : x4 : x3 : ' stress-ng: info: [4568] klog-check: warning: [445.413947] 'x2 : x1 : x0 : ' stress-ng: info: [4568] klog-check: warning: [445.413962] 'Call trace:' stress-ng: info: [4568] klog-check: warning: [445.413967] ' aafs_create.constprop.0+0xc0/0x170' stress-ng: info: [4568] klog-check: warning: [445.413977] ' __aafs_profile_mkdir+0x3a4/0x4a0' stress-ng: info: [4568] klog-check: warning: [445.413988] ' aa_replace_profiles+0x4ec/0x12c8' stress-ng: info: [4568] klog-check: warning: [445.414003] ' policy_update+0xfc/0x1c0' stress-ng: info: [4568] klog-check: warning: [445.414012] ' profile_replace+0x110/0x200' stress-ng: info: [4568] klog-check: warning: [445.
[Bug 2068615] [NEW] kernel oops in pick_next_task_fair in 6.8.1-1002-realtime kernel
Public bug reported: Ubuntu Noble, Real Time kernel: cking@noble-amd64-efi:~$ uname -a Linux noble-amd64-efi 6.8.1-1002-realtime #2-Ubuntu SMP PREEMPT_RT Tue May 21 21:13:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux How to reproduce issue: git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j 8 sudo ./stress-ng --seq 16 -t 20 --metrics --vmstat 5 -x apparmor,prio- inv --progress --pathological Note that this oops'd while executing the schedpolicy stressor, but just running this stressor by itself doesn't seem to trigger the oops per se, so it may be something to do with stressors being run prior to the schedpolicy stressor. ... stress-ng: info: [8315] starting schedpolicy, 224 of 330 (67.88%), 16 instances, finish at 13:11:48 2024-06-06 stress-ng: info: [8318] vmstat: 16 0 70076 3422692158820 16725640 17 0 65858 266843 34 57 9 0 0 [ 4943.415061] BUG: kernel NULL pointer dereference, address: 00a0 [ 4943.415069] #PF: supervisor read access in kernel mode [ 4943.415071] #PF: error_code(0x) - not-present page [ 4943.415072] PGD 0 P4D 0 [ 4943.415075] Oops: [#1] PREEMPT_RT SMP PTI [ 4943.415079] CPU: 4 PID: 690936 Comm: kworker/u33:4 Not tainted 6.8.1-1002-realtime #2-Ubuntu [ 4943.415083] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2024.02-2 03/11/2024 [ 4943.415085] Workqueue: 0x0 (ttm) [ 4943.415158] RIP: 0010:pick_next_task_fair+0x91/0x630 [ 4943.415165] Code: 93 00 00 00 49 81 bd b0 02 00 00 00 d3 8e bd 75 62 4d 89 fe eb 27 4c 89 f7 e8 3b bf ff ff 84 c0 75 41 4c 89 f7 e8 8f 3e ff ff <4c> 8b b0 a0 00 00 00 48 89 c3 4d 85 f6 0f 84 fe 00 00 00 49 8b 46 [ 4943.415168] RSP: :a2ccc8fcfd38 EFLAGS: 00010046 [ 4943.415172] RAX: RBX: a2ccc8fcfe10 RCX: [ 4943.415173] RDX: RSI: RDI: [ 4943.415175] RBP: a2ccc8fcfd78 R08: R09: [ 4943.415177] R10: R11: R12: 9395fbc35300 [ 4943.415178] R13: 93958e0c5200 R14: 9395fbc35400 R15: 9395fbc35400 [ 4943.415181] FS: () GS:9395fbc0() knlGS: [ 4943.415183] CS: 0010 DS: ES: CR0: 80050033 [ 4943.415185] CR2: 00a0 CR3: 00014b696006 CR4: 00370ef0 [ 4943.415192] Call Trace: [ 4943.415194] [ 4943.415196] ? show_regs+0x6d/0x80 [ 4943.415201] ? __die+0x24/0x80 [ 4943.415204] ? page_fault_oops+0x99/0x1c0 [ 4943.415210] ? do_user_addr_fault+0x2ed/0x6b0 [ 4943.415214] ? exc_page_fault+0x83/0x1b0 [ 4943.415218] ? asm_exc_page_fault+0x27/0x30 [ 4943.415225] ? pick_next_task_fair+0x91/0x630 [ 4943.415230] ? pick_next_task_fair+0x91/0x630 [ 4943.415235] pick_next_task+0x5f/0xce0 [ 4943.415242] __schedule+0x124/0x6f0 [ 4943.415246] ? trace_preempt_off+0x1a/0x70 [ 4943.415250] ? process_one_work+0x1a1/0x350 [ 4943.415256] schedule+0x38/0x120 [ 4943.415260] worker_thread+0x1d6/0x440 [ 4943.415265] ? __pfx_worker_thread+0x10/0x10 [ 4943.415269] kthread+0xfe/0x130 [ 4943.415273] ? __pfx_kthread+0x10/0x10 [ 4943.415276] ret_from_fork+0x44/0x70 [ 4943.415280] ? __pfx_kthread+0x10/0x10 [ 4943.415283] ret_from_fork_asm+0x1b/0x30 [ 4943.415290] [ 4943.415291] Modules linked in: snd_seq_dummy tls cuse uhid snd_seq snd_seq_device userio hci_vhci bluetooth ecdh_generic ecc vfio_iommu_type1 vfio iommufd nvram vhost_vsock vmw_vsock_virtio_transport_common vsock vhost_net vhost vhost_iotlb tap dccp_ipv4 dccp atm pcbc lrw chacha_generic chacha_x86_64 libchacha xxhash_generic xcbc wp512 vmac sm3_generic sm3_avx_x86_64 sm3 poly1305_generic poly1305_x86_64 nhpoly1305_avx2 nhpoly1305_sse2 nhpoly1305 libpoly1305 michael_mic md4 streebog_generic rmd160 cmac algif_rng twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic fcrypt cast6_avx_x86_64 cast6_generic cast5_avx_x86_64 cast5_generic cast_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 blowfish_generic blowfish_x86_64 blowfish_common algif_skcipher algif_hash aria_aesni_avx2_x86_64 aria_aesni_avx_x86_64 aria_generic sm4_generic sm4_aesni_avx2_x86_64 sm4_aesni_avx_x86_64 sm4 ccm [ 4943.415418] des3_ede_x86_64 des_generic libdes authenc aegis128 aegis128_aesni algif_aead af_alg qrtr cfg80211 binfmt_misc intel_rapl_msr intel_rapl_common intel_pmc_core intel_vsec pmt_telemetry pmt_class nls_iso8859_1 kvm_intel kvm irqbypass rapl snd_hda_codec_generic i2c_i801 i2c_smbus snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec lpc_ich snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore joydev qxl drm_ttm_helper ttm input_leds mac_hid serio_raw dm_multipath msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel
** Summary changed: - kernel oops in aafs_create in 6.8.1-1002-realtime + kernel oops in aafs_create in 6.8.1-1002-realtime kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime
** Package changed: qemu (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068602 Title: kernel oops in aafs_create in 6.8.1-1002-realtime kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068602] [NEW] kernel oops in aafs_create in 6.8.1-1002-realtime
Public bug reported: Ubuntu Noble, Real Time kernel: cking@noble-amd64-efi:~$ uname -a Linux noble-amd64-efi 6.8.1-1002-realtime #2-Ubuntu SMP PREEMPT_RT Tue May 21 21:13:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux How to reproduce issue: git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j 8 sudo ./stress-ng --apparmor 8 --vmstat 1 after a while I observed the kernel oops splat message: [ 131.881354] AppArmor DFA next/check upper bounds error [ 131.993510] BUG: kernel NULL pointer dereference, address: 0040 [ 131.993512] #PF: supervisor read access in kernel mode [ 131.993513] #PF: error_code(0x) - not-present page [ 131.993514] PGD 0 P4D 0 [ 131.993516] Oops: [#1] PREEMPT_RT SMP PTI [ 131.993518] CPU: 1 PID: 2357 Comm: stress-ng-appar Not tainted 6.8.1-1002-realtime #2-Ubuntu [ 131.993521] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2024.02-2 03/11/2024 [ 131.993522] RIP: 0010:aafs_create.constprop.0+0x7f/0x130 [ 131.993532] Code: 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 c3 cc cc cc cc <4d> 8b 55 40 4d 8d ba c0 00 00 00 4c 89 55 c0 4c 89 ff e8 6a d3 af [ 131.993533] RSP: 0018:b589810efbe8 EFLAGS: 00010246 [ 131.993535] RAX: RBX: 41ed RCX: [ 131.993536] RDX: RSI: RDI: [ 131.993537] RBP: b589810efc28 R08: R09: [ 131.993538] R10: 8bf44a786040 R11: R12: a9babb88 [ 131.993539] R13: R14: R15: [ 131.993540] FS: 7ed4e777cf40() GS:8bf4bba8() knlGS: [ 131.993541] CS: 0010 DS: ES: CR0: 80050033 [ 131.993542] CR2: 0040 CR3: 0001093ba004 CR4: 00370ef0 [ 131.993546] DR0: DR1: DR2: [ 131.993547] DR3: DR6: fffe0ff0 DR7: 0400 [ 131.993548] Call Trace: [ 131.993549] [ 131.993551] ? show_regs+0x6d/0x80 [ 131.993567] ? __die+0x24/0x80 [ 131.993569] ? page_fault_oops+0x99/0x1c0 [ 131.993572] ? do_user_addr_fault+0x2ed/0x6b0 [ 131.993575] ? exc_page_fault+0x83/0x1b0 [ 131.993577] ? asm_exc_page_fault+0x27/0x30 [ 131.993582] ? aafs_create.constprop.0+0x7f/0x130 [ 131.993584] ? aafs_create.constprop.0+0x51/0x130 [ 131.993587] __aafs_profile_mkdir+0x3d6/0x480 [ 131.993589] aa_replace_profiles+0x83f/0x1270 [ 131.993606] policy_update+0xe3/0x180 [ 131.993608] profile_replace+0xbc/0x150 [ 131.993610] ? preempt_count_sub+0xc8/0x110 [ 131.993612] vfs_write+0xff/0x4a0 [ 131.993629] ? putname+0x5b/0x80 [ 131.993632] ksys_write+0x73/0x100 [ 131.993634] __x64_sys_write+0x19/0x30 [ 131.993636] x64_sys_call+0x7e/0x25c0 [ 131.993638] do_syscall_64+0x81/0x190 [ 131.993641] ? do_syscall_64+0x8e/0x190 [ 131.993643] ? debug_smp_processor_id+0x17/0x30 [ 131.993645] ? fpregs_assert_state_consistent+0x30/0x60 [ 131.993648] ? syscall_exit_to_user_mode+0x86/0x260 [ 131.993650] ? do_syscall_64+0x8e/0x190 [ 131.993652] ? do_syscall_64+0x8e/0x190 [ 131.993654] ? do_syscall_64+0x8e/0x190 [ 131.993656] ? do_syscall_64+0x8e/0x190 [ 131.993658] ? irqentry_exit+0x43/0x50 [ 131.993660] entry_SYSCALL_64_after_hwframe+0x78/0x80 [ 131.993661] RIP: 0033:0x7ed4e8041574 [ 131.993674] Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d d5 ea 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89 [ 131.993676] RSP: 002b:7fff57a26798 EFLAGS: 0202 ORIG_RAX: 0001 [ 131.993677] RAX: ffda RBX: 592cb9ed38f0 RCX: 7ed4e8041574 [ 131.993678] RDX: 0001916a RSI: 592cb9ed96d0 RDI: 0007 [ 131.993679] RBP: 7fff57a267f0 R08: 592cb9eb1010 R09: 0007 [ 131.993680] R10: R11: 0202 R12: 0001916a [ 131.993681] R13: 592cb9ed96d0 R14: 592cb9ed96d0 R15: 0003 [ 131.993684] [ 131.993685] Modules linked in: pcbc lrw chacha_generic chacha_x86_64 libchacha xxhash_generic xcbc wp512 vmac sm3_generic sm3_avx_x86_64 sm3 poly1305_generic poly1305_x86_64 nhpoly1305_avx2 nhpoly1305_sse2 nhpoly1305 libpoly1305 michael_mic md4 streebog_generic rmd160 cmac algif_rng twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic fcrypt cast6_avx_x86_64 cast6_generic cast5_avx_x86_64 cast5_generic cast_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 blowfish_generic blowfish_x86_64 blowfish_common algif_skcipher algif_hash aria_aesni_avx2_x86_64 aria_aesni_avx_x86_64 aria_generic sm4_generic sm4_aesni_avx2_x86_64 sm4_aesni_av
[Bug 2065794] [NEW] Crash on initial setup during keyboard configuration
Public bug reported: This was installing Ubuntu 24.04 LTS on a Raspberry Pi 5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubiquity 24.04.5 ProcVersionSignature: Ubuntu 6.8.0-1004.4-raspi 6.8.1 Uname: Linux 6.8.0-1004-raspi aarch64 ApportVersion: 2.28.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed May 15 16:26:06 2024 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug arm64 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065794 Title: Crash on initial setup during keyboard configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1984203] Re: /var/run/reboot-required not created after installing new kernel
Ah, yes, it is. https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1998947 https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401 The system knows when a reboot is required in those fraction of cases when it is despite having livepatch enabled. A message dialogue pops up during an apt-get / aptitude upgrade to recommend one at those times and motd is also said to mention that one is required when it is. Why can the reboot-required file not be created as well in those cases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1984203] Re: /var/run/reboot-required not created after installing new kernel
I have this issue on one 22.04 server. Several other 22.04 servers are completely fine. On the one where it isn't, auditd confirms the file is simply never created during the update process. update-notifier-common is installed on all of them. Looking to see what the differences between the servers are, I do note this is the only one to have Ubuntu Advantage enabled: # pro status SERVICE ENTITLED STATUS DESCRIPTION anbox-cloud yes disabled Scalable Android in the cloud esm-apps yes enabled Expanded Security Maintenance for Applications esm-infrayes enabled Expanded Security Maintenance for Infrastructure livepatchyes enabled Canonical Livepatch service realtime-kernel yes disabled Ubuntu kernel with PREEMPT_RT patches integrated This makes me wonder if something related to livepatch is going 'Ha, you don't need to reboot' even when you do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1984203 Title: /var/run/reboot-required not created after installing new kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064509] Re: Fossil regression due CVE-2024-24795
Xenial and Bionic also addressed through ESM: Ubuntu 18.04 LTS fossil 1:2.5-1ubuntu0.1~ Ubuntu 16.04 LTS fossil 1:1.33-3ubuntu0.1~esm1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064509 Title: Fossil regression due CVE-2024-24795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fossil/+bug/2064509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064509] Re: Fossil regression due CVE-2024-24795
USN for reference: https://ubuntu.com/security/notices/USN-6770-1 ** Changed in: fossil (Ubuntu Bionic) Status: New => Fix Released ** Changed in: fossil (Ubuntu Xenial) Status: New => Fix Released ** Changed in: fossil (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064509 Title: Fossil regression due CVE-2024-24795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fossil/+bug/2064509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064509] Re: Fossil regression due CVE-2024-24795
Fix commit: https://fossil-scm.org/home/info/a8e33fb161f45b65 (For this issue, a subset of the changes to src/http.c are the fix) Followed by: https://fossil-scm.org/home/info/71919ad1b542832c and https://fossil-scm.org/home/info/f4ffefe708793b03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064509 Title: Fossil regression due CVE-2024-24795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fossil/+bug/2064509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064509] Re: Fossil regression due CVE-2024-24795
Workaround note: Fossil CGI documentation adds config option to restore legacy behavior in Apache: https://fossil-scm.org/home/doc/trunk/www/server/any/cgi.md ** Also affects: fossil (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: fossil (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: fossil (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fossil (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fossil (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fossil (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064509 Title: Fossil regression due CVE-2024-24795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fossil/+bug/2064509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064549] Re: pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-6.5 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-nvidia-6.5 (Ubuntu Noble)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064549
Title:
pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin
permission before access.")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2064549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] Re: backport arm64 THP improvements from 6.9
** Also affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-nvidia (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
This issue looks to be related to kernel configuration. Using upstream stable 6.8.1 which is what the current noble being tested is rebased on. Using 'make defconfig' the nvidia module loads successfully. But with same kernel using noble config, the nvidia module experiences the same hang as with noble kernel. I'm currently working through config comparison and testing changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062380 Title: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2062380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
** Summary changed: - Using a 6.8 kernel modprobe nvidia hangs on Grace Hopper + Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu) Status: New => Confirmed ** Description changed: Using both -generic and -nvidia 6.8 kernels I'm seeing a hang when I load the nvidia driver. + + $ sudo dmidecode -t 0 + # dmidecode 3.5 + Getting SMBIOS data from sysfs. + SMBIOS 3.6.0 present. + # SMBIOS implementations newer than version 3.5.0 are not + # fully supported by this version of dmidecode. + + Handle 0x0001, DMI type 0, 26 bytes + BIOS Information + Vendor: NVIDIA + Version: 01.02.01 + Release Date: 20240207 + ROM Size: 64 MB + Characteristics: + PCI is supported + PNP is supported + BIOS is upgradeable + BIOS shadowing is allowed + Boot from CD is supported + Selectable boot is supported + Serial services are supported (int 14h) + ACPI is supported + Targeted content distribution is supported + UEFI is supported + Firmware Revision: 0.0 [ 382.938326] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 382.946075] rcu: 53-...0: (4 ticks this GP) idle=1c2c/1/0x4000 softirq=4866/4868 fqs=14124 [ 382.955683] rcu: hardirqs softirqs csw/system [ 382.961378] rcu: number:0 00 [ 382.967071] rcu: cputime:0 00 ==> 30026(ms) [ 382.974189] rcu: (detected by 52, t=60034 jiffies, g=24469, q=1199 ncpus=72) [ 392.982095] rcu: rcu_preempt kthread starved for 9994 jiffies! g24469 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 392.992769] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior - After seeing this, I Enabled kdump and set kernel.panic_on_rcu_stall = 1 KDUMP INFO WARNING: cpu 54: cannot find NT_PRSTATUS note - KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] - DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] - CPUS: 72 - DATE: Wed Apr 17 21:39:13 UTC 2024 - UPTIME: 00:06:10 + KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] + DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] + CPUS: 72 + DATE: Wed Apr 17 21:39:13 UTC 2024 + UPTIME: 00:06:10 LOAD AVERAGE: 0.68, 0.63, 0.28 -TASKS: 854 - NODENAME: hinyari - RELEASE: 6.8.0-1005-nvidia-64k - VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 - MACHINE: aarch64 (unknown Mhz) - MEMORY: 479.7 GB -PANIC: "Kernel panic - not syncing: RCU Stall" - PID: 0 - COMMAND: "swapper/21" - TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] - CPU: 21 -STATE: TASK_RUNNING (PANIC) + TASKS: 854 + NODENAME: hinyari + RELEASE: 6.8.0-1005-nvidia-64k + VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 + MACHINE: aarch64 (unknown Mhz) + MEMORY: 479.7 GB + PANIC: "Kernel panic - not syncing: RCU Stall" + PID: 0 + COMMAND: "swapper/21" + TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] + CPU: 21 + STATE: TASK_RUNNING (PANIC) [ 300.313144] nvidia: loading out-of-tree module taints kernel. [ 300.313153] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 300.316694] nvidia-nvlink: Nvlink Core is being initialized, major device number 506 - [ 300.316699] + [ 300.316699] [ 360.323454] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 360.331206] rcu: 54-...0: (24 ticks this GP) idle=742c/1/0x4000 softirq=4931/4933 fqs=13148 [ 360.340903] rcu: hardirqs softirqs csw/system [ 360.346597] rcu: number:0 00 [ 360.352291] rcu: cputime:0 00 ==> 30031(ms) [ 360.359408] rcu: (detected by 21, t=60038 jiffies, g=25009, q=1123 ncpus=72) [ 360.366704] Sending NMI from CPU 21 to CPUs 54: [ 370.367310] rcu: rcu_preempt kthread starved for 9993 jiffies! g25009 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 370.377983] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 370.387322] rcu: RCU grace-period kthread stack dump: [ 370.392482] task:rcu_preempt state:I stack:0 pid:17tgid:17 ppid:2 flags:0x0008 [ 370.392488] Call trace: [
[Bug 2062380] [NEW] Using a 6.8 kernel modprobe nvidia hangs on Grace Hopper
Public bug reported: Using both -generic and -nvidia 6.8 kernels I'm seeing a hang when I load the nvidia driver. [ 382.938326] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 382.946075] rcu: 53-...0: (4 ticks this GP) idle=1c2c/1/0x4000 softirq=4866/4868 fqs=14124 [ 382.955683] rcu: hardirqs softirqs csw/system [ 382.961378] rcu: number:0 00 [ 382.967071] rcu: cputime:0 00 ==> 30026(ms) [ 382.974189] rcu: (detected by 52, t=60034 jiffies, g=24469, q=1199 ncpus=72) [ 392.982095] rcu: rcu_preempt kthread starved for 9994 jiffies! g24469 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 392.992769] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior After seeing this, I Enabled kdump and set kernel.panic_on_rcu_stall = 1 KDUMP INFO WARNING: cpu 54: cannot find NT_PRSTATUS note KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] CPUS: 72 DATE: Wed Apr 17 21:39:13 UTC 2024 UPTIME: 00:06:10 LOAD AVERAGE: 0.68, 0.63, 0.28 TASKS: 854 NODENAME: hinyari RELEASE: 6.8.0-1005-nvidia-64k VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 MACHINE: aarch64 (unknown Mhz) MEMORY: 479.7 GB PANIC: "Kernel panic - not syncing: RCU Stall" PID: 0 COMMAND: "swapper/21" TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] CPU: 21 STATE: TASK_RUNNING (PANIC) [ 300.313144] nvidia: loading out-of-tree module taints kernel. [ 300.313153] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 300.316694] nvidia-nvlink: Nvlink Core is being initialized, major device number 506 [ 300.316699] [ 360.323454] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 360.331206] rcu: 54-...0: (24 ticks this GP) idle=742c/1/0x4000 softirq=4931/4933 fqs=13148 [ 360.340903] rcu: hardirqs softirqs csw/system [ 360.346597] rcu: number:0 00 [ 360.352291] rcu: cputime:0 00 ==> 30031(ms) [ 360.359408] rcu: (detected by 21, t=60038 jiffies, g=25009, q=1123 ncpus=72) [ 360.366704] Sending NMI from CPU 21 to CPUs 54: [ 370.367310] rcu: rcu_preempt kthread starved for 9993 jiffies! g25009 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 370.377983] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 370.387322] rcu: RCU grace-period kthread stack dump: [ 370.392482] task:rcu_preempt state:I stack:0 pid:17tgid:17 ppid:2 flags:0x0008 [ 370.392488] Call trace: [ 370.392489] __switch_to+0xd0/0x118 [ 370.392499] __schedule+0x2a8/0x7b0 [ 370.392501] schedule+0x40/0x168 [ 370.392502] schedule_timeout+0xac/0x1e0 [ 370.392505] rcu_gp_fqs_loop+0x128/0x508 [ 370.392512] rcu_gp_kthread+0x150/0x188 [ 370.392514] kthread+0xf8/0x110 [ 370.392519] ret_from_fork+0x10/0x20 [ 370.392524] rcu: Stack dump where RCU GP kthread last ran: [ 370.398128] Sending NMI from CPU 21 to CPUs 31: [ 370.398131] NMI backtrace for cpu 31 [ 370.398136] CPU: 31 PID: 0 Comm: swapper/31 Kdump: loaded Tainted: G OE 6.8.0-1005-nvidia-64k #5-Ubuntu [ 370.398139] Hardware name: /P3880, BIOS 01.02.01 20240207 [ 370.398140] pstate: 6349 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 370.398142] pc : cpuidle_enter_state+0xd8/0x790 [ 370.398150] lr : cpuidle_enter_state+0xcc/0x790 [ 370.398153] sp : 800081eefd70 [ 370.398154] x29: 800081eefd70 x28: x27: [ 370.398157] x26: x25: 00563d67e4e0 x24: [ 370.398160] x23: a0a1445699f8 x22: x21: 00563d72ece0 [ 370.398162] x20: a0a144569a10 x19: 8fa4a800 x18: 800081f00030 [ 370.398165] x17: x16: x15: ac8c73b08db0 [ 370.398168] x14: x13: x12: [ 370.398170] x11: x10: 2da0fbe3d5e8c649 x9 : a0a1424fd244 [ 370.398173] x8 : 820559b8 x7 : x6 : [ 370.398175] x5 : x4 : x3 : [ 370.398178] x2 : x1 : x0 : [ 370.398181] Call trace: [ 370.398183] cpuidle_enter_state+0xd8/0x790 [ 370.398185] cpuidle_enter+0x44/0x78 [ 370.398195] cpuidle_idle_call+0x15c/0x210 [ 370.398202] do_idle+0xb0/0x130 [ 370.398204] cpu_startup_entry+0x40/0x50 [ 370.398206] secondary_start_kernel+0xec/0x130 [ 370.398211] __secondary_switched+0xc0/0xc8 [ 370.399132] Kernel panic - not syncing: RCU Stall [ 370.403938] CPU: 21 PID: 0 Comm:
[Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg
After kernel + x.org updates this week, firefox is now displaying properly using xserver-xorg on the Athlon 200GE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055712] Re: Pull-request to address bug in mm/page_alloc.c
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055712 Title: Pull-request to address bug in mm/page_alloc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055712] Re: Pull-request to address bug in mm/page_alloc.c
** Changed in: linux-nvidia-6.5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055712 Title: Pull-request to address bug in mm/page_alloc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I am seeing similar interactivity issues on fully updated 22.04 on a Dell Precision laptop with Nvidia + X11 that started a day or so ago. Most noticeable in the terminal with lag/stuttering and seemingly lost keyboard inputs, but also affecting other apps with stuttering keyboard inputs and sometimes seemingly lost mouse clicks. I will try downgrading mutter and suggested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059150] Re: jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper
Upgrading bios firmware resolves failure $ sudo dmidecode -t 0 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.6.0 present. # SMBIOS implementations newer than version 3.5.0 are not # fully supported by this version of dmidecode. Handle 0x0001, DMI type 0, 26 bytes BIOS Information Vendor: NVIDIA Version: 01.02.01 Release Date: 20240207 ROM Size: 64 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported Serial services are supported (int 14h) ACPI is supported Targeted content distribution is supported UEFI is supported Firmware Revision: 0.0 ** Changed in: linux-nvidia-6.5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059150 Title: jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059150] [NEW] jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper
Public bug reported: Output from BMC SOL console: Unhandled Exception from EL2 x0 = 0x11f210305619 x1 = 0x x2 = 0x x3 = 0x x4 = 0x5f972493 x5 = 0x x6 = 0x x7 = 0x x8 = 0x x9 = 0xa0e0a03e7d6c x10= 0x x11= 0x x12= 0x x13= 0x x14= 0x x15= 0x x16= 0x x17= 0x x18= 0x x19= 0xf0f18080 x20= 0x80009e86f6a0 x21= 0x80009e86f720 x22= 0x07a5a0e0a03e7d6c x23= 0x x24= 0xa0e0a3348aa0 x25= 0xa0e0a2990008 x26= 0xa0e0a2990008 x27= 0xa0e04b4f5748 x28= 0x80009e86f710 x29= 0x80008000fe00 x30= 0xa0e0a03e7d6c scr_el3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x02c0 mair_el3 = 0x004404ff spsr_el3 = 0x034000c9 elr_el3= 0xa0e04b4f58b4 ttbr0_el3 = 0x0078734a5001 esr_el3= 0x622c5c1f far_el3= 0x9446dd42099e8148 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x spsr_und = 0x spsr_irq = 0x spsr_fiq = 0x sctlr_el1 = 0x30d00980 actlr_el1 = 0x cpacr_el1 = 0x0030 csselr_el1 = 0x0002 sp_el1 = 0x esr_el1= 0x ttbr0_el1 = 0x ttbr1_el1 = 0x mair_el1 = 0x amair_el1 = 0x tcr_el1= 0x tpidr_el1 = 0x tpidr_el0 = 0x8000 tpidrro_el0= 0x par_el1= 0x0800 mpidr_el1 = 0x8102 afsr0_el1 = 0x afsr1_el1 = 0x contextidr_el1 = 0x vbar_el1 = 0x cntp_ctl_el0 = 0x cntp_cval_el0 = 0x0012ec91c420 cntv_ctl_el0 = 0x cntv_cval_el0 = 0x cntkctl_el1= 0x sp_el0 = 0x0078732cf4f0 isr_el1= 0x0040 cpuectlr_el1 = 0x4000340340003000 gicd_ispendr regs (Offsets 0x200 - 0x278) Offset:value 0200: 0xUnhandled Exception in EL3. x30= 0x0078732c4384 x0 = 0x x1 = 0x0078732cb7d8 x2 = 0x0018 x3 = 0x0078732b1720 x4 = 0x x5 = 0x003c x6 = 0x0078732c9109 x7 = 0x22000204 x8 = 0x4000340340003000 x9 = 0x x10= 0x x11= 0x0012ec91c420 x12= 0x x13= 0x x14= 0x x15= 0x0078732cf4f0 x16= 0x2200 x17= 0x0018 x18= 0x0407073d x19= 0x007873386440 x20= 0x80009e86f6a0 x21= 0x80009e86f720 x22= 0x07a5a0e0a03e7d6c x23= 0x x24= 0xa0e0a3348aa0 x25= 0xa0e0a2990008 x26= 0xa0e0a2990008 x27= 0xa0e04b4f5748 x28= 0x80009e86f710 x29= 0x80008000fe00 scr_el3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x03c0 mair_el3 = 0x004404ff spsr_el3 = 0x834002cd elr_el3= 0x0078732b0af4 ttbr0_el3 = 0x0078734a5001 esr_el3= 0xbe11 far_el3= 0x9446dd42099e8148 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x spsr_und = 0x spsr_irq = 0x spsr_fiq = 0x sctlr_el1 = 0x30d00980 actlr_el1 = 0x cpacr_el1 = 0x0030 csselr_el1 = 0x0002 sp_el1 = 0x esr_el1= 0x ttbr0_el1 = 0x ttbr1_el1 = 0x mair_el1 = 0x0
Re: [Bug 2058634] Re: scribus-doc puts docs in wrong place
Hi Mattia, On Sat, 23 Mar 2024 at 21:30, Mattia Rizzolo <2058...@bugs.launchpad.net> wrote: > I see what's happening there... That's due to snap's containerization > efforts, which blocks loading of files from /usr/share/scribus. If you use > any other non-snap browser it should just work. > > > I don't use snaps, no, so I'm having no good ideas on how to fix that. And > ISTR I had a good reason to have the symlinks that way instead of > installing in usr/share/doc amd symlinking on usr/share/scribus, but i > could always try again, as that's likely the easier workaround to those > blocks. > You might want to contact Oliver Grawert (o...@ubuntu.com) as he diagnosed the snap issue. He might be able to give you some ideas. BW, Ian -- -- ACCU - Professionalism in programming - http://www.accu.org -- My writing - https://sites.google.com/site/ianbruntlett/ -- Free Software page - https://github.com/ian-bruntlett/TECH-Manuals/blob/main/tm-free-software.md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058634 Title: scribus-doc puts docs in wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus-doc/+bug/2058634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058634] Re: scribus-doc puts docs in wrong place
Hi Mattia, On Sat, 23 Mar 2024 at 20:30, Mattia Rizzolo <2058...@bugs.launchpad.net> wrote: > You are right that scribus needs them in what is the "wrong" location > for the Debian policy, but I remember doing things so that it would work > for both. > > The package ships everything in /usr/share/scribus/doc and then sets up > symlinks from e.g. /usr/share/doc/scribus/de to ../../scribus/doc/de > (i.e. /usr/share/scribus/doc/de). > > What is not working for you? > Well, Firefox (as a snap), for some reason or another, can't access the files. /usr/share/doc/scribus/en$ xdg-open index.html Yields this error page in Firefox: *File not foundFirefox can’t find the file at /usr/share/doc/scribus/en/index.html.Check the file name for capitalisation or other typing errors.Check to see if the file was moved, renamed or deleted.* /usr/share/scribus/doc/en$ xdg-open index.html Yields this error page in Firefox: *File not foundFirefox can’t find the file at /usr/share/scribus/doc/en/index.html.Check the file name for capitalisation or other typing errors.Check to see if the file was moved, renamed or deleted.* Is it possible that the snap system does not like the symlink approach? Do you have Firefox installed as a snap? Do you have scribus-doc installed? That way, you should be able to experience this problem, too. BW, Ian -- -- ACCU - Professionalism in programming - http://www.accu.org -- My writing - https://sites.google.com/site/ianbruntlett/ -- Free Software page - https://github.com/ian-bruntlett/TECH-Manuals/blob/main/tm-free-software.md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058634 Title: scribus-doc puts docs in wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus-doc/+bug/2058634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058634] [NEW] scribus-doc puts docs in wrong place
Public bug reported: the issue is that scribus does not use a standard location for its docs ... typically deb packages ship their docs in /usr/share/doc/ while scribus ships them in /usr/share//doc ... This is important because the Firefox snap only has permissions to access files in the standard location. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: scribus 1.5.8+dfsg-2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 10:32:17 2024 InstallationDate: Installed on 2020-08-07 (1321 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: scribus UpgradeStatus: Upgraded to jammy on 2022-08-15 (584 days ago) ** Affects: scribus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058634 Title: scribus-doc puts docs in wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/2058634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056448] Re: hfs: weird file system free block state after creating files and removing them with a mix of i/o operations
** Summary changed: - weird file system free block state after creating files and removing them with a mix of i/o operations + hfs: weird file system free block state after creating files and removing them with a mix of i/o operations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056448 Title: hfs: weird file system free block state after creating files and removing them with a mix of i/o operations To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056448] Re: weird file system free block state after creating files and removing them with a mix of i/o operations
** Bug watch added: Linux Kernel Bug Tracker #218571 https://bugzilla.kernel.org/show_bug.cgi?id=218571 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=218571 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056448 Title: weird file system free block state after creating files and removing them with a mix of i/o operations To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056451] [NEW] hfs: concurrent create/unlink can trip -EEXIST on non-existent files
Public bug reported: Summary: create hfs file system, loop-back mount it, run filename stressor with stress-ng to exercise filename create/stat/unlink and we get unexpected -EEXIST errors. This can be worked around by adding a sync() call after the unlink() to ensure metadata is sync'd. Kernel: 6.8.0-11-generic test case: sudo apt-get install hfsprogs dd if=/dev/zero of=fs.img bs=1M count=2048 mkfs.hfs fs.img sudo mount fs.img /mnt sudo mkdir /mnt/x sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132412] setting to a 20 secs run per stressor stress-ng: info: [132412] dispatching hogs: 8 filename stress-ng: fail: [132424] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 20 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132421] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 23 bytes, errno=17 (File exists) stress-ng: fail: [132425] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 7 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 11 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 24 bytes, errno=17 (File exists) adding a sync() call in the stress-ng stressor fixes the issue: git diff diff --git a/stress-filename.c b/stress-filename.c index a64898fb1..b8266f91e 100644 --- a/stress-filename.c +++ b/stress-filename.c @@ -308,6 +308,7 @@ static void stress_filename_test( VOID_RET(int, shim_stat(filename, &buf)); (void)shim_unlink(filename); + (void)sync(); } /* exercise dcache lookup of non-existent filename */ sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132461] setting to a 20 secs run per stressor stress-ng: info: [132461] dispatching hogs: 8 filename stress-ng: info: [132461] skipped: 0 stress-ng: info: [132461] passed: 8: filename (8) stress-ng: info: [132461] failed: 0 stress-ng: info: [132461] metrics untrustworthy: 0 stress-ng: info: [132461] successful run completed in 20.05 secs The sync should not be required by the way, I just added it to illustrate that there is a racy metadata sync issue in hfs. ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - hfs: concurrent create/unlink can trip -EEXIST on files + hfs: concurrent create/unlink can trip -EEXIST on non-existent files ** Bug watch added: Linux Kernel Bug Tracker #218570 https://bugzilla.kernel.org/show_bug.cgi?id=218570 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=218570 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056451 Title: hfs: concurrent create/unlink can trip -EEXIST on non-existent files To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056448] [NEW] weird file system free block state after creating files and removing them with a mix of i/o operations
Public bug reported: Summary: create hfs file system, loop-back mount it, run iomix stessor with stress-ng to exercise with a mix of file I/O operations and remove files at end. File system is empty but a lot of blocks are used and can't seem to be recovered. Kernel: 6.8.0-11-generic test case: sudo apt-get install hfsprogs dd if=/dev/zero of=fs.img bs=1M count=2048 mkfs.hfs fs.img sudo mount fs.img /mnt sudo mkdir /mnt/x df /mnt Filesystem 1K-blocks Used Available Use% Mounted on /dev/loop6 2097128 2015 2095113 1% /mnt sudo stress-ng --temp-path /mnt/x --iomix 1 -t 2 df /mnt Filesystem 1K-blocks Used Available Use% Mounted on /dev/loop6 2097128 674635 1422493 33% /mnt ls -alR /mnt/ /mnt/: total 4 drwxr-xr-x 1 root root3 Mar 7 12:37 . drwxr-xr-x 23 root root 4096 Feb 28 14:13 .. drwxr-xr-x 1 root root2 Mar 7 12:37 x /mnt/x: total 0 drwxr-xr-x 1 root root 2 Mar 7 12:37 . drwxr-xr-x 1 root root 3 Mar 7 12:37 .. ..so file system is 33% full, but no files are on the file system. Something looks wrong here. ** Affects: linux (Ubuntu) Importance: High Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056448 Title: weird file system free block state after creating files and removing them with a mix of i/o operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg
Similar hardware: R7 240 graphics card (previous generation graphics cores) on Athlon 200GE: everything works fine on X11 Plugged SSD from Athlon install into 5600G (Vega 6 graphics instead of Vega 3): everything works fine on X11. So it seems to be something weird about Vega 3 graphics in relation to amdgpu & xserver-xorg-video-amdgpu. I don't speak Git, but I am happy to download, compile, and test anything you would like me to if you don't have access to matching hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/2055351/+attachment/5753661/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2055351/+attachment/5753660/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2055351/+attachment/5753652/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/2055351/+attachment/5753659/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055351] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2055351/+attachment/5753653/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
