From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Tejun Heo" <htejun@gmail.com>, "Jeff Garzik" <jgarzik@pobox.com>,
"Ingo Molnar" <mingo@elte.hu>
Subject: v2.6.25: WARNING: at kernel/lockdep.c:2437 __lock_acquire+0xc69/0xfa0()
Date: Sun, 20 Apr 2008 12:29:52 +0200 [thread overview]
Message-ID: <19f34abd0804200329j3308b081vc0732c3ec5c0b721@mail.gmail.com> (raw)
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
next reply other threads:[~2008-04-20 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 10:29 Vegard Nossum [this message]
2008-04-21 12:48 ` Peter Zijlstra
2008-04-24 3:01 ` Tejun Heo
2009-04-11 16:10 ` Jeff Garzik
2009-04-12 18:11 ` Tejun Heo
2009-04-14 3:59 ` [PATCH #upstream-fixes] pata_legacy: fix no device fail path Tejun Heo
2009-04-16 19:23 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0804200329j3308b081vc0732c3ec5c0b721@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®