Hi, sorry to hear about your issue. On Fri, 19 Mar 2010, 이동호 wrote:
> We currently use the FW-6490 made in Lanner. The following is spec. I assume this system is some kind of embedded device? A quick google shows it to be a security appliance. Have you contacted the vendor for support? > --------------------------------------------------- > Model Name: FW-6490F > HDD: CF 4G > NIC: Intel 82573L x 2 , 82541Gi x 2 > Mainboard chip sets: VIA CN700 + VT8251 we have had a lot of problems with VIA chipsets and their bugs, I don't know anything about this particular one. > OS : Fedora4(kernel?2.6.11-1.1369_FC4) > ---------------------------------------------------- > > We installed the e1000e-0.4.1.7 for use of Intel 82573L NIC. > Later, those equipment is working order, but they occur the unspecified hang > or kernel panic. do you have any information that points the networking hardware to being the cause of the kernel panic? > We tried to find the cause of this problem in various ways. > But we couldn’t find a clear answer and the content was confirmed as below. > The content was added in e1000e-1.1.2 as follow. > -------------------------------------------------------------------------------------------- > TROUBLESHOOTING: Some systems have trouble supporting MSI and/or MSI-X > interrupts. If you believe your system needs to disable this style of > interrupt, the driver can be built and installed with the command: > > # make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install > > Normally the driver will generate an interrupt every two seconds, so if > you can see that you're no longer getting interrupts in > cat /proc/interrupts for the ethX e1000e device, then this workaround > may be necessary. > --------------------------------------------------------------------------------------------- is there something wrong with MSI interrupts? It is unlikely that a panic or hard hang kind of issue could be related to MSI interrupts. Usually MSI failures prevent the adapter from getting link or being able to pass traffic. > In addition, we confirmed that the option didn’t exist related to MSI in > kernel 2.6.11-1.1369_FC4. > In case of Fedora8, the option related to MSI is contained as follow. you can probably boot the kernel with pci=nomsi or some equivalent option that will allow you to disable MSI. > -------------------------------------------------------- > cat /boot/config-2.6.23.1-42.fc8 | grep MSI > CONFIG_ARCH_SUPPORTS_MSI=y > CONFIG_PCI_MSI=y > CONFIG_MSI_LAPTOP=m > ------------------------------------------------------- why did you pick fedora 8 here? did you try running the FC8 kernel and did it work better? > We confirmed that Intel 82573L NIC which we use now didn’t support the MSI, > too. 82573L *does* support MSI, maybe your system hardware does not. > ----------------------------------------------------------------------------- > Q1: If we don't apply the added TROUBLESHOOTING option to e10003-1.1.2, what > problem has arise? the troubleshooting is only IF you have a problem, so disabling MSI by itself will not cause any issues. > Q2: If I use the Intel 82573L in kernel 2.6.11-1.1369_FC4 which can’t set a > option related to MSI, can it occur the kernel panic or hang caused by the > use of e1000e-0.4.1.7? I don't know, there aren't any particular issues that come to mind. can you enable nmi_watchdog or magic SYSRQ key and hit it after the crash? can you enable serial console or netconsole and capture the panic? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
