mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Erik Tews <erik@debian.franken.de>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-rc3: waiting for eth0 to become free
Date: Tue, 08 Jun 2004 08:11:07 +0200	[thread overview]
Message-ID: <1086675067.1658.3.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1086649443.21227.44.camel@localhost>

On Tue, 2004-06-08 at 01:04 +0200, Erik Tews wrote:
> Am Di, den 08.06.2004 schrieb Felipe Alfaro Solana um 0:52:
> > On my laptop, when using a CardBus 3c59x-based NIC, I need to run
> > "cardctl eject" so the system won't freeze when resuming. "cardctl
> > eject" worked fine in 2.6.7-rc2-mm2, even when there were programs with
> > network sockets opened (for example, Evolution mantaining a connection
> > against an IMAP server): the card is ejected (well, not physically),
> > even when there are ESTABLISHED connections.
> > 
> > However, starting with 2.6.7-rc3, "cardctl eject" hangs if a program
> > holds any socket open. After a while the "unregister_netdevice: waiting
> > for eth0 to become free" message starts appearing on the kernel message
> > ring. The only apparent solution is killing that program, ejecting the
> > card from its slot and wait until 3c59x.o usage count reaches zero.
> 
> I have seen similar problems with my prism2 minipci-card. I often unload
> the driver to reset the card, sometimes it hangs during unloading with
> the same message. Would it be possible to add some code to backtrace
> this lock?
> 
> This happens with a lot of recent 2.6 kernels, not always reproduceable.

I can reproduce this consistently with 2.6.7-rc3: launch an ftp session
against a remote server and then try running "cardctl eject". In my
case, it just refuses to unload with an usage count of 1.


  reply	other threads:[~2004-06-08  6:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 22:52 Felipe Alfaro Solana
2004-06-07 23:04 ` Erik Tews
2004-06-08  6:11   ` Felipe Alfaro Solana [this message]
2004-06-08  8:23 ` Russell King
     [not found] <1086722310.1682.1.camel@teapot.felipe-alfaro.com>
     [not found] ` <20040608124215.291a7072@dell_ss3.pdx.osdl.net>
     [not found]   ` <1086725369.1806.1.camel@teapot.felipe-alfaro.com>
     [not found]     ` <20040608140200.2ddaa6f4@dell_ss3.pdx.osdl.net>
2004-06-09 13:06       ` Felipe Alfaro Solana
2004-06-09 15:18       ` Felipe Alfaro Solana
2004-06-09 22:48         ` Christian Kujau
2004-06-10  6:07           ` Felipe Alfaro Solana
2004-06-10 11:06             ` Christian Kujau
2004-06-10 15:36         ` Stephen Hemminger
2004-06-10 20:08           ` Felipe Alfaro Solana
2004-06-10 17:43         ` Diego Calleja García

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=1086675067.1658.3.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=erik@debian.franken.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®