Segmentation fault WAS: SCC causes kernel crash

From: Robert Schelander (idwah@mailit.tunk.net)
Date: Wed Jun 07 2000 - 07:12:07 EEST

  • Next message: Barrett, Peter G: "RE: Linux + Baycom problems..."

    I tried to update my 2.2.10 to 2.2.14.
    Always after running "listen" for an hour I always got an
    "segmentation fault" which crashed my system.

    But maybe this was also a result of an upgrade from SuSE6.2
    to 6.4 which also sucks in my opinion:

    1. I was not able to compile any kernel downloaded from kernel.org
        (maybe the compilers fault)
    2. After upgrading the system didn't know terminal type 'ansi'
        (I always got an error message like: "ansi, unknown terminal type" when
        I wanted to start some pseudo-graphical programms like yast, pico, ect.
        via telnet)
    3. Many other unnice changes of the configuration

    I was lucky to had a backup image of all partitions. Unfortunately 2.2.10
    seems
    to have a isdn4linux bug which causes the ippp0 device to get very slow
    after
    some days online. It's a pity that my system only seems to compile the
    preinstalled 2.2.10 kernelsource

    Robert

    ----- Original Message -----
    From: Bent Bagger <hfawg.ijuwi@veths.no>
    To: <fkoauje@ncannings.fair>
    Sent: Tuesday, June 06, 2000 10:38 AM
    Subject: RE: SCC causes kernel crash

    > For what it is worth: I had similar, but not quite identical, oops' from
    > 2.2.13 and 2.2.14 kernels. It turned out that I had errorneously
    > misconfigured the kernel. The machine is a 33 MHz 486 with standard AT
    > expansion boards. The misconfiguration consisted in my enabling the PCI
    bus
    > code in the kernel. When I changed the kernel configuration and rebuilt
    the
    > kernel, not only disappeared the kernel oops but the machine appeared to
    be
    > twice as fast.
    >
    > Best 73 de Bent/OZ6BL
    >
    >



    This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 03:35:26 EEST