Created attachment 840129 [details]
File: dmesg

Created attachment 840348 [details]
/var/log/messages showing hang in kernel

I get this almost every time in kernel-12.5-200.fc19.x86_64. Reverting to kernel-3.11.10-200.fc19.x86_64 makes the problem go away.

This attachement shows:
1) Running normally under 3-11.10-200 until Dec 21 23:39:22.
2) Attempting to boot in 12,5-200 at Dec 22 08:22:43.

Starting to get ACPI type mismatch warnings starting at
"Dec 22 08:22:43 mariehe kernel: [    5.773794] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130725/nsarguments-95)"

I also note:
"Dec 22 08:22:43 mariehe kernel: [    5.820328] [drm] Wrong MCH_SSKPD value: 0x16040307
Dec 22 08:22:43 mariehe kernel: [    5.820403] [drm] This can cause pipe underruns and display issues.
Dec 22 08:22:43 mariehe kernel: [    5.820481] [drm] Please upgrade your BIOS to fix this.
"

More ACPI warnings, perhaps related to the ones mentioned above:
"Dec 22 08:22:43 mariehe kernel: [   16.018149] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130725/utaddress-251)
Dec 22 08:22:43 mariehe kernel: [   16.019207] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
"

And finally:
"Dec 22 08:25:00 mariehe kernel: [  104.302007] ------------[ cut here ]------------
Dec 22 08:25:00 mariehe kernel: [  104.302007] WARNING: CPU: 1 PID: 614 at kernel/watchdog.c:272 watchdog_overflow_callback+0x9c/0xd0()
Dec 22 08:25:00 mariehe kernel: [  104.302007] Watchdog detected hard LOCKUP on cpu 1
"

Removed kernel-3.12.5-200.fc19.x86_64.

Installed 3.12.5-200.fc19.x86_64.debug #1 SMP. First boot worked OK. Will post dmesg output and /var/log/messages. Will try for a few days.

In dmesg output, I note:
"[    0.276121] SMP alternatives: lockdep: fixing up alternatives
[    0.276139] smpboot: Booting Node   0, Processors  #   1
[    0.289285] TSC synchronization [CPU#0 -> CPU#1]:
[    0.289288] Measured 4400626 cycles TSC warp between CPUs, turning off TSC clock.
[    0.002000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
[    0.278484] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[    0.279055] SMP alternatives: lockdep: fixing up alternatives
[    0.279059]  #   2
[    0.290973] SMP alternatives: lockdep: fixing up alternatives
[    0.290978]  #   3
[    0.302853] SMP alternatives: lockdep: fixing up alternatives
[    0.302857]  #   4
[    0.314566] SMP alternatives: lockdep: fixing up alternatives
[    0.314572]  #   5
[    0.326334] SMP alternatives: lockdep: fixing up alternatives
[    0.326339]  #   6
[    0.338217] SMP alternatives: lockdep: fixing up alternatives
[    0.338222]  #   7 OK
[    0.349543] Brought up 8 CPUs
[    0.349547] smpboot: Total of 8 processors activated (35120.76 BogoMIPS)
"

Better than the lockups I was getting. I'll look into upgrading the microcode, as suggested.

After plugging in a USB removable disk, I was unexpectedly asked to validate mounting a disused partitionn on the permanent hard disk!

Created attachment 840512 [details]
dmesg output for kernel-3.12.5-200.fc19.x86_64.debug #1 SMP

Created attachment 840513 [details]
/var/logmessages for kernel-3.12.5-200.fc19.x86_64.debug #1 SMP

Description of problem:
freeze kernel kernel-3.12.5-302.fc20.x86_64

Version-Release number of selected component:
kernel

Additional info:
reporter:       libreport-2.1.10
cmdline:        BOOT_IMAGE=/vmlinuz-3.12.5-302.fc20.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 4 PID: 751 at kernel/watchdog.c:272 watchdog_overflow_callback+0x9c/0xd0()
Watchdog detected hard LOCKUP on cpu 4
Modules linked in: fuse xt_CHECKSUM nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep snd_hda_codec_realtek snd_hda_intel e1000e arc4 snd_hda_codec iwldvm mac80211 btusb uvcvideo videobuf2_vmalloc tpm_tis serio_raw iwlwifi iTCO_wdt videobuf2_memops iTCO_vendor_support cfg80211 videobuf2_core videodev sdhci_pci sdhci media x86_pkg_temp_thermal coretemp snd_hwdep ptp thinkpad_acpi pps_core joydev mmc_core bluetooth mei_me mei snd_seq snd_seq_device shpchp snd_pcm snd_page_alloc snd_timer snd kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel lpc_ich rfkill i2c_i801 mfd_core soundcore microcode tpm tpm_bios nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper firewire_ohci drm firewire_core crc_itu_t i2c_core wmi video
CPU: 4 PID: 751 Comm: Xorg Not tainted 3.12.5-302.fc20.x86_64 #1
Hardware name: LENOVO 2429CTO/2429CTO, BIOS G4ET90WW (2.50 ) 12/20/2012
 0000000000000009 ffff88033e306c28 ffffffff81662d11 ffff88033e306c70
 ffff88033e306c60 ffffffff810691dd ffff88032d210000 0000000000000000
 ffff88033e306d90 0000000000000000 ffff88033e306ef8 ffff88033e306cc0
Call Trace:
 <NMI>  [<ffffffff81662d11>] dump_stack+0x45/0x56
 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106924c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff811001b0>] ? restart_watchdog_hrtimer+0x50/0x50
 [<ffffffff8110024c>] watchdog_overflow_callback+0x9c/0xd0
 [<ffffffff81138b7e>] __perf_event_overflow+0x8e/0x220
 [<ffffffff811396e4>] perf_event_overflow+0x14/0x20
 [<ffffffff8102ddad>] intel_pmu_handle_irq+0x1bd/0x3c0
 [<ffffffff8166b3fb>] perf_event_nmi_handler+0x2b/0x50
 [<ffffffff8166ac48>] nmi_handle.isra.3+0x88/0x180
 [<ffffffff8166aea9>] do_nmi+0x169/0x310
 [<ffffffff8166a241>] end_repeat_nmi+0x1e/0x2e
 [<ffffffff813172c2>] ? ioread32+0x42/0x50
 [<ffffffff813172c2>] ? ioread32+0x42/0x50
 [<ffffffff813172c2>] ? ioread32+0x42/0x50
 <<EOE>>  [<ffffffffa01cdfb4>] ? nouveau_timer_wait_eq+0x64/0xd0 [nouveau]
 [<ffffffffa01b0192>] nv84_bar_flush+0x52/0x90 [nouveau]
 [<ffffffffa01e29ea>] nvc0_fifo_playlist_update+0xea/0x170 [nouveau]
 [<ffffffffa01e2adb>] nvc0_fifo_chan_init+0x6b/0x80 [nouveau]
 [<ffffffffa01aee7d>] nouveau_object_inc+0xbd/0x1b0 [nouveau]
 [<ffffffffa01ad74b>] nouveau_handle_init+0x7b/0x230 [nouveau]
 [<ffffffffa01ad7e1>] nouveau_handle_init+0x111/0x230 [nouveau]
 [<ffffffffa01ad7e1>] nouveau_handle_init+0x111/0x230 [nouveau]
 [<ffffffffa01ac162>] nouveau_client_init+0x32/0x60 [nouveau]
 [<ffffffffa0206b38>] nouveau_do_resume+0x48/0x190 [nouveau]
 [<ffffffffa0208150>] nouveau_pmops_runtime_resume+0x90/0x110 [nouveau]
 [<ffffffff8133ab8b>] pci_pm_runtime_resume+0x7b/0xc0
 [<ffffffff8140ae11>] __rpm_callback+0x31/0x80
 [<ffffffff8140ae84>] rpm_callback+0x24/0x80
 [<ffffffff8140be36>] rpm_resume+0x476/0x670
 [<ffffffff8140c07f>] __pm_runtime_resume+0x4f/0x80
 [<ffffffffa0206e1c>] nouveau_drm_ioctl+0x3c/0x90 [nouveau]
 [<ffffffff811c0bbd>] do_vfs_ioctl+0x2dd/0x4b0
 [<ffffffff811c0e11>] SyS_ioctl+0x81/0xa0
 [<ffffffff8166d78e>] ? do_page_fault+0xe/0x10
 [<ffffffff81671d69>] system_call_fastpath+0x16/0x1b

Created attachment 841285 [details]
/var/log/messages

Got a shutdown with blue Fedora showing. I had to power down by holding the power key.
Lines 200ff of the attachment shows the kernel debug version seems to step around the problem reported in this bug.

same freeze on ThinkPad T430 (this bug appears me with a fresh Fedora 20 x86_64 installation).

I temporarily resolv it disabling discrete graphics (NVIDIA) and Optimus on BIOS and setting ON only integrate Intel graphic card

Discovered a dozed kerneloops ABRT's. When I tried to report them, I got a message indicating the the abort data was incomplete. I deleted the reports.

Created attachment 841969 [details]
dmesg output for kernel -3.12.6-200.fc19.x86_64

Original bug seems to be resolved:
"dmesg_20131226.txt:246:[    0.050098] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
messages_20131226.txt:211:Dec 26 10:15:29 mariehe kernel: [    0.280475] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
messages_20131226.txt:1680:Dec 26 10:35:49 mariehe kernel: [    0.046095] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
messages_20131226.txt:2946:Dec 26 10:39:39 mariehe kernel: [    0.050098] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
"

However I note other problems:
1) When I first booted the new kernel, I thought I had a hang with the blue fedora logo showing, and CTRL-ALT-Fn and CTRL-ALT-DEL had no effect. Rebooted, removed rhgb and quiet from command line, and started OK! The reboot is shown in the /var/log/messages file, around line 2751.

2) These messages appear in /var/log/messages before I rebooted:
"2738 Dec 26 10:36:10 mariehe systemd[1]: Started Network Manager Script Dispatcher Service.
2739 Dec 26 10:36:10 mariehe kernel: [   47.441300] ACPI Error: Method parse/execution failed [\_SB     _.PCI0.PEG0.PEGP.SGON] (Node ffff88023408de88), AE_AML_INFINITE_LOOP (20130725/psparse-536)
2740 Dec 26 10:36:10 mariehe kernel: [   47.441310] ACPI Error: Method parse/execution failed [\_SB     _.PCI0.PEG0.PEGP._ON_] (Node ffff8802340a7b40), AE_AML_INFINITE_LOOP (20130725/psparse-536)
2741 Dec 26 10:36:10 mariehe kernel: [   47.441314] ACPI Error: Method parse/execution failed [\_SB     _.PCI0.PEG0.PEGP._PS0] (Node ffff8802340a78c0), AE_AML_INFINITE_LOOP (20130725/psparse-536)
2742 Dec 26 10:36:10 mariehe kernel: [   47.441322] video LNXVIDEO:00: Failed to change power state      to D0
2743 Dec 26 10:36:10 mariehe systemd[1]: Stopping Sendmail Mail Transport Client...
2744 Dec 26 10:36:10 mariehe systemd[1]: Stopping Sendmail Mail Transport Agent...
2745 Dec 26 10:36:10 mariehe systemd[1]: Starting Sendmail Mail Transport Agent...
2746 Dec 26 10:36:10 mariehe kernel: [   47.452066] nouveau 0000:01:00.0: Refused to change power s     tate, currently in D3
2747 Dec 26 10:36:10 mariehe systemd[1]: Started Sendmail Mail Transport Agent.
2748 Dec 26 10:36:10 mariehe systemd[1]: Starting Sendmail Mail Transport Client...
2749 Dec 26 10:36:10 mariehe systemd[1]: Started Sendmail Mail Transport Client.
2750 Dec 26 10:36:15 mariehe chronyd[505]: Selected source 208.80.96.70
2751 <deleted 1900 null characters here>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^     @^@^@Dec 26 10:39:39 mariehe rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="50     5" x-info="http://www.rsyslog.com"] start
2752 Dec 26 10:39:39 mariehe kernel: [    0.000000] Initializing cgroup subsys cpuset
2753 Dec 26 10:39:39 mariehe kernel: [    0.000000] Initializing cgroup subsys cpu
"

Created attachment 841976 [details]
/var/log/messages for kernel-3.12.6-200.fc19.x86_64

Searching for "abrt" in this file shows problems with reporting kerlel oopses, which I did not see when I opened ABRT:
" 791 Dec 26 10:15:46 mariehe abrtd[461]: Can't open file '/var/tmp/abrt/ccpp-2013-08-09-18:13:29-46     4/type': Aucun fichier ou dossier de ce type
 792 Dec 26 10:15:46 mariehe abrtd[461]: Missing or empty file: type
 793 Dec 26 10:15:46 mariehe abrtd[461]: Unlocked '/var/tmp/abrt/ccpp-2013-08-09-18:13:29-464/.lock     ' (no or corrupted 'type' file)
"

My system freezes after installing the kernel kernel-3.12.6-200.fc19.x86_64 and works fine in kernel-3.11.10-200.fc19.x86_64.
I can able to reproduce by pressing Fn key along with Home for increasing brightness. It just freezes no keys in keyboard no external mouse not thinkpad mouse works.

it seems that in 3.13.0-0.rc8.git2.1.fc21.x86_64 the bug has disappeared (i continue to check if bug reappears)

I have the freeze issue with my T430 too. Besides, I find that if I disable NVIDIA graphics in BIOS and use only integrated graphics, I cannot make connecting to external VGA projector work. The projector seems not be able to detect the laptop. Shall I open a new bug report on that?

Regarding comment #14:
 * You probably have an "optimus" hardware setup like I have on Lenovo W520:
   - On board Intel chipset only drives the laptop screen.
   - An NVIDIA chipset can replace the Intel chipset for high-end graphics
     and lower-battery life.
   - The external VGA connectro is only driven by the NVIDIA chipset.

 * The results for me:
   - Unstable kernel if NVIDIA is enabled in BIOS :-(
   - No VGA projector functionality :-(
   - Thank you NVIDIA...

   BTW: I took this laptop after verifying it had Intel GFX. Only
        later I learned about that tricky NVIDIA infiltration...

In 3.13.6-200.fc20.x86_64 the bug is not present (I have a T430 with NVIDIA optimus enabled)

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.