rfkill hotkey does not switch off bluetooth on Dell Inspiron Mini

 SRU Justification:

    Impact:
    A type of Dell Inspiron Mini does not turn off bluetooth physically when
    pressing F2 (rfkill hotkey).

    Fix:
    Current kernel code expects hardware to handle the hard-rfkill switching
    spontaneously and only notify rfkill subsystem with the status change.
    This patch makes kernel to explicitly fire a SMI to switch on/off
    rfkill devices if BIOS reports that the hardware switch is not supported.

    This patch depends on the following sauce patch in lucid kernel so is not going upstream:
            UBUNTU: SAUCE: dell-laptop: Store the HW switch status internally rather than requerying every time

    Testcase:
    I tested the patch on a Dell Mini 10. It works smoothly.

Accepted linux into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

This bug was fixed in the package linux - 2.6.32-24.38

---------------
linux (2.6.32-24.38) lucid-proposed; urgency=low

  [ Keng-Yu Lin ]

  * SAUCE: dell-laptop: fire SMI when toggling hardware killswitch
    (revised)
    - LP: #590607

  [ Upstream Kernel Changes ]

  * sfc: Wait at most 10ms for the MC to finish reading out MAC statistics
    - LP: #590783
  * sfc: Always close net device at the end of a disabling reset
    - LP: #590783
  * sfc: Change falcon_probe_board() to fail for unsupported boards
    - LP: #590783
  * ext4: Fix potential quota deadlock
    - LP: #588069
  * jbd: jbd-debug and jbd2-debug should be writable
    - LP: #588069
  * ext4: replace BUG() with return -EIO in ext4_ext_get_blocks
    - LP: #588069
  * ext4, jbd2: Add barriers for file systems with exernal journals
    - LP: #588069
  * ext4: Eliminate potential double free on error path
    - LP: #588069
  * ext4: return correct wbc.nr_to_write in ext4_da_writepages
    - LP: #588069
  * ext4: Ensure zeroout blocks have no dirty metadata
    - LP: #588069
  * ext4: Patch up how we claim metadata blocks for quota purposes
    - LP: #588069
  * ext4: Fix accounting of reserved metadata blocks
    - LP: #588069
  * ext4: Calculate metadata requirements more accurately
    - LP: #588069
  * ext4: Handle -EDQUOT error on write
    - LP: #588069
  * ext4: Fix quota accounting error with fallocate
    - LP: #588069
  * ext4: Drop EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE flag
    - LP: #588069
  * ext4: Use bitops to read/modify EXT4_I(inode)->i_state
    - LP: #588069
  * ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
    - LP: #588069
  * ext4: Add flag to files with blocks intentionally past EOF
    - LP: #588069
  * ext4: Fix fencepost error in chosing choosing group vs file
    preallocation.
    - LP: #588069
  * ext4: fix error handling in migrate
    - LP: #588069
  * ext4: explicitly remove inode from orphan list after failed direct io
    - LP: #588069
  * ext4: Handle non empty on-disk orphan link
    - LP: #588069
  * ext4: make "offset" consistent in ext4_check_dir_entry()
    - LP: #588069
  * ext4: Fix insertion point of extent in mext_insert_across_blocks()
    - LP: #588069
  * ext4: Fix the NULL reference in double_down_write_data_sem()
    - LP: #588069
  * ext4: Code cleanup for EXT4_IOC_MOVE_EXT ioctl
    - LP: #588069
  * ext4: Fix estimate of # of blocks needed to write indirect-mapped files
    - LP: #588069
  * ext4: Fixed inode allocator to correctly track a flex_bg's used_dirs
    - LP: #588069
  * ext4: Fix possible lost inode write in no journal mode
    - LP: #588069
  * ext4: Fix buffer head leaks after calls to ext4_get_inode_loc()
    - LP: #588069
  * ext4: Issue the discard operation *before* releasing the blocks to be
    reused
    - LP: #588069
  * ext4: check missed return value in ext4_sync_file()
    - LP: #588069
  * ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
    - LP: #588069
  * ext4: Remove unnecessary call to ext4_get_group_desc() in mballoc
    - LP: #588069
  * ext4: rename ext4_mb_release_desc() to ext4_mb_unload_buddy()
    - LP: #588069
  * ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32b...

After upgrading the kernel image from 2.6.32-24.37 to 2.6.32-24.38 I can't no longer suspend to RAM. The screen becomes black but the laptop doesn't enter in suspend state. Of course it's impossible to restore, I have to shutdown by holding the power switch a few seconds.

My laptop is a Dell Latitude E6510 and I'm writing this in this bug report because it seems related to Dell laptops.