Georg Wilckens wrote:
> Sorry but the information you are giving is not enough. You have to
> run the oops you posted through ksymoops (comes with the kernel
> sources) and post the output of that program (read
> linux/Documentation/oops-tracing for more information).
Here it is (I hope I got the right part of it):
>>EIP: c01a80e6 <isdn_command+7e/90>
Trace: c01b096e <isdn_tty_dial+162/2f0>
Trace: c010e7cb <timer_interrupt+9b/114>
Trace: c019758c <flush_to_ldisc+110/11c>
Trace: c01b5023 <isdn_tty_parse_at+1bb/524>
Trace: c01ce0da <isac_fill_fifo+10e/154>
Trace: c01b5422 <isdn_tty_edit_at+96/1a0>
Trace: c01b16dd <isdn_tty_write+2dd/354>
Trace: c0199ac2 <write_chan+17e/228>
Code: c01a80e6 <isdn_command+7e/90> 00000000 <_EIP>: <===
Code: c01a80e6 <isdn_command+7e/90> 0: 8b 40 24
movl 0x24(%eax),%eax <===
Code: c01a80e9 <isdn_command+81/90> 3: 53
pushl %ebx
Code: c01a80ea <isdn_command+82/90> 4: 8b 40 18
movl 0x18(%eax),%eax
Code: c01a80ed <isdn_command+85/90> 7: ff d0
call *%eax
Code: c01a80ef <isdn_command+87/90> 9: 83 c4 04
addl $0x4,%esp
Code: c01a80f2 <isdn_command+8a/90> c: 5b
popl %ebx
Code: c01a80f3 <isdn_command+8b/90> d: 5e
popl %esi
Code: c01a80f4 <isdn_command+8c/90> e: 5f
popl %edi
Code: c01a80f5 <isdn_command+8d/90> f: c3
ret
Code: c01a80f6 <isdn_command+8e/90> 10: 89 f6
movl %esi,%esi
Code: c01a80f8 <isdn_all_eaz+0/34> 12: 83 ec 00
subl $0x0,%esp
>
> > and then silence.
> >
> > yaps is the programme that sends the messages. It uses ttyI4. Since
>
> The message is coming directly from the kernel and shows a kernel BUG!
I just wanted to give enough information (though it wasn't). If such a
message wouldn't come from the kernel, it would also be a kernel bug ;-)
>
> > 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?
>
> Dunno... shouldn't cause an oops though.
>
> > Could anyone of you solve this ? ;-)
>
> Someone might given the output of ksymoops.
OK. Try your luck.
btw: yesterday that thing stopped working again, but this time without
any output in the logs. It's odd, perhaps really a hardware problem, but
the other oops I found before (it was 2.2.3) was also in the isdn-code.
Regards
Ren�
