The timeout default was 10000 which apparently not enough time and caused a
Hope this helps someone.
I'm experiencing a strange problem with a kernel module I wrote
(AtariSIO, see http://www.horus.com/~hias/atari/ ).
One system, my laptop running kernel 2.2.19, is doing fine. The
kernel was compiled with gcc 2.95.4 (from debian woody).
If I compile my module with gcc 2.95.4 (debian woody), 3.0 (also
debian woody) or 3.2.2 (vanilla sources from gcc.gnu.org),
everything runs smoothly.
But I'm having troubles on my other machine running kernel
2.4.18 (compiled with the same gcc 2.95.4 as the 2.2 kernel):
Using gcc 2.95.4 works fine, but if I use any of the mentioned
gcc-3.x versions, my system completely locks up (not even the
SysReq key works any more), as soon as the interrupt routine
Here's some more information about my kernel module:
atarisio accesses the 16550 chip directly and processes some
parts of the Atari 8bit SIO protocol in kernel mode. It's a
quite simple driver and reacts to character receive/send
and modem status line change interrupts of the 16550.
Both of my machines are running debian, potato on my old
laptop, and woody on my other machine.
Now here's my question:
Does someone have an idea what might be causing these crashes,
and what might be a solution to avoid them?
I googled for a while and read that at least the vmware modules
had to be compiled with the same gcc version as it was used to
compile the kernel. Some other postings mentioned that gcc 3.x
isn't recommended at all for compiling the kernel, while again
some other postings reported success.
At the moment I think there are (at least) the following possibilites:
1) it's a bug in gcc 3.x that only shows up with 2.4 kernels
2) there's still a bug hiding in my own module code
so long & thanks in advance for any comments,