Subject: Re: Recent kernel panics, kernel <-> boot loader version related?
To: email@example.com, Nino Dehne <firstname.lastname@example.org>
From: Greg Oster <email@example.com>
Date: 03/01/2006 15:28:55
Markus W Kilbinger writes:
> Nino> I'm using a netbsd-3 boot loader to boot -current kernels.
> Nino> This worked until recently. A kernel as of today panics when
> Nino> booting:
> Nino> boot device: <unknown>
> Nino> root on md0auvm_fault(0xc361a0c0, 0, 0, 1) -> 0xe
> Nino> fatal page fault in supervisor mode
> Nino> trap type 6 code 0 eip c01e52bf cs c01e0008 eflags 10282 cr2 10 ile
> vel 0
> Nino> panic: trap
> I can confirm these panics for all my -current (i386) systems booting
> from raid1. Same boot loader config with older kernels and directly
> booting from hard disks (wd, sd) seems to work fine.
> -> Does the raid (and md) booting stuff need some adaptation for
> recent kernel changes ('device_is_a()' related?)?
Yes..... I'm working on a fix for the RAIDframe bits.