Problem with tar, make, date, df, ls, etc. - Debian

This is a discussion on Problem with tar, make, date, df, ls, etc. - Debian ; Hi Since yesterday around 3 pm, I have a problem with my debian machine. The commands df, date, ls -l, make, tar don't work anymore. I've found the following in /var/log/messages: For df: Dec 17 15:00:09 waaghaals kernel: Unable to ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Problem with tar, make, date, df, ls, etc.

  1. Problem with tar, make, date, df, ls, etc.

    Hi

    Since yesterday around 3 pm, I have a problem with my debian machine.
    The commands df, date, ls -l, make, tar don't work anymore. I've found
    the following in /var/log/messages:

    For df:
    Dec 17 15:00:09 waaghaals kernel: <1>Unable to handle kernel NULL
    pointer dereference at virtual address 0000010c
    Dec 17 15:00:09 waaghaals kernel: printing eip:
    Dec 17 15:00:09 waaghaals kernel: 58c0106c
    Dec 17 15:00:09 waaghaals kernel: Oops: 0002
    Dec 17 15:00:09 waaghaals kernel: CPU: 0
    Dec 17 15:00:09 waaghaals kernel: EIP:
    0010:[agp_frontend_cleanup+1488982124/-1072693248] Not tainted
    Dec 17 15:00:09 waaghaals kernel: EFLAGS: 00010293
    Dec 17 15:00:09 waaghaals kernel: eax: 0000010c ebx: c3b4a000 ecx:
    00000054 edx: 00000018
    Dec 17 15:00:09 waaghaals kernel: esi: bffffd48 edi: 40132ff4 ebp:
    bffff498 esp: c3b4bfc0
    Dec 17 15:00:09 waaghaals kernel: ds: 0018 es: 0018 ss: 0018
    Dec 17 15:00:09 waaghaals kernel: Process df (pid: 2786,
    stackpage=c3b4b000)
    Dec 17 15:00:09 waaghaals kernel: Stack: c0106be3 08052058 00000054
    bffff4bc bffffd48 40132ff4 bffff498 0000010c
    Dec 17 15:00:09 waaghaals kernel: 0000002b 0000002b 0000010c
    400c8a33 00000023 00000246 bffff44c 0000002b
    Dec 17 15:00:09 waaghaals kernel: Call Trace: [system_call+51/56]
    Dec 17 15:00:09 waaghaals kernel:
    Dec 17 15:00:09 waaghaals kernel: Code: Bad EIP value.

    For date:
    Dec 18 04:00:01 waaghaals kernel: <1>Unable to handle kernel paging
    request at virtual address 08e8c358
    Dec 18 04:00:01 waaghaals kernel: printing eip:
    Dec 18 04:00:01 waaghaals kernel: 08e8c358
    Dec 18 04:00:01 waaghaals kernel: Oops: 0000
    Dec 18 04:00:01 waaghaals kernel: CPU: 0
    Dec 18 04:00:01 waaghaals kernel: EIP:
    0010:[agp_frontend_cleanup+149472088/-1072693248] Not tainted
    Dec 18 04:00:01 waaghaals kernel: EFLAGS: 00010293
    Dec 18 04:00:01 waaghaals kernel: eax: 00000109 ebx: c30f2000 ecx:
    bffffe08 edx: 00000018
    Dec 18 04:00:01 waaghaals kernel: esi: 00000000 edi: 00000000 ebp:
    bffffd18 esp: c30f3fc0
    Dec 18 04:00:01 waaghaals kernel: ds: 0018 es: 0018 ss: 0018
    Dec 18 04:00:01 waaghaals kernel: Process date (pid: 12274,
    stackpage=c30f3000)
    Dec 18 04:00:01 waaghaals kernel: Stack: c0106be3 00000000 bffffe08
    40025ff4 00000000 00000000 bffffd18 00000109
    Dec 18 04:00:01 waaghaals kernel: 0000002b 0000002b 00000109
    4002210c 00000023 00000246 bffffd08 0000002b
    Dec 18 04:00:01 waaghaals kernel: Call Trace: [system_call+51/56]
    Dec 18 04:00:01 waaghaals kernel:
    Dec 18 04:00:01 waaghaals kernel: Code: Bad EIP value.

    for ls -l:
    Dec 18 17:17:13 waaghaals kernel: <1>Unable to handle kernel paging
    request at virtual address 08e8c358
    Dec 18 17:17:13 waaghaals kernel: printing eip:
    Dec 18 17:17:13 waaghaals kernel: 08e8c358
    Dec 18 17:17:13 waaghaals kernel: Oops: 0000
    Dec 18 17:17:13 waaghaals kernel: CPU: 0
    Dec 18 17:17:13 waaghaals kernel: EIP:
    0010:[agp_frontend_cleanup+149472088/-1072693248] Not tainted
    Dec 18 17:17:13 waaghaals kernel: EFLAGS: 00010293
    Dec 18 17:17:13 waaghaals kernel: eax: 00000109 ebx: c2f2e000 ecx:
    bffff2e8 edx: 00000018
    Dec 18 17:17:13 waaghaals kernel: esi: 00000000 edi: 4014d7a0 ebp:
    bfffe828 esp: c2f2ffc0
    Dec 18 17:17:13 waaghaals kernel: ds: 0018 es: 0018 ss: 0018
    Dec 18 17:17:13 waaghaals kernel: Process ls (pid: 915,
    stackpage=c2f2f000)
    Dec 18 17:17:13 waaghaals kernel: Stack: c0106be3 00000000 bffff2e8
    40025ff4 00000000 4014d7a0 bfffe828 00000109
    Dec 18 17:17:13 waaghaals kernel: 0000002b 0000002b 00000109
    4002210c 00000023 00000246 bfffe818 0000002b
    Dec 18 17:17:13 waaghaals kernel: Call Trace: [system_call+51/56]
    Dec 18 17:17:13 waaghaals kernel:
    Dec 18 17:17:13 waaghaals kernel: Code: Bad EIP value.

    Google doesn't gave me any solutions to this problem, using loads of
    keywords from these messages.

    Using strace I tried to pinpoint the problem to a specific call. This
    came out for most commands:
    clock_gettime(CLOCK_REALTIME,
    +++ killed by SIGSEGV +++
    except df:
    statfs64("/", 84,
    +++ killed by SIGSEGV +++

    Some information about the system
    Debian Testing with kernel 2.4.23
    cat /proc/iomem
    00000000-0009fbff : System RAM
    0009fc00-0009ffff : reserved
    000a0000-000bffff : Video RAM area
    000c0000-000c7fff : Video ROM
    000f0000-000fffff : System ROM
    00100000-09ffffff : System RAM
    00100000-00209dc0 : Kernel code
    00209dc1-002818bf : Kernel data
    d0000000-d1ffffff : PCI Bus #01
    d0000000-d0ffffff : NVidia / SGS Thomson (Joint Venture) Riva128
    d2000000-d2ffffff : Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
    d3000000-d3ffffff : PCI Bus #01
    d3000000-d3ffffff : NVidia / SGS Thomson (Joint Venture) Riva128
    ffff0000-ffffffff : reserved
    cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 5
    model name : Celeron (Covington)
    stepping : 0
    cpu MHz : 300.685
    cache size : 32 KB
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
    cmov pat pse36 mmx fxsr
    bogomips : 599.65
    cat /proc/pci
    PCI devices found:
    Bus 0, device 0, function 0:
    Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
    (rev 2).
    Master Capable. Latency=32.
    Prefetchable 32 bit memory at 0xd2000000 [0xd2ffffff].
    Bus 0, device 1, function 0:
    PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev
    2).
    Master Capable. Latency=64. Min Gnt=136.
    Bus 0, device 7, function 0:
    ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 2).
    Bus 0, device 7, function 1:
    IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 1).
    Master Capable. Latency=32.
    I/O at 0xf000 [0xf00f].
    Bus 0, device 7, function 2:
    USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 1).
    IRQ 11.
    Master Capable. Latency=32.
    I/O at 0xe000 [0xe01f].
    Bus 0, device 7, function 3:
    Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 2).
    IRQ 9.
    Bus 0, device 9, function 0:
    Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
    (rev 0).
    IRQ 11.
    I/O at 0xe400 [0xe41f].
    Bus 1, device 0, function 0:
    VGA compatible controller: NVidia / SGS Thomson (Joint Venture)
    Riva128 (rev 16).
    IRQ 10.
    Master Capable. Latency=32. Min Gnt=3.Max Lat=1.
    Non-prefetchable 32 bit memory at 0xd0000000 [0xd0ffffff].
    Prefetchable 32 bit memory at 0xd3000000 [0xd3ffffff].

    Is this a known problem? Is there something I can do to solve it
    (without tar, apt-get doesn't work)? Is it a hardware problem and how
    can I find out which hardware causes it? A knoppix cd (3.6) didn't gave
    any problems at all, strange enough.

    I hope you guys can help me out here.

    Thijs


  2. Re: Problem with tar, make, date, df, ls, etc.

    I found out the problem after a tip from a Dutch newsgroup. The machine
    had the SuckIt rootkit installed in /usr/share/locale/sk/.sk12 and is
    now offline for a new install.

    Thijs


+ Reply to Thread