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 #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
2. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
3. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
4. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
5. Re: Openmoko Bug #2206: Can't mount GadgetFS on OM.
(Openmoko Public Trac)
6. Re: Openmoko Bug #1955: pppd persist and holdoff does not
work (Openmoko Public Trac)
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
Reporter: raster | Owner: zecke
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by werner):
* status: in_testing => closed
* resolution: => fixed
Comment:
Yes, time to move on :-)
I'm closing it as "fixed" (in 2.6.28).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:56>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
Reporter: raster | Owner: zecke
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by Matthias):
Replying to [comment:56 werner]:
> Yes, time to move on :-)
> I'm closing it as "fixed" (in 2.6.28).
Werner, don't get me wrong, but I have always a bad feeling if a bug gets
closed because "I believe this bug has vanished" or when a bug can not be
reproduced any more; a bug is only really fixed when someone says, for
example, "yes there was a small int used where it should be integer, I've
changed and commited it"; believe me that I know about what I'm talking,
I'm working as the tech head in a software company;
concerning the bug itself I said, that it also occurs without 'long
suspend time'; may be we are talking about two different bugs or usages of
the FR; has someone with a 2.6.28 kernel tested it 7x24 without suspending
the FR, at least?
anyway; I will update asap to 2.6.28 (once I get an idea about an upgrade
path in Om2008.12++) and will come back to this (or hopefully not :-))
just my concerns, Matthias
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:57>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
Reporter: raster | Owner: zecke
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by andy):
It'll get reopened for sure if there is any more sign of it on 2.6.28.
As for the upgrade path, I read that testing or unstable repo for FSO has
migrated to 2.6.28 already, it can be worth checking out on SD Card maybe.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:58>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
Reporter: raster | Owner: zecke
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by werner):
Matthias, I agree with the sentiment. That's also why I left the bug open
so long, on the off chance that the bug would somehow show up again. But
it
didn't.
The change that made it "disappear" is the complete replacement of the
SDIO
stack. That's some 10'000 lines of Atheros SDIO code that were removed
from
our kernel and now we're using something like the same amount of different
code (the Linux SDIO stack) in its place.
And yes, I had 2.6.28 running for weeks without seeing this problem, while
it would quite reliably show up on 2.6.24.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:59>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2206: Can't mount GadgetFS on OM.
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by frankmpunkt):
Replying to [comment:1 Sander]:
I am not sure if I applied the patch correctly, but after having build
everything the following file shows your changes:
{{{
${OM}/build/tmp/work/om-gta01-angstrom-linux-gnueabi/linux-
openmoko-3_2.6.24+gitr0+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01/git/drivers/usb/gadget/s3c2410_udc.c
}}}
Anyway, the kernel module still shows the same error: no such filesystem
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2206#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1955: pppd persist and holdoff does not work
---------------------+------------------------------------------------------
Reporter: niccolo | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2007.2
Component: Distro | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by niccolo):
I did forther testing and I strongly believe there is a bug in pppd. So I
wrote a mail to Paul Mackerras and James Carlson (contacts in the README).
This is the mail, just for the record.
I'm using pppd on the FreeRunner phone, running the OpenMoko
distribution. The problem is always reproducible and it is as
follow:
- start pppd with its chat script
- the chatscript fails for whatever (e.g. no GPRS signal)
- pppd waits for the "holdoff" time
- chatscript is **NOT** fired up again
- pppd stalls in an endless select()
this happens despite my configuration file which contains:
maxfail 0
holdoff 13
persist
If I SIGHUP pppd, it ends the select() and does a new chat
attempt.
Because I need an always-on connection on un unattended mobile
phone, you understand that this is very annoying.
Reading the source I suspec that the for() loop in main.c:494
does start chat only in the first run, not in the second.
The phone environment:
* pppd version 2.4.3-r4
* OpenMoko 2008.12 (based on Angstrom armv4t)
* Linux om-gta02 2.6.24 #1 PREEMPT Wed Dec 17 02:13:29 CST 2008
armv4tl
I attach my configuration file and an strace of the pppd process.
Thank you very much for any hints.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1955#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
