Re: Kernel-2.4.7 Oops

From: Kjell Jarl (apez.kdmffts@wmcohs.com)
Date: Sun Jan 06 2002 - 18:55:41 EET

  • Next message: Sandor Dibuz: "unregister_netdevice ?"

    I also have problems, with many kernels, with panics. Thought it was the
    USCC driver, but in 2.4.13 which I now use there should be patches in
    the driver.

    It seems to occur when ax25 netrom disconnects, possibly ending node or
    call program simultanesly and writing to log on disc.

    I think I saw something about 2.4.19 having some more fixes?
    73
    Kjell, sm7gvf

    "Wilson G. Hein" wrote:
    >
    > Hello all,
    >
    > I've been recieving the following kernel oops. I initially thought it was
    > being caused by beacon, but now believe it's something else ax25 related.
    > THinking back, I only started recieving these oops's since I compiled ax25
    > into the kernel. Plus I'm currently running the machine without running any
    > of the ax25 stuff and all has been stable thus far.
    >
    > System
    > Pentium 233 MMX with 128MB/PC100 sdram
    > RedHat Linux 7.2
    > kernel-2.4.7-10 and source
    > libax25-0.0.7-2
    > ax25-tools-0.0.6-2
    > ax25-apps-0.0.4-3
    > gcc-2.96-98
    > all from rpm
    >
    > Unable to handle kernel paging request at virtual address 08e25210
    >
    > *pde = 00000000
    > Oops: 0000
    > CPU: 0
    > EIP: 0010:[<08e25210>]
    > EFLAGS: 00010002
    > eax: 00000000 ebx: e27fccb8 ecx: 00000001 edx: 00000003
    > esi: c39e6ce0 edi: c27fcc9f ebp: 00000001 esp: c0265ed8
    > ds: 0018 es: 0018 ss: 0018
    > Process swapper (Pid: 0, Stackpage = c0265000)
    > Stack: 00000001 c11c1800 00000086 00000086 c27fccb8 c11b19c0 00000008
    > 00000001
    > c017e453 c27fcca0 00000001 c11b19c0 c11b6560 00000001 00000046 c01891c4
    > c11b19c0 00000001 c02d6d40 00000000 c11b19c0 c02d6c50 c02d6c10 c01932b6
    > CallTrace: [<c017e453>] [<c01891c4>] [<c01932b6>] [<c018ab20>] [<c0193250>]
    > [<c01082ba>] [<c010843b>] [<c0105380>] [<c021d6c8>] [<c0105380>]
    > [<c01053a4>] [<c0105412>] [<c0105000>]
    >
    > Code: Bad EIP value
    > <0> Kernel panic: Aiee, killing interrupt handler!
    > In interrupt handler - not syncing
    >
    > I believe there may be patches that may work, but in looking though my
    > archives there may be more then one. Or after applying one it broke
    > something else that the second patches?
    >
    > Or it nothing related:-0
    >
    > Help!
    >
    > Thanks in advance and anything I can do to help trouble shoot let me know.
    >
    > Wilson
    > odoebh.ahnmgp@median.is
    >
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    > the body of a message to iiula@rele.tunk.net
    > More majordomo info at http://vger.kernel.org/majordomo-info.html
    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to uknoe@victoriagas.com
    More majordomo info at http://vger.kernel.org/majordomo-info.html



    This archive was generated by hypermail 2b30 : Sun Jan 06 2002 - 19:00:37 EET