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

[Kieran Kunhya]

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

> Quoting Kieran Kunhya (2023-12-22 02:40:55)
> > On Fri, 22 Dec 2023, 00:36 Michael Niedermayer, <michael at 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