Alright, this is pretty frustrating. I've installed DP2 4 or 5 times now (each time reformatting).
The first time the installation program acted really weird and didn't do the install correctly. The second time I had weird random core dump problems so that I couldn't even log in. The third time I think was with the trap 12 when I started tcsh...now I reinstalled and it SEEMS to be working fine. At least enough that I was able to compile a custom kernel, and compile most of the gnome suite from ports too (and then to remove it ;). There was ONE problem I had -- one of the g++ include files (limits) had one line that was 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 times with random results. fwiw, I'm running stable off the same harddisk as I 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 more > > 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 trying to > > install. pkg_adding seems fine. Any chance this could be acpi related? > > How about this... > > o Are you using a GENERIC kernel? > > o Do you have a timestamp that can be used to check out a > /usr/src/sys from CVS that will let me build the same > kernel? > > o Do you have a place I can upload two or more 3/4MB kernel > files 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
