Re: Big problem with linux-2.0.33, gcc-2.8.0 and iopl()

von Essen, Matthias (VON_ESSEN@ntn04.FEV.de)
Mon, 6 Apr 1998 16:03:38 +0200


Perhaps this helps:

(Taken from egcs-faq:)
You may get errors with the X driver of the form
_X11TransSocketUNIXConnect: Can't connect: errno = 111

It's a kernel bug. The function sys_iopl in arch/i386/kernel/process.c
does an illegal hack which used to work but is now broken since GCC
optimizes more aggressively . The newer 2.1.x kernels already have a fix
which should also work in 2.0.32.

-M
_____
Mathias von Essen ("`-''-/").___..--''"`-._ Staff Engineer
von_essen@fev.de `o_ o ) `-. ( ).`-.__.`) FEV Motorentechnik
T +49 241 5689 316 (_Y_.)' ._ ) `._ `. ``-..-' GmbH & Co. KG
F +49 241 5689 119_..`--'_..-_/ /--'_.' .' Neuenhofstr. 181
(il).-'' (li).' ((!.-' 52078 Aachen
Germany
***** real men use Linux *****
http://www.fev-et.com

> Need URGENT help!
> I upgraded to gcc 2.8.0 and after a kernel recompilation,
>the X refused to startup -- Xserver core dumped! I traced the problem
>up to an outb() call. The problem is related with the iopl()
>call. After an iopl(3), any inb() causes a seg fault! The same inb()
>preceeded by an appropriate ioperm() works fine. I don't have a clue
>what is happening. Any help is greatly appreciated.
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu