[FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1982 bytes --]

Hi all

My main development machiene died today, so expect increased delays
about things that involve me/it until thats fixed

Rest of the mail is just about the issue, and you can skip reading that

Timeline:
box suddenly stopped, no reaction to any input or pings
power off and on did not bring it back, screen stayed dark, keyboard too
but fans spin up and theres power
opening it up i find it stuck on Q-code "0d" so i power it off
wiggle the ram modules a bit power it back on and it gets stuck on
qcode "15" i power cycle again and it reaches bios setup, so i go over all
values and just look but as i look, it hangs hard again
off/on again and we hit "0d" again
so i remove one of the CPU fans to get to the DIMM modules and reconfigure them like this:
B1A1 0+2 -> boot ok
B2A2 0+2 -> boot ok
B2A2 1+3 -> 0d
B2A2 0+3 -> boot ok
B1A1 1+2 -> 0d

This is consistent with DIMM module 1 being faulty. But iam not 100% convinced
because this box never crashed not once, it was always rock solid and suddenly
one module is so faulty the box hangs so early.
Either way i ordered 4 new and bigger modules from 2 independant shops
they should be here soon but i dont know what "soon" is around christmess

also i could try running it with just 2 modules, i might try that
tomorrow

RAM modules are: G.Skill Trident Z F4-3600C15D-16GTZ DDr4-3600 CL15-15-15 1.35v 8Gb manufaturing date 2019 Dec
MOBO is: ASUS ROG STRIX X570-E Gaming

PS: i could have gotten the modules quicker but i was trying to get
4x16gb to double the 4x8gb and have them not slower. And it seems that
constrains me to 2-3days waiting at quickest.

PS2: The faulty module looks perfectly fine and all look suprisingly clean

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1836 bytes --]

On Thu, Dec 21, 2023 at 03:22:20AM +0100, Michael Niedermayer wrote:
> Hi all
> 
> My main development machiene died today, so expect increased delays
> about things that involve me/it until thats fixed
> 
> Rest of the mail is just about the issue, and you can skip reading that
> 
> Timeline:
> box suddenly stopped, no reaction to any input or pings
> power off and on did not bring it back, screen stayed dark, keyboard too
> but fans spin up and theres power
> opening it up i find it stuck on Q-code "0d" so i power it off
> wiggle the ram modules a bit power it back on and it gets stuck on
> qcode "15" i power cycle again and it reaches bios setup, so i go over all
> values and just look but as i look, it hangs hard again
> off/on again and we hit "0d" again
> so i remove one of the CPU fans to get to the DIMM modules and reconfigure them like this:
> B1A1 0+2 -> boot ok
> B2A2 0+2 -> boot ok
> B2A2 1+3 -> 0d
> B2A2 0+3 -> boot ok
> B1A1 1+2 -> 0d
> 
> This is consistent with DIMM module 1 being faulty. But iam not 100% convinced
> because this box never crashed not once, it was always rock solid and suddenly
> one module is so faulty the box hangs so early.
> Either way i ordered 4 new and bigger modules from 2 independant shops
> they should be here soon but i dont know what "soon" is around christmess
> 

> also i could try running it with just 2 modules, i might try that
> tomorrow

system seems working stable with 2 DIMM sticks

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

"You are 36 times more likely to die in a bathtub than at the hands of a
terrorist. Also, you are 2.5 times more likely to become a president and
2 times more likely to become an astronaut, than to die in a terrorist
attack." -- Thoughty2


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[Kieran Kunhya]

On Fri, 22 Dec 2023, 00:36 Michael Niedermayer, <michael@niedermayer.cc>
wrote:

> On Thu, Dec 21, 2023 at 03:22:20AM +0100, Michael Niedermayer wrote:
> > Hi all
> >
> > My main development machiene died today, so expect increased delays
> > about things that involve me/it until thats fixed
> >
> > Rest of the mail is just about the issue, and you can skip reading that
> >
> > Timeline:
> > box suddenly stopped, no reaction to any input or pings
> > power off and on did not bring it back, screen stayed dark, keyboard too
> > but fans spin up and theres power
> > opening it up i find it stuck on Q-code "0d" so i power it off
> > wiggle the ram modules a bit power it back on and it gets stuck on
> > qcode "15" i power cycle again and it reaches bios setup, so i go over
> all
> > values and just look but as i look, it hangs hard again
> > off/on again and we hit "0d" again
> > so i remove one of the CPU fans to get to the DIMM modules and
> reconfigure them like this:
> > B1A1 0+2 -> boot ok
> > B2A2 0+2 -> boot ok
> > B2A2 1+3 -> 0d
> > B2A2 0+3 -> boot ok
> > B1A1 1+2 -> 0d
> >
> > This is consistent with DIMM module 1 being faulty. But iam not 100%
> convinced
> > because this box never crashed not once, it was always rock solid and
> suddenly
> > one module is so faulty the box hangs so early.
> > Either way i ordered 4 new and bigger modules from 2 independant shops
> > they should be here soon but i dont know what "soon" is around christmess
> >
>
> > also i could try running it with just 2 modules, i might try that
> > tomorrow
>
> system seems working stable with 2 DIMM sticks
>

You should get comparable memory bandwidth with 2 sticks or 4 on consumer
grade systems. The differences are minor.

If you need to know which stick is bad memtest will tell you.

Kieran

>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[Anton Khirnov]

Quoting Kieran Kunhya (2023-12-22 02:40:55)
> On Fri, 22 Dec 2023, 00:36 Michael Niedermayer, <michael@niedermayer.cc>
> wrote:
> 
> > On Thu, Dec 21, 2023 at 03:22:20AM +0100, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > My main development machiene died today, so expect increased delays
> > > about things that involve me/it until thats fixed
> > >
> > > Rest of the mail is just about the issue, and you can skip reading that
> > >
> > > Timeline:
> > > box suddenly stopped, no reaction to any input or pings
> > > power off and on did not bring it back, screen stayed dark, keyboard too
> > > but fans spin up and theres power
> > > opening it up i find it stuck on Q-code "0d" so i power it off
> > > wiggle the ram modules a bit power it back on and it gets stuck on
> > > qcode "15" i power cycle again and it reaches bios setup, so i go over
> > all
> > > values and just look but as i look, it hangs hard again
> > > off/on again and we hit "0d" again
> > > so i remove one of the CPU fans to get to the DIMM modules and
> > reconfigure them like this:
> > > B1A1 0+2 -> boot ok
> > > B2A2 0+2 -> boot ok
> > > B2A2 1+3 -> 0d
> > > B2A2 0+3 -> boot ok
> > > B1A1 1+2 -> 0d
> > >
> > > This is consistent with DIMM module 1 being faulty. But iam not 100%
> > convinced
> > > because this box never crashed not once, it was always rock solid and
> > suddenly
> > > one module is so faulty the box hangs so early.
> > > Either way i ordered 4 new and bigger modules from 2 independant shops
> > > they should be here soon but i dont know what "soon" is around christmess
> > >
> >
> > > also i could try running it with just 2 modules, i might try that
> > > tomorrow
> >
> > system seems working stable with 2 DIMM sticks
> >
> 
> You should get comparable memory bandwidth with 2 sticks or 4 on consumer
> grade systems. The differences are minor.
> 
> If you need to know which stick is bad memtest will tell you.

It's hard to run memtest when the system refuses to boot with the stick
in question.

-- 
Anton Khirnov
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] Temporary delays in patch reviewing and testing by me

[Kieran Kunhya]

On Fri, 22 Dec 2023 at 08:05, Anton Khirnov <anton@khirnov.net> wrote:

> Quoting Kieran Kunhya (2023-12-22 02:40:55)
> > On Fri, 22 Dec 2023, 00:36 Michael Niedermayer, <michael@niedermayer.cc>
> > wrote:
> >
> > > On Thu, Dec 21, 2023 at 03:22:20AM +0100, Michael Niedermayer wrote:
> > > > Hi all
> > > >
> > > > My main development machiene died today, so expect increased delays
> > > > about things that involve me/it until thats fixed
> > > >
> > > > Rest of the mail is just about the issue, and you can skip reading
> that
> > > >
> > > > Timeline:
> > > > box suddenly stopped, no reaction to any input or pings
> > > > power off and on did not bring it back, screen stayed dark, keyboard
> too
> > > > but fans spin up and theres power
> > > > opening it up i find it stuck on Q-code "0d" so i power it off
> > > > wiggle the ram modules a bit power it back on and it gets stuck on
> > > > qcode "15" i power cycle again and it reaches bios setup, so i go
> over
> > > all
> > > > values and just look but as i look, it hangs hard again
> > > > off/on again and we hit "0d" again
> > > > so i remove one of the CPU fans to get to the DIMM modules and
> > > reconfigure them like this:
> > > > B1A1 0+2 -> boot ok
> > > > B2A2 0+2 -> boot ok
> > > > B2A2 1+3 -> 0d
> > > > B2A2 0+3 -> boot ok
> > > > B1A1 1+2 -> 0d
> > > >
> > > > This is consistent with DIMM module 1 being faulty. But iam not 100%
> > > convinced
> > > > because this box never crashed not once, it was always rock solid and
> > > suddenly
> > > > one module is so faulty the box hangs so early.
> > > > Either way i ordered 4 new and bigger modules from 2 independant
> shops
> > > > they should be here soon but i dont know what "soon" is around
> christmess
> > > >
> > >
> > > > also i could try running it with just 2 modules, i might try that
> > > > tomorrow
> > >
> > > system seems working stable with 2 DIMM sticks
> > >
> >
> > You should get comparable memory bandwidth with 2 sticks or 4 on consumer
> > grade systems. The differences are minor.
> >
> > If you need to know which stick is bad memtest will tell you.
>
> It's hard to run memtest when the system refuses to boot with the stick
> in question.
>

fair enough

Kieran
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".