Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Nov 2002 22:10:24 -0500
From:      Scott Sipe <cscotts@mindspring.com>
To:        Terry Lambert <tlambert2@mindspring.com>
Cc:        John Baldwin <jhb@FreeBSD.org>, current@FreeBSD.org
Subject:   Re: DP2 Fatal Trap
Message-ID:  <200211222210.24713.cscotts@mindspring.com>
In-Reply-To: <3DDEC261.B5BEDFDC@mindspring.com>
References:  <XFMail.20021122105737.jhb@FreeBSD.org> <200211221427.31031.cscotts@mindspring.com> <3DDEC261.B5BEDFDC@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Alright, this is pretty frustrating.  I've installed DP2 4 or 5 times now=
=20
(each time reformatting).

The first time the installation program acted really weird and didn't do =
the=20
install correctly.  The second time I had weird random core dump problems=
 so=20
that I couldn't even log in.  The third time I think was with the trap 12=
=20
when I started tcsh...now I reinstalled and it SEEMS to be working fine. =
 At=20
least enough that I was able to compile a custom kernel, and compile most=
 of=20
the gnome suite from ports too (and then to remove it ;).  There was ONE=20
problem I had -- one of the g++ include files (limits) had one line that =
was=20
corrupted and I could fix.
the line was like:

coint name_more; (somethingl ike that)

when it should have been
const int name_more10;

(line 1710 iirc)

so basically it seems like I'm getting random data corruption at random t=
imes=20
with random results.  fwiw, I'm running stable off the same harddisk as I=
=20
type this.

sorry if this throws a wrench in things again.

Scott

On Friday 22 November 2002 06:48 pm, Terry Lambert wrote:
> Scott Sipe wrote:
> > It was a trap 12, and definitely that address...I think something mor=
e
> > overarching must be going on though.  I'm able to login with /bin/sh =
(not
> > csh/tcsh) and so I've been trying various things--I can't compile a
> > kernel because I get bus errors, same with many ports I've been tryin=
g to
> > install. pkg_adding seems fine.  Any chance this could be acpi relate=
d?
>
> How about this...
>
> o=09Are you using a GENERIC kernel?
>
> o=09Do you have a timestamp that can be used to check out a
> =09/usr/src/sys from CVS that will let me build the same
> =09kernel?
>
> o=09Do you have a place I can upload two or more 3/4MB kernel
> =09files for you to try?
>
> Let's say the answer to all three questions is "yes".
>
> Assuming I can build you a binary kernel from your sources which
> then fails on your machine, I believe I can fix the problem, and
> give you a new binary kernel that fixes it, if it's the problem I
> think it is.
>
> That way, we all win: you get a working kernel, and I get to
> convince people that the problem is what I said it was in the
> first place: a CPU bug that has to be specifically worked around.
>
> -- Terry


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211222210.24713.cscotts>