Hello Matwey, I hope soon to be able to collect panic log, as tegra20 serial output is fixed in kernel-source now. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Wed, Aug 5, 2015 at 3:27 PM, Matwey V. Kornilov wrote:

That is strange, as far as I remember there is no panic timeout in JeOS

2015-08-03 14:17 GMT+03:00 Misha Komarovskiy :

...

Hello, I have no experience with kgdb. As system restarts after panic timeout i wanted to catch oops message in kernel output via serial console. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom

On Sat, Aug 1, 2015 at 1:46 PM, Matwey V. Kornilov wrote:

...

01.08.2015 12:48, Misha Komarovskiy пишет:

...

Hello, I found that latest images for my armv7 board (paz00/ac100) which use kernel-default have kernel panic on start without any output to serial console, but serial output was working last time i tested image back in may.

I cloned kernel-source git repo made sequence-patched kernel and recompiled it with enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to config/armv7hl/default config, but found that there is no ttyS0 output, only earlycon here is paste: http://paste.opensuse.org/31390203

Have you tried to use kgdb? Does it not work too?

...

Recompiling same kernel with multi_v7_defconfig config and same debug/earlyprintk options have no panics and normal serial output: http://paste.opensuse.org/13080662

Maybe kernel-default config require some extra tricks now to have serial output? I want to catch that panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom

-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hello, On Wed, Aug 5, 2015 at 5:12 PM, Misha Komarovskiy wrote:

Hello Matwey, I hope soon to be able to collect panic log, as tegra20 serial output is fixed in kernel-source now.

Panic happen before simple serial console started, but i made package of kernel-default with tegra DEBUG_LL enabled and now i have panic logs: http://paste.opensuse.org/15729922, log with initcall_debug http://paste.opensuse.org/76504505 I blame some kernel-default config option, because same kernel compiled with tegra_defconfig boots fine, but how to find which one?

--- Best Regards, Misha Komarovskiy zombahatgmaildotcom

On Wed, Aug 5, 2015 at 3:27 PM, Matwey V. Kornilov wrote:

...

That is strange, as far as I remember there is no panic timeout in JeOS

2015-08-03 14:17 GMT+03:00 Misha Komarovskiy :

...

Hello, I have no experience with kgdb. As system restarts after panic timeout i wanted to catch oops message in kernel output via serial console. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom

On Sat, Aug 1, 2015 at 1:46 PM, Matwey V. Kornilov wrote:

...

01.08.2015 12:48, Misha Komarovskiy пишет:

...

Hello, I found that latest images for my armv7 board (paz00/ac100) which use kernel-default have kernel panic on start without any output to serial console, but serial output was working last time i tested image back in may.

I cloned kernel-source git repo made sequence-patched kernel and recompiled it with enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to config/armv7hl/default config, but found that there is no ttyS0 output, only earlycon here is paste: http://paste.opensuse.org/31390203

Have you tried to use kgdb? Does it not work too?

...

Recompiling same kernel with multi_v7_defconfig config and same debug/earlyprintk options have no panics and normal serial output: http://paste.opensuse.org/13080662

Maybe kernel-default config require some extra tricks now to have serial output? I want to catch that panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom

-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru

-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hello Matwey, On Thu, Sep 3, 2015 at 10:35 PM, Matwey V. Kornilov wrote:

2015-09-03 19:23 GMT+03:00 Misha Komarovskiy :

...

Hello,

On Wed, Aug 5, 2015 at 5:12 PM, Misha Komarovskiy wrote:

...

Hello Matwey, I hope soon to be able to collect panic log, as tegra20 serial output is fixed in kernel-source now.

Panic happen before simple serial console started, but i made package of kernel-default with tegra DEBUG_LL enabled and now i have panic logs: http://paste.opensuse.org/15729922, log with initcall_debug http://paste.opensuse.org/76504505

I would suggest using gdb to understand where the issue appears, it is probably the fastest way. I wrote an instruction for myself how to do that, but unfortunately it is written in Russian and Google Translate doesn't help much: https://goo.gl/7LlcEz

I'll try to find more details with kgdb, it seems problems on my tegra20 family board starts after 3.19 kernel. Russian is my native language, i will follow your guide, thanks.

...

I blame some kernel-default config option, because same kernel compiled with tegra_defconfig boots fine, but how to find which one?

...

--- Best Regards, Misha Komarovskiy zombahatgmaildotcom

On Wed, Aug 5, 2015 at 3:27 PM, Matwey V. Kornilov wrote:

...

That is strange, as far as I remember there is no panic timeout in JeOS

2015-08-03 14:17 GMT+03:00 Misha Komarovskiy :

...

Hello, I have no experience with kgdb. As system restarts after panic timeout i wanted to catch oops message in kernel output via serial console. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom

On Sat, Aug 1, 2015 at 1:46 PM, Matwey V. Kornilov wrote:

...

01.08.2015 12:48, Misha Komarovskiy пишет: > Hello, > I found that latest images for my armv7 board (paz00/ac100) which use > kernel-default have kernel panic on start without any output to serial > console, but serial output was working last time i tested image back > in may. > > I cloned kernel-source git repo made sequence-patched kernel and > recompiled it with > enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to > config/armv7hl/default config, but found that there is no ttyS0 > output, only earlycon here is paste: > http://paste.opensuse.org/31390203 >

Have you tried to use kgdb? Does it not work too?

> Recompiling same kernel with multi_v7_defconfig config and same > debug/earlyprintk options have no panics and normal serial output: > http://paste.opensuse.org/13080662 > > Maybe kernel-default config require some extra tricks now to have serial output? > I want to catch that panic. > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom >

-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru

-- Best Regards, Misha Komarovskiy zombahatgmaildotcom

-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru

-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hello Andreas, On Mon, Sep 7, 2015 at 4:35 PM, Andreas Färber wrote:

Hi,

Am 03.09.2015 um 18:23 schrieb Misha Komarovskiy:

...

On Wed, Aug 5, 2015 at 5:12 PM, Misha Komarovskiy wrote:

...

Hello Matwey, I hope soon to be able to collect panic log, as tegra20 serial output is fixed in kernel-source now.

Panic happen before simple serial console started, but i made package of kernel-default with tegra DEBUG_LL enabled and now i have panic logs: http://paste.opensuse.org/15729922, log with initcall_debug http://paste.opensuse.org/76504505

I blame some kernel-default config option, because same kernel compiled with tegra_defconfig boots fine, but how to find which one?

Please take a look at function tegra_pmc_probe() (`git grep tegra_pmc_probe -- drivers/` to find the corresponding file). I'm guessing it tries to of_node_put() a NULL pointer or something else it shouldn't touch.

Thierry Reding pointed me to patch that fixes this oops in tegra pmc, it is already accepted for linux-next, http://patchwork.ozlabs.org/patch/493307/ and it should go to 4.1.7 or next stable release I just tested this patch with kernel-source stable branch and it fix boot for paz00 board, no panic anymore.

Regards, Andreas

-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi, Am 05.10.2015 um 18:50 schrieb Misha Komarovskiy:

Current image openSUSE-Tumbleweed-ARM-JeOS-paz00.armv7l-1.12.1-Build331.3.raw.xz now include kernel 4.2.1 which have tegra pmc fix included, kernel start to load now but i have new different oops, here is log http://paste.opensuse.org/3794617

Doesn't ring any bell... You could try a more recent U-Boot, but I doubt it's related. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org