All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Doug Chapman <doug.chapman@hp.com>
Subject: Re: REGRESSION: panic on e1000 driver
Date: Wed, 30 May 2007 21:51:14 -0700	[thread overview]
Message-ID: <465E5442.7010503@intel.com> (raw)
In-Reply-To: <20070531005147.GA30628@gondor.apana.org.au>

Herbert Xu wrote:
> On Wed, May 30, 2007 at 03:57:13PM -0700, Kok, Auke wrote:
>> Hmm, we're making a mess of it.
> 
> Indeed :)
> 
>> Herbert, wouldn't it just have been a lot easier to do just add a 
>> netif_poll_disable in e1000_probe, so that any and all other poll 
>> enable/disables are symmetric ? Something like this?
> 
> I wish if it were as simple as that.  As soon as register_netdev
> returns somebody else can invoke e1000_open so disabling poll
> here can be undesirable.  In fact the existing netif_stop_queue
> and netif_carrier_off calls are also bad for the same reason.

this has been an age-old confusion that I never grasped either, so I perfectly 
understand why you added the explicit e1000_disable_irq call in the other patch 
(and think thats a great idea). But really, there should be a way for a driver 
to tell the stack that it should really keep it's hands off :)

BTW e1000 currently triggers a single irq manually in the watchdog as link goes 
up, so that might be the one that is giving problems now. In any case I can't 
reproduce any of it - perhaps my hardware is too fast. Time to whip out the pIII :o

Auke

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  reply	other threads:[~2007-05-31  4:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 21:22 REGRESSION: panic on e1000 driver Doug Chapman
2007-05-30 22:57 ` Kok, Auke
2007-05-30 23:31   ` Doug Chapman
2007-05-31  0:51   ` Herbert Xu
2007-05-31  4:51     ` Kok, Auke [this message]
2007-05-31  5:06       ` Herbert Xu
2007-05-31 14:54         ` Kok, Auke
2007-05-31 21:49           ` Herbert Xu
2007-05-31 22:11             ` Kok, Auke
2007-05-31  1:08 ` Herbert Xu
2007-05-31 15:16   ` Doug Chapman
2007-05-31 15:23     ` [E1000-devel] " Kok, Auke
2007-05-31 21:48       ` Herbert Xu
2007-05-31 22:10         ` Kok, Auke
2007-05-31 22:10     ` Herbert Xu
2007-05-31 22:38       ` Doug Chapman
2007-06-01  0:34         ` Herbert Xu

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=465E5442.7010503@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=doug.chapman@hp.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@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.