Created attachment 800284 [details]
screenshot of place where it is going on in message log
Created attachment 800285 [details]
screenshot of place where it is going on in message log
[mikhail@localhost ~]$ lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41) 05:00.0 Audio device: Creative Labs Device 0012 (rev 01) [mikhail@localhost ~]$ lsusb Bus 002 Device 002: ID 2109:0811 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 009: ID 05e3:0723 Genesys Logic, Inc. GL827L SD/MMC/MS Flash Card Reader Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 003: ID 2109:0811 Bus 001 Device 004: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO) Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Created attachment 800294 [details]
screenshot of place where it is going on in message log
Try installing kernel-debug and seeing if you get additional debug output from that. what kernel is in use ? $ uname -a Linux localhost.localdomain 3.11.1-200.fc19.x86_64.debug #1 SMP Sat Sep 14 14:51:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Created attachment 800864 [details]
screenshot of place where it is going on in message log (debug kernel)
Created attachment 800865 [details]
full message log
> Try installing kernel-debug and seeing if you get additional debug output from that.
I am installing kernel-debug but still not see any usefull in message log. Can you see too?
Same problem here. No log messages and the console is blank. The problem started after upgrading to 3.11.1-200.fc19. Unfortunately, memtest86+ doesn't work on 4th generation core, so I can't test the memory, but I am doubtful that this would be a problem since it never happened with earlier kernels. I am running 3.10.11 right now to see if it will reappear. Motherboard is Intel's DH87RL and a CPU is i5-4570 (no overclocking, just a default mode). CPU temperatures are in the 30s, barely any load on the machine. I'll attach dmidecode, cpuinfo and lspci outputs. Created attachment 801168 [details]
dmidecode output
Created attachment 801169 [details]
cpuinfo output
Created attachment 801170 [details]
lspci -vv output
Created attachment 801220 [details]
screenshot of place where it is going on in message log
Created attachment 801221 [details]
messages
Tomislav, how long you have i5-4570 (Haswell)? I have found this problem after upgrade to i7-4770. It is noticed that this happens more often in the idle mode, as if the cause is some new energy-saving features of the processor. And even when the computer hangs, reset button is not activated immediately and after 5 seconds after pressing. In this case, a computer shuts down and restarts. Created attachment 801236 [details]
screenshot of place where it is going on in message log
Created attachment 801237 [details]
screenshot of place where it is going on in message log
interesting observation. I noticed that the freeze happened a few times while trying to unlock the computer. Ie the music was playing, when I tried to unlock the computer, the computer freezes and the music gone in cycles. (In reply to Mikhail from comment #17) > Tomislav, how long you have i5-4570 (Haswell)? I have found this problem I have it for about 2 weeks now. I didn't have any problem with prior kernels, but since I upgraded to 3.11.1-200.fc19, it would hung within an hour of becoming idle. I am running 3.10.11-200.fc19 since early this morning, no problems while plenty of idle time. It does seem like some issue with energy savings features that you mention. Hopefully as Haswell propagates we'll see this fixed soon. I can confirm than since 3.11 this issue occurs more often (almost every computer unlock), but with 3.10 with issue occurs too (more rarely). I don't see this problem in Fedora 20 alpha. Who can explain why? Opps problem returns with 3.11.6-300.fc20.x86_64+debug kernel :( *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested. |
Created attachment 800283 [details] screenshot of place where it is going on in message log Description of problem: Every time when I leave the computer on for a long time. When I come back, I found computer in a hung state. The keyboard usually does not respond (pressing CapsLock does not change the status of the corresponding light bulb), and does not ping from network. On screen there is no trace Kernel panic and in log messages, too, there is no mention of this. Help me please for find out what's going on.