linux-kernel - Re: Hardware Problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 28 Oct 2006 21:05:16 -0700
From:	Marc Perkel <marc@...kel.com>
To:	Bill Davidsen <davidsen@....com>
CC:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Hardware Problem - Asus A8N-VM CSM



Bill Davidsen wrote:
> Marc Perkel wrote:
>>
>>
>> Langsdorf, Mark wrote:
>>>>> The problem. 2 out of the 4 sees all 4 gigs of ram. The other 2 
>>>>> see only 2.8 gigs of ram. And it's hardware related because in the 
>>>>> bios setup the ones that show 2.8 show it in the bios.
>>>>>
>>>>> The motherboards were not prchased at the same time. All have 
>>>>> different brands of ram. And the processors are different. The 2 
>>>>> that don't see all the ram are the newest ones.
>>>>>
>>>>> I tried swapping ram between one that saw 2.8 gigs and one that 
>>>>> saw 4 gigs and the problem stays with the motherboard.
>>>>> I haven't yet swapped out the processors.
>>>>>
>>>>> So - I'm a little stumped. Can someone point me in the right 
>>>>> direction?
>>>>>       
>>>
>>> Usually, missing memory comes from the PCI I/O hole, or the
>>> IOMMU/AGP/framebuffer overlays.  Does your BIOS have an
>>> options for creating a memory hole or hoisting memory?  If
>>> so, are the settings between the 4G machines different from
>>> the 2.8G machines?
>>>
>>> Also, do you have an IOMMU aperture enabled and if so, how
>>> large?
>>>
>>> Are there any hardware differences between the systems, like
>>> different AGP or PCI graphics cards?
>>>
>>>  
>>>> Answering my own question perhaps. Could it be related to whether 
>>>> or not the processor is a "revision e" chip?
>>>>     
>>>
>>> Possibly, but I'd expect the RevE parts to see more DRAM than
>>> the earlier parts.
>>>
>>>
>>>   
>>
>> I fixed the problem. It wasn't a Revision E issue after all. I just 
>> pulled the battery and when it came up clean it saw all the memory. 
>> Thanks for your help.
>>
> Would have been interesting to use the "reset to factory defaults" 
> option, just to see if some bit isn't set to known state doing that.
>

Actually that's what it tuened out to be. It had nothing to do with 
Revision E.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/