José Luís wrote:
Hi,
I have some problems with the arm omap 1610 board. I'm trying to use
rt-preemption patch,
but when kernel boot, it mount nfs filesystem and after network down, see
console messages:
IP-Config: Got DHCP answer from 10.0.0.1, my address is 10.0.0.9
IP-Config: Complete:
device=eth0, addr=10.0.0.9, mask=255.255.255.0, gw= 255.255.255.255,
host=10.0.0.9, domain=atena, nis-domain=(none),
bootserver=10.0.0.1, rootserver=10.0.0.1, rootpath=
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
VFS: Mounted root (nfs filesystem).
Freeing init memory: 132K
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server 10.0.0.1 not responding, still trying
nfs: server 10.0.0.1 not responding, still trying
nfs: server 10.0.0.1 not responding, still trying
nfs: server 10.0.0.1 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server 10.0.0.1 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
I'm using kernel image linux-2.6.23.9 from kernel.org, the
2.6.23-omap1patch from
muru.com and 2.6.23.9-rt12 patch from Ingo Molnar.
You need a small OMAP specific patch on top of -rt of Ingo Molnar. See
http://linux.omap.com/pipermail/linux-omap-open-source/2007-October/011613.html
Especially the kernel/irq/manage.c changes are there to fix above
transmit timed out.
Regards
Dirk
P.S.: See
http://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch#Platforms_Tested_and_in_Use_with_CONFIG_PREEMPT_RT
as well.
-
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
