Displaying 20 results from an estimated 1000 matches similar to: "Memory problems with CentOS box"
2006 Oct 11
41
ZFS Inexpensive SATA Whitebox
All,
So I have started working with Solaris 10 at work a bit (I''m a Linux
guy by trade) and I have a dying nfs box at home. So the long and short of
it is as follows: I would like to setup a SATAII whitebox that uses ZFS as
its filesystem. The box will probably be very lightly used, streaming media
to my laptop and workstation would be the bulk of the work. However I do
have quite a
2005 Jun 22
11
Opteron Mobo Suggestions
I've been planning to build a dual Opteron server for awhile. I'd like
to get people's suggestions on a suitable motherboard.
I've looked at the Tyan K8SE (S2892) and K8SRE (S2891) but would like to
find more Linux-specific experiences with these boards.
Some features I expect are at least 4 SATA (SATA-300?) ports, serial
console support in the BIOS, USB 2.0 and IEEE-1394
2003 Apr 08
1
Panic asus a7m266 with 2 512Mb PC2400 DDR333 memory
Hi,
Last thursday, I installed (20/Mar/2003) 2 kingston valueram
512Mb PC2400 DDR333 (KVR333X64C25/512) sticks on my A7M266 running
up to date -STABLE. The system became unstable right after installation,
any form of system load triggered a kernel panic: "Page Fault While
In Kernel Mode". My main test was the usual 'make buildworld'.
I became worried about the quality of the
2004 Dec 20
7
NMI issues...
I have read thru what other users have tried in this list when they have
experienced seemingly similar issues to what I have, without success. I
suspect there might be an issue regarding both the X100P and TDM04b cards
being used in an Intel SE7525GP2 motherboard, as I had to even wait for a
BIOS update from Intel in order to utilize my 3ware 9500 SATA raid
controller on it (3ware Kb -->
2020 May 14
1
[virtio-dev] [PATCH v3 00/15] virtio-mem: paravirtualized memory
On 14.05.20 13:10, David Hildenbrand wrote:
> On 14.05.20 12:12, David Hildenbrand wrote:
>> On 14.05.20 12:02, teawater wrote:
>>>
>>>
>>>> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ???
>>>>
>>>> On 14.05.20 08:44, teawater wrote:
>>>>> Hi David,
>>>>>
>>>>> I got a
2020 May 14
2
[virtio-dev] [PATCH v3 00/15] virtio-mem: paravirtualized memory
On 14.05.20 12:02, teawater wrote:
>
>
>> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ???
>>
>> On 14.05.20 08:44, teawater wrote:
>>> Hi David,
>>>
>>> I got a kernel warning with v2 and v3.
>>
>> Hi Hui,
>>
>> thanks for playing with the latest versions. Surprisingly, I can
>> reproduce even by
2020 May 14
2
[virtio-dev] [PATCH v3 00/15] virtio-mem: paravirtualized memory
On 14.05.20 12:02, teawater wrote:
>
>
>> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ???
>>
>> On 14.05.20 08:44, teawater wrote:
>>> Hi David,
>>>
>>> I got a kernel warning with v2 and v3.
>>
>> Hi Hui,
>>
>> thanks for playing with the latest versions. Surprisingly, I can
>> reproduce even by
2010 Jun 22
4
New kernel causes hardware error?
I have recently upgraded to 2.6.18-194.3.1.el5 and within several days
the machine crashed with the following error (repeating in mcelog):
MCE 0
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 2 BANK 8 MISC 41
MCG status:
MCi status:
Error overflow
Uncorrected error
MCi_MISC register valid
Processor context corrupt
MCA: MEMORY CONTROLLER AC_CHANNEL0_ERR
2020 Jun 16
4
NVDIMM sizes and DIMM hot plug
Hi,
I've found out that NVDIMM size and label size matter for regular
(non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the
guest OS will not accept the hot plugged memory and will complain with
messages such as
Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000
The start address above is also reported within <memory> element of the
hot
2020 Apr 30
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> On 30.04.20 17:38, Eric W. Biederman wrote:
>> David Hildenbrand <david at redhat.com> writes:
>>
>>> Some devices/drivers that add memory via add_memory() and friends (e.g.,
>>> dax/kmem, but also virtio-mem in the future) don't want to create entries
>>> in /sys/firmware/memmap/ -
2020 Apr 30
2
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> On 30.04.20 17:38, Eric W. Biederman wrote:
>> David Hildenbrand <david at redhat.com> writes:
>>
>>> Some devices/drivers that add memory via add_memory() and friends (e.g.,
>>> dax/kmem, but also virtio-mem in the future) don't want to create entries
>>> in /sys/firmware/memmap/ -
2013 Apr 24
3
DIMM problem
Hey, folks,
I've got an HP Proliant DL580 G5 throwing ECC errors. This is annoying,
since a) it's all new as of a few months ago, and b) it's *fully*
populated. The two things I need to figure out are a) *which* DIMM it
is, and b) is it mirrored; if so, which *other* DIMM needs to come out
until we get replacements from the OEM.
Here's one of many, all identical, from dmesg:
2017 Jun 16
7
[RFC] virtio-mem: paravirtualized memory
Hi,
this is an idea that is based on Andrea Arcangeli's original idea to
host enforce guest access to memory given up using virtio-balloon using
userfaultfd in the hypervisor. While looking into the details, I
realized that host-enforcing virtio-balloon would result in way too many
problems (mainly backwards compatibility) and would also have some
conceptual restrictions that I want to avoid.
2017 Jun 16
7
[RFC] virtio-mem: paravirtualized memory
Hi,
this is an idea that is based on Andrea Arcangeli's original idea to
host enforce guest access to memory given up using virtio-balloon using
userfaultfd in the hypervisor. While looking into the details, I
realized that host-enforcing virtio-balloon would result in way too many
problems (mainly backwards compatibility) and would also have some
conceptual restrictions that I want to avoid.
2020 Apr 30
3
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> On 30.04.20 18:33, Eric W. Biederman wrote:
>> David Hildenbrand <david at redhat.com> writes:
>>
>>> On 30.04.20 17:38, Eric W. Biederman wrote:
>>>> David Hildenbrand <david at redhat.com> writes:
>>>>
>>>>> Some devices/drivers that add memory via add_memory() and
2020 Apr 30
3
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> On 30.04.20 18:33, Eric W. Biederman wrote:
>> David Hildenbrand <david at redhat.com> writes:
>>
>>> On 30.04.20 17:38, Eric W. Biederman wrote:
>>>> David Hildenbrand <david at redhat.com> writes:
>>>>
>>>>> Some devices/drivers that add memory via add_memory() and
2001 Nov 03
3
Vorbis 1.0 before the end of the year?
Hi guys.
IMO now it's definitely time for finalizing Vorbis and throwing it
in the arena.
Two reasons:
- RC2 sounds wonderfully well, I'm really amazed how good it is..
and I personally think there's little room for further improvement in
sound quality..
- portable music devices are starting to take off (see Waitec, Creative,
Apple and many other vendors).
Wouldn't be good
2010 Mar 03
26
How to verify ecc for ram is active and enabled?
Is there a method to view the status of the rams ecc single or double bit errors? I would like to confirm that ecc on my xeon e5520 and ecc ram are performing their role since memtest is ambiguous.
I am running memory test on a p6t6 ws, e5520 xeon, 2gb samsung ecc modules and this is what is on the screen:
Chipset: Core IMC (ECC : Detect / Correct)
However, further down "ECC" is
2008 Nov 14
23
Still more questions WRT selecting a mobo for small ZFS RAID
Like many others, I am looking to put together a SOHO NAS based on ZFS/CIFS. The plan is 6 x 1TB drives in RAIDZ2 configuration, driven via mobo with 6 SATA ports.
I''ve read most, if not all, of the threads here, as well as sbredon''s excellent article on building a home NAS, yet I still have a number of unanswered questions.
I was leaning heavily towards the M2N-E for a while,
2009 May 13
9
PXELINUX, pxechain.com and Etherboot
Hi,
Anyone has tried to use pxechain with Etherboot? Here is my problem:
The Etherboot client had no problem to get the list of install servers
manual from the pxechain. But didn't matter which server was chosen,
Etherboot client always tried to use the first server to do the
installation. Etherboot 5.4 was used.
What the problem may be? PXEchain or Etherboot?
Thanks,
Joyce
--