From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Subject: Fw: BUG: atomic counter underflow when running "rmmod tg3" on 2.6.10-rc1-mm3
Date: Mon, 8 Nov 2004 21:41:59 -0800 [thread overview]
Message-ID: <20041108214159.6400e8de.akpm@osdl.org> (raw)
There's a debug patch in -mm which generates a trace when someone does
atomic_dec_and_test() on an atomic_t which already has a value of zero.
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/broken-out/detect-atomic-counter-underflows.patch
It looks like it has found a problem in qdisc_destroy().
Begin forwarded message:
Date: Tue, 9 Nov 2004 03:33:36 +0100
From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: linux-kernel@vger.kernel.org
Subject: BUG: atomic counter underflow when running "rmmod tg3" on 2.6.10-rc1-mm3
BUG: atomic counter underflow at:
[<c02882f6>] qdisc_destroy+0x66/0x80
[<c02885e2>] dev_shutdown+0x32/0x90
[<c02d796f>] __down_failed_trylock+0x7/0xc
[<c027b6b2>] unregister_netdevice+0x142/0x29e
[<c014c171>] handle_mm_fault+0xf1/0x510
[<c0240a95>] unregister_netdev+0x15/0x20
[<e0d3a2b5>] tg3_remove_one+0x25/0x70 [tg3]
[<c01db4e9>] pci_device_remove+0x69/0x70
[<c0232646>] device_release_driver+0x86/0x90
[<c0232a2b>] bus_remove_driver+0x5b/0x100
[<e0d3a780>] tg3_cleanup+0x0/0x13 [tg3]
[<c0232fc0>] driver_unregister+0x10/0x20
[<c01db234>] pci_unregister_driver+0x14/0xa0
[<e0d3a78f>] tg3_cleanup+0xf/0x13 [tg3]
[<c013462b>] sys_delete_module+0x17b/0x1e0
[<c0104ff1>] sysenter_past_esp+0x52/0x71
divert: freeing divert_blk for eth0
next reply other threads:[~2004-11-09 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 5:41 Andrew Morton [this message]
2004-11-09 5:51 ` Fw: BUG: atomic counter underflow when running "rmmod tg3" on 2.6.10-rc1-mm3 Patrick McHardy
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=20041108214159.6400e8de.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bero@arklinux.org \
--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).