All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: maxk@qualcomm.com, bluez-devel@lists.sourceforge.net,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [oops] in bluetooth
Date: Fri, 18 May 2007 16:19:48 +0200	[thread overview]
Message-ID: <1179497988.10069.198.camel@violet> (raw)
In-Reply-To: <20070518141342.GA3692@elf.ucw.cz>

Hi Pavel,

> I played with rfcomm here -- I'm trying to emulate bluetooth gps using
> normal pc -- and got couple of oopses.
> 
> pavel@amd:~$ uname -a
> Linux amd 2.6.21 #421 SMP Fri Apr 27 15:06:54 CEST 2007 i686 GNU/Linux
> pavel@amd:~$
> 

can you try with 2.6.22-rc1. I have seen this before, but never actually
found the root cause for it. It might be inside the sysfs layer.

Regards

Marcel



  reply	other threads:[~2007-05-18 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 14:13 [oops] in bluetooth Pavel Machek
2007-05-18 14:19 ` Marcel Holtmann [this message]
2007-05-18 15:01   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2007-05-28  9:38 Andrew Ruthven
2007-05-31 17:49 ` Chuck Ebbert

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=1179497988.10069.198.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=pavel@ucw.cz \
    /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.