Openmoko Bug #2077: [FSO-testing] Module problems at boot (sysfs_add_one, bt_sock_wait_state, ...)

Openmoko Public Trac bugs at docs.openmoko.org
Wed Oct 22 11:54:09 CEST 2008


#2077: [FSO-testing] Module problems at boot (sysfs_add_one, bt_sock_wait_state,
...)
--------------------+-------------------------------------------------------
 Reporter:  erl     |          Owner:  julian_chu
     Type:  defect  |         Status:  new       
 Priority:  normal  |      Milestone:            
Component:  Distro  |        Version:            
 Severity:  normal  |       Keywords:            
 Haspatch:  0       |      Blockedby:            
Estimated:          |    Patchreview:            
 Blocking:          |   Reproducible:            
--------------------+-------------------------------------------------------
 I am running the FSO-testing distro on a Freerunner, updated with opkg
 update & upgrade today.

 At boot I get the error messages below (from dmesg).

 Andy wrote in a comment 6 weeks ago
 (https://docs.openmoko.org/trac/ticket/1841#comment:15) in bug #1841 that
 this was due to kernel/module mismatches in the distribution. This bug was
 opened to fix this.

 I'm trying to track down some audio problems, and don't know if anything
 depends on module clashes.

 dmesg:

 bluetooth: exports duplicate symbol bt_sock_wait_state (owned by kernel)
 Bluetooth: HCI USB driver ver 2.9
 usbcore: registered new interface driver hci_usb
 bluetooth: exports duplicate symbol bt_sock_wait_state (owned by kernel)
 l2cap: exports duplicate symbol l2cap_load (owned by kernel)
 Bluetooth: HIDP (Human Interface Emulation) ver 1.2
 hidp_init_sockets: Can't register HIDP socket
 [cut]
 bluetooth: exports duplicate symbol bt_sock_wait_state (owned by kernel)
 l2cap: exports duplicate symbol l2cap_load (owned by kernel)
 sysfs: duplicate filename 'rfcomm' can not be created
 WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
 [<c002e384>] (dump_stack+0x0/0x14) from [<c00d046c>]
 (sysfs_add_one+0x50/0xfc)
 [<c00d041c>] (sysfs_add_one+0x0/0xfc) from [<c00d0b68>]
 (create_dir+0x58/0xa8)
  r6:fffffff4 r5:c7da3e48 r4:c7042cf0
 [<c00d0b10>] (create_dir+0x0/0xa8) from [<c00d0bf8>]
 (sysfs_create_dir+0x40/0x60)
  r8:00000003 r7:bf0120cc r6:bf014d08 r5:bf014cc0 r4:bf014d08
 [<c00d0bb8>] (sysfs_create_dir+0x0/0x60) from [<c015e48c>]
 (kobject_add+0xf4/0x1d0)
  r4:bf014d08
 [<c015e398>] (kobject_add+0x0/0x1d0) from [<c0062398>]
 (mod_sysfs_setup+0x28/0xb4)
 [<c0062370>] (mod_sysfs_setup+0x0/0xb4) from [<c00635b8>]
 (sys_init_module+0xf90/0x14bc)
  r8:c886e88c r7:c886ea6c r6:bf014cc0 r5:00000000 r4:bf0120cc
 [<c0062628>] (sys_init_module+0x0/0x14bc) from [<c0029f40>]
 (ret_fast_syscall+0x0/0x2c)
 kobject_add failed for rfcomm with -EEXIST, don't try to register things
 with the same name in the same directory.
 [<c002e384>] (dump_stack+0x0/0x14) from [<c015e51c>]
 (kobject_add+0x184/0x1d0)
 [<c015e398>] (kobject_add+0x0/0x1d0) from [<c0062398>]
 (mod_sysfs_setup+0x28/0xb4)
 [<c0062370>] (mod_sysfs_setup+0x0/0xb4) from [<c00635b8>]
 (sys_init_module+0xf90/0x14bc)
  r8:c886e88c r7:c886ea6c r6:bf014cc0 r5:00000000 r4:bf0120cc
 [<c0062628>] (sys_init_module+0x0/0x14bc) from [<c0029f40>]
 (ret_fast_syscall+0x0/0x2c)
 snd: exports duplicate symbol snd_add_device_sysfs_file (owned by kernel)
 snd_page_alloc: exports duplicate symbol snd_free_pages (owned by kernel)
 snd_timer: exports duplicate symbol snd_timer_interrupt (owned by kernel)
 snd_pcm: exports duplicate symbol snd_pcm_notify (owned by kernel)
 snd_soc_core: exports duplicate symbol snd_soc_put_volsw_2r (owned by
 kernel)
 snd_soc_s3c24xx: exports duplicate symbol s3c24xx_soc_platform (owned by
 kernel)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2077>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the buglog mailing list