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 #2023: Continuous gsm registering
(Openmoko Public Trac)
2. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
3. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
4. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
5. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
6. Re: Openmoko Bug #1815: u-boot fails to detect sandisk 8gb
microsdhc correctly (Openmoko Public Trac)
7. Re: Openmoko Bug #2023: Continuous gsm registering
(Openmoko Public Trac)
8. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
--- Begin Message ---
#2023: Continuous gsm registering
----------------------+-----------------------------------------------------
Reporter: christof | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Keywords: gsm register
Blockedby: | Reproducible: always
Blocking: |
----------------------+-----------------------------------------------------
My phone (GTA02) is registering continuous to the provider. Every minute
it is trying to connect. I can hear some noise in my speaker (not the
phone speaker) and I see that the gsm icon is changing.
My provider is klarmobil (t-mobile network) and the signal strength is
very good (5 bars).
Installed version:
* Om2008.8-gta02-20080903.uImage.bin
* Om2008.8-gta02-20080918.rootfs.tar.gz
Steps to reproduce:
* just wait a minute and you will hear the noise and see the icon change
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2023>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
Hi,
I'm having this issue too. I'm not adding any dmesg, since they are the
same as others. Currently, only one reason for this has been proposed by
Andy, it would be nice to have a bit more status on this.Here's the
original comment:
> I have seen two behaviours that give WSOD despite the happy story above
-- first is during resume, the Glamo's Reset pin is falsely activated by a
spike. Because we assume most Glamo registers survive suspend, this kills
us dead and the partial resume action we do on the registers does not
succeed to issue any video. So with that problem you get a sticky WSOD
until you reboot.
Is this spike theory has been proven ? What would cause this spike ? If we
know a spike might reset the Glamo, can we detect that in software and
maybe do a complete reset of the Glamo ? What would be the result of
always doing a complete reset of the Glamo ? I think we are all ready for
experiment on this, we just need a OpenMoko god to guide are ignorance
when hacking the Glamo driver.
Thanks,
Nicolas
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
Hi,
I'm having this issue too. I'm not adding any dmesg, since they are the
same as others. Currently, only one reason for this has been proposed by
Andy, it would be nice to have a bit more status on this.Here's the
original comment:
> I have seen two behaviours that give WSOD despite the happy story above
-- first is during resume, the Glamo's Reset pin is falsely activated by a
spike. Because we assume most Glamo registers survive suspend, this kills
us dead and the partial resume action we do on the registers does not
succeed to issue any video. So with that problem you get a sticky WSOD
until you reboot.
Is this spike theory has been proven ? What would cause this spike ? If we
know a spike might reset the Glamo, can we detect that in software and
maybe do a complete reset of the Glamo ? What would be the result of
always doing a complete reset of the Glamo ? I think we are all ready for
experiment on this, we just need a OpenMoko god to guide are ignorance
when hacking the Glamo driver.
Thanks,
Nicolas
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by Zoup):
OK! using kitchen gloves i made a hack!
i did tested two different things ,
* first its appear that voltages are as you said ( i'm not sure if i have
tested right spots , an image would be great
* when jack input is facing you , the second ring of jack ( the last
silver one ) has a very small golden connector to its right-down , when i
insert the headphone they getting connected , when i remove headphone they
are disconnected .
so , is this really hardware issue ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by werner):
Oh, cool. I just wrote a long description of how to test the jack, and
trac
threw it away, probably because I started editing before you added your
last
update :-(
Anyway, here's the picture:
http://people.openmoko.org/werner/jack-3-5.jpg
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1815: u-boot fails to detect sandisk 8gb microsdhc correctly
---------------------------------+------------------------------------------
Reporter: x | Owner: openmoko-kernel
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: GTA02v5
Severity: normal | Resolution:
Keywords: u-boot sdhc sandisk | Blockedby:
Blocking: |
---------------------------------+------------------------------------------
Comment(by olberger):
I just experienced the same problem as initially reported, but for a 2Gb
card.
The card is a sandisk 2GB SDSDQ-2048-E11MK microSD, but mmcinit reports
the following with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) :
GTA02v5 # mmcinit
Card Type: SD 2.0
Manufacturer: 0x03, OEM "SD"
Product name: "SU02G", revision 8.0
Serial number: 24786483
Manufacturing date: 3/2008
MMC/SD size: 511MiB
Hope this helps (and doesn't mess, as the initial report was about 8Gb
cards).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1815#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2023: Continuous gsm registering
-----------------------------+----------------------------------------------
Reporter: christof | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution: duplicate
Keywords: gsm register | Blockedby:
Reproducible: always | Blocking:
-----------------------------+----------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => duplicate
Comment:
Duplicate of #1024.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2023#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by zecke):
http://downloads.openmoko.org/schematics/ in case you are not aware of
that.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
