BUG: sleeping function called from invalid context atfs/proc/task_mmu.c:826
From: Dave Jones
Date: Wed Mar 28 2012 - 14:18:20 EST
Just hit this on v3.3-7919-g6658a69
Dave
BUG: sleeping function called from invalid context at fs/proc/task_mmu.c:826
in_atomic(): 1, irqs_disabled(): 0, pid: 15123, name: trinity
INFO: lockdep is turned off.
Pid: 15123, comm: trinity Not tainted 3.3.0+ #30
Call Trace:
[<ffffffff8109bf75>] __might_sleep+0x145/0x200
[<ffffffff8122ee77>] ? pagemap_pte_range+0x67/0x340
[<ffffffff8122ef3f>] pagemap_pte_range+0x12f/0x340
[<ffffffff811924b9>] walk_page_range+0x389/0x520
[<ffffffff8122e9a2>] pagemap_read+0x282/0x350
[<ffffffff8122ee10>] ? clear_refs_pte_range+0x180/0x180
[<ffffffff8122d340>] ? get_vmalloc_info+0x110/0x110
[<ffffffff8122e5c0>] ? pid_numa_maps_open+0x20/0x20
[<ffffffff811c3a43>] vfs_read+0xb3/0x180
[<ffffffff811c3b5d>] sys_read+0x4d/0x90
[<ffffffff816c02a9>] system_call_fastpath+0x16/0x1b
BUG: scheduling while atomic: trinity/15123/0x10000002
INFO: lockdep is turned off.
Modules linked in: scsi_transport_iscsi ip6_queue ipt_ULOG nfnetlink dccp_ipv4 dccp bnep sctp l2tp_ppp l2tp_netlink l2tp_core binfmt_misc hidp can_bcm ip_queue rfcomm cmtp kernelcapi phonet bluetooth rfkill can_raw can pppoe pppox ppp_generic slhc irda crc_ccitt rds af_key rose ax25 af_802154 appletalk ipx p8022 psnap llc p8023 atm nfs fscache auth_rpcgss nfs_acl lockd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables btrfs zlib_deflate libcrc32c dm_mirror dm_region_hash dm_log raid0 snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm coretemp snd_timer snd soundcore snd_page_alloc ppdev dcdbas microcode pcspkr serio_raw iTCO_wdt iTCO_vendor_support i2c_i801 tg3 parport_pc parport shpchp i5000_edac edac_core i5k_amb sunrpc firewire_ohci firewire_core crc_itu_t floppy nouveau ttm drm_kms_helper drm i2c_core mxm_wmi video wmi [last unloaded: scsi_wait_scan]
Pid: 15123, comm: trinity Not tainted 3.3.0+ #30
Call Trace:
[<ffffffff816ab6f0>] __schedule_bug+0x80/0x85
[<ffffffff816b63b9>] __schedule+0x969/0x9d0
[<ffffffff810a3f28>] __cond_resched+0x18/0x30
[<ffffffff816b6842>] _cond_resched+0x32/0x40
[<ffffffff8122ef44>] pagemap_pte_range+0x134/0x340
[<ffffffff811924b9>] walk_page_range+0x389/0x520
[<ffffffff8122e9a2>] pagemap_read+0x282/0x350
[<ffffffff8122ee10>] ? clear_refs_pte_range+0x180/0x180
[<ffffffff8122d340>] ? get_vmalloc_info+0x110/0x110
[<ffffffff8122e5c0>] ? pid_numa_maps_open+0x20/0x20
[<ffffffff811c3a43>] vfs_read+0xb3/0x180
[<ffffffff811c3b5d>] sys_read+0x4d/0x90
[<ffffffff816c02a9>] system_call_fastpath+0x16/0x1b
BUG: soft lockup - CPU#2 stuck for 22s! [trinity:15123]
Modules linked in: tun scsi_transport_iscsi ip6_queue ipt_ULOG nfnetlink dccp_ipv4 dccp bnep sctp l2tp_ppp l2tp_netlink l2tp_core binfmt_misc hidp can_bcm ip_queue rfcomm cmtp kernelcapi phonet bluetooth rfkill can_raw can pppoe pppox ppp_generic slhc irda crc_ccitt rds af_key rose ax25 af_802154 appletalk ipx p8022 psnap llc p8023 atm nfs fscache auth_rpcgss nfs_acl lockd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables btrfs zlib_deflate libcrc32c dm_mirror dm_region_hash dm_log raid0 snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm coretemp snd_timer snd soundcore snd_page_alloc ppdev dcdbas microcode pcspkr serio_raw iTCO_wdt iTCO_vendor_support i2c_i801 tg3 parport_pc parport shpchp i5000_edac edac_core i5k_amb sunrpc firewire_ohci firewire_core crc_itu_t floppy nouveau ttm drm_kms_helper drm i2c_core mxm_wmi video wmi [last unloaded: scsi_wait_scan]
irq event stamp: 0
hardirqs last enabled at (0): [< (null)>] (null)
hardirqs last disabled at (0): [<ffffffff81063958>] copy_process+0x6e8/0x19a0
softirqs last enabled at (0): [<ffffffff81063958>] copy_process+0x6e8/0x19a0
softirqs last disabled at (0): [< (null)>] (null)
(and then shit really hit the fan, with it spewing that CPU stuck message for
every CPU over and over)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/