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 #1482: [oe]AUX bottom doesn't shine red
light while charging (Openmoko Public Trac)
2. Re: Openmoko Bug #1482: [oe]AUX bottom doesn't shine red
light while charging (Openmoko Public Trac)
3. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
4. Re: Openmoko Bug #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
5. Re: Openmoko Bug #1525: Exposure Crashes (or at least its
inaccessible) (Openmoko Public Trac)
6. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
7. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
--- Begin Message ---
#1482: [oe]AUX bottom doesn't shine red light while charging
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: julian_chu
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: must have | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by wendy_hung):
Test with the image below:
kernel:20080720-asu.stable-uImage.bin
root file system:20080721-asu.stable-rootfs.jffs2
Will happened some results as fallowing:
1) shine red light and charging icon ----> rarely happened
2) no red light but charging icon -----> almost happened every time, just
like before
3) shine red light after plug out charger/USB -----> plug in charger/USB
again red light will disappear
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1482#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1482: [oe]AUX bottom doesn't shine red light while charging
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: julian_chu
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: must have | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by andy):
Yes charging in general is royally FUBAR'd at the moment, it is getting
looked at. Whether the light is telling the truth about charging state
and it really is that bad is the question.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1482#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
-----------------------------+----------------------------------------------
Reporter: raster | Owner: andy
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by andy):
How about neod / eating 2 x 100Hz motion sensor traffic?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: ASU
Component: Xfbdev (kdrive), Xglamo | Version: unspecified
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------------------+--------------------------------------
Comment(by andy):
Last time I looked at it XGlamo has obvious problem that it cut and pasted
the kernel fb code and pressed the Super MMAP button and "did it in
Userspace": it does not cooperate with locking and modal command queue
handling in kernel world. Maybe that can make the trouble, in which case
the answer is put XGlamo guts into kernel world and talk to it on IOCTL or
something.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1525: Exposure Crashes (or at least its inaccessible)
------------------------+---------------------------------------------------
Reporter: will | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by wendy_hung):
* cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (removed)
* cc: [EMAIL PROTECTED] (added)
* status: closed => reopened
* resolution: fixed =>
Comment:
Test with the image below:
kernel:20080720-asu.stable-uImage.bin
root file system:20080721-asu.stable-rootfs.jffs2
The ghost screen happened again, this time, it bring out device crashed.
Try for many times, can not totally reproduce this, but have similar
result.
Sometimes even splinter happened, i wonder it's not a problem in illume.
please see attached photos.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1525#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
-----------------------------+----------------------------------------------
Reporter: raster | Owner: andy
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by zecke):
More likely (besides we don't have a neod running). I would have to check
if the the legacy tty handler is playing an input_handler for the motion
sensors as well. The only issue is that neod doesn't run with asu.
I have a constant load of 2.x on my neo and wonder where it comes from. I
think iotop will help me finding out (but that needs a special kernel
config).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
-----------------------------+----------------------------------------------
Reporter: raster | Owner: andy
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by andy):
About the load, update your kernel, a Jason Uhlenkott fixed it for us some
days ago
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=287b292cf95edbd82dc63085ae5f0167a6e8141f
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#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
