Bug 744677

Summary: [abrt] kernel: WARNING: at lib/list_debug.c:56 __list_del_entry+0x8d/0x98(): TAINTED P--------W
Product: [Fedora] Fedora Reporter: Pavel Alexeev <pahan>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:dbff3dd9cfaa6e3d581dd9dde3c894cdc78e4276
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-03 19:33:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: smolt_data none

Description Pavel Alexeev 2011-10-10 07:09:05 UTC 
libreport version: 2.0.6
abrt_version:   2.0.4.981
cmdline:        BOOT_IMAGE=/vmlinuz-3.1.0-0.rc8.git0.1.fc16.x86_64 root=UUID=74c652da-2859-4b43-a6ab-6b265d5da89c ro quiet rhgb LANG=ru_RU.UTF-8 KEYTABLE=ru
comment:        I think it is not interfere with usercpace actions.
kernel:         undefined
kernel_tainted: 513
reason:         WARNING: at lib/list_debug.c:56 __list_del_entry+0x8d/0x98()
time:           Sun Oct  9 12:04:17 2011

smolt_data:     Binary file, 3604 bytes

backtrace:
:WARNING: at lib/list_debug.c:56 __list_del_entry+0x8d/0x98()
:Hardware name: RC410/RC510/RC710          
:list_del corruption. next->prev should be ffff880131404090, but was           (null)
:Modules linked in: cpufreq_stats rfcomm bnep btusb bluetooth rfkill tcp_lp lockd nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables binfmt_misc joydev uvcvideo videodev media v4l2_compat_ioctl32 fuse snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm lib80211_crypt_tkip microcode wl(P) intel_ips i2c_i801 r8169 snd_timer snd mii iTCO_wdt iTCO_vendor_support lib80211 soundcore snd_page_alloc sunrpc uinput nouveau ttm mxm_wmi wmi i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
:Pid: 12943, comm: Xorg Tainted: P            3.1.0-0.rc8.git0.1.fc16.x86_64 #1
:Call Trace:
: [<ffffffff81057b32>] warn_slowpath_common+0x83/0x9b
: [<ffffffff81057bed>] warn_slowpath_fmt+0x46/0x48
: [<ffffffff8122f41d>] __list_del_entry+0x8d/0x98
: [<ffffffff8122f436>] list_del+0xe/0x2d
: [<ffffffff81139af2>] dentry_kill+0x8f/0x127
: [<ffffffff81139ed9>] dput+0xd3/0xe0
: [<ffffffff8112a4de>] fput+0x1b8/0x1d0
: [<ffffffff810ff246>] remove_vma+0x45/0x7a
: [<ffffffff81100539>] do_munmap+0x2f2/0x30b
: [<ffffffff811d1f20>] sys_shmdt+0xa0/0x134
: [<ffffffff814bc0c2>] system_call_fastpath+0x16/0x1b

event_log:
:2011-10-10-11:07:41> Smolt profile successfully saved
:2011-10-10-11:07:56> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-10-10-11:09:01  Kernel oops has not been sent due to Couldn't connect to server
:2011-10-10-11:09:01* (exited with 1)

kernel_tainted_long:
:Proprietary module has been loaded.
:Taint on warning.
Comment 1 Pavel Alexeev 2011-10-10 07:09:14 UTC 
Created attachment 527170 [details]
File: smolt_data
Comment 2 Josh Boyer 2011-10-24 15:35:11 UTC 
Are you still seeing this on the latest f16 kernel and can you recreate it without the wl driver loaded?
Comment 3 Pavel Alexeev 2011-10-29 21:08:25 UTC 
Yes, I still periodically seeing this on latest kernel. And I can't test without proprietary wl driver - it is only choose to work with it hardware for Broadcom WiFi.
Comment 4 Josh Boyer 2011-11-02 17:02:22 UTC 
(In reply to comment #3)
> Yes, I still periodically seeing this on latest kernel. And I can't test
> without proprietary wl driver - it is only choose to work with it hardware for
> Broadcom WiFi.

You could try to do some local actions that don't require network access and keep the module from being loaded.  The problem with proprietary drivers, as I'm sure you know, is that we can't really tell if it's causing issues like memory corruption.  Given the bug report is a corrupted list, it seems at least an initial attempt to recreate without that module is in order.
Comment 5 Pavel Alexeev 2011-11-02 17:08:53 UTC 
It is hardly reproduced, so remove that module and say not got that erorr 1 or two hour nothing say. So feel free to close the report if you found nothing usefull there.