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. [Bug 676] New: dfu-upload on GTA02v1 causes data corruption
([EMAIL PROTECTED])
2. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
3. [Bug 677] New: I/O errors on heavy microSD writes
([EMAIL PROTECTED])
4. [Bug 678] New: System inappropriately suspends with no GUI
app present ([EMAIL PROTECTED])
5. [Bug 95] verify charger current and battery temperature
reading correctness ([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 102] SIM phonebook access
([EMAIL PROTECTED])
8. [Bug 593] audio doesn't survive suspend/resume
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=676
Summary: dfu-upload on GTA02v1 causes data corruption
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
It seems like dfu-upload on GTA02v1 results in a corrupted image.
This is not 100% verified yet, but I just file this as a reminder to myself (and
a warning to other GTA02v1 prototype testers).
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-08-01 20:21 -------
hmm...didn't think my SIM cards were new enough to have 3g issues. They are both
indicate 64Ksmartchip and neither work. Details:
Gemplus, Sku+: 63698G3002
Oberthur, Sku+ 64205O4020
As you can see from the skus they are quite old.
I get the CME Error 32 for awhile, and the AT+CIMI gives an CME Error 13
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677
Summary: I/O errors on heavy microSD writes
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Writing heavily to the microSD will cause intermittent I/O errors. Case in
point; I tried to scp a bunch of music to the Sandisk microSD provided with the
Neo, and I got I/O errors at some point. Experimenting with transfer speeds
revealed that scp -l 500 (that is, 500 kilobits per second) still was vulnerable
to the error, but -l 100 managed to transfer the ~250 megabytes without errors.
I couldn't reproduce later with local dd if=/dev/zero of=foo, experimenting with
different block sizes. Maybe luck, or maybe the scp CPU consumption and/or write
patterns helps triggering. I _was_ able to reproduce with scping some more with
no speed limit. Here's some dmesg from the Neo from this reproduction:
<3>s3c2410-sdi s3c2410-sdi: unfinished write - pio_count:[1024] pio_words:[0]
<3>mmcblk0: error 4 transferring data
<3>s3c2410-sdi s3c2410-sdi: unfinished write - pio_count:[1024] pio_words:[0]
<3>mmcblk0: error 4 transferring data
<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=53, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 713 0
<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=53, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 711 0
<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=53, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 716 0
<3>s3c2410-sdi s3c2410-sdi: unfinished write - pio_count:[1024] pio_words:[0]
<3>mmcblk0: error 4 transferring data
<4>end_request: I/O error, dev mmcblk0, sector 708600
<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=53, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 713 0
Haven't seen problems yet on reading.
I'm using these kernel and root images:
uImage-2.6.21.6-moko10-r1_0_0_2388_0-fic-gta01.bin
openmoko-devel-image-fic-gta01-20070728081358.rootfs.jffs2
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=678
Summary: System inappropriately suspends with no GUI app present
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Couldn't really decide which component to blame of those listed, as power
management and related stuff isn't separated. So I put it here, move if
appropriate.
Anyway, it appears that OpenMoko will suspend the Neo within about five minutes
if there are no GUI apps (sans the top panel) running. This with no regard to it
being plugged in, and usbnet being in active use. Also playing music in the
background with ogg123 will not prevent suspend.
To reproduce, kill the today app by pushing the power button while it's up, then
kill the task manager similarly, if necessary with a little aid from tapping the
graphical quarter-wheel at the left of screen. After this, suspension will be
imminent.
(I first thought that this was an USB or usbnet issue, and reflected this on the
device-owners list; this was in fact not the case in the end, in case someone
was wondering.)
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=95
------- Additional Comments From [EMAIL PROTECTED] 2007-08-02 00:25 -------
I've compared the displayed current intake w/ an actual measurement of the same.
There is no factor, the displayed values are
- all way off
- are bouncing up and down
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=129
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=344
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=347
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=352
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=511
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=571
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=605
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=639
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=643
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=644
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=102
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #211 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2007-08-02 07:40 -------
Created an attachment (id=235)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=235&action=view)
SIM Phonebook access 2nd try
Based on attach #2111
Perform code clean up and mention API changes:
lgsm_pb_read_entryies -> lgsm_pb_read_entries
lgsm_pb_list_storage (new):
List of supported phonebook memory storage.
lgsm_pb_set_storage (new);
Select phonebook memory storage.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=593
------- Additional Comments From [EMAIL PROTECTED] 2007-08-02 10:41 -------
I think I have tracked down the problem with this, it requires me though to
merge in the latest ASoC v2 changes to fix. I think this is on the schedule in
next month or so.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
