Bug 1152784 - [abrt] WARNING: CPU: 1 PID: 28245 at fs/buffer.c:1168 mark_buffer_dirty+0xb5/0xd0() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 1 PID: 28245 at fs/buffer.c:1168 mark_buffer_dirty+0xb5/...
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: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:49c1eae43abbdefdd861dce041f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-14 23:40 UTC by ken
Modified: 2014-12-10 15:00 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:00:18 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (75.89 KB, text/plain)
2014-10-14 23:40 UTC, ken
no flags Details

Description ken 2014-10-14 23:40:43 UTC
Additional info:
reporter:       libreport-2.2.3
WARNING: CPU: 1 PID: 28245 at fs/buffer.c:1168 mark_buffer_dirty+0xb5/0xd0()
Modules linked in: nls_utf8 udf fuse bnep bluetooth ip6t_rpfilter ip6t_REJECT cfg80211 rfkill 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 ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel kvm_amd snd_hda_controller snd_hda_codec kvm snd_hwdep snd_seq snd_seq_device snd_pcm sp5100_tco edac_core edac_mce_amd shpchp k10temp i2c_piix4 microcode serio_raw snd_timer snd wmi soundcore asus_atk0110 acpi_cpufreq binfmt_misc ata_generic pata_acpi radeon atl1e pata_atiixp i2c_algo_bit drm_kms_helper
ttm firewire_ohci firewire_core drm crc_itu_t i2c_core
CPU: 1 PID: 28245 Comm: pool Not tainted 3.16.4-200.fc20.x86_64 #1
Hardware name: System manufacturer System Product Name/M4A78-E, BIOS 1210    06/26/2009
0000000000000000 00000000a184eeb9 ffff8800bcb5fb38 ffffffff81707965
0000000000000000 ffff8800bcb5fb70 ffffffff8108d0ad ffff8800ab24e138
ffff8800ab24e138 ffff88020387f388 ffff880091a76000 ffff8800c678c378
Call Trace:
[<ffffffff81707965>] dump_stack+0x45/0x56
[<ffffffff8108d0ad>] warn_slowpath_common+0x7d/0xa0
[<ffffffff8108d1da>] warn_slowpath_null+0x1a/0x20
[<ffffffff81225545>] mark_buffer_dirty+0xb5/0xd0
[<ffffffffa05c553d>] lvid_get_unique_id+0x5d/0x70 [udf]
[<ffffffffa05bc2d4>] udf_new_inode+0xe4/0x310 [udf]
[<ffffffffa05c3b59>] udf_create+0x39/0x190 [udf]
[<ffffffff8120244d>] vfs_create+0xcd/0x130
[<ffffffff81202ed6>] do_last+0xa26/0x1190
[<ffffffff811ff1b1>] ? link_path_walk+0x81/0x8c0
[<ffffffff811d6b56>] ? kmem_cache_alloc_trace+0x1d6/0x200
[<ffffffff812f632c>] ? selinux_file_alloc_security+0x3c/0x60
[<ffffffff8120370d>] path_openat+0xcd/0x670
[<ffffffff812180a8>] ? vfs_getxattr+0x88/0xb0
[<ffffffff812182a0>] ? getxattr+0x160/0x1d0
[<ffffffff8120450d>] do_filp_open+0x4d/0xb0
[<ffffffff8121107d>] ? __alloc_fd+0x7d/0x120
[<ffffffff811f2b07>] do_sys_open+0x137/0x240
[<ffffffff811f2c2e>] SyS_open+0x1e/0x20
[<ffffffff8170efa9>] system_call_fastpath+0x16/0x1b

Comment 1 ken 2014-10-14 23:40:49 UTC
Created attachment 947057 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-11-13 16:00:26 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 15:00:18 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.