Skip to contentSkip to conversation

Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS)

DISCUSSION 임근식 2 participants 2 messages Jan 19, 2006 Network drivers

lore
Share & tools
lore

임근식

author
#0 lore raw

Thanks for your replying. I already successed with nfs root file system using kernel.org.2.6.15 + omap2.patch. But, In my circumstance, Now, I have to do booting using 2.6.10 kernel.
Please. inform method that can do Poting to omap board using 2.6.10 kernel because I use 2.6.10 version.

<-----Original Message----->

Quoted 5 lines

From: "Tony Lindgren" <[email protected]>
To: "임근식" <[email protected]>
Cc: <[email protected]>
Sent: 2006-01-19 16:30
Subject: Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS)

Quoted 53 lines · 임근식

It seems that my email system problem. so i changed email address.

Subject - Oops: 805 [#1] problem using kernel.2.6.10.omap1patch with NFS(RFS)
-----------------------------------------

I finished compiling and porting ousing kernel.2.6.10 of kernel.org and patch.2.6.10.omap1. But, When I try booting with compiled zImage on omap5912osk board, I meet below error message. For reference, When I use Ramdisk(root file system), kerenl is booted successfully. Only When I use NFS Root file system , error happened like belows. Please. What's reason? . Tell me how to solve this problem. (P.S: When I tryed "ping target.board.ip.address" command on host pc(RH9.0), I receviced TTL reply. )

* Test Envirionment.

(quoted diff) +0 -6
-board : TI omap5912.osk board 
-Ethernet : SMC91C94 Ethernet card 
-kernel.org :kernel.2.6.10.tar.gz (www.kernel.org ) 
-compiler :montavista _arm_v5 
-omap patch :http://www.muru.com/linux/omap/patches/patch-2.6.10-omap1.bz2 
-Rootfilesystem: NFS Root file system

* When I boot kernel.2.6.10.omap1 with nfsroot , I meet "Oops: 805 [#1]:" mesasge like belows. ............... upper omission.....................
eth0: link up
IP-Config: Complete:
device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.2,
host=192.168.0.10, domain=, nis-domain=(none),
bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath= Looking up port of RPC 100003/2 on 192.168.0.2 Looking up port of RPC 100005/1 on 192.168.0.2
VFS: Mounted root (nfs filesystem).
Freeing init memory: 104K
<------------------- Ref: After 10 minutes, Belows message appeared on console. Unable to handle kernel paging request at virtual address c2000000 pgd = c0010000 [c2000000] *pgd=00000000 Internal error: Oops: 805 [#1] Modules linked in:

CPU: 0 
PC is at .insw_8_lp+0x30/0x44 
LR is at 0x4341 
pc : [] lr : [<00004341>] Not tainted

sp : c0299e44 ip : 43414341 fp : c0299e98
r10: c0339000 r9 : c2852000 r8 : 00000000
r7 : c0339220 r6 : fffffffa r5 : 43414341 r4 : 43414341 r3 : 43414341 r2 : 7fe11855 r1 : c1fffff4 r0 : c2852008
Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment user
Control: 5717F Table: 10010000 DAC: 00000015 Process init (pid: 1, stack limit = 0xc0298190)

Stack: (0xc0299e44 to 0xc029a000)

9e40: c03f74e0 c2852000 c012de94 c1c230b2 00004030 00000007 00000033 9e60: c0339220 c033ea20 000000a0 00000000 c033ea20 00000000 00000000 000000a0 9e80: c0299f40 c0299f40 fefbe418 c0299ebc c0299e9c c00232f8 c012dc14 c0210540 9ea0: 000000a0 c033ea20 c0299f40 c01d584c c0299edc c0299ec0 c0023454 c00232bc 9ec0: 000000a1 00001e00 00000001 c0210570 c0299f08 c0299ee0 c002e7d8 c00233b4 9ee0: c0299f74 fefecb00 c0298000 c0028d4c 20000013 c020e740 c0299f40 c0299f3c 9f00: c0299f0c c00235dc c002e744 0000001e c0299fb0 c0299f74 fefecb00 ffffffff 9f20: c0028d4c 20000013 ffffffff 40127000 c0299fac c0299f40 c00223e0 c002359c 9f40: c0013ff8 c0007ff8 00000000 10002401 ffff1000 c0010000 10002001 00000000 9f60: c0299fb0 00000000 40127000 c0299fac 00003ff8 c0299f88 c0298000 c0028d4c 9f80: 20000013 ffffffff fefecb00 c01d2fa0 ffff1000 60000010 00057177 c0299fec 9fa0: 00000000 c0299fb0 c0022718 c0028cd8 00000000 00000001 401282b8 ffff0fff 9fc0: 00000000 00000000 401282b8 000012b8 00000000 00000000 40127000 00000000 9fe0: beffff3c befffdd8 40049b94 ffff1000 60000010 ffffffff e5903084 e3530001

Quoted 6 lines
Backtrace: 
[] (smc_interrupt+0x0/0x6d0) from [] (__do_irq+0x4c/0x88) [] (__do_irq+0x0/0x88) from [] (do_edge_IRQ+0xb0/0x12c) r8 = C01D584C r7 = C0299F40 r6 = C033EA20 r5 = 000000A0 r4 = C0210540 [] (do_edge_IRQ+0x0/0x12c) from [] (gpio_irq_handler+0xa4/0xb8) r7 = C0210570 r6 = 00000001 r5 = 00001E00 r4 = 000000A1 [] (gpio_irq_handler+0x0/0xb8) from [] (asm_do_IRQ+0x50/0x150) [] (asm_do_IRQ+0x0/0x150) from [] (__irq_svc+0x20/0x80) [] (do_translation_fault+0x0/0xac) from [] (ret_from_exception+0x0/0x10) r8 = C0299FEC r7 = 00057177 r6 = 60000010 r5 = FFFF1000 r4 = C01D2FA0 
Code: e185580c e1d0c0b0 e1d0e0b0 e18cc80e (e8a11038)

<0>Kernel panic - not syncing: Aiee, killing interrupt handler!

end of Line.

This sounds like the old wrong-flash-memory-bus-timings problem with smc91x. Try a more recent kernel and it should go away.

Tony

------------------------------------------------------------------------
NAVER :: Korea's No.1 portal service
www.naver.com

#1 lore raw

Hi,

Quoted 5 lines

Thanks for your replying. I already successed with nfs root file system using kernel.org.2.6.15 + omap2.patch. But, In my circumstance, Now, I have to do booting using 2.6.10 kernel.
Please. inform method that can do Poting to omap board using 2.6.10 kernel because I use 2.6.10 version.

Try this patch. Hope it works for you.

Best Regards,

HK.
--

drivers/net/smc91x.c +21 -0
@@ -483,6 +483,11 @@
 		dev->name, packet_number, status,
 		packet_len, packet_len);
 
+	if (unlikely(packet_len == 0 && !(status & RS_ERRORS))) {
+		printk(KERN_ERR "%s: bad memory timings: rxlen %u status %x\n",
+			dev->name, packet_len, status);
+		status |= RS_TOOSHORT;
+	}
 	if (unlikely(status & RS_ERRORS)) {
 		SMC_WAIT_MMU_BUSY();
 		SMC_SET_MMU_CMD(MC_RELEASE);

@@ -1333,6 +1338,19 @@
 	return IRQ_HANDLED;
 }
 
+#ifdef CONFIG_NET_POLL_CONTROLLER
+/*
+ * Polling receive - used by netconsole and other diagnostic tools
+ * to allow network i/o with interrupts disabled.
+ */
+static void smc_poll_controller(struct net_device *dev)
+{
+	disable_irq(dev->irq);
+	smc_interrupt(dev->irq, dev, NULL);
+	enable_irq(dev->irq);
+}
+#endif
+
 /* Our watchdog timed out. Called by the networking layer */
 static void smc_timeout(struct net_device *dev)
 {

@@ -1912,6 +1930,9 @@
 	dev->get_stats = smc_query_statistics;
 	dev->set_multicast_list = smc_set_multicast_list;
 	dev->ethtool_ops = &smc_ethtool_ops;
+#ifdef CONFIG_NET_POLL_CONTROLLER
+	dev->poll_controller = smc_poll_controller;
+#endif
 
 	tasklet_init(&lp->tx_task, smc_hardware_send_pkt, (unsigned long)dev);
 	INIT_WORK(&lp->phy_configure, smc_phy_configure, dev);