Bug 575151 - rf kill switch causes atomic scheduling warning
Summary: rf kill switch causes atomic scheduling warning
Keywords:
Status: CLOSED DUPLICATE of bug 572827
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Len Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-19 15:41 UTC by Sunil
Modified: 2010-03-23 01:57 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-23 01:57:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The dmesg of the system (84.66 KB, application/octet-stream)
2010-03-19 15:41 UTC, Sunil
no flags Details
lspci -vvv (28.99 KB, application/octet-stream)
2010-03-19 15:42 UTC, Sunil
no flags Details

Description Sunil 2010-03-19 15:41:46 UTC
Created attachment 401273 [details]
The dmesg of the system

Description of problem:
turning off wireless using the rf-kill switch causes a warning.

Version-Release number of selected component (if applicable):
[sun@localhost ~]$ uname -r
2.6.32.9-70.fc12.i686.PAE
[sun@localhost ~]$ 

How reproducible:
Everytime

Steps to Reproduce:
1. Turn off the wifi using the rfkill switch
2.
3.
  
Actual results:
BUG: sleeping function called from invalid context at kernel/sched.c:5804
in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper
Pid: 0, comm: swapper Not tainted 2.6.32.9-70.fc12.i686.PAE #1
Call Trace:
 [<c04335e8>] __might_sleep+0xca/0xd1
 [<c07a43e3>] wait_for_common+0x26/0x10d
 [<c0433173>] ? task_rq_unlock+0xf/0x11
 [<c04345c9>] ? list_add+0xf/0x11
 [<c07a4555>] wait_for_completion+0x17/0x19
 [<c043e109>] set_cpus_allowed_ptr+0xcd/0xec
 [<f8b2a7b5>] dcdbas_smi_request+0x5c/0xdd [dcdbas]
 [<f8b52070>] dell_send_request+0x45/0x4d [dell_laptop]
 [<c0430d00>] ? ftrace_raw_event_sched_kthread_stop_ret+0x30/0x78
 [<f8b520aa>] dell_rfkill_query+0x32/0x63 [dell_laptop]
 [<f8b52104>] dell_input_filter+0x29/0x5b [dell_laptop]
 [<c06c630d>] input_pass_event+0x41/0x8b
 [<c06c830b>] input_handle_event+0x373/0x37c
 [<c06c83d5>] input_event+0x54/0x67
 [<c06ccc16>] atkbd_interrupt+0x40a/0x4b6
 [<c06c4841>] serio_interrupt+0x37/0x6a
 [<c06c52d6>] i8042_interrupt+0x1d9/0x1ea
 [<c048aea0>] handle_IRQ_event+0x57/0xfd
 [<c048c711>] handle_edge_irq+0xb5/0xf5
 [<c040b1e3>] handle_irq+0x40/0x4d
 [<c040a9a9>] do_IRQ+0x46/0x9a
 [<c0409750>] common_interrupt+0x30/0x38
 [<c045007b>] ? rm_from_queue_full+0x1/0x6b
 [<c06210d3>] ? acpi_idle_enter_bm+0x24d/0x27e
 [<c06f6c2f>] cpuidle_idle_call+0x72/0xc3
 [<c04081f2>] cpu_idle+0x96/0xb0
 [<c07a0671>] start_secondary+0x1f5/0x233
BUG: scheduling while atomic: swapper/0/0x10010000
Modules linked in: vfat fat fuse rfcomm sco bridge stp llc bnep l2cap sunrpc cpufreq_ondemand acpi_cpufreq ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 dm_multipath uinput snd_hda_codec_intelhdmi snd_hda_codec_idt btusb bluetooth arc4 snd_hda_intel ecb snd_hda_codec snd_hwdep iwlagn snd_seq sdhci_pci snd_seq_device firewire_ohci iwlcore firewire_core sdhci snd_pcm snd_timer crc_itu_t mac80211 mmc_core ricoh_mmc iTCO_wdt snd soundcore iTCO_vendor_support i2c_i801 snd_page_alloc tg3 cfg80211 dell_laptop dell_wmi rfkill dcdbas wmi joydev yenta_socket rsrc_nonstatic usb_storage i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: microcode]

Pid: 0, comm: swapper Not tainted (2.6.32.9-70.fc12.i686.PAE #1) Latitude E5500                  
EIP: 0060:[<c06210d3>] EFLAGS: 00000286 CPU: 1
EIP is at acpi_idle_enter_bm+0x24d/0x27e
EAX: c0a7f8ac EBX: 000032e5 ECX: 00000d6f EDX: 03285000
ESI: 00000000 EDI: f72134c0 EBP: f70a5f70 ESP: f70a5f48
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 8005003b CR2: 09bdab80 CR3: 00969000 CR4: 000006f0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
 [<c06f6c2f>] cpuidle_idle_call+0x72/0xc3
 [<c04081f2>] cpu_idle+0x96/0xb0
 [<c07a0671>] start_secondary+0x1f5/0x233


Expected results:
no issues like this at all

Additional info:
This is a dell latitude e5500. Should be in a position to test rpms (will be a bit hard to compile kernels locally and test them)

Attaching full dmesg

Comment 1 Sunil 2010-03-19 15:42:33 UTC
Created attachment 401274 [details]
lspci -vvv

Comment 2 Len Brown 2010-03-23 01:36:38 UTC
This appears to be a bug in the dell_laptop driver --
which invokes dcdbas_smi_request() from an interrupt handler.
But dcdbas_smi_request() requires running SMM from CPU0,
and switching to CPU0 (and waiting) requires interrupts to be enabled...

Comment 3 Len Brown 2010-03-23 01:57:56 UTC

*** This bug has been marked as a duplicate of bug 572827 ***


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