Bug 964367 - [abrt] kernel BUG at net/rfkill/core.c:244!
Summary: [abrt] kernel BUG at net/rfkill/core.c:244!
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ecf58f558a4a794de3d0b7dbf27...
: 963708 965870 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-18 04:59 UTC by Simon Lewis
Modified: 2013-05-27 10:27 UTC (History)
11 users (show)

Fixed In Version: kernel-3.9.4-300.fc19
Clone Of:
Environment:
Last Closed: 2013-05-26 02:57:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (73.56 KB, text/plain)
2013-05-18 04:59 UTC, Simon Lewis
no flags Details

Description Simon Lewis 2013-05-18 04:59:42 UTC
Description of problem:
SELinux shows message imediately after desktop is started...

Additional info:
reporter:       libreport-2.1.4
kernel BUG at net/rfkill/core.c:244!
invalid opcode: 0000 [#1] SMP 
Modules linked in: b43 bcma mac80211 cfg80211 iTCO_wdt iTCO_vendor_support hp_wmi(+) sparse_keymap rfkill btrfs zlib_deflate raid6_pq libcrc32c xor mperf coretemp microcode joydev serio_raw snd_hda_codec_analog snd_hda_intel snd_hda_codec lpc_ich snd_hwdep mfd_core ssb snd_seq snd_seq_device mmc_core snd_pcm wmi snd_page_alloc snd_timer e1000e snd ptp soundcore pps_core i915 usb_storage i2c_algo_bit drm_kms_helper drm i2c_core video uinput
CPU 0 
Pid: 200, comm: systemd-udevd Not tainted 3.9.0-0.rc6.git2.3.fc19.x86_64 #1 Hewlett-Packard         /3618
RIP: 0010:[<ffffffffa03d653f>]  [<ffffffffa03d653f>] rfkill_set_hw_state+0x9f/0xb0 [rfkill]
RSP: 0018:ffff8800b822db50  EFLAGS: 00010246
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000018
RDX: 0000000000000006 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff8800b822db70 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff8800a03792a0
R13: ffff8800a0379290 R14: 0000000000000000 R15: ffffffffa03bd200
FS:  00007f12826d6880(0000) GS:ffff8800bf000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f32c4150000 CR3: 00000000b882e000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process systemd-udevd (pid: 200, threadinfo ffff8800b822c000, task ffff8800b3c30000)
Stack:
 0000000000000000 ffff8800a03792a0 ffff8800a0379290 0000000000000000
 ffff8800b822dba0 ffffffffa007b25a 0606163900000af0 ffff8800a03792a0
 ffffffffa03bd028 ffff8800a0379290 ffff8800b822dbd0 ffffffff814755cc
Call Trace:
 [<ffffffffa007b25a>] hp_wmi_bios_setup+0x25a/0x3a0 [hp_wmi]
 [<ffffffff814755cc>] platform_drv_probe+0x3c/0x70
 [<ffffffff81472c1a>] ? driver_sysfs_add+0x7a/0xb0
 [<ffffffff814732e7>] driver_probe_device+0x87/0x390
 [<ffffffff814736c3>] __driver_attach+0x93/0xa0
 [<ffffffff81473630>] ? __device_attach+0x40/0x40
 [<ffffffff81471243>] bus_for_each_dev+0x63/0xa0
 [<ffffffff81472d3e>] driver_attach+0x1e/0x20
 [<ffffffff814728c0>] bus_add_driver+0x1f0/0x2b0
 [<ffffffff81473d41>] driver_register+0x71/0x150
 [<ffffffff814753c6>] platform_driver_register+0x46/0x50
 [<ffffffff8147548b>] platform_driver_probe+0x1b/0xb0
 [<ffffffffa007b569>] hp_wmi_init+0x1c9/0xc60 [hp_wmi]
 [<ffffffffa007b3a0>] ? hp_wmi_bios_setup+0x3a0/0x3a0 [hp_wmi]
 [<ffffffff8100210a>] do_one_initcall+0x10a/0x160
 [<ffffffff810e984d>] load_module+0x1ead/0x2870
 [<ffffffff8137f7f0>] ? ddebug_proc_write+0xf0/0xf0
 [<ffffffff810ea2d1>] sys_init_module+0xc1/0x110
 [<ffffffff81725699>] system_call_fastpath+0x16/0x1b
Code: 48 ff ff ff 80 7b 64 00 74 d2 41 83 e5 01 45 38 ec 74 c9 48 8d bb 60 06 00 00 e8 2d 7d cb e0 5b 41 5c 41 5d 44 89 f0 41 5e 5d c3 <0f> 0b 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 
RIP  [<ffffffffa03d653f>] rfkill_set_hw_state+0x9f/0xb0 [rfkill]
 RSP <ffff8800b822db50>

Potential duplicate: bug 963708

Comment 1 Simon Lewis 2013-05-18 04:59:48 UTC
Created attachment 749562 [details]
File: dmesg

Comment 2 Josh Boyer 2013-05-20 13:09:47 UTC
Er... clearly not awake yet.

Comment 3 Josh Boyer 2013-05-22 18:15:10 UTC
*** Bug 965870 has been marked as a duplicate of this bug. ***

Comment 4 jurek.bajor 2013-05-22 19:16:08 UTC
There seems to be a fix:
https://bugzilla.kernel.org/show_bug.cgi?id=58401

Comment 5 Simon Lewis 2013-05-23 01:37:09 UTC
Can you let us know when when the fedora Kernel has been updated to include this patch and can be found in testing?

Comment 6 Josh Boyer 2013-05-23 13:37:31 UTC
I've started a scratch build of the kernel with that patch included.  Can you please download and test it once it completes building and let us know if the issue is resolved for you?

http://koji.fedoraproject.org/koji/taskinfo?taskID=5413972

Comment 7 jurek.bajor 2013-05-23 19:41:49 UTC
$ uname -a
Linux localhost.localdomain 3.9.3-302.1.fc19.i686 #1 SMP Thu May 23 15:40:56 UTC 2013 i686 i686 i386 GNU/Linux

Tested boot and suspend. OK.

Comment 8 jurek.bajor 2013-05-23 19:47:47 UTC
We would like to have the fix included in F18 as well.

Comment 9 Josh Boyer 2013-05-23 20:09:59 UTC
(In reply to jurek.bajor from comment #7)
> $ uname -a
> Linux localhost.localdomain 3.9.3-302.1.fc19.i686 #1 SMP Thu May 23 15:40:56
> UTC 2013 i686 i686 i386 GNU/Linux
> 
> Tested boot and suspend. OK.

Thanks for testing.

Comment 10 Josh Boyer 2013-05-23 20:16:20 UTC
(In reply to jurek.bajor from comment #8)
> We would like to have the fix included in F18 as well.

I've fixed it on all Fedora branches.  Bodhi will leave the usual comments when it gets submitted in an update.

Comment 11 Fedora Update System 2013-05-25 04:53:32 UTC
kernel-3.9.4-200.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/kernel-3.9.4-200.fc18

Comment 12 Fedora Update System 2013-05-25 12:08:35 UTC
kernel-3.9.4-300.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/kernel-3.9.4-300.fc19

Comment 13 Fedora Update System 2013-05-25 19:04:48 UTC
Package kernel-3.9.4-300.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.9.4-300.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9214/kernel-3.9.4-300.fc19
then log in and leave karma (feedback).

Comment 14 Fedora Update System 2013-05-26 02:57:34 UTC
kernel-3.9.4-200.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2013-05-27 03:22:26 UTC
kernel-3.9.4-300.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 16 Stanislaw Gruszka 2013-05-27 10:27:04 UTC
*** Bug 963708 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.