From: folkert <folkert@vanheusden.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Bernard Pidoux <bernard.pidoux@free.fr>,
linux-hams <linux-hams@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: CPU: 0 Not tainted (3.1.9+ #1) when ifconfig rose0 down
Date: Fri, 3 Aug 2012 16:32:00 +0200 [thread overview]
Message-ID: <20120803143200.GE10211@belle.intranet.vanheusden.com> (raw)
In-Reply-To: <87ipd0ykdg.fsf@xmission.com>
> You might want to simply try moving unregister_netdevice_notifier a bit
> earlier in rose_exit and see if that helps. Otherwise I would recommend
> instrumenting the code up with some printk so you can understand what
> part of unregistration is failing.
Or bisect! Give e.g. the oldest 2.6 kernel a try to find a last known
good and then do a bisect upto a known bad kernel.
Folkert van Heusden
--
To MultiTail einai ena polymorfiko ergaleio gia ta logfiles kai tin
eksodo twn entolwn. Prosferei: filtrarisma, xrwmatismo, sygxwneysi,
diaforetikes provoles. http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2012-08-03 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:11 CPU: 0 Not tainted (3.1.9+ #1) when ifconfig rose0 down Bernard Pidoux
2012-07-31 15:27 ` Bernard Pidoux
2012-07-31 17:58 ` folkert
2012-08-02 23:03 ` Eric W. Biederman
2012-07-31 17:56 ` folkert
2012-08-02 22:55 ` Eric W. Biederman
2012-08-03 14:32 ` folkert [this message]
2012-08-05 16:23 ` Bernard Pidoux
2012-08-05 17:23 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2012-08-05 17:08 Folkert van Heusden
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=20120803143200.GE10211@belle.intranet.vanheusden.com \
--to=folkert@vanheusden.com \
--cc=bernard.pidoux@free.fr \
--cc=ebiederm@xmission.com \
--cc=linux-hams@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox