From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: 394742@bugs.debian.org
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] crash logs with a kernel.org 2.6.18.2
Date: Wed, 8 Nov 2006 14:57:01 +0200 [thread overview]
Message-ID: <20061108125701.GA10813@nalle> (raw)
Hello,
I can reproduce this with the latest from kernel.org too. Here are the
logs:
http://kapsi.fi/mcfrisk/temp/bt_oops.txt
-Mikko
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-11-08 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 12:57 Mikko Rapeli [this message]
2006-11-10 7:36 ` [Bluez-devel] Bug#394742: crash logs with a kernel.org 2.6.18.2 maximilian attems
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=20061108125701.GA10813@nalle \
--to=mikko.rapeli@iki.fi \
--cc=394742@bugs.debian.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