Sender: nneul AT delorie DOT com Message-ID: <36D9DAC7.B9927C01@umr.edu> Date: Sun, 28 Feb 1999 18:09:44 -0600 From: Nathan Neulinger <nneul AT umr DOT edu> X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.2-ac3 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgcc AT delorie DOT com Subject: problems with pgcc and linux kernel module (2.2.x) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: pgcc AT delorie DOT com Ok. First let me start off by saying that 99.9% of the time I have no problems at all, but ona few new machines I am having a very serious problem. Most of the machines I have built the recent kernels on have worked fine, except for ones where I load the 'xfs' kernel module that is part of the 'arla' package. When compiling the kernel and loading the arla module I get tons of "SIG: sigpending lied" messages from the kernel and other odd problems with the filesystem that this module provides access to. This occurs when compiling with or without any optimization. If I build either the kernel itself or the arla module using a pgcc patched egcs the problem occurs. I do not know if an unpatched egcs has the problem. The problem is 100% reproducible. As soon as I load arla I get a few of the messages, and then more dependent on the degree of access to the filesystem. infinity(1)>gcc -v Reading specs from /afs/umr.edu/software/egcs11/redhat52/lib/gcc-lib/i686-pc-linux-gnu/pgcc-2.91.60/specs gcc version pgcc-2.91.60 19981201 (egcs-1.1.1 release) The module that gets compiled is relatively small, so if you wanted to take a look at it, that might be reasonable. Please let me know if I can provide any assistance or additional info, for now, I've fallen back to using gcc for all kernel related compiles on the machines that load arla. -- Nathan