From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shmulik Hen <shmulik@trego.co.il>
Cc: netdev@vger.kernel.org
Subject: Re: System blocks (hangs) on ifconfig up
Date: Sun, 12 Dec 2010 21:29:46 +0100 [thread overview]
Message-ID: <1292185786.18698.5.camel@edumazet-laptop> (raw)
In-Reply-To: <4D04E57C.7020509@trego.co.il>
Le dimanche 12 décembre 2010 à 17:08 +0200, Shmulik Hen a écrit :
> Hello,
>
> My system is Ubuntu 10.04, running kernel 2.6.32-26-generic.
>
> Whenever I try to bring up a specific ethernet interface for the second
> time, my
> system becomes unresponsive for 60 seconds - i.e. no mouse, no keyboard, no
> screen refresh. etc.
>
> Looking at the driver's code, I could see that it's dev->open() method
> calls
> wait_event_interruptible_timeout() with a timeout of 60 seconds - exactly
> the delay I'm seeing.
>
What is this driver ?
> I have narrowed the code to a bare minimum (see below - loosely based on
> dummy.c), which only calls mdelay(10000) in it's dev->open() method, and
> still, my system blocks for exactly 10 seconds when I run the following
> sequence:
>
> > sudo ifconfig shmulik0 up
> > sudo ifconfig shmulik0 down
> > sudo ifconfig shmulik0 up
>
> At this point - the system is stuck for 10 seconds.
>
Certainly not "stuck for 10 seconds"
mdelay(10000) suspends this task for 10 seconds, but other tasks can
certainly run.
However, your shell waits that "ifconfig ... up" finishes.
next prev parent reply other threads:[~2010-12-12 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 15:08 System blocks (hangs) on ifconfig up Shmulik Hen
2010-12-12 20:29 ` Eric Dumazet [this message]
2010-12-12 20:53 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2010-12-12 15:00 Shmulik Hen
2010-12-12 23:03 ` Ben Hutchings
2010-12-13 9:14 ` Shmulik Hen
2010-12-13 12:37 ` Eric Dumazet
2010-12-13 13:11 ` Shmulik Hen
2010-12-12 23:29 ` Stephen Hemminger
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=1292185786.18698.5.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shmulik@trego.co.il \
/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