This happens everytime i try to load an application of ours that
uses shmem for syslog...

Jeff Dike wrote:

>dbahi@enterasys.com said:
>
>
>>i know things are hot and heavy in 2.6 but i hope somebody can spare a
>>thought about this panic i'm struggling to understand.
>>
>>
>
>Is this easily reproduced?
>
>The stack isn't ringing any bells with me, particularly since none of my code
>appears on the stack until the bug has already happened.
>
>				Jeff
>
>
>

--
db