NetBSD Problem Report #9067
Received: (qmail 21035 invoked from network); 28 Dec 1999 19:39:55 -0000
Message-Id: <199912281939.MAA18650@garbled.net>
Date: Tue, 28 Dec 1999 12:39:24 -0700 (MST)
From: Charlie Root <root@garbled.net>
Reply-To: root@garbled.net
To: gnats-bugs@gnats.netbsd.org
Subject: LFS panics in 1.4.2_ALPHA while building world
X-Send-Pr-Version: 3.95
>Number: 9067
>Category: kern
>Synopsis: LFS panics in 1.4.2_ALPHA while building world
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Dec 28 11:42:00 +0000 1999
>Closed-Date: Wed Mar 31 07:41:48 +0000 2004
>Last-Modified: Wed Mar 31 07:41:48 +0000 2004
>Originator: Charlie Root
>Release: 1.4.2_ALPHA
>Organization:
>Environment:
NetBSD giauzar 1.4.2_ALPHA NetBSD 1.4.2_ALPHA (GIAUZAR) #1: Fri Dec 24 17:25:12 MST 1999 root@giauzar:/usr/src/1.4.2/syssrc/sys/arch/alpha/compile/GIAUZAR alpha
>Description:
While doing a make build:
/build/tools/usr/bin/cc -B/build/tools/usr/libexec/ -o uuconv -nostdlib -L/build/root/usr/lib /build/root/usr/lib/crt0.o /build/root/usr/lib/crtbegin.o uuconv.o /build/src/gnu/libexec/uucp/libunix/obj.alpha/libunix.a /build/src/gnu/libexec/uucp/libuuconf/obj.alpha/libuuconf.a /build/src/gnu/libexec/uucp/libuucp/obj.alpha/libuucp.a -lgcc -lc -lgcc /build/root/usr/lib/crtend.o
dependall ===> gnu/libexec/uucp/uucp
The following occurred:
lfs_fastvget: ino 174868 inlocked by pid 5367
lfs_fastvget: ino 174868 inlocked by pid 5367
lfs_fastvget: ino 174868 inlocked by pid 11462
lfs_fastvget: ino 174868 inlocked by pid 11462
lfs_fastvget: ino 174868 inlocked by pid 13074
lfs_fastvget: ino 174868 inlocked by pid 13074
lfs_fastvget: ino 174868 inlocked by pid 13074
Warning: received processor correctable error.
Warning: received processor correctable error.
lfs_fastvget: ino 91665 inlocked by pid 16342
lfs_fastvget: ino 174868 inlocked by pid 16772
Warning: received processor correctable error.
Warning: received processor correctable error.
lfs_fastvget: ino 174868 inlocked by pid 9554
lfs_fastvget: ino 174868 inlocked by pid 11128
lfs_fastvget: ino 174868 inlocked by pid 11128
lfs_fastvget: ino 174868 inlocked by pid 11128
lfs_fastvget: ino 42537 inlocked by pid 13011
Warning: received processor correctable error.
lfs_fastvget: ino 174868 inlocked by pid 16386
lfs_fastvget: ino 174868 inlocked by pid 16386
lfs_fastvget: ino 174868 inlocked by pid 16386
lfs_fastvget: ino 174868 inlocked by pid 16386
lfs_fastvget: ino 65103 inlocked by pid 16875
panic: lfs_nextseg: no clean segments
Stopped in lfs_cleanerd at Debugger+0x4: ret zero,(ra)
ps shows the following lfs related states:
20081 359 20081 0 3 0x4006 tail lfsinod
>How-To-Repeat:
Unsure.. Activity on the disk seems to eventually trigger this.
>Fix:
I wish I had one..
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: kern-bug-people->perseant
Responsible-Changed-By: perseant
Responsible-Changed-When: Sat Jan 15 15:37:23 PST 2000
Responsible-Changed-Why:
I have responsibility for LFS-related problems.
Responsible-Changed-From-To: perseant->kern-bug-people
Responsible-Changed-By: perseant
Responsible-Changed-When: Thu Nov 20 19:53:49 UTC 2003
Responsible-Changed-Why:
Trying to be realistic
State-Changed-From-To: open->feedback
State-Changed-By: tls
State-Changed-When: Wed Mar 31 06:38:50 UTC 2004
State-Changed-Why:
I believe this bug is fixed in -current and on the 2.0 branch. Can you confirm?
From: Tim Rightnour <root@garbled.net>
To: gnats-bugs@gnats.netbsd.org
Cc: tls@netbsd.org, kern-bug-people@netbsd.org
Subject: Re: kern/9067
Date: Wed, 31 Mar 2004 00:38:33 -0700 (MST)
On 31-Mar-2004 tls@netbsd.org wrote:
> Synopsis: LFS panics in 1.4.2_ALPHA while building world
>
> State-Changed-From-To: open->feedback
> State-Changed-By: tls
> State-Changed-When: Wed Mar 31 06:38:50 UTC 2004
> State-Changed-Why:
> I believe this bug is fixed in -current and on the 2.0 branch. Can you
> confirm?
I have no way of testing this anymore. I trust you that it's fixed though, so
you can close it out.
---
Tim Rightnour <root@garbled.net>
NetBSD: Free multi-architecture OS http://www.netbsd.org/
NetBSD supported hardware database: http://mail-index.netbsd.org/cgi-bin/hw.cgi
State-Changed-From-To: feedback->closed
State-Changed-By: tls
State-Changed-When: Wed Mar 31 07:41:36 UTC 2004
State-Changed-Why:
Closed per submitter's OK.
>Unformatted:
>115 113 113 0 2 0x4 lfs_cleanerd
113 1 113 0 3 0x84 lfs_cleanerd wait
db> c
syncing disks...
fatal kernel trap:
trap entry = 0x2 (memory management fault)
a0 = 0x0
a1 = 0x1
a2 = 0x0
pc = 0xfffffc00004f4538
ra = 0xfffffc0000468b08
curproc = 0xfffffc0002491310
pid = 115, comm = lfs_cleanerd
panic: trap
Stopped in lfs_cleanerd at Debugger+0x4: ret zero,(ra)
db>
after performing the dump:
sd12: WARNING: cache synchronization failed
sd11: WARNING: cache synchronization failed
rebooting...
Random information:
This disk is a ccd, and the LFS portion is about 4g. There was about 3g free
on the LFS when this panic occurred. sd11 and sd12 are the ccd components,
and are wide diff drives on a BHA-958D controller.
/dev/ccd0d 3994624 3330216 264946 92% /build
Hrmm.. actually.. I have no idea what is taking up all that space in there..
and now.. attempts to cd into that FS lock the terminal up. Whatever happened
to that FS, was fatal.
0 114 1 25 10 0 88 512 wait Is ?? 0:00.00 /usr/libexec/l
fs_cleanerd /build
0 115 114 9 -5 0 5432 4184 lfs se D ?? 0:00.07 /usr/libexec/l
fs_cleanerd /build
0 201 1 0 -14 0 640 288 lfsino D p0- 0:00.00 mount -a
0 205 1 0 -14 0 1024 488 lfsino Ds+ p1 0:00.03 -csh
0 116 1 12 -5 0 112 56 lfs_av D C0- 0:00.00 mount_ffs /dev
/ccd0e /build/root
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.