Re: NForce2 pseudoscience stability testing (2.6.0-test11)

From: Josh McKinney (forming_at_charter.net)
Date: 12/02/03

  • Next message: Jonathan Fors: "Re: [2.6.0-test11]: It doesn't boot with a bootcd"
    Date:	Tue, 2 Dec 2003 16:12:56 -0500
    To: linux-kernel@vger.kernel.org
    
    

    To me the strangest thing is that when I first got this board a month or
    so ago it would hang with APIC or LAPIC enabled. Now it works fine
    without disabling APIC. All I did was update the BIOS and use it for a
    while with APIC disabled. 2.6.0-test9-mm through 2.6.0-test11 all work
    just fine. Still at the same time some people are reporting that it
    works, some are reporting that it doesn't. I probably wouldn't think to
    much of this except I was one of the ones that said APIC causes crashes
    with IDE load, but now it doesn't?

    On approximately Tue, Dec 02, 2003 at 10:13:46AM +0000, ross.alexander@uk.neceur.com wrote:
    > Alistair,
    >
    > I upgraded the BIOS about a week ago to 1007. I personally found it to be
    > less
    > stable than 1006. I don't believe it is a problem with my hardware
    > combination
    > since it has been stable for long periods of time. I was running the SMP
    > kernel
    > simply because I (wrongly) presumed a) you needed it to get the IO-APIC
    > working,
    > and b) it didn't do any harm.
    >
    > It is clear that the UP kernel is considerable more stable than the SMP
    > kernel. This
    > is a very useful fact since it suggests that it is not a problem with the
    > IDE device
    > driver per se. The whole purpose of my testing is to try to determine
    > which options
    > increased the stability and hence highlight where the problem could be.
    >
    > One of the reasons I don't like ACPI is the huge amount of additional
    > complexity
    > it adds and the amount of stuff it could screw up. Now I have not heard
    > that any
    > of the VIA KTxxx based motherboards have any problems. If this is true
    > then the
    > problem does not lie with the LAPIC, since that is in the processor, not
    > the MB.
    > The fact that it seems to only occur with the NForce2 chipset means it
    > could
    > well be some interrupt coming into the LAPIC from Interrupt Bus. However
    > I certainly don't claim to be an expert on this so I could well be talking
    > complete
    > crap.
    >
    > Conclusion: More testing required.
    >
    > Cheers,
    >
    > Ross
    >
    > ---------------------------------------------------------------------------------
    > Ross Alexander "We demand clearly defined
    > MIS - NEC Europe Limited boundaries of uncertainty and
    > Work ph: +44 20 8752 3394 doubt."
    >
    >
    >
    >
    > Alistair John Strachan <s0348365@sms.ed.ac.uk>
    > 28/11/2003 04:46 p.m.
    >
    > To: ross.alexander@uk.neceur.com, "Brendan Howes"
    > <brendan@netzentry.com>
    > cc: linux-kernel@vger.kernel.org
    > Subject: Re: NForce2 pseudoscience stability testing
    > (2.6.0-test11)
    >
    >
    > On Friday 28 November 2003 15:13, ross.alexander@uk.neceur.com wrote:
    > [snip]
    > >
    > > The conclusion to this is the problem is in Local APIC with SMP. I'm
    > not
    > > saying this is actually true
    > > only that is what the data suggests. If anybody wants me to try some
    > > other stuff feel free to suggest
    > > ideas.
    > >
    > > Cheers,
    > >
    > > Ross
    > >
    >
    > It's evidently a configuration problem, albeit BIOS, mainboard revision,
    > memory quality, etc. because I and many others like me are able to run
    > Linux
    > 2.4/2.6 with all the options you tested and still achieve absolute
    > stability,
    > on the nForce 2 platform.
    >
    > My system is an EPOX 8RDA+, with an Athlon 2500+ (Barton) overclocked to
    > 2.2Ghz, and 2x256MB TwinMOS PC3200 dimms. FSB is at 400Mhz, and the ram
    > timings are 4,2,2,2. One might expect such a configuration to be unstable,
    >
    > but it is not.
    >
    > I'm currently running 2.6.0-test10-mm1 with full ACPI (+ routing), APIC
    > and
    > local APIC, no preempt, UP, and everything has been rock-solid, despite
    > the
    > machine being under constant 100% CPU load and fairly active IO load.
    >
    > Also, many others have found that just disabling local apic (and the MPS
    > setting in the BIOS) as well as ACPI solves their problem, so I'm
    > skeptical
    > that SMP really causes *nForce 2 specific* instability.
    >
    > --
    > Cheers,
    > Alistair.
    >
    > personal: alistair()devzero!co!uk
    > university: s0348365()sms!ed!ac!uk
    > student: CS/AI Undergraduate
    > contact: 7/10 Darroch Court,
    > University of Edinburgh.
    >
    >
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html
    > Please read the FAQ at http://www.tux.org/lkml/

    -- 
    Josh McKinney		     |	Webmaster: http://joshandangie.org
    --------------------------------------------------------------------------
                                 | They that can give up essential liberty
    Linux, the choice       -o)  | to obtain a little temporary safety deserve 
    of the GNU generation    /\  | neither liberty or safety. 
                            _\_v |                          -Benjamin Franklin
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Jonathan Fors: "Re: [2.6.0-test11]: It doesn't boot with a bootcd"

    Relevant Pages

    • Re: GRUB module query
      ... config screen for various RAID options - I turn them off and use kernel ... The whole interaction between BIOS, ... case a secondary "on card" bios, and then GRUB, and then Kernel. ... So on boot the BIOS conspire to load the ...
      (Ubuntu)
    • Re: AMD Athlon 64 X2
      ... then appears a kernel trap D just as the desktop begins to appear. ... I tried all of the recent SMP kernels but no luck. ... work with OS/2 SMP and the ones that do are likely very unstable. ... I suspect you may have a problem with the BIOS in the motherboard. ...
      (comp.os.os2.setup.misc)
    • Re: AMD Athlon 64 X2
      ... I tried all of the recent SMP kernels but no luck. ... The best I was able to do was to boot to a hang in the desktop with the blue screen and cursor clock showing which was just a tiny bit farther than the kernel trap D. The problem is definitely in the kernel, perhaps related to the faster-than-before-X2 inter-cpu communication, so I don't think people should plan on running OS/2 SMP on an Athlon X2 anytime soon. ... My expectation at present would be that most Athlon X2 systems will not work with OS/2 SMP and the ones that do are likely very unstable. ... I suspect you may have a problem with the BIOS in the motherboard. ...
      (comp.os.os2.setup.misc)
    • SCSI host adapter "gone" after kernel upgrade
      ... The server has since had problems with spurious hangs and kernel oops, ... I flashed the BIOS ... Disabling SMP was the only configuration difference to the old ... PCI: No IRQ known for interrupt pin A of device 02:0a.0. ...
      (Debian-User)
    • Re: Big-disk woes
      ... >> In the olden days the system still needed the bios to load any boot loader ... >> to Linux (which would talk to the hardware directly and not need the BIOS ... but I seem to remember days where the kernel would be in / and not ...
      (comp.os.linux.setup)