[Voyage-linux] kobject (cec84330): tried to init an initialized object, something is seriously wrong

[Kim-man 'Punky' TSE]

Hi all,

May be you can blacklist the xpp-usb modules and try.

Regards,
Punky

rodney at optimail.com.au wrote:
> Jean-Pierre,
>
>  I have a similar problem (usb links dropping out regularly) when using
> the Sierra Wireless MC8790, and another user reported a similar problem
> when using the Sierra Wireless MC8775.
>
>  This problem occurs with Voyage 0.6.x and not with Voyage 0.5.x or with
> Zeroshell linux.
>
>  By stopping the udev daemon, it is found that any udev/hotplug messages
> are a result of the problem, not the cause of the problem.
>
>  My suspicion is usbserial.ko, the USB serial generic driver, maybe
> doesn't handle an interrupt correctly.
>  Haven't had time to check the source code for what changed.
>
>
> Rodney
>
>   
>>    1. kobject (cec84330): tried to init an initialized object,
>>       something is seriously wrong (Jean-Pierre Schwickerath)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 20 Apr 2009 18:40:03 +0200
>> From: Jean-Pierre Schwickerath <voyage at hilotec.com>
>> Subject: [Voyage-linux] kobject (cec84330): tried to init an
>> 	initialized object, something is seriously wrong
>> To: voyage-linux at voyage.hk
>> Message-ID: <20090420184003.30138f88 at ws007.hilotec.lan>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hello
>>
>>
>> I'm testing the update to voyage 0.6.1 from a 0.5.2 setup where I run
>> asterisk with a Xorcom USB 4BRI connected to an Alix-Board.
>>
>> I made a fresh install of 0.6.1 and installed zaptel_1.4.11~dfsg-3_i386
>>
>> When I connect the astribank I get a scary message:
>>
>> Zaptel Version: 1.4.11
>> Zaptel Echo Canceller: MG2
>> ztdummy: Trying to load High Resolution Timer
>> ztdummy: Initialized High Resolution Timer
>> ztdummy: Starting High Resolution Timer
>> ztdummy: High Resolution Timer started, good to go
>> eth0: no IPv6 routers present
>> usb 2-1: new high speed USB device using ehci_hcd and address 2
>> usb 2-1: configuration #1 chosen from 1 choice
>> usb 2-1: USB disconnect, address 2
>> usb 2-1: new high speed USB device using ehci_hcd and address 3
>> usb 2-1: configuration #1 chosen from 1 choice
>> usb 2-1: USB disconnect, address 3
>> usb 2-1: new high speed USB device using ehci_hcd and address 4
>> usb 2-1: configuration #1 chosen from 1 choice
>> INFO-xpp: revision trunk-r5744 MAX_XPDS=64 (8*8)
>> INFO-xpp: FEATURE: with BRISTUFF support
>> INFO-xpp: FEATURE: with PROTOCOL_DEBUG
>> INFO-xpp: FEATURE: with ECHO_SUPPRESSION
>> INFO-xpp: FEATURE: without XPP_EC_CHUNK
>> INFO-xpp: FEATURE: with sync_tick() from ZAPTEL
>> INFO-xpp_usb: revision trunk-r5744
>> usb 2-1: reset high speed USB device using ehci_hcd and address 4
>> INFO-xpp_usb: XUSB: Xorcom LTD -- Astribank -- FPGA
>> INFO-xpp: XBUS-00: [] Activating
>> usbcore: registered new interface driver xpp_usb
>> INFO-xpp: XBUS-00: DESCRIPTOR: 1 cards, protocol revision 30
>> INFO-xpp: XBUS-00:     CARD 0 type=3.0 ports=4 (1x4), port-dir=0xFC
>> INFO-xpd_bri: revision trunk-r5744
>> INFO-xpp: XBUS-00/XPD-00: Initialized: BRI_TE
>> INFO-xpp: XBUS-00/XPD-01: Initialized: BRI_TE
>> INFO-xpp: XBUS-00/XPD-02: Initialized: BRI_NT
>> INFO-xpp: XBUS-00/XPD-03: Initialized: BRI_NT
>> kobject (cec84330): tried to init an initialized object, something is
>> seriously wrong. Pid: 3739, comm: XBUS-00 Not tainted 2.6.26-486-voyage
>> #1 [<c01e0115>] kobject_init+0x29/0x69
>>  [<c0217967>] device_initialize+0x18/0x84
>>  [<c0218042>] device_register+0x8/0x10
>>  [<d08e9a64>] xbus_sysfs_create+0x8a/0x13b [xpp]
>>  [<d08e8f37>] xbus_populate+0x439/0x4a7 [xpp]
>>  [<d08e8afe>] xbus_populate+0x0/0x4a7 [xpp]
>>  [<c011f4ef>] run_workqueue+0x83/0x11b
>>  [<c011f8b1>] worker_thread+0x7c/0x87
>>  [<c0122044>] autoremove_wake_function+0x0/0x2d
>>  [<c011f835>] worker_thread+0x0/0x87
>>  [<c0121cb0>] kthread+0x36/0x5a
>>  [<c0121c7a>] kthread+0x0/0x5a
>>  [<c0103c27>] kernel_thread_helper+0x7/0x10
>>  =======================
>>
>>
>> I tried various firmwares (those of zaptel 1.4.11 and 1.4.12) but
>> the kernel dump persists. I also noticed a few lock ups of the whole
>> system after plugin in the astribank.
>>
>> Which part is broken? The kernel itself or the zaptel drivers? Or is
>> the firmware not compatible with the 2.6.26 interfaces?
>>
>> Does someone have a hint where I should start fixing the issue?
>>
>>
>> Regards
>>
>> Jean-Pierre
>>
>> --
>> HILOTEC Engineering + Consulting AG - Langnau im Emmental
>> Energietechnik und Datensysteme: Server, PCs, Linux, Telefonanlagen,
>> VOIP, Hosting, Datenbanken, Entwicklung, Komplettlösungen für KMUs
>> Tel: +41 34 402 74 00 - http://www.hilotec.com/
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>>
>> End of Voyage-linux Digest, Vol 52, Issue 24
>> ********************************************
>>
>>     
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>   


-- 
Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
  - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
  - Network Engineering, Development Platform and Consultation