From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HPp5v-0005oj-6I for qemu-devel@nongnu.org; Fri, 09 Mar 2007 19:05:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HPp5t-0005lz-JZ for qemu-devel@nongnu.org; Fri, 09 Mar 2007 19:05:54 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HPp5t-0005lg-Ae for qemu-devel@nongnu.org; Fri, 09 Mar 2007 19:05:53 -0500 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HPp5V-0002z6-Os for qemu-devel@nongnu.org; Fri, 09 Mar 2007 19:05:29 -0500 From: Rob Landley Subject: Re: [Qemu-devel] Intermittant linux kernel panic on arm Date: Fri, 9 Mar 2007 19:05:27 -0500 References: <20070307181433.GA2911@urbana.css.mot.com> In-Reply-To: <20070307181433.GA2911@urbana.css.mot.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200703091905.28445.rob@landley.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Quentin Barnes On Wednesday 07 March 2007 1:14 pm, Quentin Barnes wrote: > This is my first post to the list. Hopefully, it will go well. > > I've been using the ARM qemu for Linux development for some basic > work, but wanted to expand and do more with it. I outgrew the > initrd limitation and needed a disk. Since I've been using a disk, > I've been getting intermittant panics during the udevd phase of > boot. Once the system is up though, it's been stable. > > The panic occurs about 50%-75% the time. I've had this problem on both > 0.9.0 and the 2007-03-07_05 snapshot. I've had this problem using both > my own 2.6.19-1 ARM kernel made directly from kernel.org as well as > Aurelien Jarno's 2.6.18 Debian ARM kernel at > http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-4-versatile The first thing I'd do is try to figure out what's udev doing to trigger this panic? > r7 = 00000036 r6 = 00002285 r5 = FFFFFFF7 r4 = C0BA0D20 > [] (sys_ioctl+0x0/0x64) from [] (ret_fast_syscall+0x0/0x2c) Is there any way you can figure out which ioctl this is? Presumably udev read something from /sys that told it to mknod something in /dev. I'm not quite sure where an ioctl comes into this... If you could get a small C program that triggers the panic, and a kernel .config you built your kernel with, that would be helpful. Rob -- Vista: Windows Millenium Second Edition