All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hciattach problem
Date: Fri, 04 Feb 2005 13:46:22 +0100	[thread overview]
Message-ID: <1107521182.6921.12.camel@pegasus> (raw)
In-Reply-To: <42036A83.8090309@web.de>

Hi Andreas,

> I have also a Problem with hciattach. As written in a Thread befor a kill of hciattach causes a System freez. Also the System hangs, when I want to shutdown the System at shuting down PCMCIA. I have tested with different kernels an bluez-utils/lib versions. I have found out, that with kernel 2.6.10 and bluez-utils/lib 2.14 the problem isn't there. With patch mh1 it works also. But with patch mh2 or kernel 2.6.11-rc2 or with kernel 2.6.10 and utils/lib 2.15 the freez is also there. I have a 3com Version 3 PCMCIA Card.

please check if the bluez-utils version really matters.

So the bad patch is between 2.6.10-mh1 and 2.6.10-mh2 and the 3Com
version 3 card is using BCSP, right?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-02-04 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 12:28 [Bluez-devel] hciattach problem Andreas Millinger
2005-02-04 12:46 ` 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=1107521182.6921.12.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 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.