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. Openmoko Bug #2266: xf86-video-glamo fills xdm.log with
GLAMOExaPrepareSolid: Only 16bpp is supported (Openmoko Public Trac)
2. Openmoko Bug #2267: [wifi] kernel oops when starting
wpa_supplicant (Openmoko Public Trac)
3. Openmoko Bug #2268: Alignment trap: Xglamo (Openmoko Public Trac)
4. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
5. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
6. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
7. Re: Openmoko Bug #2264: Heavy GPRS traffic causes a Calypso
crash (Openmoko Public Trac)
8. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
--- Begin Message ---
#2266: xf86-video-glamo fills xdm.log with GLAMOExaPrepareSolid: Only 16bpp is
supported
-----------------------------+----------------------------------------------
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:
-----------------------------+----------------------------------------------
[I sent this by email to lars last month but just to make sure I don't
forget it here's a bug report as well]
after running xf86-video-glamo for a while (it seems to be quite
stable!) I noticed that my /var/log/xdm.log now has 46 megabytes of
the line
GLAMOExaPrepareSolid: Only 16bpp is supported
Can you ratelimit this a bit? Maybe it should only be printed the
first time?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2266>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2267: [wifi] kernel oops when starting wpa_supplicant
---------------------+------------------------------------------------------
Reporter: tilman2 | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
I'm running shr-unstable from April 9th:
http://build.shr-project.org/shr-unstable/images/om-gta02/openmoko-shr-
lite-image-glibc-ipk--20090409-om-gta02.rootfs.jffs2
http://build.shr-project.org/shr-unstable/images/om-
gta02/uImage-2.6.28-oe1+gitr119783+901d73fe51f33032b34b2ae5612eb863ec90532a-r3.1
-om-gta02.bin
The kernel version reported is 2.6.29-rc3.
When starting wpa_supplicant, the kernel oopses. I'll attach the output of
dmesg and my wpa_supplicant.conf.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2267>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2268: Alignment trap: Xglamo
----------------------+-----------------------------------------------------
Reporter: xbaldauf | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
Hello,
from time to time, I experience alignment traps on my Freerunner,
involving various binaries. I'm not sure whether this is a result of a bug
in the software which is trapping, a bug in the kernel I'm running
(2.6.29-GTA02_stable-t-mokodev) or a hardware defect. This time, Xglamo
crashed, but the remaining system remained stable.
r...@om-gta02:~# dmesg | grep Xglamo
[ 5116.140000] Alignment trap: Xglamo (1510) PC=0x40283fc4
Instr=0xe5846008 Address=0xfc610007 FSR 0x803
r...@om-gta02:~# md5sum $(which Xglamo)
3ddb5f186f92e6a6f56eb923732bf7dc /usr/bin/Xglamo
r...@om-gta02:~#
I have not yet found a reliable way to reproduce this type of bug.
I know that it may be hard to analyze this bug (given this little
information), but maybe other people who have the same problem gravitate
to this ticket and can contribute useful information.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2268>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by joerg):
Dieter reported some finding about an out-of-mem freeze in firmware which
he thinks might be caused by a memleak.
Dieter, please have a look into this as well. Thanks
/j
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by BillK):
Flashed shr-unstable last night (built locally - 10th April) - 2.6.29
kernel
Never was able to talk to the GSM over many attempts using the mux - often
got this error:
Apr 10 19:43:59 om-gta02 user.debug kernel: [ 185.015000] modem wakeup
interrupt
Apr 10 19:44:04 om-gta02 user.debug kernel: [ 189.830000] rxerr: port=0
ch=0x00, rxs=0x0000000c
Apr 10 19:44:04 om-gta02 user.debug kernel: [ 190.075000] modem wakeup
interrupt
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by PaulFertser):
BillK, please try lindi's command from the bug description (to connect
with socat). If it works, please provide an strace log of a successful
attempt.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:16>
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 dieter):
This bug is caused because the GSM firmware is out of memory and asserts
(stops). Most certainly there is a memory leak somewhere. The problem:
Openmoko does not have the source code of the GSM stack and this is most
certainly the place where the memory leak occurs. The entities of the GSM
stack communicate by sending messages, the memory for those messages is
dynamically allocated and (hopefully) freed again. I will see what can be
done, but I can't estimate yet how long it takes to fix it (if possible at
all).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2264#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by arhuaco):
I'll start testing this bug.
# cd /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-gsm.
# echo 0 > power_on; sleep 3; echo 1 > power_on; echo 1 > reset
# socat - file:/dev/ttySAC0,crtscts,crnl,b115200
ATZ
(No reply, strace shows: select(16, [0 3], [], [], NULL).
It's the first time I talk to the modem in the GTA02. I should have
received a reply from the modem, right?
BTW, I didn't get any reply with b8b36e5ec3db71d5. Do I need to enable
echo?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
