Subject: port-xen/32925: xen.gz crahes on Via Technologies C3 chipset
To: None <port-xen-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: None <rfranklin@wildbluecorp.com>
List: netbsd-bugs
Date: 02/24/2006 22:10:01
>Number:         32925
>Category:       port-xen
>Synopsis:       xen.gz crahes on Via Technologies C3 chipset
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 24 22:10:00 +0000 2006
>Originator:     Robert Franklin
>Release:        3.0 release
>Organization:
WildBlue Communications
>Environment:
Can't, system reboots immediately after the loading of xen.gz. Here is the uname -a output when booted in i386 mode with generic kernel:

NetBSD domain0_90.wildblue.net 3.0 NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005  builds@works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386

>Description:
the xen.gz kernel does not work on a Via Technologies C3 chipset.
I followed the directions in the Xen HOWTO to setup a domain0 on a via technologies PD6000 mini-itx board, including the installation of GRUB.

After the system loads xen.gz, the system immediately reboots. I can't even read the error message.

I followed the same procedure documented in the Xen HOWTO on an intel pentium4 setup, and had 0 issues getting domain0 to boot, so I do not think it is an installer issue (ie me installing it wrong or missing a config in the grub menu.lst file)

I found this on the xen-devel mailing list via google:

http://lists.xensource.com/archives/html/xen-devel/2005-09/msg00074.html

that seems to document a similar problem.

>How-To-Repeat:
Install NetBSD3.0, then install domain0 as documented by the xen HOWTO on a via technologies board that has a C3 chipset. The system will immediately reboot. I can arrange access to the system remotely with serial console if someone would like to look at it further. I can be contacted at rfranklin@wildbluecorp.com


>Fix: