Bug 1182370

Summary: [abrt] WARNING: CPU: 3 PID: 76 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
Product: [Fedora] Fedora Reporter: Peter Trenholme <PTrenholme>
Component: kernelAssignee: fs-maint
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, mchehab, pomidorabelisima
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9fe938768a949848290130211cd27d848f1721d2
Whiteboard: abrt_hash:54fc859a2549ca43b6ffe3804e5d924f67cf5000
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-23 21:04:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Peter Trenholme 2015-01-15 00:31:36 UTC 
Description of problem:
Just booted, loged in, and started KDE

Additional info:
reporter:       libreport-2.3.0
WARNING: CPU: 3 PID: 76 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
do not call blocking ops when !TASK_RUNNING; state=2 set at [<ffffffff818709e5>] wait_for_completion_io+0xf5/0x150
Modules linked in: v4l2_common videodev media rt2800pci(+) rt2800mmio rt2800lib rt2x00pci rt2x00mmio kvm_amd rt2x00lib snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_controller snd_hda_codec kvm cfg80211 snd_hwdep snd_seq eeprom_93cx6 crc_ccitt rfkill snd_seq_device serio_raw snd_pcm k10temp edac_core edac_mce_amd snd_timer snd soundcore sp5100_tco shpchp i2c_piix4 acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace binfmt_misc raid1 btrfs xor raid6_pq radeon uas usb_storage 8021q garp i2c_algo_bit mrp drm_kms_helper stp llc ttm drm r8169 mii wmi sunrpc
CPU: 3 PID: 76 Comm: kworker/u12:2 Not tainted 3.19.0-0.rc3.git2.1.fc22.x86_64 #1
Hardware name: Hewlett-Packard p6710f/2AB1 , BIOS 6.07 05/04/2011
Workqueue: writeback bdi_writeback_workfn (flush-9:127)
 0000000000000000 00000000d56aa949 ffff8800c99e3208 ffffffff8186cc07
 0000000000000000 ffff8800c99e3260 ffff8800c99e3248 ffffffff810ac82a
 ffff8800c99d4150 ffffffff81cb6da0 00000000000006e3 0000000000000000
Call Trace:
 [<ffffffff8186cc07>] dump_stack+0x4c/0x65
 [<ffffffff810ac82a>] warn_slowpath_common+0x8a/0xc0
 [<ffffffff810ac8b5>] warn_slowpath_fmt+0x55/0x70
 [<ffffffff818709e5>] ? wait_for_completion_io+0xf5/0x150
 [<ffffffff818709e5>] ? wait_for_completion_io+0xf5/0x150
 [<ffffffff810dd5fd>] __might_sleep+0xbd/0xd0
 [<ffffffff81028c4a>] ? native_sched_clock+0x2a/0xa0
 [<ffffffff813e9a6f>] generic_make_request_checks+0x3f/0x620
 [<ffffffff81109f9c>] ? mark_held_locks+0x7c/0xb0
 [<ffffffff81875f66>] ? _raw_spin_unlock_irqrestore+0x36/0x70
 [<ffffffff8110a12d>] ? trace_hardirqs_on_caller+0x15d/0x200
 [<ffffffff813ea077>] generic_make_request+0x27/0x150
 [<ffffffffa0451568>] raid1_unplug+0x108/0x160 [raid1]
 [<ffffffff813ed92a>] blk_flush_plug_list+0x9a/0x260
 [<ffffffff81870247>] io_schedule_timeout+0x87/0x110
 [<ffffffff81875fd0>] ? _raw_spin_unlock_irq+0x30/0x50
 [<ffffffff81870a07>] wait_for_completion_io+0x117/0x150
 [<ffffffff810e6a00>] ? wake_up_state+0x20/0x20
 [<ffffffff813f5787>] __blkdev_issue_zeroout+0x227/0x270
 [<ffffffff8187093c>] ? wait_for_completion_io+0x4c/0x150
 [<ffffffff813f58b9>] blkdev_issue_zeroout+0xe9/0xf0
 [<ffffffff81106d0e>] ? __lock_is_held+0x5e/0x90
 [<ffffffff8134093c>] ext4_ext_zeroout.isra.33+0x4c/0x60
 [<ffffffff81346a17>] ext4_ext_handle_unwritten_extents+0x6a7/0x10c0
 [<ffffffff81106d0e>] ? __lock_is_held+0x5e/0x90
 [<ffffffff81347d7e>] ext4_ext_map_blocks+0x91e/0x13b0
 [<ffffffff81314d53>] ? ext4_map_blocks+0x123/0x580
 [<ffffffff81314d53>] ? ext4_map_blocks+0x123/0x580
 [<ffffffff81314d76>] ext4_map_blocks+0x146/0x580
 [<ffffffff81318a20>] ext4_writepages+0x810/0x13b0
 [<ffffffff811f3111>] do_writepages+0x21/0x40
 [<ffffffff812a86cb>] __writeback_single_inode+0x6b/0x880
 [<ffffffff812a9d35>] writeback_sb_inodes+0x295/0x5e0
 [<ffffffff812aa11f>] __writeback_inodes_wb+0x9f/0xd0
 [<ffffffff812aa573>] wb_writeback+0x423/0x7a0
 [<ffffffff811f1700>] ? bdi_dirty_limit+0x40/0xe0
 [<ffffffff812aae10>] bdi_writeback_workfn+0x280/0x920
 [<ffffffff810cde05>] process_one_work+0x215/0x840
 [<ffffffff810cdd6e>] ? process_one_work+0x17e/0x840
 [<ffffffff810ce52b>] ? worker_thread+0xfb/0x4b0
 [<ffffffff810ce49b>] worker_thread+0x6b/0x4b0
 [<ffffffff810ce430>] ? process_one_work+0x840/0x840
 [<ffffffff810d492f>] kthread+0x11f/0x140
 [<ffffffff810eab85>] ? local_clock+0x25/0x30
 [<ffffffff810d4810>] ? kthread_create_on_node+0x250/0x250
 [<ffffffff81876b7c>] ret_from_fork+0x7c/0xb0
 [<ffffffff810d4810>] ? kthread_create_on_node+0x250/0x250
Comment 1 Peter Trenholme 2015-01-15 00:31:39 UTC 
Created attachment 980257 [details]
File: dmesg
Comment 2 Jaroslav Reznik 2015-03-03 16:42:49 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 3 poma 2015-05-14 17:50:18 UTC 
https://bugzilla.kernel.org/show_bug.cgi?id=98191
https://bugzilla.redhat.com/show_bug.cgi?id=1220519
Comment 4 Justin M. Forbes 2015-10-20 19:30:11 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.
Comment 5 Peter Trenholme 2015-10-23 20:52:19 UTC 
Sorry, I should have marked this as no longer an issue. (It was, IIRC, fixed before 22 was released.)