Additional info: reporter: libreport-2.1.10 kernel BUG at drivers/cpufreq/cpufreq.c:79! invalid opcode: 0000 [#1] SMP Modules linked in: fuse bnep nf_conntrack_netbios_ns bluetooth 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 coretemp kvm_intel arc4 iwl3945 iwlegacy mac80211 kvm tg3 snd_hda_codec_si3054 snd_hda_codec_analog snd_hda_intel hp_wmi joydev cfg80211 snd_hda_codec ptp iTCO_wdt iTCO_vendor_support ppdev sdhci_pci sdhci mmc_core lpc_ich sparse_keymap tpm_tis microcode serio_raw snd_hwdep snd_seq rfkill tifm_7xx1 tifm_core pps_core mfd_core snd_seq_device snd_pcm parport_pc tpm_infineon tpm tpm_bios acpi_cpufreq snd_page_alloc snd_timer snd soundcore wmi parport i915 i2c_algo_bit firewire_ohci drm_kms_helper firewire_core drm crc_itu_t i2c_core ata_generic yenta_socket pata_acpi video CPU: 0 PID: 10521 Comm: grep Not tainted 3.12.6-300.fc20.i686+PAE #1 Hardware name: Hewlett-Packard HP Compaq nc6320 (EV073AV)/30AA, BIOS 68YDU Ver. F.0D 04/17/2007 task: e04e0000 ti: d2e02000 task.ti: d2e02000 EIP: 0060:[<c087f9a3>] EFLAGS: 00010246 CPU: 0 EIP is at lock_policy_rwsem_read+0x33/0x40 EAX: 36885000 EBX: ffffffea ECX: 00000001 EDX: 00000000 ESI: f319fd24 EDI: c0c7e220 EBP: d2e03f08 ESP: d2e03f08 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: 08469094 CR3: 1ede2000 CR4: 000007f0 Stack: d2e03f20 c087f9e0 f71a7000 ed1b09c0 f3221000 c0a23b7c d2e03f64 c05c1608 ef6f3e48 00000000 00000000 f6fbfc38 d2e03f64 c0562714 00000002 f319fd24 c0a23b7c 08461000 00008000 ed1b09d4 ef6f3e40 08461000 c05c1580 d2e03f88 Call Trace: [<c087f9e0>] show+0x30/0x70 [<c05c1608>] sysfs_read_file+0x88/0x170 [<c0562714>] ? rw_verify_area+0x54/0x100 [<c05c1580>] ? sysfs_write_file+0x110/0x110 [<c0562840>] vfs_read+0x80/0x150 [<c063bf7c>] ? selinux_file_ioctl+0x4c/0xf0 [<c0562fc9>] SyS_read+0x49/0x90 [<c09b9a8d>] sysenter_do_call+0x12/0x28 Code: ba 24 d4 d5 c0 8b 04 85 20 03 ca c0 8b 14 02 85 d2 74 18 8b 52 0c b8 00 d4 d5 c0 03 04 95 20 03 ca c0 e8 81 09 13 00 31 c0 5d c3 <0f> 0b 8d 74 26 00 8d bc 27 00 00 00 00 55 89 e5 57 56 53 83 ec EIP: [<c087f9a3>] lock_policy_rwsem_read+0x33/0x40 SS:ESP 0068:d2e03f08
Created attachment 845763 [details] File: dmesg
Interesting. This was supposed to be fixed: http://lkml.indiana.edu/hypermail/linux/kernel/1309.2/02320.html via commit 26ca8694344af4c833d22590c5b77d6b9cff0722 Author: Viresh Kumar <viresh.kumar> Date: Fri Sep 20 22:37:31 2013 +0530 cpufreq: check cpufreq driver is valid and cpufreq isn't disabled in cpufreq_get() cpufreq_get() can be called from external drivers which might not be aware if cpufreq driver is registered or not. And so we should actually check if cpufreq driver is registered or not and also if cpufreq is active or disabled, at the beginning of cpufreq_get(). Otherwise call to lock_policy_rwsem_read() might hit BUG_ON(!policy). Reported-and-tested-by: Linus Walleij <linus.walleij> Signed-off-by: Viresh Kumar <viresh.kumar> Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat.ibm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki> Which hit 3.12
That bug was triggered by reading or writing some sysfs file, do you know what file was that ? Does it happen any-time you read/write this file ?
(In reply to Stanislaw Gruszka from comment #3) > That bug was triggered by reading or writing some sysfs file, do you know > what file was that ? Does it happen any-time you read/write this file ? No, unfortunately not. This pops up after bringing my laptop out of hibernation, if that helps. As for what file, I have no idea which file it was trying to read at the time. Maybe it was as it was trying to hibernate that it tried to do something?
*********** 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.
I can see a few fixes on 3.13 that could help with this bug. Could you test that kernel to see if problem happen again, i.e. run script like below for few hours: while true ; do echo "0" > /sys/class/rtc/rtc0/wakealarm echo "+300" > /sys/class/rtc/rtc0/wakealarm pm-hibernate done
Unfortunately, I can't test this any longer, as I've migrated the affected laptop away from Fedora. I'll mark this bug as closed and if it reoccurs for someone else on a more recent kernel version, they can open a new bug.