From: Christian Reiser <r.christian@gmx.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Suspend locks up usb
Date: Tue, 23 Aug 2005 17:57:50 +0200 [thread overview]
Message-ID: <430B477E.4050503@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0508230921130.9834@Magrathea>
Hi Marcel,
Marcel Holtmann wrote:
> I can't tell you anything about the APM. Did you tried to use ACPI?
Sorry, this is a Thinkpad 600e (400 Mhz, PII). APM is working well -
ACPI won't.
> What kernel version is this?
Linux version 2.6.12-mh2
> However to unload you module you need to do a "hciconfig hci0 down"
> first. This will deactivate the interface.
Okay - did not know this. But it does not entirely solve my problem. The
bluetooth modules can be unloaded after executing hciconfig - USB is
still dead. Syslog:
Aug 23 10:20:35 alpha uhci_hcd 0000:00:07.2: Unlink after no-IRQ?
Controller is probably using the wrong IRQ.
Aug 23 10:20:41 alpha usbcore: deregistering driver hci_usb
Anyway. I borrowed an USB-Memorydevice and suspended... same problem.
So: This is not a bluez-bug.
============================
Sorry Guys - i will look for the USB-developers list ;-)
Thanks for your help && Ciao
Christian
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2005-08-23 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.63.0508230921130.9834@Magrathea>
2005-08-23 15:57 ` Christian Reiser [this message]
2005-08-21 13:58 [Bluez-devel] Suspend locks up usb Christian Reiser
2005-08-22 11:15 ` Marcel Holtmann
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=430B477E.4050503@gmx.de \
--to=r.christian@gmx.de \
--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