Bug 11220

This may be a duplicate of bug #11178, but confirmation is needed.

I've had the same symptoms: long delay when resuming with I/O errors. Patch http://bugzilla.kernel.org/attachment.cgi?id=17043 from bug #11178 fixed it.

Not-Handled-By : "Rafael J. Wysocki" <rjw@sisk.pl>

Created attachment 17757 [details]
dmesg of dell inspiron waking up to blank screen and Xorg.0.log

my dell inspiron wakes to a blank screen, not sure if this is kernel or xorg.conf

>(II) I810(0): PIPEBCONF is 0x00000000
this means display isn't enabled. Can you please try a new xorg intel video driver?

(In reply to comment #5)
> >(II) I810(0): PIPEBCONF is 0x00000000
> this means display isn't enabled. Can you please try a new xorg intel video
> driver?
> 

Thanks for the advice, I have never really setup intel graphics before:
So after looking into it, loading
the right modules; 3D is working now, and echo mem > /sys/power/state works
no delay, just starts right up.
 Now for the other situation
when doing the same with a macbook pro ATI chipset I did apply the patch from
#2 and was successful without any delays of over 30 secs. But that was a few weeks ago(noticed a change in that file), Now without adding any patches 
and keeping a clean kernel as possible suspend does work, but I'm waiting 
around over a minute or so. 

(In reply to comment #6)
> (In reply to comment #5)
> > >(II) I810(0): PIPEBCONF is 0x00000000
> > this means display isn't enabled. Can you please try a new xorg intel video
> > driver?
> > 
> 
> Thanks for the advice, I have never really setup intel graphics before:
> So after looking into it, loading
> the right modules; 3D is working now, and echo mem > /sys/power/state works
> no delay, just starts right up.

Good.

>  Now for the other situation
> when doing the same with a macbook pro ATI chipset I did apply the patch from
> #2 and was successful without any delays of over 30 secs. But that was a few
> weeks ago(noticed a change in that file), Now without adding any patches 
> and keeping a clean kernel as possible suspend does work, but I'm waiting 
> around over a minute or so. 

Did you change the kernel or is it the same kernel that worked well before?

On Sunday, 26 of October 2008, Justin Mattock wrote:
> On Sat, Oct 25, 2008 at 2:07 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.26 and 2.6.27.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.26 and 2.6.27.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=11220
> > Subject         : Screen stays black after resume
> > Submitter       : Nico Schottelius <nico@schottelius.org>
> > Date            : 2008-07-31 21:05 (87 days old)
> > References      : http://marc.info/?l=linux-kernel&m=121753882422899&w=4
> 
> apologize for not responding,(tied up with debootstrap);
> after running ubuntu8.10 last week with the latest git
> suspend was resulting in a black screen on wakeup,
> (when using the latest radeon), maybe the video driver needs
> more time in the development stage. As for running the latest git
> today, suspend works without any delays. unfortunately I have to
> load a proprietary module for my system to be successful with suspend,
> that is until radeon becomes more mature in that area, or it is; I'm just not
> googling enough.

*** This bug has been marked as a duplicate of bug 7225 ***