Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-07 Thread Carl Jacobsen
On Fri, Nov 6, 2020 at 4:25 AM Michael Ellerman wrote: > So something seems to have gone wrong linking this, I see eg: > > 10004a8c : > 10004a8c: 2b 10 40 3c lis r2,4139 > 10004a90: 88 f7 42 38 addir2,r2,-2168 > 10004a94: a6 02 08 7c mflrr0 >

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-06 Thread Michal Suchánek
On Mon, Nov 02, 2020 at 12:14:27PM -0800, Carl Jacobsen wrote: > I've got a SUSE 15.1 install (on ppc64le) that kernel panics on a very > simple > test program, built in a slightly unusual way. > > I'm compiling on SUSE 12, using gcc 4.8.3. I'm linking to a static > copy of libcrypto.a (from opens

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-06 Thread Michael Ellerman
Carl Jacobsen writes: > On Thu, Nov 5, 2020 at 2:19 AM Michael Ellerman wrote: > >> Carl Jacobsen writes: >> > The panic (on a call to malloc from static linked libcrypto) looks like >> > this: >> >> What hardware is this on? >> > > Thank you for looking into this. > > The system that's panickin

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-05 Thread Carl Jacobsen
On Thu, Nov 5, 2020 at 2:19 AM Michael Ellerman wrote: > Carl Jacobsen writes: > > The panic (on a call to malloc from static linked libcrypto) looks like > > this: > > What hardware is this on? > Thank you for looking into this. The system that's panicking identifies like this: # uname -a

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-05 Thread Segher Boessenkool
On Thu, Nov 05, 2020 at 09:19:22PM +1100, Michael Ellerman wrote: > Carl Jacobsen writes: > This doesn't make a lot of sense. > > > Bad kernel stack pointer 7fffeac0 at 700 > > "at 700" is the regs->nip value, and suggests we're trying to handle a > program check, which is either a trap or B

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-05 Thread Michael Ellerman
Carl Jacobsen writes: > The panic (on a call to malloc from static linked libcrypto) looks like > this: Thanks. This doesn't make a lot of sense. > Bad kernel stack pointer 7fffeac0 at 700 "at 700" is the regs->nip value, and suggests we're trying to handle a program check, which is either

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-03 Thread Carl Jacobsen
The panic (on a call to malloc from static linked libcrypto) looks like this: Bad kernel stack pointer 7fffeac0 at 700 Oops: Bad kernel stack pointer, sig: 6 [#1] SMP NR_CPUS=2048 NUMA pSeries Modules linked in: scsi_transport_iscsi af_packet xt_tcpudp ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_c

Re: Kernel panic from malloc() on SUSE 15.1?

2020-11-02 Thread Michael Ellerman
Carl Jacobsen writes: > I've got a SUSE 15.1 install (on ppc64le) that kernel panics on a very > simple > test program, built in a slightly unusual way. > > I'm compiling on SUSE 12, using gcc 4.8.3. I'm linking to a static > copy of libcrypto.a (from openssl-1.1.1g), built without threads. > I ha

Kernel panic from malloc() on SUSE 15.1?

2020-11-02 Thread Carl Jacobsen
I've got a SUSE 15.1 install (on ppc64le) that kernel panics on a very simple test program, built in a slightly unusual way. I'm compiling on SUSE 12, using gcc 4.8.3. I'm linking to a static copy of libcrypto.a (from openssl-1.1.1g), built without threads. I have a 10 line C test program that com