[lkml]   [1996]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectYet another PPP panic, 2.0.8 (completely different machine)
Yet another panic.

486DX2/66, 16m ram, VLB
Kernel 2.0.8 compiled as AOUT
GCC 2.7.2, libc 4.6.27
PPP 2.2.0f (AOUT)
No modules

Note that this machine is *completely* different from our main 2.0.20
machine - AOUT versus ELF, libc 4.6.27 versus 5.3.12, VLB versus PCI,
486 versus Pentium, and even different kernel. The offsets are different
but the stack trace is *exactly* the same, down to the exact executed

I think we can come to several conclusions here:

1) It's not bad hardware. It's not hardware dependent, either.
2) It is 2.0.x kernel independent (at least from 2.0.8 to 2.0.20).
3) It's not related to libc/elf/aout/etc
4) It's ppp related
5) It's 100% repeatable


general protection: 0000
CPU: 0
EIP: 0010:[<0019e6ec>]
EFLAGS: 00010286
eax: fffffffc ebx: 00279220 ecx: 00000128 edx: 00000000
esi: 00000004 edi: 002792f0 ebp: 00000021 esp: 001a4888
ds: 0018 es: 0018 fs: 0000 gs: 0000 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=001a2b74)
Stack: 002792f0 00279220 00867d50 0071e000 00000246 0019e988 002792f0 00279220
00000000 00000001 00867d50 00279388 002792f0 0013e3a6 00867d50 002792f0
00867d50 00279388 00000001 fffffffe 00000001 00000246 0013e67a 00867d50
Call Trace: [<0019e988>] [<0013e3a6>] [<0013e67a>] [<0013e4df>] [<0013e4f9>] [<0011750e>] [<00110f7a>]
[<00115ed6>] [<001161f4>] [<0010b18a>] [<0010aebc>] [<02000000>] [<01800000>] [<001a0018>] [<00110d8b>]
[<00110ae2>] [<00110af0>] [<0010ac05>] [<001a0018>] [<0013002b>] [<0019e558>] [<0019e988>] [<0013e3a6>]
[<0013e67a>] [<0013e4df>] [<0013e4f9>] [<0011750e>] [<00110f7a>] [<00109977>] [<00109985>] [<001099db>]
[<0010aa7a>] [<001096a0>] [<001a0018>] [<001a0018>] [<001094a8>]
Code: c6 00 ff c6 40 01 03 c6 40 02 00 89 e9 88 48 03 56 50 8b 43
Aiee, killing interrupt handler
Using `../' to map addresses to symbols.

>>EIP: 19e6ec <_ppp_dev_xmit_ip+1ac/220>
Trace: 19e988 <_ppp_dev_xmit+e8/130>
Trace: 13e3a6 <_do_dev_queue_xmit+1a6/1e0>
Trace: 13e67a <_dev_tint+6a/a0>
Trace: 13e4df <_dev_transmit+1f/30>
Trace: 13e4f9 <_net_bh+9/120>
Trace: 11750e <_do_bottom_half+3a/94>
Trace: 110f7a <_schedule+3a/2b0>
Trace: 115ed6 <_exit_notify+e2/220>
Trace: 1161f4 <_do_exit+1e0/1f0>
Trace: 10b18a <_die_if_kernel+2c2/2f0>
Trace: 10aebc <_page_fault+174/180>
Trace: 2000000
Trace: 1800000
Trace: 1a0018 <_ei_interrupt+48/260>
Trace: 110d8b <_do_page_fault+29b/320>
Trace: 110ae2 <_si_meminfo+1ba/1c8>
Trace: 110d8b <_do_page_fault+29b/320>
Trace: 10ac05 <error_code+3d/50>
Trace: 1a0018 <_ei_interrupt+48/260>
Trace: 13002b <_sys_fcntl+1db/4c0>
Trace: 19e558 <_ppp_dev_xmit_ip+18/220>
Trace: 19e988 <_ppp_dev_xmit+e8/130>
Trace: 13e3a6 <_do_dev_queue_xmit+1a6/1e0>
Trace: 13e67a <_dev_tint+6a/a0>
Trace: 13e4df <_dev_transmit+1f/30>
Trace: 13e4f9 <_net_bh+9/120>
Trace: 11750e <_do_bottom_half+3a/94>
Trace: 110f7a <_schedule+3a/2b0>
Trace: 109977 <_hard_idle+1f/40>
Trace: 109985 <_hard_idle+2d/40>
Trace: 1099db <_sys_idle+43/80>
Trace: 10aa7a <_system_call+52/80>
Trace: 1096a0 <_init>
Trace: 1a0018 <_ei_interrupt+48/260>
Trace: 1a0018 <_ei_interrupt+48/260>
Trace: 1094a8 <_start_kernel+168/180>

Code: 19e6ec <_ppp_dev_xmit_ip+1ac/220> movb $0xff,(%eax)
Code: 19e6ef <_ppp_dev_xmit_ip+1af/220> movb $0x3,0x1(%eax)
Code: 19e6f3 <_ppp_dev_xmit_ip+1b3/220> movb $0x0,0x2(%eax)
Code: 19e6f7 <_ppp_dev_xmit_ip+1b7/220> movl %ebp,%ecx
Code: 19e6f9 <_ppp_dev_xmit_ip+1b9/220> movb %cl,0x3(%eax)
Code: 19e6fc <_ppp_dev_xmit_ip+1bc/220> pushl %esi
Code: 19e6fd <_ppp_dev_xmit_ip+1bd/220> pushl %eax
Code: 19e6fe <_ppp_dev_xmit_ip+1be/220> movl 0x0(%ebx),%eax
Code: 19e701 <_ppp_dev_xmit_ip+1c1/220> nop
Code: 19e702 <_ppp_dev_xmit_ip+1c2/220> nop

 \ /
  Last update: 2005-03-22 13:37    [W:0.014 / U:1.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site