All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CRAP in 2.4.18-pre7
Date: Mon, 28 Jan 2002 07:37:32 -0800	[thread overview]
Message-ID: <3C55703C.30306@zytor.com> (raw)
In-Reply-To: <20020126171545.GB11344@fefe.de> <3C542FE6.7C56D6BD@mandrakesoft.com> <3C5439C1.6000305@evision-ventures.com> <3C543E86.7F0FA37A@gmx.net> <a31q91$upd$1@nell.transmeta.com> <3C553EE3.4060202@evision-ventures.com>

Martin Dalecki wrote:

> 
> Well boys, I know about the ifconfig command, and I just don't see 
> anything special there.
> In esp. no collision indications. I would rather suspect, that there are 
> maybe some IRQ sharing
> problems with the driver, since this got changed as well. However I 
> simple just didn't
> have the time to narrow it down to this. (In esp. doing a recompile with 
> just the blah_irq -> blash_irqsave
> changes enabled.
> 


Autoconfigure screwing up usually (in my experience) doesn't indicate 
collisions.  If you have 100Mbit and FD lights on your card, they would 
typically be going on and off, though.

	-hpa



  reply	other threads:[~2002-01-28 15:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-26 17:15 question about sparc 64-bit user land Felix von Leitner
2002-01-26 17:24 ` Ben Collins
2002-01-26 17:25 ` Jeff Garzik
2002-01-27 14:11   ` CRAP in 2.4.18-pre7 Martin Dalecki
2002-01-27 16:50     ` Jeff Garzik
2002-01-27 17:32       ` Martin Dalecki
2002-01-27 17:53         ` root
2002-01-27 21:08           ` H. Peter Anvin
2002-01-28 12:06             ` Martin Dalecki
2002-01-28 15:37               ` H. Peter Anvin [this message]
2002-01-27 18:46     ` Michal Jaegermann
2002-01-27 21:58       ` Stephan von Krawczynski
2002-01-28  3:40         ` Michal Jaegermann
2002-01-26 18:07 ` question about sparc 64-bit user land Andreas Jaeger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C55703C.30306@zytor.com \
    --to=hpa@zytor.com \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.