Page 1 of 1

(SOLVED) Floating point exception

PostPosted: Apr 25th, '13, 20:58
by condor
I have clean installed 3 rc on two machines now. One is a 990fx system with 955BE processor. The other is a x79 system with i7 3820 processor. The first system boots up, no error. The second system gives a 'Floating point Exception' message interrupting the plymouth boot splash upon every boot.

Re: Floating point exception

PostPosted: Apr 25th, '13, 21:58
by condor
A further note: applying all the available updates did not change anything in either case.

Re: Floating point exception

PostPosted: Apr 26th, '13, 00:18
by tom_
is your situations similar to this one?

https://bugs.mageia.org/show_bug.cgi?id=9689

Re: Floating point exception

PostPosted: Apr 26th, '13, 00:31
by condor
It sounds like it-but if so, it isn't 'resolved fixed' as that bug is marked, because I just got this 'floating point exception' on the one machine after clean installing these two systems earlier today with the x64 3 rc as noted above.
There shouldn't be a need to regen the initrds on a new install-but tried that anyway, with no change on the affected system.
I will say that it doesn't seem to affect how the system runs, but it's apt to be a scary looking message for anyone giving Mageia a try for the first time.

Re: Floating point exception

PostPosted: Apr 26th, '13, 18:52
by doktor5000
Well, the bug is correctly marked resolved, but it was about another problem. Colin mentioned in the last post,
that he will try to reproduce the problem, but if he doesn't trigger it (as it seems to happen only with some processors) then
there's only a small chance to fix it. Best reopen that bug and put a comment there that you're also affected, and also
reference this thread and post your processor model there.

Re: Floating point exception

PostPosted: Apr 26th, '13, 20:02
by condor
Ok, I have done that, doktor5000, thanks.

Re: Floating point exception

PostPosted: May 2nd, '13, 23:39
by condor
As noted in the bug link posted above, this was continued in:
https://bugs.mageia.org/show_bug.cgi?id=9850

where Colin noted it should be fixed, and indeed it is now. Marking this post solved.