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 #2264: Heavy GPRS traffic causes a Calypso
crash (Openmoko Public Trac)
2. Re: Openmoko Bug #2344: early WSOD with linux 2.6.32 and Qi
(Openmoko Public Trac)
3. Openmoko Bug #2367: Restore Bluetooth state on resume
(Openmoko Public Trac)
4. Openmoko Bug #2368: Please integrate DRM/KMS support
(Openmoko Public Trac)
5. Re: Openmoko Bug #2349: Too high power consumption in 2.6.32
(Openmoko Public Trac)
6. Re: Openmoko Bug #2367: Restore Bluetooth state on resume
(Openmoko Public Trac)
7. Re: Openmoko Bug #2264: Heavy GPRS traffic causes a Calypso
crash (Openmoko Public Trac)
8. Re: Openmoko Bug #2264: Heavy GPRS traffic causes a Calypso
crash (Openmoko Public Trac)
9. Re: Openmoko Bug #2367: Restore Bluetooth state on resume
(Openmoko Public Trac)
--- Begin Message ---
#2264: Heavy GPRS traffic causes a Calypso crash
----------------------------+-----------------------------------------------
Reporter: budfive | Type: defect
Status: new | Priority: normal
Milestone: | Component: GSM Modem
Version: unspecified | Severity: normal
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
----------------------------+-----------------------------------------------
Comment(by lindi):
Uploading data with netcat caused me to hit this again and again. Using
tc qdisc add dev ppp0 root tbf rate 2kbit latency 50ms burst 1600
seems to have so far helped. Can everyone who is suffering from this bug
try this please? (It does limit your outgoing traffic considerably but
that might just be the price for stability)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2264#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2344: early WSOD with linux 2.6.32 and Qi
--------------------+-------------------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version:
Severity: major | Keywords: wsod 2.6.32
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
--------------------+-------------------------------------------------------
Comment(by TimoJyrinki):
WSOD fixing patches:
http://github.com/radekp/linux-2.6/commit/98c3c2082a601d3982f73c0e83ac0748d781be2e
http://github.com/radekp/linux-2.6/commit/b76e1206d85e7ae984bc2dcb9f91b74d5b41f4b0
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2344#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2367: Restore Bluetooth state on resume
-------------------------+--------------------------------------------------
Reporter: TimoJyrinki | Owner: Nytowl
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Bluetooth state is not restored during resume.
The patch at
http://github.com/radekp/linux-2.6/commit/00875594c874c4ef32637e0bb08f040ea0b13408
should fix the problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2367>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2368: Please integrate DRM/KMS support
-------------------------+--------------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: kernel | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Please integrate DRM/KMS support for the 2.6.34 (or newer) kernel at
git.openmoko.org.
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux
/linux-openmoko-2.6.34 - the following patches:
0001-DRM-for-platform-devices.patch
0001-glamo-display-Enable-FIFO-stage-for-the-LCD-engine-s.patch
0002-Glamo-DRM-and-KMS-driver.patch
0003-Work-on-Glamo-core-for-DRM.patch
0004-JBT6k74-work-for-KMS.patch
0005-Fix-dynamic-command-queue-allocation.patch
0006-Debug-statements-for-testing.patch
0007-Fix-claim-of-2D-register-resource.patch
0008-Use-unlocked_ioctl-rather-than-ioctl.patch
0009-glamo-display-fix-WSOD-for-242-timming.patch
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2368>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2349: Too high power consumption in 2.6.32
----------------------+-----------------------------------------------------
Reporter: Q-Master | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: kernel | Version:
Severity: major | Keywords:
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Changes (by TimoJyrinki):
* haspatch: 0 => 1
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2349#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2367: Restore Bluetooth state on resume
-------------------------+--------------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Changes (by TimoJyrinki):
* owner: Nytowl => openmoko-kernel
* component: Distro => kernel
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2367#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2264: Heavy GPRS traffic causes a Calypso crash
----------------------------+-----------------------------------------------
Reporter: budfive | Type: defect
Status: new | Priority: normal
Milestone: | Component: GSM Modem
Version: unspecified | Severity: normal
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
----------------------------+-----------------------------------------------
Comment(by lindi):
I sent UDP packets at regular intervals and wrote down how it affects the
calypso system:
size(bytes) interval(msec) result
1000 1000 ok
1000 500 crash
1000 750 crash
1000 900 crash
500 500 ok
250 250 ok
130 130 crash
It seems that we can sustain 1000 bytes per second but trying to go faster
causes calypso to crash. This probably means that setting "rate" in the
above tc command to anything higher than say "7kbit" probably allows
normal users to crash calypso.
I'm currently testing with
$ cat /etc/ppp/ip-up.d/09lindi-tc
#!/bin/sh
/sbin/tc qdisc add dev ppp0 root tbf rate 7kbit latency 4500ms burst 3200
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2264#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2264: Heavy GPRS traffic causes a Calypso crash
----------------------------+-----------------------------------------------
Reporter: budfive | Type: defect
Status: new | Priority: normal
Milestone: | Component: GSM Modem
Version: unspecified | Severity: normal
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
----------------------------+-----------------------------------------------
Comment(by TimoJyrinki):
With quick testing I can confirm that lindi's tc command improves GPRS
usability tremendously. I'm now browsing google maps with full javascript
and images and SSHing to a server running irssi at the same time,
something which is on the heavy side and has tended to always crash the
GSM before.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2264#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2367: Restore Bluetooth state on resume
-------------------------+--------------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by psonek):
I have patch in qtmoko which saves bluetooth in variable and restores it
after suspend:
http://github.com/radekp/linux-2.6/commit/00875594c874c4ef32637e0bb08f040ea0b13408
Works good for me, as a benefit it avoids reading pin from hardware.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2367#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
