From: Mike Lykov <combr@yandex.ru>
To: Don Zickus <dzickus@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
kirill@shutemov.name
Subject: Re: [BUG?] false positive in soft lockup detector while unlzma initramfs on slow cpu
Date: Fri, 01 Feb 2013 20:43:02 +0400 [thread overview]
Message-ID: <510BF096.7060705@yandex.ru> (raw)
In-Reply-To: <20130201155908.GR98867@redhat.com>
01.02.2013 19:59, Don Zickus пишет:
> Hmm, that seems to make sense. I was expecting that problem to pop up on
> my end but didn't see. I just asusmed the boot code didn't use that
> decompressor.
Can you accumulate all our discussion and create one right-coded,
kernelcode-styled patch?
> Though I am not sure why that is leading to your other PATA problems
> below. Did you have similar problems when you used other decompression
> levels?
In past - no. But I not test this last kernel variant with other level.
> I am not sure how to explain the differences.
I think this is similar as decompress:
Kernel stop and wait next try in "default_idle()" for 20-30 sec, and in
this moment softlockup detector panics ;)
But without patch for touch_softlockup_watchdog in
decompress_unlzma+misc.c it works (try, fail, pause, try, fail, go on).
--
Mike
Sapienti sat.
prev parent reply other threads:[~2013-02-01 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 13:42 [BUG?] false positive in soft lockup detector while unlzma initramfs on slow cpu Mike Lykov
2013-01-29 15:33 ` Don Zickus
2013-01-29 17:18 ` anish kumar
2013-01-30 15:51 ` Don Zickus
2013-01-30 15:59 ` anish kumar
2013-01-29 23:59 ` Andrew Morton
2013-01-31 11:18 ` Ingo Molnar
2013-01-30 9:39 ` Mike Lykov
2013-01-30 15:40 ` Don Zickus
2013-01-31 11:21 ` Mike Lykov
2013-01-31 14:46 ` Don Zickus
2013-02-01 10:44 ` Mike Lykov
2013-02-01 15:59 ` Don Zickus
2013-02-01 16:43 ` Mike Lykov [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=510BF096.7060705@yandex.ru \
--to=combr@yandex.ru \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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