Xen users - Dec 2005 - "netdev watchdog" error and non-working sis900 network card - solution

Hi, I just found something that might be interesting - I didn''t find
the
solution here on this list:

when installing xen 3.0  I had trouble to get networking going - it 
worked perfectly on the same machinwith the non-xen kKernel. But with 
the xen Kernel (self-compiled, to get support for my sis900 network 
chipset) ran, I got
lots of error messages with something like "netdev watchdog..."  in
it,
followed by my network card not working on the xen dom0 privileged system.

I also tried the demo cd, same thing.

The troubles went away when adding kernel options "noapic acpi=off" to
the modules grub line.

Henning

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of henning
> Sent: 22 December 2005 16:41
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] "netdev watchdog" error and non-working 
> sis900 network card - solution
> 
> Hi, I just found something that might be interesting - I 
> didn''t find the solution here on this list:
> 
> when installing xen 3.0  I had trouble to get networking 
> going - it worked perfectly on the same machinwith the 
> non-xen kKernel. But with the xen Kernel (self-compiled, to 
> get support for my sis900 network
> chipset) ran, I got
> lots of error messages with something like "netdev 
> watchdog..."  in it, followed by my network card not working 
> on the xen dom0 privileged system.
> 
> I also tried the demo cd, same thing.
> 
> The troubles went away when adding kernel options "noapic 
> acpi=off" to the modules grub line.
Both noapic and acpi=off make big difference to the machine setup - it
would probably be a good idea to figure out which one makes the
difference. If it''s acpi=off, a new BIOS that has more suitable things
in the ACPI tables is probably the solution. 

If it''s the noapic that actually solves the problem, then that would be
useful to know (but I''m not sure what the fix is, aside from the fact
that it may actually be the PCI enumeration that goes wrong in the
system - lspci -vvv may give some info. 

--
Mats
> 
> Henning
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users