[origen] kernel oops with quantal rootfs when networking starts

Thanks, I confirm the issue. We see the same behavior on LAVA.
As soon as we try to bring up ethernet interface, we get the kernel panic.

fyi, Image is using linux-linaro 3.7 rc6.

Has this come up when we moved from precise to quantal? Can some one verify if the same hwpack works/fails with precise?

On 7 December 2012 10:56, Tushar Behera <email address hidden> wrote:
> Has this come up when we moved from precise to quantal?

It coincides with the transition to quantal and we use linux-linaro
tracking (3.7 rc6)

> Can some one verify if the same hwpack works/fails with precise?

yes, I'll send this set up to lava.
@Botao, please double check on your side too.

Confirmed, this bug can also be reproduced on Origen Linux Linaro build:

http://snapshots.linaro.org/quantal/pre-built/origen/9/origen-quantal_developer_20121209-9.img.gz

wanted to know if we get the same issue with this hwpack when used with precise?

On 11 December 2012 06:11, Tushar Behera <email address hidden> wrote:
> wanted to know if we get the same issue with this hwpack when used with
> precise?

yes, same result:
http://validation.linaro.org/lava-server/scheduler/job/41588/log_file

I have used with the following builds
http://releases.linaro.org/12.11/ubuntu/leb-origen/linaro-precise-ubuntu-desktop-20121124-560.tar.gz
http://snapshots.linaro.org/quantal/hwpacks/origen/14/hwpack_linaro-origen_20121214-14_armhf_supported.tar.gz

ethernet is working on my side.

bootlog is attached for reference.

Botao/Soumya, modify /etc/network/interfaces is expected on headless rootfs like developer.
By default Origen doesn't have ethernet interface. For this reason, the hardware pack configuration doesn't contain a wired interface entry.

also observed with Samsung-origen quantal build
http://snapshots.linaro.org/quantal/pre-built/origen/9/origen-quantal_developer_20121209-9.img.gz

ethernet is unavilable for this builds.

kernel panic is happend after modify "/etc/network/interfaces" and run
sudo dhclient eth0

complete log is attached for reference.

on IRC someone said this issue cannot be reproduced on android?

Are we sure we are on 3.7 for android as well?

2012.11 release on Android was done on 3.7-rc6 kernel.

the kernel oops isn't triggered with LT kernel 3.6 (from 2012.10 release):
hwpack_linaro-leb-origen_20121021-424_armhf_supported.tar.gz

linaro-quantal-developer-20121216-12.tar.gz has been used for this test.

When I build the kernel locally with config generated through following command[1] , there are no kernel oops and ping test is successful. Tested on linux-linaro kernel [2].

[1] ./scripts/kconfig/merge_config.sh ./linaro/configs/ubuntu-minimal.conf ./linaro/configs/linaro-base.conf ./linaro/configs/origen.conf

[2] git://git.linaro.org/kernel/linux-linaro-tracking.git (ll-20121218.0)

Confirmed. Only the PPA package as the issue. I cross-built the same source and config available from the package and no kernel oops.

Submitted to LAVA for double checking:
http://validation.linaro.org/lava-server/scheduler/job/42486/log_file

As per comment #16, marking invalid for linaro-landing-team-samsung project.

Re-open for Samsung LT, we have the same issue on Arndale.
comment #16 is pointing a different behavior depending on the toolchain.
It's still not clear what's the root cause (kernel? toolchain? other?).

Issue is similar on both Origen and Arndale.
Issue doesn't happen when the kernel is cross-built with gcc-linaro 4.7-2012.08 but happens in all other cases (gcc-linaro > 4.7-2012.08 and native toolchain used by PPA).

After use the second method mentioned in bug description, Ethernet finally works on Samsung Origen board with Linux Linaro ubuntu Quantal image:

http://snapshots.linaro.org/quantal/pre-built/origen/64/origen-quantal_developer_20130130-64.img.gz

root@localhost:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr b8:8d:12:52:ed:c1
          inet addr:10.0.0.48 Bcast:10.0.0.255 Mask:255.255.255.0
          inet6 addr: fe80::ba8d:12ff:fe52:edc1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1375 (1.3 KB) TX bytes:1876 (1.8 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1280 (1.2 KB) TX bytes:1280 (1.2 KB)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@localhost:~# ping www.google.com
PING www.google.com (74.125.237.16) 56(84) bytes of data.
64 bytes from syd01s04-in-f16.1e100.net (74.125.237.16): icmp_req=1 ttl=53 time=34.1 ms
64 bytes from syd01s04-in-f16.1e100.net (74.125.237.16): icmp_req=2 ttl=53 time=32.4 ms
64 bytes from syd01s04-in-f16.1e100.net (74.125.237.16): icmp_req=3 ttl=53 time=33.2 ms
^C
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 32.421/33.277/34.191/0.738 ms