From: Mark Hounschell <markh@compro.net>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Booting problems with dual p4 on i860 chipset with 2.4 and 2.5
Date: Fri, 20 Sep 2002 11:16:46 -0400 [thread overview]
Message-ID: <3D8B3BDE.11C7E177@compro.net> (raw)
In-Reply-To: 20020920190537.A11244@namesys.com
Oleg Drokin wrote:
>
> Hello!
>
> We have a problem with newly acquired dual p4 xeon (2.2Ghz, heperthreading
> blah blah) box built on i860 chipset (SuperMicro P4DC6+ motherboard).
> Whenever we try to boot 2.4 or 2,5 kernel in there it decompresses
> the kernel itself, states 'Ok, booting the kernel' and hangs.
> We already tested these versions 2.4.15, 2.4.20-pre7, 2.4.18 from SuSE 8.0,
> 2.4.18 from RedHat 7.3 and latest RedHat beta (null), 2.5.36 (latest bk
> snapshot as of now).
> I remember I saw something like we experience now being reported on lkml
> awhile back and 2.2 was able to boot in that case, so we tried 2.2.21
> and it worked to our surprise.
> We tried to install latest BIOS version available from MB manufacturer but
> that did not help.
> Unfortunatelly we are no longer able to find that mail with similar problems,
> so may be someone have any ideas on what to do to get 2.4 (and 2.5)
> up and runing on such a box?
>
> Thank you.
>
I've got 6 of them here running SuSE 8.0. Hyperthreading was disabled in the
bios when Suse-8.0 was
installed and 3 of the 6 had the clock speed set at it's lowest setting when
they arrived but other than that there were no problems. HT was enabled after
the install of SuSE-8.0 and no problems there either. ?????
Mark
next prev parent reply other threads:[~2002-09-20 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 15:05 Booting problems with dual p4 on i860 chipset with 2.4 and 2.5 Oleg Drokin
2002-09-20 15:16 ` Mark Hounschell [this message]
2002-09-20 15:31 ` Alexander Lyamin
2002-09-20 15:39 ` [P4DC6+] " Alexander Lyamin
2002-09-20 17:07 ` Mark Hounschell
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=3D8B3BDE.11C7E177@compro.net \
--to=markh@compro.net \
--cc=green@namesys.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).