WSOD (Was: Re: [SHR-Today] Accept call without unlocking)

[Jens Seidel]

On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote:
> On 9/8/09, Jens Seidel <jensseidel at users.sf.net> wrote:
> > Funny, it's opposite for me. I used until yesterday 2.6.29 together with
> > uboot but switched back to 2.6.28 and now the WSOD vanished. Great!
> >
> > With 2.6.29 WSOD happened very often (I would say in 50% of all cases).
> > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it
> > in the past mainly as PDA.
> 
> BTW. Why are you playing with kernels instead of using ditribution
> one?

A good question and I don't know the proper answer. I use SHR but have also
Debian installed. SHR is currently more stable and much fancier so I prefer
it. I often update the system via opkg update and opkg upgrade which resulted
in kernel 2.6.29-rc3.

Why should I keep it if it is unstable? And a very stupid question: I know
that 2.6.29-rc3 is installed in the file system (/boot) but is it used or
the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual
and wasted yesterday at least 3 hours because of it. I also checked the
uboot config, booted via USB serial connection started printenv, ...
That's not a easy way!!! I flashed finally directly into the "kernel"
partition which seems to work. So opkg doesn't affect the running kernel ...

I know that Debian provided a script to customize the uboot configuration
and I know that the kernel in the filesystem is used and /dev/mtdblock3
as fallback (or in reverse order, don't remember). But SHR?

Digging into the Wiki and mailinglist postings is still the most time
consuming task and I'm always lost in it and not able to do any work with
my phone!

> I understand playing with 2.6.31 RC kernels, but downgrading?

I prefer a WSOD free kernel, you not?

> SHR-unstable comes with latest andy-tracking. If something doesn't
> work in this kernel, then it has to be reported, debuged and fixed,
> instead of just switching back and being quiet about that!

The problem in 2.6.29 is already known, there is no need to report it
so I tried to avoid it using 2.6.28 (which reports itself as
2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why
aren't both WSOD bug reports updated? I wasn't even aware until very
recently that the original WSOD bug was fixed as the initial report is still
open without activity since months.

I now tried again at least ten minutes to find the SHR kernel download link
but failed, it's not on http://wiki.openmoko.org/wiki/Download,
http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel,
http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via
Google, What a mess! At least I don't remember seeing anything andy-tracking
related (except the Wiki article about getting the source).

Jens