LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: "Cestonaro,
	Thilo (external)"  <Thilo.Cestonaro.external@fujitsu-siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how can I touch softlockup watchdog on all cpus?
Date: Thu, 22 Mar 2007 11:30:18 -0400	[thread overview]
Message-ID: <75b66ecd0703220830wdb4a612u86c80e71d4918cc4@mail.gmail.com> (raw)
In-Reply-To: <F7F9B0BE3E9BD449B110D0B1CEF6CAEF04FB710B@ABGEX01E.abg.fsc.net>

On 3/22/07, Cestonaro, Thilo (external)
<Thilo.Cestonaro.external@fujitsu-siemens.com> wrote:
> > You didn't explain _why_ you need to sleep for such a long time,
> > and as you didn't give a pointer to your code, there's not
> > much people can do to recommend changes other than "don't do that".
>
> The code which is executed between the local_irq_disable and enable,
> is just a function call into our companies bios (e.g. for updating itself)
> and the long time is just 15 sec. while the bios has full control and OS is halted.
> So I can't change anything at this point, but I need to fetch the watchdog,
> cause it is not so nice, if there is a big BUG output on console while the
> computer updates it's bios, very trustworthy isn't it :).

Just disable the softlockup watchdog.

Lee

  reply	other threads:[~2007-03-22 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 16:06 Cestonaro, Thilo (external)
2007-03-21 16:44 ` Dave Jones
2007-03-22  7:33   ` Cestonaro, Thilo (external)
2007-03-22 15:30     ` Lee Revell [this message]
2007-03-22 15:46       ` Cestonaro, Thilo (external)
2007-03-22 16:17         ` Lee Revell
2007-03-22 16:46           ` Cestonaro, Thilo (external)
2007-03-22 22:46             ` Jeremy Fitzhardinge
2007-03-23  1:16               ` Dave Jones
2007-03-23  1:48                 ` Jeremy Fitzhardinge
2007-03-21 16:10 Cestonaro, Thilo (external)

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=75b66ecd0703220830wdb4a612u86c80e71d4918cc4@mail.gmail.com \
    --to=rlrevell@joe-job.com \
    --cc=Thilo.Cestonaro.external@fujitsu-siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: how can I touch softlockup watchdog on all cpus?' \
    /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

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).