On 3/31/20 4:03 PM, Brandon Nielsen wrote:
On 3/31/20 3:53 PM, Chris Murphy wrote:
gcc version?
I don't think an application written mostly in assembly would change
that significantly in size with different compiler versions.
Anyway, it looks like it broke when gcc-compat was dropped:
h
On 3/31/20 3:53 PM, Chris Murphy wrote:
gcc version?
I don't think an application written mostly in assembly would change
that significantly in size with different compiler versions.
Anyway, it looks like it broke when gcc-compat was dropped:
https://bugzilla.redhat.com/show_bug.cgi?id=1
On Tue, Mar 31, 2020 at 9:24 AM Kamil Paral wrote:
>
> On Tue, Mar 31, 2020 at 4:06 PM Brandon Nielsen wrote:
>>
>> Recently I've had cause to run memtest on some relatively modern systems
>> (Haswell, Haswell refresh, and Kaby Lake R). On all three systems the
&g
. Something changed
recently (F31) for the worse. Interestingly, memtest always reports the
same version (5.01) so I wonder what affects this.
I can confirm F30 Workstation Live works. I don't see any obvious
difference in how memtest86+ is invoked.
The binary itself is obviously different ho
Brandon Nielsen composed on 2020-03-31 09:05 (UTC-0500):
> Recently I've had cause to run memtest on some relatively modern systems
> (Haswell, Haswell refresh, and Kaby Lake R). On all three systems the
> memtest86+ provided with the Fedora Workstation Live media failed.
> O
On Tue, Mar 31, 2020 at 4:06 PM Brandon Nielsen
wrote:
> Recently I've had cause to run memtest on some relatively modern systems
> (Haswell, Haswell refresh, and Kaby Lake R). On all three systems the
> memtest86+ provided with the Fedora Workstation Live media failed.
>
>
My experience is that you need to change the bios to legacy and then it
works fine.
Thanks
Richard
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
Recently I've had cause to run memtest on some relatively modern systems
(Haswell, Haswell refresh, and Kaby Lake R). On all three systems the
memtest86+ provided with the Fedora Workstation Live media failed.
On the Haswell and Haswell refresh machines it froze shortly after
startin
memtest86+ package was shipped without proper installation script adjusted
for grub2 until memtest86+-4.20-2. Now there is proper memtest-setup, but it
is not run by default as postinstall script. People used to do their own
setting at 23_memtest according to numerous web guides.
Paths changed in
- "He Rui" wrote:
> On Thu, 2010-08-12 at 04:42 -0400, Kamil Paral wrote:
> > - "He Rui" wrote:
> > > I don't intend to cover all the memtest features, but think we
> should
> > > at
> > > least check if there's a test result shown to reflect the test,
> > > that's
> > > the main goal t
On Thu, 2010-08-12 at 04:42 -0400, Kamil Paral wrote:
> - "He Rui" wrote:
> > I don't intend to cover all the memtest features, but think we should
> > at
> > least check if there's a test result shown to reflect the test,
> > that's
> > the main goal to run a memtest.
> >
>
> Ok, I have wa
- "He Rui" wrote:
> I don't intend to cover all the memtest features, but think we should
> at
> least check if there's a test result shown to reflect the test,
> that's
> the main goal to run a memtest.
>
Ok, I have waited for the whole test cycle to complete (10 minutes on my
machine). It
On Thu, 2010-08-12 at 03:18 -0400, Kamil Paral wrote:
> - "He Rui" wrote:
> > >
> > > > 2. Test report is shown once a test is completed.
> > >
> > > The test is never completed, it runs infinitely over and over
> > again.
> > > It takes quite some time too.
> > > Also, no report is ever s
- "He Rui" wrote:
> >
> > > 2. Test report is shown once a test is completed.
> >
> > The test is never completed, it runs infinitely over and over
> again.
> > It takes quite some time too.
> > Also, no report is ever shown, just statistics are continuously
> updated
> > in the lower part
Hi Kamil,
On Wed, 2010-08-11 at 06:27 -0400, Kamil Paral wrote:
> I want to discuss the QA:Testcase Memtest86 [1] from our F14 installation
> matrix.
>
> The test case is a little weird to me and took me quite some time to
> understand what to test and when to report outcome.
>
On Wed, 2010-08-11 at 06:27 -0400, Kamil Paral wrote:
> I want to discuss the QA:Testcase Memtest86 [1] from our F14 installation
> matrix.
>
> The test case is a little weird to me and took me quite some time to
> understand what to test and when to report outcome.
>
> &
I want to discuss the QA:Testcase Memtest86 [1] from our F14 installation
matrix.
The test case is a little weird to me and took me quite some time to
understand what to test and when to report outcome.
> How to test:
> 1. Boot the installer using any available means
We don't w
17 matches
Mail list logo
