[mythtv-users] IOBOUND: Arrrg, will it ever end?
Donn
sharky at gmail.com
Fri May 20 07:41:30 UTC 2005
I upgraded to kernel 2.6.11 and hd3000 DVB drivers 2.0. I have not
seen the IOBOUND msgs for 36 hours so far.
I'm keeping my fingers crossed that those errors are gone for good.
Looking very promising :-)
Thanks for the suggestions!
Donn
On 5/17/05, Blammo <blammo.doh at gmail.com> wrote:
> On 5/17/05, Donn <sharky at gmail.com> wrote:
> > Over 2 weeks, I have read countless search hits and attempted several
> > fixes to stop these awful IOBOUND message floods. I'm in need of some
> > serious help. I have implemented many of the suggestions in the
> > archives (and some of my own crazy ideas) with no luck.
> >
> > Sometimes when recording two shows at once, mythtv gets locked into a
> > series of IOBOUND messages:
> >
> > 2005-05-16 23:36:43.145 IOBOUND - blocking in ThreadedFileWriter::Write()
> > 2005-05-16 23:36:47.807 IOBOUND - blocking in ThreadedFileWriter::Write()
> > 2005-05-16 23:36:52.579 IOBOUND - blocking in ThreadedFileWriter::Write()
> > 2005-05-16 23:36:57.729 IOBOUND - blocking in ThreadedFileWriter::Write()
>
> I would suggest a couple things:
>
> 1. Move to a newer kernel. I had some strangeness with 2.6.9 / 2.6.10
> along the way with IO (air2pc / pvr-250 / 4-drive raid5) and moving to
> 2.6.11 cured almost all of them.
>
> 2. Check your IRQ's. lspci -v and check for things sharing the same
> IRQ. When you're faciing an IO problem sharing can become a big issue.
> This was another key for me in removing IO problems.
>
> 3. What's the RAM clock on your machine? Is it 133 or 200? Should be
> 133 to make the PC2100 happy.
>
More information about the mythtv-users
mailing list