Re: Kernel crash message in F12 - anyone explain?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As far as I know this is not a crash, but rather an unoptimal (slower)
path taken somewhere.
I don't thing there's neet to worry about this...

- Clemens

2010/1/30 Mike Cloaked <mike.cloaked@xxxxxxxxx>:
>
> Today I got the following after abrt popped up - I don't know what this
> refers to or why the crash happened!
>
> Jan 30 14:17:03 home1 kernel: ------------[ cut here ]------------
> Jan 30 14:17:03 home1 kernel: WARNING: at
> fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x32/0x56() (Not
> tainted)
> Jan 30 14:17:03 home1 kernel: Hardware name: OptiPlex 960
> Jan 30 14:17:03 home1 kernel: inotify closing but id=0 for entry=ef4832c0 in
> group=f006f480 still in idr.  Probably leaking memory
> Jan 30 14:17:03 home1 kernel: Modules linked in: fuse ipt_MASQUERADE bridge
> stp llc sunrpc cpufreq_ondemand acpi_cpufreq iptable_nat nf_nat
> iptable_mangle ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6
> dm_multipath kvm uinput usblp snd_hda_codec_analog snd_hda_intel
> snd_hda_codec snd_hwdep iTCO_wdt snd_seq iTCO_vendor_support e1000e
> snd_seq_device snd_pcm snd_timer serio_raw ppdev snd parport_pc i2c_i801
> soundcore parport dcdbas snd_page_alloc wmi pata_acpi ata_generic nouveau
> ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: microcode]
> Jan 30 14:17:03 home1 kernel: Pid: 2413, comm: imap Not tainted
> 2.6.31.12-174.2.3.fc12.i686.PAE #1
> Jan 30 14:17:03 home1 kernel: Call Trace:
> Jan 30 14:17:03 home1 kernel: [<c043db4b>] warn_slowpath_common+0x70/0x87
> Jan 30 14:17:03 home1 kernel: [<c04ede48>] ? idr_callback+0x32/0x56
> Jan 30 14:17:03 home1 kernel: [<c043dba0>] warn_slowpath_fmt+0x29/0x2c
> Jan 30 14:17:03 home1 kernel: [<c04ede48>] idr_callback+0x32/0x56
> Jan 30 14:17:03 home1 kernel: [<c059ee84>] idr_for_each+0x5c/0x97
> Jan 30 14:17:03 home1 kernel: [<c04ede16>] ? idr_callback+0x0/0x56
> Jan 30 14:17:03 home1 kernel: [<c04ec4fc>] ? fsnotify_put_event+0x48/0x4b
> Jan 30 14:17:03 home1 kernel: [<c04ede05>] inotify_free_group_priv+0x1a/0x2b
> Jan 30 14:17:03 home1 kernel: [<c04ec5db>]
> fsnotify_final_destroy_group+0x1e/0x28
> Jan 30 14:17:03 home1 kernel: [<c04ec69f>] fsnotify_put_group+0x75/0x78
> Jan 30 14:17:03 home1 kernel: [<c04edfbd>] inotify_release+0x1e/0x28
> Jan 30 14:17:03 home1 kernel: [<c04c9dbf>] __fput+0xed/0x184
> Jan 30 14:17:03 home1 kernel: [<c04c9e6e>] fput+0x18/0x1a
> Jan 30 14:17:03 home1 kernel: [<c04c7311>] filp_close+0x56/0x60
> Jan 30 14:17:03 home1 kernel: [<c04c737b>] sys_close+0x60/0x8f
> Jan 30 14:17:03 home1 kernel: [<c0408fbb>] sysenter_do_call+0x12/0x28
> Jan 30 14:17:03 home1 kernel: ---[ end trace 934d4ab904d334bf ]---
> Jan 30 14:17:03 home1 kernel: entry->group=(null) inode=(null) wd=1024
> Jan 30 14:17:52 home1 named[1064]: client 127.0.0.1#36927: RFC 1918 response
> from Internet for 1.122.168.192.in-addr.arpa
> Jan 30 14:18:17 home1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
> Jan 30 14:18:17 home1 abrtd: Directory 'kerneloops-1264861097-1' creation
> detected
> Jan 30 14:18:17 home1 abrtd: Getting local universal unique identification
> Jan 30 14:18:17 home1 abrtd: New crash, saving
> Jan 30 14:18:17 home1 abrtd:
> RunApp('/var/cache/abrt/kerneloops-1264861097-1','test x"`cat component`" =
> x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
> Jan 30 14:18:17 home1 abrtd: Getting local universal unique identification
> Jan 30 14:18:54 home1 named[1064]: client 127.0.0.1#53596: RFC 1918 response
> from Internet for 1.122.168.192.in-addr.arpa
> Jan 30 14:19:55 home1 abrtd: Getting crash infos...
> Jan 30 14:19:56 home1 named[1064]: client 127.0.0.1#44889: RFC 1918 response
> from Internet for 1.122.168.192.in-addr.arpa
> Jan 30 14:20:12 home1 abrtd: Creating report...
> Jan 30 14:20:12 home1 abrtd: Getting local universal unique identification
> Jan 30 14:20:12 home1 abrtd: Getting local universal unique identification
>
> Anyone interpret this for me?
> Tnanks
> --
> View this message in context: http://n3.nabble.com/Kernel-crash-message-in-F12-anyone-explain-tp178722p178722.html
> Sent from the Fedora Users mailing list archive at Nabble.com.
> --
> users mailing list
> users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux