Re: DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0

2017-01-04 Thread Peter Zijlstra
On Tue, Jan 03, 2017 at 06:11:20PM -0800, Christian Kujau wrote: > Hi, > > booting v4.10-rc2 on this PowerPC G4 machine prints the following early > on, but then continues to boot and the machine is running fine so far: > > > BUG: key ef0ba7d0 not in .data! > DEBUG_LOCKS_WARN_ON(1) >

Re: DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0

2017-01-04 Thread Peter Zijlstra
On Tue, Jan 03, 2017 at 06:11:20PM -0800, Christian Kujau wrote: > Hi, > > booting v4.10-rc2 on this PowerPC G4 machine prints the following early > on, but then continues to boot and the machine is running fine so far: > > > BUG: key ef0ba7d0 not in .data! > DEBUG_LOCKS_WARN_ON(1) >

DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0

2017-01-03 Thread Christian Kujau
Hi, booting v4.10-rc2 on this PowerPC G4 machine prints the following early on, but then continues to boot and the machine is running fine so far: BUG: key ef0ba7d0 not in .data! DEBUG_LOCKS_WARN_ON(1) [ cut here ] WARNING: CPU: 0 PID: 1 at

DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0

2017-01-03 Thread Christian Kujau
Hi, booting v4.10-rc2 on this PowerPC G4 machine prints the following early on, but then continues to boot and the machine is running fine so far: BUG: key ef0ba7d0 not in .data! DEBUG_LOCKS_WARN_ON(1) [ cut here ] WARNING: CPU: 0 PID: 1 at