public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* MAX_STACK_TRACE_ENTRIES too low (2.6.31-rc2)
@ 2009-07-07 16:32 Dave Jones
  2009-07-08 17:17 ` Jörn Engel
  0 siblings, 1 reply; 2+ messages in thread
From: Dave Jones @ 2009-07-07 16:32 UTC (permalink / raw)
  To: Linux Kernel

I see this every time I boot.

	Dave

BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
Pid: 0, comm: swapper Not tainted 2.6.31-0.42.rc2.fc12.i686.PAE #1
Call Trace:
 [<c08277f3>] ? printk+0x22/0x37
 [<c04759b3>] save_trace+0x89/0xa3
 [<c0476410>] mark_lock+0xaf/0x1f6
 [<c0476c36>] ? check_usage_forwards+0x0/0x61
 [<c047755e>] __lock_acquire+0x301/0xb08
 [<c060bcc3>] ? get_hash_bucket+0x3a/0x55
 [<c0477e1c>] lock_acquire+0xb7/0xeb
 [<c060bcc3>] ? get_hash_bucket+0x3a/0x55
 [<c060bcc3>] ? get_hash_bucket+0x3a/0x55
 [<c082a537>] _spin_lock_irqsave+0x45/0x89
 [<c060bcc3>] ? get_hash_bucket+0x3a/0x55
 [<c060bcc3>] get_hash_bucket+0x3a/0x55
 [<c060d07d>] add_dma_entry+0x1f/0x4f
 [<c060d2fd>] debug_dma_map_sg+0xd0/0x136
 [<c06de03d>] ata_qc_issue+0x223/0x2c1
 [<c06e4be9>] __ata_scsi_queuecmd+0x16a/0x1c8
 [<c06c25a6>] ? scsi_done+0x0/0x32
 [<c06e4653>] ? ata_scsi_rw_xlat+0x0/0x20a
 [<c06e4d00>] ata_scsi_queuecmd+0x55/0x95
 [<c06c25a6>] ? scsi_done+0x0/0x32
 [<c06c284f>] scsi_dispatch_cmd+0x187/0x208
 [<c06c8641>] scsi_request_fn+0x33a/0x47d
 [<c05e8cb6>] __blk_run_queue+0x49/0x85
 [<c05e8db9>] blk_run_queue+0x2e/0x51
 [<c06c7b30>] scsi_run_queue+0x28d/0x32b
 [<c06c89b1>] scsi_next_command+0x3b/0x59
 [<c06c9415>] scsi_io_completion+0x1de/0x3c1
 [<c04768be>] ? trace_hardirqs_on+0x19/0x2c
 [<c06c912e>] ? scsi_device_unbusy+0x97/0xaf
 [<c06c258d>] scsi_finish_command+0xde/0xf7
 [<c06c9722>] scsi_softirq_done+0xf9/0x112
 [<c05eed28>] blk_done_softirq+0x74/0x93
 [<c0452508>] __do_softirq+0xc8/0x192
 [<c045261b>] do_softirq+0x49/0x7f
 [<c045276f>] irq_exit+0x48/0x8c
 [<c040c751>] do_IRQ+0x92/0xb7
 [<c040b035>] common_interrupt+0x35/0x3c
 [<c06704a9>] ? acpi_idle_enter_simple+0x11d/0x161
 [<c06701d2>] acpi_idle_enter_bm+0xd2/0x28c
 [<c076229a>] ? menu_select+0x48/0xc2
 [<c07613c3>] cpuidle_idle_call+0x73/0xbc
 [<c0409983>] cpu_idle+0xac/0xcd
 [<c0813ec2>] rest_init+0x66/0x79
 [<c0a86af8>] start_kernel+0x370/0x388
 [<c0a86090>] i386_start_kernel+0x7f/0x98


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: MAX_STACK_TRACE_ENTRIES too low (2.6.31-rc2)
  2009-07-07 16:32 MAX_STACK_TRACE_ENTRIES too low (2.6.31-rc2) Dave Jones
@ 2009-07-08 17:17 ` Jörn Engel
  0 siblings, 0 replies; 2+ messages in thread
From: Jörn Engel @ 2009-07-08 17:17 UTC (permalink / raw)
  To: Dave Jones; +Cc: Linux Kernel

On Tue, 7 July 2009 12:32:23 -0400, Dave Jones wrote:
> 
> I see this every time I boot.

Same here, with a slightly different backtrace.  Seems to go away
after quadrupling the value.  Not that I understand any of it.

BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
Pid: 264, comm: pdflush Not tainted 2.6.31-rc2 #4
Call Trace:
 [<ffffffff81016c7b>] ? save_stack_trace+0x2f/0x4d
 [<ffffffff8106c8b9>] save_trace+0x93/0x9b
 [<ffffffff8106c940>] add_lock_to_list+0x7f/0xc0
 [<ffffffff810706c9>] __lock_acquire+0x135c/0x16bb
 [<ffffffff8122877e>] ? scsi_setup_fs_cmnd+0xbc/0xc5
 [<ffffffff81227dc2>] ? scsi_request_fn+0x1cd/0x535
 [<ffffffff81070af7>] lock_acquire+0xcf/0xfb
 [<ffffffff81227dc2>] ? scsi_request_fn+0x1cd/0x535
 [<ffffffff813235bf>] _spin_lock+0x36/0x6b
 [<ffffffff81227dc2>] ? scsi_request_fn+0x1cd/0x535
 [<ffffffff81323428>] ? _spin_unlock+0x2b/0x2f
 [<ffffffff81227dc2>] scsi_request_fn+0x1cd/0x535
 [<ffffffff81173a63>] __generic_unplug_device+0x35/0x3a
 [<ffffffff8116deab>] elv_insert+0x24f/0x258
 [<ffffffff8116df53>] __elv_add_request+0x9f/0xa7
 [<ffffffff81174640>] __make_request+0x38c/0x40b
 [<ffffffff81171cb5>] generic_make_request+0x326/0x370
 [<ffffffff8106e3cd>] ? mark_held_locks+0x4d/0x6b
 [<ffffffff81171dca>] submit_bio+0xcb/0xd4
 [<ffffffff8110b87b>] submit_bh+0x106/0x12a
 [<ffffffff8110e54a>] __block_write_full_page+0x1fb/0x2f6
 [<ffffffff8110ce66>] ? end_buffer_async_write+0x0/0x184
 [<ffffffff811109a6>] ? blkdev_get_block+0x0/0x65
 [<ffffffff8110e719>] block_write_full_page_endio+0xd4/0xd8
 [<ffffffff8110e732>] block_write_full_page+0x15/0x17
 [<ffffffff811118c0>] blkdev_writepage+0x18/0x1a
 [<ffffffff810bc6de>] __writepage+0x1a/0x40
 [<ffffffff810bcff0>] write_cache_pages+0x262/0x3a8
 [<ffffffff810bc6c4>] ? __writepage+0x0/0x40
 [<ffffffff810bd15d>] generic_writepages+0x27/0x2d
 [<ffffffff810bd193>] do_writepages+0x30/0x40
 [<ffffffff81106951>] writeback_single_inode+0x189/0x395
 [<ffffffff81107025>] generic_sync_sb_inodes+0x2a6/0x44a
 [<ffffffff810bdfbe>] ? pdflush+0x0/0x239
 [<ffffffff811072f7>] writeback_inodes+0xa2/0xfa
 [<ffffffff810bd30d>] wb_kupdate+0xb3/0x129
 [<ffffffff810be113>] pdflush+0x155/0x239
 [<ffffffff810bd25a>] ? wb_kupdate+0x0/0x129
 [<ffffffff8105dc98>] kthread+0x8d/0x95
 [<ffffffff8100ce8a>] child_rip+0xa/0x20
 [<ffffffff8100c810>] ? restore_args+0x0/0x30
 [<ffffffff8105dc0b>] ? kthread+0x0/0x95
 [<ffffffff8100ce80>] ? child_rip+0x0/0x20


Jörn

-- 
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is easily forgotten.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-07-08 17:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-07 16:32 MAX_STACK_TRACE_ENTRIES too low (2.6.31-rc2) Dave Jones
2009-07-08 17:17 ` Jörn Engel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox