Re: Problems with AMD64 and 8 GB RAM?

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 03/31/05

  • Next message: Dag-Erling Smørgrav: "Re: file /usr/src/etc/rc.d/network is not installed"
    Date: Thu, 31 Mar 2005 07:57:27 -0500
    To: Scott Long <scottl@samsco.org>
    
    

    On Mar 31, 2005, at 12:27 AM, Scott Long wrote:

    > Jon Noack wrote:
    >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote:
    >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote:
    >>>
    >>>> Greg 'groggy' Lehey wrote:
    >>>>
    >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote:
    >>>>>
    >>>>>> On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote:
    >>>>>>
    >>>>>>>> lapic0: LINT1 trigger: edge
    >>>>>>>> lapic0: LINT1 polarity: high
    >>>>>>>> lapic1: Routing NMI -> LINT1
    >>>>>>>> lapic1: LINT1 trigger: edge
    >>>>>>>> lapic1: LINT1 polarity: high
    >>>>>>>> -ioapic0 <Version 0.3> irqs 0-23 on motherboard
    >>>>>>>> +ioapic0 <Version 0.0> irqs 0-23 on motherboard
    >>>>>>>> cpu0 BSP:
    >>>>>>>> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR:
    >>>>>>>> 0x0fffffff
    >>>>>>>> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR:
    >>>>>>>> 0x000001ff
    >>>>>>
    >>>>>>
    >>>>>> This shows that in the - case the APIC is broken somehow (0.0
    >>>>>> isn't a
    >>>>>> valid I/O APIC version).
    >>>>>
    >>>>>
    >>>>> You mean the + case, I suppose. Yes, that's what I suspected.
    >>>>>
    >>>>>
    >>>>>> It would seem that the system has mapped RAM over top of the I/O
    >>>>>> APIC perhaps?
    >>>>>
    >>>>>
    >>>>> That's what I suspected too, but imp doesn't think so.
    >>>>
    >>>>
    >>>> I'd be more inclined to believe that there is an erroneous mapping
    >>>> by the OS, not that things are fundamentally broken in hardware.
    >>>
    >>>
    >>> Agreed. This has been my favourite hypothesis all along. But isn't
    >>> that what jhb is saying?
    >>>
    >>>> Your SMAP table shows everything correctly. It's becoming hard to
    >>>> break through your pre-concieved notions here and explain how things
    >>>> actually work.
    >>>
    >>>
    >>> No, there's nothing to break through. I think you're just having
    >>> problems
    >>>
    >>> 1. expressing yourself, and
    >>> 2. understanding what I'm saying.
    >>>
    >>> I have no preconceived notions. All I can see here is an
    >>> antagonistic
    >>> attitude on your part. What's the problem? You'll recall from my
    >>> first message that I asked for suggestions about how to approach the
    >>> issue. jhb provided some; you haven't so far. From what you've
    >>> written, it's unclear whether you disagree with jhb or not. If you
    >>> do, why? If you don't, what's your point here?
    >>>
    >>>>>> It would be interesting to see the contents of your MADT to see if
    >>>>>> it's trying to use a 64-bit PA for your APIC.
    >>>>>
    >>>>>
    >>>>> Any suggestions about how to do so?
    >>>>
    >>>>
    >>>> man acpidump
    >>>
    >>>
    >>> How do you run that on a system that won't boot?
    >> You said the system worked with 4 GB (albeit detecting only 3.5 GB).
    >> My perception of this whole ACPI thing is that it is fixed in your
    >> BIOS (although it can be overridden by the OS). As such, the amount
    >> of RAM you have in the machine shouldn't change acpidump results. Is
    >> that not correct?
    >> Jon
    >
    > This is absolutely correct.

    It might though. Notice the change in APIC version with 4GB of RAM vs
    8GB. The APIC hardware is the same, so that's already indicative of
    something fishy going on. I think that his APIC address is correct
    though as otherwise no interrupts at all would work and it wouldn't
    claim to have 24 IRQs on the APIC in both cases. One can always boot
    an i386 non-PAE kernel with 8GB in the machine and get an acpidump
    though.

    -- 
    John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
    "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
    

  • Next message: Dag-Erling Smørgrav: "Re: file /usr/src/etc/rc.d/network is not installed"

    Relevant Pages

    • Re: Extra RAM Installation Blues Vol 3
      ... of Info that you had found about the RAM Modules & BIOS/Motherboard ... If it was just WinXP, it might have been worth doing another Install ... It must be the BIOS that does this ... Manually Set the various Figures & Settings to be used. ...
      (uk.people.silversurfers)
    • Re: P5N32-SLI DL
      ... I am on my third motherboard an 6th set of ram, I also tried patriot DDR 2G8000 and this fails as well. ... In all cases the system locks up after a while and when I run Microsoft's Ram tester I get errors on the LDAP test on the third pass and every pass after that. ... I have loaded the latest beta bios and that has improved things slightly but the system still locks up and the memory tester fails again on the random LDAP test but less frequently. ... Good stability once you get enough power and cooling. ...
      (alt.comp.periphs.mainboard.asus)
    • Re: New M2A-VM HDMI, Cant get it to start
      ... As I had the screen paused to read off the BIOS version, ... owners manual says for RAM sockets (one stick in A1, ... Now the lights come on, the drives start spinning, but no video comes ... CPU, heatsink/fan, motherboard, no RAM, no video, no disk, computer ...
      (alt.comp.periphs.mainboard.asus)
    • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
      ... They can be useful at times...for instance, if you've got the RAM to spare, ... >>> of network transparency in Linux. ... > using the real-mode BIOS to tell me what hardware is attached and what ... many OSes simply call the BIOS "memory size" routines before switching ...
      (alt.lang.asm)
    • Re: Extra RAM Installation Blues Vol 2
      ... >>> Slot, along with various esoteric Info, such as the RAM Timings etc. ... >> and even gives the manufacturer. ... > & the Memory Timings etc... ... along with the BIOS & Chipset ...
      (uk.people.silversurfers)