[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#32890: closed ([PATCH 0/2] test mems)

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#32890: closed ([PATCH 0/2] test mems)
Date: Thu, 04 Oct 2018 02:32:02 +0000

Your message dated Thu, 04 Oct 2018 04:30:57 +0200
with message-id <address@hidden>
and subject line Re: [PATCH 0/2] test mems
has caused the debbugs.gnu.org bug report #32890,
regarding [PATCH 0/2] test mems
to be marked as done.

(If you believe you have received this mail in error, please contact

32890: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32890
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH 0/2] test mems Date: Mon, 01 Oct 2018 12:14:21 +0200

Here are some memory testers.

Memtest86+ must be built with '--system=i686-linux' (is there a way to ask for a 32-bit glibc on x86_64?) and still needs to be tested by a volunteer with a BIOS machine. It can be launched from GRUB ('linux16 memtest') or catted to a boot disc (memtest.bin).

Memtester runs in user space and can even run as a regular user. It should just work.

Kind regards,


--- End Message ---
--- Begin Message --- Subject: Re: [PATCH 0/2] test mems Date: Thu, 04 Oct 2018 04:30:57 +0200 Pushed as 5eff43804eaed5744967f83edbaeb7ffdb77aec1 & fb5412511479c19b3e4c884e9cc65e652ea923e2 with the aforementioned changes, as well as descriptions which (I hope) better describe both tools' similarities and differences.
Kind regards,


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]