public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Kellermann <max@duempel.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc[1-5]: soft lockups on Athlon64 X2
Date: Wed, 1 Mar 2006 23:23:05 +0100	[thread overview]
Message-ID: <20060301222305.GA12138@roonstrasse.net> (raw)
In-Reply-To: <20060301022235.51f47b42.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 616 bytes --]

On 2006/03/01 11:22, Andrew Morton <akpm@osdl.org> wrote:
> I guess it'd be useful to see where all that time is spent, if you have
> time.   Enable CONFIG_PROFILING, boot with `profile=1', do:
> 
> readprofile -r
> mount ...
> readprofile -n -v -m /boot/System.map | sort -n -k 3 | tail -40

Here it is.  As an explanation of the profile's scope, I have also
sent the shell script which reproduces the problem on my machine.

The script however is not 100% reliable; sometimes, the lockup just
won't occur.  Sounds like a timing problem to me.

btw. my other partitions are also reiserfs (but not encrypted).

Max


[-- Attachment #2: profile --]
[-- Type: text/plain, Size: 1719 bytes --]

     0 *unknown*
ffffffff81030f20 do_syslog                                     1   0.0009
ffffffff81041cc0 __queue_work                                  1   0.0078
ffffffff81054540 find_get_page                                 1   0.0104
ffffffff81062db0 __handle_mm_fault                             1   0.0004
ffffffff8107a450 __getblk                                      1   0.0017
ffffffff811fce50 xor_128                                       1   0.0312
ffffffff811fd140 cbc_process_decrypt                           1   0.0035
ffffffff8122ec60 strncpy_from_user                             1   0.0125
ffffffff812dc9b0 scsi_dispatch_cmd                             1   0.0014
ffffffff8101c120 do_gettimeoffset_pm                           2   0.0417
ffffffff8101eee1 enc128                                        2   0.0010
ffffffff810910b0 get_filesystem_list                           2   0.0139
ffffffff8122e990 memset                                        3   0.0156
ffffffff8105c4b0 __pagevec_lru_add_active                     12   0.0500
ffffffff8105c790 __pagevec_release                           108   1.6875
ffffffff8105c2c0 pagevec_lookup                              112   2.3333
ffffffff8105c6d0 lru_add_drain                               144   1.5000
ffffffff8105d100 invalidate_mapping_pages                    411   1.2844
ffffffff8105c2f0 release_pages                               551   1.2299
ffffffff810096e0 default_idle                               4194  37.4464
ffffffff810c9b50 reiserfs_dirty_inode                      23849 165.6181
ffffffff810545a0 find_get_pages                            24892 172.8611
0000000000000000 total                                     54291   0.0100

[-- Attachment #3: trigger_soft_lockup.sh --]
[-- Type: application/x-sh, Size: 515 bytes --]

      reply	other threads:[~2006-03-01 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 12:27 2.6.16-rc[1-5]: soft lockups on Athlon64 X2 Max Kellermann
2006-03-01  6:19 ` Andrew Morton
2006-03-01 10:07   ` Max Kellermann
2006-03-01 10:22     ` Andrew Morton
2006-03-01 22:23       ` Max Kellermann [this message]

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=20060301222305.GA12138@roonstrasse.net \
    --to=max@duempel.org \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox