Hi,
On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote:
> On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote:
> > On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote:
> > > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
> > > [snip]
> > > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout
>with(0x70)!
> > >
> > > Please try the attached patch.
> > > Actually, it's designed to solve another problem, but may be your one has the
> > > same origin as that other.
> >
> > Cool. Thanks. I recompiled the module and am trying it now. So far the
> > ethernet connection is fine but the above problem isn't reproducable with
> > 100% accuracy and so it'll take me a wee while before I decide 'oooo....
> > aaaaa... that rocks my boat. it's fixed.'. :)
>
> It happened again. Same deal. Once was after a reboot and this time
> was after a resume. :/
In my experiments wait_for_cmd timeouts almost always were related to
DumpStats command.
I think, we need to investigate what time constraints are related to this
command.
Best regards
Andrey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
