Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Re: Re: hciattach problem
Date: Thu, 10 Feb 2005 21:00:58 +0100	[thread overview]
Message-ID: <1108065658.15974.126.camel@pegasus> (raw)
In-Reply-To: <420BBA0B.5090405@web.de>

Hi Andreas,

> >please try 2.6.11-rc3-bk7 and what does "modinfo bluetooth" say?
> modinfo bluetooth:
> filename:       /lib/modules/2.6.10-mh3/kernel/net/bluetooth/bluetooth.ko
> author:         Maxim Krasnyansky <maxk@qualcomm.com>, Marcel Holtmann 
> <marcel@holtmann.org>
> description:    Bluetooth Core ver 2.7
> version:        2.7
> license:        GPL
> alias:          net-pf-31
> vermagic:       2.6.10-mh3 PENTIUMIII REGPARM gcc-3.3
> depends:
> srcversion:     DAE2F0A0D8CBDE079A024DB
> 
> I will try 2.6.11-rc3-bk7.

so no SMP and no PREEMPT. This means that this can't be a deadlock and
there should be no problem, but you can try to disable the REGPARM.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-02-10 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 19:46 [Bluez-devel] Re: Re: Re: hciattach problem Andreas Millinger
2005-02-10 20:00 ` Marcel Holtmann [this message]

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=1108065658.15974.126.camel@pegasus \
    --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