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 #2236: GTA01 with andy-traking reporting bad
cordinates near up event (Openmoko Public Trac)
2. Re: Openmoko Bug #2236: GTA01 with andy-traking reporting bad
cordinates near up event (Openmoko Public Trac)
3. Openmoko Bug #2237: pcf50633 INT1 and INT3 flood logs with
gadgetfs keyboard (Openmoko Public Trac)
4. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
5. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
6. Openmoko Bug #2238: CONFIG_FUNCTION_TRACER panics very early
(Openmoko Public Trac)
7. Re: Openmoko Bug #2238: CONFIG_FUNCTION_TRACER panics very
early (Openmoko Public Trac)
--- Begin Message ---
#2236: GTA01 with andy-traking reporting bad cordinates near up event
-----------------------+----------------------------------------------------
Reporter: perezdiez | Owner: Nytowl
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: Distro | Version: GTA01Bv4
Severity: normal | Keywords: andy-tracking touchscreen GTA01
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------+----------------------------------------------------
First noticed on Feb 17 with kernel
0d8d2fe29182f0eaed6abbd7533d6667a5d0f42d
Tested with
http://svn.openmoko.org/developers/tick/touchtest/touch_test.py
The Up event and some times the previous Move ends near (300-575) making
the onscreen keyboard useless.
I have aplied the patch attched and the cordinates reported on Up are
nearer to the reality with and whithout the filters aplied, but I still
get some missreports.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2236>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2236: GTA01 with andy-traking reporting bad cordinates near up event
-----------------------+----------------------------------------------------
Reporter: perezdiez | Owner: Nytowl
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: Distro | Version: GTA01Bv4
Severity: normal | Keywords: andy-tracking touchscreen GTA01
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------+----------------------------------------------------
Comment(by perezdiez):
The path here is the same that the one on the kernel list
http://news.gmane.org/find-
root.php?message_id=%3ca858c7d0902210238t1ec9f644kbecc57c2aecea660%40mail.gmail.com%3e
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2236#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2237: pcf50633 INT1 and INT3 flood logs with gadgetfs keyboard
-----------------------------+----------------------------------------------
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:
-----------------------------+----------------------------------------------
Steps to reproduce:
1) connect freerunner to a PC and setup ssh access over wlan since g_ether
can not be used during test
2) tar zxf testcase1.tar.gz
3) cd testcase1
4) make
5) sudo bash setup.sh
6) sudo ./usb
Expected results:
6) freerunner shows up as a new usb keyboard on the PC side
Actual results:
6) freerunner shows up as a new usb keyboard on the PC side but on the
freerunner side it starts to flood logs with about 8 lines/second:
{{{
Feb 21 19:02:32 ginger user.info kernel: [ 288.060000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x20 INT4=0x00 INT5=0x00
Feb 21 19:02:32 ginger user.info kernel: [ 288.135000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:32 ginger user.info kernel: [ 288.155000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 288.775000] pcf50633 0-0073:
INT1=0x80 INT2=0x00 INT3=0x10 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 288.840000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 288.860000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 288.990000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x20 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 289.060000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:33 ginger user.info kernel: [ 289.080000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:34 ginger user.info kernel: [ 289.800000] pcf50633 0-0073:
INT1=0x80 INT2=0x00 INT3=0x10 INT4=0x00 INT5=0x00
Feb 21 19:02:34 ginger user.info kernel: [ 289.865000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:34 ginger user.info kernel: [ 289.885000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
Feb 21 19:02:34 ginger user.info kernel: [ 290.105000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x20 INT4=0x00 INT5=0x00
Feb 21 19:02:34 ginger user.info kernel: [ 290.175000] pcf50633 0-0073:
INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00
}}}
More info:
1) the keyboard gadget does not yet work reliably but that is not what
this bug report is about :-)
2) I am using andy-tracking b8b36e5ec3db71d5
3) udevd seems to consume 5% cpu time constantly. strace shows
{{{
--- SIGCHLD (Child exited) @ 0 (0) ---
write(7, "\0"..., 1) = 1
sigreturn() = ? (mask now [HUP QUIT ABRT BUS
USR1 SEGV PIPE ALRM TERM CHLD CONT STOP TSTP TTOU VTALRM PROF PWR SYS])
gettimeofday({1235235981, 461967}, NULL) = 0
select(7, [3 4 5 6], NULL, NULL, NULL) = 2 (in [5 6])
recv(5, "change@/class/power_supply/adapte"..., 2560, 0) = 296
gettimeofday({1235235981, 479707}, NULL) = 0
unlink("/dev/.udev/failed/\\x2fclass\\x2fpower_supply\\x2fadapter") = -1
ENOENT (No such file or directory)
rmdir("/dev/.udev/failed") = -1 ENOTEMPTY (Directory not
empty)
stat64("/dev/.udev/queue", {st_mode=S_IFDIR|0755, st_size=60, ...}) = 0
symlink("/class/power_supply/adapter", "/dev/.udev/queue/2037") = 0
open("/dev/.udev/uevent_seqnum", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE,
0644) = 8
write(8, "2037\n"..., 5) = 5
close(8) = 0
read(6, "\0"..., 256) = 1
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, NULL) = 3020
gettimeofday({1235235981, 549209}, NULL) = 0
unlink("/dev/.udev/failed/\\x2fclass\\x2fpower_supply\\x2fusb") = -1
ENOENT (No such file or directory)
rmdir("/dev/.udev/failed") = -1 ENOTEMPTY (Directory not
empty)
unlink("/dev/.udev/queue/2036") = 0
rmdir("/dev/.udev/queue") = -1 ENOTEMPTY (Directory not
empty)
wait4(-1, 0x3ea4cf8, WNOHANG, NULL) = -1 ECHILD (No child processes)
open("/proc/stat", O_RDONLY|O_LARGEFILE) = 8
fstat64(8, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x40020000
read(8, "cpu 3979 0 10751 65310 1394 0 29"..., 1024) = 386
close(8) = 0
munmap(0x40020000, 4096) = 0
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2237>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by xbaldauf):
Replying to [comment:18 andy]:
> Replying to [comment:16 xbaldauf]:
> > Interestingly, however, it looks like that, by using
glamo_mci.sd_max_clk=1000000, I can raise the probability of getting such
a crash like above to 100%. The crash happens always at GSM-login-time.
>
> To be clear, at the time of this "crash", you have the permanent noisy
screen business?
Sometimes, sometimes not. Sometimes the noisy screen is busy (e.g.
updated), sometimes even normal redraws happen (so the noisy screen is
overwritten with the correct content), and sometimes everything stops,
including screen updates.
The triggering of the bug seems to be strongly GSM-related. AFAIK, it only
happened when I login into the GSM network, place a phonecall or receive a
phonecall or short message. Thus, when I have no GSM traffic for some
hours or even days, the system seems to remain stable.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Cool, the evil twin of "MMC kills GPS" :-(
A few things to try:
When this happens, is the battery fully charged ? Does it also happen with
USB connected and providing 500mA ?
Does this also happen with a different SIM, a different SD card, or at a
different location ?
Also, if there is the possibility to test with another GTA02 in the same
settings (same battery, SD card, SIM, location), that may shed some light.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2238: CONFIG_FUNCTION_TRACER panics very early
-----------------------------+----------------------------------------------
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:
-----------------------------+----------------------------------------------
Enabling kernel function tracer (CONFIG_FUNCTION_TRACER) panics andy-
tracking b8b36e5ec3db71d very early (before framebuffer init). Could
anybody with a debug board reproduce this and attach the panic message?
The ramconsole patch in http://docs.openmoko.org/trac/ticket//2135 does
not help since it works only after vm_init has beel called.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2238>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2238: CONFIG_FUNCTION_TRACER panics very early
-----------------------------+----------------------------------------------
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):
CONFIG_FUNCTION_TRACER is incompatible with attribute ((__naked__)) used
in the FIQ stuff... it comes in and adds a preamble where no preamble can
be accepted.
It's a bug in CONFIG_FUNCTION_TRACER I think...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2238#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
