Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[jason henson]

Edgar Martinez wrote:
I think I have nailed it...somewhat...
So I set it up so I could ssh to it from my office and try to mess with
it...ran solid as a rock...I think got home tonight and checked my
logs...nothing bad...so I THEN rebooted went into BIOS and enabled the
cache...BAM...errors out every time...threw in
ubuntu...craptastic...DISABLED the CACHE...everything smooth...sooo the
question now is...MB or CPU??  

The CPU is listed as DTR...OMFG WTF is DTR?? (acro-cursing intended..)
Model: AMD Athlon 64 3000+ DTR
Core: ClawHammer
Operating Frequency: 1.8 GHz
FSB: Integrated into Chip
Cache: L1/64K+64K; L2/1MB
Voltage: 1.5V
Process: 0.13Micron
Socket: Socket 754
Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+
Packaging: OEM(Processor Only)

-Original Message-
From: jason henson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 7:20 PM
To: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez 
 

DTR stands for desktop replacement notebook.  You have a cpu for a 
powerful notebook, but I think it would still be a low powered desktop 
cpu.  Maybe you could try a bios update, but I would you need to rma 
that cpu.  Sounds like it has some bad cache on it?

http://www.hothardware.com/viewarticle.cfm?articleid=642
http://www.voodoopc.com/boards/messages.aspx?topic=32296&forum=2
http://www.theregister.co.uk/2003/07/29/amd_cuts_opteron_prices_by/
http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_10220_9486,00.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

I think I have nailed it...somewhat...

So I set it up so I could ssh to it from my office and try to mess with
it...ran solid as a rock...I think got home tonight and checked my
logs...nothing bad...so I THEN rebooted went into BIOS and enabled the
cache...BAM...errors out every time...threw in
ubuntu...craptastic...DISABLED the CACHE...everything smooth...sooo the
question now is...MB or CPU??  

The CPU is listed as DTR...OMFG WTF is DTR?? (acro-cursing intended..)

Model: AMD Athlon 64 3000+ DTR
Core: ClawHammer
Operating Frequency: 1.8 GHz
FSB: Integrated into Chip
Cache: L1/64K+64K; L2/1MB
Voltage: 1.5V
Process: 0.13Micron
Socket: Socket 754
Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+
Packaging: OEM(Processor Only)



-Original Message-
From: jason henson [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 7:20 PM
To: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez wrote:

>All,
>
> 
>
>I cant begin to tell you how horrible of a time I have had trying to get
>this system installed and running. Sysinstall kept throwing up a privilege
>fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough
>to get lucky to an install complete..the system then spends its time
>periodically rebooting.this is the first venture into AMD64 turf as I
>historically stick with i386.so any pointers.gotchas.tweaks or tips..
please
>let me know..I really don't want to give up, so I want to see what can be
>done to stabilize this.
>
> 
>
>MSI K8T Neo
>
>AMD64 3000 w/1MB
>
> 
>  
>
I was just reading the archives this week at freebsd.org and it leads me 
to believe msi make crap boards.  They can not handle tough loads or 
lots of ram.  I think it was in the amd64 list under a heading that 
mentioned 8gig of ram.  There were several developers that just trashed 
there msi boards and all the rest of there hardware worked fine in a new 
board.  You should look it up.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Roland Smith]

On Wed, Apr 13, 2005 at 08:20:23PM -0400, jason henson wrote:

> >MSI K8T Neo
> >
> >AMD64 3000 w/1MB
> >
> I was just reading the archives this week at freebsd.org and it leads me 
> to believe msi make crap boards.  They can not handle tough loads or 
> lots of ram.  I think it was in the amd64 list under a heading that 
> mentioned 8gig of ram.  There were several developers that just trashed 
> there msi boards and all the rest of there hardware worked fine in a new 
> board.  You should look it up.

There was/is an issue with >4GB RAM, but I don't recall it being only
with MSI boards. And since 4GB is the limit for 32-bit addressing, I
would rather suspect a 32/64-bitness issue.

Personally I've used MSI motherboards in my last four desktops, running
Linux or FreeBSD, and have never had issues with them. I'm using a MSI
K8T NEO FSR (MS-6702) in my current amd64 box without problems.

Roland
-- 
R.F. Smith   /"\ASCII Ribbon Campaign
r s m i t h @ x s 4 a l l . n l  \ /No HTML/RTF in e-mail
http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail
public key: http://www.keyserver.net / \Respect for open standards


pgpVZaj0wBIHI.pgp
Description: PGP signature

Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[jason henson]

Edgar Martinez wrote:
All,

I cant begin to tell you how horrible of a time I have had trying to get
this system installed and running. Sysinstall kept throwing up a privilege
fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough
to get lucky to an install complete..the system then spends its time
periodically rebooting.this is the first venture into AMD64 turf as I
historically stick with i386.so any pointers.gotchas.tweaks or tips.. please
let me know..I really don't want to give up, so I want to see what can be
done to stabilize this.

MSI K8T Neo
AMD64 3000 w/1MB
 

I was just reading the archives this week at freebsd.org and it leads me 
to believe msi make crap boards.  They can not handle tough loads or 
lots of ram.  I think it was in the amd64 list under a heading that 
mentioned 8gig of ram.  There were several developers that just trashed 
there msi boards and all the rest of there hardware worked fine in a new 
board.  You should look it up.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

Yep first thing I assumed...ACPI was disabled...both in BIOS and via
MENU...no joy...UDMA disabled...in fact..

PATA DISABLED (after install via CD)
USB DISABLED
FDD DIABLED
APM DIABLED
SMART DISABLED
LAN DISABLED
SOUND DISABLED
FIREWIRE DISABLED

=)

If you cant tell, I have literally installed over a hundred FBSD boxes and
have encountered TONS of caveats...however this one has def got me
stumped..after the install, the system seems to be holding stable with the
BIOS INTERNAL/EXTERNAL cache disabled...its SLLLOOOWWW but stable...


-Original Message-
From: NMH [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 2:19 PM
To: [EMAIL PROTECTED]; questions
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)


--- Edgar Martinez <[EMAIL PROTECTED]> wrote:

> All,
> 
>  
> 
> I cant begin to tell you how horrible of a time I
> have had trying to get
> this system installed and running. Sysinstall kept
> throwing up a privilege
> fault kernel error randomly (7sed...4m.7m..etc), and
> after I go fast enough
> to get lucky to an install complete..the system then
> spends its time
> periodically rebooting.this is the first venture
> into AMD64 turf as I
> historically stick with i386.so any
> pointers.gotchas.tweaks or tips.. please
> let me know..I really don't want to give up, so I
> want to see what can be
> done to stabilize this.
> 


 Unless someone else can vouch for that MB, it can be
a suspect as well. While AMD is good, not all MB's for
them are.

 Also ACPI can cause weird stuff like that too.
Perhaps try turning that off or try other settings in
the BIOS. I had that problem once. It actually did
then when ACPI was turned off in the bios. 


 Best of luck.


 NMH

> 
> MSI K8T Neo
> 
> AMD64 3000 w/1MB
> 
>  
> 
> Thanks!
> 

>  
> 
> ## SNIP ##
> 
>


The Large Print Giveth And The Small Print Taketh Away
 -- Anon



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[NMH]

--- Edgar Martinez <[EMAIL PROTECTED]> wrote:

> All,
> 
>  
> 
> I cant begin to tell you how horrible of a time I
> have had trying to get
> this system installed and running. Sysinstall kept
> throwing up a privilege
> fault kernel error randomly (7sed...4m.7m..etc), and
> after I go fast enough
> to get lucky to an install complete..the system then
> spends its time
> periodically rebooting.this is the first venture
> into AMD64 turf as I
> historically stick with i386.so any
> pointers.gotchas.tweaks or tips.. please
> let me know..I really don't want to give up, so I
> want to see what can be
> done to stabilize this.
> 


 Unless someone else can vouch for that MB, it can be
a suspect as well. While AMD is good, not all MB's for
them are.

 Also ACPI can cause weird stuff like that too.
Perhaps try turning that off or try other settings in
the BIOS. I had that problem once. It actually did
then when ACPI was turned off in the bios. 


 Best of luck.


 NMH

> 
> MSI K8T Neo
> 
> AMD64 3000 w/1MB
> 
>  
> 
> Thanks!
> 

>  
> 
> ## SNIP ##
> 
>


The Large Print Giveth And The Small Print Taketh Away
 -- Anon



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

I appreciate your help! There is NO stupid question or answer...as far as I
am concerned ANY help is always WELCOME help...THANKS

So, yeah being from the i386 world, I am also aware of the timing quirks in
the intel world. The CPU is a 754 pin...specs below..hope this sheds some
light on the situation...if anyone wants me to throw up some debug info let
me know!!

AMD Athlon 64 3000+, 1MB L2 Cache, 64-bit Processor for DTR Notebooks - OEM

Model# AMA3000BEX5AP
Item # N82E16819103444

Specifications:
Model: AMD Athlon 64 3000+
Core: ClawHammer
Operating Frequency: 1.8 GHz
FSB: Integrated into Chip
Cache: L1/64K+64K; L2/1MB
Voltage: 1.5V
Process: 0.13Micron
Socket: Socket 754
Multimedia Instruction: MMX, SSE, SSE2, 3DNOW!, 3DNOW!+
Packaging: OEM(Processor Only)


PATRIOT Extreme Performance 184-Pin 512MB DDR PC-3200 w/ XBL Technology,
Model PEP5123200+XBL - Retail

Model# PEP5123200+XBL
Item # N82E16820220036
Specifications:
Manufacturer: PDP Systems
Speed: DDR400(PC3200)
Type: 184-Pin DDR SDRAM
Error Checking: Non-ECC
Registered/Unbuffered: Unbuffered
Cas Latency: 2-2-2-5 T1
Support Voltage: 2.8V
Bandwidth: 3.2GB/s
Organization: 64M x 64 -Bit
Warranty: Lifetime


-Original Message-
From: Alex Zbyslaw [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 9:40 AM
To: [EMAIL PROTECTED]
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez wrote:

>OK, removed all misc cards, devices, recabled...attempting to reinstall
with
>5.3, and I continue to get a "kernel: priviledged instruction fault"
>followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings?
>  
>
I don't know this brand of RAM, and I may be completely wrong but...

When looking at 939 pin AMD CPUs, and what memory to get, I noticed that 
for one major quality RAM maker, the timings they recommended for Intel 
CPUs were faster than those they recommended for AMD CPUs and your 
figures look eerily familiar.  It was something like 2-2-2-5 for Intel 
and 2-2.5-2-5 for AMD.

I'm no expert on RAM, but your error does sound very hardware related.  
Can you check the RAM manufacturer's web site to see if they say anything?

Also, some motherboards can be very picky about RAM.  Is it worth trying 
with just one RAM chip?  Does the machine POST ok with full memory tests 
on?  (It doesn't prove anything, but if a chip is really duff it should 
find it).

A little heretical, I realise, but is there the possibility of trying 
another OS (Windows, Linux) just to see if you have the same kinds of 
problems?

I'm not copying to the list because I'm no real expert on this kind of 
thing; just stuff picked up from background reading.  If you try any of 
this and it works can you post back to the list what finally worked?

Best,

--Alex


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

Yep,

Tried 5.3 mini, two different 5.3 Disc 1, 5.4RC2 Disc 1

Strangely enough, I disabled in the bios the CPU Cache and although the
system is sluggish and slow, it has not freaked out yet..

-Original Message-
From: Trevor Sullivan [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 9:13 AM
To: [EMAIL PROTECTED]
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez wrote:

>New error before death
>
>"Panic: page fault"
>
>-Original Message-
>From: Trevor Sullivan [mailto:[EMAIL PROTECTED] 
>Sent: Wednesday, April 13, 2005 9:00 AM
>To: [EMAIL PROTECTED]
>Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3,
5.4
>(pre+post install)
>
>Edgar Martinez wrote:
>
>  
>
>>OK, removed all misc cards, devices, recabled...attempting to reinstall
>>
>>
>with
>  
>
>>5.3, and I continue to get a "kernel: priviledged instruction fault"
>>followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings?
>>
>>-Original Message-
>>From: Kris Kennaway [mailto:[EMAIL PROTECTED] 
>>Sent: Wednesday, April 13, 2005 5:23 AM
>>To: Edgar Martinez
>>Cc: freebsd-questions@freebsd.org
>>Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3,
>>
>>
>5.4
>  
>
>>(pre+post install)
>>
>>On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote:
>> 
>>
>>
>>
>>>All,
>>>
>>>
>>>
>>>I cant begin to tell you how horrible of a time I have had trying to get
>>>this system installed and running. Sysinstall kept throwing up a
privilege
>>>fault kernel error randomly (7sed...4m.7m..etc), and after I go fast
>>>   
>>>
>>>  
>>>
>>enough
>> 
>>
>>
>>
>>>to get lucky to an install complete..the system then spends its time
>>>periodically rebooting.this is the first venture into AMD64 turf as I
>>>historically stick with i386.so any pointers.gotchas.tweaks or tips..
>>>   
>>>
>>>  
>>>
>>please
>> 
>>
>>
>>
>>>let me know..I really don't want to give up, so I want to see what can be
>>>done to stabilize this.
>>>   
>>>
>>>  
>>>
>>Sounds like the usual bad hardware story..check RAM, power supply, CPU
>>cooling, cabling, etc.
>>
>>kris
>>
>>___
>>freebsd-questions@freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>To unsubscribe, send any mail to
>>
>>
>"[EMAIL PROTECTED]"
>  
>
>> 
>>
>>
>>
>Is this computer overclocked at all? I would highly recommend running it 
>at the speeds it was meant to...you can avoid a lot of errors that way.
>
>-Trevor
>
>
>  
>
Is there perhaps a problem with the burned CD? Did you check the hash 
after downloading it, and verify the cd's contents after burning it? 
Sorry it's a stab in the dark, but maybe it'll give you a push in the 
direction of making it work =D

-Trevor

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

New error before death

"Panic: page fault"

-Original Message-
From: Trevor Sullivan [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 9:00 AM
To: [EMAIL PROTECTED]
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez wrote:

>OK, removed all misc cards, devices, recabled...attempting to reinstall
with
>5.3, and I continue to get a "kernel: priviledged instruction fault"
>followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings?
>
>-Original Message-
>From: Kris Kennaway [mailto:[EMAIL PROTECTED] 
>Sent: Wednesday, April 13, 2005 5:23 AM
>To: Edgar Martinez
>Cc: freebsd-questions@freebsd.org
>Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3,
5.4
>(pre+post install)
>
>On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote:
>  
>
>>All,
>>
>> 
>>
>>I cant begin to tell you how horrible of a time I have had trying to get
>>this system installed and running. Sysinstall kept throwing up a privilege
>>fault kernel error randomly (7sed...4m.7m..etc), and after I go fast
>>
>>
>enough
>  
>
>>to get lucky to an install complete..the system then spends its time
>>periodically rebooting.this is the first venture into AMD64 turf as I
>>historically stick with i386.so any pointers.gotchas.tweaks or tips..
>>
>>
>please
>  
>
>>let me know..I really don't want to give up, so I want to see what can be
>>done to stabilize this.
>>
>>
>
>Sounds like the usual bad hardware story..check RAM, power supply, CPU
>cooling, cabling, etc.
>
>kris
>
>___
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>
>  
>
Is this computer overclocked at all? I would highly recommend running it 
at the speeds it was meant to...you can avoid a lot of errors that way.

-Trevor

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

Its using the default bios settings and nothing is overclocked at all..

-Original Message-
From: Trevor Sullivan [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 9:00 AM
To: [EMAIL PROTECTED]
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

Edgar Martinez wrote:

>OK, removed all misc cards, devices, recabled...attempting to reinstall
with
>5.3, and I continue to get a "kernel: priviledged instruction fault"
>followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings?
>
>-Original Message-
>From: Kris Kennaway [mailto:[EMAIL PROTECTED] 
>Sent: Wednesday, April 13, 2005 5:23 AM
>To: Edgar Martinez
>Cc: freebsd-questions@freebsd.org
>Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3,
5.4
>(pre+post install)
>
>On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote:
>  
>
>>All,
>>
>> 
>>
>>I cant begin to tell you how horrible of a time I have had trying to get
>>this system installed and running. Sysinstall kept throwing up a privilege
>>fault kernel error randomly (7sed...4m.7m..etc), and after I go fast
>>
>>
>enough
>  
>
>>to get lucky to an install complete..the system then spends its time
>>periodically rebooting.this is the first venture into AMD64 turf as I
>>historically stick with i386.so any pointers.gotchas.tweaks or tips..
>>
>>
>please
>  
>
>>let me know..I really don't want to give up, so I want to see what can be
>>done to stabilize this.
>>
>>
>
>Sounds like the usual bad hardware story..check RAM, power supply, CPU
>cooling, cabling, etc.
>
>kris
>
>___
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>
>  
>
Is this computer overclocked at all? I would highly recommend running it 
at the speeds it was meant to...you can avoid a lot of errors that way.

-Trevor

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

OK, removed all misc cards, devices, recabled...attempting to reinstall with
5.3, and I continue to get a "kernel: priviledged instruction fault"
followed by a reboot...RAM is brand new Patriot 2-2-2-5...mem timings?

-Original Message-
From: Kris Kennaway [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 13, 2005 5:23 AM
To: Edgar Martinez
Cc: freebsd-questions@freebsd.org
Subject: Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4
(pre+post install)

On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote:
> All,
> 
>  
> 
> I cant begin to tell you how horrible of a time I have had trying to get
> this system installed and running. Sysinstall kept throwing up a privilege
> fault kernel error randomly (7sed...4m.7m..etc), and after I go fast
enough
> to get lucky to an install complete..the system then spends its time
> periodically rebooting.this is the first venture into AMD64 turf as I
> historically stick with i386.so any pointers.gotchas.tweaks or tips..
please
> let me know..I really don't want to give up, so I want to see what can be
> done to stabilize this.

Sounds like the usual bad hardware story..check RAM, power supply, CPU
cooling, cabling, etc.

kris

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Kris Kennaway]

On Wed, Apr 13, 2005 at 01:10:42AM -0500, Edgar Martinez wrote:
> All,
> 
>  
> 
> I cant begin to tell you how horrible of a time I have had trying to get
> this system installed and running. Sysinstall kept throwing up a privilege
> fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough
> to get lucky to an install complete..the system then spends its time
> periodically rebooting.this is the first venture into AMD64 turf as I
> historically stick with i386.so any pointers.gotchas.tweaks or tips.. please
> let me know..I really don't want to give up, so I want to see what can be
> done to stabilize this.

Sounds like the usual bad hardware story..check RAM, power supply, CPU
cooling, cabling, etc.

kris


pgpKNP0L6zNAb.pgp
Description: PGP signature

AMD64 (former i386 convert)+ FreeBSD various issues in 5.3, 5.4 (pre+post install)

[Edgar Martinez]

All,

 

I cant begin to tell you how horrible of a time I have had trying to get
this system installed and running. Sysinstall kept throwing up a privilege
fault kernel error randomly (7sed...4m.7m..etc), and after I go fast enough
to get lucky to an install complete..the system then spends its time
periodically rebooting.this is the first venture into AMD64 turf as I
historically stick with i386.so any pointers.gotchas.tweaks or tips.. please
let me know..I really don't want to give up, so I want to see what can be
done to stabilize this.

 

MSI K8T Neo

AMD64 3000 w/1MB

 

Thanks!

 

PS: WTF is this?? (fpudna in kernel mode!) only reference I could find.

 

http://fxr.watson.org/fxr/source/amd64/amd64/trap.c

 

## SNIP ##

327 
/* kernel trap */
328   
329 
KASSERT  (cold
  || td
 ->td_ucred != NULL
 ,
330 
("kernel trap doesn't have ucred"));
331 
switch (type  ) {
332 
case T_PAGEFLT  :
/* page fault */
333 
(void) trap_pfault  (&frame
 , FALSE
 );
334 
goto out  ;
335   
336 
case T_DNA  :
337 
/*
338 
* The kernel is apparently using fpu for copying.
339 
* XXX this should be fatal unless the kernel has
340 
* registered such use.
341 
*/
342 
if (fpudna  ()) {
343 
printf  ("fpudna in kernel
mode!\n");
344 
goto out  ;
345 
}
346 
break;

## SNIP ##

 

 

## DMSG ##

 

FreeBSD 5.4-RC2 #0: Sun Apr 10 04:02:23 UTC 2005

[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC

ACPI APIC Table: 

Timecounter "i8254" frequency 1193182 Hz quality 0

CPU: AMD Athlon(tm) 64 Processor 3000+ (1800.08-MHz K8-class CPU)

  Origin = "AuthenticAMD"  Id = 0xf4a  Stepping = 10

 
Features=0x78bfbff

  AMD Features=0xe0500800

real memory  = 536805376 (511 MB)

avail memory = 506781696 (483 MB)

ioapic0  irqs 0-23 on motherboard

acpi0:  on motherboard

acpi0: Power Button (fixed)

Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000

acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0

cpu0:  on acpi0

acpi_button0:  on acpi0

pcib0:  port 0xcf8-0xcff on acpi0

pci0:  on pcib0

pcib1:  at device 1.0 on pci0

pci1:  on pcib1

pci1:  at device 0.0 (no driver attached)

re0:  port 0xd400-0xd4ff mem
0xcfffbf00-0xcfffbfff irq 16 at device 11.0 on pci0

miibus0:  on re0

rgephy0:  on miibus0

rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto

re0: Ethernet address: 00:11:09:ed:a0:47

atapci0:  port
0xd800-0xd8ff,0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00
-0xec07 irq 20 at device 15.0 on pci0

ata2: channel #0 on atapci0

ata3: channel #1 on atapci0

isab0:  at device 17.0 on pci0

isa0:  on isab0

pci0:  at device 17.5 (no driver attached)

acpi_button1:  on acpi0

sio0: configured irq 4 not in bitmap of probed irqs 0

sio0: port may not be enabled

sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0

sio0: type 16550A

ppc0:  port 0x778-0x77b,0x378-0x37f irq 7 drq 3
on acpi0

ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode

ppc0: FIFO with 16/16/9 bytes threshold

ppbus0:  on ppc0

plip0:  on ppbus0

lpt0:  on ppbus0

lpt0: Interrupt-driven port

ppi0:  on ppbus0

atkbdc0:  port 0x64,0x60 irq 1 on acpi0

atkbd0:  flags 0x1 irq 1 on atkbdc0

kbd0 at atkbd0

orm0:  at iomem 0xe-0xe0fff on