From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Kernel Oops while transmitting data on several RFCOMMlinks
Date: Thu, 26 Jul 2007 16:30:54 +0200 [thread overview]
Message-ID: <1185460255.7111.140.camel@violet> (raw)
In-Reply-To: <46A8A7C1.1050200@idlum.be>
Hi Pierre-Yves,
> After upgrading to kernel 2.6.21-2 (in fact, the
> linux-image-2.6.21-2-486_2.6.21-5_i386.deb package from debian
> unstable), I performed some new tests, and it happened again.
>
> Please find attached what I got in the logs. What's wrong here? I will
> gladly perform any test or action which you may ask to help track the
> problem down. Just ask.
that is not the latest upstream kernel. Try 2.6.23-rc1.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-26 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070709093602.A2C6B58D565@mailflip16.edt02.net>
2007-07-10 10:15 ` [Bluez-devel] Kernel Oops while transmitting data on several RFCOMM links Pierre-Yves Paulus
2007-07-10 11:54 ` [Bluez-devel] Kernel Oops while transmitting data on several RFCOMMlinks Williams, Richard
2007-07-11 9:36 ` Pierre-Yves Paulus
2007-07-26 13:55 ` Pierre-Yves Paulus
2007-07-26 14:30 ` Marcel Holtmann [this message]
2007-09-14 17:04 ` Pierre-Yves Paulus
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=1185460255.7111.140.camel@violet \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox