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 #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
2. Re: Openmoko Bug #2044: om-locations - map licensing
(Openmoko Public Trac)
3. Re: Openmoko Bug #2045: [Om2008.9] Wifi associating is very
unreliable (Openmoko Public Trac)
4. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
5. Re: Openmoko Bug #2044: om-locations - map licensing
(Openmoko Public Trac)
6. Re: Openmoko Bug #2044: om-locations - map licensing
(Openmoko Public Trac)
7. Re: Openmoko Bug #2036: resize2fs /dev/mmcblk02p2 128m seg
faults (Openmoko Public Trac)
8. Re: Openmoko Bug #2036: resize2fs /dev/mmcblk02p2 128m seg
faults (Openmoko Public Trac)
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by matt_hsu):
Problem statement:
This issue is result from the INT is trapped in the PMU when system is
getting into suspend. During the time of getting into suspend, there's a
window that the I2C device is suspended. This interrupt from PCF50633
can't be READ & CLEAR in this moment. So you could not wake the system
anymore.
In my opinion, there are three approaches which could resolve this
issue.
1. Like HXD8, add an alternative INT pin to S3C2442. This this pin
as a wakeup source.
2. Extend the debounce time of ONKEY. But this will change the
behavior of users.
3. Use bitbang to R&C the INT register of PMU in the last
moment(this sounds crazy).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2044: om-locations - map licensing
------------------------+---------------------------------------------------
Reporter: drlizau | Owner: julian_chu
Type: task | Status: new
Priority: highest | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by drlizau):
The application does not have to attribute OSM, but I am waiting on
further advice from OSM-legal-talk mailing list. Then I can make a few
broader notes on the wiki to explain the licensing of the data.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2044#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2045: [Om2008.9] Wifi associating is very unreliable
--------------------------------+-------------------------------------------
Reporter: Matthias | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Matthias):
I've re-booted the FR and without any kind of changes in software now I
have one working case:
[EMAIL PROTECTED]:~# ifdown eth0
WPA: Terminating
wpa_supplicant: terminating wpa_supplicant daemon via pidfile
/var/run/wpa_supplicant.eth0.pid
stopped /usr/sbin/wpa_supplicant (pid 1516)
[EMAIL PROTECTED]:~# ifup eth0
WPA: Configuring Interface
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /usr/sbin/wpa_supplicant -B -P
/var/run/wpa_supplicant.eth0.pid -i eth0 -D wext -c
/etc/wpa_supplicant/wpa_supplicant.conf -C /var/run/wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
wpa_supplicant: ctrl_interface socket located at
/var/run/wpa_supplicant/eth0
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending select for 10.0.1.217...
Lease of 10.0.1.217 obtained, lease time 7200
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
adding dns 10.0.1.201
adding dns 192.87.44.17
adding dns 192.168.52.230
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2045#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by andy):
What happens if we read the level of the EINT for PMU as GPIO input at the
end of suspend, and abort the suspend (ie, resume) if we see it is active?
What happens if we turn PMU interrupt to level instead of edge?
Previously it made trouble but that was before 2.6.24 and we never really
understood the mechanism anyway. Maybe just using level will clear this
issue (by forcing wake from EINT under these circumstances).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2044: om-locations - map licensing
------------------------+---------------------------------------------------
Reporter: drlizau | Owner: julian_chu
Type: task | Status: new
Priority: highest | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by olv):
All map packages have
LICENSE = "Creative Commons Attribution-ShareAlike 2.0"
in the .bb. But there is no(?) indication in the installer. Nor
attribution to OpenStreetMap.
I am really sorry about my oversight, and I would love to do whatever
needed to make it clear the map data are from OSM and honor the license
and hard works of the OSM folks.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2044#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2044: om-locations - map licensing
------------------------+---------------------------------------------------
Reporter: drlizau | Owner: julian_chu
Type: task | Status: new
Priority: highest | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by olv):
The above patches to OE
1. mention the licence of the map packages and attribute the work to
OpenStreetMap in the package description,
2. add a map package for low level tiles,
3. bump up the revision of om-locations so that the low level tiles do not
distribute with it.
I am not sure whether patch 2 & 3 are necessary, and I am not sure whether
patch 1 is enough. But I hope this is a start point for discussion.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2044#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2036: resize2fs /dev/mmcblk02p2 128m seg faults
------------------------+---------------------------------------------------
Reporter: Niko! | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by Niko!):
Hi zeche,
Finally i got the time to backup my phone and redo the test in a
sistematic way, to give you a method to reproduce it.
I flashed and reflashed my device different times with 2008.9, fso-
milestone-3 and fso-unstable, and i got always the seg fault.
This was a surprise for me, as i'm sure i resized the card partition
successfull with fso.
Just now i decided to delete partition and to recreate and format it, and
resize2fs worked well with all the distro!
So i really suppose that sometingh similiar to bug #1802 occourred, but
apparently the partition table was good.
You may close this issue, and if i'll be able to reproduce it i'll report
a comment on #1802 or where it fits better.
Regards
Nicola
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2036#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2036: resize2fs /dev/mmcblk02p2 128m seg faults
------------------------+---------------------------------------------------
Reporter: Niko! | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* owner: julian_chu => openmoko-devel
* component: Distro => unknown
Comment:
Okay. I think I already pointed you to
http://wiki.openmoko.org/wiki/Bug_Filing_Policy this means the next bug
will be just closed as "Invalid" according to the policy. This is not bad
will but writing this consumes engineering time that could be better spend
on reviewing patches or fixing actual bugs.
You set a component and shouldn't have set one, you are supposed to append
the output of opkg list_installed and you didn't. Specially the last part
is something that is really missing in this case.
Please append the required files.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2036#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
_______________________________________________
devel mailing list
[EMAIL PROTECTED]
https://lists.openmoko.org/mailman/listinfo/devel
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
