Dear User Group:
More information about the boot problem.
I've localized the problem to check_mnt()
where it is called by do_add_mount(). (i.e.
Both are in linux-2.4.x/fs/namespace.c) At that
point it determines the passed mount point is
not root and returns -22 = -EINVAL.
do_add_mount() is called with the following arguments:
1) nd - This is obtained from a call to path_lookup() on
"/dev/root" with the flags LOOKUP_FOLLOW and LOOKUP_POSITIVE.
2) type = "ext2"
3) flags = 0x8001 (i.e. MS_VERBOSE | MS_RDONLY)
4) mnt_flags = 0
5) name = "/dev/root"
6) page = 0
The whole problem originates when mount_block_root("/dev/root", 0x8001)
eventually calls sys_mount() with the following arguments:
(i.e. In linux-2.4.x/init/do_mounts.c)
1) dev_name = "/dev/root"
2) dir_page = "/root"
3) type_page = "/ext2"
4) flags = 0x8001 (i.e. MS_VERBOSE | MS_RDONLY)
5) data_page = 0
At that point mount_block_root() goes into an infinite loop
because sys_mount() returns -22 = -EINVAL.
Does anybody have insight about this problem ?
Best Regards,
Paul R.
****************** PREVIOUS MESSAGE ************
Hi Gavin:
Some more information about the problem.
The next thing that executes is mount_block_root()--from
linux-2.4.x/init/do_mounts.c and it generates the
following message:
"VFS: Mounted root (romfs only) read only."
It then calls do_mount() for each FS that needs to be mounted.
I think ext2 systems are mounted first.
The rest of the diagnostic messages you commented
on originate as follows:
The "Bad boy: Colfire Timer (at 0x00022f50)
called request_irq without a dev_id!" is the only
one that really worries me. It is generated in
request_irq() in linux-2.4.x/arch/m68knommu/platform/5307/ints.c
when the request is made for a Coldfire timer
I assume exists on the 5307 version but not the
5249 version of the Coldfire CPU. Is this
a problem ?
The messages prefixed by kmem_create: come from the
kmem_create() routine in linux-2.4.x/mm and are just
diagnostics.
"Dentry cache hash table entries : 1024 (order: 1, 8192 bytes)"
comes from dcache_init() in linux-2.4.x/fs/dcache.c and looks
to be an informative diagnostic.
Inode cache hash table entries: 512 (order: 0, 4096 bytes)" comes
from inode_init() in linux-2.4.x/fs/inode.c and also appears diagnostic.
************ PREVIOUS MESSAGE ********
Quoth Paul Romero [paulr at rcom-software.com]:
> The boot on my M5249C3 w/ 2 MB of Flash just began
> hanging today. The last line it prints is as follows:
>
> "NET4: Unix domaine sockets 1.0/SMP for Linux NET 4.0."
>
> I certainly didn't change anything in my system setup and
> think this may be indicative of a hardware problem.
> The rest of the boot log follows and any ideas
> would be appreciated.
[...]
> Kernel command line: mtdparts=physmap:1280k(flash1),768k(flash2)
> Bad boy: ColdFire Timer (at 0x00022f50) called request_irq
> without a dev_id! Calibrating delay loop... 92.56 BogoMIPS
There's an odd error right there...
> Memory available: 4952k/8192k RAM, 0k/0k ROM (918k kernel code, 233k
> data) kmem_create: Forcing size word alignment - vm_area_struct
> kmem_create: Forcing size word alignment - mm_struct
> kmem_create: Forcing size word alignment - filp
> Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
> Inode cache hash table entries: 512 (order: 0, 4096 bytes)
> kmem_create: Forcing size word alignment - inode_cache
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> kmem_create: Forcing size word alignment - bdev_cache
> kmem_create: Forcing size word alignment - cdev_cache
> kmem_create: Forcing size word alignment - kiobuf
All of those kmem_create errors seem odd to me too (I don't get them,
anyway, but then again, I use 2.6). Maybe something has changed in your
malloc or in your byte packing settings?
> TCP: Hash tables configured (established 512 bind 512)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> ΓΈ
Maybe something is changing your serial port baud rate at this point, or
messing with the registers/pins that control your serial port (just a
wild guess)? What's the next line in a normal run? -- that might give
you some clues.
--
Paul Romero
--
Paul Romero
RCOM Communications Software
Phone/Fax: (510)339-2628
E-Mail: [EMAIL PROTECTED]
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
