[REGRESSION] Kernel 3.5 to 3.7-rc4 / GMA500 / DPMS sometimes crashes system

[Chini, Georg (HP App Services)]

Hello,

I have an issue with the GMA500 driver for kernels from 3.5 up to 3.7-rc4.
I am using an Intel board with a D2700 Atom processor running Debian unstable.
Sometimes when DPMS switches off the screen the system reboots. More often it
does not reboot but shows a white screen on reactivation. Then I can ssh into
the box from another host but the white screen remains even if I restart X or
change VT. This never seems to happen the first time the screen is switched off,
generally it takes 3 or 4 cycles to trigger the bug. Kernel 3.4.3 works fine.
There are no messages in the logs. Any idea what might cause this or how I
can debug it any further? I will supply more details on my setup if needed.
Please CC me in your reply as I am not subscribed to the list.

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

Re: [REGRESSION] Kernel 3.5 to 3.7-rc4 / GMA500 / DPMS sometimes crashes system

[Alan Cox]

> generally it takes 3 or 4 cycles to trigger the bug. Kernel 3.4.3 works fine.
> There are no messages in the logs. Any idea what might cause this or how I
> can debug it any further? I will supply more details on my setup if needed.
> Please CC me in your reply as I am not subscribed to the list.

If 3.4.3 works and 3.5 fails then that is a big help as it narrows the
possible range of causes down quite a bit.

Hardware info would be helpful here but I suspect it may be a case of
doing a set of test builds to identify the offending patch.

Also anything in the log might be helpful including doing the runs with
drm.debug=255 in the kernel command line to get full traces

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

RE: [REGRESSION] Kernel 3.5 to 3.7-rc4 / GMA500 / DPMS sometimes crashes system

[Chini, Georg (HP App Services)]

Hello Alan,

> Hardware info would be helpful here but I suspect it may be a case of
> doing a set of test builds to identify the offending patch.

Board is an Intel Mini-ITX 2700MUD, Atom 2700 processor, GMA 3650. Lspci gives:

00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller (rev 09)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio 
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 
02)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 
02)
00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#1 (rev 02)
00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#2 (rev 02)
00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#3 (rev 02)
00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#4 (rev 02)
00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller 
(rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA Controller 
[AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

> Also anything in the log might be helpful including doing the runs with
> drm.debug=255 in the kernel command line to get full traces

See attached file. I removed the bit where I tested switching off/on for a 
while, there
is no additional information. When the error occurs I find following additional 
lines
in the log:

Nov  9 14:53:12 pico kernel: [drm:drm_crtc_helper_set_config],
Nov  9 14:53:12 pico kernel: [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:61] 
#connectors=1 (x y) (0 0)
Nov  9 14:53:12 pico kernel: [drm:drm_crtc_helper_set_config], 
[CONNECTOR:12:DVI-D-1] to [CRTC:3]
Nov  9 14:53:12 pico kernel: [drm:drm_crtc_helper_set_config],
Nov  9 14:53:12 pico kernel: [drm:drm_crtc_helper_set_config], [CRTC:4] [NOFB]

Do you need any more information?

Regards
   Georg  


drm.log
Description: drm.log