From: Andrew Morton <akpm@linux-foundation.org>
To: Hussam Al-Tayeb <ht990332@gmail.com>
Cc: linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 35662] New: softlockup with kernel 2.6.39
Date: Mon, 23 May 2011 16:48:04 -0700 [thread overview]
Message-ID: <20110523164804.572cecfd.akpm@linux-foundation.org> (raw)
In-Reply-To: <201105240241.52307.hussam@visp.net.lb>
On Tue, 24 May 2011 02:41:51 +0300
Hussam Al-Tayeb <ht990332@gmail.com> wrote:
> YEs,
> lsmod | grep dm_crypt
> dm_crypt 12887 2
> dm_mod 55464 5 dm_crypt
>
> Still no lockups since downgrading to 2.6.38.6 which was a few hours before I
> filed the bug report.
> I could reinstall 2.6.39 if there is anything you would like me to test.
Thanks.
CONFIG_PROVE_LOCKING=y would be useful, if you didn't already have it
set.
Also after the kernel has failed, kill everything off and do a `ps aux'
and look for any other tasks which are stuck in "D" state. Backtraces
for any such processes can be obtained with "echo w >
/proc/sysrq-trigger".
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-23 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-35662-10286@https.bugzilla.kernel.org/>
2011-05-23 23:22 ` [Bugme-new] [Bug 35662] New: softlockup with kernel 2.6.39 Andrew Morton
2011-05-23 23:41 ` Hussam Al-Tayeb
2011-05-23 23:48 ` Andrew Morton [this message]
2011-05-24 7:01 ` Hussam Al-Tayeb
2011-05-26 5:03 ` Hussam Al-Tayeb
2011-05-26 16:33 ` Hussam Al-Tayeb
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=20110523164804.572cecfd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=ht990332@gmail.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).