From: Vladislav Malyshkin <mal@gromco.com>
To: linux-kernel@vger.kernel.org
Subject: kernel-2.6.18-1.2200 trace
Date: Thu, 19 Oct 2006 03:42:22 -0400 [thread overview]
Message-ID: <45372C5E.8060601@gromco.com> (raw)
I have a strange trace during dmesg on kernel-2.6.18-1.2200
idr_remove called for id=1 which is not allocated.
[<c0403f10>] dump_trace+0x69/0x1af
[<c040406e>] show_trace_log_lvl+0x18/0x2c
[<c04045e9>] show_trace+0xf/0x11
[<c0404673>] dump_stack+0x15/0x17
[<c04d3fcb>] idr_remove+0xe2/0x143
[<c051ee50>] release_dev+0x63b/0x652
[<c051ee6e>] tty_release+0x7/0xa
[<c0461b2e>] __fput+0xba/0x178
[<c045f466>] filp_close+0x52/0x59
[<c041d3b4>] put_files_struct+0x64/0xa6
[<c041e3fe>] do_exit+0x248/0x747
[<c041e973>] sys_exit_group+0x0/0xd
[<f5d480e4>] 0xf5d480e4
DWARF2 unwinder stuck at 0xf5d480e4
Leftover inexact backtrace:
[<c0426b76>] get_signal_to_deliver+0x38a/0x3b2
[<c040243a>] do_notify_resume+0x75/0x62f
[<c044bfc0>] __pagevec_lru_add_active+0x95/0xa0
[<c042c814>] autoremove_wake_function+0x0/0x35
[<c05fc113>] _spin_unlock_irq+0x5/0x7
[<c05fa9cf>] schedule+0x529/0x585
[<c0402e2a>] work_notifysig+0x13/0x19
=======================
eth1: link down.
eth1: link up.
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211429 for
details of this bug.
reply other threads:[~2006-10-19 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45372C5E.8060601@gromco.com \
--to=mal@gromco.com \
--cc=linux-kernel@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 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.