From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262104AbVFUJUH (ORCPT ); Tue, 21 Jun 2005 05:20:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262084AbVFUJRn (ORCPT ); Tue, 21 Jun 2005 05:17:43 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:10895 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S261507AbVFUJQn (ORCPT ); Tue, 21 Jun 2005 05:16:43 -0400 Date: Tue, 21 Jun 2005 11:15:57 +0200 From: Pavel Machek To: Dipankar Sarma Cc: kernel list , Andrew Morton Subject: Re: 2.6.12-mm1: BUG() in fd_install, RCU related? Message-ID: <20050621091557.GD1953@elf.ucw.cz> References: <20050621083424.GA2076@elf.ucw.cz> <20050621090721.GA7976@in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050621090721.GA7976@in.ibm.com> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > I got > > > > Jun 21 10:30:20 amd kernel: ------------[ cut here ]------------ > > Jun 21 10:30:20 amd kernel: kernel BUG at fs/open.c:935! > > Jun 21 10:30:20 amd kernel: invalid operand: 0000 [#1] > > Jun 21 10:30:20 amd kernel: Modules linked in: ipw2100 > > Jun 21 10:30:20 amd kernel: CPU: 0 > > Jun 21 10:30:20 amd kernel: EIP: 0060:[page_referenced+39/160] Not tainted VLI > > Jun 21 10:30:20 amd kernel: EFLAGS: 00010286 (2.6.12-mm1) > > Jun 21 10:30:20 amd kernel: EIP is at fd_install+0x27/0x40 > > Jun 21 10:30:20 amd kernel: eax: f7268e00 ebx: 00000080 ecx: f61a9800 edx: f6106400 > > This has been reported by several other people. > I am looking at it except that I can't reproduce it with the config > files in one of those bug reports. Probably whatever userland triggers > this bug isn't in my lab machine. Besides I am running really old > userland anyway. I am going to find a box with newer userland > and try. > > Some things are common - always with fcntl() or fcntl64() and with > a daemon. Does your box come up at all ? If so, can you get me an > strace on the process that triggers this ? If I can narrow it > down to a small testcase, it would be a lot easier. Also, does > switching off CONFIG_PREEMPT fix this problem ? It is not reproducible for me. My machine came up, I worked for hour or so, then seen this one. It is still usable (I did not reboot yet). I do not see report which process is causing it :-(, original oops does not contain it AFAICS. Pavel -- teflon -- maybe it is a trademark, but it should not be.