public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Laine <jeremy.laine@polytechnique.org>
To: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
Cc: linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: OOPS: frequent crashes with bttv in 2.6.X series (inc. 2.6.12)
Date: Thu, 07 Jul 2005 16:35:56 +0100	[thread overview]
Message-ID: <1120750556.42cd4bdc7101c@webmail.jerryweb.org> (raw)
In-Reply-To: <42CD4667.9050205@brturbo.com.br>

Hi Mauro,

First of all, many thanks for taking the time to reply to my email!

> We don't have any other OOPS reported for BTTV cards.

The reply from Bodo Eggert seems to indicate otherwise..

Here is some extra information as requested:

> 	1) desactivate any overclocking at motherboard/video board;

I do not use any kind of overclocking, never have done and never will!

> 	2) use a standard vanilla kernel (not a distro kernel, that may have
> some experimental patches applied;

The crashes I reported were on a vanilla 2.6.12 kernel, compiled straight from
the tarball on kernel.org.

> 	3) use a minimum ammount of cards leaving only neccessary cards at MB.
> For these, it is good to clean its contacts;

The only extension cards I use are:
- 1 nVidia GeForce 6800 video adapter
- 1 Pinacle PCTV card
- 1 3Com 3c905C ethernet card
- 1 SB Live! 1024 card

I regularly vacuum-clean my tower and have checked the contacts on the extension
cards on several occasions. For tests, I am willing to remove the NIC +
soundcard if you think that will help (will try over the weekend), but in the
long run I don't consider any of the above cards to be "exotic" or optional..

> 	4) Test it again.

Will do, as stated above.  On a sidenote, so far I have been unable to reproduce
the problem when PREEMPT is disactivated (I stressed my box by compiling a
kernel while watching TV).

Cheers,
Jeremy

--
http://www.jerryweb.org/             : JerryWeb.org
http://sailcut.sourceforge.net/      : Sailcut CAD
http://opensource.polytechnique.org/ : Polytechnique.org Free Software

  reply	other threads:[~2005-07-07 15:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 10:11 OOPS: frequent crashes with bttv in 2.6.X series (inc. 2.6.12) Jeremy Laine
2005-07-06 14:44 ` Michael Krufky
2005-07-07 14:31   ` Lee Revell
2005-07-07 14:35     ` Michael Krufky
2005-07-06 14:59 ` Alexey Dobriyan
2005-07-07  8:25   ` Jeremy Laine
2005-07-07 15:12     ` Mauro Carvalho Chehab
2005-07-07 15:35       ` Jeremy Laine [this message]
2005-07-07 16:17       ` matthieu castet
2005-07-07 19:11         ` Duncan Sands
  -- strict thread matches above, loose matches on Subject: below --
2005-07-06 15:02 Piszcz, Justin
2005-07-06 20:46 ` Lee Revell
     [not found] <4njei-1Ps-21@gated-at.bofh.it>
2005-07-06 23:09 ` Bodo Eggert
2005-07-07  8:17   ` Duncan Sands
2005-07-07  8:31   ` Jeremy Laine
     [not found] <4nrlt-8po-15@gated-at.bofh.it>
     [not found] ` <4nrlt-8po-13@gated-at.bofh.it>
2005-07-07 15:52   ` Bodo Eggert
2005-07-08 17:19     ` Mauro Carvalho Chehab
2005-07-09  7:34       ` Bodo Eggert

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=1120750556.42cd4bdc7101c@webmail.jerryweb.org \
    --to=jeremy.laine@polytechnique.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    --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