On Wed, Jul 15, 2020 at 4:05 pm, Chris Murphy
wrote:
I haven't. It might be useful to know what Michael Catanzaro thinks of
it, before he goes off to buy and install ECC RAM!
I've been running it since last night and it hasn't turned up any
problems. Very tricky. :/
On Wed, Jul 15, 2020 at 01:17:50PM -0600, Chris Murphy wrote:
> On Wed, Jul 15, 2020 at 12:49 PM Solomon Peachy wrote:
> >
> > On Wed, Jul 15, 2020 at 01:41:27PM -0500, Michael Catanzaro wrote:
> > > Note: memtest86+ actually had an upstream release recently after a *very*
> > > long hiatus, so I
On Wed, Jul 15, 2020 at 10:56 PM Przemek Klosowski via devel <
devel@lists.fedoraproject.org> wrote:
> Have you looked at memtester? What do you think of it?
>
I've successfully used memtester in the past to detect suspend-resume
memory corruption on my desktop, just by periodically suspending an
On 15.07.2020 21:17, Chris Murphy wrote:
> Does anyone know if Microsoft has a signed UEFI memory tester?
Yes, but it requires Windows Native API in order to work.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@l
On Wed, Jul 15, 2020 at 2:55 PM Przemek Klosowski via devel
wrote:
>
> On 7/15/20 1:11 PM, Chris Murphy wrote:
> > Hi,
> >
> > While bad RAM is uncommon, it comes up with some regularity to cause
> > folks a lot of grief. I'm wondering if there's a way to make it easier
> > to get bad news :-\ In
On 7/15/20 1:11 PM, Chris Murphy wrote:
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of memte
On Wed, 2020-07-15 at 11:11 -0600, Chris Murphy wrote:
> Hi,
>
> While bad RAM is uncommon, it comes up with some regularity to cause
> folks a lot of grief. I'm wondering if there's a way to make it
> easier
> to get bad news :-\ In particular there are cases where RAM defects
> just don't show u
On Wed, Jul 15, 2020 at 12:49 PM Solomon Peachy wrote:
>
> On Wed, Jul 15, 2020 at 01:41:27PM -0500, Michael Catanzaro wrote:
> > Note: memtest86+ actually had an upstream release recently after a *very*
> > long hiatus, so I guess it's no longer dead. But I agree memtest86+ should
> > be dropped,
On Wed, Jul 15, 2020 at 12:09 PM Laura Abbott wrote:
>
> Detecting hardware faults is a very hard problem unfortunately. I
> brought up this question at a conference a few years ago in the
> context of determining real bugs from hardware issues and nobody
> had any great suggestions. Much of it en
On Wed, Jul 15, 2020 at 01:41:27PM -0500, Michael Catanzaro wrote:
> Note: memtest86+ actually had an upstream release recently after a *very*
> long hiatus, so I guess it's no longer dead. But I agree memtest86+ should
> be dropped, since it's incompatible with UEFI and surely not what we want
> p
Note that in my mail, I was referring to proprietary memtest86. I
haven't tried memtest86+ on my current system since it's clearly
obsolete.
On Wed, Jul 15, 2020 at 1:20 pm, Brandon Nielsen
wrote:
While I consider the effort to keep Memtest86+ working in Fedora
pretty
heroic, and I've never
On Wed, Jul 15, 2020 at 11:11 am, Chris Murphy
wrote:
4. "multiple concurrent kernel compiles" and "GCC seems to have memory
usage patterns that reliably trigger memory errors that
aren't caught by memtest"
In my experience, GCC is a really good test for RAM that is obviously
bad. By "obvious
On 7/15/20 12:11 PM, Chris Murphy wrote:
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of memt
On 7/15/20 1:11 PM, Chris Murphy wrote:
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of memte
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of memtest86+, it can take days of
contiguous test
15 matches
Mail list logo