NetBSD Problem Report #58808

From www@netbsd.org  Sun Nov  3 10:57:27 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 529E31A9238
	for <gnats-bugs@gnats.NetBSD.org>; Sun,  3 Nov 2024 10:57:27 +0000 (UTC)
Message-Id: <20241103105725.B6B551A923B@mollari.NetBSD.org>
Date: Sun,  3 Nov 2024 10:57:25 +0000 (UTC)
From: uklaus@hgb-leipzig.de
Reply-To: uklaus@hgb-leipzig.de
To: gnats-bugs@NetBSD.org
Subject: NetBSD 10.0_STABLE: file system corruption after ticket 985 
X-Send-Pr-Version: www-1.0

>Number:         58808
>Category:       kern
>Synopsis:       NetBSD 10.0_STABLE: file system corruption after ticket 985
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 03 11:00:01 +0000 2024
>Last-Modified:  Thu Dec 05 16:10:01 +0000 2024
>Originator:     Uwe Klaus
>Release:        NetBSD 10.0_STABLE
>Organization:
>Environment:
NetBSD rpi4 10.0_STABLE NetBSD 10.0_STABLE (GENERIC64) #38: Thu Oct  29 17:45:51 CEST 2024  root@rpi4:/usr/obj.evbarm/sys/arch/evbarm/compile/GENERIC64 evbarm
>Description:
I'm following 10.0_STABLE on a Raspberry Pi4 since several months.
The file system is on a Kingston 512GB sd card (canvas go! plus, SDCG3/512GBSP). 

[     1.000004] sdmmc1 at sdhc1 slot 0
[     1.529342] sdmmc1: SD card status: 4-bit, C10, U3, V30, A2
[     1.529342] ld1 at sdmmc1: <0x9f:0x5449:SD512:0x61:0x4938055c:0x179>
[     1.538289] ld1: 461 GB, 60208 cyl, 255 head, 63 sec, 512 bytes/sect x 967245824 sectors
[     1.548290] ld1: GPT GUID: 5a277550-751a-42b6-b282-524be2b0d6b3
[     1.548290] dk0 at ld1: "EFI", 163840 blocks at 8192, type: msdos
[     1.548290] dk1 at ld1: "netbsd-root", 5332992 blocks at 172032, type: ffs
[     1.561200] dk2 at ld1: "netbsd-usr", 167780352 blocks at 5505024, type: ffs
[     1.561200] dk3 at ld1: "swap", 16777216 blocks at 173285376, type: swap
[     1.574909] dk4 at ld1: "netbsd-var", 16777216 blocks at 190062592, type: ffs
[     1.582025] dk5 at ld1: "rpi4", 734003200 blocks at 206839808, type: ffs
[     1.582025] ld1: 4-bit width, High-Speed/SDR25, 50.000 MHz

The system ran stable until the latest tickets were applied. The kernel now panics and the filesystems get corrupted. 

I suspect ticket #985. My last "good" kernel is from Oct 4th. With recent userland and the older kernel the Pi runs stable again.
>How-To-Repeat:
-
>Fix:
-

>Audit-Trail:
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/58808: NetBSD 10.0_STABLE: file system corruption after ticket 985 
Date: Sun, 3 Nov 2024 11:11:49 -0000 (UTC)

 uklaus@hgb-leipzig.de writes:

 >The system ran stable until the latest tickets were applied. The kernel now panics and the filesystems get corrupted. 

 Can you please show the panic message (and other messages before the crash) ?

From: Uwe Klaus <uklaus@hgb-leipzig.de>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/58808: NetBSD 10.0_STABLE: file system corruption after
 ticket 985
Date: Thu, 5 Dec 2024 16:15:16 +0100 (CET)

 On Sun, 3 Nov 2024, Michael van Elst via gnats wrote:

 > Can you please show the panic message (and other messages before the crash) ?
 here is an update of this issue. I couldn't catch any panic
 anymore. Nevertheless I got several file system corruptions with
 different kernels before and after applying ticket 985. After booting I 
 had the run fsck to  repair the filesystems.

 Probably the sd card itself woes.

 Since I need a stable system :-) I replaced the rpi case and add a 
 built-in sata ssd usb connected.
 For more than two weeks the system runs stable again even under
 heavy load.

 Best regards,
 Uwe

Home	PR Database Search