Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Temporary delays in patch reviewing and testing by me
Date: Fri, 22 Dec 2023 08:11:56 +0000
Message-ID: <CAK+ULv4SXGm0w8R8J8h0i_hxbvYDziOrHOXL75YU_hfn=kmtOg@mail.gmail.com> (raw)
In-Reply-To: <170323230568.8914.9300477941680805761@lain.khirnov.net>

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".

      reply	other threads:[~2023-12-22  8:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  2:22 Michael Niedermayer
2023-12-22  0:36 ` Michael Niedermayer
2023-12-22  1:40   ` Kieran Kunhya
2023-12-22  8:05     ` Anton Khirnov
2023-12-22  8:11       ` Kieran Kunhya [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK+ULv4SXGm0w8R8J8h0i_hxbvYDziOrHOXL75YU_hfn=kmtOg@mail.gmail.com' \
    --to=kierank@obe.tv \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git