Bug#266674: kernel: Confirmed on 2.6.11

[Filipus Klutiero <cheal@hotpop.com>]

Package: kernel
Followup-For: Bug #266674

I am again experiencing this on 2.6.11-1-k7 2.6.11-2.

Device 'vesafb0' does not have a release() function, it is broken and
must be fixed.
Badness in device_release at drivers/base/core.c:85
 [<c01b2628>] kobject_cleanup+0x98/0xa0
 [<c01b2630>] kobject_release+0x0/0x10
 [<c01b30d9>] kref_put+0x39/0xa0
 [<c01b265e>] kobject_put+0x1e/0x30
 [<c01b265e>] kobject_put+0x1e/0x30
 [<c01b2630>] kobject_release+0x0/0x10
 [<d08022bf>] vesafb_exit+0xf/0x1f [vesafb]
 [<c012e129>] sys_delete_module+0x159/0x190
 [<c01457e0>] sys_munmap+0x50/0x80
 [<c0103003>] syscall_call+0x7/0xb

Note that this doesn't happen on my main PC. Being quite clueless about
kernels, feel free to request more info if needed.
-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-k7
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)