Your message dated Thu, 01 May 2025 17:20:07 +0200 (CEST) with message-id <20250501152007.C3044BE2DE0@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #1026259, regarding linux: SW RAID to JFS intermittent boot fail with NULL pointer dereference to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1026259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026259 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux: SW RAID to JFS intermittent boot fail with NULL pointer dereference
- From: Andy Simpkins <rattusrattus@debian.org>
- Date: Sat, 17 Dec 2022 14:47:38 +0000
- Message-id: <167128845833.8388.3979736359347136453.reportbug@gila.koipond.org.uk>
Source: linux Severity: normal X-Debbugs-Cc: rattusrattus@debian.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Images testing for SW RAID release 11.6 * What exactly did you do (or not do) that was effective (or ineffective)? Installation testing option test matrix option #3 with the following disk partitions sda1 primary 1GB B K raid (#1) sda3 primary 15GB K raid (#0) sda5 logical 1GB F swap swap RAID1 #0 jfs / RAID1 #1 ext2 /boot * What was the outcome of this action? kernel crash with [ 2.671938] BUG: kernel NULL pointer dereference, address: 0000000000000028 (console output attached) * What outcome did you expect instead? Boot into fresh installed system :-) * More details (1) I have demonstrated this to Sledge on MULTIPLE instalations, both BIOS and UEFI and various degraded RAID configurations. (2) It appears to be Machine spacific; i.e. Sledge has been unable to reproduce the problem on his hardware (3) We have seen the problem on installations of debian 11.5 as well (4) Occasionally I have been able to get lucky and the system has booted. This, coupled with #2 might suggest a race hazard / timing issue? Sorry /AndyAttachment: RAID_JFS_kernel_bug_console_out
Description: application/json
--- End Message ---
--- Begin Message ---
- To: 1026259-done@bugs.debian.org
- Cc: 1026259-submitter@bugs.debian.org
- Subject: Closing this bug (BTS maintenance for src:linux bugs)
- From: carnil@debian.org
- Date: Thu, 01 May 2025 17:20:07 +0200 (CEST)
- Message-id: <20250501152007.C3044BE2DE0@eldamar.lan>
Hi This bug was filed for a (very) old kernel or the bug is old itself without resolution. Maybe it was for a feature enablement which nobody acted on. We are sorry we were not able to timely deal with this issue. There are many open bugs for the src:linux package and thus we are closing older bugs where it's unclear if they still occur in newer versions and are still relevant to the reporter. For an overview see: https://bugs.debian.org/src:linux . If you can reproduce your issue with - the current version in unstable/testing - the latest kernel from backports or, if it was a feature addition/wishlist and still consider it relevant, then: Please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Please try to provide as much fresh details including kernel logs where relevant. In particular were an issue is coupled with specific hardware we might ask you to do additional debugging on your side as the owner of the hardware. Regards, Salvatore
--- End Message ---