Bug 773170

Summary: [abrt] kernel: BUG: MAX_STACK_TRACE_ENTRIES too low!
Product: [Fedora] Fedora Reporter: William M. Quarles <walrus>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c8ab0c30e6244a463a88062f2a9df244ed44da05
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-11 14:02:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description William M. Quarles 2012-01-11 06:18:14 UTC 
abrt version: 2.0.3
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_quarlewm7-lv_root rd_LVM_LV=vg_quarlewm7/lv_root rd_LVM_LV=vg_quarlewm7/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        This happened after unplugging a USB drive which the system kept refusing to "remove safely."
component:      kernel
kernel:         undefined
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: MAX_STACK_TRACE_ENTRIES too low!
time:           Wed Jan 11 01:15:47 2012

backtrace:
:BUG: MAX_STACK_TRACE_ENTRIES too low!
:turning off the locking correctness validator.
:Pid: 42, comm: khubd Not tainted 3.0.14-1.rt31.1.fc15.ccrma.x86_64.rt #1
:Call Trace:
: [<ffffffff8108c442>] save_trace+0x9f/0xa5
: [<ffffffff8108de48>] mark_lock+0x99/0x220
: [<ffffffff8108e37b>] __lock_acquire+0x3ac/0xcf7
: [<ffffffff8108f499>] ? mark_held_locks+0x4b/0x6d
: [<ffffffff8108f714>] ? debug_check_no_locks_freed+0x11b/0x130
: [<ffffffff8108f5c6>] ? trace_hardirqs_on_caller+0x10b/0x12f
: [<ffffffff811a0c81>] ? sysfs_addrm_finish+0x36/0x55
: [<ffffffff8108f1bc>] lock_acquire+0xf3/0x13e
: [<ffffffff811a0c81>] ? sysfs_addrm_finish+0x36/0x55
: [<ffffffff811a0573>] sysfs_deactivate+0x97/0xec
: [<ffffffff811a0c81>] ? sysfs_addrm_finish+0x36/0x55
: [<ffffffff8108dddc>] ? mark_lock+0x2d/0x220
: [<ffffffff8100f9f5>] ? paravirt_read_tsc+0x9/0xd
: [<ffffffff8100f9f5>] ? paravirt_read_tsc+0x9/0xd
: [<ffffffff811a0c81>] sysfs_addrm_finish+0x36/0x55
: [<ffffffff8119f63f>] sysfs_hash_and_remove+0x59/0x7a
: [<ffffffff811a0095>] sysfs_remove_file_from_group+0x3c/0x49
: [<ffffffff8137c7da>] usb_remove_sysfs_dev_files+0x3f/0x53
: [<ffffffff8136d91b>] usb_bus_notify+0x5c/0x73
: [<ffffffff814f4e4d>] notifier_call_chain+0x84/0xbb
: [<ffffffff81095264>] ? rt_down_read+0x10/0x12
: [<ffffffff8107f99e>] __blocking_notifier_call_chain+0x67/0x84
: [<ffffffff8107f9cf>] blocking_notifier_call_chain+0x14/0x16
: [<ffffffff813160ed>] device_del+0x39/0x184
: [<ffffffff8137005a>] usb_disconnect+0x115/0x166
: [<ffffffff8137220d>] hub_thread+0x843/0x12bb
: [<ffffffff814f1e3e>] ? _raw_spin_unlock_irq+0x4c/0x59
: [<ffffffff8104000a>] ? __driver_rfc4106_decrypt+0xbb/0x2bc
: [<ffffffff8107a31d>] ? __init_waitqueue_head+0x7c/0x7c
: [<ffffffff813719ca>] ? usb_remote_wakeup+0x64/0x64
: [<ffffffff81079a3a>] kthread+0x99/0xa1
: [<ffffffff8108b9e4>] ? trace_hardirqs_off+0xd/0xf
: [<ffffffff8108f5f7>] ? trace_hardirqs_on+0xd/0xf
: [<ffffffff814f8f24>] kernel_thread_helper+0x4/0x10
: [<ffffffff814f21d8>] ? retint_restore_args+0x13/0x13
: [<ffffffff810799a1>] ? __init_kthread_worker+0x8c/0x8c
: [<ffffffff814f8f20>] ? gs_change+0x13/0x13
Comment 1 Josh Boyer 2012-01-11 14:02:15 UTC 
This seems to have been hit with a hand build -rt kernel.  Fedora doesn't build
or support that, so you'll need to take this up with upstream.