From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965620AbXJPU6T (ORCPT ); Tue, 16 Oct 2007 16:58:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753118AbXJPU5v (ORCPT ); Tue, 16 Oct 2007 16:57:51 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:47459 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965115AbXJPU5k (ORCPT ); Tue, 16 Oct 2007 16:57:40 -0400 Date: Tue, 16 Oct 2007 13:46:20 -0700 From: Andrew Morton To: Kamalesh Babulal Cc: linux-kernel@vger.kernel.org, David Woodhouse , linux-mtd@lists.infradead.org Subject: Re: [BUG] 2.6.23-rc9 kernel panic - simple_map_write+0x4e/0x75 Message-Id: <20071016134620.7b3ce56f.akpm@linux-foundation.org> In-Reply-To: <4710686C.8060603@linux.vnet.ibm.com> References: <4710686C.8060603@linux.vnet.ibm.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.20; i486-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 X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 13 Oct 2007 12:10:44 +0530 Kamalesh Babulal wrote: > Kernel panic's with following oops message with 2.6.23-rc9 kernel > > [ 320.747257] ks0108: ERROR: parport didn't register new device > [ 320.771314] cfag12864b: ERROR: ks0108 is not initialized > [ 320.794308] cfag12864bfb: ERROR: cfag12864b is not initialized > [ 320.820729] BUG: unable to handle kernel paging request at virtual address > bf000000 > [ 320.857712] printing eip: > [ 320.872556] *pde = 00000000 > [ 320.887577] Oops: 0002 [#1] > [ 320.902383] SMP > [ 320.914174] Modules linked in: > [ 320.929333] CPU: 0 > [ 320.929334] EIP: 0060:[] Not tainted VLI > [ 320.929335] EFLAGS: 00010286 (2.6.23-rc9-1 #1) > [ 320.982753] EIP is at simple_map_write+0x4e/0x75 > [ 321.001956] eax: f0f0f0f0 ebx: c1de3f00 ecx: c1de3f00 edx: c1de3f00 > [ 321.027701] esi: c3ca8d6c edi: bf000000 ebp: c3ca8d98 esp: c3ca8d6c > [ 321.053322] ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068 > [ 321.075981] Process swapper (pid: 1, ti=c3ca8000 task=f7f44000 task.ti=c3ca8000) > [ 321.103031] Stack: f0f0f0f0 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 > [ 321.139446] c3ca8e20 00000001 c3ca8e40 c3ca8e6c c0d692e6 f0f0f0f0 > 00000000 00000000 > [ 321.176495] 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 000050e6 > [ 321.214141] Call Trace: > [ 321.233922] [] show_trace_log_lvl+0x19/0x2e > [ 321.255433] [] show_stack_log_lvl+0x99/0xa1 > [ 321.276706] [] show_registers+0x1b8/0x290 > [ 321.297254] [] die+0x118/0x1fd > [ 321.314920] [] do_page_fault+0x51c/0x5f3 > [ 321.335291] [] error_code+0x72/0x78 > [ 321.354413] [] cfi_probe_chip+0x148/0x9e1 > [ 321.375202] [] genprobe_new_chip+0x82/0x98 > [ 321.396298] [] genprobe_ident_chips+0x26/0x205 > [ 321.418493] [] mtd_do_chip_probe+0x10/0x97 > [ 321.439654] [] cfi_probe+0xd/0xf > [ 321.458157] [] do_map_probe+0x40/0x53 > [ 321.477931] [] init_pnc2000+0x3b/0x6d > [ 321.497559] [] do_initcalls+0x7a/0x1c2 > [ 321.517377] [] do_basic_setup+0x1c/0x1e > [ 321.537327] [] kernel_init+0x69/0xaa > [ 321.556311] [] kernel_thread_helper+0x7/0x10 > [ 321.577207] ======================= > [ 321.592882] Code: 83 f8 01 75 0a 03 7b 10 8b 45 d4 88 07 eb 35 83 f8 02 75 0c > 0f b7 45 d4 03 7b 10 66 89 07 eb 24 83 f8 04 75 0a 03 7b 10 8b 45 d4 <89> 07 eb > 15 7e 13 03 7b 10 89 c1 c1 e9 02 f3 a5 89 c1 83 e1 03 > [ 321.668990] EIP: [] simple_map_write+0x4e/0x75 SS:ESP 0068:c3ca8d6c > [ 321.695750] Kernel panic - not syncing: Attempted to kill init! Would I be correct in assuming that the machine has no mtd devices, but you happened to link that driver into your vmlinux?