All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Voluspa <lista4@comhem.se>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0
Date: Sun, 22 Aug 2004 17:50:19 +0200	[thread overview]
Message-ID: <4128C0BB.9060503@trash.net> (raw)
In-Reply-To: <200408221504.i7MF4Z719895@d1o404.telia.com>

Voluspa wrote:

>Greetings,
>
>NOTE
>I wrote the text below just prior to the posting of
>01-2.6-cbq-leaks.diff but applying it doesn't change the
>situation here. I still get the same Oops as below. Slight
>changes in memory address but the Call Trace is identical.
>So, different problem?
>ENDNOTE
>
Yes, your problem is a different one, but looks related to
the one in the thread "Oops: Process zebra, EIP is at
fib_create_info+0x22b/0x580".

Regards
Patrick

  reply	other threads:[~2004-08-22 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 15:04 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 Voluspa
2004-08-22 15:50 ` Patrick McHardy [this message]
2004-08-23 17:11 ` Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23 22:31 Voluspa

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=4128C0BB.9060503@trash.net \
    --to=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lista4@comhem.se \
    --cc=netdev@oss.sgi.com \
    /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.