NetBSD Problem Report #7559
Received: (qmail 856 invoked from network); 12 May 1999 04:15:31 -0000
Message-Id: <199905120417.GAA00779@smaug.fh-regensburg.de>
Date: Wed, 12 May 1999 06:17:57 +0200 (MEST)
From: Hubert Feyrer <hubertf@channel.regensburg.org>
Reply-To: hubert.feyrer@rz.uni-regensburg.de
To: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: panic: kernel fault (see also PR 7442)
X-Send-Pr-Version: 3.95
>Number: 7559
>Category: port-sparc
>Synopsis: panic: kernel fault (see also PR 7442)
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: port-sparc-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 11 21:20:01 +0000 1999
>Closed-Date: Thu Feb 03 17:24:24 +0000 2000
>Last-Modified: Thu Feb 03 17:25:28 +0000 2000
>Originator: Hubert Feyrer
>Release: 1.4
>Organization:
Hubert Feyrer <hubertf@channel.regensburg.org>
>Environment:
System: NetBSD smaug 1.4 NetBSD 1.4 (RFHS8028) #0: Mon May 10 20:05:03 PDT 1999 feyrer@rfhs8028:/amd/jabberwocky/usr/cvs/src-1.4/sys/arch/sparc/compile/RFHS8028 sparc
>Description:
It seems the problem described in PR 7442 still exists in 1.4:
(gdb) target kcore netbsd.0.core
panic: kernel fault
#0 0xf00891f8 in mi_switch ()
(gdb) bt
#0 0xf00891f8 in mi_switch ()
#1 0xf0088b68 in tsleep ()
#2 0xf013a990 in uvm_scheduler ()
#3 0xf0079474 in main ()
>How-To-Repeat:
Take a Sun SparcStation 5 (85MHz), 64MB RAM, try to set up a
RAID w/ RaidFrame.
Setting up the raid seems to trigger the fault.
The setup for the raid is:
sd1 - 2GB disk
sd2 - 4GB disk
sd3 - 2GB disk
raid0 - sd1 & sd3 (see raid0dev.conf below)
raid1 - raid0 and sd2 (see raid1dev.conf below)
Set up the raid:
- create appropriate partitions sd1e and sd3e, and sd2e
- raidctl -C raid0dev.conf raid0
- raidctl -I 12345 raid0
- raidctl -i raid0
- Everything works fine so far, create a raid0e
- raidctl -C raid1dev.conf raid1
- raidctl -I 54321 raid1 <--- BOOM
smaug# cat /etc/raid0dev.conf
START array
1 2 0
START disks
/dev/sd1e
/dev/sd3e
START layout
128 1 1 0
START queue
fifo 100
smaug# cat /etc/raid1dev.conf
START array
1 2 0
START disks
/dev/raid1e
/dev/sd2e
START layout
128 1 1 0
START queue
fifo 100
>Fix:
Please.
>Release-Note:
>Audit-Trail:
From: Michael Graff <explorer@flame.org>
To: hubert.feyrer@rz.uni-regensburg.de
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: 11 May 1999 23:50:23 -0700
Hubert Feyrer <hubertf@channel.regensburg.org> writes:
> Set up the raid:
> - create appropriate partitions sd1e and sd3e, and sd2e
> - raidctl -C raid0dev.conf raid0
> - raidctl -I 12345 raid0
> - raidctl -i raid0
> - Everything works fine so far, create a raid0e
> - raidctl -C raid1dev.conf raid1
> - raidctl -I 54321 raid1 <--- BOOM
Did you create the raid0e partition with disklabel?
Does this do the same thing if you make the underlying layer use ccd?
--Michael
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: hubert.feyrer@rz.uni-regensburg.de
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: Wed, 12 May 1999 13:09:54 +0200
On May 12, Hubert Feyrer wrote
> >Description:
> It seems the problem described in PR 7442 still exists in 1.4:
>
> (gdb) target kcore netbsd.0.core
> panic: kernel fault
> #0 0xf00891f8 in mi_switch ()
> (gdb) bt
> #0 0xf00891f8 in mi_switch ()
> #1 0xf0088b68 in tsleep ()
> #2 0xf013a990 in uvm_scheduler ()
> #3 0xf0079474 in main ()
>
I used to get these on my IPC with 1.4_ALPHA, just with a 'make -j2' kernel
compile. I can't reproduce it with 1.4, and I installed 1.4 on a IPX, it's
solid.
But both are sun4c ...
--
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
--
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
To: Michael Graff <explorer@flame.org>
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: Wed, 12 May 1999 14:54:51 +0200 (MET DST)
On 11 May 1999, Michael Graff wrote:
> > - Everything works fine so far, create a raid0e
> > - raidctl -C raid1dev.conf raid1
> > - raidctl -I 54321 raid1 <--- BOOM
>
> Did you create the raid0e partition with disklabel?
Yes
> Does this do the same thing if you make the underlying layer use ccd?
I haven't found time to try this yet. Given that the machine is in
production use, I don't want to risk too much downtime, but ccd is what I
will try next.
- Hubert
--
NetBSD - Better for your uptime than Viagra
From: Michael Graff <explorer@flame.org>
To: Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: 12 May 1999 07:57:36 -0700
Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de> writes:
> I haven't found time to try this yet. Given that the machine is in
> production use, I don't want to risk too much downtime, but ccd is what I
> will try next.
I have used the raidframe system (single layer raid5, not dual layer
raid0/1) for about 6 months now, and the only time I saw this problem
was when more than one of the components was missing in the raid5 set.
--Michael
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
To: Michael Graff <explorer@flame.org>
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: Wed, 12 May 1999 17:24:39 +0200 (MET DST)
On 12 May 1999, Michael Graff wrote:
> I have used the raidframe system (single layer raid5, not dual layer
> raid0/1) for about 6 months now, and the only time I saw this problem
> was when more than one of the components was missing in the raid5 set.
on i386 or sparc?
- Hubert
--
NetBSD - Better for your uptime than Viagra
From: Michael Graff <explorer@flame.org>
To: Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>
Cc: gnats-bugs@gnats.netbsd.org, pk@netbsd.org
Subject: Re: port-sparc/7559: panic: kernel fault (see also PR 7442)
Date: 12 May 1999 08:54:37 -0700
Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de> writes:
> On 12 May 1999, Michael Graff wrote:
> > I have used the raidframe system (single layer raid5, not dual layer
> > raid0/1) for about 6 months now, and the only time I saw this problem
> > was when more than one of the components was missing in the raid5 set.
>
> on i386 or sparc?
Good point... i386. I have no sparc, and the arm32 has no hard
drives. :)
--Michael
State-Changed-From-To: open->feedback
State-Changed-By: pk
State-Changed-When: Fri Jan 21 07:04:21 PST 2000
State-Changed-Why:
Does this problem still occur in either 1.4.2 ALPHA or -current?
State-Changed-From-To: feedback->closed
State-Changed-By: pk
State-Changed-When: Thu Feb 3 09:24:24 PST 2000
State-Changed-Why:
Submitter cannot reproduce the problem; presumed fixed.
>Unformatted:
(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.