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 #788: Starting or stopping gsmd completely
locks up the Neo (Openmoko Public Trac)
2. Re: Openmoko Bug #79: suspend/resume to RAM support
(Openmoko Public Trac)
3. Re: Openmoko Bug #2223: gsm0710muxd loosing packets?
(Openmoko Public Trac)
4. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
5. Re: Openmoko Bug #2231: interrupt not always generated when
flowcontrolled=1 and modem wants to talk (Openmoko Public Trac)
6. Re: Openmoko Bug #1250: No Wifi in Managed Mode
(Openmoko Public Trac)
7. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
8. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
--- Begin Message ---
#788: Starting or stopping gsmd completely locks up the Neo
--------------------------------+-------------------------------------------
Reporter: mwes...@… | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: 2007.2
Severity: critical | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by mickey):
* status: assigned => closed
* resolution: => fixed
Comment:
With regards to the original problem of starting or stopping gsmd locking
the Neo, I'll close this bug now for several reasons:
a) ogsmd, fso-abyss, gsm0710muxd all seem to start, stop, restart GSM
without problems (apart from the fancy sysfs dance that is required to
reliably reset it).
a) gsmd is dead.
With regards to the other problems, please open dedicated bugs for that as
you see fit.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/788#comment:58>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#79: suspend/resume to RAM support
-------------------------------------+--------------------------------------
Reporter: lafo...@… | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: highest | Milestone:
Component: System Software | Version: current svn head
Severity: blocker | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-------------------------------------+--------------------------------------
Changes (by mwester):
* status: reopened => closed
* resolution: => fixed
Comment:
The current situation with the latest (2.6.29) kernel is unknown from a
"in-the-field" point-of-view (few users, if any, I expect) -- but this
ticket has probably outlived its usefulness. Time to close it, and any
new issues found should open new (more specific) tickets instead.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/79#comment:39>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2223: gsm0710muxd loosing packets?
------------------------+---------------------------------------------------
Reporter: kapiteined | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------+---------------------------------------------------
Comment(by kapiteined):
Hi,
Today (12 feb 2009) i took the code from the git repository and build
gsm0710muxd.
it still does not work well with this version.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2223#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Sascha):
Ok, then do you already have enough informations to fix this bug?
Btw, fix-gta02-irq-arbiter-priority.patch doesn't change anything here.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2231: interrupt not always generated when flowcontrolled=1 and modem wants to
talk
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: joerg
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Changes (by joerg):
* owner: openmoko-kernel => joerg
* status: new => accepted
* haspatch: 0 => 1
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2231#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1250: No Wifi in Managed Mode
------------------------------------+---------------------------------------
Reporter: mic...@… | Owner: openmoko-ker...@…
Type: defect | Status: reopened
Priority: highest | Milestone:
Component: System Software | Version: unspecified
Severity: critical | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
------------------------------------+---------------------------------------
Comment(by werner):
Here's an update:
http://lists.openmoko.org/pipermail/devel/2009-February/004722.html
My original interpretation that the AP was first offering a
capability which it later refused was incorrect. I can even
reproduce the problem. But this still doesn't explain the root
of this particular evil.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1250#comment:28>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by Sascha):
I've done some more tests... and I must say that there are some bytes lost
in the gsm uart (64 bytes after the overrun flag has been set).
{{{
received: \r\n2,2,2,2,2,2\r\n2,2,2 ,0,0,0,0,0\r\n
expected: \r\n2,2,2,2,2,2\r\n2,2,2,2,2,2\r\n0,0,0,0,0,0\r\n
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
It seems there is a new update of the GSM firmware that is worth trying:
http://people.openmoko.org/joerg/calypso_moko_FW/moko11/
I just read on kernel list mwester found this solved handshake issues he
also had around suspend time.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
