Probable seamless bug: can't pop es
The following simple program runs on a P4 linux system, but gets a SIGSEGV on an Itanium. Most likely a seamless bug rather than a hardware bug. Even though we don't use segment registers in Linux, it is legal to push and pop them, isn't it?
main()
{
asm ("pushl %ds");
asm ("popl %es");
}David Robboy
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · David G
David.R> The following simple program runs on a P4 linux system, but David.R> gets a SIGSEGV on an Itanium. Most likely a seamless bug David.R> rather than a hardware bug. Even though we don't use David.R> segment registers in Linux, it is legal to push and pop David.R> them, isn't it?
Actually, even segmentation is supported (via modify_ldt()), so the program should work. GDB says it dies on the "popl" instruction. The address that triggering the fault is 0x4c. I don't see where this is coming from. My suspicion is that the segv happens when the CPU attempts to load the segment descriptor from the GDT, but if that's the case, the address should be somewhere in the 0xc0000000 range. Another possibility is that the GDTD is not set up properly, but I don't see anything obvious that's wrong there.
Perhaps someone more familiar with x86 could take a look?
--david
Short answer: Yes, the GDTD was set up wrong, here's the patch to fix this. (I must be getting better, it only took me a weekend to find the single bit that had to change rather than my typical effort of over a week :-) We were neglecting to set the present bit, an obvious no-no.
Long answer: I'm amazed we've gotten as far as we have with this bug. ANY attempt by an IA32 program to load a segment register from the GDT would cause a fault. The only reason we have worked up to now is that the IA64 code sets up all of the segment descriptors manually without reference to the GDT and very few protected mode IA32 programs attempt to load any of the segment registers.
Also, there is a non-zero change that this will fix the problem with Wine trying to run certain programs, you might want to try TurboTax again with this fix in.
Quoted 25 lines · David Mosberger
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · David G
David.R> The following simple program runs on a P4 linux system, but David.R> gets a SIGSEGV on an Itanium. Most likely a seamless bug David.R> rather than a hardware bug. Even though we don't use David.R> segment registers in Linux, it is legal to push and pop David.R> them, isn't it?
Actually, even segmentation is supported (via
modify_ldt()), so the program should work. GDB says it dies on the "popl" instruction. The address that triggering the fault is0x4c. I don't see where this is coming from. My suspicion is that the segv happens when the CPU attempts to load the segment descriptor from the GDT, but if that's the case, the address should be somewhere in the0xc0000000range. Another possibility is that the GDTD is not set up properly, but I don't see anything obvious that's wrong there.Perhaps someone more familiar with x86 could take a look?
--david_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64
Signature · 4 lines
Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale [email protected] Ph: 303/652-0870x117
arch/ia64/ia32/binfmt_elf32.c +4 -3
@@ -135,10 +135,11 @@/* * Setup GDTD. Note: GDTD is the descrambled version of the pseudo-descriptor * format defined by Figure 3-11 "Pseudo-Descriptor Format" in the IA-32 -* architecture manual. +* architecture manual. Also note that the only fields that are not +* ignored are `base', `limit', 'G', `P' (must be 1) and `S' (must be 0) */ - regs->r31 =IA32_SEG_UNSCRAMBLE (IA32_SEG_DESCRIPTOR (IA32_GDT_OFFSET ,IA32_PAGE_SIZE -1 ,0 , -0 ,0 ,0 ,0 ,0 ,0 )); + regs->r31 =IA32_SEG_UNSCRAMBLE (IA32_SEG_DESCRIPTOR (IA32_GDT_OFFSET , +IA32_PAGE_SIZE -1 ,0 ,0 ,0 ,1 ,0 ,0 ,0 ));ia64_psr (regs)->ac =0 ;/* turn off alignment checking */ regs->loadrs =0 ;
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · On Sun, 14 Oct 2001 12:35:54 -0600, [email protected] said:
Don> Short answer: Yes, the GDTD was set up wrong, here's the patch Don> to fix this. (I must be getting better, it only took me a Don> weekend to find the single bit that had to change rather than Don> my typical effort of over a week :-) We were neglecting to set Don> the present bit, an obvious no-no.
Ah, yes, indeed. Good catch!
Don> Long answer: I'm amazed we've gotten as far as we have with Don> this bug. ANY attempt by an IA32 program to load a segment Don> register from the GDT would cause a fault. The only reason we Don> have worked up to now is that the IA64 code sets up all of the Don> segment descriptors manually without reference to the GDT and Don> very few protected mode IA32 programs attempt to load any of Don> the segment registers.
Don> Also, there is a non-zero change that this will fix the problem Don> with Wine trying to run certain programs, you might want to try Don> TurboTax again with this fix in.
I tried it and TurboTax does start up now! It's still pretty crash happy (e.g., "View Forms" kills it), but it's still impressive to watch it.
Does anyone know how well TurboTax works with WINE on a real x86 machine? Does it work without a full windows installation?
Perhaps more significantly, this apparently also was the bug that kept x86 abiword from working.
Thanks,
--david