public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Kernel: which machine to choose?
Date: Tue, 08 Aug 2000 18:51:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205278@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205272@msgid-missing>

>>>>> On Tue, 08 Aug 2000 11:26:09 -0700, Uros Prestor <uros@turbolinux.com> said:

  Uros> Why is that?  Our kernels have been compiled with AzusA hacks
  Uros> enabled and we had no problems with our kernels running on
  Uros> BigSurs and Lions.

Any configuration with the string *HACKS* in it should be turned on
only for that machine.  You may get lucky at the moment and the
current AzusA hacks may not cause problems on Lion or BigSur, but I
won't guarantee that it will stay that way.  The AzusA hacks need to
be merged in cleanly with the existing source code so that #define can
go away (eventually, I don't expect this to happen over night).

  Uros> On another note, we are getting a lot more segfaults during
  Uros> builds lately.  The 0505 release which had the 2.3.99-pre6
  Uros> kernel was rock solid; after moving to 2.4.0 kernels the
  Uros> segfaults came back with a vengeance.  We did upgrade
  Uros> processors from A2 to A3 but I don't think this could be a
  Uros> culprit.  Any ideas on this?

Yes, we are seeing similar behavior.  I suspect the kernel's new
memcpy routine.  Can you try the old (and stupid) byte-by-byte copy
routine and let me know if that helps on your machines?

	--david


  parent reply	other threads:[~2000-08-08 18:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-08  7:14 [Linux-ia64] Kernel: which machine to choose? G\351raud Krawezik
2000-08-08 16:02 ` Broadfoot, KenX
2000-08-08 17:16 ` David Mosberger
2000-08-08 18:26 ` Uros Prestor
2000-08-08 18:51 ` David Mosberger [this message]
2000-08-08 18:55 ` Gerrit.Huizenga
2000-08-08 18:55 ` Jes Sorensen
2000-08-08 19:10 ` Jim Wilson
2000-08-08 19:15 ` Don Dugger
2000-08-08 19:36 ` Jes Sorensen
2000-08-08 19:43 ` Uros Prestor
2000-08-09 10:36 ` Gerrit.Huizenga
2000-08-09 16:37 ` Broadfoot, KenX

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=marc-linux-ia64-105590678205278@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox