The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Patch Devil <lkpatches@paypc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] i8xx_tco - Add SuperMicro ICH[56] Pentium 4 watchdog support
Date: Sat, 17 Dec 2005 12:37:29 -0800	[thread overview]
Message-ID: <20051217123729.498c7919.akpm@osdl.org> (raw)
In-Reply-To: <1134600697.43a0a1f9de94e@www.paypc.com>

Patch Devil <lkpatches@paypc.com> wrote:
>
> Hello friends of LK:
> 
> It seems that SuperMicro P4-based motherboards DO actually have working
> watchdog hardware (be sure jumpers *and* BIOS settings are configured
> appropriately), however the setup of their internal ports and registers
> deviate from canonical Intel specification.
> 
> Because it seems impossible/difficult to do a proper auto-detection for these
> deviations, I've added a module_param to the TCO module to provide minor
> changes to the existing i8xx TCO code.  I've given it some testing on i845
> (Northwood P4) and E7520 (Nacona/EM64T SMP-Xeon) and it does indeed activate
> watchdog (reset/reboot) functionality and provide WDT resets to keep the
> system up.
> 
> SuperMicro had provided me with some documentation for their Pentium III
> motherboards, however I was not able to ever get it functioning on my SSE370+,
> however I've incorporated the logic as documented as a bit of a "bookmark" for
> future implementors who MAY be lucky to have P3 SuperMicros with working WDT
> functionality.
> 
> My patch activates the watchdog even if the BIOS setting disables it, however
> it cannot override the jumper on the motherboard.
> 
> Naturally, users should do two-way testing before deploying this on production
> hardware: 1) Verify that the watchdog IS actually able to reset the machine --
> so you'll need to deliberately lockup or kill the WDT refresh and make sure
> the machine reboots, and then 2) Verify that the watchdog timer is being
> properly reset.
> 
> This patch was made against 2.6.13.2, and I provide some background detail in
> the patched source.
> 
> I've had this working in production for a couple of months now without any
> issues.  Of course, these very reliable systems never lockup (typical uptimes
> are over 300-400 days, and are rebooted for kernel upgrades only).  But hey, I
> was a bit annoyed that an advertised feature wasn't available to me.
> 
> Cheers,
> Robert
> 

Thanks for doing this work.

Unfortunately we shouldn't be merging nontrivial patches from new
contributors with names like "Robert the Patch Devil" ;)

Please review Section 11 of Documentation/SubmittingPatches.txt and, if you
find the terms there to be acceptable, resend the patch with a
Signed-off-by: and your real name, thanks.


      reply	other threads:[~2005-12-17 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 22:51 [PATCH 2.6] i8xx_tco - Add SuperMicro ICH[56] Pentium 4 watchdog support Patch Devil
2005-12-17 20:37 ` Andrew Morton [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=20051217123729.498c7919.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkpatches@paypc.com \
    /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