From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932353AbYDVNbo (ORCPT ); Tue, 22 Apr 2008 09:31:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760437AbYDVNba (ORCPT ); Tue, 22 Apr 2008 09:31:30 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:40757 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758642AbYDVNb3 (ORCPT ); Tue, 22 Apr 2008 09:31:29 -0400 Date: Tue, 22 Apr 2008 06:29:38 -0700 From: Andrew Morton To: hermann pitton Cc: brandon@ifup.org, jasny@vidsoft.de, video4linux-list@redhat.com, linux-kernel@vger.kernel.org, mchehab@infradead.org, stable@kernel.org Subject: Re: 2.6.25 regression: vivi - scheduling while atomic Message-Id: <20080422062938.0e491c0c.akpm@linux-foundation.org> In-Reply-To: <1208822912.10519.24.camel@pc10.localdom.local> References: <20080421081639.GE26724@vidsoft.de> <20080421223751.GD9073@plankton.ifup.org> <1208822912.10519.24.camel@pc10.localdom.local> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.19; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Tue, 22 Apr 2008 02:08:32 +0200 hermann pitton wrote: > Hi, > > Am Montag, den 21.04.2008, 15:37 -0700 schrieb Brandon Philips: > > On 10:16 Mon 21 Apr 2008, Gregor Jasny wrote: > > > Call Trace: > > > [] schedule+0xe5/0x5c7 > > > [] __rmqueue_smallest+0x88/0x107 > > > [] getnstimeofday+0x2f/0x83 > > > [] ktime_get_ts+0x17/0x48 > > > [] schedule_timeout+0x1e/0xad > > > [] enqueue_task+0x13/0x1e > > > [] wait_for_common+0xf6/0x16b > > > [] default_wake_function+0x0/0xe > > > [] kthread_create+0xa3/0x108 > > > [] :vivi:vivi_thread+0x0/0x779 > > > [] remap_vmalloc_range+0xa1/0xe6 > > > [] lock_timer_base+0x26/0x4c > > > [] __mod_timer+0xb6/0xc5 > > > [] :vivi:vivi_start_thread+0x54/0xc9 > > > [] :videobuf_core:videobuf_streamon+0x6c/0xaa > > > [] :videodev:__video_do_ioctl+0x1327/0x2ad9 > > > [] __wake_up+0x38/0x4f > > > [] futex_wake+0xdb/0xfa > > > [] :videodev:video_ioctl2+0x17c/0x210 > > > [] handle_mm_fault+0x6b1/0x6cb > > > [] vfs_ioctl+0x55/0x6b > > > [] do_vfs_ioctl+0x253/0x264 > > > [] sys_ioctl+0x3c/0x5d > > > [] system_call_after_swapgs+0x7b/0x80 > > > > > > This happenes on a vanilla 2.6.25 with loaded nvidia graphics module. > > > System architecture is x86_64. If it matters I'll try to reproduce this > > > error on a non tainted kernel. > > > > No need to reproduce on a non-tainted Kernel. This is a known issue > > with patches merged into the v4l-dvb tree several weeks ago but it seems > > to not have made it into 2.6.25 :( > > > > http://linuxtv.org/hg/v4l-dvb/rev/06eb92ed0b18 > > http://linuxtv.org/hg/v4l-dvb/rev/c50180f4ddfc > > > > I can rebase the patches for 2.6.25 but they are too big to go into the > > stable 2.6.25 tree... > > > > Thanks for the report, > > > > Brandon > > > > hmm, because of that 100 lines only rule including offsets? > > The current v4l-dvb on 2.6.24 has 233 modules. > > It is usual that changes, if needed, are going over lots of them. > > How far one can come with _such_ rules, given that one single line > changed counts up to seven with the offsets? > > How can one even comment on that brain damage? > There is no "100 line rule" for -stable patches, if that is what you were referring to. Please just send the patches to stable@kernel.org, along with a full description of why they are needed in 2.6.25.x. If those fine folk see a problem with merging the patches then they will explain that problem and discussion will ensue. It will not involve the term "100 line rule"!