From: Seth Goldberg <bergsoft@home.com>
To: Gordon Sadler <gbsadler1@lcisp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.5pre1 will not boot
Date: Fri, 04 May 2001 00:43:22 -0700 [thread overview]
Message-ID: <3AF25D9A.982B040B@home.com> (raw)
In-Reply-To: <20010504021243.A8621@debian-home.lcisp.com>
Hi,
What hardware are you running?
--seth
>
> Please CC any replies.
> Please refer to my previous post 'PROBLEM: 2.4.4 oops, will not boot'
> for complete machine details/configuration.
>
> I'm still working on different 2.4 kernels trying to get just one to
> boot normally. Currently I've removed all modules and built everything
> into the kernel, that seems to help a 'little'.
>
> Just tried 2.4.5pre1...
>
> 1st boot. Got as far as "Checking all file systems...", which is:
> fsck -C -R -A -a (Debian Sid). This was followed by numerous (>50)
> lines of the form:
> memory.c: 83 (something I couldn't read fast enough)
> followed by the machine auto-rebooting.
>
> 2nd boot. Trying to duplicate to read above memory.c ...
> Led to the attached oops.txt > ksym.out contained in the tarball.
>
> 3rd boot. I was actually able to login... for about 5 mins. I attempted
> to run the above oops through ksymoops while kernel was running. It
> appeared to work, just then machine froze, required my using reset
> button on case. This led to booting back into 2.2.19 with duplicate
> inodes, manual run of fsck.
>
> 4th boot. Led to the attached oops2.txt > ksym2.out which was just the
> first oops of approx. 20 or more before machine froze. All the
> remaining oops (that I looked at) were of the same type/address.
>
> I really hope someone finds this, Andrew Morton(sp?) was looking into my
> 2.4.4 oops, says my slab is being corrupted? Would be kind of
> interesting to find out it is hardware related. This m/b and CPU are
> brand new, can still take them back -)
>
> Thanks for your time.
>
> Gordon Sadler
>
>
>
>
> Name: 2.4.5pre1.oops.tar.gz
> 2.4.5pre1.oops.tar.gz Type: Unix Tape Archive (application/x-tar)
> Encoding: base64
next prev parent reply other threads:[~2001-05-04 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 7:12 PROBLEM: 2.4.5pre1 will not boot Gordon Sadler
2001-05-04 7:43 ` Seth Goldberg [this message]
2001-05-04 8:01 ` Gordon Sadler
2001-05-04 8:28 ` Seth Goldberg
2001-05-05 2:55 ` Gordon Sadler
2001-05-05 3:05 ` Seth Goldberg
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=3AF25D9A.982B040B@home.com \
--to=bergsoft@home.com \
--cc=gbsadler1@lcisp.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