From: Marcel Holtmann <marcel@holtmann.org>
To: Geert Geurts <geert@ebm.nl>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] sendmsg: No buffer space available
Date: Tue, 23 Mar 2004 00:25:31 +0100 [thread overview]
Message-ID: <1079997930.2663.290.camel@pegasus> (raw)
In-Reply-To: <1079973771.5419.24.camel@geert.ebm.nl>
Hi Geert,
> Hello, I've got a problem with my usb-dongle...
> as soon as I put request too much traffic over ppp (a webpage is too
> much, ping is no problem) the connection is broken...
> when I try to ping over the ppp after I got the timeout on my palm, I
> get sendmsg: No buffer space available
> when I do the same when I didn't get the timeout message yet I get a
> normal reply...
>
> I found out that I have the same problem when I try connecting via
> normal cradle/cable...
> no matter witch speed I set! well tried 19200 without success...
>
> I'm using gentoo linux
> devfs and usbfs
> 2.4.23-ck3-mh2 kernel
> bluez-kernel-2.3
> bluez-libs-2.4
> bluez-pan-1.1
> bluez-sdp-1.5
> bluez-utils-2.3-r1
don't use bluez-kernel-2.3, because my latest -mh patch should be
enough.
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-22 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 16:42 [Bluez-users] sendmsg: No buffer space available Geert Geurts
2004-03-22 23:25 ` 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=1079997930.2663.290.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=geert@ebm.nl \
/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;
as well as URLs for NNTP newsgroup(s).