Re: [5.6.0-rc2-next-20200218/powerpc] Boot failure on POWER9

2020-02-18 Thread Kirill Tkhai
On 18.02.2020 14:38, Sachin Sant wrote: > > >> On 18-Feb-2020, at 4:20 PM, Kirill Tkhai wrote: >> >> Hi, Sachin, >> >> On 18.02.2020 13:45, Sachin Sant wrote: >>> >>> commit a75056fc1e7c >>> mm/memcontrol.c: allocate shri

Re: [5.6.0-rc2-next-20200218/powerpc] Boot failure on POWER9

2020-02-18 Thread Kirill Tkhai
On 18.02.2020 14:01, Kirill Tkhai wrote: > On 18.02.2020 13:50, Kirill Tkhai wrote: >> Hi, Sachin, >> >> On 18.02.2020 13:45, Sachin Sant wrote: >>> Todays next fails to boot on a POWER9 PowerVM logical partition >>> with following trace: >>> &

Re: [5.6.0-rc2-next-20200218/powerpc] Boot failure on POWER9

2020-02-18 Thread Kirill Tkhai
Hi, Sachin, On 18.02.2020 13:45, Sachin Sant wrote: > Todays next fails to boot on a POWER9 PowerVM logical partition > with following trace: > > [8.767660] random: systemd: uninitialized urandom read (16 bytes read) > [8.768629] BUG: Kernel NULL pointer dereference on read at 0x73b0

Re: [5.6.0-rc2-next-20200218/powerpc] Boot failure on POWER9

2020-02-18 Thread Kirill Tkhai
On 18.02.2020 13:50, Kirill Tkhai wrote: > Hi, Sachin, > > On 18.02.2020 13:45, Sachin Sant wrote: >> Todays next fails to boot on a POWER9 PowerVM logical partition >> with following trace: >> >> [8.767660] random: systemd: uninitialized urandom read (16

Re: [linux-next][ppc] kernel hung when running trinity fuzzer

2017-08-28 Thread Kirill Tkhai
On 28.08.2017 13:28, Abdul Haleem wrote: > Hi, > > offlate we are seeing hung task call traces when running trinity fuzzer > test. kernel go hung and requires machine reboot. > > Machine Type : Power 8 > Kernel : 4.13.0-rc6-next-20170825 > config: Tul-VM-config > > > call traces: >