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:	Wed, 06 Jun 2007 17:47:56 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Reinaldo de Carvalho <reinaldow@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Another missing RAM on x86_64

Reinaldo de Carvalho wrote:
> This laptop have a nVidia 10de:0244 with 256Mb of RAM. No shared memory.
> 
> 
> Reinaldo de Carvalho
> 
> 
> 
> 00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express 
> Bridge (rev a2) (prog-if 00 [VGA])
>         Subsystem: Hewlett-Packard Company Unknown device 30b5
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 0
>         Interrupt: pin A routed to IRQ 21
>         Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=16M]
>         Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
>         Region 3: Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
>         [virtual] Expansion ROM at 50000000 [disabled] [size=128K]
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ 
> Queue=0/0 Enable-
>                 Address: 0000000000000000  Data: 0000

It's a bit mysterious, then, where the extra 40-some MB of RAM has gone. 
However, there's not much the kernel can do about it, as the BIOS is not 
telling us about that memory..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ