Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1359939 > unrolled thread

next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot

Back to article view | Back to linux.kernel

Contents

  next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot Valdis Kletnieks <Valdis.Kletnieks@vt.edu> - 2016-03-17 16:10 +0100
    Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at  boot Wolfram Sang <wsa@the-dreams.de> - 2016-03-17 22:00 +0100
      Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot Valdis.Kletnieks@vt.edu - 2016-03-18 04:00 +0100
        Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at  boot Wolfram Sang <wsa@the-dreams.de> - 2016-03-18 08:30 +0100

#1359939 — next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot

[Multipart message — attachments visible in raw view] — view raw

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?

[toc] | [next] | [standalone]

#1360191 — Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#1360319

[Multipart message — attachments visible in raw view] — view raw

On Thu, 17 Mar 2016 21:52:25 +0100, Wolfram Sang said:

> 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=3Db980a26d02d1f54be31346666222304fcd27ea33
>
> I think this should solve it.

Confirming that issue is fixed in next-20160317.

Now on to fix the *next* problem :)

[toc] | [prev] | [next] | [standalone]

#1360388 — Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at boot

[Multipart message — attachments visible in raw view] — view raw

> Confirming that issue is fixed in next-20160317.

Thanks for confirming...

> Now on to fix the *next* problem :)

...and good luck with that!

   Wolfram

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web