Linux 2.6.9: Badness in __vunmap at mm/vmalloc.c:315 and some following oopses...

[Marc Schiffbauer]

Hi kernel folks,

i got some oopses while playing with my ipw2100 wireless card
(trying to load/unload driver)

are these oopses of any use to debug for you guys?
please tell we if I can provide further information to track this
down.


Full output is here (about 70k):
http://www.links2linux.de/tmp/2.6.9_oopses


It starts like this:
Oct 28 23:06:31 localhost kernel: Trying to vfree() nonexistent vm area (f8fa9000)
Oct 28 23:06:31 localhost kernel: Badness in __vunmap at mm/vmalloc.c:315
Oct 28 23:06:31 localhost kernel:  [vfree+39/53] vfree+0x27/0x35
Oct 28 23:06:31 localhost kernel:  [fw_realloc_buffer+154/202] fw_realloc_buffer+0x9a/0xca
Oct 28 23:06:31 localhost kernel:  [firmware_data_write+150/235] firmware_data_write+0x96/0xeb
Oct 28 23:06:31 localhost kernel:  [flush_write+58/66] flush_write+0x3a/0x42
Oct 28 23:06:31 localhost kernel:  [write+204/232] write+0xcc/0xe8
Oct 28 23:06:31 localhost kernel:  [write+0/232] write+0x0/0xe8
Oct 28 23:06:31 localhost kernel:  [vfs_write+176/281] vfs_write+0xb0/0x119
Oct 28 23:06:31 localhost kernel:  [sys_write+81/128] sys_write+0x51/0x80
Oct 28 23:06:31 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Oct 28 23:06:31 localhost kernel: Badness in map_area_pte at mm/vmalloc.c:100
Oct 28 23:06:31 localhost kernel:  [map_area_pte+153/155] map_area_pte+0x99/0x9b
Oct 28 23:06:31 localhost kernel:  [map_area_pmd+111/151] map_area_pmd+0x6f/0x97
Oct 28 23:06:31 localhost kernel:  [map_vm_area+97/171] map_vm_area+0x61/0xab
Oct 28 23:06:31 localhost kernel:  [__vmalloc+225/279] __vmalloc+0xe1/0x117
Oct 28 23:06:31 localhost kernel:  [vmalloc+32/36] vmalloc+0x20/0x24
Oct 28 23:06:31 localhost kernel:  [fw_realloc_buffer+69/202] fw_realloc_buffer+0x45/0xca
Oct 28 23:06:31 localhost kernel:  [firmware_data_write+150/235] firmware_data_write+0x96/0xeb
Oct 28 23:06:31 localhost kernel:  [flush_write+58/66] flush_write+0x3a/0x42
Oct 28 23:06:31 localhost kernel:  [write+204/232] write+0xcc/0xe8
Oct 28 23:06:31 localhost kernel:  [write+0/232] write+0x0/0xe8
Oct 28 23:06:31 localhost kernel:  [vfs_write+176/281] vfs_write+0xb0/0x119
Oct 28 23:06:31 localhost kernel:  [sys_write+81/128] sys_write+0x51/0x80
Oct 28 23:06:31 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Oct 28 23:06:31 localhost kernel: Badness in map_area_pte at mm/vmalloc.c:100
Oct 28 23:06:31 localhost kernel:  [map_area_pte+153/155] map_area_pte+0x99/0x9b
Oct 28 23:06:31 localhost kernel:  [map_area_pmd+111/151] map_area_pmd+0x6f/0x97
Oct 28 23:06:31 localhost kernel:  [map_vm_area+97/171] map_vm_area+0x61/0xab
Oct 28 23:06:31 localhost kernel:  [__vmalloc+225/279] __vmalloc+0xe1/0x117
Oct 28 23:06:31 localhost kernel:  [vmalloc+32/36] vmalloc+0x20/0x24
Oct 28 23:06:31 localhost kernel:  [fw_realloc_buffer+69/202] fw_realloc_buffer+0x45/0xca
Oct 28 23:06:31 localhost kernel:  [firmware_data_write+150/235] firmware_data_write+0x96/0xeb
Oct 28 23:06:31 localhost kernel:  [flush_write+58/66] flush_write+0x3a/0x42
Oct 28 23:06:31 localhost kernel:  [write+204/232] write+0xcc/0xe8
Oct 28 23:06:31 localhost kernel:  [write+0/232] write+0x0/0xe8
Oct 28 23:06:31 localhost kernel:  [vfs_write+176/281] vfs_write+0xb0/0x119
Oct 28 23:06:31 localhost kernel:  [sys_write+81/128] sys_write+0x51/0x80
Oct 28 23:06:31 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Oct 28 23:06:31 localhost kernel: Unable to handle kernel paging request at virtual address 00100100
Oct 28 23:06:31 localhost kernel:  printing eip:
Oct 28 23:06:31 localhost kernel: c015aefa
Oct 28 23:06:31 localhost kernel: *pde = 00000000
Oct 28 23:06:31 localhost kernel: Oops: 0000 [#1]

-marc
-- 
+------------------------------------------------------------------+
|              --> http://www.links2linux.de <--                   |
|                                                                  |
+---Registered-Linux-User-#136487------------http://counter.li.org +
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/