LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [BUG] 2.6.23-rc9 kernel panic - simple_map_write+0x4e/0x75
Date: Wed, 17 Oct 2007 12:59:08 +0530	[thread overview]
Message-ID: <4715B9C4.8000904@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071017002317.7ae2cbf4.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Wed, 17 Oct 2007 12:41:33 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> 
>>>> [  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: [<c0d7e4e2>] 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?
>>>
>> Hi Andrew,
>>
>> The machine do not have the mtd device, and the mtd is compiled into the vmlinuz.
>> This configuration works fine for other kernels and is reproducible with
>> 2.6.23-rc9 only.
> 
> So 2.6.23 is OK?

Hi Andrew,

The kernel panic is not seen in 2.6.23 kernel with CONFIG_MTD set.

-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  reply	other threads:[~2007-10-17  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13  6:40 Kamalesh Babulal
2007-10-16 20:46 ` Andrew Morton
2007-10-17  7:11   ` Kamalesh Babulal
2007-10-17  7:23     ` Andrew Morton
2007-10-17  7:29       ` Kamalesh Babulal [this message]
2008-01-19  3:06 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4715B9C4.8000904@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --subject='Re: [BUG] 2.6.23-rc9 kernel panic - simple_map_write+0x4e/0x75' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).