From: Brian Norris <computersforpeace@gmail.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: Yuanhan Liu <yuanhan.liu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Su Tao <tao.su@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Fengguang Wu <fengguang.wu@intel.com>, LKP <lkp@01.org>,
Jet Chen <jet.chen@intel.com>
Subject: Re: [sbc_gxx] kernel BUG at include/linux/mtd/map.h:148!
Date: Thu, 7 Aug 2014 15:46:18 -0700 [thread overview]
Message-ID: <20140807224618.GQ3711@ld-irv-0074> (raw)
In-Reply-To: <CAPDOMVgN=tc_o7E19ss4j5FAG4vpgUSzuUXYLSNGfpWCvPsAwA@mail.gmail.com>
Hi,
On Tue, Aug 05, 2014 at 08:08:57PM -0400, Nick Krause wrote:
> On Tue, Aug 5, 2014 at 9:59 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Hello,
> >
> > This is an old BUG that still lives in linux-next.
> >
> > [ 4.284620] device id = 2670
> > [ 4.286157] SBC-GXx flash: IO:0x258-0x259 MEM:0xdc000-0xdffff
> > [ 4.287060] ------------[ cut here ]------------
> > [ 4.287722] kernel BUG at include/linux/mtd/map.h:148!
> > [ 4.288048] invalid opcode: 0000 [#1] PREEMPT SMP
>
> I am new , here and will try to trace your issue on linus's tree
> unless there is a major difference between Linus's tree and
> linux-next.
> If there is please let me known before I start tracing this.
This is a known issue, and Fengguang has reported this before:
http://lists.infradead.org/pipermail/linux-mtd/2014-March/053019.html
I'm still not quite sure how to solve this one. It seems to be a
limitation of the kconfig language.
Brian
next prev parent reply other threads:[~2014-08-07 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 13:59 [sbc_gxx] kernel BUG at include/linux/mtd/map.h:148! Fengguang Wu
2014-08-06 0:08 ` Nick Krause
2014-08-07 22:46 ` Brian Norris [this message]
2014-08-08 2:08 ` Nick Krause
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=20140807224618.GQ3711@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lkp@01.org \
--cc=tao.su@intel.com \
--cc=xerofoify@gmail.com \
--cc=yuanhan.liu@intel.com \
/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