Please update kernel to 3.6. Can you reproduce the problem on updated kernel ?

*** Bug 882391 has been marked as a duplicate of this bug. ***

Unfortunately this also happen on 3.6.7 (bug 882391).

Please attach full dmesg (which will include this warning). You can find it in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/

Is this bug reproducible or happen at random ? Do you have step to reproduce ?

*** Bug 876443 has been marked as a duplicate of this bug. ***

Problem happened during the standard boot procedure, no specific steps were made.

Package: kernel
OS Release: Fedora release 17 (Beefy Miracle)

I need a dmesg , see comment 3

Stanislav, sorry, I have occasionally deleted it. As soon this error will happen again I will post.

*** Bug 893730 has been marked as a duplicate of this bug. ***

https://bugzilla.redhat.com/show_bug.cgi?id=893730

Stanislav, this is leftover in the ABRT from the same crash I had on F18. I dunno why but there is no dmesg in the directories you pointed.

Perhaps ABRT has to be updated. Anyway when this will happen again just do "dmesg > dmesg.txt" and attach dmesg.txt here.

Created attachment 676473 [details]
dmesg from Andrey

ABRT is for sure the lastest available in the official repo.

OK, good news: I got the same crash, I got dmesg. More than that I know exactly when it happens: each time I am openining my laptop after hibernation. In addition to this error I also get message about tainted kernelqith GW flags which is strange, because I use a stock one, and even for the lapop's embedded Nvidia I use nouveau.

Taint's flag come from WARNING, once kernel generate a warning it is considered tainted.

We have those in dmesg, before iwl3945 problem:

[ 2513.855112] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1)
[ 2513.855769] CPU1: Core temperature/speed normal
[ 2604.265073] CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
[ 2604.265725] CPU0: Core temperature/speed normal
[ 2699.997045] mce: [Hardware Error]: Machine check events logged

I'm not sure if those messages are related, but perhaps they are, if we overheat machine devices can not communicate properly via PCIe bus with CPU. 

Overheat happen after about 40 minutes in your dmesg. So let's check if hibernate works early, if you boot machine and then try to hibernate few times, does the problem happen?

*** Bug 889467 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I just had a message come up that there was a prolem inthe kernal

Package: kernel
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)

Upgraded to the lastest.
Installed skype. Logged in correctly.
Using Opera.
On battery.

Went for a coffee, machine turned to sleep.

Back from sleep, kernel error, wifi not working.

Restarted, kernel error (reporting), everything seems to be working.


Package: kernel
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)

Just happened to notice the ABRT icon was visible.  Wireless network is currently functioning.  Possibly occurred when somehow (not intentionally) the system suspended and then I attempted to unsuspend.  Because video never recovered from suspend, I ssh'd in and did "sudo reboot".

Package: kernel
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)

comment 12 problem was caused by hardware (overheat). On further reports in comments 16 to 18 root of the issue is unknown.


Paul, Fernando, Stephen, could you please attach dmesg, which include this WARNING ?

I switched from KDE to AwesomeWM (to extend battery life) and the problem never happen again.

Note, there is no support to sleep or hibernate from AwesomeWM.
Then i have to login as root, and use the command pm-suspend, or pm-hibernate.

So, the problem may be around KDE.
I will test it later and report back.
Also i will test it with my other laptop.

I can confirm this happens as of Fedora 18, under Gnome 3 (not KDE specific). Wireless stops working _every time_ I resume from suspend/hibernate.

Created attachment 750805 [details]
dmesg

Created attachment 750806 [details]
backtrace

I remember similar issues on older kernels like 3.3 or so, which was caused by PCI layer bugs:
https://lkml.org/lkml/2011/12/27/65
https://lkml.org/lkml/2012/3/11/112

Bug on comment 22 is on kernel 3.6 , but perhaps issue is now fixed on 3.8 or 3.9. Markus, could you update kernel and check if problem is still there?

The same bug (or I'm assuming the same bug - the behaviour is identical) occurred on a different distro (Arch) on a 3.9 kernel - however, I haven't had the chance to update this installation yet - I'll definitely post back once I've updated though (internet is throttled ATM so that'll take a bit).

Created attachment 751449 [details]
dmesg (F18/Kernel 3.9.2)

Upgraded the whole system, bug is still present with 3.9.2.

Created attachment 751453 [details]
backtrace (F18/Kernel 3.9.2)

This bug behaves differently on the debug kernel - wireless stops working after resume, but I do _not_ get a crash, and the bug can be worked around by simply unloading and reloading the iwl3945 module. This workaround does _not_ work (for me) on non-debug kernels (tried both PAE and non-PAE).

Created attachment 751614 [details]
dmesg (F18/Kernel 3.9.2 debug)

A small addendum: crashes are far less common with the debug kernel, but given enough sleep-resume cycles even it can crash (and if that happens, the unload-reload workaround does not work, I tried it a couple of times). The dmesg output looks quite unspectacular to me, but I'm attaching it nonetheless (the kernels does become tainted at one point though). 

I also only just realised that the backtrace is included in dmesg :/

Description of problem:
The problem happened while I was downloading through torrent. I was getting the new version of Fedora (19) and suddenly the wifi shutoff.
The thing is this can not be reproduced because other times I'm just surfing and the wifi will get cut off or other times I'm watching a video (not on the internet) while I'm doing nothing in the background (no downloading or anything else that uses the internet connection actively) and then the connection will get cut off.

Always happens with the wifi and it is not the router as I have another computer (server running on Debian) and it doesn't have that problem at all.

Version-Release number of selected component:
kernel

Additional info:
reporter:       libreport-2.1.4
cmdline:        BOOT_IMAGE=/boot/vmlinuz-3.9.6-200.fc18.i686.PAE root=UUID=187c8b3f-95d6-455b-84a7-1f6b9110ddf4 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=fr LANG=en_US.UTF-8 rhgb quiet
kernel:         3.9.6-200.fc18.i686.PAE
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
WARNING: at drivers/net/wireless/iwlegacy/common.c:117 _il_grab_nic_access+0x96/0xa0 [iwlegacy]()
Hardware name: 0769EDG
Timeout waiting for ucode processor access (CSR_GP_CNTRL 0xffffffff)
Modules linked in: fuse ebtable_nat ebtables rfcomm bnep be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi ip6t_REJECT scsi_transport_iscsi nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ip6_tables acpi_cpufreq mperf coretemp iTCO_wdt iTCO_vendor_support microcode arc4 iwl3945 iwlegacy i2c_i801 mac80211 r592 btusb memstick bluetooth snd_hda_codec_realtek snd_hda_intel uvcvideo snd_hda_codec lpc_ich mfd_core snd_hwdep videobuf2_vmalloc snd_seq videobuf2_memops snd_seq_device tg3 videobuf2_core videodev ptp media pps_core cfg80211 snd_pcm snd_page_alloc rfkill snd_timer snd soundcore nfsd binfmt_misc uinput auth_rpcgss nfs_acl lockd sunrpc sdhci_pci firewire_ohci i915 sdhci mmc_core i2c_algo_bit drm_kms_helper firewire_core crc_itu_t drm i2c_core wmi video
Pid: 7991, comm: kworker/1:1 Not tainted 3.9.6-200.fc18.i686.PAE #1
Call Trace:
 [<c044e6a9>] warn_slowpath_common+0x69/0x90
 [<f87fb8b6>] ? _il_grab_nic_access+0x96/0xa0 [iwlegacy]
 [<f87fb8b6>] ? _il_grab_nic_access+0x96/0xa0 [iwlegacy]
 [<c044e773>] warn_slowpath_fmt+0x33/0x40
 [<f87fb8b6>] _il_grab_nic_access+0x96/0xa0 [iwlegacy]
 [<f87fb952>] il_wr_prph+0x32/0x90 [iwlegacy]
 [<f87fc5c1>] il_apm_init+0x1b1/0x320 [iwlegacy]
 [<f89a628f>] ? ieee80211_led_tx+0x3f/0x50 [mac80211]
 [<f8788b85>] il3945_apm_init+0x15/0x130 [iwl3945]
 [<f87898d0>] il3945_hw_nic_init+0x30/0x9d0 [iwl3945]
 [<c047e81e>] ? try_to_wake_up+0x18e/0x230
 [<f8984308>] ? ieee80211_tx+0xb8/0xf0 [mac80211]
 [<f8781562>] __il3945_up+0xb2/0x2f0 [iwl3945]
 [<c046715e>] ? wake_up_worker+0x1e/0x30
 [<f87852e7>] il3945_mac_start+0x527/0xe70 [iwl3945]
 [<f896cf5f>] ? ieee80211_start_next_roc+0x17f/0x1b0 [mac80211]
 [<f8987025>] ? ieee80211_queue_work+0x35/0x40 [mac80211]
 [<c09a7108>] ? mutex_lock+0x18/0x40
 [<f896b13a>] ? __ieee80211_scan_completed+0xca/0x290 [mac80211]
 [<f8988c82>] ieee80211_reconfig+0x282/0x1510 [mac80211]
 [<f896c461>] ? ieee80211_scan_cancel+0xe1/0x160 [mac80211]
 [<c09a7108>] ? mutex_lock+0x18/0x40
 [<f8964786>] ieee80211_restart_work+0x86/0xa0 [mac80211]
 [<c0877f08>] ? od_dbs_timer+0x98/0x120
 [<c0467fc6>] process_one_work+0x116/0x330
 [<c04693d9>] worker_thread+0xf9/0x320
 [<c04692e0>] ? manage_workers+0x270/0x270
 [<c046e524>] kthread+0x94/0xa0
 [<c09b0c77>] ret_from_kernel_thread+0x1b/0x28
 [<c046e490>] ? kthread_create_on_node+0xc0/0xc0

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.

*********** 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.

I do not see chance to fix this problem on that old hardware, but fortunately issue is rare.