Bug 1133347 - [abrt] WARNING: CPU: 5 PID: 3314 at fs/buffer.c:1166 mark_buffer_dirty+0xb5/0xd0() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 5 PID: 3314 at fs/buffer.c:1166 mark_buffer_dirty+0xb5/0...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fedora-kernel-extfs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:554377d60650cd19c8dfa029055...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-24 23:03 UTC by Ian Pilcher
Modified: 2014-12-10 14:59 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 14:59:38 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (70.29 KB, text/plain)
2014-08-24 23:03 UTC, Ian Pilcher
no flags Details

Description Ian Pilcher 2014-08-24 23:03:51 UTC
Additional info:
reporter:       libreport-2.2.3
WARNING: CPU: 5 PID: 3314 at fs/buffer.c:1166 mark_buffer_dirty+0xb5/0xd0()
Modules linked in: loop rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd sunrpc fscache vfat fat uas usb_storage iptable_nat nf_nat_ipv4 nf_nat fuse 8021q garp stp mrp llc ip6table_filter ip6_tables ebtable_nat ebtables openvswitch gre vxlan libcrc32c w83627ehf hwmon_vid xt_conntrack nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack btrfs raid6_pq xor iTCO_wdt gpio_ich iTCO_vendor_support ppdev x86_pkg_temp_thermal coretemp kvm_intel kvm snd_hda_codec_hdmi crct10dif_pclmul e1000e snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec crc32_pclmul snd_hwdep crc32c_intel snd_seq ghash_clmulni_intel snd_seq_device mei_me nuvoton_cir i2c_i801 mei lpc_ich ptp pps_core shpchp rc_core mfd_core parport_pc snd_pcm serio_raw parport microcode snd_timer snd
soundcore binfmt_misc raid1 bcache i915 video i2c_algo_bit drm_kms_helper drm i2c_core [last unloaded: nf_nat]
CPU: 5 PID: 3314 Comm: cat Not tainted 3.15.10-200.rhbz1125273.fc20.x86_64 #1
Hardware name:                  /DQ67SW, BIOS SWQ6710H.86A.0065.2012.0917.1519 09/17/2012
0000000000000000 00000000f72be33b ffff88070596fb38 ffffffff816ef9c8
0000000000000000 ffff88070596fb70 ffffffff8108931d 0000000000000001
ffff8806c98e5410 ffffffff8182c4c0 00000000000000fe ffff88080b993000
Call Trace:
[<ffffffff816ef9c8>] dump_stack+0x45/0x56
[<ffffffff8108931d>] warn_slowpath_common+0x7d/0xa0
[<ffffffff8108944a>] warn_slowpath_null+0x1a/0x20
[<ffffffff81218255>] mark_buffer_dirty+0xb5/0xd0
[<ffffffff812a0851>] __ext4_handle_dirty_super+0x41/0x90
[<ffffffff8126b349>] ext4_file_open+0x149/0x190
[<ffffffff811e3ddf>] do_dentry_open+0x1ff/0x2c0
[<ffffffff8126b200>] ? ext4_htree_store_dirent+0x120/0x120
[<ffffffff811e4071>] finish_open+0x31/0x40
[<ffffffff811f5e64>] do_last+0xa64/0x1190
[<ffffffff811f2161>] ? link_path_walk+0x81/0x890
[<ffffffff811c9ec6>] ? kmem_cache_alloc_trace+0x1d6/0x200
[<ffffffff812eb5ec>] ? selinux_file_alloc_security+0x3c/0x60
[<ffffffff811f665d>] path_openat+0xcd/0x670
[<ffffffff811a4acd>] ? vma_link+0x7d/0xc0
[<ffffffff811f745d>] do_filp_open+0x4d/0xb0
[<ffffffff81203f9d>] ? __alloc_fd+0x7d/0x120
[<ffffffff811e5af7>] do_sys_open+0x137/0x240
[<ffffffff811e5c1e>] SyS_open+0x1e/0x20
[<ffffffff816ffae9>] system_call_fastpath+0x16/0x1b

Comment 1 Ian Pilcher 2014-08-24 23:03:54 UTC
Created attachment 930248 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-11-13 15:59:40 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 3 Justin M. Forbes 2014-12-10 14:59:38 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.


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