Re: Soft lockup in e100 driver ?

[Matti Aarnio]

On Tue, Aug 09, 2005 at 11:41:40AM -0400, Steven Rostedt wrote:
> On Tue, 2005-08-09 at 17:37 +0300, Matti Aarnio wrote:
> > On Tue, Aug 09, 2005 at 03:55:49PM +0200, Jesper Juhl wrote:
> > > On 8/9/05, Matti Aarnio <matti.aarnio@xxxxxxxxxxx> wrote:
> > > > Running very recent Fedora Core Development kernel I can following
> > > > soft-oops..   ( 2.6.12-1.1455_FC5smp )
> > > > 
> > > Various patches to the e100 driver have been merged since 2.6.12.1
> > > (which is ~1.5months old), so it would make sense to try a more recent
> > > kernel like 2.6.13-rc6, 2.6.13-rc6-git1 or 2.6.13-rc5-mm1 and see if
> > > you can still reproduce the problem with those.
> > 
> > The kernel in question is less than 3 days old RedHat Fedora Core
> > Development kernel with baseline as:
> >   * Sun Aug 07 2005 Dave Jones <davej@xxxxxxxxxx>
> >     - 2.6.13-rc5-git4
> > 
> > Those merges have not helped.
> 
> Matti,
> 
> I believe Fedora must have added Ingo's soft lockup detect code.  I've
> made additions to this code as well. Could you point me to a link that I
> could download this kernel source.  No rpm's or packagemanagers please.
> Just a tarball would be fine.

The fundamental thing is, IT LOCKS UP (for a while), when I do 
"ifconfig eth0 down" and there is active traffic but the card DIES
somehow.  Apparently it requires marginal/unreliable hardware to
happen as well.  (Which for e100 is rather rare.)

That is: at first the card dies, then I notice it, and do the ifconfig.
Then things go _bad_, and recover.  Then I do 'rmmod e100', and
restart network (which reloads the driver module), and things work
once again.

Fedora kernel sources have this "softlockups" patch file: (size and date)
   6159 May 12 04:50 linux-2.6.12-detect-softlockups.patch

That file I can upload, if you want.  Or send in email.
Rest of the RPM-wrapper CPIO package I would prefer not to...


> Thanks,
> -- Steve

/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/