Re: BUG: Bad page state in process swapper on new imx8qm board

2019-10-21 Thread Oliver Graute
On 17/10/19, Cengiz Can wrote:
> Hello Oliver,
> 
> > So after some more digging I assume that this error is related to a
> > missing "reserved-memory" node in my devicetree. Now I need to find
> > out how to split up my memory the right way for this imx8qm congatec
> > board.
> 
> I think asking in #linux-imx (freenode) would be a much better idea.
> 
> You can use https://webchat.freenode.net/ if you don't have an IRC
> client handy.

thx for this hint. I'll show up there.

Best regards,

Oliver

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: BUG: Bad page state in process swapper on new imx8qm board

2019-10-21 Thread Oliver Graute
On 17/10/19, Peng Fan wrote:
> 
> 
> > -Original Message-
> > From: Oliver Graute 
> > Sent: 2019年10月17日 15:34
> > To: kernelnewbies@kernelnewbies.org; Aisheng Dong
> > ; Peng Fan 
> > Subject: Re: BUG: Bad page state in process swapper on new imx8qm board
> > 
> > On 16/10/19, Oliver Graute wrote:
> > > Hello list,
> > >
> > > I try to bootup up a new imx8qm congatec board and I have written a
> > > dts file for it and applied some imx8qm related patches which are not
> > > mainline yet but working fine on another imx8qm board (same cpu,
> > > different board vendor).
> > >
> > > The Kernel starts to boot. But unfortunately its stucked after few
> > > seconds with a lot memory/swapper issues.
> > >
> > > BUG: Bad page state in process swapper
> > >
> > > Some clue what`s going on here?
> > 
> > So after some more digging I assume that this error is related to a missing
> > "reserved-memory" node in my devicetree. Now I need to find out how to
> > split up my memory the right way for this imx8qm congatec board.
> 
> Which uboot release are you using? Did you include M4 image in flash.bin?

I'am using the u-boot master branch with my board patches. Together with
the M4 Image. This particular problem is solved now by adding the right
reserved-memory statement and linux,cma {} statement.

No more kernel crashes yet. Now the kernel starts systemd and is stucked
there. I get no login prompt. It looks for me like getty can't find any
serial to attach. But the kernel is still running and writing to serial
lpuart32.

Best regards,

Oliver

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


RE: BUG: Bad page state in process swapper on new imx8qm board

2019-10-17 Thread Peng Fan


> -Original Message-
> From: Oliver Graute 
> Sent: 2019年10月17日 15:34
> To: kernelnewbies@kernelnewbies.org; Aisheng Dong
> ; Peng Fan 
> Subject: Re: BUG: Bad page state in process swapper on new imx8qm board
> 
> On 16/10/19, Oliver Graute wrote:
> > Hello list,
> >
> > I try to bootup up a new imx8qm congatec board and I have written a
> > dts file for it and applied some imx8qm related patches which are not
> > mainline yet but working fine on another imx8qm board (same cpu,
> > different board vendor).
> >
> > The Kernel starts to boot. But unfortunately its stucked after few
> > seconds with a lot memory/swapper issues.
> >
> > BUG: Bad page state in process swapper
> >
> > Some clue what`s going on here?
> 
> So after some more digging I assume that this error is related to a missing
> "reserved-memory" node in my devicetree. Now I need to find out how to
> split up my memory the right way for this imx8qm congatec board.

Which uboot release are you using? Did you include M4 image in flash.bin?

Regards,
Peng.

> 
> Any hints?
> 
> Best regards,
> 
> Oliver
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: BUG: Bad page state in process swapper on new imx8qm board

2019-10-17 Thread Cengiz Can
Hello Oliver,

> So after some more digging I assume that this error is related to a
> missing "reserved-memory" node in my devicetree. Now I need to find
> out how to split up my memory the right way for this imx8qm congatec
> board.

I think asking in #linux-imx (freenode) would be a much better idea.

You can use https://webchat.freenode.net/ if you don't have an IRC
client handy.

Good luck!

-- 
Cengiz Can


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: BUG: Bad page state in process swapper on new imx8qm board

2019-10-17 Thread Oliver Graute
On 16/10/19, Oliver Graute wrote:
> Hello list,
> 
> I try to bootup up a new imx8qm congatec board and I have written a dts
> file for it and applied some imx8qm related patches which are not
> mainline yet but working fine on another imx8qm board (same cpu,
> different board vendor).
> 
> The Kernel starts to boot. But unfortunately its stucked after few
> seconds with a lot memory/swapper issues.
> 
> BUG: Bad page state in process swapper
> 
> Some clue what`s going on here?

So after some more digging I assume that this error is related to a
missing "reserved-memory" node in my devicetree. Now I need to find out
how to split up my memory the right way for this imx8qm congatec board.

Any hints?

Best regards,

Oliver

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


BUG: Bad page state in process swapper on new imx8qm board

2019-10-16 Thread Oliver Graute
Hello list,

I try to bootup up a new imx8qm congatec board and I have written a dts
file for it and applied some imx8qm related patches which are not
mainline yet but working fine on another imx8qm board (same cpu,
different board vendor).

The Kernel starts to boot. But unfortunately its stucked after few
seconds with a lot memory/swapper issues.

BUG: Bad page state in process swapper

Some clue what`s going on here?

Best regards,

Oliver

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x00 [0x410fd034]
[0.00] Linux version 5.3.0-rc7-next-20190904-00033-gf19a0a4e7252-dirty 
(alarm@imx8qm) (gcc version 8.3.0 (GCC)) #4 SMP PREEMPT Thu Oct 10 13:23:33 UTC 
2019
[0.00] Machine model: Congatec QMX8 Qseven series
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 32 MiB at 0xfe00
[0.00] earlycon: lpuart32 at MMIO 0x5a06 (options '')
[0.00] printk: bootconsole [lpuart32] enabled
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x8020-0x00097fff]
[0.00] NUMA: NODE_DATA [mem 0x97f3e2800-0x97f3e3fff]
[0.00] Zone ranges:
[0.00]   DMA32[mem 0x8020-0x]
[0.00]   Normal   [mem 0x0001-0x00097fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x8020-0x]
[0.00]   node   0: [mem 0x00088000-0x00097fff]
[0.00] Initmem setup node 0 [mem 0x8020-0x00097fff]
[0.00] psci: probing for conduit method from DT.
[0.00] psci: PSCIv1.1 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] psci: MIGRATE_INFO_TYPE not supported.
[0.00] psci: SMC Calling Convention v1.1
[0.00] percpu: Embedded 22 pages/cpu s52952 r8192 d28968 u90112
[0.00] Detected VIPT I-cache on CPU0
[0.00] CPU features: detected: ARM erratum 845719
[0.00] CPU features: detected: GIC system register CPU interface
[0.00] Speculative Store Bypass Disable mitigation not required
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 1547784
[0.00] Policy zone: Normal
[0.00] Kernel command line: console=ttyLP0,115200 root=/dev/mmcblk2p2 
rootwait rw earlycon
[0.00] Dentry cache hash table entries: 1048576 (order: 11, 8388608 
bytes, linear)
[0.00] Inode-cache hash table entries: 524288 (order: 10, 4194304 
bytes, linear)
[0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
[0.00] software IO TLB: mapped [mem 0xfa00-0xfe00] (64MB)
[0.00] BUG: Bad page state in process swapper  pfn:b0001
[0.00] page:fea00040 refcount:0 mapcount:1 
mapping: index:0x0
[0.00] flags: 0x0()
[0.00] raw:    

[0.00] raw:    

[0.00] page dumped because: nonzero mapcount
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 
5.3.0-rc7-next-20190904-00033-gf19a0a4e7252-dirty #4
[0.00] Hardware name: Congatec QMX8 Qseven series (DT)
[0.00] Call trace:
[0.00]  dump_backtrace+0x0/0x140
[0.00]  show_stack+0x14/0x20
[0.00]  dump_stack+0xb0/0xf4
[0.00]  bad_page+0xec/0x118
[0.00]  free_pages_check_bad+0x70/0xa8
[0.00]  __free_pages_ok+0x2a8/0x2c8
[0.00]  __free_pages+0x4c/0x58
[0.00]  __free_pages_core+0xc0/0xd0
[0.00]  memblock_free_pages+0x10/0x18
[0.00]  memblock_free_all+0x188/0x254
[0.00]  mem_init+0x48/0x58
[0.00]  start_kernel+0x254/0x484
[0.00] Disabling lock debugging due to kernel taint
[0.00] BUG: Bad page state in process swapper  pfn:b0002
[0.00] page:fea00080 refcount:0 mapcount:1 
mapping: index:0x0
[0.00] flags: 0x0()
[0.00] raw:    

[0.00] raw:    

[0.00] page dumped because: nonzero mapcount
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Tainted: GB 
5.3.0-rc7-next-20190904-00033-gf19a0a4e7252-dirty #4
[0.00] Hardware name: Congatec QMX8 Qseven series (DT)
[0.00] Call trace:
[0.00]  dump_backtrace+0x0/0x140
[0.00]  show_stack+0x14/0x20
[0.00]  dump_stack+0xb0/0xf4
[0.00]  bad_page+0xec/0x118
[0.00]  free_pages_check_bad+0x70/0xa8
[0.00]  __free_pages_ok+0x2a8/0x2c8
[0.00]  __free_pages+0x4c/0x58
[