5.2-current does not allow login and panics with modified memory after free

From: Artem Koutchine (matrix_at_itlegion.ru)
Date: 04/02/04

  • Next message: Sean McNeil: "natd no longer working" 
    To: <freebsd-current@freebsd.org>
Date: Fri, 2 Apr 2004 16:03:08 +0400

    Hello!

    I am trying to run 5.2-CURRENT (cvsupped and rebuild apr 1) on the following
    server:

    Supermicro DPE-G2 motherboard
    DUAL XEON 2.66Ghz (HT enabled)
    2GB RAM
    4 SATA SEAGTE 120GB DRIVES
    3WARE 8506-4LP SATA RAID5 CONTROLLER

    SATA drivers are joint into a single RAID5 array which is seens
    as twe0.

    3dm is installed.

    The box ran half a day and a night just fine. After that it was shutdown
    correctly and after a couple of hours turned on.

    I have heared (leds do not work due to connector incompatibility with
    supermicro case) high hdd activity for some time, but all filesysrems
    were marked as clean. I tried to login but i could not because after i
    types 'root' at the login nothing happened at all. Just a blinking cursor.
    However, the box was not hanging - screensaver appeared after some
    time and i can type on tty and also swicth vttys and use scroll lock to
    scroll
    boot messages. 3DM did not respond via web. So, i waited 4 hours and
    rebooted.

    After reboot i can logon but after several requests to RAID status via
    web (3dm) i got the following on the console:

    twe0: TWEIO_GET_PARAM failed for 0x402/0x3/16

    Then after a minute or two the following happened:

    Memory modified after free 0x788f400(508) val=20202020 @ 0xe788f400
    panic: Most recently used by devbuf
    at line 128 in file /usr/src/sys/udm_dbg.c
    cpu=0;
    Debugger ("panic")
    Stopped at Debugger +0.46: xchgl %ebx, in_Debugger.0

    and i typed 'c' in debugger:

    the system started to shutdown and here is what i saw:

    twe0: failed to delete unit 0
    stray irq9

    Is this all a twe driver problem or general 5.2-CURRENT instability?
    Any ideas what happened in two cases and how to avoid it or/and
    solve the problems?

    Regards,
    Artem Kuchin
    General Director of IT Legion Ltd.
    Russia, Moscow
    www.itlegion.ru
    matrix@itlegion.ru
    +7 095 232-0338

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Sean McNeil: "natd no longer working"

    Relevant Pages

    • 5.2-current does not allow login and panics with modified memory after free
      ... Supermicro DPE-G2 motherboard ... 3WARE 8506-4LP SATA RAID5 CONTROLLER ... SATA drivers are joint into a single RAID5 array which is seens ...
      (freebsd-questions)
    • Re: Install XP on blank partition on Vista machine
      ... relate that to SATA is obscure. ... What Medion say is 'we do not have SATA drivers available as the machine ... I have created a blank partition using Paragon Hard Disk Manager, ...
      (microsoft.public.windowsxp.general)
    • Re: External floppy drives vs winxp install
      ... and the MS install will ONLY accept drivers from the A: ... And if all you have available is a SATA HD, ... Is it possible to boot a USB drive as A:??? ... circumvent this particular problem of SATA drivers w/o a FDD. ...
      (alt.comp.hardware.pc-homebuilt)
    • Re: Unable to install XP Pro - BlueScreen!
      ... Which is where you need to provide SATA drivers to Setup. ... "Gary S. Terhune" wrote: ... I am attempting to install it from CD to the formatted HD... ...
      (microsoft.public.windowsxp.general)
    • Re: Putting previously purchased copy of XP on another laptop
      ... have no desire to upgrade to Vista. ... Whats the deal with registering with microsoft when I try to install ... One of the most important things is getting SATA drivers since XP ... My desktop system uses an ASUS board, it has only SATA hard disks, and there is no need to provide no SATA drivers during the install. ...
      (microsoft.public.windowsxp.general)