From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] rfcomm socket and rfcomm tty
Date: Wed, 05 Jan 2005 16:15:25 +0800 [thread overview]
Message-ID: <41DBA21D.7010707@avantwave.com> (raw)
In-Reply-To: <1104839485.8894.88.camel@pegasus>
Dear Marcel
It is 2.6.5, which is default kernel of Fedora 2.
Does it the problem on kernel?Actually, i really no idea for that.
best regard
Mike,Lee
Marcel Holtmann wrote:
>Hi Mike,
>
>
>
>> Actually, i have tried to connect to Window base computer and test
>>with hyperterminal . my program does success in connection and send out
>>data. But when i try to connect to rfcomm listen in another computer, it
>>comes out a oops. and then my usb dongle halt and need a OS reboot.
>> Do you have any idea on below oops? Thanks for helping
>>
>>------------[ cut here ]------------
>>kernel BUG at include/linux/module.h:325!
>>invalid operand: 0000 [#1]
>>CPU: 0
>>EIP: 0060:[<129d25e1>] Not tainted
>>EFLAGS: 00010246 (2.6.5-1.358)
>>EIP is at rfcomm_session_add+0x73/0x88 [rfcomm]
>>eax: 00000000 ebx: 0e63a984 ecx: 00000000 edx: 11ee5400
>>esi: 00000002 edi: 0e63a9b0 ebp: 0bda8080 esp: 0e283fa4
>>ds: 007b es: 007b ss: 0068
>>Process krfcommd (pid: 1835, threadinfo=0e283000 task=10ee39b0)
>>Stack: 128daba0 0bda8080 0a7e1800 0397c91c 129d3b29 029d91a8 129d84f0
>>00000000
>> 0e283000 00000000 0e283fde 00000000 129d3f49 00000000 00000000
>>0000007b
>> 0000007b 129d3ef1 00000000 021041d9 00000000 00000000 00000000
>>Call Trace:
>> [<129d3b29>] rfcomm_worker+0x10b/0x3a6 [rfcomm]
>> [<129d3f49>] rfcomm_run+0x58/0x6b [rfcomm]
>> [<129d3ef1>] rfcomm_run+0x0/0x6b [rfcomm]
>> [<021041d9>] kernel_thread_helper+0x5/0xb
>>
>>Code: 0f 0b 45 01 ff 5f 9d 12 ff 05 00 89 9d 12 89 d8 5b 5e 5f 5d
>>
>>
>
>what kernel is this? Try the latest one.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-05 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 9:03 [Bluez-devel] rfcomm socket and rfcomm tty mike
2004-12-29 10:25 ` Marcel Holtmann
2004-12-30 1:55 ` mike
2005-01-01 18:42 ` Marcel Holtmann
2005-01-03 7:15 ` mike
2005-01-03 9:51 ` Marcel Holtmann
2005-01-04 7:32 ` mike
2005-01-04 11:51 ` Marcel Holtmann
2005-01-05 8:15 ` mike [this message]
2005-01-05 11:39 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 18:49 omap
2005-01-03 18:54 ` Marcel Holtmann
2005-01-03 19:12 omap
2005-01-03 19:52 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41DBA21D.7010707@avantwave.com \
--to=mikelee@avantwave.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.