Hard freeze (ethernet related?)

[Riccardo Bortolato]

Hello,

sorry if it already has been asked but I couldn't find anything like this so I'm gonna post my issue.

I'm running ubuntu 13.04 with kernel 3.8.13-bone41 from emmc (powered by a 5V 2A power supply) and I am experiencing this:

unplugging (and/or plugging in back) the ethernet cable can result in the board freezing and the USR2 led stuck on.

I tried reading output from UART0 but there's nothing useful.

How can I further debug this? Is it a known issue?

Thanks,
Riccardo

[Gerald Coley]

Can you try it using the latest Debian image?

http://beagleboard.org/latest-images

Gerald

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Riccardo Bortolato]

Hello Gerald,

I downloaded debian, ran it from the uSD and I was installing a bunch
of stuff..after a while here's what I got:

[ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds.
[ 360.546242] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks
[ 360.561039] [<c0010443>] (unwind_backtrace+0x1/0x8a) from
[<c0455ced>] (panic+0x51/0x148)
[ 360.569697] [<c0455ced>] (panic+0x51/0x148) from [<c006770b>]
(watchdog+0x14f/0x194)
[ 360.577909] [<c006770b>] (watchdog+0x14f/0x194) from [<c003fb8f>]
(kthread+0x67/0x74)
[ 360.586206] [<c003fb8f>] (kthread+0x67/0x74) from [<c000c0dd>]
(ret_from_fork+0x11/0x34)
[ 360.594750] drm_kms_helper: panic occurred, switching back to text console

USR2 led stuck on

Ideas?

Thanks

> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/5vaehZewk2U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

[Gerald Coley]

Sounds like some sort of SW issue.

Gerald

[Robert Nelson]

On Thu, Mar 27, 2014 at 1:54 PM, Riccardo Bortolato <riky...@gmail.com> wrote:

> Hello Gerald,
>
> I downloaded debian, ran it from the uSD and I was installing a bunch
> of stuff..after a while here's what I got:
>
> [ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds.
> [ 360.546242] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks
> [ 360.561039] [<c0010443>] (unwind_backtrace+0x1/0x8a) from
> [<c0455ced>] (panic+0x51/0x148)

That's the 3.8 mmc driver.. We've back-ported a few fixes from
v3.12/v3.13 to "fix" that issue, but for some devices it's still a
problem. If you aren't using any capes (or just a simple usart/spi
ones, we have another option for you, essentially running v3.13.x)

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[Riccardo Bortolato]

Hello Robert,

well I just need usart1, usb and ethernet so the 3.13 option is fine for me.

Meanwhile I was just searching for similar issues and found this:

http://blog.machinekit.io/2013/10/hung-task-bug-in-xenomai-kernel.html
which points to
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7472bab236bdee1173412585591329e718f4d324

I am posting this since you replied so fast I didn't even took a look
at the patches you added to your kernels!

Do you think this is the same issue I posted in the original post?
Anyway, now I'll build a 3.13 deb.

P.S. thanks for your tools/scripts, the whole process works like a charm :)

Thanks

[Robert Nelson]

On Thu, Mar 27, 2014 at 2:05 PM, Riccardo Bortolato <riky...@gmail.com> wrote:
> Hello Robert,
>
> well I just need usart1, usb and ethernet so the 3.13 option is fine for me.
>
> Meanwhile I was just searching for similar issues and found this:
>
> http://blog.machinekit.io/2013/10/hung-task-bug-in-xenomai-kernel.html
> which points to
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7472bab236bdee1173412585591329e718f4d324
>
> I am posting this since you replied so fast I didn't even took a look
> at the patches you added to your kernels!

Yeap, that's the patch we backported..

https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L848

It helped, in some situations but something else between v3.8-v3.13 is
also needed..

> Do you think this is the same issue I posted in the original post?
> Anyway, now I'll build a 3.13 deb.
>
> P.S. thanks for your tools/scripts, the whole process works like a charm :)

So before you build, you can actually test..

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --beta-kernel

For capes, if you need "ttyO1" this the way v3.13.x is setup:

with: 2014-03-04

cd /boot/uboot/dtbs/
cp am335x-boneblack.dtb am335x-boneblack-bak.dtb
cp am335x-boneblack-ttyO1.dtb am335x-boneblack.dtb

with: 2014-03-19

Edit: /boot/uboot/uEnv.txt

set:
CAPE=ttyO1

[Riccardo Bortolato]

Thank you (awesome scripts!)

I'll try to test in the next days and let you know (even if it looks
like the issue is pretty much solved fortunately :))

Riccardo

[Riccardo Bortolato]

Robert,

with the latest debian image (and 3.13) I can get it to crash with the
same procedure. Only this time no debug output in uart0 and USR0+USR2
leds stuck on.

I must say that i swapped wicd for network-manager. Do you think this
could be a cause? Any way I can help further debug this issue?

Thanks,
Riccardo

[Riccardo Bortolato]

Update: looks like I obtain the bug in ubuntu raring with kernel 3.13
and wicd, so network-manager should not be an issue.

[Riccardo Bortolato]

Another update: I think it could be dhcp-related, I can make it happen
also connecting an usb-wifi while ethernet is active and working..
really weird!

[Robert Nelson]

On Fri, Mar 28, 2014 at 3:14 AM, Riccardo Bortolato <riky...@gmail.com> wrote:
> Robert,
>
> with the latest debian image (and 3.13) I can get it to crash with the
> same procedure. Only this time no debug output in uart0 and USR0+USR2
> leds stuck on.
>
> I must say that i swapped wicd for network-manager. Do you think this
> could be a cause? Any way I can help further debug this issue?

It's network-manager... (or any gtk2 app that seems to to decompress
something png related)

See:
http://bugs.elinux.org/issues/35

That's why i went with wicd..

TI's looking into it, so far we've tried to jtag debug it, but even
the jtag interface locks up..

[Riccardo Bortolato]

Ouch!

Is there some public bug I can subscribe to?

Thank you

[Robert Nelson]

On Fri, Mar 28, 2014 at 9:01 AM, Riccardo Bortolato <riky...@gmail.com> wrote:
> Ouch!
>
> Is there some public bug I can subscribe to?

Not really, It's one of the main subject's in our inside weekly
meeting. When it's fixed, there will be much rejoicing on this list.

[Riccardo Bortolato]

I'll follow the list then, thank you.

Riccardo