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 #1767: Enlightenment Error (Openmoko Public Trac)
2. Re: Openmoko Bug #2133: kmmcd: page allocation failure.
order:4, mode:0xd0 (Openmoko Public Trac)
3. Re: Openmoko Bug #2133: kmmcd: page allocation failure.
order:4, mode:0xd0 (Openmoko Public Trac)
4. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
5. Re: Openmoko Bug #1850: qtopia datebook does not raise alarm
(Openmoko Public Trac)
6. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
7. Re: Openmoko Bug #1392: ar6000: switching wifi modes does not
work (Openmoko Public Trac)
8. Re: Openmoko Bug #1767: Enlightenment Error (Openmoko Public Trac)
--- Begin Message ---
#1767: Enlightenment Error
---------------------------+------------------------------------------------
Reporter: ssweeny | Owner: john_lee
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: E - Illume | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------+------------------------------------------------
Comment(by Benson):
Any news on this? Getting the same SIGABRT message on om-testing! I get it
even when doing nothing or entering a menu in the illume settings...
[EMAIL PROTECTED]:~# /etc/X11/Xserver
*** glibc detected *** enlightenment: realloc(): invalid next size:
0x003be640 ***}}}
Switching to software_x engine solves the problem, but it's much slower
than software_16_x. Is there no way you can reproduce it? Might
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1767#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2133: kmmcd: page allocation failure. order:4, mode:0xd0
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: minor | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by werner):
If you could reproduce the old problem easily, then it would be nice if
you
could test the patch. If that was just a once-in-a-lifetime occurrence,
then I think we should just put it into *-tracking and be done with it.
In the unlikely event that anyone has code that uses Atheros' raw
interface,
it would of course be very interesting to see if I didn't break it.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2133#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2133: kmmcd: page allocation failure. order:4, mode:0xd0
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: minor | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by lindi):
I do not know how to reproduce this but I'll report here if I can figure
it out.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2133#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by gomez):
Hi,
same phenomenon here! it seems that the heat from itself while the display
was just blanked was enough with normal temperature (like 20°C), but as it
got colder i got this problem even if just blanked.
{{{
cat /proc/cpuinfo
Hardware : GTA02
Revision : 0350
Serial : 0000000000000000
}}}
{{{
>>> gsmdevice.GetInfo()
{ 'imei': '354651011613199',
'manufacturer': 'FIC/OpenMoko',
'model': '"Neo1973 GTA02 Embedded GSM Modem"',
'revision': '"HW: GTA02BV5, GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8"'}
}}}
will do more tests if needed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:72>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1850: qtopia datebook does not raise alarm
---------------------------------------------+------------------------------
Reporter: mkluge | Owner: tick
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: normal | Resolution: duplicate
Keywords: qtopia datebook missed alarm | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
---------------------------------------------+------------------------------
Changes (by tick):
* status: assigned => closed
* resolution: => duplicate
Comment:
dulplicated to #1822 close it
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1850#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
Ok, I think we are very close to a solution. I've disable deep sleep in
the JBT driver, checked the suspend still works for the rest of the driver
(around 20 sleep, unsleep), put it to sleep, put it in the freezer for 20
minutes, took out and waked up, no WSOD. I've put back the unpatched
kernel, did same thing, got a WSOD. There is definitely something wrong
about this driver.
From that point without the datasheet (under NDA) it will be hard to
continu, and to make sure we doing things right. Whatever how bad the
datasheet are (as mentionned on the dev mailing list), the ones who has it
will figure out the bug quicker than me. I'm going to post my patch, so
other people can reproduce. Note that I have no idea what effect this
patch may have on power consumption or anything else you could think of.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:73>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1392: ar6000: switching wifi modes does not work
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
------------------------------------+---------------------------------------
Changes (by werner):
* haspatch: => 0
Comment:
Only found this report recently, sorry. The "essid off" was the clue I
needed.
Patch ar6k-disconnect-more-often.patch should solve this problem:
http://lists.openmoko.org/pipermail/openmoko-
kernel/2008-November/006847.html
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1392#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1767: Enlightenment Error
------------------------+---------------------------------------------------
Reporter: ssweeny | Owner: john_lee
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: E - Illume | Version: Om2008.8
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------+---------------------------------------------------
Comment(by john_lee):
upstream mainly works on software_x and illume-theme-illume, so this
combination is known to work. if you prefer to use upstream illume theme,
please switch to software_x engine. since asu theme seems to work with
software_16, fixing this is low priority at the moment.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1767#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
