----- Original Message -----
At 2012-4-25 23:59, Dave Anderson wrote:
> I will put this module on the extension module web page for now.
Hello Dave,
I rebuild a new SLES kernel, and try to figure out the problem you
pointed out. The version I used is 2.6.5-7.308-smp. And then I tried
ipcs module, it seems ipcs command works well, like below.
crash> ipcs -M
SHMID_KERNEL KEY SHMID UID PERMS BYTES NATTCH
STATUS
10027a816a0 00000000 1605632 0 666 90000 1
PAGES ALLOCATED/RESIDENT/SWAPPED: 22/1/0
VFS_INODE: 100268d38e8
SHMID_KERNEL KEY SHMID UID PERMS BYTES NATTCH
STATUS
10027a813a0 00000001 1638401 0 666 90000 1
PAGES ALLOCATED/RESIDENT/SWAPPED: 22/0/0
VFS_INODE: 10025e2a168
SHMID_KERNEL KEY SHMID UID PERMS BYTES NATTCH
STATUS
10027a814a0 00000002 1671170 0 666 90000 1
PAGES ALLOCATED/RESIDENT/SWAPPED: 22/1/0
VFS_INODE: 10025e2a4e8
crash> ipcs
SHMID_KERNEL KEY SHMID UID PERMS BYTES NATTCH
STATUS
10027a816a0 00000000 1605632 0 666 90000 1
10027a813a0 00000001 1638401 0 666 90000 1
10027a814a0 00000002 1671170 0 666 90000 1
SEM_ARRAY KEY SEMID UID PERMS NSEMS
100020787a0 00000000 0 0 666 1
100020786a0 00000001 32769 0 666 1
100020782a0 00000002 65538 0 666 1
MSG_QUEUE KEY MSQID UID PERMS USED-BYTES
MESSAGES
1002f7cd1a0 00001f58 0 0 600 0 0
The problems didn't show on my kernel. So I think the problems do not
come from the edition of SLES, but the modification of the third party.
So I think is it possible to get the debuginfo and core you used to
test.
OK, that's good.
I will send you a link to my files off-list. And perhaps you can
make your SLES files available to me so I can have a "clean"
example?
Thanks,
Dave