From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 17361] Random kmemcheck errors and kernel freeze on 2.6.36-rc*
Date: Wed, 20 Oct 2010 20:10:39 GMT [thread overview]
Message-ID: <201010202010.o9KKAdL3014017@demeter2.kernel.org> (raw)
In-Reply-To: <bug-17361-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=17361
Christian Casteyde <casteyde.christian@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #20 from Christian Casteyde <casteyde.christian@free.fr> 2010-10-20 20:10:37 ---
Hello
My bisection was obviously false, sorry.
It took me some time, but I've finally understood why my bisection failed, and
what was happening.
The problem is that with kmemcheck, the kernel boots so slowly (except if there
is a warning at boot in swapper, as it occured in several revision pre rc1),
that the hard and soft lockup detection mechanism was triggering (often in udev
or hal or ldconfig or other slow commands). Moreover, it triggered sometimes at
a place the kernel cannot cope with it, and crashes.
Before bisecting, I took a fresh 2.6.35 .config file and reactivated the
debugging options, but I fogot the lockup detector. So I couldn't see the
errors anymore. Nevertheless, I checked other warnings that used to occur
before -rc1, and that were fixed later. As I was looking for a range between
2.6.35 and rc1, I got false results on already fixed bugs.
Finally, I do not have any problem anymore with 2.6.36-rc8. Except that the
lockup timeout is either too low for my computers, or crashes the kernel
sometimes whent it triggers. But that's not critical.
I'm closing the bug.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-10-20 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 20:00 [Bug 17361] New: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
2010-09-07 22:27 ` bugzilla-daemon
2010-09-14 5:48 ` bugzilla-daemon
2010-09-14 5:51 ` bugzilla-daemon
2010-09-14 18:08 ` bugzilla-daemon
2010-09-21 17:19 ` bugzilla-daemon
2010-09-22 17:48 ` bugzilla-daemon
2010-09-22 17:51 ` bugzilla-daemon
2010-09-22 17:53 ` bugzilla-daemon
2010-09-22 17:56 ` bugzilla-daemon
2010-09-22 17:58 ` bugzilla-daemon
2010-09-22 18:01 ` bugzilla-daemon
2010-09-22 18:11 ` bugzilla-daemon
2010-09-22 18:13 ` bugzilla-daemon
2010-09-27 19:26 ` bugzilla-daemon
2010-10-02 16:42 ` bugzilla-daemon
2010-10-11 20:43 ` Andreas Dilger
2010-10-04 18:48 ` bugzilla-daemon
2010-10-04 18:51 ` [Bug 17361] Random kmemcheck errors and kernel freeze on 2.6.36-rc* bugzilla-daemon
2010-10-10 19:19 ` bugzilla-daemon
2010-10-10 19:20 ` bugzilla-daemon
2010-10-10 19:22 ` bugzilla-daemon
2010-10-10 19:38 ` bugzilla-daemon
2010-10-20 20:10 ` bugzilla-daemon [this message]
2010-10-20 20:38 ` bugzilla-daemon
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=201010202010.o9KKAdL3014017@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).