Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269252AbUINKB4 (ORCPT ); Tue, 14 Sep 2004 06:01:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269255AbUINKB4 (ORCPT ); Tue, 14 Sep 2004 06:01:56 -0400 Received: from hirsch.in-berlin.de ([192.109.42.6]:60339 "EHLO hirsch.in-berlin.de") by vger.kernel.org with ESMTP id S269252AbUINKAL (ORCPT ); Tue, 14 Sep 2004 06:00:11 -0400 X-Envelope-From: kraxel@bytesex.org Date: Tue, 14 Sep 2004 11:49:28 +0200 From: Gerd Knorr To: Peter Osterlund Cc: Kernel List Subject: Re: Linux 2.6.9-rc2 Message-ID: <20040914094928.GF27258@bytesex> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1176 Lines: 36 On Mon, Sep 13, 2004 at 11:57:44PM +0200, Peter Osterlund wrote: > Linus Torvalds writes: > > > Gerd Knorr: > > o v4l: bttv driver update > > This patch, > > Output from dmesg with a working kernel: (-rc2 with the above patch reverted) > [ ... ] > When running the crashing kernel, the last line in /var/log/messages > after the crash is: > > bttv0: pinnacle/mt: id=2 info="PAL+SECAM / stereo" radio=yes > > Maybe there is more data that doesn't make it to the disk. I can try > again with a serial console if you think that would help. That certainly is incomplete, at least the insmod messages should be there if mencoder triggeres the crash. A serial console log would be helpful. You can also try to reverse only parts of the patch, only the changes in bttv-driver.c and/or in bttv-risc.c and see what happens. Which format+size you are capturing with mencoder? Gerd -- return -ENOSIG; - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/