screen goes blank when loading gma500_gfx (atom D2500)

[Michael Tokarev]

Hello.

Today I rebooted my router into a new kernel and noticed that
the screen goes blank after booting the system (initial bootup
messages are visible).  After some debugging it turns out that
the screen goes blank when loading gma500_gfx module.

This is an intel D2500CC motherboard with Atom D5200 built-in,
with a monitor connected to a VGA port, the following vga device
is reported by lspci:

00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09)

Here are the dmesg output after loading gma500_gfx:

[  176.427071] Linux agpgart interface v0.103
[  176.452914] [drm] Initialized drm 1.1.0 20060810
[  176.476037] gma500 0000:00:02.0: setting latency timer to 64
[  176.476216] gma500 0000:00:02.0: irq 50 for MSI/MSI-X
[  176.491675] acpi device:29: registered as cooling_device2
[  176.492041] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[  176.492169] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11
[  176.492357] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[  176.492396] [drm] No driver support for vblank timestamp query.
[  176.607485] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[  176.607531] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[  176.806078] [drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0

which does not look bad or suspicious to me.

fbcon is loaded so it isn't an issue.

I tried 3.10 kernel initially (the above messages are from it), next
I tried 3.13 kernel too, and that one behaves exactly the same.

As far as I remember, this system never worked with graphics well.
Previous kernel (from which I updated) was 3.2 which had no
gma500 module (local build).

What are the steps to debug this further?

Thanks,

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/