From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Laurent Birtz <laurent.birtz@usherbrooke.ca>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] bttv driver memory corruption
Date: Sun, 31 Oct 2010 01:40:45 +0200 [thread overview]
Message-ID: <20101030234045.GA15147@minime.bse> (raw)
In-Reply-To: <4CC5A390.9010800@usherbrooke.ca>
On Mon, Oct 25, 2010 at 11:34:40AM -0400, Laurent Birtz wrote:
> I've observed that the poison was corrupted at some random pages, but
> always in the first four bytes. The value of those bytes is 0x23232323.
> This byte sequence often appears in kernel oops reports on my setup.
I couldn't verify your findings by mallocing an equivalent of the
physical memory, filling everything with 0xdeadbeef, and then
periodically checking it didn't change while watching tv at 768x576
in YUY2.
Which video mode and resolution did you use in your tests?
Did you try loading bttv with triton1=1 and vsfx=1?
Daniel
next prev parent reply other threads:[~2010-10-30 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 15:34 [PATCH] bttv driver memory corruption Laurent Birtz
2010-10-30 23:40 ` Daniel Glöckner [this message]
2010-10-31 1:21 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2010-08-16 17:13 Laurent Birtz
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=20101030234045.GA15147@minime.bse \
--to=daniel-gl@gmx.net \
--cc=laurent.birtz@usherbrooke.ca \
--cc=linux-media@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.