[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4A36A7ED.2050702@grupopie.com>
Date: Mon, 15 Jun 2009 20:58:37 +0100
From: Rui Santos <rsantos@...popie.com>
To: Wim Van Sebroeck <wim@...ana.be>
CC: Stephen Clark <sclark46@...thlink.net>,
Denys Fedoryschenko <denys@...p.net.lb>,
Johannes Dewender <arch@...nyjd.net>,
"Rafael J. Wysocki" <rjw@...k.pl>, Frans Pop <elendil@...net.nl>,
Rutger Nijlunsing <bugzilla.kernel@....tmfweb.nl>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Andriy Gapon <avg@...b.net.ua>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [WATCHDOG] iTCO_wdt.c - ICH9 reboot issue - testing wanted
Wim Van Sebroeck wrote:
> Hi Rui,
>
Hi Wim,
>
>> With your patch, the Intel DG35EC board will not allow my distribution
>> reboot or halt the machine. In order to circumvent that problem, I've
>> made a few addition to your previous patch witch allows the restore of
>> the changed Bit 0 to it's previous value if the module is unloaded.
>> My only doubt is if it should be done every time the gbl_smi_en is zero,
>> or in conjunction with nowayout when the value also equals zero. This
>> patch has what I described and a commented gbl_smi_en only.
>>
>
> Forget the previous patch. I don't like having this hack in the main iTCO_wdt code.
> So I added it to the iTCO_vendor_support code with the necessary warnings.
> Can you test this (please note that the iTCO_vendor_support module needs to be
> loaded with the vendorsupport=911 module parameter).
>
It's working like a charm. Also, the Bit 0 is changed to its original
value, so all reboots work.
I've tested on 2.6.30 and 2.6.27 ( with a few mods... ).
> Thanks in advance,
>
Thank you,
> Wim.
>
Rui
--
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