From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Dave Mehler <dmehler26@woh.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 kernel hangs system
Date: Tue, 22 Apr 2003 17:00:23 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0304221649050.17809@chaos> (raw)
In-Reply-To: <000501c3090c$71683c60$0200a8c0@satellite>
On Tue, 22 Apr 2003, Dave Mehler wrote:
> Hello,
> Ok, i've got a 2.5.68 kernel compilation that when i try to boot it it
> hangs the system. It gives me hex codes after it loads the kernel or if i
> have it load an initrd, it loads that then gives hex codes and stops.
> I've got output from lspci -v and my config file at the following url:
> www.davemehler.net
> Suggestions are desperately needed.
> If there's missing information that i should post please let me know and i
> will post it.
> Thanks.
> Dave.
>
First, I don't understand how as you say, "suggestions are
desperately needed" on a developmental kernel. These things are
not known to work on all configurations and some information like
"It gives me hex codes..." is worthless. Please write down
these "hex-codes" and, after booting a version the works, run them
through ksymoops. If you don't know what that is:
The latest version can be found in
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops together
with patches to other utilities in order to give more accurate Oops
debugging.
FYI, after you run the text through ksymoops, you may find that it
occurs in a module that you really don't need to load at boot time.
Just remove that from initrd and try again.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-04-22 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 20:19 Dave Mehler
2003-04-22 20:55 ` Michael Buesch
2003-04-22 21:00 ` Richard B. Johnson [this message]
2003-04-22 23:11 ` Felipe Alfaro Solana
2003-04-23 1:29 ` Murray J. Root
2003-04-23 1:55 ` Randy.Dunlap
2003-04-23 2:31 ` Murray J. Root
2003-04-23 2:17 ` Brett
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=Pine.LNX.4.53.0304221649050.17809@chaos \
--to=root@chaos.analogic.com \
--cc=dmehler26@woh.rr.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
all inboxes | Powered by JetHome®