From: Bernd Schubert <bs@q-leap.de>
To: linux-kernel@vger.kernel.org
Subject: frame unwinder patches
Date: Thu, 04 Sep 2008 18:46:52 +0200 [thread overview]
Message-ID: <g9p3du$n95$1@ger.gmane.org> (raw)
Hello,
up to 2.6.22 the -mm series had these nice frame unwinder patches,
which gave beautiful stack traces. Unfortunately these frame unwinder patches
seem to have been dropped :(
Anyone still maintaining updated patches?
Here is an example of a horrible stack trace, confusing my eyes
[ 855.504734] Call Trace:
[ 855.504734] [<ffffffff80495af2>] ? scsi_request_fn+0x252/0x370
[ 855.504734] [<ffffffff8058b068>] io_schedule+0x28/0x40
[ 855.504734] [<ffffffff8038b876>] get_request_wait+0x96/0x110
[ 855.504734] [<ffffffff80249d40>] ? autoremove_wake_function+0x0/0x40
[ 855.504734] [<ffffffff8038bca8>] blk_get_request+0x38/0x80
[ 855.504734] [<ffffffff804950a3>] scsi_execute+0x43/0x140
[ 855.504734] [<ffffffffa00250dc>] :scsi_transport_spi:spi_execute+0x7c/0xd0
[ 855.504734] [<ffffffff8038accb>] ? blk_put_request+0x4b/0x60
[ 855.504734] [<ffffffff8049515f>] ? scsi_execute+0xff/0x140
[ 855.504734] [<ffffffffa0025b86>] :scsi_transport_spi:spi_dv_device_echo_buffer+0x1c6/0x290
[ 855.504734] [<ffffffffa00349f0>] ? :mptbase:mpt_timer_expired+0x0/0x70
[ 855.504734] [<ffffffffa0024dc3>] :scsi_transport_spi:spi_dv_retrain+0x63/0x240
[ 855.504734] [<ffffffffa00259c0>] ? :scsi_transport_spi:spi_dv_device_echo_buffer+0x0/0x290
[ 855.504734] [<ffffffffa00255f7>] :scsi_transport_spi:spi_dv_device+0x3b7/0x720
[ 855.504734] [<ffffffffa005017b>] :mptspi:mptspi_dv_device+0x6b/0x1a0
[ 855.504734] [<ffffffffa00502ce>] ? :mptspi:mptspi_dv_renegotiate_work+0x1e/0x100
[ 855.504734] [<ffffffffa005038f>] :mptspi:mptspi_dv_renegotiate_work+0xdf/0x100
[ 855.504734] [<ffffffffa00502b0>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0x100
[ 855.504734] [<ffffffffa00502b0>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0x100
[ 855.504734] [<ffffffff80245b36>] run_workqueue+0x176/0x220
[ 855.504734] [<ffffffff80246786>] worker_thread+0xa6/0x110
[ 855.504734] [<ffffffff80249d40>] ? autoremove_wake_function+0x0/0x40
[ 855.504734] [<ffffffff802466e0>] ? worker_thread+0x0/0x110
[ 855.504734] [<ffffffff8024990d>] kthread+0x4d/0x80
[ 855.504734] [<ffffffff8020c5e8>] child_rip+0xa/0x12
[ 855.504734] [<ffffffff8020bcff>] ? restore_args+0x0/0x30
[ 855.504734] [<ffffffff802498c0>] ? kthread+0x0/0x80
[ 855.504734] [<ffffffff8020c5de>] ? child_rip+0x0/0x12
[ 855.504734]
Probably all the "?" lines shouldn't be printed.
Thanks,
Bernd
next reply other threads:[~2008-09-04 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 16:46 Bernd Schubert [this message]
2008-09-04 17:29 ` frame unwinder patches Arjan van de Ven
2008-09-05 9:19 ` Bernd Schubert
2008-09-05 13:33 ` Arjan van de Ven
2008-09-05 13:52 ` Bernd Schubert
2008-09-05 14:13 ` Arjan van de Ven
2008-09-05 14:48 ` Bernd Schubert
2008-09-05 14:57 ` Arjan van de Ven
2008-09-05 15:08 ` Andi Kleen
2008-09-04 19:13 ` Andi Kleen
2008-09-05 9:24 ` Bernd Schubert
2008-09-05 9:43 ` Andi Kleen
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='g9p3du$n95$1@ger.gmane.org' \
--to=bs@q-leap.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.