From: Bodo Eggert <harvested.in.lkml@7eggert.dyndns.org>
To: Duncan Sands <duncan.sands@math.u-psud.fr>,
Roland Scheidegger <rscheidegger_lists@hispeed.ch>,
Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: four bttv tuners in one PC crashed
Date: Sat, 11 Mar 2006 11:08:25 +0100 [thread overview]
Message-ID: <E1FI11O-0000bK-8u@be1.lrz> (raw)
In-Reply-To: <5NRBv-6ze-9@gated-at.bofh.it>
Duncan Sands <duncan.sands@math.u-psud.fr> wrote:
>> The bttv driver/chip seems to cause random memory corruption sometimes,
>> processes will just start dying...
>
> There is a known buffer overflow in the bttv driver (when using
> grabdisplay). The fix is waiting on an audit of the rest of the
> bttv (and similar) code, since it looks like the same mistake
> occurs in several places.
Can you give me a hint on where exactly to shoot at? I'n still hoping it's
not my VIA board giving me trouble (corrupting the first four bytes of a
semi-random page).
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
next parent reply other threads:[~2006-03-11 10:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5NpZk-7wW-13@gated-at.bofh.it>
[not found] ` <5NJ1x-1OE-15@gated-at.bofh.it>
[not found] ` <5NPJk-3GD-3@gated-at.bofh.it>
[not found] ` <5NRBv-6ze-9@gated-at.bofh.it>
2006-03-11 10:08 ` Bodo Eggert [this message]
2006-03-12 11:21 ` Sami Farin
2006-03-06 15:34 Jiri Tyr
2006-03-06 15:56 ` Duncan Sands
2006-03-06 15:58 ` Jiri Tyr
2006-03-06 18:39 ` Jiri Tyr
2006-03-07 8:22 ` Jiri Tyr
2006-03-07 11:50 ` Jiri Tyr
2006-03-07 12:32 ` Duncan Sands
2006-03-15 8:48 ` Jiri Tyr
2006-03-15 14:21 ` Sami Farin
2006-03-15 14:30 ` Jiri Tyr
2006-03-15 15:25 ` Jiri Tyr
2006-03-15 15:41 ` Sami Farin
2006-03-07 19:08 ` Roland Scheidegger
2006-03-07 19:43 ` Duncan Sands
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=E1FI11O-0000bK-8u@be1.lrz \
--to=harvested.in.lkml@7eggert.dyndns.org \
--cc=7eggert@gmx.de \
--cc=duncan.sands@math.u-psud.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rscheidegger_lists@hispeed.ch \
--cc=video4linux-list@redhat.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®