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 #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
2. Openmoko Bug #2224: Qi starts and then dies - sometimes
(Openmoko Public Trac)
3. Re: Openmoko Bug #2224: Qi starts and then dies - sometimes
(Openmoko Public Trac)
4. Re: Openmoko Bug #2224: Qi starts and then dies - sometimes
(Openmoko Public Trac)
5. Openmoko Bug #2225: [fso-testing] Two lines of `nameserver'
appendded to resolv.conf everytime usb0 is up (Openmoko Public Trac)
--- 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 laforge):
andy: with regard to non-GTA devices: yes, there is no glamo, there is no
SDIO or AR6000. There also is o FIQ/HDQ. And yes usb/ethernet is up and
runnign.
Apart from that, the s3c2410fb is used, like in GTA01. The NAND flash is
used. The SD-card is used (s3cmci, like GTA01). I have a couple of my
glofiish specific drivers, but none of them
are actually loaded when this bug occurs. There is no particular system
activity, no daemons
running, almost zero CPU consumption.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2224: Qi starts and then dies - sometimes
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: Qi
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Qi starts, you can feel the vibrator thump, and if lucky enough to be in
an environment you may see the backlight is on, but some 10 seconds later
the backlight switches off and nothing happens.
The lack of feedback that Qi is doing anything (the backlight isnt easily
seen in many environments) means its a very frustrating way to bootup -
and very time wasting as you have to wait many minutes to see if its
booted or not, then often have to try again.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2224>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2224: Qi starts and then dies - sometimes
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: Qi
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by PaulFertser):
I don't agree here, Bill.
You know how many vibes you feel when everything is working like you want
to, so you'll notice any abnormal situation by counting vibes. After the
kernel is booted (you say that you can see backlight in certain
conditions, but you know that the kernel is booted anyway, by feeling
proper number of vibes), it's up to the kernel, then to the userspace to
show anything on screen.
It's doesn't depend on bootloader. If you want messages, enable them in
your append-GTA02 file and have the feedback on the price of slower boot.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2224#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2224: Qi starts and then dies - sometimes
-----------------------------+----------------------------------------------
Reporter: BillK | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: Qi
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by andy):
There's a simple rule of thumb, if the backlight came up then blame the
kernel, not Qi. Qi doesn't bring up the backlight, so your kernel is
quite far along with booting.
What you're describing though is what happens if you try to start GTA02
without a battery or with very low battery.
As Paul says enable kernel debug messages on LCM and find out your kernel
or hardware -- not Qi -- problem that way.
For the larger issue of feedback, we can enable kernel splash image to
help it.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2224#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2225: [fso-testing] Two lines of `nameserver' appendded to resolv.conf
everytime
usb0 is up
-------------------------+--------------------------------------------------
Reporter: koreylu | Owner: julian_chu
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: trivial | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Hardware: GTA02
Software: fso-testing image, openmoko-fso-image-glibc-ipk--20090118-om-
gta02.rootfs.tar.gz
Now that /etc/resolv.conf is a regular file (not a symlink to a temporary
file in volatile file system), and in /etc/network/interfaces two lines of
`up echo nameserver xxx >> /etc/resolv.conf' still do their job,
/etc/resolv.conf is growing all the time.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2225>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
