Bug 920762 - [abrt]: WARNING: at kernel/smp.c:466 smp_call_function_many+0xbd/0x270()
Summary: [abrt]: WARNING: at kernel/smp.c:466 smp_call_function_many+0xbd/0x270()
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6189e4245fc5ded00cc6f86772f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 16:58 UTC by João Paulo Rechi Vita
Modified: 2013-08-01 02:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 02:25:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (116.67 KB, text/x-log)
2013-03-12 19:13 UTC, João Paulo Rechi Vita
no flags Details

Description João Paulo Rechi Vita 2013-03-12 16:58:54 UTC
Additional info:
WARNING: at kernel/smp.c:466 smp_call_function_many+0xbd/0x270()
Hardware name: Latitude E6430
Modules linked in: hidp fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_CHECKSUM iptable_mangle bridge stp llc lockd sunrpc rfcomm 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 scsi_transport_iscsi bnep ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media snd_hda_codec_hdmi arc4 snd_hda_codec_idt iwldvm snd_hda_intel btusb snd_hda_codec snd_hwdep snd_seq snd_seq_device mac80211 bluetooth snd_pcm iwlwifi cfg80211 snd_page_alloc snd_timer rfkill vhost_net snd dell_laptop dcdbas ppdev parport_pc parport mei iTCO_wdt iTCO_vendor_support lpc_ich mfd_core soundcore coretemp tun e1000e i2c_i801 microcode dell_wmi sparse_keymap macvtap macvlan kvm_intel kvm uinput crc32c_intel ghas
h_clmulni_intel sdhci_pci sdhci mmc_core wmi usb_storage i915 video i2c_algo_bit drm_kms_helper drm i2c_core
Pid: 79, comm: kworker/2:2 Not tainted 3.7.9-104.fc17.x86_64 #1
Call Trace:
 [<ffffffff8105e6ff>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105e75a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff810bc09d>] smp_call_function_many+0xbd/0x270
 [<ffffffff8104c6b0>] ? rbt_memtype_copy_nth_element+0xc0/0xc0
 [<ffffffff8104c6b0>] ? rbt_memtype_copy_nth_element+0xc0/0xc0
 [<ffffffff810bc3a2>] smp_call_function+0x22/0x30
 [<ffffffff810bc408>] on_each_cpu+0x28/0x70
 [<ffffffff8104cc9d>] flush_tlb_kernel_range+0x6d/0x70
 [<ffffffff81166c14>] __purge_vmap_area_lazy+0x164/0x1c0
 [<ffffffff811679b5>] vm_unmap_aliases+0x175/0x190
 [<ffffffff81048ae0>] change_page_attr_set_clr+0xc0/0x470
 [<ffffffff81167497>] ? alloc_vmap_area+0x257/0x360
 [<ffffffff810497af>] _set_memory_wb+0x2f/0x40
 [<ffffffff81047867>] ioremap_change_attr+0x17/0x40
 [<ffffffff8104a66d>] kernel_map_sync_memtype+0x7d/0xe0
 [<ffffffff810475e8>] __ioremap_caller+0x268/0x370
 [<ffffffff816131e4>] ? acpi_os_map_memory+0x70/0x15f
 [<ffffffff81047724>] ioremap_cache+0x14/0x20
 [<ffffffff8161327a>] acpi_os_map_memory+0x106/0x15f
 [<ffffffff81359df6>] acpi_ex_system_memory_space_handler+0xea/0x1e9
 [<ffffffff81359d0c>] ? acpi_ex_do_logical_op+0x167/0x167
 [<ffffffff81353a33>] acpi_ev_address_space_dispatch+0x1aa/0x200
 [<ffffffff813570b8>] acpi_ex_access_region+0x275/0x292
 [<ffffffff813573df>] acpi_ex_field_datum_io+0xf9/0x176
 [<ffffffff8135771d>] acpi_ex_write_with_update_rule+0xc2/0xcd
 [<ffffffff8134421b>] ? acpi_os_wait_semaphore+0x49/0x5f
 [<ffffffff813572c4>] acpi_ex_insert_into_field+0x1ef/0x211
 [<ffffffff813442ae>] ? acpi_os_release_lock+0xe/0x10
 [<ffffffff81356dcf>] acpi_ex_write_data_to_field+0x1a2/0x1cf
 [<ffffffff8136764d>] ? acpi_ut_update_ref_count+0x5f/0xa9
 [<ffffffff8135abd2>] acpi_ex_store_object_to_node+0x9a/0xdd
 [<ffffffff8135acd2>] acpi_ex_store+0xbd/0x23f
 [<ffffffff8135837f>] acpi_ex_opcode_1A_1T_1R+0x368/0x4ba
 [<ffffffff813509f4>] acpi_ds_exec_end_op+0xd4/0x3f4
 [<ffffffff8136211d>] acpi_ps_parse_loop+0x7ce/0x971
 [<ffffffff8134ed18>] ? acpi_ds_call_control_method+0x131/0x1a1
 [<ffffffff813626b3>] acpi_ps_parse_aml+0x96/0x27b
 [<ffffffff81362f33>] acpi_ps_execute_method+0x1cb/0x27c
 [<ffffffff8135d767>] acpi_ns_evaluate+0xc3/0x1ad
 [<ffffffff813678ef>] acpi_ut_evaluate_object+0x83/0x1ac
 [<ffffffff81367a87>] acpi_ut_execute_STA+0x26/0x55
 [<ffffffff81360bec>] acpi_get_object_info+0x184/0x358
 [<ffffffff81346474>] do_acpi_find_child+0x1f/0x4a
 [<ffffffff81344252>] ? acpi_os_signal_semaphore+0x21/0x2d
 [<ffffffff8135fef5>] acpi_ns_walk_namespace+0xbe/0x179
 [<ffffffff81346455>] ? acpi_get_child+0x50/0x50
 [<ffffffff81346455>] ? acpi_get_child+0x50/0x50
 [<ffffffff813603ab>] acpi_walk_namespace+0x98/0xcb
 [<ffffffff8134644b>] acpi_get_child+0x46/0x50
 [<ffffffff81424b1a>] ata_dev_acpi_handle+0x4a/0x90
 [<ffffffff81425d61>] ata_acpi_unbind+0x21/0xa0
 [<ffffffff81415e79>] ata_scsi_handle_link_detach+0xa9/0x190
 [<ffffffff81418754>] ata_scsi_hotplug+0x64/0xb0
 [<ffffffff8107a657>] process_one_work+0x147/0x490
 [<ffffffff814186f0>] ? ata_scsi_media_change_notify+0x30/0x30
 [<ffffffff8107ceee>] worker_thread+0x15e/0x450
 [<ffffffff8107cd90>] ? busy_worker_rebind_fn+0x110/0x110
 [<ffffffff81081e50>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0
 [<ffffffff81081d90>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff8163b7ec>] ret_from_fork+0x7c/0xb0
 [<ffffffff81081d90>] ? kthread_create_on_node+0x120/0x120

Potential duplicate: bug 886965

Comment 1 Josh Boyer 2013-03-12 18:38:09 UTC
You seem to be hitting this:

WARN_ON_ONCE(cpu_online(this_cpu) && irqs_disabled()
                     && !oops_in_progress && !early_boot_irqs_disabled);

which means that interrupts are disabled when they shouldn't be.  Can you post the full dmesg for this boot?

Comment 2 João Paulo Rechi Vita 2013-03-12 19:13:40 UTC
Created attachment 709120 [details]
dmesg

Submitting full dmesg.

Comment 3 Josh Boyer 2013-03-12 19:31:18 UTC
Hm.  This seems to be because your hard drive stopped responding to commands for a bit.  Have you run the smartctl selftests on this drive recently?

Comment 4 João Paulo Rechi Vita 2013-03-13 14:19:13 UTC
You're referring to /dev/sdd, right? This is a external HD which was connected on the eSATA interface through a eSATA-SATA cable.

It seems the SMART command has failed when trying to run SMART self tests (dmesg [11921.879834]). Command output and dmesg log after drive connected bellow (HD was /dev/sdc on this boot):

---

[jprvita@schizophrenia ~]$ sudo smartctl -t long -C /dev/sdc
[sudo] password for jprvita: 
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.9-104.fc17.x86_64] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in captive mode".
Drive command "Execute SMART Extended self-test routine immediately in captive mode" successful.
Testing has begun.
Please wait 255 minutes for test to complete.
Test will complete after Wed Mar 13 15:01:12 2013

[jprvita@schizophrenia ~]$ 

---

dmesg output:

[ 9658.711098] ata5: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[ 9658.711105] ata5: irq_stat 0x00000040, connection status changed
[ 9658.711109] ata5: SError: { CommWake DevExch }
[ 9658.711118] ata5: hard resetting link
[ 9660.913819] ata5: SATA link down (SStatus 1 SControl 300)
[ 9660.913836] ata5: EH complete
[ 9660.924741] ata5: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[ 9660.924750] ata5: irq_stat 0x00000040, connection status changed
[ 9660.924756] ata5: SError: { CommWake DevExch }
[ 9660.924769] ata5: hard resetting link
[ 9663.128294] ata5: SATA link down (SStatus 1 SControl 300)
[ 9663.128315] ata5: EH complete
[ 9663.139216] ata5: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[ 9663.139225] ata5: irq_stat 0x00000040, connection status changed
[ 9663.139231] ata5: SError: { CommWake DevExch }
[ 9663.139245] ata5: limiting SATA link speed to 1.5 Gbps
[ 9663.139252] ata5: hard resetting link
[ 9664.116578] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9664.351989] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 9664.351998] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 9664.352003] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 9664.352179] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 9664.391673] ata5.00: ATA-8: WDC WD10TPVT-00HT5T0, 01.01A01, max UDMA/133
[ 9664.391681] ata5.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 9664.462929] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 9664.462939] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 9664.462943] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 9664.463138] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 9664.469015] ata5.00: configured for UDMA/133
[ 9664.469043] ata5: EH complete
[ 9664.469221] scsi 4:0:0:0: Direct-Access     ATA      WDC WD10TPVT-00H 01.0 PQ: 0 ANSI: 5
[ 9664.492833] sd 4:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 9664.492882] sd 4:0:0:0: Attached scsi generic sg3 type 0
[ 9664.493118] sd 4:0:0:0: [sdc] Write Protect is off
[ 9664.493132] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 9664.493340] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9664.511480]  sdc: sdc1
[ 9664.512217] sd 4:0:0:0: [sdc] Attached SCSI disk
[11921.879825] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[11921.879834] ata5.00: failed command: SMART
[11921.879842] ata5.00: cmd b0/d4:00:82:4f:c2/00:00:00:00:00/00 tag 0
[11921.879842]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[11921.879847] ata5.00: status: { DRDY }
[11921.879853] ata5: hard resetting link
[11922.184556] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[11922.253189] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[11922.253198] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[11922.253203] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[11922.253384] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[11922.361028] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[11922.361039] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[11922.361047] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[11922.361231] ata5.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[11922.367140] ata5.00: configured for UDMA/133
[11922.367186] ata5: EH complete

---

And when I run 'sudo smartctl -l selftest /dev/sdc' (even after reboot) I get this:

[jprvita@schizophrenia ~]$ sudo smartctl -l selftest /dev/sdc
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.9-104.fc17.x86_64] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended captive    Interrupted (host reset)      90%       971         -

Comment 5 Fedora End Of Life 2013-07-03 23:36:07 UTC
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.

Comment 6 Fedora End Of Life 2013-08-01 02:25:51 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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


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