Xen users - Jan 2006 - RE: "netdev watchdog" error and non-working sis900 networkcard - solution

> Ian Pratt wrote:
> > Yes. The acpi= line must go on the *xen* command line, 
> which will then 
> > pass it to linux.
> >   
> Sorry, I do not understand that completely - you say it 
> _must_ go in the xen command line -  but In my case, putting 
> it in the kernel command line instead makes my network work.
> 
> Before you said using acpi=off is bad, probably meaning 
> "putting acpi=off in the xen command line is bad" - is it not 
> so bad anymore, now that you know I do not put this in the 
> xen command line? Or is it even worse?
Xen and Linux must agree on whether they''re using the ioapic/acpi or
not. If the apci= parameter goes on the xen command line, xen will also
add it to Linux''s.

Using acpi=off is far from ideal -- its much better to use an ioapic if
you have one.
> Most important to me, can I stay with this setup, or should I 
> test what happens when I put it in the xen command line and 
> tell you what happens?
Was you''re problem that the network failed intermittently when allowing
the ioapic to be used? If so, I''m very interested. If it was just that
it didn''t work at all then that suggests a bios bug (possibly solveable
by an upgrade), and isn''t a big deal.

Ian

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

Ian Pratt wrote:
> [...]
> Xen and Linux must agree on whether they''re using the ioapic/acpi
or
> not. If the apci= parameter goes on the xen command line, xen will also
> add it to Linux''s.
>
> Using acpi=off is far from ideal -- its much better to use an ioapic if
> you have one.
>   
Is ioapic just another word for acpi?
> [...]
> Was you''re problem that the network failed intermittently when
allowing
> the ioapic to be used? If so, I''m very interested. If it was just
that
> it didn''t work at all then that suggests a bios bug (possibly
solveable
> by an upgrade), and isn''t a big deal.
>
>   
The network card was shown in "ifconfig" after putting it up. But it 
neither got any dhcp messages and couldn''t be assigned an IP address, 
any try to access it, e.g. with ifconfig results in the "netdev 
watchdog" errors mentioned (see the diffs). So it looks like it''s
not
working at all, not just intermittently.

I''ll see if I can get a BIOS upgrade, or just live with it as
it''s only
a testing machine which doesn''t have to do anything especially
reliable.


Thanks for the information.
Henning

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

Ian Pratt wrote:
> [...]
> Xen and Linux must agree on whether they''re using the ioapic/acpi
or
> not. If the apci= parameter goes on the xen command line, xen will also
> add it to Linux''s.
>
> Using acpi=off is far from ideal -- its much better to use an ioapic if
> you have one.
>   
Is ioapic just another word for acpi?
> [...]
> Was you''re problem that the network failed intermittently when
allowing
> the ioapic to be used? If so, I''m very interested. If it was just
that
> it didn''t work at all then that suggests a bios bug (possibly
solveable
> by an upgrade), and isn''t a big deal.
>
>   
The network card was shown in "ifconfig" after putting it up. But it
neither got any dhcp messages and couldn''t be assigned an IP address,
any try to access it, e.g. with ifconfig results in the "netdev
watchdog" errors mentioned (see the diffs). So it looks like it''s
not
working at all, not just intermittently.

I''ll see if I can get a BIOS upgrade, or just live with it as
it''s only
a testing machine which doesn''t have to do anything especially
reliable.


Thanks for the help and information.
Henning



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

henning wrote:
 > [...]
> The network card was shown in "ifconfig" after putting it up. But
it
> neither got any dhcp messages and couldn''t be assigned an IP
address,
> any try to access it, e.g. with ifconfig results in the "netdev 
> watchdog" errors mentioned (see the diffs). So it looks like
it''s not
> working at all, not just intermittently.
>
> I''ll see if I can get a BIOS upgrade, or just live with it as
it''s
> only a testing machine which doesn''t have to do anything
especially
> reliable.
Upgrading to the newest available BIOS version (which says at bootup " 
version 2.60 - ACPI compatible") didn''t help.

Same effect. This is an older asrock K7 board.

I have to use acpi=off at xen grub command line

Henning

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