Re: kernel 3.11.6 general protection fault

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

Adding intel-gfx@ to CC.

On Thu, Oct 31, 2013 at 03:00:24PM +0100, emanoil.kotsev@fincom.at wrote:
> Hi again, just noticed that it happens also without starring at
> youtube, but again in the drm

Right, I can see a bunch of #GPs happening at

drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60

(I'm looking also at your other mail) but also, there are other ones
which are completely unrelated and happening at random places. The whole
thing looks like random corruption to me.

And you have out of tree, proprietary crap loaded so can you reproduce
the same issue without those modules, i.e. vsock, vmci, vmmon... loaded?

Leaving the rest for reference.

> Thanks in advance and kind regards
> 
> ------- cut --------
> 
> Oct 31 10:51:01 maistor kernel: [drm] Setting output timings on
> SDVOB failed
> Oct 31 10:51:01 maistor kernel: lp: driver loaded but no devices found
> Oct 31 10:51:01 maistor kernel: ppdev: user-space parallel port driver
> Oct 31 10:51:01 maistor kernel: ------------[ cut here ]------------
> Oct 31 10:51:01 maistor kernel: WARNING: CPU: 1 PID: 6441 at
> drivers/gpu/drm/i915/intel_display.c:8292
> check_crtc_state+0x5cf/0xa60 [i915]()
> Oct 31 10:51:01 maistor kernel: pipe state doesn't match!
> Oct 31 10:51:01 maistor kernel: Modules linked in: ppdev lp bnep
> rfcomm bluetooth crc16 vmnet(O) parport_pc parport vsock(O) vmci(O)
> vmmon(O) cpufreq_ondemand cpufreq_powersave cpufreq_performance
> cpufreq_stats cpufreq_conservative xt_state xt_tcpudp ipt_REJECT
> xt_limit iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
> nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables
> acpi_pad custom_method sbs sbshc fan acpi_ipmi ipmi_msghandler
> snd_hrtimer binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2
> usb_storage snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep
> snd_pcm_oss snd_mixer_oss snd_pcm iTCO_wdt iTCO_vendor_support
> snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi
> snd_seq_midi_event snd_rawmidi yenta_socket snd_seq pcmcia_rsrc
> lpc_ich acpi_cpufreq snd_seq_device snd_timer snd i2c_i801 arc4
> mperf iwl3945 iwlegacy mac80211 cfg80211 rfkill soundcore irda
> ehci_pci 8250 crc_ccitt joydev processor dcdbas dell_wmi
> sparse_keymap rtc_cmos wmi evdev battery ac serial_core sha256_ssse3
> s
> Oct 31 10:51:01 maistor kernel: ha256_generic cbc hid_generic usbhid
> hid loop dm_crypt dm_mod sg sr_mod cdrom sd_mod firewire_ohci
> firewire_core thermal b44 ssb mmc_core mii pcmcia crc_itu_t
> pcmcia_core i915 cfbfillrect cfbimgblt video button i2c_algo_bit
> cfbcopyarea drm_kms_helper drm intel_agp uhci_hcd ehci_hcd intel_gtt
> agpgart i2c_core thermal_sys freq_table usbcore usb_common
> Oct 31 10:51:01 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg Tainted:
> P           O 3.11.6eko2 #1
> Oct 31 10:51:01 maistor kernel: Hardware name: Dell Inc. Latitude
> D520                   /0NF743, BIOS A04 12/18/2006
> Oct 31 10:51:01 maistor kernel: 0000000000000000 0000000000000009
> ffffffff813db19f ffff8800268b1888
> Oct 31 10:51:01 maistor kernel: ffffffff8103f561 ffff880037fd96d8
> ffff8800268b1900 ffff880037c01800
> Oct 31 10:51:01 maistor kernel: 0000000000000001 ffff880037c01c88
> ffffffff8103f645 ffffffffa0162ea2
> Oct 31 10:51:01 maistor kernel: Call Trace:
> Oct 31 10:51:01 maistor kernel: [<ffffffff813db19f>] ?
> dump_stack+0x50/0x80
> Oct 31 10:51:01 maistor kernel: [<ffffffff8103f561>] ?
> warn_slowpath_common+0x81/0xb0
> Oct 31 10:51:01 maistor kernel: [<ffffffff8103f645>] ?
> warn_slowpath_fmt+0x45/0x50
> Oct 31 10:51:01 maistor kernel: [<ffffffffa01106ff>] ?
> check_crtc_state+0x5cf/0xa60 [i915]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa011aeed>] ?
> intel_modeset_check_state+0x2bd/0x730 [i915]
> Oct 31 10:51:01 maistor kernel: [<ffffffff811fa769>] ?
> snprintf+0x39/0x40
> Oct 31 10:51:01 maistor kernel: [<ffffffffa011b3cd>] ?
> intel_set_mode+0x1d/0x30 [i915]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa011bb8a>] ?
> intel_crtc_set_config+0x7aa/0x980 [i915]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa00a8505>] ?
> drm_mode_set_config_internal+0x55/0xd0 [drm]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa00aa378>] ?
> drm_mode_setcrtc+0x118/0x640 [drm]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa009b1ad>] ?
> drm_ioctl+0x4ed/0x5f0 [drm]
> Oct 31 10:51:01 maistor kernel: [<ffffffffa00aa260>] ?
> drm_mode_setplane+0x3a0/0x3a0 [drm]
> Oct 31 10:51:01 maistor kernel: [<ffffffff8111d97b>] ?
> do_vfs_ioctl+0x8b/0x530
> Oct 31 10:51:01 maistor kernel: [<ffffffff8111de6d>] ?
> SyS_ioctl+0x4d/0xa0
> Oct 31 10:51:01 maistor kernel: [<ffffffff813e1e56>] ?
> system_call_fastpath+0x1a/0x1f
> Oct 31 10:51:01 maistor kernel: ---[ end trace 65327d016e6b6847 ]---
> Oct 31 10:51:08 maistor kernel: [drm] Setting output timings on
> SDVOB failed
> Oct 31 10:51:08 maistor kernel: ------------[ cut here ]------------
> Oct 31 10:51:08 maistor kernel: WARNING: CPU: 1 PID: 6441 at
> drivers/gpu/drm/i915/intel_display.c:8292
> check_crtc_state+0x5cf/0xa60 [i915]()
> Oct 31 10:51:08 maistor kernel: pipe state doesn't match!
> Oct 31 10:51:08 maistor kernel: Modules linked in: ppdev lp bnep
> rfcomm bluetooth crc16 vmnet(O) parport_pc parport vsock(O) vmci(O)
> vmmon(O) cpufreq_ondemand cpufreq_powersave cpufreq_performance
> cpufreq_stats cpufreq_conservative xt_state xt_tcpudp ipt_REJECT
> xt_limit iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
> nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables
> acpi_pad custom_method sbs sbshc fan acpi_ipmi ipmi_msghandler
> snd_hrtimer binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2
> usb_storage snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep
> snd_pcm_oss snd_mixer_oss snd_pcm iTCO_wdt iTCO_vendor_support
> snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi
> snd_seq_midi_event snd_rawmidi yenta_socket snd_seq pcmcia_rsrc
> lpc_ich acpi_cpufreq snd_seq_device snd_timer snd i2c_i801 arc4
> mperf iwl3945 iwlegacy mac80211 cfg80211 rfkill soundcore irda
> ehci_pci 8250 crc_ccitt joydev processor dcdbas dell_wmi
> sparse_keymap rtc_cmos wmi evdev battery ac serial_core sha256_ssse3
> s
> Oct 31 10:51:08 maistor kernel: ha256_generic cbc hid_generic usbhid
> hid loop dm_crypt dm_mod sg sr_mod cdrom sd_mod firewire_ohci
> firewire_core thermal b44 ssb mmc_core mii pcmcia crc_itu_t
> pcmcia_core i915 cfbfillrect cfbimgblt video button i2c_algo_bit
> cfbcopyarea drm_kms_helper drm intel_agp uhci_hcd ehci_hcd intel_gtt
> agpgart i2c_core thermal_sys freq_table usbcore usb_common
> Oct 31 10:51:08 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg Tainted:
> P        W  O 3.11.6eko2 #1
> Oct 31 10:51:08 maistor kernel: Hardware name: Dell Inc. Latitude
> D520                   /0NF743, BIOS A04 12/18/2006
> Oct 31 10:51:08 maistor kernel: 0000000000000000 0000000000000009
> ffffffff813db19f ffff8800268b1888
> Oct 31 10:51:08 maistor kernel: ffffffff8103f561 ffff880037fd96d8
> ffff8800268b1900 ffff880037c01800
> Oct 31 10:51:08 maistor kernel: 0000000000000001 ffff880037c01c88
> ffffffff8103f645 ffffffffa0162ea2
> Oct 31 10:51:08 maistor kernel: Call Trace:
> Oct 31 10:51:08 maistor kernel: [<ffffffff813db19f>] ?
> dump_stack+0x50/0x80
> Oct 31 10:51:08 maistor kernel: [<ffffffff8103f561>] ?
> warn_slowpath_common+0x81/0xb0
> Oct 31 10:51:08 maistor kernel: [<ffffffff8103f645>] ?
> warn_slowpath_fmt+0x45/0x50
> Oct 31 10:51:08 maistor kernel: [<ffffffffa01106ff>] ?
> check_crtc_state+0x5cf/0xa60 [i915]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa011aeed>] ?
> intel_modeset_check_state+0x2bd/0x730 [i915]
> Oct 31 10:51:08 maistor kernel: [<ffffffff811fa769>] ?
> snprintf+0x39/0x40
> Oct 31 10:51:08 maistor kernel: [<ffffffffa011b3cd>] ?
> intel_set_mode+0x1d/0x30 [i915]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa011bb8a>] ?
> intel_crtc_set_config+0x7aa/0x980 [i915]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa00a8505>] ?
> drm_mode_set_config_internal+0x55/0xd0 [drm]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa00aa378>] ?
> drm_mode_setcrtc+0x118/0x640 [drm]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa009b1ad>] ?
> drm_ioctl+0x4ed/0x5f0 [drm]
> Oct 31 10:51:08 maistor kernel: [<ffffffffa00aa260>] ?
> drm_mode_setplane+0x3a0/0x3a0 [drm]
> Oct 31 10:51:08 maistor kernel: [<ffffffff8111d97b>] ?
> do_vfs_ioctl+0x8b/0x530
> Oct 31 10:51:08 maistor kernel: [<ffffffff810424d5>] ?
> do_setitimer+0x1b5/0x1e0
> Oct 31 10:51:08 maistor kernel: [<ffffffff8111de6d>] ?
> SyS_ioctl+0x4d/0xa0
> Oct 31 10:51:08 maistor kernel: [<ffffffff813e1e56>] ?
> system_call_fastpath+0x1a/0x1f
> Oct 31 10:51:08 maistor kernel: ---[ end trace 65327d016e6b6848 ]---
> Oct 31 10:51:49 maistor kernel: [drm] Setting output timings on
> SDVOB failed
> Oct 31 10:55:06 maistor kernel: perf samples too long (2512 > 2500),
> lowering kernel.perf_event_max_sample_rate to 50000
> Oct 31 11:22:11 maistor kernel: perf samples too long (5003 > 5000),
> lowering kernel.perf_event_max_sample_rate to 25000
> 
> ------- cut --------
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

Re: kernel 3.11.6 general protection fault

[emanoil.kotsev]

Hi, thanks for swift response.
Yes, without those modules loaded it hangs as well. Perhaps I did not 
understand you well - do you mean unloaded or not compiled/installed, or 
even blacklisted. I tried only with unloading them. The custom stuff is 
vmware nothing else, but if I remember issues popped up after 
compiling/patching vmware/player for 3.10
As I said I noticed this recently when I spent more time watching 
youtube videos, but it could be that this only reveals the problem which 
was persistent before (perhaps after vmplayer patch/modules).

I'm using the Notebook with a docking station - and I have a same 
notebook with different bios version. Does it make sense to try the 
kernel on a different bios version?

thanks and regards

На 2013-10-31 15:37, Borislav Petkov написа:
> Adding intel-gfx@ to CC.
> 
> On Thu, Oct 31, 2013 at 03:00:24PM +0100, emanoil.kotsev@fincom.at 
> wrote:
>> Hi again, just noticed that it happens also without starring at
>> youtube, but again in the drm
> 
> Right, I can see a bunch of #GPs happening at
> 
> drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60
> 
> (I'm looking also at your other mail) but also, there are other ones
> which are completely unrelated and happening at random places. The 
> whole
> thing looks like random corruption to me.
> 
> And you have out of tree, proprietary crap loaded so can you reproduce
> the same issue without those modules, i.e. vsock, vmci, vmmon... 
> loaded?
> 
> Leaving the rest for reference.
> 
>> Thanks in advance and kind regards
>> 
>> ------- cut --------
>> 
>> Oct 31 10:51:01 maistor kernel: [drm] Setting output timings on
>> SDVOB failed
>> Oct 31 10:51:01 maistor kernel: lp: driver loaded but no devices found
>> Oct 31 10:51:01 maistor kernel: ppdev: user-space parallel port driver
>> Oct 31 10:51:01 maistor kernel: ------------[ cut here ]------------
>> Oct 31 10:51:01 maistor kernel: WARNING: CPU: 1 PID: 6441 at
>> drivers/gpu/drm/i915/intel_display.c:8292
>> check_crtc_state+0x5cf/0xa60 [i915]()
>> Oct 31 10:51:01 maistor kernel: pipe state doesn't match!
>> Oct 31 10:51:01 maistor kernel: Modules linked in: ppdev lp bnep
>> rfcomm bluetooth crc16 vmnet(O) parport_pc parport vsock(O) vmci(O)
>> vmmon(O) cpufreq_ondemand cpufreq_powersave cpufreq_performance
>> cpufreq_stats cpufreq_conservative xt_state xt_tcpudp ipt_REJECT
>> xt_limit iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
>> nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables
>> acpi_pad custom_method sbs sbshc fan acpi_ipmi ipmi_msghandler
>> snd_hrtimer binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2
>> usb_storage snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep
>> snd_pcm_oss snd_mixer_oss snd_pcm iTCO_wdt iTCO_vendor_support
>> snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi
>> snd_seq_midi_event snd_rawmidi yenta_socket snd_seq pcmcia_rsrc
>> lpc_ich acpi_cpufreq snd_seq_device snd_timer snd i2c_i801 arc4
>> mperf iwl3945 iwlegacy mac80211 cfg80211 rfkill soundcore irda
>> ehci_pci 8250 crc_ccitt joydev processor dcdbas dell_wmi
>> sparse_keymap rtc_cmos wmi evdev battery ac serial_core sha256_ssse3
>> s
>> Oct 31 10:51:01 maistor kernel: ha256_generic cbc hid_generic usbhid
>> hid loop dm_crypt dm_mod sg sr_mod cdrom sd_mod firewire_ohci
>> firewire_core thermal b44 ssb mmc_core mii pcmcia crc_itu_t
>> pcmcia_core i915 cfbfillrect cfbimgblt video button i2c_algo_bit
>> cfbcopyarea drm_kms_helper drm intel_agp uhci_hcd ehci_hcd intel_gtt
>> agpgart i2c_core thermal_sys freq_table usbcore usb_common
>> Oct 31 10:51:01 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg Tainted:
>> P           O 3.11.6eko2 #1
>> Oct 31 10:51:01 maistor kernel: Hardware name: Dell Inc. Latitude
>> D520                   /0NF743, BIOS A04 12/18/2006
>> Oct 31 10:51:01 maistor kernel: 0000000000000000 0000000000000009
>> ffffffff813db19f ffff8800268b1888
>> Oct 31 10:51:01 maistor kernel: ffffffff8103f561 ffff880037fd96d8
>> ffff8800268b1900 ffff880037c01800
>> Oct 31 10:51:01 maistor kernel: 0000000000000001 ffff880037c01c88
>> ffffffff8103f645 ffffffffa0162ea2
>> Oct 31 10:51:01 maistor kernel: Call Trace:
>> Oct 31 10:51:01 maistor kernel: [<ffffffff813db19f>] ?
>> dump_stack+0x50/0x80
>> Oct 31 10:51:01 maistor kernel: [<ffffffff8103f561>] ?
>> warn_slowpath_common+0x81/0xb0
>> Oct 31 10:51:01 maistor kernel: [<ffffffff8103f645>] ?
>> warn_slowpath_fmt+0x45/0x50
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa01106ff>] ?
>> check_crtc_state+0x5cf/0xa60 [i915]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa011aeed>] ?
>> intel_modeset_check_state+0x2bd/0x730 [i915]
>> Oct 31 10:51:01 maistor kernel: [<ffffffff811fa769>] ?
>> snprintf+0x39/0x40
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa011b3cd>] ?
>> intel_set_mode+0x1d/0x30 [i915]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa011bb8a>] ?
>> intel_crtc_set_config+0x7aa/0x980 [i915]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa00a8505>] ?
>> drm_mode_set_config_internal+0x55/0xd0 [drm]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa00aa378>] ?
>> drm_mode_setcrtc+0x118/0x640 [drm]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa009b1ad>] ?
>> drm_ioctl+0x4ed/0x5f0 [drm]
>> Oct 31 10:51:01 maistor kernel: [<ffffffffa00aa260>] ?
>> drm_mode_setplane+0x3a0/0x3a0 [drm]
>> Oct 31 10:51:01 maistor kernel: [<ffffffff8111d97b>] ?
>> do_vfs_ioctl+0x8b/0x530
>> Oct 31 10:51:01 maistor kernel: [<ffffffff8111de6d>] ?
>> SyS_ioctl+0x4d/0xa0
>> Oct 31 10:51:01 maistor kernel: [<ffffffff813e1e56>] ?
>> system_call_fastpath+0x1a/0x1f
>> Oct 31 10:51:01 maistor kernel: ---[ end trace 65327d016e6b6847 ]---
>> Oct 31 10:51:08 maistor kernel: [drm] Setting output timings on
>> SDVOB failed
>> Oct 31 10:51:08 maistor kernel: ------------[ cut here ]------------
>> Oct 31 10:51:08 maistor kernel: WARNING: CPU: 1 PID: 6441 at
>> drivers/gpu/drm/i915/intel_display.c:8292
>> check_crtc_state+0x5cf/0xa60 [i915]()
>> Oct 31 10:51:08 maistor kernel: pipe state doesn't match!
>> Oct 31 10:51:08 maistor kernel: Modules linked in: ppdev lp bnep
>> rfcomm bluetooth crc16 vmnet(O) parport_pc parport vsock(O) vmci(O)
>> vmmon(O) cpufreq_ondemand cpufreq_powersave cpufreq_performance
>> cpufreq_stats cpufreq_conservative xt_state xt_tcpudp ipt_REJECT
>> xt_limit iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
>> nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables
>> acpi_pad custom_method sbs sbshc fan acpi_ipmi ipmi_msghandler
>> snd_hrtimer binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2
>> usb_storage snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep
>> snd_pcm_oss snd_mixer_oss snd_pcm iTCO_wdt iTCO_vendor_support
>> snd_seq_dummy snd_page_alloc snd_seq_oss snd_seq_midi
>> snd_seq_midi_event snd_rawmidi yenta_socket snd_seq pcmcia_rsrc
>> lpc_ich acpi_cpufreq snd_seq_device snd_timer snd i2c_i801 arc4
>> mperf iwl3945 iwlegacy mac80211 cfg80211 rfkill soundcore irda
>> ehci_pci 8250 crc_ccitt joydev processor dcdbas dell_wmi
>> sparse_keymap rtc_cmos wmi evdev battery ac serial_core sha256_ssse3
>> s
>> Oct 31 10:51:08 maistor kernel: ha256_generic cbc hid_generic usbhid
>> hid loop dm_crypt dm_mod sg sr_mod cdrom sd_mod firewire_ohci
>> firewire_core thermal b44 ssb mmc_core mii pcmcia crc_itu_t
>> pcmcia_core i915 cfbfillrect cfbimgblt video button i2c_algo_bit
>> cfbcopyarea drm_kms_helper drm intel_agp uhci_hcd ehci_hcd intel_gtt
>> agpgart i2c_core thermal_sys freq_table usbcore usb_common
>> Oct 31 10:51:08 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg Tainted:
>> P        W  O 3.11.6eko2 #1
>> Oct 31 10:51:08 maistor kernel: Hardware name: Dell Inc. Latitude
>> D520                   /0NF743, BIOS A04 12/18/2006
>> Oct 31 10:51:08 maistor kernel: 0000000000000000 0000000000000009
>> ffffffff813db19f ffff8800268b1888
>> Oct 31 10:51:08 maistor kernel: ffffffff8103f561 ffff880037fd96d8
>> ffff8800268b1900 ffff880037c01800
>> Oct 31 10:51:08 maistor kernel: 0000000000000001 ffff880037c01c88
>> ffffffff8103f645 ffffffffa0162ea2
>> Oct 31 10:51:08 maistor kernel: Call Trace:
>> Oct 31 10:51:08 maistor kernel: [<ffffffff813db19f>] ?
>> dump_stack+0x50/0x80
>> Oct 31 10:51:08 maistor kernel: [<ffffffff8103f561>] ?
>> warn_slowpath_common+0x81/0xb0
>> Oct 31 10:51:08 maistor kernel: [<ffffffff8103f645>] ?
>> warn_slowpath_fmt+0x45/0x50
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa01106ff>] ?
>> check_crtc_state+0x5cf/0xa60 [i915]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa011aeed>] ?
>> intel_modeset_check_state+0x2bd/0x730 [i915]
>> Oct 31 10:51:08 maistor kernel: [<ffffffff811fa769>] ?
>> snprintf+0x39/0x40
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa011b3cd>] ?
>> intel_set_mode+0x1d/0x30 [i915]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa011bb8a>] ?
>> intel_crtc_set_config+0x7aa/0x980 [i915]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa00a8505>] ?
>> drm_mode_set_config_internal+0x55/0xd0 [drm]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa00aa378>] ?
>> drm_mode_setcrtc+0x118/0x640 [drm]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa009b1ad>] ?
>> drm_ioctl+0x4ed/0x5f0 [drm]
>> Oct 31 10:51:08 maistor kernel: [<ffffffffa00aa260>] ?
>> drm_mode_setplane+0x3a0/0x3a0 [drm]
>> Oct 31 10:51:08 maistor kernel: [<ffffffff8111d97b>] ?
>> do_vfs_ioctl+0x8b/0x530
>> Oct 31 10:51:08 maistor kernel: [<ffffffff810424d5>] ?
>> do_setitimer+0x1b5/0x1e0
>> Oct 31 10:51:08 maistor kernel: [<ffffffff8111de6d>] ?
>> SyS_ioctl+0x4d/0xa0
>> Oct 31 10:51:08 maistor kernel: [<ffffffff813e1e56>] ?
>> system_call_fastpath+0x1a/0x1f
>> Oct 31 10:51:08 maistor kernel: ---[ end trace 65327d016e6b6848 ]---
>> Oct 31 10:51:49 maistor kernel: [drm] Setting output timings on
>> SDVOB failed
>> Oct 31 10:55:06 maistor kernel: perf samples too long (2512 > 2500),
>> lowering kernel.perf_event_max_sample_rate to 50000
>> Oct 31 11:22:11 maistor kernel: perf samples too long (5003 > 5000),
>> lowering kernel.perf_event_max_sample_rate to 25000
>> 
>> ------- cut --------
>> 
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe 
>> linux-kernel" in
>> the body of a message to majordomo@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: kernel 3.11.6 general protection fault

[Borislav Petkov]

Please do not top-post.

On Thu, Oct 31, 2013 at 04:52:54PM +0100, emanoil.kotsev@fincom.at wrote:
> Hi, thanks for swift response.
> Yes, without those modules loaded it hangs as well. Perhaps I did
> not understand you well - do you mean unloaded or not
> compiled/installed, or even blacklisted. I tried only with unloading
> them.

Right, try to build a kernel from pristine 3.11.6 sources without any
vmware code patched in or loaded. To be sure, get the sources anew so
that you don't have any remnants of those modules and build the whole
thing from scratch.

AFAIK, those vendor packages have some hooks into the kernel
installation path so make sure you remove those vmware packages too with
your distro's package manager or however they are being removed.

> The custom stuff is vmware nothing else, but if I remember issues
> popped up after compiling/patching vmware/player for 3.10 As I said
> I noticed this recently when I spent more time watching youtube
> videos, but it could be that this only reveals the problem which was
> persistent before (perhaps after vmplayer patch/modules).

Yeah, from the looks of it, it probably would happen if you do other
things too.

> I'm using the Notebook with a docking station - and I have a same
> notebook with different bios version. Does it make sense to try the
> kernel on a different bios version?

Well, since you started seeing this after patching 3.10, I don't think
the BIOS was the problem so no need to do any BIOS updates for now.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

On Fri, Nov 01, 2013 at 10:18:49AM +0100, MPhil. Emanoil Kotsev wrote:
> On Thursday 31 October 2013 17:44:03 you wrote:
> > Please do not top-post.
> 
> Sorry for top posting

No probs :). Btw, one more thing: when you reply, make sure you hit
reply-to-all so that CC list remains intact.

> I tried with no success. I remember that I also tested this with an
> older version 3.3.8 which was working fine before, but now it dies (it
> was not locked however, so I could reboot) If you notice this kernel
> was not tainted.

Right, the fact that you're triggering it with different kernels could
point at a hardware issue, maybe DIMMs going bad.

You could try taking out DIMMs one by one and see whether it still
happens. Somewhere it said the BIOS version is from 2006 so it is kinda
of an older box so I can imagine stuff going kaputtski :)

And the #GP below doesn't point at DRM anywhere which strengthens the
suspicion of a hw issue.

> 
> Oct 17 14:40:36 maistor kernel: general protection fault: 0000 [#1] PREEMPT 
> SMP
> Oct 17 14:40:36 maistor kernel: CPU 0
> Oct 17 14:40:36 maistor kernel: Modules linked in: snd_hrtimer nfs lockd 
> nfs_acl sunrpc iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack 
> nf_defrag_ipv4 acpi
> _cpufreq mperf iptable_mangle iptable_filter ip_tables x_tables 
> cpufreq_ondemand cpufreq_powersave cpufreq_performance cpufreq_stats 
> freq_table cpufreq_conse
> rvative parport_pc ppdev lp parport bnep rfcomm bluetooth crc16 acpi_ipmi 
> ipmi_msghandler acpi_pad sbs sbshc pci_slot fan binfmt_misc uinput fuse 
> af_packet i
> pv6 firewire_sbp2 uvcvideo videobuf2_core snd_usb_audio videodev 
> snd_usbmidi_lib v4l2_compat_ioctl32 videobuf2_vmalloc videobuf2_memops 
> snd_hda_codec_idt snd
> _hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm 
> snd_seq_dummy snd_seq_oss snd_seq_midi yenta_socket snd_rawmidi 
> snd_seq_midi_event snd_s
> eq snd_timer snd_seq_device snd pcmcia_rsrc iTCO_wdt iTCO_vendor_support arc4 
> iwl3945 iwlegacy mac80211 soundcore cfg80211 rfkill i2c_i801 8250_pnp 
> dell_wmi
> sparse_keymap processor snd_page_alloc wmi dcdbas rtc_cmos 8250 evdev joydev 
> battery a
> Oct 17 14:40:36 maistor kernel: c serial_core sha256_generic cryptd aes_x86_64 
> aes_generic cbc usbhid hid loop dm_crypt dm_mod usb_storage usb_libusual uas 
> i
> 915 cfbfillrect cfbimgblt thermal sd_mod sg sr_mod cdrom firewire_ohci 
> firewire_core crc_itu_t b44 ssb mmc_core mii video uhci_hcd pcmcia 
> pcmcia_core ehci_hc
> d button cfbcopyarea i2c_algo_bit drm_kms_helper usbcore intel_agp intel_gtt 
> drm usb_common agpgart i2c_core thermal_sys hwmon [last unloaded: 
> scsi_wait_scan
> ]
> Oct 17 14:40:36 maistor kernel:
> Oct 17 14:40:36 maistor kernel: Pid: 6082, comm: firefox Not tainted 3.3.8eko2 
> #4 Dell Inc. Latitude D520                   /0NF743
> Oct 17 14:40:36 maistor kernel: RIP: 0010:[<ffffffff8117076f>]  
> [<ffffffff8117076f>] plist_del+0x3b/0x66
> Oct 17 14:40:36 maistor kernel: RSP: 0018:ffff880032025ce0  EFLAGS: 00010246
> Oct 17 14:40:36 maistor kernel: RAX: ffff880032131cf0 RBX: ffff8800322212f0 
> RCX: fcff880032131cf0
> Oct 17 14:40:36 maistor kernel: RDX: ffff880032131cf0 RSI: ffffffff8150f338 
> RDI: ffff880032131ce8
> Oct 17 14:40:36 maistor kernel: RBP: ffff880032131ce8 R08: fcff880032131cf0 
> R09: ffff880032025f08
> Oct 17 14:40:36 maistor kernel: R10: 000000007fffffff R11: 0000000000000283 
> R12: ffffffff8150f330
> Oct 17 14:40:36 maistor kernel: R13: ffffffff8150fdf8 R14: 0000000000000000 
> R15: 0000000000000000
> Oct 17 14:40:36 maistor kernel: FS:  00007fc2ec3e4740(0000) 
> GS:ffff88007f400000(0000) knlGS:0000000000000000
> Oct 17 14:40:36 maistor kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 
> 0000000080050033
> Oct 17 14:40:36 maistor kernel: CR2: 00002ac4fd23b000 CR3: 000000003221e000 
> CR4: 00000000000006f0
> Oct 17 14:40:36 maistor kernel: DR0: 0000000000000000 DR1: 0000000000000000 
> DR2: 0000000000000000
> Oct 17 14:40:36 maistor kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 
> DR7: 0000000000000400
> Oct 17 14:40:36 maistor kernel: Process firefox (pid: 6082, threadinfo 
> ffff880032024000, task ffff8800320cb2b0)
> Oct 17 14:40:36 maistor kernel: Stack:
> Oct 17 14:40:36 maistor kernel: ffffffff8105f7cd 0000000000000000 
> 0000000000000000 ffff880032131ce8
> Oct 17 14:40:36 maistor kernel: ffffffff81060d51 00000000525fdac4 
> ffff880032025d58 ffff880000000001
> Oct 17 14:40:36 maistor kernel: 0000000055aa3e58 ffffffff8150f320 
> 0000000100000001 ffffffff8150f338
> Oct 17 14:40:36 maistor kernel: Call Trace:
> Oct 17 14:40:36 maistor kernel: [<ffffffff8105f7cd>] ? wake_futex+0x16/0x45
> Oct 17 14:40:36 maistor kernel: [<ffffffff81060d51>] ? 
> futex_requeue+0x4a2/0x690
> Oct 17 14:40:36 maistor kernel: [<ffffffff81061042>] ? do_futex+0x103/0x8be
> Oct 17 14:40:36 maistor kernel: [<ffffffff810c303e>] ? do_sync_read+0xb1/0xea
> Oct 17 14:40:36 maistor kernel: [<ffffffff81253289>] ? 
> sys_recvfrom+0x113/0x12b
> Oct 17 14:40:36 maistor kernel: [<ffffffff81061927>] ? sys_futex+0x12a/0x142
> Oct 17 14:40:36 maistor kernel: [<ffffffff810c3b56>] ? sys_read+0x62/0x6e
> Oct 17 14:40:36 maistor kernel: [<ffffffff812eafa2>] ? 
> system_call_fastpath+0x16/0x1b
> Oct 17 14:40:36 maistor kernel: Code: 18 48 39 f0 74 1d 48 8b 48 f0 48 8d 70 
> f0 48 39 f1 75 10 49 89 48 08 4c 89 40 f0 48 89 50 f8 48 89 4f 08 48 8b 4f 08 
> 48 8b 47 10 <48> 89 41 08 48 89 08 48 89 57 08 48 89 57 10 48 8b 4f 18 48 8b
> Oct 17 14:40:36 maistor kernel: RSP <ffff880032025ce0>
> Oct 17 14:40:36 maistor kernel: ---[ end trace a3d22cd9bf0e297f ]---
> Oct 17 14:40:36 maistor kernel: note: firefox[6082] exited with preempt_count 
> 2
> Oct 17 14:40:50 maistor shutdown[18878]: shutting down for system reboot

[ … ]

> I did system upgrade recently. The thing is I never had time to watch youtube

what exactly do you mean by "system upgrade"? Hardware, distro upgrade?

> I'm wondering if this matters

Nah.

> [*] Detect Hard and Soft Lockups

That's just the watchdog which checks whether your machine is doing any
progress.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi

On Friday 01 November 2013 12:27:55 Borislav Petkov wrote:
> On Fri, Nov 01, 2013 at 10:18:49AM +0100, MPhil. Emanoil Kotsev wrote:
> > On Thursday 31 October 2013 17:44:03 you wrote:
> > > Please do not top-post.
> >
> > Sorry for top posting
>
> No probs :). Btw, one more thing: when you reply, make sure you hit
> reply-to-all so that CC list remains intact.

yes, I didn't notice this

>
> > I tried with no success. I remember that I also tested this with an
> > older version 3.3.8 which was working fine before, but now it dies (it
> > was not locked however, so I could reboot) If you notice this kernel
> > was not tainted.
>
> Right, the fact that you're triggering it with different kernels could
> point at a hardware issue, maybe DIMMs going bad.

I already checked this (before bothering people like you)

>
> You could try taking out DIMMs one by one and see whether it still
> happens. Somewhere it said the BIOS version is from 2006 so it is kinda
> of an older box so I can imagine stuff going kaputtski :)
>
> And the #GP below doesn't point at DRM anywhere which strengthens the
> suspicion of a hw issue.
>
> > Oct 17 14:40:36 maistor kernel: general protection fault: 0000 [#1]
> > PREEMPT SMP
> > Oct 17 14:40:36 maistor kernel: CPU 0
> > Oct 17 14:40:36 maistor kernel: Modules linked in: snd_hrtimer nfs lockd
> > nfs_acl sunrpc iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
> > nf_defrag_ipv4 acpi
> > _cpufreq mperf iptable_mangle iptable_filter ip_tables x_tables
> > cpufreq_ondemand cpufreq_powersave cpufreq_performance cpufreq_stats
> > freq_table cpufreq_conse
> > rvative parport_pc ppdev lp parport bnep rfcomm bluetooth crc16 acpi_ipmi
> > ipmi_msghandler acpi_pad sbs sbshc pci_slot fan binfmt_misc uinput fuse
> > af_packet i
> > pv6 firewire_sbp2 uvcvideo videobuf2_core snd_usb_audio videodev
> > snd_usbmidi_lib v4l2_compat_ioctl32 videobuf2_vmalloc videobuf2_memops
> > snd_hda_codec_idt snd
> > _hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm
> > snd_seq_dummy snd_seq_oss snd_seq_midi yenta_socket snd_rawmidi
> > snd_seq_midi_event snd_s
> > eq snd_timer snd_seq_device snd pcmcia_rsrc iTCO_wdt iTCO_vendor_support
> > arc4 iwl3945 iwlegacy mac80211 soundcore cfg80211 rfkill i2c_i801
> > 8250_pnp dell_wmi
> > sparse_keymap processor snd_page_alloc wmi dcdbas rtc_cmos 8250 evdev
> > joydev battery a
> > Oct 17 14:40:36 maistor kernel: c serial_core sha256_generic cryptd
> > aes_x86_64 aes_generic cbc usbhid hid loop dm_crypt dm_mod usb_storage
> > usb_libusual uas i
> > 915 cfbfillrect cfbimgblt thermal sd_mod sg sr_mod cdrom firewire_ohci
> > firewire_core crc_itu_t b44 ssb mmc_core mii video uhci_hcd pcmcia
> > pcmcia_core ehci_hc
> > d button cfbcopyarea i2c_algo_bit drm_kms_helper usbcore intel_agp
> > intel_gtt drm usb_common agpgart i2c_core thermal_sys hwmon [last
> > unloaded: scsi_wait_scan
> > ]
> > Oct 17 14:40:36 maistor kernel:
> > Oct 17 14:40:36 maistor kernel: Pid: 6082, comm: firefox Not tainted
> > 3.3.8eko2 #4 Dell Inc. Latitude D520                   /0NF743
> > Oct 17 14:40:36 maistor kernel: RIP: 0010:[<ffffffff8117076f>]
> > [<ffffffff8117076f>] plist_del+0x3b/0x66
> > Oct 17 14:40:36 maistor kernel: RSP: 0018:ffff880032025ce0  EFLAGS:
> > 00010246 Oct 17 14:40:36 maistor kernel: RAX: ffff880032131cf0 RBX:
> > ffff8800322212f0 RCX: fcff880032131cf0
> > Oct 17 14:40:36 maistor kernel: RDX: ffff880032131cf0 RSI:
> > ffffffff8150f338 RDI: ffff880032131ce8
> > Oct 17 14:40:36 maistor kernel: RBP: ffff880032131ce8 R08:
> > fcff880032131cf0 R09: ffff880032025f08
> > Oct 17 14:40:36 maistor kernel: R10: 000000007fffffff R11:
> > 0000000000000283 R12: ffffffff8150f330
> > Oct 17 14:40:36 maistor kernel: R13: ffffffff8150fdf8 R14:
> > 0000000000000000 R15: 0000000000000000
> > Oct 17 14:40:36 maistor kernel: FS:  00007fc2ec3e4740(0000)
> > GS:ffff88007f400000(0000) knlGS:0000000000000000
> > Oct 17 14:40:36 maistor kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
> > 0000000080050033
> > Oct 17 14:40:36 maistor kernel: CR2: 00002ac4fd23b000 CR3:
> > 000000003221e000 CR4: 00000000000006f0
> > Oct 17 14:40:36 maistor kernel: DR0: 0000000000000000 DR1:
> > 0000000000000000 DR2: 0000000000000000
> > Oct 17 14:40:36 maistor kernel: DR3: 0000000000000000 DR6:
> > 00000000ffff0ff0 DR7: 0000000000000400
> > Oct 17 14:40:36 maistor kernel: Process firefox (pid: 6082, threadinfo
> > ffff880032024000, task ffff8800320cb2b0)
> > Oct 17 14:40:36 maistor kernel: Stack:
> > Oct 17 14:40:36 maistor kernel: ffffffff8105f7cd 0000000000000000
> > 0000000000000000 ffff880032131ce8
> > Oct 17 14:40:36 maistor kernel: ffffffff81060d51 00000000525fdac4
> > ffff880032025d58 ffff880000000001
> > Oct 17 14:40:36 maistor kernel: 0000000055aa3e58 ffffffff8150f320
> > 0000000100000001 ffffffff8150f338
> > Oct 17 14:40:36 maistor kernel: Call Trace:
> > Oct 17 14:40:36 maistor kernel: [<ffffffff8105f7cd>] ?
> > wake_futex+0x16/0x45 Oct 17 14:40:36 maistor kernel: [<ffffffff81060d51>]
> > ?
> > futex_requeue+0x4a2/0x690
> > Oct 17 14:40:36 maistor kernel: [<ffffffff81061042>] ?
> > do_futex+0x103/0x8be Oct 17 14:40:36 maistor kernel: [<ffffffff810c303e>]
> > ? do_sync_read+0xb1/0xea Oct 17 14:40:36 maistor kernel:
> > [<ffffffff81253289>] ?
> > sys_recvfrom+0x113/0x12b
> > Oct 17 14:40:36 maistor kernel: [<ffffffff81061927>] ?
> > sys_futex+0x12a/0x142 Oct 17 14:40:36 maistor kernel:
> > [<ffffffff810c3b56>] ? sys_read+0x62/0x6e Oct 17 14:40:36 maistor kernel:
> > [<ffffffff812eafa2>] ?
> > system_call_fastpath+0x16/0x1b
> > Oct 17 14:40:36 maistor kernel: Code: 18 48 39 f0 74 1d 48 8b 48 f0 48 8d
> > 70 f0 48 39 f1 75 10 49 89 48 08 4c 89 40 f0 48 89 50 f8 48 89 4f 08 48
> > 8b 4f 08 48 8b 47 10 <48> 89 41 08 48 89 08 48 89 57 08 48 89 57 10 48 8b
> > 4f 18 48 8b Oct 17 14:40:36 maistor kernel: RSP <ffff880032025ce0>
> > Oct 17 14:40:36 maistor kernel: ---[ end trace a3d22cd9bf0e297f ]---
> > Oct 17 14:40:36 maistor kernel: note: firefox[6082] exited with
> > preempt_count 2
> > Oct 17 14:40:50 maistor shutdown[18878]: shutting down for system reboot
>
> [ … ]
>
> > I did system upgrade recently. The thing is I never had time to watch
> > youtube
>
> what exactly do you mean by "system upgrade"? Hardware, distro upgrade?
I'm using debian with kde-trinity. I upgraded from squeeze to wheeze.
I looked yesterday into the package list and found few packages remainded 
still configured, so I cleaned all up.
>
> > I'm wondering if this matters
>
> Nah.
>
> > [*] Detect Hard and Soft Lockups
>
> That's just the watchdog which checks whether your machine is doing any
> progress.

OK thanks.
I revisited the .config and removed/added some options which were 
(not)recommended, compiled and rebooted. For now it was working fine all day 
long without an issue. If it keeps working it would be great. However I don't 
think it's worth to track it further down. It might have been some unlucky 
combination of events.

regards
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

(sorry it replys automaticaly only to the sender - now added the list)

What do the intel-gfx people think?

====== original mail follows =======
Hi sorry for bothering you once again. 

I noticed most of the issues are coming from drm (I have the stupid "Intel 
Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller (rev 03)")

So I checked today the logs again and found out it crashed in the mornign when 
turning on the notebook in the office.

Is there something you can conclude from the trace below and another 
question - why is it checking CRTC as I have LVDS, VGA1 and DVI1 - actually 
using only the LVDS and DVI outputs

Thanks again for taking your time



Nov 13 09:36:21 maistor kernel: [   40.447271] ------------[ cut 
here ]------------
Nov 13 09:36:21 maistor kernel: [   40.447311] WARNING: CPU: 1 PID: 4142 at 
drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60 [i915]
()
Nov 13 09:36:21 maistor kernel: [   40.447313] pipe state doesn't match!
Nov 13 09:36:21 maistor kernel: [   40.447315] Modules linked in: snd_hrtimer 
acpi_pad sbs sbshc fan binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2 
snd
_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss 
snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi 
snd_seq_midi_eve
nt snd_rawmidi snd_seq snd_seq_device snd_timer arc4 iTCO_wdt snd gpio_ich 
iwl3945 dell_wmi sparse_keymap i2c_i801 iTCO_vendor_support ehci_pci iwlegacy 
mac8
0211 cfg80211 soundcore rfkill dell_laptop lpc_ich yenta_socket pcmcia_rsrc 
irda 8250 evdev wmi processor dcdbas rtc_cmos battery crc_ccitt ac joydev 
sha256_
ssse3 sha256_generic cbc hid_generic usbhid hid loop dm_crypt dm_mod sg b44 
sr_mod cdrom ssb i915 cfbfillrect cfbimgblt mmc_core mii pcmcia pcmcia_core 
uhci_
hcd i2c_algo_bit cfbcopyarea firewire_ohci video backlight firewire_core 
crc_itu_t drm_kms_helper drm ehci_hcd sd_mod i2c_core thermal thermal_sys 
freq_table
 usbcore usb_common button intel_agp intel_gtt agpgart
Nov 13 09:36:21 maistor kernel: [   40.447384] CPU: 1 PID: 4142 Comm: Xorg 
Tainted: P             3.11.6eko2 #3
Nov 13 09:36:21 maistor kernel: [   40.447386] Hardware name: Dell Inc. 
Latitude D520                   /0NF743, BIOS A04 12/18/2006
Nov 13 09:36:21 maistor kernel: [   40.447388]  0000000000000000 
0000000000000009 ffffffff813ce8ab ffff880079c8f888
Nov 13 09:36:21 maistor kernel: [   40.447392]  ffffffff81038001 
ffff88007a2596d8 ffff880079c8f900 ffff880037f3a000
Nov 13 09:36:21 maistor kernel: [   40.447395]  0000000000000001 
ffff880037f3a488 ffffffff810380e5 ffffffffa0295531
Nov 13 09:36:21 maistor kernel: [   40.447398] Call Trace:
Nov 13 09:36:21 maistor kernel: [   40.447407]  [<ffffffff813ce8ab>] ? 
dump_stack+0x41/0x51
Nov 13 09:36:21 maistor kernel: [   40.447412]  [<ffffffff81038001>] ? 
warn_slowpath_common+0x81/0xb0
Nov 13 09:36:21 maistor kernel: [   40.447415]  [<ffffffff810380e5>] ? 
warn_slowpath_fmt+0x45/0x50
Nov 13 09:36:21 maistor kernel: [   40.447427]  [<ffffffffa024338f>] ? 
check_crtc_state+0x5cf/0xa60 [i915]
Nov 13 09:36:21 maistor kernel: [   40.447440]  [<ffffffffa024db7d>] ? 
intel_modeset_check_state+0x2bd/0x730 [i915]
Nov 13 09:36:21 maistor kernel: [   40.447445]  [<ffffffff811ec219>] ? 
snprintf+0x39/0x40
Nov 13 09:36:21 maistor kernel: [   40.447456]  [<ffffffffa024e05d>] ? 
intel_set_mode+0x1d/0x30 [i915]
Nov 13 09:36:21 maistor kernel: [   40.447467]  [<ffffffffa024e81a>] ? 
intel_crtc_set_config+0x7aa/0x980 [i915]
Nov 13 09:36:21 maistor kernel: [   40.447481]  [<ffffffffa00f9155>] ? 
drm_mode_set_config_internal+0x55/0xd0 [drm]
Nov 13 09:36:21 maistor kernel: [   40.447490]  [<ffffffffa00fb118>] ? 
drm_mode_setcrtc+0x118/0x640 [drm]
Nov 13 09:36:21 maistor kernel: [   40.447497]  [<ffffffffa00ec11d>] ? 
drm_ioctl+0x4ed/0x5f0 [drm]
Nov 13 09:36:21 maistor kernel: [   40.447507]  [<ffffffffa00fb000>] ? 
drm_mode_setplane+0x3a0/0x3a0 [drm]
Nov 13 09:36:21 maistor kernel: [   40.447512]  [<ffffffff8111428b>] ? 
do_vfs_ioctl+0x8b/0x520
Nov 13 09:36:21 maistor kernel: [   40.447515]  [<ffffffff8111476d>] ? 
SyS_ioctl+0x4d/0xa0
Nov 13 09:36:21 maistor kernel: [   40.447519]  [<ffffffff813d4c56>] ? 
system_call_fastpath+0x1a/0x1f
Nov 13 09:36:21 maistor kernel: [   40.447521] ---[ end trace 
307df46ce6dc8ed1 ]---

Re: kernel 3.11.6 general protection fault

[Daniel Vetter]

On Wed, Nov 13, 2013 at 08:58:29PM +0100, MPhil. Emanoil Kotsev wrote:
> (sorry it replys automaticaly only to the sender - now added the list)
> 
> What do the intel-gfx people think?
> 
> ====== original mail follows =======
> Hi sorry for bothering you once again. 
> 
> I noticed most of the issues are coming from drm (I have the stupid "Intel 
> Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
> Controller (rev 03)")
> 
> So I checked today the logs again and found out it crashed in the mornign when 
> turning on the notebook in the office.
> 
> Is there something you can conclude from the trace below and another 
> question - why is it checking CRTC as I have LVDS, VGA1 and DVI1 - actually 
> using only the LVDS and DVI outputs
> 
> Thanks again for taking your time

Testing on latest drm-intel-nightly from

http://cgit.freedesktop.org/~danvet/drm-intel/

If that doesn't help then please boot with drm.debug=0xe, reproduce the
issue and then attach the complete dmesg. Please make sure everything
starting from boot messages is in there, increase the dmesg buffer with
log_buf_len=4M or so if that isn't the case.
-Daniel

> 
> 
> 
> Nov 13 09:36:21 maistor kernel: [   40.447271] ------------[ cut 
> here ]------------
> Nov 13 09:36:21 maistor kernel: [   40.447311] WARNING: CPU: 1 PID: 4142 at 
> drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60 [i915]
> ()
> Nov 13 09:36:21 maistor kernel: [   40.447313] pipe state doesn't match!
> Nov 13 09:36:21 maistor kernel: [   40.447315] Modules linked in: snd_hrtimer 
> acpi_pad sbs sbshc fan binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2 
> snd
> _hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss 
> snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi 
> snd_seq_midi_eve
> nt snd_rawmidi snd_seq snd_seq_device snd_timer arc4 iTCO_wdt snd gpio_ich 
> iwl3945 dell_wmi sparse_keymap i2c_i801 iTCO_vendor_support ehci_pci iwlegacy 
> mac8
> 0211 cfg80211 soundcore rfkill dell_laptop lpc_ich yenta_socket pcmcia_rsrc 
> irda 8250 evdev wmi processor dcdbas rtc_cmos battery crc_ccitt ac joydev 
> sha256_
> ssse3 sha256_generic cbc hid_generic usbhid hid loop dm_crypt dm_mod sg b44 
> sr_mod cdrom ssb i915 cfbfillrect cfbimgblt mmc_core mii pcmcia pcmcia_core 
> uhci_
> hcd i2c_algo_bit cfbcopyarea firewire_ohci video backlight firewire_core 
> crc_itu_t drm_kms_helper drm ehci_hcd sd_mod i2c_core thermal thermal_sys 
> freq_table
>  usbcore usb_common button intel_agp intel_gtt agpgart
> Nov 13 09:36:21 maistor kernel: [   40.447384] CPU: 1 PID: 4142 Comm: Xorg 
> Tainted: P             3.11.6eko2 #3
> Nov 13 09:36:21 maistor kernel: [   40.447386] Hardware name: Dell Inc. 
> Latitude D520                   /0NF743, BIOS A04 12/18/2006
> Nov 13 09:36:21 maistor kernel: [   40.447388]  0000000000000000 
> 0000000000000009 ffffffff813ce8ab ffff880079c8f888
> Nov 13 09:36:21 maistor kernel: [   40.447392]  ffffffff81038001 
> ffff88007a2596d8 ffff880079c8f900 ffff880037f3a000
> Nov 13 09:36:21 maistor kernel: [   40.447395]  0000000000000001 
> ffff880037f3a488 ffffffff810380e5 ffffffffa0295531
> Nov 13 09:36:21 maistor kernel: [   40.447398] Call Trace:
> Nov 13 09:36:21 maistor kernel: [   40.447407]  [<ffffffff813ce8ab>] ? 
> dump_stack+0x41/0x51
> Nov 13 09:36:21 maistor kernel: [   40.447412]  [<ffffffff81038001>] ? 
> warn_slowpath_common+0x81/0xb0
> Nov 13 09:36:21 maistor kernel: [   40.447415]  [<ffffffff810380e5>] ? 
> warn_slowpath_fmt+0x45/0x50
> Nov 13 09:36:21 maistor kernel: [   40.447427]  [<ffffffffa024338f>] ? 
> check_crtc_state+0x5cf/0xa60 [i915]
> Nov 13 09:36:21 maistor kernel: [   40.447440]  [<ffffffffa024db7d>] ? 
> intel_modeset_check_state+0x2bd/0x730 [i915]
> Nov 13 09:36:21 maistor kernel: [   40.447445]  [<ffffffff811ec219>] ? 
> snprintf+0x39/0x40
> Nov 13 09:36:21 maistor kernel: [   40.447456]  [<ffffffffa024e05d>] ? 
> intel_set_mode+0x1d/0x30 [i915]
> Nov 13 09:36:21 maistor kernel: [   40.447467]  [<ffffffffa024e81a>] ? 
> intel_crtc_set_config+0x7aa/0x980 [i915]
> Nov 13 09:36:21 maistor kernel: [   40.447481]  [<ffffffffa00f9155>] ? 
> drm_mode_set_config_internal+0x55/0xd0 [drm]
> Nov 13 09:36:21 maistor kernel: [   40.447490]  [<ffffffffa00fb118>] ? 
> drm_mode_setcrtc+0x118/0x640 [drm]
> Nov 13 09:36:21 maistor kernel: [   40.447497]  [<ffffffffa00ec11d>] ? 
> drm_ioctl+0x4ed/0x5f0 [drm]
> Nov 13 09:36:21 maistor kernel: [   40.447507]  [<ffffffffa00fb000>] ? 
> drm_mode_setplane+0x3a0/0x3a0 [drm]
> Nov 13 09:36:21 maistor kernel: [   40.447512]  [<ffffffff8111428b>] ? 
> do_vfs_ioctl+0x8b/0x520
> Nov 13 09:36:21 maistor kernel: [   40.447515]  [<ffffffff8111476d>] ? 
> SyS_ioctl+0x4d/0xa0
> Nov 13 09:36:21 maistor kernel: [   40.447519]  [<ffffffff813d4c56>] ? 
> system_call_fastpath+0x1a/0x1f
> Nov 13 09:36:21 maistor kernel: [   40.447521] ---[ end trace 
> 307df46ce6dc8ed1 ]---
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

Some more suggestions, in addition to Daniel's:

On Wed, Nov 13, 2013 at 09:09:14PM +0100, Daniel Vetter wrote:
> > Nov 13 09:36:21 maistor kernel: [   40.447271] ------------[ cut 
> > here ]------------
> > Nov 13 09:36:21 maistor kernel: [   40.447311] WARNING: CPU: 1 PID: 4142 at 
> > drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60 [i915]
> > ()
> > Nov 13 09:36:21 maistor kernel: [   40.447313] pipe state doesn't match!

That's

	if (active &&
	    !intel_pipe_config_compare(dev, &crtc->config, &pipe_config)) {
		WARN(1, "pipe state doesn't match!\n");				<---
		intel_dump_pipe_config(crtc, &pipe_config,
				       "[hw state]");
		intel_dump_pipe_config(crtc, &crtc->config,
				       "[sw state]");
	}

> > Nov 13 09:36:21 maistor kernel: [   40.447315] Modules linked in: snd_hrtimer 
> > acpi_pad sbs sbshc fan binfmt_misc uinput fuse af_packet ipv6 firewire_sbp2 
> > snd
> > _hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss 
> > snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss snd_seq_midi 
> > snd_seq_midi_eve
> > nt snd_rawmidi snd_seq snd_seq_device snd_timer arc4 iTCO_wdt snd gpio_ich 
> > iwl3945 dell_wmi sparse_keymap i2c_i801 iTCO_vendor_support ehci_pci iwlegacy 
> > mac8
> > 0211 cfg80211 soundcore rfkill dell_laptop lpc_ich yenta_socket pcmcia_rsrc 
> > irda 8250 evdev wmi processor dcdbas rtc_cmos battery crc_ccitt ac joydev 
> > sha256_
> > ssse3 sha256_generic cbc hid_generic usbhid hid loop dm_crypt dm_mod sg b44 
> > sr_mod cdrom ssb i915 cfbfillrect cfbimgblt mmc_core mii pcmcia pcmcia_core 
> > uhci_
> > hcd i2c_algo_bit cfbcopyarea firewire_ohci video backlight firewire_core 
> > crc_itu_t drm_kms_helper drm ehci_hcd sd_mod i2c_core thermal thermal_sys 
> > freq_table
> >  usbcore usb_common button intel_agp intel_gtt agpgart
> > Nov 13 09:36:21 maistor kernel: [   40.447384] CPU: 1 PID: 4142 Comm: Xorg 
> > Tainted: P             3.11.6eko2 #3

And there's that taint P again due to the vmware modules.

I know that you tried without the vmware modules where your kernel
wasn't tainted but then you got a #GP which could be something entirely
different. But now you're hitting some sanity-checking code which could
mean there's some corruption happening.

So, can you reproduce that exact same warning, i.e. this one:

WARNING: CPU: 1 PID: 4142 at drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x5cf/0xa60 [i915]()
pipe state doesn't match!

*without* the vmware modules installed?

Also, it wouldn't hurt to try the shiny new 3.12.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi

On Wednesday 13 November 2013 21:33:19 Borislav Petkov wrote:
> Some more suggestions, in addition to Daniel's:
>
> On Wed, Nov 13, 2013 at 09:09:14PM +0100, Daniel Vetter wrote:
> > > Nov 13 09:36:21 maistor kernel: [   40.447271] ------------[ cut
> > > here ]------------
> > > Nov 13 09:36:21 maistor kernel: [   40.447311] WARNING: CPU: 1 PID:
> > > 4142 at drivers/gpu/drm/i915/intel_display.c:8292
> > > check_crtc_state+0x5cf/0xa60 [i915] ()
> > > Nov 13 09:36:21 maistor kernel: [   40.447313] pipe state doesn't
> > > match!
>
> That's
>
> 	if (active &&
> 	    !intel_pipe_config_compare(dev, &crtc->config, &pipe_config)) {
> 		WARN(1, "pipe state doesn't match!\n");				<---
> 		intel_dump_pipe_config(crtc, &pipe_config,
> 				       "[hw state]");
> 		intel_dump_pipe_config(crtc, &crtc->config,
> 				       "[sw state]");
> 	}
>

I looked there, but it would have taken more time then available to get an 
idea on what it is exactly trying to do

> > > Nov 13 09:36:21 maistor kernel: [   40.447315] Modules linked in:
> > > snd_hrtimer acpi_pad sbs sbshc fan binfmt_misc uinput fuse af_packet
> > > ipv6 firewire_sbp2 snd
> > > _hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss
> > > snd_mixer_oss snd_pcm snd_page_alloc snd_seq_dummy snd_seq_oss
> > > snd_seq_midi
> > > snd_seq_midi_eve
> > > nt snd_rawmidi snd_seq snd_seq_device snd_timer arc4 iTCO_wdt snd
> > > gpio_ich iwl3945 dell_wmi sparse_keymap i2c_i801 iTCO_vendor_support
> > > ehci_pci iwlegacy mac8
> > > 0211 cfg80211 soundcore rfkill dell_laptop lpc_ich yenta_socket
> > > pcmcia_rsrc irda 8250 evdev wmi processor dcdbas rtc_cmos battery
> > > crc_ccitt ac joydev sha256_
> > > ssse3 sha256_generic cbc hid_generic usbhid hid loop dm_crypt dm_mod sg
> > > b44 sr_mod cdrom ssb i915 cfbfillrect cfbimgblt mmc_core mii pcmcia
> > > pcmcia_core uhci_
> > > hcd i2c_algo_bit cfbcopyarea firewire_ohci video backlight
> > > firewire_core crc_itu_t drm_kms_helper drm ehci_hcd sd_mod i2c_core
> > > thermal thermal_sys freq_table
> > >  usbcore usb_common button intel_agp intel_gtt agpgart
> > > Nov 13 09:36:21 maistor kernel: [   40.447384] CPU: 1 PID: 4142 Comm:
> > > Xorg Tainted: P             3.11.6eko2 #3
>
> And there's that taint P again due to the vmware modules.
>
> I know that you tried without the vmware modules where your kernel
> wasn't tainted but then you got a #GP which could be something entirely
> different. But now you're hitting some sanity-checking code which could
> mean there's some corruption happening.

Yes with #GP machine locks and this time it didn't 

>
> So, can you reproduce that exact same warning, i.e. this one:
>
> WARNING: CPU: 1 PID: 4142 at drivers/gpu/drm/i915/intel_display.c:8292
> check_crtc_state+0x5cf/0xa60 [i915]() pipe state doesn't match!
>
> *without* the vmware modules installed?

I'm not sure - you know it happens random

>
> Also, it wouldn't hurt to try the shiny new 3.12.

I was thinking to do so - but lets be honest. I would save everybody's time if 
I were 100% sure it is a hardware issue and I would buy a new notebook. The 
one was serving great for the past 7y and it payed off itself already long 
time ago.
I could try 3.12 and also try in combination with the git drm-intel as Daniel 
suggested.
I'm still thinking that his has something to do with the graphics, but rather 
guessing from intuition.

I'm not sure if it helps somehow but when I grep as following I find only the 
tainted erros - it's not visible which of them were GP, but still it shows 
where it hit the issue

zgrep 'Comm:' messages* | more
messages:Nov 11 10:52:42 maistor kernel: [   43.961984] CPU: 1 PID: 4103 Comm: 
Xorg Tainted: P             3.11.6eko2 #3
messages:Nov 11 10:52:54 maistor kernel: [   55.759687] CPU: 1 PID: 4103 Comm: 
Xorg Tainted: P        W    3.11.6eko2 #3
messages:Nov 12 10:35:42 maistor kernel: [   28.626271] CPU: 0 PID: 3895 Comm: 
Xorg Tainted: P             3.11.6eko2 #3
messages:Nov 12 10:35:55 maistor kernel: [   41.618447] CPU: 1 PID: 3895 Comm: 
Xorg Tainted: P        W    3.11.6eko2 #3
messages:Nov 13 09:36:21 maistor kernel: [   40.447384] CPU: 1 PID: 4142 Comm: 
Xorg Tainted: P             3.11.6eko2 #3
messages:Nov 13 09:36:34 maistor kernel: [   53.624754] CPU: 0 PID: 4142 Comm: 
Xorg Tainted: P        W    3.11.6eko2 #3
messages.1:Nov  4 11:21:19 maistor kernel: [   38.497643] CPU: 1 PID: 4104 
Comm: Xorg Tainted: P             3.11.6eko2 #3
messages.1:Nov  4 11:21:31 maistor kernel: [   50.844193] CPU: 0 PID: 4104 
Comm: Xorg Tainted: P        W    3.11.6eko2 #3
messages.1:Nov  5 10:28:49 maistor kernel: [   39.545474] CPU: 1 PID: 4253 
Comm: Xorg Tainted: P             3.11.6eko2 #3
messages.1:Nov  5 10:29:02 maistor kernel: [   52.078761] CPU: 0 PID: 4253 
Comm: Xorg Tainted: P        W    3.11.6eko2 #3
messages.1:Nov  6 10:33:01 maistor kernel: [   38.876587] CPU: 0 PID: 4128 
Comm: Xorg Tainted: P             3.11.6eko2 #3
messages.1:Nov  6 10:33:12 maistor kernel: [   49.777082] CPU: 0 PID: 4128 
Comm: Xorg Tainted: P        W    3.11.6eko2 #3
messages.1:Nov  7 10:27:40 maistor kernel: [   38.771546] CPU: 0 PID: 4110 
Comm: Xorg Tainted: P             3.11.6eko2 #3
messages.1:Nov  7 10:27:53 maistor kernel: [   51.896606] CPU: 1 PID: 4110 
Comm: Xorg Tainted: P        W    3.11.6eko2 #3
messages.1:Nov  8 10:35:13 maistor kernel: [   42.021333] CPU: 1 PID: 4224 
Comm: Xorg Tainted: P             3.11.6eko2 #3
messages.1:Nov  8 10:35:22 maistor kernel: [   51.699993] CPU: 0 PID: 4224 
Comm: Xorg Tainted: P        W    3.11.6eko2 #3
messages.2.gz:Oct 27 19:01:29 maistor kernel: CPU: 1 PID: 6111 Comm: 
plugin-containe Tainted: P           O 3.11.6eko2 #1
messages.2.gz:Oct 27 22:15:14 maistor kernel: CPU: 1 PID: 9024 Comm: 
plugin-containe Tainted: P           O 3.11.6eko2 #1
messages.2.gz:Oct 28 10:33:34 maistor kernel: CPU: 0 PID: 4195 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.2.gz:Oct 28 10:33:43 maistor kernel: CPU: 0 PID: 4195 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.2.gz:Oct 29 10:34:29 maistor kernel: CPU: 1 PID: 4633 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.2.gz:Oct 29 10:34:41 maistor kernel: CPU: 1 PID: 4633 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.2.gz:Oct 30 10:30:55 maistor kernel: CPU: 1 PID: 4030 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.2.gz:Oct 30 10:31:06 maistor kernel: CPU: 0 PID: 4030 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.2.gz:Oct 31 10:51:01 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg 
Tainted: P           O 3.11.6eko2 #1
messages.2.gz:Oct 31 10:51:08 maistor kernel: CPU: 1 PID: 6441 Comm: Xorg 
Tainted: P        W  O 3.11.6eko2 #1
messages.2.gz:Nov  2 06:32:48 maistor kernel: CPU: 0 PID: 5925 Comm: Socket 
Thread Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 20 02:37:01 maistor kernel: CPU: 0 PID: 5952 Comm: Socket 
Thread Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 20 23:34:00 maistor kernel: CPU: 0 PID: 14534 Comm: 
plugin-containe Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 20 23:34:24 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:34:52 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:35:20 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:35:48 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:36:16 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:36:44 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 20 23:37:12 maistor kernel: CPU: 1 PID: 14535 Comm: 
plugin-containe Tainted: P      D      3.11.6eko2 #1
messages.3.gz:Oct 21 10:42:33 maistor kernel: CPU: 0 PID: 4002 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 21 10:42:45 maistor kernel: CPU: 1 PID: 4002 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.3.gz:Oct 22 11:24:20 maistor kernel: CPU: 1 PID: 4129 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 22 11:24:30 maistor kernel: CPU: 1 PID: 4129 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.3.gz:Oct 23 11:09:10 maistor kernel: CPU: 1 PID: 4197 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 23 11:09:18 maistor kernel: CPU: 1 PID: 4197 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.3.gz:Oct 24 11:00:12 maistor kernel: CPU: 0 PID: 3981 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 24 11:00:23 maistor kernel: CPU: 1 PID: 3981 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.3.gz:Oct 25 12:55:49 maistor kernel: CPU: 0 PID: 4564 Comm: Xorg 
Tainted: P             3.11.6eko2 #1
messages.3.gz:Oct 25 12:56:01 maistor kernel: CPU: 1 PID: 4564 Comm: Xorg 
Tainted: P        W    3.11.6eko2 #1
messages.3.gz:Oct 26 21:57:03 maistor kernel: CPU: 0 PID: 30118 Comm: 
plugin-containe Tainted: P           O 3.11.6eko2 #1
messages.3.gz:Oct 26 21:57:27 maistor kernel: CPU: 1 PID: 30117 Comm: 
plugin-containe Tainted: P      D    O 3.11.6eko2 #1
messages.3.gz:Oct 26 21:57:55 maistor kernel: CPU: 1 PID: 30117 Comm: 
plugin-containe Tainted: P      D    O 3.11.6eko2 #1
messages.3.gz:Oct 26 21:58:23 maistor kernel: CPU: 1 PID: 30117 Comm: 
plugin-containe Tainted: P      D    O 3.11.6eko2 #1
messages.3.gz:Oct 26 21:58:51 maistor kernel: CPU: 1 PID: 30117 Comm: 
plugin-containe Tainted: P      D    O 3.11.6eko2 #1
messages.3.gz:Oct 26 21:59:19 maistor kernel: CPU: 1 PID: 30117 Comm: 
plugin-containe Tainted: P      D    O 3.11.6eko2 #1
messages.4.gz:Oct 14 19:40:28 maistor kernel: CPU: 1 PID: 19163 Comm: konsole 
Tainted: P           O 3.10.9eko2 #4
messages.4.gz:Oct 14 19:42:04 maistor kernel: CPU: 0 PID: 26225 Comm: wfica 
Tainted: P      D    O 3.10.9eko2 #4
messages.4.gz:Oct 14 20:17:55 maistor kernel: CPU: 1 PID: 390 Comm: kswapd0 
Tainted: P      D    O 3.10.9eko2 #4
messages.4.gz:Oct 15 20:16:45 maistor kernel: CPU: 0 PID: 4058 Comm: Xorg 
Tainted: P           O 3.10.9eko2 #4
messages.4.gz:Oct 17 10:40:44 maistor kernel: CPU: 1 PID: 6417 Comm: 
plugin-containe Tainted: P           O 3.10.9eko2 #4
messages.4.gz:Oct 17 12:42:09 maistor kernel: CPU: 1 PID: 390 Comm: kswapd0 
Tainted: P      D    O 3.10.9eko2 #4
messages.4.gz:Oct 17 13:16:14 maistor kernel: CPU: 0 PID: 6108 Comm: kmix 
Tainted: P           O 3.10.9eko2 #4
messages.4.gz:Oct 17 13:17:33 maistor kernel: CPU: 1 PID: 20690 Comm: 
udisks-daemon Tainted: P      D    O 3.10.9eko2 #4
messages.4.gz:Oct 17 13:17:33 maistor kernel: CPU: 1 PID: 20690 Comm: 
udisks-daemon Tainted: P      D W  O 3.10.9eko2 #4
messages.4.gz:Oct 17 13:56:58 maistor kernel: CPU: 1 PID: 13731 Comm: 
plugin-containe Tainted: P           O 3.10.9eko2 #4
messages.4.gz:Oct 17 13:57:04 maistor kernel: CPU: 0 PID: 4494 Comm: Xorg 
Tainted: P        W  O 3.10.9eko2 #4

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi
I listened to your advise and installed 3.12 kernel (no other modules on top 
that would taint the kernel like vmware/player). 
So it turned out I have to enable /proc/acpi (depreciated) and acpi_cpufreq, 
so that I may have a proper support for cooling and frequency.

$ acpi -t
Thermal 0: ok, 50.5 degrees C
$ acpi -c
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: LCD 3 of 7
$ lsmod | grep cpu
cpufreq_ondemand        8085  2
cpufreq_powersave        926  0
cpufreq_performance      930  0
cpufreq_conservative     6305  0
acpi_cpufreq            6955  0
processor              23167  3 acpi_cpufreq

After doing all of this I was able to reproduce the issue by overloading the 
system with following simple steps:
1. start a compilation of something (ex. kernel)
2. run another process hungry application (flashplayer in firefox)
=> system locks in about 3-5mins

I also noticed that the board gets pretty hot, so in my opinion it locks 
because of thermal issue.
I think this also would explain why I see errors at different processes 
(mostly Xorg), but with 3.12 I do not get any trace message in the log files.
Could you advise which option should be enabled in the kernel or how I could 
log/trace if system locks.
How can I make sure that the cooling/temp works properly?

Perhaps after upgrading in september the system is working under heavier load 
and therefore I started having the issue, or something broke in software or 
hardware and it can not cool down properly. I don't think the kernel is the 
issue, because I had the same with older kernels that were working fine 
before.
The fan looks clean and there is no dust or whatever in the cooling area, that 
would prevent colling. The physical position of the notebook (docking 
station) also did not change.
I don't know where to look at or to start, so any advise is appreciated.

thanks in advance and kind regards

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

On Sun, Nov 17, 2013 at 12:35:16PM +0100, MPhil. Emanoil Kotsev wrote:
> After doing all of this I was able to reproduce the issue by
> overloading the system with following simple steps:
> 1. start a compilation of something (ex. kernel)
> 2. run another process hungry application (flashplayer in firefox)
> => system locks in about 3-5mins

Ha, so we're getting somewhere :)

> I also noticed that the board gets pretty hot, so in my opinion it
> locks because of thermal issue.

The symptoms we're seeing so far are very much consistent with a thermal
issue.

> I think this also would explain why I see errors at different
> processes (mostly Xorg), but with 3.12 I do not get any trace message
> in the log files. Could you advise which option should be enabled in
> the kernel or how I could log/trace if system locks.

Try enabling CONFIG_LOCKUP_DETECTOR, that could tell us where we're
hanging.

But, make sure to be on a console and not in X in order to get a chance
to see the message. What I do is reroute all log messages to /dev/tty8,
i.e. have

*.*		|/dev/tty8

in syslog.conf and switch to it with Ctrl-Alt-F8.

> How can I make sure that the cooling/temp works properly?
>
> Perhaps after upgrading in september the system is working under

What kind of upgrade exactly did you do to a laptop?

> heavier load and therefore I started having the issue, or something
> broke in software or hardware and it can not cool down properly. I
> don't think the kernel is the issue, because I had the same with older
> kernels that were working fine before.
>
> The fan looks clean and there is no dust or whatever in the cooling
> area, that would prevent colling. The physical position of the
> notebook (docking station) also did not change.

Does the issue happen if the laptop is not in the docking station?

In any case, you need to follow your steps back of the upgrade to have
at least a clue what causes the overheating.

Can you revert the upgrade and see whether it still happens?

Also, do you have sensors support for your hardware? IOW, can you
monitor the temperature of some hardware elements by running

$ sensors

?

For example, I see this on my box here:

$ sensors
fam15h_power-pci-00c4
Adapter: PCI adapter
power1:       45.64 W  (crit = 125.19 W)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +19.2°C  (high = +70.0°C)
                       (crit = +90.0°C, hyst = +87.0°C)

radeon-pci-0100
Adapter: PCI adapter
temp1:        +80.0°C

so when something overheats, running "watch -n 1 sensors" could give
some hints.

Also, what does

$ grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq

give?

Also, can you connect your laptop to a serial or netconsole to collect
dmesg before and while the lockup happens?

Basically, we're looking for a hint about which part of the hw causes
the overheating...

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi,

On Sunday 17 November 2013 13:07:34 Borislav Petkov wrote:
> On Sun, Nov 17, 2013 at 12:35:16PM +0100, MPhil. Emanoil Kotsev wrote:
> > After doing all of this I was able to reproduce the issue by
> > overloading the system with following simple steps:
> > 1. start a compilation of something (ex. kernel)
> > 2. run another process hungry application (flashplayer in firefox)
> > => system locks in about 3-5mins
>
> Ha, so we're getting somewhere :)

yes looks like :)

>
> > I also noticed that the board gets pretty hot, so in my opinion it
> > locks because of thermal issue.
>
> The symptoms we're seeing so far are very much consistent with a thermal
> issue.

this is also true - which makes me sad as the notebook was working great in 
the past 7y

>
> > I think this also would explain why I see errors at different
> > processes (mostly Xorg), but with 3.12 I do not get any trace message
> > in the log files. Could you advise which option should be enabled in
> > the kernel or how I could log/trace if system locks.
>
> Try enabling CONFIG_LOCKUP_DETECTOR, that could tell us where we're
> hanging.
>
> But, make sure to be on a console and not in X in order to get a chance
> to see the message. What I do is reroute all log messages to /dev/tty8,
> i.e. have
>
> *.*		|/dev/tty8
>
> in syslog.conf and switch to it with Ctrl-Alt-F8.

thanks for the advise. I'll do so

>
> > How can I make sure that the cooling/temp works properly?
> >
> > Perhaps after upgrading in september the system is working under
>
> What kind of upgrade exactly did you do to a laptop?

I was using debian squeeze with trinity desktop (KDE 3.5.10) and upgraded to 
debian wheeze with TDE (3.5.13)

>
> > heavier load and therefore I started having the issue, or something
> > broke in software or hardware and it can not cool down properly. I
> > don't think the kernel is the issue, because I had the same with older
> > kernels that were working fine before.
> >
> > The fan looks clean and there is no dust or whatever in the cooling
> > area, that would prevent colling. The physical position of the
> > notebook (docking station) also did not change.
>
> Does the issue happen if the laptop is not in the docking station?

I wanted to test this, but as I have to replug a lot, didn't do it so far, 
also because it was working with this docking station for the past 2y

>
> In any case, you need to follow your steps back of the upgrade to have
> at least a clue what causes the overheating.
>
> Can you revert the upgrade and see whether it still happens?
This would be hard - no impossible as I have a backup but it will be time 
consuming
>
> Also, do you have sensors support for your hardware? IOW, can you
> monitor the temperature of some hardware elements by running
>
> $ sensors

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +47.5°C  (crit = +126.0°C)


>
> ?
>
> For example, I see this on my box here:
>
> $ sensors
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:       45.64 W  (crit = 125.19 W)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:        +19.2°C  (high = +70.0°C)
>                        (crit = +90.0°C, hyst = +87.0°C)
>
> radeon-pci-0100
> Adapter: PCI adapter
> temp1:        +80.0°C
>
> so when something overheats, running "watch -n 1 sensors" could give
> some hints.
>
> Also, what does
>
> $ grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
>
> give?

grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1:2000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:1:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:1:10000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1:2000000 
1667000 1333000 1000000
/sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:1:0 1
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:1:acpi-cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1:1000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:1:ondemand 
powersave performance conservative userspace
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1:1000000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1:2000000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1:1000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1:2000000
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:1:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1:1000000
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus:1:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1:<unsupported>


>
> Also, can you connect your laptop to a serial or netconsole to collect
> dmesg before and while the lockup happens?

I could try this. I guess this assumes I have to have another machine running 
in paralell, but this can be arranged with a little effort

>
> Basically, we're looking for a hint about which part of the hw causes
> the overheating...
>
> HTH.

Thanks for the hints. As I never had to do with overheating or similar issues, 
your help is very precious to me. Unfortunately we have a little child on 
board and time is limitted :) to a couple of hours daily, where I can work at 
home which means even less time for debugging. But I never give up. I just 
want to be sure that it is not a hardware issue

Thanks again and kind regards. I'll post when I have some useful input

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote:
> this is also true - which makes me sad as the notebook was working
> thgreat in e past 7y

Hmm, maybe it is heading slowly for the eternal hunting fields... :-)

> > What kind of upgrade exactly did you do to a laptop?
> 
> I was using debian squeeze with trinity desktop (KDE 3.5.10) and upgraded to 
> debian wheeze with TDE (3.5.13)

Oh ok, so I thought you were talking about a hw upgrade, like adding
more RAM, hew hdd, etc.

Ok, can you try this: boot without X and try overloading the machine on
the console, i.e. do

while true; do make clean && make -j64; done

or similar in your kernel repository. Does it trigger then?

Although I can't imagine how a software upgrade would cause the
overheating... :-\.

> > Can you revert the upgrade and see whether it still happens?
> This would be hard - no impossible as I have a backup but it will be
> time consuming

You could try booting a distro from a livecd and see any change there...

> $ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:        +47.5°C  (crit = +126.0°C)

That's some ACPI timezone thing. So what happens if you do

$ watch -n 1 sensors

and you incur the load? Do you hit the critical temperature?

> grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:1:ondemand
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:1:10000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1:2000000 1667000 1333000 1000000
> /sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:1:0 1
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:1:acpi-cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:1:ondemand powersave performance conservative userspace
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1:1000000
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:1:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1:<unsupported>

Yeah, I don't see anything wrong with that output.

> I could try this. I guess this assumes I have to have another machine
> running in paralell, but this can be arranged with a little effort

Yep.

> Thanks for the hints. As I never had to do with overheating or
> similar issues, your help is very precious to me. Unfortunately we
> have a little child on board and time is limitted :) to a couple of
> hours daily, where I can work at home which means even less time for
> debugging. But I never give up. I just want to be sure that it is not
> a hardware issue

No worries, take care of the child first - the laptop and everyone else
can wait :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi

On Sunday 17 November 2013 16:06:07 you wrote:
> On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote:
> > this is also true - which makes me sad as the notebook was working
> > thgreat in e past 7y
>
> Hmm, maybe it is heading slowly for the eternal hunting fields... :-)
may be, but I am a bit of academic so until 100% prove - I doubt, which does 
not mean that I can not purchaise a new one :)
>
> > > What kind of upgrade exactly did you do to a laptop?
> >
> > I was using debian squeeze with trinity desktop (KDE 3.5.10) and upgraded
> > to debian wheeze with TDE (3.5.13)
>
> Oh ok, so I thought you were talking about a hw upgrade, like adding
> more RAM, hew hdd, etc.
>
> Ok, can you try this: boot without X and try overloading the machine on
> the console, i.e. do
>
> while true; do make clean && make -j64; done
>
> or similar in your kernel repository. Does it trigger then?
I'll try - I'm also curious what will happen!
>
> Although I can't imagine how a software upgrade would cause the
> overheating... :-\.
How - new libraries - more exhaustive algorythms - higher cpu usage etc. Some 
of the things M$ is doing on purpose to force you upgrade your hardware every 
2-3years

>
> > > Can you revert the upgrade and see whether it still happens?
> >
> > This would be hard - no impossible as I have a backup but it will be
> > time consuming
>
> You could try booting a distro from a livecd and see any change there...
>
> > $ sensors
> > acpitz-virtual-0
> > Adapter: Virtual device
> > temp1:        +47.5°C  (crit = +126.0°C)
>
> That's some ACPI timezone thing. So what happens if you do
>
> $ watch -n 1 sensors
>
> and you incur the load? Do you hit the critical temperature?

I wanted to first compile the kernel with the debug option you mentioned, but 
while compiling it went to about 75°C.

>
> > grep . -EriIn /sys/devices/system/cpu/cpu0/cpufreq
> > /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1:2000000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:1:ondemand
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:1:10000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1:2000
> >000 1667000 1333000 1000000
> > /sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:1:0 1
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:1:acpi-cpufreq
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1:1000000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:1:ondema
> >nd powersave performance conservative userspace
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1:1000000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1:2000000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1:1000000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1:2000000
> > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:1:0
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1:1000000
> > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:1:0
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1:<unsupported>
>
> Yeah, I don't see anything wrong with that output.
yes looks nice
>
> > I could try this. I guess this assumes I have to have another machine
> > running in paralell, but this can be arranged with a little effort
>
> Yep.
>
> > Thanks for the hints. As I never had to do with overheating or
> > similar issues, your help is very precious to me. Unfortunately we
> > have a little child on board and time is limitted :) to a couple of
> > hours daily, where I can work at home which means even less time for
> > debugging. But I never give up. I just want to be sure that it is not
> > a hardware issue
>
> No worries, take care of the child first - the laptop and everyone else
> can wait :-)

yes - we do load balancing with my wife :)

I'll post back with some data (I hope)

regards
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

On Sun, Nov 17, 2013 at 05:45:18PM +0100, MPhil. Emanoil Kotsev wrote:
> How - new libraries - more exhaustive algorythms - higher cpu usage
> etc. Some of the things M$ is doing on purpose to force you upgrade
> your hardware every 2-3years

That would be too easy and machines would be dying left and right of
overheating. Actually, sane hardware is much more robust than that and
it throttles itself in case of critical temperature levels. And, IMHO
your Dell Latitude D520 should be fine, in that respect. But we'll see.
:-)

> I wanted to first compile the kernel with the debug option you
> mentioned, but while compiling it went to about 75°C.

Yeah, that's still ok if we trust the output saying that 126°C is the
critical temp.

It would be interesting to see what this sensor says right before the
machine locks up.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi

On Sunday 17 November 2013 21:05:46 Borislav Petkov wrote:
> On Sun, Nov 17, 2013 at 05:45:18PM +0100, MPhil. Emanoil Kotsev wrote:
> > How - new libraries - more exhaustive algorythms - higher cpu usage
> > etc. Some of the things M$ is doing on purpose to force you upgrade
> > your hardware every 2-3years
>
> That would be too easy and machines would be dying left and right of
> overheating. Actually, sane hardware is much more robust than that and
> it throttles itself in case of critical temperature levels. And, IMHO
> your Dell Latitude D520 should be fine, in that respect. But we'll see.
>

I was thinking the same - but started to despair

> :-)
> :
> > I wanted to first compile the kernel with the debug option you
> > mentioned, but while compiling it went to about 75°C.
>
> Yeah, that's still ok if we trust the output saying that 126°C is the
> critical temp.
>
> It would be interesting to see what this sensor says right before the
> machine locks up.

This test is outstanding for a moment where I have more free time to reproduce 
and log everything

I did something else yesterday evening before going to bed ~00:30
I closed the  notebook cover just so that it would switch off the LCD display
In the morning I opened up and found the notebook with blinking led lights 

http://www.dell.com/support/troubleshooting/us/en/19/KCS/KcsArticles/ArticleView?c=us&l=en&s=dhs&docid=DSN_DBECF64CFEDA449398CB9E859D4944A5

unfortunately I don't find the pattern in the link above
the left one was on and the other two were blinking

Arter shut down (keep power button pressed) and turning it on only the two 
leds (middle and right) were blinking, which according the link above means 

Configuring PCI bridges	Replacing the system board.

After waiting for about 1-2mins notebook starts normally - another link to 
heating issues.

At the moment I have to do pretty much at all levels, so I can not test any 
further.
This is just an update. I'll post again when more results are available.
I'm thinking to open up and inspect from inside - perhaps somewhere the 
cooling system is clogged or something.

regards

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: kernel 3.11.6 general protection fault

[MPhil. Emanoil Kotsev]

Hi again,
sorry for writing  after such long time of silence, but I was busy with one 
project (and family as well)

On Sunday 17 November 2013 21:05:46 you wrote:
> On Sun, Nov 17, 2013 at 05:45:18PM +0100, MPhil. Emanoil Kotsev wrote:
> > How - new libraries - more exhaustive algorythms - higher cpu usage
> > etc. Some of the things M$ is doing on purpose to force you upgrade
> > your hardware every 2-3years
>
> That would be too easy and machines would be dying left and right of
> overheating. Actually, sane hardware is much more robust than that and
> it throttles itself in case of critical temperature levels. And, IMHO
> your Dell Latitude D520 should be fine, in that respect. But we'll see.
>

I was able to solve the issue by removing some of the modules I had in 
xorg.conf.
I noticed that it is not the cpu that is overheating, but rather the 
video/graphic card. The area around the "Dell" logo on the front of the 
display is still pretty hot, but the system seem to be working fine now and I 
can not reproduce the issue any more.
Someone would ask why I'm using the xorg.conf. The reason is because without 
it X automatically loads the GL direver for 3d support and I am not able to 
use second display.
Perhaps it is worth trying latest intel driver as susggested before. However 
with the current one it is working fine, so I would consider the issue as 
solved.

I would like to thank you for your precious support and ideas once again.

regards

Re: kernel 3.11.6 general protection fault

[Borislav Petkov]

On Wed, Dec 18, 2013 at 09:59:22PM +0100, MPhil. Emanoil Kotsev wrote:
> I was able to solve the issue by removing some of the modules I had in
> xorg.conf. I noticed that it is not the cpu that is overheating, but
> rather the video/graphic card. The area around the "Dell" logo on the
> front of the display is still pretty hot, but the system seem to be
> working fine now and I can not reproduce the issue any more.

Interesting. Which module was that?

It was probably making your GPU go nuts. The more interesting question
is whether this module would behave on your machine normally and only
some buggy incarnation of it would cause the overheating... I.e., it
could be you upgraded X and with the new version the issue started
appearing. Fun.

> I would like to thank you for your precious support and ideas once
> again.

Sure, you're welcome!

:-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--