[mythtv-users] Question on 8GB of RAM. Was: 32 bit or 64bit???
Stackpole, Chris
CStackpole at barbnet.com
Tue Jan 27 14:28:04 UTC 2009
> From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
> bounces at mythtv.org] On Behalf Of Francis Hartojo
> Sent: Monday, January 26, 2009 4:26 PM
> Subject: Re: [mythtv-users] Question on 8GB of RAM. Was: 32 bit or
> 64bit???
>
> On Mon, Jan 26, 2009 at 2:46 PM, Stackpole, Chris
> <CStackpole at barbnet.com> wrote:
> >
> > To quote a popular net phrase: ZOMG!!1!!
> >
> > I just looked at some of the notes I took when I was having these
> > problems and they match up almost exactly with your description. I
think
> > I am going to have to look into this bug a bit more.
> >
> > However, since I did those updates / patches (see messages from last
> > week) I have not had a single mythtv related problem (neighborhood
lost
> > power and the battery backup only gave me 2 of the 10 minutes
*shakes
> > fist in anger*). So I think that the updates fixed it, but it can't
hurt
> > to look into this bug and see if I can find more information on it.
>
> Which updates/patches? Kernel or MythTV updates/patches? Or both?
>
> I'm just running a stock Mythbuntu 8.10 64-bit with the latest
> official updates. No custom compiles or builds.
>
> > Also, as I side note: I used to have a script that would run every
> > couple of hours to update the time. If left unattended in 64bit mode
the
> > time would drift by ~15 sec/day. NTP had issues keeping it in sync.
It
> > kept perfect time in 32bit mode. Since the update it drifts maybe 2
> > sec/day. NTP seems to be working well.
>
> I haven't come across that issue so far.
>
> Thanks.
> --
> Francis
> echo "sunegbwb at tznvy.pbz" | tr '[a-z]' '[n-za-m]'
I seem to have launched a bit more conversation then I meant to so let
me clarify.
NTP
I have a smoothwall firewall setup that updates NTP every 3 hours
(possibly 6, can't remember off the top of my head). All of my systems
behind the firewall update their time from it.
My current BE hardware running 64bit Debian Lenny, did not drift wildly.
NTP kept it in sync perfectly. The same hardware running 32bit Mythbuntu
8.04 did not drift wildly. NTP kept it in sync. However, the exact same
hardware running 64bit Mythbuntu 8.04 drifted a lot. More so then what
NTP would correct. Then I applied the updates, and now NTP appears to be
keeping everything in sync. The clock still drifts by about 3 seconds
every day, but NTP seems to be keeping it in line.
Updates
Higher up in this thread I was having a lot of problems with MythTV and
more then 4GB of memory, but no problems with 4GB. I was inquiring about
a comment made about Myth having problems with more then 4GB of memory.
I found a message through a Google search that said my problem was
motherboard related. I updated the BIOS to the latest version and it
fixed my Memory problems, as well as the problems I was seeing in
MythTV. What I started researching (with no luck at the moment) was if
the BIOS patch fixed this AMD bug mentioned or if I was even at risk for
that bug. The close similarity to the error messages makes me think I
might have had that bug and the BIOS update fixed it.
I know this is getting to be a long thread so hopefully I clarified my
statements without rehashing the whole thread too much. :-)
~Stack~
More information about the mythtv-users
mailing list