From: Stefan Rompf <srompf@isg.de>
To: David Brownell <david-b@pacbell.net>
Cc: netdev@oss.sgi.com
Subject: Re: 2.5.50 BUG_TRAP on !dev->deadbeaf, and oopses
Date: Sun, 01 Dec 2002 13:45:06 +0100 [thread overview]
Message-ID: <3DEA0452.B1F15BFD@isg.de> (raw)
In-Reply-To: 3DE9290A.7070502@pacbell.net
Hi,
David Brownell wrote:
> KERNEL: assertion (!dev->deadbeaf) failed at net/core/dev.c(2544)
>
> I think there's another bug, beyond the obvious speling erorz. Namely,
> that "deadbeaf" is only set after that BUG_TRAP, or on one error path.
> The assertion prevents hotpluggable network drivers from unregistering
> when the hardware goes away ... which is a regression.
actually, the assertion is triggered when someone tries to unregister a
netdevice twice, and that's also why you get
> unregister_netdevice: device /dfd74058 never was registered
>From a short browsing through usb.c I don't see a similiar bug catcher
in usb_device_remove(), so have a look if the USB subsystem itself
removes a unplugged device
twice for some reason.
Stefan
next prev parent reply other threads:[~2002-12-01 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 21:09 2.5.50 BUG_TRAP on !dev->deadbeaf, and oopses David Brownell
2002-12-01 12:45 ` Stefan Rompf [this message]
2002-12-02 18:44 ` David Brownell
2002-12-08 22:42 ` David Brownell
2002-12-09 19:51 ` David Brownell
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=3DEA0452.B1F15BFD@isg.de \
--to=srompf@isg.de \
--cc=david-b@pacbell.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).