[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75b66ecd0703220830wdb4a612u86c80e71d4918cc4@mail.gmail.com>
Date: Thu, 22 Mar 2007 11:30:18 -0400
From: "Lee Revell" <rlrevell@...-job.com>
To: "Cestonaro, Thilo (external)"
<Thilo.Cestonaro.external@...itsu-siemens.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: how can I touch softlockup watchdog on all cpus?
On 3/22/07, Cestonaro, Thilo (external)
<Thilo.Cestonaro.external@...itsu-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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists