Messages in this thread | | | Date | Fri, 15 Aug 2008 17:11:55 +0200 | From | "Vegard Nossum" <> | Subject | 2.6.25.11-97.fc9 (P): idr_remove called for id=236 which is not allocated |
| |
Hi,
First the confessions: It's fedora-patched kernel, 2.6.25.11-97.fc9, tainted by NVIDIA driver. So feel free to drop to /dev/null until I can reproduce on a clean and recent kernel. (But -rc3 didn't boot for me, and I don't have anything else handy atm.)
By bashing on random device nodes (with mknod + mmap as root), I got a few messages of this kind:
idr_remove called for id=236 which is not allocated. Pid: 3019, comm: a.out Tainted: P 2.6.25.11-97.fc9.i686 #1 [<c04f030c>] idr_remove+0xd5/0x138 [<c0540bfc>] release_dev+0x5bd/0x5cf [<c04909fd>] ? d_free+0x3b/0x4d [<c04955d0>] ? mntput_no_expire+0x16/0x69 [<c048309d>] ? __fput+0x149/0x151 [<c0540d8c>] tty_release+0x12/0x1c [<c0483001>] __fput+0xad/0x151 [<c04830bc>] fput+0x17/0x19 [<c04807df>] filp_close+0x50/0x5a [<c0480852>] sys_close+0x69/0xa1 [<c0405bf2>] syscall_call+0x7/0xb [<c0620000>] ? agp_amd64_probe+0x134/0x3ee =======================
idr_remove called for id=127 which is not allocated. Pid: 3019, comm: a.out Tainted: P 2.6.25.11-97.fc9.i686 #1 [<c04f030c>] idr_remove+0xd5/0x138 [<c0540bfc>] release_dev+0x5bd/0x5cf [<c04909fd>] ? d_free+0x3b/0x4d [<c04955d0>] ? mntput_no_expire+0x16/0x69 [<c048309d>] ? __fput+0x149/0x151 [<c0540d8c>] tty_release+0x12/0x1c [<c0483001>] __fput+0xad/0x151 [<c04830bc>] fput+0x17/0x19 [<c04807df>] filp_close+0x50/0x5a [<c0480852>] sys_close+0x69/0xa1 [<c0405bf2>] syscall_call+0x7/0xb =======================
It looks scary. Or is it purely my own fault?
Thanks,
Vegard
-- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036
| |