Bug 1089550

Summary: [abrt] WARNING: CPU: 1 PID: 6 at fs/buffer.c:1166 mark_buffer_dirty+0xb5/0xd0()
Product: [Fedora] Fedora Reporter: Chuck Forsberg <caf>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cf8dcfaab3af608bb6be647ae2b486196ba75ab1
Whiteboard: abrt_hash:306a44e19bc0477c80c484cace87309b845dcd82
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-10 15:01:25 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 Chuck Forsberg 2014-04-20 15:41:03 UTC 
Additional info:
reporter:       libreport-2.2.1
WARNING: CPU: 1 PID: 6 at fs/buffer.c:1166 mark_buffer_dirty+0xb5/0xd0()
sd 6:0:0:0: [sde] Unhandled error code
sd 6:0:0:0: [sde]  
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 6:0:0:0: [sde] CDB: 
Write(16): 8a
Modules linked in: arc4 md4 nls_utf8 cifs dns_resolver fscache fuse xt_CHECKSUM tun bnep bluetooth ip6t_ipv6header nf_conntrack_ftp ipt_MASQUERADE cfg80211 ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter 00 00 00
 ip6_tables 00 00 00
 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw pl2303 eeepc_wmi 00 08 00 00 00
 asus_wmi 00 08 00 00
end_request: I/O error, dev sde, sector 2048
Buffer I/O error on device sde1, logical block 0
lost page write due to I/O error on sde1
 sparse_keymap rfkill iTCO_wdt iTCO_vendor_support ppdev snd_hda_codec_hdmi x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel joydev snd_hda_codec_realtek microcode serio_raw sb_edac edac_core snd_hda_intel i2c_i801 snd_hda_codec snd_virtuoso snd_oxygen_lib snd_mpu401_uart snd_hwdep snd_rawmidi lpc_ich mfd_core snd_seq snd_seq_device snd_pcm parport_serial parport_pc parport snd_page_alloc snd_timer snd soundcore mei_me mei shpchp nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc nouveau video i2c_algo_bit drm_kms_helper ttm drm mxm_wmi r8169 mii i2c_core wmi
CPU: 1 PID: 6 Comm: kworker/u16:0 Not tainted 3.13.10-200.fc20.x86_64 #1
Hardware name: System manufacturer System Product Name/X79-DELUXE, BIOS 0701 01/07/2014
Workqueue: writeback bdi_writeback_workfn (flush-8:64)
 0000000000000009 ffff880813f53990 ffffffff81687eac 0000000000000000
 ffff880813f539c8 ffffffff8106d4dd 000000000e8e1e4b ffff88080865ec98
 ffff880809999400 000000004cc72388 ffff880811a75800 ffff880813f539d8
Call Trace:
 [<ffffffff81687eac>] dump_stack+0x45/0x56
 [<ffffffff8106d4dd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106d5ba>] warn_slowpath_null+0x1a/0x20
 [<ffffffff811e9265>] mark_buffer_dirty+0xb5/0xd0
 [<ffffffff8125af64>] ext4_commit_super+0x174/0x230
 [<ffffffff8125b7fd>] __ext4_std_error+0x6d/0x100
 [<ffffffff8126bf40>] __ext4_journal_stop+0x80/0x90
 [<ffffffff81242c57>] ext4_writepages+0x7e7/0xcc0
 [<ffffffff8115676e>] do_writepages+0x1e/0x40
 [<ffffffff811e10b0>] __writeback_single_inode+0x40/0x210
 [<ffffffff811e1c5f>] writeback_sb_inodes+0x19f/0x400
 [<ffffffff811e1f5f>] __writeback_inodes_wb+0x9f/0xd0
 [<ffffffff811e2703>] wb_writeback+0x233/0x2b0
EXT4-fs (sde1): previous I/O error to superblock detected
 [<ffffffff811e3c43>] bdi_writeback_workfn+0x2c3/0x430
 [<ffffffff81087bf6>] process_one_work+0x176/0x430
 [<ffffffff8108882b>] worker_thread+0x11b/0x3a0
 [<ffffffff81088710>] ? rescuer_thread+0x350/0x350
 [<ffffffff8108f2f2>] kthread+0xd2/0xf0
 [<ffffffff8108f220>] ? insert_kthread_work+0x40/0x40
 [<ffffffff81696dbc>] ret_from_fork+0x7c/0xb0
sd 6:0:0:0: [sde] Unhandled error code
sd 6:0:0:0: [sde]  
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 6:0:0:0: [sde] CDB: 
Write(16): 8a
 [<ffffffff8108f220>] ? insert_kthread_work+0x40/0x40
Comment 1 Chuck Forsberg 2014-04-20 15:41:07 UTC 
Created attachment 887965 [details]
File: dmesg
Comment 2 Justin M. Forbes 2014-05-21 19:39:45 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  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 experience different issues, please open a new bug report for those.
Comment 3 Chuck Forsberg 2014-05-22 07:59:43 UTC 
The Fedora kernel running omen.com has been rather stable since I disabled the Intel Ethernet chip on the motherboard.
Comment 4 Justin M. Forbes 2014-11-13 16:02:01 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 5 Justin M. Forbes 2014-12-10 15:01:25 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.