From: joe briggs <jbriggs@briggsmedia.com>
To: andras@t-online.de (Andreas Arens),
linux-kernel@vger.kernel.org, motion@pdx.frogtown.com
Subject: Re: IDE corruption during heavy bt878-induced interrupt load [LKM]
Date: Tue, 22 Apr 2003 16:09:18 -0400 [thread overview]
Message-ID: <200304221609.18961.jbriggs@briggsmedia.com> (raw)
In-Reply-To: <200304222048.41595.andras@t-online.de>
I forgot to mention 2.4.19 on Debian Woody, GigaByte GA-7VAXP/Athlon
MX2500/512 MB (and several other Intel motherboards).
I am glad that you mentioned ext3 because while I curse ReiserFS, I really
don't think that it is part of the problem. Definately PCI-dma related, but
does onboard IDE (i.e., my system disk) use DMA in the same way that a PCI
adapter such as Promise does?
On Tuesday 22 April 2003 02:48 pm, you wrote:
> >I create multi-channel digital surveillance systems using cards with 4 or
> > more multiplexed bt878 framegrabbers; each one capturing 5 or more frames
> > per second on each of its two input channels (total 4 * 2 * 5 = 40 fps).
> > Typically I run using either a Promise or Adaptec HPT370 IDE-RAID
> > controller with 2 WD-120GB/8MB-cache drives striped in RAID-0, with
> > another IDE as hda for my system drive. What happens is that every few
> > seconds I get a "BTTV: RISC ERROR - resetting" from the frame grabber
> > driver. After a few days of this I have corruption on my Reiser file
> > system; which usually I am able to clean up with mkreiserfs --fix-fixable
> > or --rebuild-tree. The corruption is both on my RAID and my system drive.
> > Missing doing this maintenance action can really ruin my day.
> >
> >All comments/suggestions/etc. appreciated.
> >
> >Joe
>
> Hi,
>
> I'm seeing the same type of corruption (kernel 2.4.21pre7-ac1+acpi) when
> mencoding from BT878 to ext3 on ide raid1 (VIA 8233A on-board ide) with
> single 25 FPS. The kernel even oopsed on umount of the array, showing signs
> of memory corruption.
> I haven't come far with investigation, since I cannot affort to ruin that
> (production) system, however it seems clear to me that the v4l driver is
> the culprit. We also thought of dma contention, so my next test will be to
> switch the drives to PIO, to see if the dma traffic reduction helps.
>
> If you find some solution, please let me know
>
> Best Regards
> Andy
--
Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL/FAX 603-232-3115 MOBILE 603-493-2386
www.briggsmedia.com
parent reply other threads:[~2003-04-22 18:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200304222048.41595.andras@t-online.de>]
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=200304221609.18961.jbriggs@briggsmedia.com \
--to=jbriggs@briggsmedia.com \
--cc=andras@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=motion@pdx.frogtown.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®