From: Wolfram Sang <wsa@the-dreams.de>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot
Date: Thu, 17 Mar 2016 21:52:25 +0100 [thread overview]
Message-ID: <20160317205225.GA1482@katana> (raw)
In-Reply-To: <5769.1458226791@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Thu, Mar 17, 2016 at 10:59:51AM -0400, Valdis Kletnieks wrote:
> Seeing this consistent crash on next-20160314. Sorry for shortened traceback,
> hand-transcribed as the crash doesn't get logged to /sys/fs/pstore as
> expected. next-20160307 works just fine.
>
> BUG: unable to handle kernel NULL pointer dereference at 000000000260
> IP: blocking_notifier_chain_register+0x37/0xd0
> ...
> Call Trace:
> bus_register_notifier+0x1c/0x20
> i2c_dev_init+0x9c/0xf2
> do_one_initcall_+0x99/0x210
> ? set_debug_rodata+0x12/0x12
> kernel_init_freeable+0x1b3/0x240
> kernel_init+0x3/0x100
>
> 'git blame' doesn't seem to find anything relevant and recent in
> kernel/notifier.c or drivers/i2c/i2c-dev.c. Does this ring any
> bells, or is it time to bisect?
Can you try a newer -next or apply this patch on top?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/drivers/i2c?id=b980a26d02d1f54be31346666222304fcd27ea33
I think this should solve it.
Thanks for reporting!
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-17 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 14:59 next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot Valdis Kletnieks
2016-03-17 20:52 ` Wolfram Sang [this message]
2016-03-18 2:55 ` Valdis.Kletnieks
2016-03-18 7:24 ` Wolfram Sang
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=20160317205225.GA1482@katana \
--to=wsa@the-dreams.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).