From: Borislav Petkov <bp@alien8.de>
To: werner <w.landgraf@ru.ru>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: 3.1 problem: crash during boot
Date: Thu, 10 Nov 2011 09:41:44 +0100 [thread overview]
Message-ID: <20111110084144.GA1960@x1.osrc.amd.com> (raw)
In-Reply-To: <web-642904662@zbackend1.aha.ru>
On Wed, Nov 09, 2011 at 08:44:30PM -0400, werner wrote:
> A neihgbour's computer crashs with 3.1 , see below hand-copied from
> the screen. More details are in the enclosed file.
>
>
Hmm, this looks incomplete and is missing the oops header which says
exactly what happens.
Judging by the call stack below, it could be MTD maps something behind
CONFIG_MTD_ICHXROM, i.e. ichxrom_init_one() and below.
Adding MTD ML in case they've seen something similar already.
> c ...
> 1618067 genprobe_ident_chips+0x83/0x261
> 1f36808 ?_raw_write_unlock_irqrestore+0x6/0x1c
> 1589dfc ? strnlen+0x3/0x1f
> 1b183c0 mtd_d0_chip_probe+0x17/0xa7
> 108bc8e ? ftrace_test_stop_func+0x12/0x14
> 1b03aae cfi_probe+0x12/0x14
> 1b03a84 do_map_probe+0x4a/0x62
> 1f3807d ? trace+0x13/0x1b
> 1f09321 ichxrom_init_one+0x391/0x503
> 24fe1fg ? parse_early_options+0x25/0x25
> 254d98a init_ichxrom+0x34/0x34
> 1001174 do_one_initall+0x8c/0x142
> 24fe1f9 ? parse_early_options+0x25/0x25
> 107f0d8 ? irq_to_desc+0x8/0x21
> 254d956 ? init_esb2rom+0x96/0x96
> 24fe1f9 ? parse_early_options+0x25/0x25
> 24fc(or e)285 kernel_init+0x8c/0x120
> 1f38046 kernel_thread_helper+0x6/0x19
HTH.
--
Regards/Gruss,
Boris
prev parent reply other threads:[~2011-11-10 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 0:44 3.1 problem: crash during boot werner
2011-11-10 8:41 ` Borislav Petkov [this message]
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=20111110084144.GA1960@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=w.landgraf@ru.ru \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox