--TYLBaaOo3Zs/tS0r
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 13, 2006 at 04:09:10PM +1200, Ivan Vari wrote:
> It is just for the record from this stage but it will be still worth for=
=20
> others who may want to use similar config. I am 99% sure that the=20
> problem is the smartarray 5i controller or its cciss driver provided by=
=20
> NetBSD team.

This is quite possible for a NetBSD dom0, that driver is rather new
and probably not well tested in some situations.

I can't see how it would make any difference for a domU, which doesn't
even see the device.

> I took 1 CPU out of my server, left the HT off and just in case passed=20
> the noapic+nosmp params to the kernel even though they are irrelevant=20
> from this stage. (The kernel still has SMP support built in what I will=
=20
> perhaps remove in the next couple of days and recompile just in case)
>=20
> NO! Same problem, domU crashed.

is this a dom0 kernel you're trying to boot as domU?  domU shouldn't
have or need that driver, or many others. something very odd is going
on.

> Then I basically dumped the same install onto a desktop box with a P4=20
> 2.4Ghz+1GB ram, SCSI hdd. The same config I pasted into my previous=20
> email fired up the netbsd 3.1RC2 install like charm. I was so happy to=20
> see a blue screen appearing under Xen. (and it wasn't an NT core dump :) )

Ok, cool. That's some encouragement, but there's probably some other
difference that's the real culprit.  Oh.. are you running the server
with PAE or in 64-bit mode?

--
Dan.

--TYLBaaOo3Zs/tS0r
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFFB4b3EAVxvV4N66cRAtAsAJ9CmsKn/BDPOVQcwCGMby6USQWkagCgwO+o
R+DixDvvNLcclrvMaJW3Zas=
=7G8i
-----END PGP SIGNATURE-----

--TYLBaaOo3Zs/tS0r--