Latest l-o and usb gadget + NFS root problems
Hi,
There seems to be something wrong with latest l-o, usb gadget ethernet and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine. This happens to me with beagleboard and a non-public omap3 board:
g_ether gadget: high speed config #1: CDC Ethernet (ECM)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=usb0, addr=192.168.2.15, mask=255.255.255.0, gw=255.255.255.255,
host=192.168.2.15, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=192.168.2.14, rootpath=Looking up port of RPC 100003/2 on 192.168.2.14 Looking up port of RPC 100005/1 on 192.168.2.14
VFS: Mounted root (nfs filesystem) on device 0:12. Freeing init memory: 140K
nfs: server 192.168.2.14 not responding, still trying
nfs: server 192.168.2.14 not responding, still trying
...
With the nonpublic board I was able to boot up occasionally, but it failed after doing something heavier on the nfs filesystem.
Tomi
Op 27 mrt 2009, om 10:40 heeft Tomi Valkeinen het volgende geschreven:
Quoted 21 lines
Hi,
There seems to be something wrong with latest l-o, usb gadget ethernet and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine. This happens to me with beagleboard and a non-public omap3 board:
g_ethergadget: high speed config #1: CDC Ethernet (ECM)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:device=usb0, addr=192.168.2.15, mask=255.255.255.0,gw=255.255.255.255,
host=192.168.2.15, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=192.168.2.14, rootpath=
Looking up port of RPC 100003/2 on 192.168.2.14
Looking up port of RPC 100005/1 on 192.168.2.14
VFS: Mounted root (nfs filesystem) on device 0:12. Freeing init memory: 140K
nfs: server 192.168.2.14 not responding, still trying
nfs: server 192.168.2.14 not responding, still trying
...
Quoted 2 lines
With the nonpublic board I was able to boot up occasionally, but it failed after doing something heavier on the nfs filesystem.
Are you running with lockdep enabled or disabled?
regards,
Koen
Hi,
Quoted 23 lines · ext Koen Kooi
Op 27 mrt 2009, om 10:40 heeft Tomi Valkeinen het volgende geschreven:
Quoted 21 lines
Hi,
There seems to be something wrong with latest l-o, usb gadget ethernet and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine. This happens to me with beagleboard and a non-public omap3 board:
g_ethergadget: high speed config #1: CDC Ethernet (ECM)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:device=usb0, addr=192.168.2.15, mask=255.255.255.0,gw=255.255.255.255,
host=192.168.2.15, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=192.168.2.14, rootpath=
Looking up port of RPC 100003/2 on 192.168.2.14
Looking up port of RPC 100005/1 on 192.168.2.14
VFS: Mounted root (nfs filesystem) on device 0:12. Freeing init memory: 140K
nfs: server 192.168.2.14 not responding, still trying
nfs: server 192.168.2.14 not responding, still trying
...
Quoted 4 lines
Quoted 2 lines
With the nonpublic board I was able to boot up occasionally, but it failed after doing something heavier on the nfs filesystem.
Are you running with lockdep enabled or disabled?
I was using default beagle defconfig, plus gadget eth compiled into kernel. DEBUG_LOCKDEP seems to be off.
Tomi
Quoted 6 lines · On Fri, 27 Mar 2009 11:40:21 +0200 Tomi Valkeinen <[email protected]>…
Hi,
There seems to be something wrong with latest l-o, usb gadget ethernet and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine. This happens to me with beagleboard and a non-public omap3 board:
I saw something very similar couple days ago on N810 and ethernet gadget. What was weird that when connection jammed, then also localhost stopped working. Unfortunately I didn't debug any further would it happen e.g. using BT PAN connection.
Jarkko
Quoted 15 lines · Jarkko Nikula
Quoted 6 lines · On Fri, 27 Mar 2009 11:40:21 +0200 Tomi Valkeinen <[email protected]>…
Hi,
There seems to be something wrong with latest l-o, usb gadget ethernet and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine. This happens to me with beagleboard and a non-public omap3 board:
I saw something very similar couple days ago on N810 and ethernet gadget. What was weird that when connection jammed, then also localhost stopped working. Unfortunately I didn't debug any further would it happen e.g. using BT PAN connection.
Quoted 6 lines
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
I got stuck in same problem last week. A reason was napi related changes in net/core/dev.c. There is a discussion and workaround too in LKML,
Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux
http://marc.info/?t=123789988400005&r=1&w=2
Regards,
Igor.
Quoted 8 lines · On Mon, 30 Mar 2009 08:47:20 +0200 ext Igor Mazanov <[email protected]> wrote:
I got stuck in same problem last week. A reason was napi related changes in
net/core/dev.c. There is a discussion and workaround too in LKML,Revert "gro: Fix legacy path
napi_completecrash", (was: Re: Linux
Thanks! Seems to help, much more reliable now :-)
Jarkko