Red Hat Bugzilla – Bug 198753
ppp dies almost instantly when uploading data
Last modified: 2008-02-05 08:34:54 EST
Description of problem:
pppd dies almost instantly when uploading data.
10-20kB can be uploaded but bigger files hangups.
Sometimes also after surfing the connection gets jammed and
when trying to ping the ping tells the following:
ping: sendmsg: No buffer space available
And after that connection needs to be restarted.
Version-Release number of selected component (if applicable):
pppd: pppd version 2.4.3
KDE: 3.5.2-0.1.fc5 Red Hat
Steps to Reproduce:
1. Open Internet connection
2. Upload something
ppp dies with hangup
Extra information in attachment (debug info, strace)...
Created attachment 132358 [details]
Card information, pcmcia information, dmesg, messages, debug, strace
And I forgot to mention, I've tested with some usual kernel parameters which
could help. Machine is Fujitsu-Siemens C-Series (C1320D) laptop.
Tried parameters: acpi=off noapic pci=routeirq
One thing about noapic makes me wonder, it still says:
"Found and enabled local APIC"
But no help with those.
Something more still:
Works nicely with old Option Globetrotter same operator and sim card
and v2 model of Vodafode branded Globetrotter (v1 has broken .cis and don't know
how to put valid when card is inserted with fc5 new system).
Operator has told that their system doesn't see anything wrong.
I were told that this isn't ppp's fault, and i were thinking that the problem
lies somewhere in the kernel.. But maybe not then..
Continue my efforts to make it work..
Is the pppd server dying?
Can you please start the pppd server in gdb and get a traceback? It would help
if you install the pppd-debuginfo package for this.
Ok, used gdb and well ppp don't die, no core, no backtrace.
It just gets the "SIGHUP" -> Hangup from somewhere..
This seems to be a kernel problem. Assigning to kernel.
I have a similar problem in my FC-5 system: my ADSL connection freezes a couple
of seconds after establishing a successful connection.
This only happens with the 2.6.17 update kernels; no problems with previous ones
(2.6.16). Right now I using the kernel 2.6.16-1.2133_FC5.
ADSL USB modem: Tompshon SpeedTouch 330.
(In reply to comment #7)
> I have a similar problem in my FC-5 system: my ADSL connection freezes a couple
> of seconds after establishing a successful connection.
> This only happens with the 2.6.17 update kernels; no problems with previous ones
> (2.6.16). Right now I using the kernel 2.6.16-1.2133_FC5.
> ADSL USB modem: Tompshon SpeedTouch 330.
It now works with kernel 2.6.17-1.2174_FC5.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.
Closing since there was an error in previous mass-close and they remained in