Subject: kern/18481: Someone broke RAIDframe autoconfig
To: None <gnats-bugs@gnats.netbsd.org>
From: None <oster@cs.usask.ca>
List: netbsd-bugs
Date: 09/30/2002 16:19:52
>Number: 18481
>Category: kern
>Synopsis: Someone broke RAIDframe autoconfig
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Sep 30 15:20:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:
>Release: -current
>Organization:
>Environment:
NetBSD rizzo 1.6I NetBSD 1.6I (GENERIC) #0: Mon Sep 30 16:05:41 CST 2002 oster@merlin:/cheetah/current2/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
Someone has Changed Things so that RAIDframe's autoconfig now
occurs *before* most of the disk devices are present. This means that
when raidattach() is called, and the autoconfig code is run, there
arn't any disks around, and the autoconfig bits won't find anything to
configure!!!!
>How-To-Repeat:
Boot a -current kernel with RAIDframe + Autoconfig, and wonder
why it can't find your root partition!!
>Fix:
Dunno, but it needs to be fixed *SOON*.
>Release-Note:
>Audit-Trail:
>Unformatted: