From: Andrew Morton <akpm@digeo.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: linux-mm@kvack.org
Subject: Re: 2.5.44-mm2 compile error using gcc 3.2 (gcc 2.96 works fine).
Date: Mon, 21 Oct 2002 19:24:52 -0700 [thread overview]
Message-ID: <3DB4B6F4.9488F283@digeo.com> (raw)
In-Reply-To: 1035252853.9472.45.camel@localhost.localdomain
Steven Cole wrote:
>
> > Are you using "nmi_watchdog=1"?
> >
>
> Nope. My understanding is that is only applicable for SMP systems, but
> I can add that to the lilo.conf append line if it would do any good on
> this troublesome UP box.
It should still work OK if you have the IO-APIC enabled.
Running an SMP kernel on UP sometimes will catch deadlocks
which a UP build would miss. But in this case, it might
make it go away - your SMP box is unaffected.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-10-22 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 18:40 2.5.44-mm2 compile error using gcc 3.2 (gcc 2.96 works fine) Steven Cole
2002-10-21 21:05 ` Andrew Morton
2002-10-21 23:03 ` Steven Cole
2002-10-21 23:21 ` Andrew Morton
2002-10-22 2:14 ` Steven Cole
2002-10-22 2:24 ` 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=3DB4B6F4.9488F283@digeo.com \
--to=akpm@digeo.com \
--cc=elenstev@mesatop.com \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.