Subject: port-i386/27241: 2.0_RC4 install kernel don't boot
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <sebastien_erard@hotmail.com>
List: netbsd-bugs
Date: 10/12/2004 21:24:21
>Number: 27241
>Category: port-i386
>Synopsis: 2.0_RC4 install kernel don't boot
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: port-i386-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Oct 12 21:25:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: Sebastien Erard
>Release: 2.0_RC4
>Organization:
>Environment:
>Description:
i386, asus p4c800-e deluxe, with 2 satalink 3112 controlers, 4 120 GB SATA drives (2 on the ICH5r, 1 on each satalink), 4 raid sets (1 raid 0 for the boot partition, 3 raid 1). plenty of other devices (list provide on demand if needed).
The 2.0_RC4 INSTALL kernel (from boot-big.fs) get stuck after scsibus enumeration, failing to recgonize my raidframe devices. Current INSTALLkernel behaves the same (at least last month). But GENERIC is ok, tested only in current.
2.0_RC4 INSTALL worked well on a asus p4s533, without raidframe used.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: