All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: wim delvaux <wim.delvaux@adaptiveplanet.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
Date: Mon, 12 Apr 2004 16:55:33 +0200	[thread overview]
Message-ID: <1081781733.5398.137.camel@pegasus> (raw)
In-Reply-To: <200404121621.56191.wim.delvaux@adaptiveplanet.com>

Hi Wim,

> > where do you get them? In the hci_usb driver or in the USB subsystem?
> 
> 	it scrolls by so fast that It is hardly visible on the console.
> 	However I can detect that the call stack is only 3 entries deep

try to use the netconsole support in 2.6.5.

> > Know problem. Some broken device which needs a longer timeout value.
> 
> 	The device at hand is the Acer BT500 BT Dongle  Where can I set that
> 	timeout ?

Look at the USB mailing list archive. I don't remember where it was, but
the Acer BT500 is one of these buggy dongles.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-04-12 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12  1:49 [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems wim delvaux
2004-04-12 10:55 ` Marcel Holtmann
2004-04-12 11:17   ` wim delvaux
2004-04-12 13:33     ` Marcel Holtmann
2004-04-12 14:21       ` wim delvaux
2004-04-12 14:55         ` 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=1081781733.5398.137.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=wim.delvaux@adaptiveplanet.com \
    /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.