Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2223: gsm0710muxd loosing packets?
(Openmoko Public Trac)
2. Re: Openmoko Bug #2223: gsm0710muxd loosing packets?
(Openmoko Public Trac)
3. Re: Openmoko Bug #2073: voice-recording.state + arecord:
Unable to handle kernel NULL pointer dereference at virtual
address 00000000 (Openmoko Public Trac)
4. Re: Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
5. Re: Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
6. Re: Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
7. Re: Openmoko Bug #2223: gsm0710muxd loosing packets?
(Openmoko Public Trac)
--- Begin Message ---
#2223: gsm0710muxd loosing packets?
------------------------+---------------------------------------------------
Reporter: kapiteined | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------+---------------------------------------------------
Comment(by kapiteined):
Hi mickey,
I did flash it. the flashing worked alright.
But the problem with the gprs connection is still there.
I make two logs, bad.log and good.log
with bad.log i use the /dev/pts/2 i get from the gsm0710muxd.
If i start pinging with larger packets ping times go up until the pings
stop.
with the good.log i use /dev/ttySAC0, after killing gsm0710muxd and qpe.
as you can see, the pingtimes are stable and not increasing much this
time.
it still seems that i have high(er) packetloss when using gsm0710muxd.
and if parts of the retransmits are
lost too, i have retransmit on retransmit, until the connection chokes.
Thanks for the help so far !
Kind regards,
Ed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2223#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2223: gsm0710muxd loosing packets?
------------------------+---------------------------------------------------
Reporter: kapiteined | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------+---------------------------------------------------
Comment(by mickey):
This is with using my new multiplexer fso-abyss:
r...@om-gta02:~# ping -s 1400 heise.de
PING heise.de (193.99.144.80): 1400 data bytes
1408 bytes from 193.99.144.80: seq=0 ttl=242 time=2521.968 ms
1408 bytes from 193.99.144.80: seq=1 ttl=242 time=2409.901 ms
1408 bytes from 193.99.144.80: seq=4 ttl=242 time=2801.211 ms
1408 bytes from 193.99.144.80: seq=5 ttl=242 time=2875.850 ms
1408 bytes from 193.99.144.80: seq=6 ttl=242 time=2401.183 ms
1408 bytes from 193.99.144.80: seq=7 ttl=242 time=1841.451 ms
1408 bytes from 193.99.144.80: seq=9 ttl=242 time=2391.964 ms
1408 bytes from 193.99.144.80: seq=10 ttl=242 time=2490.054 ms
1408 bytes from 193.99.144.80: seq=12 ttl=242 time=2407.468 ms
1408 bytes from 193.99.144.80: seq=13 ttl=242 time=2511.972 ms
1408 bytes from 193.99.144.80: seq=14 ttl=242 time=2332.015 ms
1408 bytes from 193.99.144.80: seq=15 ttl=242 time=2651.661 ms
1408 bytes from 193.99.144.80: seq=16 ttl=242 time=2761.595 ms
1408 bytes from 193.99.144.80: seq=17 ttl=242 time=2410.165 ms
1408 bytes from 193.99.144.80: seq=18 ttl=242 time=1848.718 ms
1408 bytes from 193.99.144.80: seq=20 ttl=242 time=2410.162 ms
1408 bytes from 193.99.144.80: seq=21 ttl=242 time=2891.949 ms
1408 bytes from 193.99.144.80: seq=23 ttl=242 time=2511.832 ms
1408 bytes from 193.99.144.80: seq=24 ttl=242 time=2647.290 ms
1408 bytes from 193.99.144.80: seq=25 ttl=242 time=2418.948 ms
1408 bytes from 193.99.144.80: seq=26 ttl=242 time=2434.499 ms
1408 bytes from 193.99.144.80: seq=29 ttl=242 time=2356.914 ms
1408 bytes from 193.99.144.80: seq=30 ttl=242 time=2422.326 ms
1408 bytes from 193.99.144.80: seq=31 ttl=242 time=1886.346 ms
1408 bytes from 193.99.144.80: seq=33 ttl=242 time=2420.823 ms
1408 bytes from 193.99.144.80: seq=34 ttl=242 time=2430.039 ms
1408 bytes from 193.99.144.80: seq=36 ttl=242 time=2516.453 ms
1408 bytes from 193.99.144.80: seq=37 ttl=242 time=2585.322 ms
1408 bytes from 193.99.144.80: seq=38 ttl=242 time=2393.405 ms
1408 bytes from 193.99.144.80: seq=39 ttl=242 time=2758.472 ms
1408 bytes from 193.99.144.80: seq=40 ttl=242 time=3319.996 ms
1408 bytes from 193.99.144.80: seq=41 ttl=242 time=2646.584 ms
1408 bytes from 193.99.144.80: seq=42 ttl=242 time=2393.595 ms
1408 bytes from 193.99.144.80: seq=43 ttl=242 time=2394.847 ms
1408 bytes from 193.99.144.80: seq=46 ttl=242 time=3319.976 ms
1408 bytes from 193.99.144.80: seq=47 ttl=242 time=2982.334 ms
1408 bytes from 193.99.144.80: seq=48 ttl=242 time=2654.863 ms
1408 bytes from 193.99.144.80: seq=49 ttl=242 time=2396.831 ms
1408 bytes from 193.99.144.80: seq=50 ttl=242 time=2415.035 ms
1408 bytes from 193.99.144.80: seq=53 ttl=242 time=1925.361 ms
1408 bytes from 193.99.144.80: seq=54 ttl=242 time=2395.551 ms
1408 bytes from 193.99.144.80: seq=55 ttl=242 time=1767.319 ms
1408 bytes from 193.99.144.80: seq=57 ttl=242 time=2397.221 ms
1408 bytes from 193.99.144.80: seq=58 ttl=242 time=2485.213 ms
1408 bytes from 193.99.144.80: seq=60 ttl=242 time=2384.111 ms
1408 bytes from 193.99.144.80: seq=61 ttl=242 time=2322.923 ms
1408 bytes from 193.99.144.80: seq=62 ttl=242 time=2315.131 ms
1408 bytes from 193.99.144.80: seq=63 ttl=242 time=2384.892 ms
1408 bytes from 193.99.144.80: seq=64 ttl=242 time=2389.788 ms
1408 bytes from 193.99.144.80: seq=65 ttl=242 time=2419.811 ms
1408 bytes from 193.99.144.80: seq=68 ttl=242 time=1900.657 ms
1408 bytes from 193.99.144.80: seq=69 ttl=242 time=2410.158 ms
1408 bytes from 193.99.144.80: seq=70 ttl=242 time=1810.339 ms
1408 bytes from 193.99.144.80: seq=72 ttl=242 time=2415.057 ms
1408 bytes from 193.99.144.80: seq=73 ttl=242 time=2411.042 ms
We're releasing milestone 5.1 in a couple of days which will ship it
(albeit disabled by default, still using gsm0710muxd), so please have a go
with that one.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2223#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2073: voice-recording.state + arecord: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: ALSA
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Changes (by arhuaco):
* owner: openmoko-devel => openmoko-kernel
* haspatch: 1 => 0
* component: unknown => System Software
Comment:
Replying to [comment:16 PaulFertser]:
> Please don't do both.
>
> As now Mark Brown has finally received a GTA02 he is the most likely to
fix any remaining breakage. I also studied the datasheet and the sources
and now feel more confident with these issues, but fixing everything
properly needs time.
Great. Not many people in this galaxy know how to fix this!
This is a very nice report you wrote. Now I'm jet-lagged as hell thus I
will read it carefully tomorrow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2073#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface
flags:
No such device
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
How has this issue ended up... WLAN can start OK now after resume or is
there still an issue?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface
flags:
No such device
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Haven't heard anyone complain about suspend/resume for a good while.
I think lindi only saw the effect of using power_on, which didn't do
at all what he expected. So this one may be resolve/invalid.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface
flags:
No such device
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution: invalid
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => invalid
Comment:
Great, thanks.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2223: gsm0710muxd loosing packets?
------------------------+---------------------------------------------------
Reporter: kapiteined | Owner: Nytowl
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------+---------------------------------------------------
Comment(by kapiteined):
> This is with using my new multiplexer fso-abyss:
>
> r...@om-gta02:~# ping -s 1400 heise.de
> PING heise.de (193.99.144.80): 1400 data bytes
> 1408 bytes from 193.99.144.80: seq=0 ttl=242 time=2521.968 ms
> 1408 bytes from 193.99.144.80: seq=1 ttl=242 time=2409.901 ms
Missing reply 2 and 3
> 1408 bytes from 193.99.144.80: seq=4 ttl=242 time=2801.211 ms
> 1408 bytes from 193.99.144.80: seq=5 ttl=242 time=2875.850 ms
> 1408 bytes from 193.99.144.80: seq=6 ttl=242 time=2401.183 ms
> 1408 bytes from 193.99.144.80: seq=7 ttl=242 time=1841.451 ms
8 is also missing
> 1408 bytes from 193.99.144.80: seq=9 ttl=242 time=2391.964 ms
> 1408 bytes from 193.99.144.80: seq=10 ttl=242 time=2490.054 ms
And so is 11
> 1408 bytes from 193.99.144.80: seq=12 ttl=242 time=2407.468 ms
> 1408 bytes from 193.99.144.80: seq=13 ttl=242 time=2511.972 ms
> 1408 bytes from 193.99.144.80: seq=14 ttl=242 time=2332.015 ms
> 1408 bytes from 193.99.144.80: seq=15 ttl=242 time=2651.661 ms
> 1408 bytes from 193.99.144.80: seq=16 ttl=242 time=2761.595 ms
> 1408 bytes from 193.99.144.80: seq=17 ttl=242 time=2410.165 ms
> 1408 bytes from 193.99.144.80: seq=18 ttl=242 time=1848.718 ms
hey 19 is gone
> 1408 bytes from 193.99.144.80: seq=20 ttl=242 time=2410.162 ms
> 1408 bytes from 193.99.144.80: seq=21 ttl=242 time=2891.949 ms
what happened to 22?
> 1408 bytes from 193.99.144.80: seq=23 ttl=242 time=2511.832 ms
> 1408 bytes from 193.99.144.80: seq=24 ttl=242 time=2647.290 ms
> 1408 bytes from 193.99.144.80: seq=25 ttl=242 time=2418.948 ms
> 1408 bytes from 193.99.144.80: seq=26 ttl=242 time=2434.499 ms
27 and 28 on a holiday?
> 1408 bytes from 193.99.144.80: seq=29 ttl=242 time=2356.914 ms
etc
As you can see, some replies are lost, and because i build a ssh tunnel
(tcp) over the grps connection it will cause a retransmit.
And this will acumulate over time if the retransmits also loose packets.
i think that is why my ping times are increasing to the point where it
stops.
Kind regards,
Ed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2223#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
