[All] Black Screen of Death - Won't resume from standby

[Steven **-6]

I've seen this several times with SHR-Unstable and now with Android.
So, I'd say it's something that is common among these distro's.  Is it
seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
issue?
Any clues how to debug this or what might cause it?

I know I'm not the only one that sees it.  How are others dealing with
these random lock-ups?

Thanks,
Steven

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Paul Fertser]

"Steven **" <[hidden email]> writes:
> I know I'm not the only one that sees it.  How are others dealing with
> these random lock-ups?

Saw that several times. It just doesn't resume, obviously a kernel
(probably but unlikely bootloader) problem. It'd be nice to reproduce
it with ramconsole or a real console attached.

Quite possibly it's https://docs.openmoko.org/trac/ticket/2309

--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[hidden email]

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[matzehuber]

Steven ** schrieb:

> I've seen this several times with SHR-Unstable and now with Android.
> So, I'd say it's something that is common among these distro's.  Is it
> seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> issue?
> Any clues how to debug this or what might cause it?
>
> I know I'm not the only one that sees it.  How are others dealing with
> these random lock-ups?
>
>  

i have this too with my system gta02v6 latest shr-u.
sometimes i thought, it has to do with gps, but i am not sure about.
sometimes i think, problem it is changing cell while sleeping.

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Warren Baird-2]

I just started noticing this on an shr-u build updated in early sept.   The only thing I've changed lately is installing omnewrotate.   I also noticed it on an install of the shr-testing candidate, that also had omnewrotate installed.

I'm going to keep omnewrotate installed for a while and see how often I get the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.

Warren

On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <[hidden email]> wrote:

Steven ** schrieb:

> I've seen this several times with SHR-Unstable and now with Android.
> So, I'd say it's something that is common among these distro's.  Is it
> seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> issue?
> Any clues how to debug this or what might cause it?
>
> I know I'm not the only one that sees it.  How are others dealing with
> these random lock-ups?
>
>

i have this too with my system gta02v6 latest shr-u.
sometimes i thought, it has to do with gps, but i am not sure about.
sometimes i think, problem it is changing cell while sleeping.

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[matzehuber]

Some javascript/style in this post has been disabled (why?)

 31.10.2009 18:03,   Warren Baird :

I just started noticing this on an shr-u build updated in early sept.   The only thing I've changed lately is installing omnewrotate.   I also noticed it on an install of the shr-testing candidate, that also had omnewrotate installed.
I'm going to keep omnewrotate installed for a while and see how often I get the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.

i have actually no omnewrotate installed, but i had some time ago.

On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <[hidden email]> wrote:

Steven ** schrieb:

> I've seen this several times with SHR-Unstable and now with Android.
> So, I'd say it's something that is common among these distro's.  Is it
> seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> issue?
> Any clues how to debug this or what might cause it?
>
> I know I'm not the only one that sees it.  How are others dealing with
> these random lock-ups?
>
>

i have this too with my system gta02v6 latest shr-u.
sometimes i thought, it has to do with gps, but i am not sure about.
sometimes i think, problem it is changing cell while sleeping.

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Steven **-3]

I don't have omnewrotate nor do I ever use GPS.  So, I don't think
those are the cause.

Now, I'm sure my phone switches towers occasionally.  And I have an
extreme case of the recamping issue.  I maybe see it more often with
Android-on-Freerunner now that they're doing an adaptive deep-sleep
(which I had disabled on SHR-Unstable).  Or that could just be bad
luck...

-Steven

On Sat, Oct 31, 2009 at 1:04 PM, Matthias Huber
<[hidden email]> wrote:

>  31.10.2009 18:03,   Warren Baird :
>
> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> i have actually no omnewrotate installed, but i had some time ago.
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber
> <[hidden email]> wrote:
>>
>> Steven ** schrieb:
>> > I've seen this several times with SHR-Unstable and now with Android.
>> > So, I'd say it's something that is common among these distro's.  Is it
>> > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
>> > issue?
>> > Any clues how to debug this or what might cause it?
>> >
>> > I know I'm not the only one that sees it.  How are others dealing with
>> > these random lock-ups?
>> >
>> >
>> i have this too with my system gta02v6 latest shr-u.
>> sometimes i thought, it has to do with gps, but i am not sure about.
>> sometimes i think, problem it is changing cell while sleeping.
>
>
> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community
>
>

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Rui Miguel Silva Seabra]

Hi,

As you go into suspend, a script is called that *stops* (kills the process)
omnewrotate.

As you resume, a script is called that starts omnewrotate.

So:

  1) as you suspend, omnewrotate is *not* even working.
  2) only after resume is completed does omnewrotate get started

Conclusion: omnewrotate doesn't affect suspend/resume cycles. :)

This scripts were place early on in it's development as after resuming
omnewrotate couldn't get any data from the accelerometers (let alone
my fears that keeping the device open could affect resume).

Rui

On Sat, Oct 31, 2009 at 01:03:29PM -0400, Warren Baird wrote:

> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
>
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> Warren
>
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <
> [hidden email]> wrote:
>
> > Steven ** schrieb:
> > > I've seen this several times with SHR-Unstable and now with Android.
> > > So, I'd say it's something that is common among these distro's.  Is it
> > > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> > > issue?
> > > Any clues how to debug this or what might cause it?
> > >
> > > I know I'm not the only one that sees it.  How are others dealing with
> > > these random lock-ups?
> > >
> > >
> > i have this too with my system gta02v6 latest shr-u.
> > sometimes i thought, it has to do with gps, but i am not sure about.
> > sometimes i think, problem it is changing cell while sleeping.
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [hidden email]
> > http://lists.openmoko.org/mailman/listinfo/community
> >
>
>
>
> --
> Warren Baird - Photographer and Digital Artist
> http://www.synergisticimages.ca

> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community


--

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[leviathan]

There could also be an other explanation.
In cases that you're not killing and starting special processes in the pre-
and post- suspend event, and it freezes anyway, the following reasons could be
used as explanation:
* It dies at suspend time: Sometimes the underlying hardware-near controller
layer aka. BIOS missunderstands S3 as S0. (Case with my old Phoenix-BIOS on my
very very old laptop until upgrade)
* Sometimes it dies on writing the staging and going to sleep
* Sometimes it has corruption in staged data stored in RAM, but it doesnt
remark it and dies on resuming.
* Sometimes it resumes, but the ACPI controll is not given back to the OS, and
its still in sleep mode, meaning:
** nearly black screen (You can see images, if you look from near, but it
doesnt habe illumination in the background lights)
** Wifi is down and wont come up unless you reboot
** Same as for wifi for sound

-> As often as you suspend and resume, as higher is the posibility of getting
corrupted RAM content ==> Black screen ==> RESET

greatings leviathan


_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Warren Baird-2]

That sounds quite reasonable - I wasn't trying to point fingers - just describing the experience I had.   yesterday I had my FR die with a BSOD 4 times - before I installed omnewrotate on this install I hadn't seen a BSOD at all.

I've just changed the default behavior for omnewrotate to 'Off' an hour or two ago, I'm going to run for a few days and see if that impacts things...

Warren

On Sun, Nov 1, 2009 at 9:29 AM, Rui Miguel Silva Seabra <[hidden email]> wrote:

Hi,

As you go into suspend, a script is called that *stops* (kills the process)
omnewrotate.

As you resume, a script is called that starts omnewrotate.

So:

 1) as you suspend, omnewrotate is *not* even working.
 2) only after resume is completed does omnewrotate get started

Conclusion: omnewrotate doesn't affect suspend/resume cycles. :)

This scripts were place early on in it's development as after resuming
omnewrotate couldn't get any data from the accelerometers (let alone
my fears that keeping the device open could affect resume).

Rui

On Sat, Oct 31, 2009 at 01:03:29PM -0400, Warren Baird wrote:
> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
>
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> Warren
>
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <
> [hidden email]> wrote:
>
> > Steven ** schrieb:
> > > I've seen this several times with SHR-Unstable and now with Android.
> > > So, I'd say it's something that is common among these distro's.  Is it
> > > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> > > issue?
> > > Any clues how to debug this or what might cause it?
> > >
> > > I know I'm not the only one that sees it.  How are others dealing with
> > > these random lock-ups?
> > >
> > >
> > i have this too with my system gta02v6 latest shr-u.
> > sometimes i thought, it has to do with gps, but i am not sure about.
> > sometimes i think, problem it is changing cell while sleeping.
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [hidden email]
> > http://lists.openmoko.org/mailman/listinfo/community
> >
>
>
>
> --
> Warren Baird - Photographer and Digital Artist
> http://www.synergisticimages.ca

> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community


--

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Warren Baird-2]

So - an update - it really seems that in my case at least the black screens of death were being caused by omnewrotate.  I'd been getting at least 1 or 2 a day since I installed it, and I got 4 last Sunday and at least 2 or 3 the day before that.   On monday I changed the omnewrotate behaviour to be off by default, and I haven't seen a single BSOD since then.

It's a bit annoying, since if I forget to make sure the phone is vertical before suspending it, my screen is all messed up, but that is less annoying than missing calls because of the BSODs.

Warren

On Mon, Nov 2, 2009 at 4:52 PM, Warren Baird <[hidden email]> wrote:

That sounds quite reasonable - I wasn't trying to point fingers - just describing the experience I had.   yesterday I had my FR die with a BSOD 4 times - before I installed omnewrotate on this install I hadn't seen a BSOD at all.

I've just changed the default behavior for omnewrotate to 'Off' an hour or two ago, I'm going to run for a few days and see if that impacts things...

Warren

On Sun, Nov 1, 2009 at 9:29 AM, Rui Miguel Silva Seabra <[hidden email]> wrote:

Hi,

As you go into suspend, a script is called that *stops* (kills the process)
omnewrotate.

As you resume, a script is called that starts omnewrotate.

So:

 1) as you suspend, omnewrotate is *not* even working.
 2) only after resume is completed does omnewrotate get started

Conclusion: omnewrotate doesn't affect suspend/resume cycles. :)

This scripts were place early on in it's development as after resuming
omnewrotate couldn't get any data from the accelerometers (let alone
my fears that keeping the device open could affect resume).

Rui

On Sat, Oct 31, 2009 at 01:03:29PM -0400, Warren Baird wrote:
> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
>
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> Warren
>
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <
> [hidden email]> wrote:
>
> > Steven ** schrieb:
> > > I've seen this several times with SHR-Unstable and now with Android.
> > > So, I'd say it's something that is common among these distro's.  Is it
> > > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> > > issue?
> > > Any clues how to debug this or what might cause it?
> > >
> > > I know I'm not the only one that sees it.  How are others dealing with
> > > these random lock-ups?
> > >
> > >
> > i have this too with my system gta02v6 latest shr-u.
> > sometimes i thought, it has to do with gps, but i am not sure about.
> > sometimes i think, problem it is changing cell while sleeping.
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [hidden email]
> > http://lists.openmoko.org/mailman/listinfo/community
> >
>
>
>
> --
> Warren Baird - Photographer and Digital Artist
> http://www.synergisticimages.ca

> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community


--

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Dan Staley]

I also get the BSOD (at least once every couple days...sometimes more), but I do not have omnewrotate installed....so I'm pretty sure it is something else.
I'm hoping the big new SHR update that is coming will help fix it.

-Dan

On Thu, Nov 5, 2009 at 11:01 AM, Warren Baird <[hidden email]> wrote:

So - an update - it really seems that in my case at least the black screens of death were being caused by omnewrotate.  I'd been getting at least 1 or 2 a day since I installed it, and I got 4 last Sunday and at least 2 or 3 the day before that.   On monday I changed the omnewrotate behaviour to be off by default, and I haven't seen a single BSOD since then.

It's a bit annoying, since if I forget to make sure the phone is vertical before suspending it, my screen is all messed up, but that is less annoying than missing calls because of the BSODs.

Warren

On Mon, Nov 2, 2009 at 4:52 PM, Warren Baird <[hidden email]> wrote:

That sounds quite reasonable - I wasn't trying to point fingers - just describing the experience I had.   yesterday I had my FR die with a BSOD 4 times - before I installed omnewrotate on this install I hadn't seen a BSOD at all.

I've just changed the default behavior for omnewrotate to 'Off' an hour or two ago, I'm going to run for a few days and see if that impacts things...

Warren

On Sun, Nov 1, 2009 at 9:29 AM, Rui Miguel Silva Seabra <[hidden email]> wrote:

Hi,

As you go into suspend, a script is called that *stops* (kills the process)
omnewrotate.

As you resume, a script is called that starts omnewrotate.

So:

 1) as you suspend, omnewrotate is *not* even working.
 2) only after resume is completed does omnewrotate get started

Conclusion: omnewrotate doesn't affect suspend/resume cycles. :)

This scripts were place early on in it's development as after resuming
omnewrotate couldn't get any data from the accelerometers (let alone
my fears that keeping the device open could affect resume).

Rui

On Sat, Oct 31, 2009 at 01:03:29PM -0400, Warren Baird wrote:
> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
>
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> Warren
>
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <
> [hidden email]> wrote:
>
> > Steven ** schrieb:
> > > I've seen this several times with SHR-Unstable and now with Android.
> > > So, I'd say it's something that is common among these distro's.  Is it
> > > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> > > issue?
> > > Any clues how to debug this or what might cause it?
> > >
> > > I know I'm not the only one that sees it.  How are others dealing with
> > > these random lock-ups?
> > >
> > >
> > i have this too with my system gta02v6 latest shr-u.
> > sometimes i thought, it has to do with gps, but i am not sure about.
> > sometimes i think, problem it is changing cell while sleeping.
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [hidden email]
> > http://lists.openmoko.org/mailman/listinfo/community
> >
>
>
>
> --
> Warren Baird - Photographer and Digital Artist
> http://www.synergisticimages.ca

> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community


--

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

--

Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Warren Baird-2]

There must be multiple causes for it...   I haven't seen a single BSOD in the week since I turned omnewrotate off by default - just before I turned it off I was getting 2 or sometimes more a day...

Maybe it's related to certain things happening during the resume phase?  I'm still using omnewrotate, I've just changed it so that it isn't turned on automatically when I resume from suspend...

Warren

On Mon, Nov 9, 2009 at 12:58 PM, Dan Staley <[hidden email]> wrote:

I also get the BSOD (at least once every couple days...sometimes more), but I do not have omnewrotate installed....so I'm pretty sure it is something else.
I'm hoping the big new SHR update that is coming will help fix it.

-Dan

On Thu, Nov 5, 2009 at 11:01 AM, Warren Baird <[hidden email]> wrote:

So - an update - it really seems that in my case at least the black screens of death were being caused by omnewrotate.  I'd been getting at least 1 or 2 a day since I installed it, and I got 4 last Sunday and at least 2 or 3 the day before that.   On monday I changed the omnewrotate behaviour to be off by default, and I haven't seen a single BSOD since then.

It's a bit annoying, since if I forget to make sure the phone is vertical before suspending it, my screen is all messed up, but that is less annoying than missing calls because of the BSODs.

Warren

On Mon, Nov 2, 2009 at 4:52 PM, Warren Baird <[hidden email]> wrote:

That sounds quite reasonable - I wasn't trying to point fingers - just describing the experience I had.   yesterday I had my FR die with a BSOD 4 times - before I installed omnewrotate on this install I hadn't seen a BSOD at all.

I've just changed the default behavior for omnewrotate to 'Off' an hour or two ago, I'm going to run for a few days and see if that impacts things...

Warren

On Sun, Nov 1, 2009 at 9:29 AM, Rui Miguel Silva Seabra <[hidden email]> wrote:

Hi,

As you go into suspend, a script is called that *stops* (kills the process)
omnewrotate.

As you resume, a script is called that starts omnewrotate.

So:

 1) as you suspend, omnewrotate is *not* even working.
 2) only after resume is completed does omnewrotate get started

Conclusion: omnewrotate doesn't affect suspend/resume cycles. :)

This scripts were place early on in it's development as after resuming
omnewrotate couldn't get any data from the accelerometers (let alone
my fears that keeping the device open could affect resume).

Rui

On Sat, Oct 31, 2009 at 01:03:29PM -0400, Warren Baird wrote:
> I just started noticing this on an shr-u build updated in early sept.   The
> only thing I've changed lately is installing omnewrotate.   I also noticed
> it on an install of the shr-testing candidate, that also had omnewrotate
> installed.
>
> I'm going to keep omnewrotate installed for a while and see how often I get
> the BSOD. Then I'll uninstall or disable omnewrotate and see what happens.
>
> Warren
>
>
> On Sat, Oct 31, 2009 at 4:27 AM, Matthias Huber <
> [hidden email]> wrote:
>
> > Steven ** schrieb:
> > > I've seen this several times with SHR-Unstable and now with Android.
> > > So, I'd say it's something that is common among these distro's.  Is it
> > > seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> > > issue?
> > > Any clues how to debug this or what might cause it?
> > >
> > > I know I'm not the only one that sees it.  How are others dealing with
> > > these random lock-ups?
> > >
> > >
> > i have this too with my system gta02v6 latest shr-u.
> > sometimes i thought, it has to do with gps, but i am not sure about.
> > sometimes i think, problem it is changing cell while sleeping.
> >
> > _______________________________________________
> > Openmoko community mailing list
> > [hidden email]
> > http://lists.openmoko.org/mailman/listinfo/community
> >
>
>
>
> --
> Warren Baird - Photographer and Digital Artist
> http://www.synergisticimages.ca

> _______________________________________________
> Openmoko community mailing list
> [hidden email]
> http://lists.openmoko.org/mailman/listinfo/community


--

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

--

Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca

_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community

[Marco Trevisan (Treviño)]

Steven ** wrote:
> I've seen this several times with SHR-Unstable and now with Android.
> So, I'd say it's something that is common among these distro's.  Is it
> seen on all distros?  Is it the kernel?  Hardware bug?  Bootloader
> issue?
> Any clues how to debug this or what might cause it?

In the Old OM2008 (that I always mostly use, in a very tuned and updated
version, for daily usage) I always have when:
 - I go in a place where there's no GSM signal
(- I wake up the phone from suspend there)
 - The phone suspends while the GSM has not signal at all

In a such case I always can't resume. I didn't test if this has been
fixed in newer distros.



_______________________________________________
Openmoko community mailing list
[hidden email]
http://lists.openmoko.org/mailman/listinfo/community