Hey guys, may have another one but Im not sure if this is a xen thing or a linux thing. If I disable ACPI in my Dom0 kernel, none of my NICs work. They all show up, but if you try to send or receive traffic you get a NETDEV WATCHDOG timeout error. I have found a bug on the Debian lists listing something similar in regards to nics stopping after a suspend. Could someone else try to compile a custom Dom0 kernel and only remove ACPI support and see if you have the same trouble? For reference, my NICS are eepro100''s and via Rhine II''s. xm info says root@hive:~# xm info host : hive release : 2.6.16-xen0 version : #4 Mon Mar 27 19:17:41 CST 2006 machine : i686 nr_cpus : 1 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 1599 hw_caps : 078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001 total_memory : 1008 free_memory : 861 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Sun Mar 26 11:50:39 2006 +0100 9441:30ae67d6e5f0 cc_compiler : gcc version 3.4.3 cc_compile_by : root cc_compile_domain : [unknown] cc_compile_date : Sun Mar 26 20:24:24 CST 2006 -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Jason, I have seen this behaviour as well; I though it had to do with disabling the APIC, rather than APCI. To boot without apci, you can just specify noapci on the kernel command line. I''ll verify locally a little later on with a noacpi boot. cheers, Ian. On Mon, 2006-03-27 at 20:04 -0600, Jason wrote:> Hey guys, may have another one but Im not sure if this is a xen thing or a linux thing. If I > disable ACPI in my Dom0 kernel, none of my NICs work. They all show up, but if you try to send or > receive traffic you get a NETDEV WATCHDOG timeout error. I have found a bug on the Debian lists > listing something similar in regards to nics stopping after a suspend. Could someone else try to > compile a custom Dom0 kernel and only remove ACPI support and see if you have the same trouble? > For reference, my NICS are eepro100''s and via Rhine II''s. xm info says > root@hive:~# xm info > host : hive > release : 2.6.16-xen0 > version : #4 Mon Mar 27 19:17:41 CST 2006 > machine : i686 > nr_cpus : 1 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 1 > threads_per_core : 1 > cpu_mhz : 1599 > hw_caps : 078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001 > total_memory : 1008 > free_memory : 861 > xen_major : 3 > xen_minor : 0 > xen_extra : -unstable > xen_caps : xen-3.0-x86_32 > platform_params : virt_start=0xfc000000 > xen_changeset : Sun Mar 26 11:50:39 2006 +0100 9441:30ae67d6e5f0 > cc_compiler : gcc version 3.4.3 > cc_compile_by : root > cc_compile_domain : [unknown] > cc_compile_date : Sun Mar 26 20:24:24 CST 2006 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have been able to test this on two machines (an athlon 64 and a Pentium M) with the same results in 2.6.16 in xen. I can''t test in a vanilla kernel at this time. The odd part is that I can disable all of the ACPI triggers (button, fan, temp, etc) just as long as the base ACPI support is compiled in, networking works. -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet On Tue, 28 Mar 2006, Ian MacDonald wrote:> Hi Jason, > > I have seen this behaviour as well; I though it had to do with > disabling the APIC, rather than APCI. To boot without apci, you can just > specify noapci on the kernel command line. > > I''ll verify locally a little later on with a noacpi boot. > > cheers, > Ian. > > > > On Mon, 2006-03-27 at 20:04 -0600, Jason wrote: >> Hey guys, may have another one but Im not sure if this is a xen thing or a linux thing. If I >> disable ACPI in my Dom0 kernel, none of my NICs work. They all show up, but if you try to send or >> receive traffic you get a NETDEV WATCHDOG timeout error. I have found a bug on the Debian lists >> listing something similar in regards to nics stopping after a suspend. Could someone else try to >> compile a custom Dom0 kernel and only remove ACPI support and see if you have the same trouble? >> For reference, my NICS are eepro100''s and via Rhine II''s. xm info says >> root@hive:~# xm info >> host : hive >> release : 2.6.16-xen0 >> version : #4 Mon Mar 27 19:17:41 CST 2006 >> machine : i686 >> nr_cpus : 1 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 1 >> threads_per_core : 1 >> cpu_mhz : 1599 >> hw_caps : 078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001 >> total_memory : 1008 >> free_memory : 861 >> xen_major : 3 >> xen_minor : 0 >> xen_extra : -unstable >> xen_caps : xen-3.0-x86_32 >> platform_params : virt_start=0xfc000000 >> xen_changeset : Sun Mar 26 11:50:39 2006 +0100 9441:30ae67d6e5f0 >> cc_compiler : gcc version 3.4.3 >> cc_compile_by : root >> cc_compile_domain : [unknown] >> cc_compile_date : Sun Mar 26 20:24:24 CST 2006 >> >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users