[EMAIL PROTECTED] wrote:
> > Sounds like you got caught by the conditional move instruction that is
> > generated for 686. It causes oops on 586, and somewhere in the oops or
> > printk code you hit another cmove. Double fault, kernel hang.
>
> Ah yes, it all comes back to me now :)
> Also
On Thu, 12 Oct 2000, Keith Owens wrote:
> Sounds like you got caught by the conditional move instruction that is
> generated for 686. It causes oops on 586, and somewhere in the oops or
> printk code you hit another cmove. Double fault, kernel hang.
Ah yes, it all comes back to me now :)
Also
On Thu, 12 Oct 2000, Keith Owens wrote:
Sounds like you got caught by the conditional move instruction that is
generated for 686. It causes oops on 586, and somewhere in the oops or
printk code you hit another cmove. Double fault, kernel hang.
Ah yes, it all comes back to me now :)
Also
[EMAIL PROTECTED] wrote:
Sounds like you got caught by the conditional move instruction that is
generated for 686. It causes oops on 586, and somewhere in the oops or
printk code you hit another cmove. Double fault, kernel hang.
Ah yes, it all comes back to me now :)
Also explains why
On Wed, Oct 11, 2000 at 02:26:08PM +0100, [EMAIL PROTECTED] wrote:
> I actually thought that the i686 target was the same as the i586 target
> with different instruction scheduling rules. Seems my judgement was off.
> /me goes to read gcc docs
i686 has conditional integer move and conditional
On Wed, 11 Oct 2000 14:26:08 +0100 (BST),
[EMAIL PROTECTED] wrote:
>I actually thought that the i686 target was the same as the i586 target
>with different instruction scheduling rules. Seems my judgement was off.
>/me goes to read gcc docs
Sounds like you got caught by the conditional move
On Wed, 11 Oct 2000, Frank de Lange wrote:
> Solved the problem with Winchip not booting. It turns out they do not like the
> code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
> -march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
> like it should.
> code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
> -march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
> like it should.
Thats the correct fix.
> gcc does bad things to these processors. Anyway, included is a small patch to
> solve these problems
On Wed, 11 Oct 2000, Frank de Lange wrote:
>Solved the problem with Winchip not booting. It turns out they do not like the
>code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
>-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
>like it should.
That
On Wed, 11 Oct 2000, Frank de Lange wrote:
Solved the problem with Winchip not booting. It turns out they do not like the
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
That
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
Thats the correct fix.
gcc does bad things to these processors. Anyway, included is a small patch to
solve these problems with
On Wed, 11 Oct 2000, Frank de Lange wrote:
Solved the problem with Winchip not booting. It turns out they do not like the
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
Makes
On Wed, 11 Oct 2000 14:26:08 +0100 (BST),
[EMAIL PROTECTED] wrote:
I actually thought that the i686 target was the same as the i586 target
with different instruction scheduling rules. Seems my judgement was off.
/me goes to read gcc docs
Sounds like you got caught by the conditional move
On Wed, Oct 11, 2000 at 02:26:08PM +0100, [EMAIL PROTECTED] wrote:
I actually thought that the i686 target was the same as the i586 target
with different instruction scheduling rules. Seems my judgement was off.
/me goes to read gcc docs
i686 has conditional integer move and conditional
On Wed, 11 Oct 2000, Frank de Lange wrote:
> Oops... looks like I was too quick to cry success...
Argh!
> It does NOT work, even with the patch. I tried it again and again, and
> could not get it to boot. I probably put a wrong (Pentium MMX) kernel
> on the flashdisk when I first tested your
Hi'all,
Solved the problem with Winchip not booting. It turns out they do not like the
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
I do not have a working egcs 1.1.x or gcc
OK, some more info on the hang with the Winchip2A:
it seems to hang in arch/i386/kernel/setup.c, function print_memory_map, on the
first iteration of the loop. If I target to Pentium MMX and run it on the same
(Win)chip, all's well. There's something wrong here, but it is not in that
piece of
> Ok, I've narrowed it down to the changes to mtrr.c in test8
> Looks like the Cyrix III changes broke things.
> Didn't something similar happen when these changes made it into
> a 2.2.18pre ? Alan?
2.2.18pre12 or so had a bug with Winchip but its fixed in pre15 I believe,
at least my winchip is
On Tue, Oct 10, 2000 at 06:10:48PM -0700, James Simmons wrote:
> > Dave,
> >
> > This patch fixed the problems, for now. The system now boots OK, and seems to
> > run OK (have not hit it very hard yet since it currently runs without a
> > heatsink). Tnanks...
> >
> > Cheers//Frank
Oops...
James,
The patch I referred to can be found in Dave's message... I gave him some
feedback on the problems with Winchips...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| / \
##---# _/ \
\
Either you forgot to attach the patch for it was bigger than 40K.
On Tue, 10 Oct 2000, Frank de Lange wrote:
> Dave,
>
> This patch fixed the problems, for now. The system now boots OK, and seems to
> run OK (have not hit it very hard yet since it currently runs without a
> heatsink).
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| /
> I tried the patch, but the result is the same... Uncompressing Linux...,
> now booting the kernel..., NOTHING
> These Winchips need all the help they can get, so if you know something
> else I might try...
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix
I tried the patch, but the result is the same... Uncompressing Linux...,
now booting the kernel..., NOTHING
These Winchips need all the help they can get, so if you know something
else I might try...
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix III
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| /
Either you forgot to attach the patch for it was bigger than 40K.
On Tue, 10 Oct 2000, Frank de Lange wrote:
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
James,
The patch I referred to can be found in Dave's message... I gave him some
feedback on the problems with Winchips...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| / \
##---# _/ Hacker for Hire \
On Tue, Oct 10, 2000 at 06:10:48PM -0700, James Simmons wrote:
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
Cheers//Frank
Oops... looks like I was
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix III changes broke things.
Didn't something similar happen when these changes made it into
a 2.2.18pre ? Alan?
2.2.18pre12 or so had a bug with Winchip but its fixed in pre15 I believe,
at least my winchip is
OK, some more info on the hang with the Winchip2A:
it seems to hang in arch/i386/kernel/setup.c, function print_memory_map, on the
first iteration of the loop. If I target to Pentium MMX and run it on the same
(Win)chip, all's well. There's something wrong here, but it is not in that
piece of
Hi'all,
Solved the problem with Winchip not booting. It turns out they do not like the
code generated by gcc (gcc version 2.95.2 19991024 (release)) when the
-march=i686 flag is set. Changing this flag to -march=i586 makes to box boot
like it should.
I do not have a working egcs 1.1.x or gcc
On Wed, 11 Oct 2000, Frank de Lange wrote:
Oops... looks like I was too quick to cry success...
Argh!
It does NOT work, even with the patch. I tried it again and again, and
could not get it to boot. I probably put a wrong (Pentium MMX) kernel
on the flashdisk when I first tested your
Hi Dave,
I tried the patch, but the result is the same... Uncompressing Linux..., now
booting the kernel..., NOTHING
These Winchips need all the help they can get, so if you know something else I
might try...
Cheers//Frank
--
W ___
## o o\/ Frank de
[EMAIL PROTECTED] (Frank de Lange) wrote..
> Subject says it all... If I select 'Winchip 2' or 'Winchip 2A/Winchip 3'
> for 'Processor Family' and try to boot the kernel on an iopener with a
> Winchip 2A, the show stops right after the 'decompressing the
> kernel...' line is displayed.
Hiya,
Subject says it all... If I select 'Winchip 2' or 'Winchip 2A/Winchip 3' for
'Processor Family' and try to boot the kernel on an iopener with a Winchip 2A,
the show stops right after the 'decompressing the kernel...' line is
displayed. Nothing happens. It just freezes...
Cheers//Frank
Hiya,
Subject says it all... If I select 'Winchip 2' or 'Winchip 2A/Winchip 3' for
'Processor Family' and try to boot the kernel on an iopener with a Winchip 2A,
the show stops right after the 'decompressing the kernel...' line is
displayed. Nothing happens. It just freezes...
Cheers//Frank
[EMAIL PROTECTED] (Frank de Lange) wrote..
Subject says it all... If I select 'Winchip 2' or 'Winchip 2A/Winchip 3'
for 'Processor Family' and try to boot the kernel on an iopener with a
Winchip 2A, the show stops right after the 'decompressing the
kernel...' line is displayed. Nothing
37 matches
Mail list logo
