On Tue, Jan 23, 2001 at 11:13:48AM +0000, David Ford wrote:
> > > The three cardbus cards are slightly different in numerous ways. For
> > > them they normally fault with an APM event, an eject/insert cycle via
> > > software will reset hem and a link down/up won't fix it. For the PCI
....
> > > The PCI cards are hard to get into this state, sometimes they'll run
> > > millions of packets for months on end before they'll burp. Sometimes
> > > it'll happen three times a night. The amount of traffic doesn't seem
> > > to matter, nor does the type of traffic.
> >
> > Sounds like timing issue.
>
> Hmm, should we class these as two similar but different bugs? I suspect they
> are both timing but there is another stimulus operating differently.
I think they are separate problems.
The first is power-management suspend/resume issue, and possibly
PCMCIA problem at software re-insert of card (which never was taken
out *physically*).
If I pull the cardbus card out, make sure the "dhcpcd eth0" has
died (e.g. I kill it), and re-insert the card, system is highly
likely to work.
It is just that if I suspend my laptop with card in, and wakeup it
latter, there I encounter dead network card.
Hangup/barfing on system which never suspends will never excercise
suspend/resume codepaths, but may poke at wrong moment at some register,
which causes card severe indigestion problems - rx/tx hangup.
Sadly a "100% Compatible" usually means: "beware odd problems"
> -d
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
