Re: Boot failure in 2.5.31 BK with new TLS patch

[James Bottomley <James.Bottomley@HansenPartnership.com>]

mingo@elte.hu said:
> while your patch looks OK, it would be *really* interesting to find
> out why the previous layout failed. Does the BIOS somehow corrupt the
> GDT? You are using the stock SMP code otherwise, correct? And this
> part of the patch: 

Well, I should say, this is the voyager MCA box again...

The boot problem only happens with my quad pentium cards, the dyad pentium and 
486 are fine.  Originally, a voyager system with quad cards just wouldn't boot 
(this was in the 2.2.x days).  Eventually, by trial and error and long debug 
of the boot process I discovered it would boot if the GDT was 8 bytes aligned 
(actually, the manuals say it should be 16 byte aligned, so perhaps we should 
also add this to the Linux setup.S?).  SUS (the voyager BIOS equivalent) 
reports that the CPU took a Trap 6 at FFF38466 in the boot sequence, but I 
knew there wasn't an illegal instruction, and the memory address isn't in the 
boot code. I suspect that the quad cards have some real mode instruction 
emulation and that's where the trap is occuring.

Unfortunately, all the people at NCR who could explain what is going on have 
long since departed, so I'm afraid I can only guess.

However, the general point that we should keep the boot sequence as simple as 
possible (just in case we run across any other wierd quirks even in modern 
PCs) still remains.

James