v2.6.25: WARNING: at kernel/lockdep.c:2437 __lock_acquire+0xc69/0xfa0()

[Vegard Nossum]

Hi,

This appears in clean v2.6.25:

------------[ cut here ]------------
WARNING: at kernel/lockdep.c:2437 __lock_acquire+0xc69/0xfa0()
Pid: 1002, comm: scsi_eh_4 Not tainted 2.6.25 #379
 [<c011bb5c>] warn_on_slowpath+0x3c/0x50
 [<c013b0f9>] ? __lock_acquire+0x219/0xfa0
 [<c013b0f9>] ? __lock_acquire+0x219/0xfa0
 [<c012c2c8>] ? __kernel_text_address+0x8/0x20
 [<c0104fce>] ? dump_trace+0xce/0x120
 [<c010a56c>] ? save_stack_trace+0x1c/0x40
 [<c0138659>] ? save_trace+0x39/0xa0
 [<c013a3d1>] ? mark_lock+0x61/0x540
 [<c013bb49>] __lock_acquire+0xc69/0xfa0
 [<c012b46a>] ? __cancel_work_timer+0x5a/0x140
 [<c01082ac>] ? native_sched_clock+0x5c/0xb0
 [<c013beee>] lock_acquire+0x6e/0x90
 [<c02a8e23>] ? ata_scsi_error+0x33/0x6a0
 [<c02e4946>] _spin_lock_irqsave+0x26/0x60
 [<c02a8e23>] ? ata_scsi_error+0x33/0x6a0
 [<c02a4ee0>] ? ata_bmdma_error_handler+0x0/0x50
 [<c02a8e23>] ata_scsi_error+0x33/0x6a0
 [<c02e249a>] ? schedule+0x27a/0x410
 [<c0256dd1>] ? __scsi_iterate_devices+0x51/0x70
 [<c025c681>] ? scsi_run_host_queues+0x21/0x30
 [<c025ae5e>] scsi_error_handler+0x9e/0x4e0
 [<c02e249a>] ? schedule+0x27a/0x410
 [<c025adc0>] ? scsi_error_handler+0x0/0x4e0
 [<c012dd86>] kthread+0x36/0x60
 [<c012dd50>] ? kthread+0x0/0x60
 [<c0104c27>] kernel_thread_helper+0x7/0x10
 =======================
---[ end trace 5e5d737e76fd4940 ]---

Full log and config:

http://folk.uio.no/vegardno/linux/log-20080420.txt
http://folk.uio.no/vegardno/linux/config-20080420.txt

(The bootup is from qemu for the ease of harvesting the log -- but it
happens on real hardware too!)


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/