Strange, it sounds like the e100 modules themselves at first glance are
at fault. Does a native kernel do this crash and burn, or is it just the
xenlinux kernel?
Under debian I do advise a different network script when xend is
started. The curent one seems to have issues (randomly, oddly enough)
with the ipv6 being loaded. My fix was to setup eth0 as static, auto,
and xen-br0 as static, no auto, then have network script run ifup eth0
&& ifconfig eth1 0.0.0.0.
Can you post the kernel OOPS message that you are getting on
auto-loading?
On Thu, 2004-10-21 at 08:42, Pasi Kärkkäinen wrote:
> On Thu, Oct 21, 2004 at 03:59:35PM +0300, Pasi Kärkkäinen wrote:
> > Hi again!
> >
> > I'm using the latest Debian xen 2 packages for Debian 3.1 (sarge/testing)
> > from Brian Wolfe.
> >
> > Hardware is Compaq Proliant DL360 server. It has Serverworks chipset, intel
> > etherexpress pro/100 network card (e100), cpqarray raid and dual Intel P3 /
> > 1 GHz
> > processors.
> >
> > The problem happens with both 2.6.8 and 2.4.27 xen domain0 kernels.
> >
> > If I add e100 module to /etc/modules, for loading it automatically in
> > the beginning of the boot process, the domain0 crashes during the bootup
> > when loading the module.
> >
> > Nothing on the screen, just the normal bootup messages for stuff that has
> > been done before loading the modules. Powercycle needed to get it booting
> > (or crashing ;) again. This crash happens during every boot.
> >
> > Now the weird thing is, If I move the module-init-tools script to the
> > end of the bootup process (by renaming the /etc/rcS.d/SXXmodule-init-tools
> > link), the system boots up OK without crashing..
> >
> > So something that is ran during the bootup enables the e100 module to load
> > without crashing.. any ideas what that might be? Somebody seeing the same?
> >
> > I have already disabled the default hotplug and discover scripts from the
> > bootup
> > sequence.. they seem to have no effect to this problem.
> >
>
> I did some testing, and the problem is this:
>
> If the networking-script (which enables rp_filter, ip_forwarding, syncookies
> and does ifup -a) is ran _before_ loading network driver modules, then the
> network
> modules (e100) will load successfully without crashing. In this case the
> interface is left unconfigured because the network driver is not loaded when
> the
> networking-script is run.
>
> But, if the e100-module is loaded first (before the networking-script is
> ran, the normal case), then the domain0 kernel crashes while loading the
> module..
>
> So networking-script does something, which enabled the e100 module to load
> without crashing.. any ideas?
>
> -- Pasi Kärkkäinen
>
> ^
> . .
> Linux
> / - \
> Choice.of.the
> .Next.Generation.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home