On Tue, Mar 15, 2005 at 06:30:33PM -0600, Jon Noack wrote:
Jon Noack wrote:
Is it possible GCC compiled with CPUTYPE?=athlon-xp produces bad code?
I guess my BIOS writer could've been on crack, but the machine is rock
solid without CPUTYPE defined so I don't think it is a hardware
problem.
Can you try with just -mno-sse2? I'd like to litter the compile command
line as little as possible.
I just tried. -mno-sse2 indeed is all that's required to make the kernel
work. The same flag also makes the loader run again:
--- /usr/src/sys/boot/i386/loader/Makefile.old Tue Mar 15 18:03:13
That last patch was reversed. Sorry:
--- /usr/src/sys/boot/i386/loader/Makefile.old Tue Mar 15 18:03:13 2005
+++ /usr/src/sys/boot/i386/loader/Makefile Fri Feb 27 15:10:09 2004
@@ -40,7 +40,7 @@
CLEANFILES=vers.c loader loader.bin loader.help
-CFLAGS+= -Wall
+CFLAGS+= -Wall
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me, your patch fixes the kernel.
Can you try with just -mno-sse2? I'd
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me, your patch fixes the kernel.
Can you try with just -mno-sse2? I'd
On Tue, Mar 15, 2005 at 01:12:57PM -0600, Jon Noack wrote:
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me,
On Tue, Mar 15, 2005 at 01:41:55PM -0600, Jon Noack wrote:
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Can you try with just -mno-sse2? I'd like to
David O'Brien wrote:
On Tue, Mar 15, 2005 at 01:41:55PM -0600, Jon Noack wrote:
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Can you try with just -mno-sse2?
Jon Noack wrote:
David O'Brien wrote:
On Tue, Mar 15, 2005 at 01:41:55PM -0600, Jon Noack wrote:
David O'Brien wrote:
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make
everyone's
environment happy?
Can you try with
On Sat, Mar 12, 2005 at 10:48:52PM +0100, Bartosz Fabianowski wrote:
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me, your patch fixes the kernel.
Can you try with just -mno-sse2? I'd like to litter
Are you saying, all we need to do is commit this diff to make everyone's
environment happy?
Obviously, I can't speak for everyone. For me, your patch fixes the kernel.
But the loader still causes an exception. That's of course because your patch
only affects the kernel itself and not the loader.
On Sun, Mar 06, 2005 at 07:47:08PM +0100, Bartosz Fabianowski wrote:
i have read that were some problems compiling the kernel and the
loader with pentium-m in CPUTYPE. are they fixed now?
I'm the one who filed the original bug report:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75898
..
I'd
i have read that were some problems compiling the kernel and the loader
with pentium-m in CPUTYPE. are they fixed now? or, if not yet, is it
safe to compile the world with that switch on (and downgrade to
something else - pentium3? - for kernelloader) ?
. If you want to try for yourself, just recompile your kernel with
CPUTYPE=pentium-m and see whether it boots or panics.
is it safe to compile the world with that switch on (and downgrade to
something else - pentium3? - for kernelloader) ?
I'd assume the answer to this one is yes - it's safe
Bartosz Fabianowski wrote:
I use the athlon-xp switch on 3 boxes with no problems all of them
running 5.3
What CFLAGS are you using? I have CFLAGS=-O -pipe in my make.conf. Maybe
you have optimization turned off and that's making a difference?
I reported the problem with the athlon-xp. My
- Original Message -
From: Jon Noack [EMAIL PROTECTED]
To: Bartosz Fabianowski [EMAIL PROTECTED]
Cc: Chris [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, January 06, 2005 7:35 PM
Subject: Re: Instant reboots with CPUTYPE=pentium-m
Bartosz Fabianowski wrote:
I
Note that I only see the problem when building the loader as part of a
buildworld. Compiling just the boot stuff in /usr/src/sys/boot/ (i.e.,
without a bootstrapped gcc) results in a loader that works fine.
Curious. Either what you are seeing is a different problem then or it
somehow shows in a
and hope that someone
can lead me in the right direction.
The problem is that setting CPUTYPE=pentium-m in make.conf leads to a
corrupt boot loader and a corrupt kernel being generated. This setting
for the CPUTYPE has been available on -STABLE since 16th December, when
revision 1.40.2.1
I use the athlon-xp switch on 3 boxes with no problems all of them running 5.3
What CFLAGS are you using? I have CFLAGS=-O -pipe in my make.conf. Maybe
you have optimization turned off and that's making a difference?
- Bartosz
___
Replying to myself, I have found the problem and filed a but report:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75898
Thanks for all the help everybody,
- Bartosz
___
freebsd-stable@freebsd.org mailing list
Hi list,
I am still having the problems with instant reboots that I reported [1]
a couple of weeks ago. I have a bit more info now and hope that someone
can lead me in the right direction.
The problem is that setting CPUTYPE=pentium-m in make.conf leads to a
corrupt boot loader and a corrupt
21 matches
Mail list logo
