Hi all,
I've made some progress over the last day or
so. It appears that sizeof(struct semaphore) is much bigger than
anticipated on this kernel. In fact its 164 bytes according to a kernel
printf, far larger than the 12 longs allocated in lis_semaphore->sem_mem ...
when i replace this array with an actual "struct semaphore" array the system no
longer panics.
Is the "abstraction to keep user drivers from
knowning kernel semaphores look like" really this necessary? Surely the
abstraction could reference a "struct semaphore" at least. I noticed that
I did not need to add any header files to get LiS or my drivers to compile after
making this change.
Unforunately I still do not reach my driver open
routine. Now the system scheduler appears to be corrupted as processes and
threads are no longer scheduled (but ping works so the kernel is running).
The only clue I have, from LIS_DEBUG_OPEN, is that
f_dentry->d_count does not appear to be set ... I see printfs of 1065280112
and other large random values.
Can any kernel guru's given me a clue as where to
look next? Has anyone run LiS on a PPC linux?
Thanks
Ragnar
|
- Re: [Linux-streams] PPC Linux (2.4.7) and LiS 2.13.26 Ragnar Paulson
- Re: [Linux-streams] PPC Linux (2.4.7) and LiS 2.... David Grothe
- Re: [Linux-streams] PPC Linux (2.4.7) and LiS 2.... Brian F. G. Bidulock
- Re: [Linux-streams] PPC Linux (2.4.7) and Li... Ragnar Paulson
- [Linux-streams] LiS-2.14.5 is PPC compatible David Grothe