public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jim Gifford" <maillist@jg555.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>,
	"Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
Date: Sat, 5 Jul 2003 13:28:21 -0700	[thread overview]
Message-ID: <1aa601c34333$fa82e020$3400a8c0@W2RZ8L4S02> (raw)
In-Reply-To: 2268760000.1057436124@aslan.scsiguy.com

I think the problem is elsewhere, please take a look at this message I sent
earlier.

http://marc.theaimsgroup.com/?l=linux-kernel&m=105742280413809&w=2

----- Original Message ----- 
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "Jim Gifford" <maillist@jg555.com>; "Roberto Slepetys Ferreira"
<slepetys@homeworks.com.br>; <linux-kernel@vger.kernel.org>
Sent: Saturday, July 05, 2003 1:15 PM
Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble


> > Justin, I just tried to enable the nmi watch dog. It doesn't seem to
work on
> > my system I tried both
> >
> > append="nmi_watchdog=1"
> > and
> > append="nmi_watchdog=2"
>
> Is the watchdog enabled in your kernel?  The command line only works
> if you have compiled in support for the watchdog.
>
> --
> Justin
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2003-07-05 20:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 14:44 Probably 2.4 kernel or AIC7xxx module trouble Roberto Slepetys Ferreira
2003-07-02 15:14 ` Justin T. Gibbs
2003-07-02 21:00   ` Roberto Slepetys Ferreira
2003-07-03 18:29     ` Roberto Slepetys Ferreira
     [not found]       ` <13e101c3419d$f62f9410$3400a8c0@W2RZ8L4S02>
2003-07-03 20:15         ` Roberto Slepetys Ferreira
2003-07-03 21:20           ` Justin T. Gibbs
2003-07-03 23:04             ` Jim Gifford
2003-07-05 20:15               ` Justin T. Gibbs
2003-07-05 20:28                 ` Jim Gifford [this message]
2003-07-03 22:49       ` Matthias Andree
2003-07-03 23:09         ` Jim Gifford
     [not found] <4R5X.8bo.19@gated-at.bofh.it>
     [not found] ` <4Rzh.h8.25@gated-at.bofh.it>
     [not found]   ` <4WSg.5H7.21@gated-at.bofh.it>
     [not found]     ` <5h0y.5ht.25@gated-at.bofh.it>
     [not found]       ` <5iIR.7Cp.11@gated-at.bofh.it>
     [not found]         ` <5iIQ.7Cp.9@gated-at.bofh.it>
     [not found]           ` <5jOA.14o.9@gated-at.bofh.it>
     [not found]             ` <5lnu.2l7.13@gated-at.bofh.it>
2003-07-04 17:36               ` Roberto Slepetys Ferreira
2003-07-05 20:27                 ` Justin T. Gibbs
     [not found]       ` <5ldB.2cK.1@gated-at.bofh.it>
2003-07-04 17:38         ` Roberto Slepetys Ferreira

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='1aa601c34333$fa82e020$3400a8c0@W2RZ8L4S02' \
    --to=maillist@jg555.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slepetys@homeworks.com.br \
    /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