Hi All,
First I did not tried 2.5.73 vanilla so this can be a bug in 2.5.73 itself .
When I use my 56k modem to connect to internet it always hang up 5-6 minutes
( sometimes like 1-2 minutes ) later. I checked with 2.5.72-mm1 and I got not
hang-up whatsoever. I checked system logs and it just says :
[pppd] Modem Hang Up
Anyone noticed this behaviour?
Regards,
/ismail
On Tue, 24 Jun 2003 21:02:49 +0300, "ismail (cartman) donmez" <[email protected]> said:
> Hi All,
>
> First I did not tried 2.5.73 vanilla so this can be a bug in 2.5.73 itself .
> When I use my 56k modem to connect to internet it always hang up 5-6 minutes
> ( sometimes like 1-2 minutes ) later. I checked with 2.5.72-mm1 and I got not
> hang-up whatsoever. I checked system logs and it just says :
>
> [pppd] Modem Hang Up
2.5.72-mm3 is fine for modem usage for me.
2.5.73-mm1 threw this all 3 times I tried starting PPPD:
Jun 24 22:37:48 turing-police pppd[1144]: Using interface ppp0
Jun 24 22:37:48 turing-police pppd[1144]: Connect: ppp0 <--> /dev/ttyS14
Jun 24 22:37:49 turing-police pppd[1144]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed88e38> <pcomp> <accomp>]
Jun 24 22:37:49 turing-police pppd[1144]: Modem hangup
Jun 24 22:37:49 turing-police pppd[1144]: Connection terminated.
i.e. it died a quick and horrid death. I've not checked a plain 2.5.73 yet,
but I suspect this is the most likely culprit:
# ChangeSet 1.1348.1.42 -> 1.1348.1.43
# drivers/net/pppoe.c 1.31 -> 1.32
# drivers/net/ppp_generic.c 1.33 -> 1.34
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/06/23 [email protected] 1.1348.1.43
# [NET]: Convert PPPoE to new style protocol.
# --------------------------------------------
(if only because it's the only changeset that hits ppp_generic.c between
the known good and known bad versions). If a clean 2.5.73 works, then
reverting this cset is probably the best place to start looking...
On Tue, 24 Jun 2003 23:27:57 EDT, [email protected] said:
Reverting this one cset makes the modem work for me under 2.5.73-mm1.
With it in place, pppd hung up before even finishing the option
negotiations. With it reverted, it's staying up. There's apparently
something subtly wrong with the part that hits ppp_generic.c, although
I admit not understanding enough to see exactly what.
> # ChangeSet 1.1348.1.42 -> 1.1348.1.43
> # drivers/net/pppoe.c 1.31 -> 1.32
> # drivers/net/ppp_generic.c 1.33 -> 1.34
> #
> # The following is the BitKeeper ChangeSet Log
> # --------------------------------------------
> # 03/06/23 [email protected] 1.1348.1.43
> # [NET]: Convert PPPoE to new style protocol.
> # --------------------------------------------
On Wednesday 25 June 2003 06:27, you wrote:
> 2.5.73-mm1 threw this all 3 times I tried starting PPPD:
>
> Jun 24 22:37:48 turing-police pppd[1144]: Using interface ppp0
> Jun 24 22:37:48 turing-police pppd[1144]: Connect: ppp0 <--> /dev/ttyS14
> Jun 24 22:37:49 turing-police pppd[1144]: sent [LCP ConfReq id=0x1
> <asyncmap 0x0> <magic 0x9ed88e38> <pcomp> <accomp>] Jun 24 22:37:49
> turing-police pppd[1144]: Modem hangup
> Jun 24 22:37:49 turing-police pppd[1144]: Connection terminated.
>
Yes same messages.
> i.e. it died a quick and horrid death. I've not checked a plain 2.5.73
> yet, but I suspect this is the most likely culprit:
>
> # ChangeSet 1.1348.1.42 -> 1.1348.1.43
> # drivers/net/pppoe.c 1.31 -> 1.32
> # drivers/net/ppp_generic.c 1.33 -> 1.34
> #
> # The following is the BitKeeper ChangeSet Log
> # --------------------------------------------
> # 03/06/23 [email protected] 1.1348.1.43
> # [NET]: Convert PPPoE to new style protocol.
> # --------------------------------------------
>
Nice hope its fixed in -mm2
Regards,
/ismail
[email protected] wrote:
>On Tue, 24 Jun 2003 21:02:49 +0300, "ismail (cartman) donmez" <[email protected]> said:
>
>
>>Hi All,
>>
>>First I did not tried 2.5.73 vanilla so this can be a bug in 2.5.73 itself .
>>When I use my 56k modem to connect to internet it always hang up 5-6 minutes
>>( sometimes like 1-2 minutes ) later. I checked with 2.5.72-mm1 and I got not
>>
>>
>
>
>
>>hang-up whatsoever. I checked system logs and it just says :
>>
>>[pppd] Modem Hang Up
>>
>>
>
>2.5.72-mm3 is fine for modem usage for me.
>
>2.5.73-mm1 threw this all 3 times I tried starting PPPD:
>
>Jun 24 22:37:48 turing-police pppd[1144]: Using interface ppp0
>Jun 24 22:37:48 turing-police pppd[1144]: Connect: ppp0 <--> /dev/ttyS14
>Jun 24 22:37:49 turing-police pppd[1144]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed88e38> <pcomp> <accomp>]
>Jun 24 22:37:49 turing-police pppd[1144]: Modem hangup
>Jun 24 22:37:49 turing-police pppd[1144]: Connection terminated.
>
>i.e. it died a quick and horrid death. I've not checked a plain 2.5.73 yet
>
I get the same issue in mm1, haven't tried vanilla either.
On Wed, 25 Jun 2003 00:18:31 -0400
[email protected] wrote:
> On Tue, 24 Jun 2003 23:27:57 EDT, [email protected] said:
>
> Reverting this one cset makes the modem work for me under 2.5.73-mm1.
> With it in place, pppd hung up before even finishing the option
> negotiations. With it reverted, it's staying up. There's apparently
> something subtly wrong with the part that hits ppp_generic.c, although
> I admit not understanding enough to see exactly what.
How far along did pppd get before it hung up? Was the ppp0 netdevice still
around (ifconfig -a)? I'll try a dedicated serial line and see if I can reproduce
it.
On Wednesday 25 June 2003 19:10, Stephen Hemminger wrote:
> On Wed, 25 Jun 2003 00:18:31 -0400
>
> [email protected] wrote:
> > On Tue, 24 Jun 2003 23:27:57 EDT, [email protected] said:
> >
> > Reverting this one cset makes the modem work for me under 2.5.73-mm1.
> > With it in place, pppd hung up before even finishing the option
> > negotiations. With it reverted, it's staying up. There's apparently
> > something subtly wrong with the part that hits ppp_generic.c, although
> > I admit not understanding enough to see exactly what.
>
> How far along did pppd get before it hung up?
For me its random between 1-5 minutes.
Regards,
/ismail
On Wed, 25 Jun 2003 09:10:13 PDT, Stephen Hemminger said:
> How far along did pppd get before it hung up? Was the ppp0 netdevice still
> around (ifconfig -a)? I'll try a dedicated serial line and see if I can reproduce
For me, it didn't even finish negotiating the connection:
Jun 24 22:37:48 turing-police pppd[1144]: Using interface ppp0
Jun 24 22:37:48 turing-police pppd[1144]: Connect: ppp0 <--> /dev/ttyS14
Jun 24 22:37:49 turing-police pppd[1144]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed88e38> <pcomp> <accomp>]
Jun 24 22:37:49 turing-police pppd[1144]: Modem hangup
Jun 24 22:37:49 turing-police pppd[1144]: Connection terminated.
I'm assuming the netdevice was there when it said 'Using interface'. It was
certainly gone by the time I was able to do ifconfig or 'ip link show' or
anything like that. ismail reports "several minutes" - I'm wondering it the
bug is in pskb_may_pull() being handed an oodd packet-of-death that I receive
during startup but ismail gets later on. There's comments in the patch about
making sure the decompressor is linear, but in my case the LCP stuff isn't even
negotiating compression. Uninitialized variable?
[email protected] wrote:
>On Wed, 25 Jun 2003 09:10:13 PDT, Stephen Hemminger said:
>
>
>
>>How far along did pppd get before it hung up? Was the ppp0 netdevice still
>>around (ifconfig -a)? I'll try a dedicated serial line and see if I can reproduce
>>
>>
>
>For me, it didn't even finish negotiating the connection:
>
>
Same here.
>Jun 24 22:37:48 turing-police pppd[1144]: Using interface ppp0
>Jun 24 22:37:48 turing-police pppd[1144]: Connect: ppp0 <--> /dev/ttyS14
>Jun 24 22:37:49 turing-police pppd[1144]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9ed88e38> <pcomp> <accomp>]
>Jun 24 22:37:49 turing-police pppd[1144]: Modem hangup
>Jun 24 22:37:49 turing-police pppd[1144]: Connection terminated.
>
Same message too. I tried connecting several times with the same
results (thought it might
have been the provider).
>I'm assuming the netdevice was there when it said 'Using interface'. It was
>certainly gone by the time I was able to do ifconfig or 'ip link show' or
>anything like that. ismail reports "several minutes" - I'm wondering it the
>bug is in pskb_may_pull() being handed an oodd packet-of-death that I receive
>during startup but ismail gets later on. There's comments in the patch about
>making sure the decompressor is linear, but in my case the LCP stuff isn't even
>negotiating compression. Uninitialized variable?
>
>
>