[Kernel-packages] [Bug 2051700] Re: Missing fuse backport: "fuse: add feature flag for expire-only"
This is a back port of the patch to hwe-6.2-next, conflicts had been in
the section below, as 6.2 does not have FUSE_CREATE_SUPP_GROUP
Initial patch for 6.5
```
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index d66070af145d0..660be31aaabc2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1254,7 +1254,8 @@ void fuse_send_init(struct fuse_mount *fm)
FUSE_ABORT_ERROR | FUSE_MAX_PAGES | FUSE_CACHE_SYMLINKS |
FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA |
FUSE_HANDLE_KILLPRIV_V2 | FUSE_SETXATTR_EXT | FUSE_INIT_EXT |
- FUSE_SECURITY_CTX | FUSE_CREATE_SUPP_GROUP;
+ FUSE_SECURITY_CTX | FUSE_CREATE_SUPP_GROUP |
+ FUSE_HAS_EXPIRE_ONLY;
```
Back ported version:
```
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 06876afe5ae46..a86270fa2bf5f 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1255,7 +1255,7 @@ void fuse_send_init(struct fuse_mount *fm)
FUSE_ABORT_ERROR | FUSE_MAX_PAGES | FUSE_CACHE_SYMLINKS |
FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA |
FUSE_HANDLE_KILLPRIV_V2 | FUSE_SETXATTR_EXT | FUSE_INIT_EXT |
- FUSE_SECURITY_CTX;
+ FUSE_SECURITY_CTX | FUSE_HAS_EXPIRE_ONLY;
#ifdef CONFIG_FUSE_DAX
if (fm->fc->dax)
flags |= FUSE_MAP_ALIGNMENT;
```
Right now I didn't try to compile it yet, but could do if needed.
** Patch added: "FUSE_HAS_EXPIRE_ONLY-feature-flag.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+attachment/5743550/+files/FUSE_HAS_EXPIRE_ONLY-feature-flag.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051700
Title:
Missing fuse backport: "fuse: add feature flag for expire-only"
Status in linux-hwe-6.2 package in Ubuntu:
New
Bug description:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is
probably not going to help.
Issue is that libfuse currently uses a version check instead of
testing for the corresponding feature, which is troublesome with any
kind of feature back port. I.e., if the feature back port increases
the version number, it would enable the "FUSE_EXPIRE_ONLY" although
possibly not back ported. If the back port does not increase the
version number, it might be used by libfuse...
commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi
Date: Mon Mar 27 16:14:49 2023 +0200
fuse: add feature flag for expire-only
Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.
This is needed for backports of this feature, otherwise the server could
just check the protocol version.
Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to
FUSE_NOTIFY_INVAL_ENTRY")
Cc: # v6.2
Signed-off-by: Miklos Szeredi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051700] [NEW] Missing fuse backport: "fuse: add feature flag for expire-only"
Public bug reported:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is probably
not going to help.
Issue is that libfuse currently uses a version check instead of testing
for the corresponding feature, which is troublesome with any kind of
feature back port. I.e., if the feature back port increases the version
number, it would enable the "FUSE_EXPIRE_ONLY" although possibly not
back ported. If the back port does not increase the version number, it
might be used by libfuse...
commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi
Date: Mon Mar 27 16:14:49 2023 +0200
fuse: add feature flag for expire-only
Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.
This is needed for backports of this feature, otherwise the server could
just check the protocol version.
Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to
FUSE_NOTIFY_INVAL_ENTRY")
Cc: # v6.2
Signed-off-by: Miklos Szeredi
** Affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051700
Title:
Missing fuse backport: "fuse: add feature flag for expire-only"
Status in linux-hwe-6.2 package in Ubuntu:
New
Bug description:
Hello,
I just noticed that the backport of this patch was not done for
linux-6.2 and linux-6.3, I guess because there had been a merge
conflict. I think in the mean time these versions are not maintained
anymore, so sending a version that fixes the merge conflict is
probably not going to help.
Issue is that libfuse currently uses a version check instead of
testing for the corresponding feature, which is troublesome with any
kind of feature back port. I.e., if the feature back port increases
the version number, it would enable the "FUSE_EXPIRE_ONLY" although
possibly not back ported. If the back port does not increase the
version number, it might be used by libfuse...
commit 5cadfbd5a11e5495cac217534c5f788168b1afd7
Author: Miklos Szeredi
Date: Mon Mar 27 16:14:49 2023 +0200
fuse: add feature flag for expire-only
Add an init flag idicating whether the FUSE_EXPIRE_ONLY flag of
FUSE_NOTIFY_INVAL_ENTRY is effective.
This is needed for backports of this feature, otherwise the server could
just check the protocol version.
Fixes: 4f8d37020e1f ("fuse: add "expire only" mode to
FUSE_NOTIFY_INVAL_ENTRY")
Cc: # v6.2
Signed-off-by: Miklos Szeredi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2051700/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I'm actually going to close the upstream issue - I'm still not clear on the root cause - it is a slab/kmem cache issue, but I don't which subsystem is responsible for it. It might get visible on opening various kernel debug options, but it requires to recompile and also slows down the system dramatically, unfortunately I don't have the time for that :( Especially as the issue went away after installing the linux-5.9.3 kernel. I guess switching to wayland just avoid the trigger, but the 5.8 kernel seems to have a bad bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I created https://gitlab.freedesktop.org/drm/intel/-/issues/2631 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2631 https://gitlab.freedesktop.org/drm/intel/-/issues/2631 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine:
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
The traces in https://gitlab.freedesktop.org/drm/intel/-/issues/1201 look entirely different, so I'm not sure if this is related. Here we have [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] Issue 1201 from freedesktop.org has Mar 06 22:36:00 ai-karellen-lap kernel: i915_gem_gtt_insert+0x174/0x250 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: i915_vma_pin+0x62f/0x6f0 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: i915_gem_object_pin+0x12d/0x1a0 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: i915_gem_object_pin_to_display_plane+0xa9/0xf0 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: intel_pin_and_fence_fb_obj+0x9d/0x1c0 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: intel_plane_pin_fb+0x44/0xd0 [i915] Mar 06 22:36:00 ai-karellen-lap kernel: intel_prepare_plane_fb+0xe0/0x310 [i915] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript:
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
Happens for me as well, using xfce4 (so wayland is not a simple option) and I don't use anything like pycharm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=4e0782c5-5436-4e47-9813-0946aea670c3
[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
Related to debian bug #773731 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On 01/22/2014 05:51 PM, Steve Langasek wrote: On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: The fix he outlines is not for this bug. It's not for a bug we have in upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of all of upstart's library dependencies, which are finite and accounted for. Why shouldn't switching to an independent file system (tmpfs/initramfs) and shutdown-init-process not help? That way you can kill all processes without exceptions. You can even entirely unmount the old root, no need for remounting it read-only anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
