On Fri, 19 Mar 2010 12:42:20 -0700 Jesse Brandeburg <[email protected]> wrote:
> Added netdev, the place to talk about in-kernel driver problems. > > On Thu, 2010-03-11 at 22:39 -0700, Stephen Hemminger wrote: > > ----- "Ed Ravin" <[email protected]> wrote: > > > > > I'm using the Vyatta "kenwood" Linux distribution, which is currently > > > at 2.6.31-1. I upgraded to their latest version, and began seeing > > > kernel > > > panics shortly after starting to use ssh/scp on the network connected > > > to > > > an e100 NIC. I was able to reproduce the problem immediately after > > > booting up - sometimes it even crashed during the boot. > > > > > > One of the crash logs is attached. > > Ed, thanks for the report, looks like these patches introduced a new > problem. e100 hardware has a tricky data structure that seems to cause > some problems for (particularly arm) some cpu architectures. > > > > > > > Since the problem seemed to be related to e100.c, I reverted the two > > > commits to e100.c that had taken place since I last built the kernel > > > for this box: > > > > > > Author: Roger Oksanen <[email protected]> > > > Date: Fri Dec 18 20:18:21 2009 -0800 > > > e100: Fix broken cbs accounting due to missing memset. > > > > > > Author: Roger Oksanen <[email protected]> > > > Date: Sun Nov 29 17:17:29 2009 -0800 > > > e100: Use pci pool to work around GFP_ATOMIC order 5 memory > > > allocation failu > > > > > > I rebuilt the kernel and it's not panicking anymore. > > so you just reverted both, and its good news things are working again, > but can you try one or the other and let us know if things still break > for you? > > > The Vyatta kernel for 2.6.31 is based on the 2.6.31.10 + unionfs. > > These two patches came from the 2.6.31.10 -stable update. > > This is the only report of this issue I have heard so far, so something > must be a little unique to your system or workload such that the driver > works mostly. > > I'm looking more closely into the panic trace now, maybe I can figure it > out from there. > Davem found one thing, the memset wasn't initializing the whole maximum possible tx ring. -- ------------------------------------------------------------------------------ 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
