Skip to contentSkip to conversation

4.10-rc1 on Nokia N900: regression, WARN_ON() omap_l3_smx.c

DISCUSSION Pavel Machek 2 participants 4 messages Dec 29, 2016 – Jan 23, 2017

lore
Share & tools
lore
#0 lore raw

Hi!

I forgot I had v4.10-rc1 running, and now I got warning on all the consoles (hand-copied).

Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060
...
Comm: kworker/0:0 Not tainted.

Workqueue: events musb_irq_work
...
PC is at musb_default_readb().
...
WARNING: CPU: 0 ... at drivers/bus/omap_l3_smx.c:166
omap3_l3_app_irq+0xcc/...
Tainted: GDW.

I do have patches to allow nfsroot over usb. But they worked ok in v4.9... Does anyone see it, too?

Best regards,

Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161230/ea397025/attachment.sig>
#1 lore raw
Quoted 6 lines · Pavel Machek

Hi!

I forgot I had v4.10-rc1 running, and now I got warning on all the consoles (hand-copied).

Quoted 8 lines

Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060
...
Comm: kworker/0:0 Not tainted.

Workqueue: events musb_irq_work

...
PC is at musb_default_readb().
...

This means the clocks are not enabled at that point.

Quoted 3 lines
WARNING: CPU: 0 ... at drivers/bus/omap_l3_smx.c:166
omap3_l3_app_irq+0xcc/...
Tainted: GDW.

If you comment out postcore_initcall_sync(omap3_l3_init); in drivers/bus/omap_l3_smx.c you'll see the proper stack trace instead of the l3 interrupt trace. The system will hang at that point most likely.

Quoted 2 lines

I do have patches to allow nfsroot over usb. But they worked ok in v4.9... Does anyone see it, too?

Hmm not much has changed since v4.9. Are you sure you had v4.9 or some earlier v4.9-rc version?

Regards,

Tony

#2 lore raw

Hi!

Quoted 24 lines
Quoted 4 lines

I forgot I had v4.10-rc1 running, and now I got warning on all the consoles (hand-copied).

Quoted 8 lines

Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060
...
Comm: kworker/0:0 Not tainted.

Workqueue: events musb_irq_work

...
PC is at musb_default_readb().
...

This means the clocks are not enabled at that point.

Quoted 3 lines
WARNING: CPU: 0 ... at drivers/bus/omap_l3_smx.c:166
omap3_l3_app_irq+0xcc/...
Tainted: GDW.

If you comment out postcore_initcall_sync(omap3_l3_init); in drivers/bus/omap_l3_smx.c you'll see the proper stack trace instead of the l3 interrupt trace. The system will hang at that point most likely.

Quoted 5 lines
Quoted 2 lines

I do have patches to allow nfsroot over usb. But they worked ok in v4.9... Does anyone see it, too?

Hmm not much has changed since v4.9. Are you sure you had v4.9 or some earlier v4.9-rc version?

I believe v4.9 works.

But... this may be tricky to reproduce. It happened once so far... after I reconnected N900 to computer when it was running for a while. I do have USB cable with power meter on it, thus "flakey". Lets see if it reappears...
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170102/09a252bc/attachment.sig>
#3 lore raw
In reply to Tony Lindgren

Hi!

Quoted 27 lines · Pavel Machek
Quoted 6 lines

Hi!

I forgot I had v4.10-rc1 running, and now I got warning on all the consoles (hand-copied).

Quoted 8 lines

Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060
...
Comm: kworker/0:0 Not tainted.

Workqueue: events musb_irq_work

...
PC is at musb_default_readb().
...

This means the clocks are not enabled at that point.

Quoted 3 lines
WARNING: CPU: 0 ... at drivers/bus/omap_l3_smx.c:166
omap3_l3_app_irq+0xcc/...
Tainted: GDW.

If you comment out postcore_initcall_sync(omap3_l3_init); in drivers/bus/omap_l3_smx.c you'll see the proper stack trace instead of the l3 interrupt trace. The system will hang at that point most likely.

Quoted 5 lines
Quoted 2 lines

I do have patches to allow nfsroot over usb. But they worked ok in v4.9... Does anyone see it, too?

Hmm not much has changed since v4.9. Are you sure you had v4.9 or some earlier v4.9-rc version?

It happened again in -rc5. I have full dmesg this time.

I started new thread with "

Subject: v4.9 to v4.10 regression: oops when USB cable is plugged in.

". It does no longer look completely scary.

Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170124/2ddc1b44/attachment.sig>