Re: system lockup - ata spurious interrupts - somehow updated

From: Putinas Piliponis (putinas.piliponis_at_icnspot.net)
Date: 03/21/04

  • Next message: Søren Schmidt: "Re: system lockup - ata spurious interrupts - somehow updated" 
    To: <current@freebsd.org>
Date: Sun, 21 Mar 2004 12:59:05 +0200

    As for me, it looks what ata code is not correctly handling more then one
    ata controller. If I set in bios compatible mode, and I have only P-ATA+
    S-ATA, everything works fine, I can boot in verbose mode, no spurious
    interrupts at all. If I set in bios as bios default Enchanced mode for S-ATA
    then I still can boot in verbose mode, I see plenty of spurious interrupts
    on ata2 and ata3 controllers, but system is still continues booting. If I
    set
    enchanced
    mode for S-ATA + P-ATA I cannot boot either in verbose mode or either in
    normal mode. System gets stuck forever ( or at least for long time ) after I
    see:
    "Mounting root from ufs:ad8s3a".
    and if I boot then in verbose mode, I see nonstopable spurious interrupts on
    ata2, ata3, ata4 and ata5.

    This is also could explain, why 5.2.1 is still stable with 4 ide drives,
    and continuesly freezing or panicing with 6 ( or more I guess ) ide drives.
    and as well why for some people configuration is working, either they use
    4 drives not on all different channels, but some of them maybe on same
    channel ( again my guess ).

    ----- Original Message -----
    From: "Elliot Finley" <lists@efinley.com>
    To: "Alexander Mueller" <alex@6by9.org>; <freebsd-current@freebsd.org>
    Sent: Saturday, March 20, 2004 5:29 PM
    Subject: Re: system lockup - ata related and spurious interrupts

    >
    > ----- Original Message -----
    > From: "Alexander Mueller" <alex@6by9.org>
    > To: <freebsd-current@freebsd.org>
    > Sent: Friday, March 19, 2004 6:26 PM
    > Subject: system lockup - ata related and spurious interrupts
    >
    >
    >> I can't offer you any help but at least I can tell you that I'm
    >> experiencing exactly the same two problems: TIMEOUT - WRITE_DMA
    >> when hyperthreading is enabled and inability to reboot or power
    >> off when hyperthreading is disabled. My hardware is similar to
    >> yours: Asus P4C800E Deluxe with P4 3.0 GHz using the onboard
    >> SATA controller integrated into the ICH5. My hard disk is a
    >> WD Raptor 740GD. Currently nobody seems to take care of this
    >> problem although there must be quity a lot of people out there
    >> running into similar troubles.
    >
    > plus one.
    >
    > Elliot
    >
    > _______________________________________________
    > 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"
    >
    >

    _______________________________________________
    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: Søren Schmidt: "Re: system lockup - ata spurious interrupts - somehow updated"

    Relevant Pages

    • Re: 2.6.11 AC patch CD/DVD issues
      ... there are no arrays defined as such and the raid bios defaults to pass ... through (ata) mode as if having selected this in the bios. ... > connected to the controller without issue as far as i can tell. ...
      (Linux-Kernel)
    • Re: NForce2 pseudoscience stability testing (2.6.0-test11)
      ... doesnÿt the kernel get to ... Bios revision? ... 00:00.0 Host bridge: nVidia Corporation nForce2 AGP ... 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev ...
      (Linux-Kernel)
    • Re: SIL 3112a Controller Issues....
      ... I'm still kind of thinking that the Intel controller _should_ be OK given my ... There are known issues with the earlier nvidea chip that uses Active ... The mainboard BIOS is the latest and the SIL BIOS (that's integrated into ... A SIL3112 on a motherboard, is handled a bit differently than a SIL3112 ...
      (microsoft.public.windowsxp.general)
    • [PATCH 2.4] decrypt/update ide help entries
      ... This add-on card is a bootable PCI UDMA controller. ... happen if the BIOS revisions of all installed cards do ... Promise FastTrak LP/TX2/TX4 ...
      (Linux-Kernel)
    • RE: Can FreeBSD safely use a (un-booted from) drive that is invisible to the BIOS?
      ... ata controler but have HD on wrong ribbon nipple to match master ... ad0 is the boot drive. ... It is recognized by the BIOS, obviously, ... ad2 is the only device on the second controller and it is definitely ...
      (freebsd-questions)