On 06/16/2011 01:40 PM, Tomasz Chmielewski wrote: > On 16.06.2011 18:06, Ronciak, John wrote: >> We are talking about the igb driver and not e1000, correct? Just >> want to make sure we are talking about the correct driver. BTW, our >> very latest drivers can be found at http:/e1000.sf.net which has all >> of our latest drivers including the igb driver. You might want to >> try our latest version. > > Yes, it's the igb driver, sorry if I made any confusion here. > > >>> I signaled the issue before, and it was suggested I may need to >>> update network card's firmware: >>> >>> http://comments.gmane.org/gmane.linux.network.general/14930 >> Who told you to update the firmware? The link doesn't show anything >> like that. We don't hand out updates to firmware. It's possible >> that it can be updated via a system BIOS upgrade. Is this system >> running the very latest system BIOS from HP? > > I've applied all BIOS and other firmware updates, but it didn't change > this behaviour. > > FYI, although not really related to this list, HP ProLiant DL180 G6 has > a bug in its "management firmware" (iLO), which causes very strange > network behaviour after the server is online for some time: > > - almost exactly every hour, packet delays ranging 10-20 seconds for > about a minute (ICMP packets sent from a machine connected to the same > switch). > > I've observed this behaviour on ~8 such servers (at least, there was > such a bug with hardware shipped 1.5 yrs ago); firmware update from HP > fixes it. > > >>> http://virtall.com/files/temp/IMG00066-20110420-0956.jpg >>> http://virtall.com/files/temp/IMG00067-20110420-0957.jpg >>> http://virtall.com/files/temp/2011-06-15_16-19-51_252.jpg >> The all just show the stack, nothing about the driver. What makes >> you think that it's the driver? > > Perhaps the comment from the gmane thread (and, that the box is pushing > a lot of traffic): > > Are you running the latest version of the NIC driver? It's more > likely that the problem is caused by the driver then by the > kernel. > > Although the Intel drivers are not known to be flaky, your load > is pretty high (if it's on constantly on this level) and could > reveal a rare race. > > > But you're right, there is nothing related to the driver in the output. > > I'll try to get a serial console to see if I can capture some more data. >
It's important to see the info between the message "BUG: unable to handle kernel..." and the stack trace. I think you missed that in the screenshots and we can only see the final part. If you get the info, you can report to [email protected] which is the generic networking mailing list. fbl ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ 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
