Fw: [iPAQ] Problem with mounting root filesystem through NFS

I posted this question to the ipaq list bef. Probably someone here might
know the answer.

----- Original Message -----
From: "Wong Yee Peng" <wyeepeng_at_dso.org.sg>
To: <ipaq_at_handhelds.org>
Sent: Tuesday, August 28, 2001 2:29 PM
Subject: Re: [iPAQ] Problem with mounting root filesystem through NFS

> Hi,
> I manage to find the solution to the problem of the NFS root. Somehow,
> the "Root FS on NFS" is disabled or reset by probably other setting in the
> make xconfig process even though previously I set it to on. That's why the
> kernel couldn't detect the /dev/nfs device. After fixing it, the problem
> does not appear anymore. However, a new problem appeared. Below is the
> kernel output on the console (edit to show only some important messages.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Linux version 2.4.7-rmk3-np1-devfs (root_at_ipaq1) (......)
> .....
> Kernel command line: noinitrd console=ttySA0,115200 root=/dev/nfs
> nfsroot=192.190.205.99:/tftpboot/192.190.205.3
> ip=192.190.205.3:192.190.20pWarning: uninitialized Real Time Clock
> ......
> init_module successful init major= 0 irq=48
> h3600_backpaq_fpga.c: registering char device 253
> h3600_backpaq_fpga.c: registered backpaq callback=c00cc868
> SA1100 Real Time Clock driver v1.00
> block: queued sectors max/low 9181kB/3060kB, 64 slots per queue
> Unable to handle kernel NULL pointer dereference at virtual address
00000390
> pgd = c0004000
> *pgd = 00000000, *pmd = 00000000
> Internal error: Oops: ffffffff
> CPU: 0
> pc : [<c00d658c>] lr : [<c003fae8>]
> sp : c0237efc ip : c0239560 fp : c0237f1c
> r10: 00000000 r9 : 6901b118 r8 : c01a821c
> r7 : 00000000 r6 : c0237f20 r5 : 00000390 r4 : 00000390
> r3 : 00000001 r2 : 0000001d r1 : 0000001c r0 : 000003e8
> Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
> Control: C000717F Table: C000717F DAC: 0000001D
> Process swapper (pid: 1, stackpage=c0237000)
> Stack:
> c0237ee0: c003fae8 c00d658c 60000013 ffffffff
> c0237f40
> c0237f00: c01a7f98 00000000 c0237f20 00000000 c0237f4c c0237f20 c0011b00
> c00d6544
> c0237f20: c0102ebc c01664d4 c0017ac0 c01a7f98 00000000 c01b7e3c c01a9dd8
> 0000001f
> c0237f40: c0237f68 c0237f50 c0011364 c0011a78 c01a7f98 00000000 c01a8200
> c0237f80
> c0237f60: c0237f6c c0011438 c0011318 c01a7f98 c01a80fc c0237fa4 c0237f84
> c0013b18
> c0237f80: c0011390 c001b384 c001b3d8 c01ad4f4 c01ad4dc c019ec80 c0237fb4
> c0237fa8
> c0237fa0: c0011300 c0013a50 c0237fcc c0237fb8 c00088c0 c00112ec 00001000
> c01d9eb8
> c0237fc0: c0237fdc c0237fd0 c0008904 c00088b0 c0237ffc c0237fe0 c001c064
> c00088e4
> c0237fe0: 00001000 c01d9eb8 c01ad4f4 c01ad4dc 00000000 c0238000 c001da38
> c001c060
> Backtrace:
> Function entered at [<c00d6538>] from [<c0011b00>]
> r7 = 00000000 r6 = C0237F20 r5 = 00000000 r4 = C01A7F98
> Function entered at [<c0011a6c>] from [<c0011364>]
> Function entered at [<c001130c>] from [<c0011438>]
> r6 = C01A8200 r5 = 00000000 r4 = C01A7F98
> Function entered at [<c0011384>] from [<c0013b18>]
> r5 = C01A80FC r4 = C01A7F98
> Function entered at [<c0013a44>] from [<c0011300>]
> r8 = C019EC80 r7 = C01AD4DC r6 = C01AD4F4 r5 = C001B3D8
> r4 = C001B384
> Function entered at [<c00112e0>] from [<c00088c0>]
> Function entered at [<c00088a4>] from [<c0008904>]
> r5 = C01D9EB8 r4 = 00001000
> Function entered at [<c00088d8>] from [<c001c064>]
> Function entered at [<c001c054>] from [<c001da38>]
> r7 = C01AD4DC r6 = C01AD4F4 r5 = C01D9EB8 r4 = 00001000
> Code: e1a04805 e1a04824 (e1c430b0) eb023b19 e59fc078
> Kernel panic: Attempted to kill init!
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> I looked at the source codes and found that the message right before the
> error:
> "block: queued sectors max/low 9181kB/3060kB, 64 slots per queue"
> came from linux/drivers/block/ll_rw_blk.c under the function called
> blk_dev_init(void) just bef a series of #ifdef. They looked like functions
> to initialise bootable devices.
>
> To me, it seems that the kernel failed in trying to initialise some block
> device (the nfs root fs???).
> However, I had totally turned off all block devices in the make xconfig
> under "block devices".
>
> Does anyone knows what is wrong?
>
> Regards
> Yee Peng
>
Received on Tue Aug 28 2001 - 17:49:42 EDT