From: Gerrit.Huizenga@us.ibm.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Kernel: which machine to choose?
Date: Tue, 08 Aug 2000 18:55:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205279@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205272@msgid-missing>
I noted recently that I couldn't build a kernel on the Lion when
rlogin'd to the machine, but at the console I seem to have no
problem.
Could the problems be a deadlock or other problem in the test1/test4
linux tcp code?
I've also noted that when compiling kernels with:
$ gcc -v
Reading specs from /usr/lib/gcc-lib/ia64-redhat-linux/2.9-ia64-000216-final/specs
gcc version 2.9-ia64-000216-final
I get 40 MB kernels, although the size of text/data/bss/etc. are about the
same as the 7-8 MB kernels shipped with the RedHat distro on my machine.
And, trying to get the newer compiler to work on the RedHat distro has
been a little problematic. I'm trying to bootstrap my way to a newer
kernel on the Lion (newer that ~test1) and running into problems where
the Dig kernel won't boot.
Procs are all A3 in the Lions.
gerrit
> David Mosberger wrote:
>
> > I wouldn't recommendn turning on AzusA hacks unless you have an AzusA
> > machine.
>
> Why is that? Our kernels have been compiled with AzusA hacks enabled and we had no problems
> with our kernels running on BigSurs and Lions.
>
> On another note, we are getting a lot more segfaults during builds lately. The 0505 release
> which had the 2.3.99-pre6 kernel was rock solid; after moving to 2.4.0 kernels the segfaults
> came back with a vengeance. We did upgrade processors from A2 to A3 but I don't think this
> could be a culprit. Any ideas on this?
>
> Thanks,
> Uros
>
> --
> Uros Prestor
> uros@turbolinux.com
>
>
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
next prev parent reply other threads:[~2000-08-08 18:55 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
2000-08-08 18:55 ` Gerrit.Huizenga [this message]
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-105590678205279@msgid-missing \
--to=gerrit.huizenga@us.ibm.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