From: Jorge Nerin <comandante@zaralinux.com>
To: Scott Conway <misassistant@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 kernel halting...
Date: Tue, 02 Jan 2001 14:43:45 +0100 [thread overview]
Message-ID: <3A51DB11.350E663@zaralinux.com> (raw)
In-Reply-To: <20010101180517.27929.qmail@web1103.mail.yahoo.com>
Scott Conway wrote:
>
> Hi, I'm having problems getting anything from
> 2.4.0-test12 onward to get past the IDE detectin phase
> of bootup, and not even 2.4.0-prerelease will work,
> either. At the bottom of this is the output of dmesg,
> on my current kernel (2.4.0-test11), with the spot
> where test12+ freezes indicated. btw...does anyone
> out there know how to capture output on a bad kernel;
> since the one I'm having trouble with never gets far
> enough for me to check for an oops with an externel
> program? You can locate the point where I get the
> freeze by the whole line of '*' to show where it locks
> up. Also, please forward any replies to my e-mail
> since I don't subscribe to linux-kernel due to
> excessive traffic on my end. Thanks, and below is
> dmesg output...
>
> ------------------------Cut
> Here-----------------------
> Linux version 2.4.0-test11-ac4 (root@ummagumma) (gcc
> version 2.95.3 19991030 (prerelease)) #1 Wed Dec 27
> 03:15:22 EST 2000
Try to compile with kgcc or egcs, gcc 2.95 is not a recommended
compiler, as it's know to miscompile somethings.
Search Makefile for HOSTCC and CC and chage it if needed.
--
Jorge Nerin
<comandante@zaralinux.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-03 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 18:05 2.4 kernel halting Scott Conway
2001-01-02 13:43 ` Jorge Nerin [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=3A51DB11.350E663@zaralinux.com \
--to=comandante@zaralinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=misassistant@yahoo.com \
/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.