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

["\"임근식\"" <invain@naver.com>]

[-- Attachment #1: Type: Text/Plain, Size: 9777 bytes --]


Thank you for offering you patch file. But, I tried thus patch work already for solve this problem.
In the long run , Although I adjusted patch to smc91x.c file, booting still is failed with nfs RFS.
I am poor knowledge about device dirver. If possible, I need technique of veteran engineer.

P.S: When i send packet using nmap tool from host(192.168.0.2) to target(192.168.0.10) ,
Below message appeared on minicom console.
-------------------------------------------------------
eth0: bad memory timings: rxlen 0 status 507f
eth0: bad memory timings: rxlen 0 status 407f
-------------------------------------------------------

and, When I used ping command from host to target.
-------------------------------------------------------
host#> ping target.ip.address [enter]
64 bytes from 192.168.0.10: icmp_seq=11 ttl=64 time=8.23 ms
64 bytes from 192.168.0.10: icmp_seq=12 ttl=64 time=8.11 ms
64 bytes from 192.168.0.10: icmp_seq=13 ttl=64 time=7.89 ms
64 bytes from 192.168.0.10: icmp_seq=14 ttl=64 time=7.77 ms
64 bytes from 192.168.0.10: icmp_seq=15 ttl=64 time=7.38 ms
......... below omission ..............
-------------------------------------------------------


* reference to below booting message ( target status )
-------------------------------------------------------
Uncompressing Linux.............................................................Linux version 2.6.10-omap1 (root@geunsik) (gcc version 3.4.3 (MontaVista 3.4.3-6CPU: ARM926EJ-Sid(wt) [41069263] revision 3 (ARMv5TEJ)
CPU: D VIVT write-back cache
CPU: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Machine: TI-OSK
Warning: bad configuration page, trying to continue
Memory policy: ECC disabled, Data cache writethrough
OMAP_DIE_ID_0: 0xc159110d
OMAP_DIE_ID_1: 0x9805907d DIE_REV: 2
OMAP_PRODUCTION_ID_0: 0x00aaaafc
OMAP_PRODUCTION_ID_1: 0x00016cbe JTAG_ID: 0x6cbe
OMAP32_ID_0: 0x03320500
OMAP32_ID_1: 0x2b65f02f
JTAG_ID: 0xb65f DIE_REV: 2
OMAP162123 revision 2 handled as 16xx id: 9805907dc159110d
Built 1 zonelists
Kernel command line: mem=32M console=ttyS0,115200 nfsroot=192.168.0.2:/tftpbootwTotal of 128 interrupts in 4 interrupt banks
OMAP GPIO hardware version 1.0
PID hash table entries: 256 (order: 8, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB = 32MB total
Memory: 30208KB available (1711K code, 365K data, 108K init)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
OMAP DMA hardware version 1
DMA capabilities: 000c0000:00000000:01ff:003f:007f
Initializing OMAP McBSP system
MUX: initialized AA9_USB0_VP
MUX: initialized R9_USB0_VM
USB: hmc 16, usb0 2 wires
OMAP I2C: Driver ver. 1.3
tps65010: version 20 Dec 2004
OMAP I2C WARNING: timeout waiting for bus ready
OMAP I2C WARNING: timeout waiting for bus ready
OMAP I2C WARNING: timeout waiting for bus ready
tps65010: no chip?
MUX: initialized N14_1610_UWIRE_CS0
MUX: initialized N15_1610_UWIRE_CS1
OMAP OCPI interconnect driver loaded
Power Management for TI OMAP.
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
omapfb: configured for panel osk
OMAP LCD controller initialized.
MUX: initialized PWL
Console: switching to colour frame buffer device 30x40
OMAP framebuffer initialized vram=262144
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
elevator: using anticipatory as default io scheduler
nbd: registered device at major 43
smc91x: IOADDR c2852000 doesn't match configuration (300).
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
eth0: SMC91C94 (rev 9) at 0xc2852000 IRQ 160 [nowait]
eth0: Ethernet addr: c0:00:00:1b:62:9c
i2c /dev entries driver
omap_nor_cs3: Found 1 x16 devices at 0x0 in 16-bit bank
omap_nor_cs3: Found 1 x16 devices at 0x1000000 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 4 MTD partitions on "omap_nor_cs3":
0x00000000-0x00020000 : "bootloader"
0x00020000-0x00040000 : "params"
0x00040000-0x00240000 : "kernel"
0x00240000-0x02000000 : "filesystem"
mice: PS/2 mouse device common for all mice
OMAP Keypad Driver
MUX: initialized P20_1610_GPIO4
OMAP OSK touchscreen driver initialized
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
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: 108K
eth0: bad memory timings: rxlen 0 status 507f <---- (When i send packet using nmap tool from host to target,)
eth0: bad memory timings: rxlen 0 status 407f


* Contents of oops message for find reason.
----------------------------------------------
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 : [<c00ded34>] 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
Backtrace:
[<c012dc04>] (smc_interrupt+0x0/0x6d0) from [<c00232f8>] (__do_irq+0x4c/0x88)
[<c00232ac>] (__do_irq+0x0/0x88) from [<c0023454>] (do_edge_IRQ+0xb0/0x12c)
r8 = C01D584C r7 = C0299F40 r6 = C033EA20 r5 = 000000A0
r4 = C0210540
[<c00233a4>] (do_edge_IRQ+0x0/0x12c) from [<c002e7d8>] (gpio_irq_handler+0xa4/0xb8)
r7 = C0210570 r6 = 00000001 r5 = 00001E00 r4 = 000000A1
[<c002e734>] (gpio_irq_handler+0x0/0xb8) from [<c00235dc>] (asm_do_IRQ+0x50/0x150)
[<c002358c>] (asm_do_IRQ+0x0/0x150) from [<c00223e0>] (__irq_svc+0x20/0x80)
[<c0028cc8>] (do_translation_fault+0x0/0xac) from [<c0022718>] (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.


<-----Original Message----->
> From: "Hiroki Kaminaga" <kaminaga@sm.sony.co.jp>
> To: <invain@naver.com>
> Cc: <linux-omap-open-source@linux.omap.com>,
<kaminaga@sm.sony.co.jp>
> Sent: 2006-01-19 21:36
> Subject: Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS)

Hi,

> 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.
--

<-----Original Message----->
> From: "Hiroki Kaminaga" <kaminaga@sm.sony.co.jp>
> To: <invain@naver.com>
> Cc: <linux-omap-open-source@linux.omap.com>,
 <kaminaga@sm.sony.co.jp>
> Sent: 2006-01-19 21:36
> Subject: Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS)

Hi,

> 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.
--

------------------------------------------------------------------------
네이버 :: 똑! 소리나게 바뀐 네이버 메일을 만나보세요.
http://mail.naver.com/

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]