Badness in device_release at drivers/base/core.c:84

From: Diffie (diffie@blazebox.homeip.net)
Date: Fri Aug 01 2003 - 13:22:07 EST

Hello folks,

Under 2.6.0-test2-mm2 keeps getting Badness in device_release at
drivers/base/core.c:84 when loading USB modules on NFORCE2 based board.

uname: Linux blaze 2.6.0-test2-mm2 #1 Thu Jul 31 13:11:05 EDT 2003 i686
unknown on Linux Slackware 9.0, GCC 3.2.2

Device '' does not have a release() function, it is broken and must be
fixed.
Badness in device_release at drivers/base/core.c:84
Call Trace:
[<c021dfd8>] kobject_cleanup+0x88/0x90
[<c02c03ff>] hub_port_connect_change+0x2af/0x330
[<c02bfcfd>] hub_port_status+0x3d/0xb0
[<c02c07bd>] hub_events+0x33d/0x3b0
[<c02c0865>] hub_thread+0x35/0xf0
[<c011b810>] default_wake_function+0x0/0x30
[<c02c0830>] hub_thread+0x0/0xf0
[<c01070c9>] kernel_thread_helper+0x5/0xc
                   
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x501
Device '' does not have a release() function, it is broken and
must be fixed.
Badness in device_release at drivers/base/core.c:84
Call Trace:
[<c021dfd8>] kobject_cleanup+0x88/0x90
[<c02c03ff>] hub_port_connect_change+0x2af/0x330
[<c02bfcfd>] hub_port_status+0x3d/0xb0
[<c02c07bd>] hub_events+0x33d/0x3b0
[<c02c0865>] hub_thread+0x35/0xf0
[<c011b810>] default_wake_function+0x0/0x30
[<c02c0830>] hub_thread+0x0/0xf0
[<c01070c9>] kernel_thread_helper+0x5/0xc
                                          
hub 1-0:0: debounce: port 3: delay 100ms stable 4 status
0x501
Device '' does not have a release() function, it is
broken and must be fixed.
Badness in device_release at drivers/base/core.c:84
Call Trace:
[<c021dfd8>] kobject_cleanup+0x88/0x90
[<c02c03ff>] hub_port_connect_change+0x2af/0x330
[<c02bfcfd>] hub_port_status+0x3d/0xb0
[<c02c07bd>] hub_events+0x33d/0x3b0
[<c02c0865>] hub_thread+0x35/0xf0
[<c011b810>] default_wake_function+0x0/0x30
[<c02c0830>] hub_thread+0x0/0xf0
[<c01070c9>] kernel_thread_helper+0x5/0xc

Also keep getting oops in radeon module:

[drm] Loading R200 Microcode
Unable to handle kernel NULL pointer dereference at virtual address 00000120
printing eip:
c02a8cae
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<c02a8cae>] Not tainted VLI
EFLAGS: 00210286
EIP is at aic7xxx_proc_info+0x2e/0xc80
eax: c1bb25b0 ebx: c1bb2400 ecx: c038bb20 edx: 00000000
esi: 00000400 edi: f1715000 ebp: 412de000 esp: f620fecc
ds: 007b es: 007b ss: 0068
Process nautilus (pid: 3555, threadinfo=f620e000 task=f6216720)
Stack: 000001f7 00000000 00000000 c013c612 c0379eb0 00000000 00000000 f6613340
       00000000 00000000 c0379eb0 00000400 00000400 f1715000 412de000 c02956fc
       c1bb2400 f1715000 f620ff60 00000000 00000400 00000000 c02956c0 c018bc91
Call Trace:
[<c013c612>] __alloc_pages+0x92/0x320
[<c02956fc>] proc_scsi_read+0x3c/0x60
[<c02956c0>] proc_scsi_read+0x0/0x60
[<c018bc91>] proc_file_read+0xd1/0x280
[<c015617c>] vfs_read+0xbc/0x130
[<c0156452>] sys_read+0x42/0x70
[<c01091f7>] syscall_call+0x7/0xb
Code: 53 83 ec 2c a1 b8 a6 38 c0 89 44 24 20 8b 98 20 01 00 00 85 db 74
1e 8d b6 00 00 00 00 8b 54 24 20 8b 92 1c 01 00 00 89 54 24 20 <8b> 8a
20 01 00 00 85 c9 75 e8 8b 54 24 20 85 d2 0f 84 e4 0b 00

There also seems to be a problem with SCSI subsystem where /dev/sda
devices are labeled as /dev/sdb as seen in the dmesg.txt attached file.

Regards,

Paul B.





-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:17 EST