public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: David Airlie <airlied@linux.ie>, dri-devel@lists.sourceforge.net
Subject: 2.6.29-rc breaks STD using Intel 945
Date: Wed, 4 Mar 2009 20:20:56 +0100	[thread overview]
Message-ID: <200903042020.57671.eike-kernel@sf-tec.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]

Hi,

I tested several snapshots post 2.6.28 and all of them show one severe 
problem: resume from disk is not always successful. Only about 50% of the 
resume attempts work, in the other cases I just get a completely black 
screen, can't switch to text console or anything. What I often get is a line 
like this in the logs directly before suspend:

[drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled 
pipe 0

Afterwards I find nothing in the logs. Switching back to 2.6.28 and everything 
works fine again. I have a Toshiba A110-178 running openSuSE 11.1 32 bit with 
KDE 4.2.0. I upgraded my Xserver from 1.5 to 1.6 yesterday but that did not 
change anything. The only external module I use is the omnibook module 
(http://sf.net/projects/omnibook) which I've been using for years without any 
problems.

VGA device is this:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA 
controller])
        Subsystem: Toshiba America Info Systems Device ff01
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at dc100000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at 1800 [size=8]
        Memory at c0000000 (32-bit, prefetchable) [size=256M]
        Memory at dc200000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- 
Count=1/1 Enable-
        Capabilities: [d0] Power Management version 2
        Kernel modules: intelfb

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller (rev 03)
        Subsystem: Toshiba America Info Systems Device ff01
        Flags: bus master, fast devsel, latency 0
        Memory at dc180000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 2

If you have any patches you want to try me or have any further questions just 
mail me. If you're hanging around at CeBIT I can come over and we can discuss 
this in person as I'm there for the next days anyway.

Greetings,

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-04 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 19:20 Rolf Eike Beer [this message]
2009-03-05 12:55 ` 2.6.29-rc breaks STD using Intel 945 Sitsofe Wheeler
2009-03-08 18:02   ` Rolf Eike Beer
2009-03-08 21:04     ` Rafael J. Wysocki
2009-03-14 13:37     ` Sitsofe Wheeler
2009-03-16 13:02       ` Frank Seidel
2009-03-16 17:16         ` Sitsofe Wheeler
2009-03-22 15:56       ` Rolf Eike Beer
2009-03-07 21:05 ` Rafael J. Wysocki
2009-03-07 22:02   ` Rolf Eike Beer
2009-03-14  8:08 ` Rolf Eike Beer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200903042020.57671.eike-kernel@sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox