Bug 746331 - [abrt] kernel: WARNING: at kernel/timer.c:1011 del_timer_sync+0x37/0x4c(): TAINTED P--------W
Summary: [abrt] kernel: WARNING: at kernel/timer.c:1011 del_timer_sync+0x37/0x4c(): TA...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e829970cc48fa3a1dda3cd27e80...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-14 19:25 UTC by Gregory Trivett
Modified: 2011-10-27 10:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-14 19:32:36 UTC
Type: ---


Attachments (Terms of Use)

Description Gregory Trivett 2011-10-14 19:25:48 UTC
abrt version: 2.0.3
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_gtrit61-lv_root rd_LVM_LV=vg_gtrit61/lv_root rd_LVM_LV=vg_gtrit61/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet nouveau.modeset=0 rdblacklist=nouveau
comment:        sleeping, waking.. you know.. it's probably something way over my head..but thanks for asking me to describe what i did wrong.
component:      kernel
kernel:         2.6.40.6-0.fc15.x86_64
kernel_tainted: 513
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         WARNING: at kernel/timer.c:1011 del_timer_sync+0x37/0x4c()
time:           Tue Oct 11 13:48:18 2011

backtrace:
:WARNING: at kernel/timer.c:1011 del_timer_sync+0x37/0x4c()
:Hardware name: 6470W2X
:Modules linked in: tcp_lp hidp fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge stp llc vboxpci vboxnetadp vboxnetflt vboxdrv sunrpc cpufreq_ondemand acpi_cpufreq mperf rfcomm nf_conntrack_netbios_ns ip6t_REJECT nf_conntrack_broadcast nf_conntrack_ipv6 bnep nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 xt_state ip6table_filter nf_conntrack ip6_tables nvidia(P) snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer btusb thinkpad_acpi arc4 i2c_i801 iTCO_wdt snd e1000e iwl3945 iwl_legacy mac80211 bluetooth cfg80211 snd_page_alloc i2c_core iTCO_vendor_support ppdev parport_pc parport r852 r592 rfkill memstick sm_common nand nand_ids nand_ecc mtd soundcore microcode joydev virtio_net kvm_intel kvm ipv6 firewire_ohci firewire_core sdhci_pci sdhci mmc_core yenta_socket crc_itu_t wmi video [last unloaded: scsi_wait_scan]
:Pid: 0, comm: kworker/0:0 Tainted: P            2.6.40.6-0.fc15.x86_64 #1
:Call Trace:
: <IRQ>  [<ffffffff81054d0e>] warn_slowpath_common+0x83/0x9b
: [<ffffffff81054d40>] warn_slowpath_null+0x1a/0x1c
: [<ffffffff810615d4>] del_timer_sync+0x37/0x4c
: [<ffffffffa104fca6>] rtTimerLnxStopSubTimer+0x24/0x30 [vboxdrv]
: [<ffffffffa104fdf5>] rtTimerLinuxMpEvent+0x143/0x196 [vboxdrv]
: [<ffffffff81072f70>] ? enqueue_hrtimer+0x3f/0x7a
: [<ffffffffa104c423>] rtMpNotificationDoCallbacks+0xc5/0x120 [vboxdrv]
: [<ffffffffa104fcb2>] ? rtTimerLnxStopSubTimer+0x30/0x30 [vboxdrv]
: [<ffffffffa104e545>] rtMpNotificationLinuxOnCurrentCpu+0xd5/0xde [vboxdrv]
: [<ffffffffa104e0e6>] rtmpLinuxWrapper+0x28/0x2a [vboxdrv]
: [<ffffffff8108349e>] generic_smp_call_function_single_interrupt+0xb2/0xd4
: [<ffffffff8102043b>] smp_call_function_single_interrupt+0x18/0x29
: [<ffffffff8148fb73>] call_function_single_interrupt+0x13/0x20
: <EOI>  [<ffffffff81072f70>] ? enqueue_hrtimer+0x3f/0x7a
: [<ffffffff812acafb>] ? arch_local_irq_enable+0x8/0xd
: [<ffffffff812ad461>] acpi_idle_enter_c1+0x3a/0xab
: [<ffffffff813afead>] cpuidle_idle_call+0xd7/0x168
: [<ffffffff81008307>] cpu_idle+0xa5/0xdf
: [<ffffffff81477c93>] start_secondary+0x23f/0x241

kernel_tainted_long:
:Proprietary module has been loaded.
:Taint on warning.

Comment 1 Josh Boyer 2011-10-14 19:32:36 UTC
Those appear to be issues in the vbox drivers.  Also, you have the nvidia driver loaded.  If you can recreate this without any of those loaded, let us know.

Comment 2 Frank Mehnert 2011-10-27 10:16:21 UTC
Thanks for this report. The next VirtualBox release (4.1.6) will contain a fix for this problem.


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