From: Don Zickus <dzickus@redhat.com>
To: Mike Lykov <combr@yandex.ru>
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: Thu, 31 Jan 2013 09:46:27 -0500 [thread overview]
Message-ID: <20130131144627.GL98867@redhat.com> (raw)
In-Reply-To: <510A539E.7020105@yandex.ru>
On Thu, Jan 31, 2013 at 03:21:02PM +0400, Mike Lykov wrote:
>
> 30.01.2013 19:40, Don Zickus пишет:
> > I have never seen usage like 'kernel.watchdog_thresh=30'. Could you try
> > 'watchdog_thresh=30' instead?
>
> Ok. "kernel.watchdog_thresh=30" is a sysctl presentation, i mixed
> them wrongly.
>
> Your patch about cmd support for 'watchdog_thresh=30' working. I
> tested it: parameter applies and lzma -9 initramfs loading
> successfully.
> If I delete parameter from cmdline - same kernel not boot.
Good to know.
>
> > I also attached another patch as suggested by Andrew to add a
> > touch_softlockup_watchdog in the unlzma routine. Probably makes things
> > run a little slower. Compiled tested only.
>
> In my case (3.2.32) it cannot compile:
>
> LD arch/x86/boot/compressed/vmlinux
> arch/x86/boot/compressed/misc.o: In function `decompress_kernel':
> misc.c:(.text+0x993): undefined reference to `touch_softlockup_watchdog'
I think Andrew's suggestion is a better approach which is add the
touch_softlockup_watchdog. So I would have to see you .config file to
understand the compile warning.
Cheers,
Don
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Don Zickus <dzickus@redhat.com>
To: Mike Lykov <combr@yandex.ru>
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: Thu, 31 Jan 2013 09:46:27 -0500 [thread overview]
Message-ID: <20130131144627.GL98867@redhat.com> (raw)
In-Reply-To: <510A539E.7020105@yandex.ru>
On Thu, Jan 31, 2013 at 03:21:02PM +0400, Mike Lykov wrote:
>
> 30.01.2013 19:40, Don Zickus пишет:
> > I have never seen usage like 'kernel.watchdog_thresh=30'. Could you try
> > 'watchdog_thresh=30' instead?
>
> Ok. "kernel.watchdog_thresh=30" is a sysctl presentation, i mixed
> them wrongly.
>
> Your patch about cmd support for 'watchdog_thresh=30' working. I
> tested it: parameter applies and lzma -9 initramfs loading
> successfully.
> If I delete parameter from cmdline - same kernel not boot.
Good to know.
>
> > I also attached another patch as suggested by Andrew to add a
> > touch_softlockup_watchdog in the unlzma routine. Probably makes things
> > run a little slower. Compiled tested only.
>
> In my case (3.2.32) it cannot compile:
>
> LD arch/x86/boot/compressed/vmlinux
> arch/x86/boot/compressed/misc.o: In function `decompress_kernel':
> misc.c:(.text+0x993): undefined reference to `touch_softlockup_watchdog'
I think Andrew's suggestion is a better approach which is add the
touch_softlockup_watchdog. So I would have to see you .config file to
understand the compile warning.
Cheers,
Don
next prev parent reply other threads:[~2013-01-31 14:46 UTC|newest]
Thread overview: 20+ 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 9:39 ` Mike Lykov
2013-01-30 15:40 ` Don Zickus
2013-01-30 15:40 ` Don Zickus
2013-01-31 11:21 ` Mike Lykov
2013-01-31 11:21 ` Mike Lykov
2013-01-31 14:46 ` Don Zickus [this message]
2013-01-31 14:46 ` Don Zickus
2013-02-01 10:44 ` Mike Lykov
2013-02-01 15:59 ` Don Zickus
2013-02-01 15:59 ` Don Zickus
2013-02-01 16:43 ` Mike Lykov
2013-02-01 16:43 ` Mike Lykov
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=20130131144627.GL98867@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=combr@yandex.ru \
--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 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.