Hi all 

I experienced a problem more than once now. It crashes my box. And I
belive it's the isdn-code.
So here is my config: Redhat 5.2, plain kernel 2.2.5 patched with the
isdn-tgz from suse. (same some weeks ago with 2.2.3). 
The box is used for sending Messages to Cellphones using an old AVM
Fritz ISA-Card. After some days (once it made it 2 weeks) the system
just stops working :(
The only thing I find is this from the logfile (and on console):

Apr 13 12:19:48 wiggum kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000023
Apr 13 12:19:48 wiggum kernel: current->tss.cr3 = 01dbd000, `r3 =
01dbd000
Apr 13 12:19:48 wiggum kernel: *pde = 00000000
Apr 13 12:19:48 wiggum kernel: Oops: 0000
Apr 13 12:19:48 wiggum kernel: CPU:    0
Apr 13 12:19:48 wiggum kernel: EIP:    0010:[<c01a80e6>]
Apr 13 12:19:48 wiggum kernel: EFLAGS: 00010293
Apr 13 12:19:48 wiggum kernel: eax: ffffffff   ebx: c530be40   ecx:
00000001   edx: c7fa0000
Apr 13 12:19:48 wiggum kernel: esi: c530be40   edi: ffffffff   ebp:
c7fa241c   esp: c530be00
Apr 13 12:19:48 wiggum kernel: ds: 0018   es: 0018   ss: 0018
Apr 13 12:19:48 wiggum kernel: Process yaps (pid: 4447, process nr: 71,
stackpage=c530b000)
Apr 13 12:19:48 wiggum kernel: Stack: ffffffff c01b096e c530be40
00000001 c7fa24dc c7fa241c c530bece c530bebc 
Apr 13 12:19:48 wiggum kernel:        00000004 c530be4c 00000001
00000000 c7fa251e c530be40 00000000 00000007 
Apr 13 12:19:48 wiggum kernel:        ffffffff 00000005 ffffffff
30313030 31303033 35323137 30303132 00000031 
Apr 13 12:19:48 wiggum kernel: Call Trace: [<c01b096e>] [<c010e7cb>]
[<c019758c>] [<c01b5023>] [<c01ce0da>] [<c01b5422>] [<c01b16
dd>] 
Apr 13 12:19:48 wiggum kernel:        [<c0199ac2>] [<c01958d5>]
[<c0195770>] [<c0199944>] [<c0128519>] [<c0109a0c>] 
Apr 13 12:19:48 wiggum kernel: Code: 8b 40 24 53 8b 40 18 ff d0 83 c4 04
5b 5e 5f c3 89 f6 83 ec 

and then silence.

yaps is the programme that sends the messages. It uses ttyI4. Since
often the dest. number is busy, more than one yaps tries to use ttyI4
simultaneously, but all but one are blocked (this is how it should be, I
think). Perhaps this leads to the problems?

Could anyone of you solve this ? ;-)

regards
Ren�

Reply via email to