Re: [cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

Hi James, On Wed, Apr 18, 2018 at 02:59:15PM +0100, James Simmons wrote: Hello, FYI this happens in mainline kernel 4.17.0-rc1. It looks like a new regression. [7.587002] lnet_selftest_init+0x2c4/0x5d9: lnet_selftest_init at

Re: [cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

Hi James, On Wed, Apr 18, 2018 at 02:59:15PM +0100, James Simmons wrote: Hello, FYI this happens in mainline kernel 4.17.0-rc1. It looks like a new regression. [7.587002] lnet_selftest_init+0x2c4/0x5d9: lnet_selftest_init at

Re: [cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

> Hello, > > FYI this happens in mainline kernel 4.17.0-rc1. > It looks like a new regression. > > [7.587002] lnet_selftest_init+0x2c4/0x5d9: > lnet_selftest_init at > drivers/staging/lustre/lnet/selftest/module.c:134 > [7.587002] ?

Re: [cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

> Hello, > > FYI this happens in mainline kernel 4.17.0-rc1. > It looks like a new regression. > > [7.587002] lnet_selftest_init+0x2c4/0x5d9: > lnet_selftest_init at > drivers/staging/lustre/lnet/selftest/module.c:134 > [7.587002] ?

[cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

Hello, FYI this happens in mainline kernel 4.17.0-rc1. It looks like a new regression. It occurs in 5 out of 5 boots. [6.524361] ledtrig-cpu: registered to indicate activity on CPUs [6.527658] NET: Registered protocol family 4 [6.528191] comedi: version 0.7.76 -

[cfs_trace_lock_tcd] BUG: unable to handle kernel NULL pointer dereference at 00000050

Hello, FYI this happens in mainline kernel 4.17.0-rc1. It looks like a new regression. It occurs in 5 out of 5 boots. [6.524361] ledtrig-cpu: registered to indicate activity on CPUs [6.527658] NET: Registered protocol family 4 [6.528191] comedi: version 0.7.76 -