mips linux problems
From: Jason (taolu79_at_yahoo.com.cn)
Date: 09/28/03
- Next message: Kasper Dupont: "Re: SIGCHLD, SIG_IGN and zombie processes"
- Previous message: Grzegorz Jablonski: "Re: SIGCHLD, SIG_IGN and zombie processes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Sep 2003 15:54:15 +0800
Dear all,
Recently I am working with a mips box. and met some problems. and the letter
will
be a little long, please do me the favor to read through it and give me some
issues.
1.
The enviroment is:
# cat cpuinfo
system type : WavePlus WP3200
processor : 0
cpu model : R3000 V0.3
BogoMIPS : 99.32
wait instruction : yes
microsecond timers : no
tlb_entries : 64
extra interrupt vector : no
hardware watchpoint : no
VCED exceptions : not available
VCEI exceptions : not available
ll emulations : 0
sc emulations : 0
# uname -a
Linux (none) 2.4.18-mips #24 Tue Sep 23 13:01:48 CST 2003 mips unknown
# free
total used free shared buffers
Mem: 62244 8712 53532 0 96
Swap: 0 0 0
Total: 62244 8712 53532
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/rd/0 3963 3196 767 81% /
#
2.
The CPU support two SDRAM BANKs, and every SDRAM BANK may support
64MB RAM. the address is
SDRAM BANK1 0x0000-0000 ~ 0x03FF-FFFF
SDRAM BANK2 0x0400-0000 ~ 0x07FF-FFFF
and in my box,
32M 0x0000-0000 ~ 0x01FF-FFFF first 32MB is a continous on
16M 0x0300-0000 ~ 0x03FF-FFFF third 16MB
16M 0x0500-0000 ~ 0x05FF-FFFF fourth 16MB
total is 64MB
I configure the LInux kernel to support the 64MB ram, in the prom.c
add_memory_region(0x00000000, 0x020000000, BASE_MEM_RAM);
add_memory_region(0x03000000, 0x010000000, BASE_MEM_RAM);
add_memory_region(0x05000000, 0x010000000, BASE_MEM_RAM);
Then, configure the Linux Kernel to support 16M RAMDISK.
3.
# mke2fs /dev/ram1 16000;mke2fs /dev/ram2 16000;tune2fs /dev/ram1 -c
10240;tune2
fs /dev/ram2 -c 10240
mke2fs 1.25 (20-Sep-2001)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
4000 inodes, 16000 blocks
800 blocks (5.00%) reserved for the super user
First data block=1
2 block groups
8192 blocks per group, 8192 fragments per group
2000 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs 1.25 (20-Sep-2001)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
4000 inodes, 16000 blocks
800 blocks (5.00%) reserved for the super user
First data block=1
2 block groups
8192 blocks per group, 8192 fragments per group
2000 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.25 (20-Sep-2001)
Setting maximal mount count to 10240
tune2fs 1.25 (20-Sep-2001)
Setting maximal mount count to 10240
#
4.
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/rd/0 3963 3198 765 81% /
/dev/ram1 15491 13 14678 0% /var/tmp/ram1
/dev/ram2 15491 13 14678 0% /var/tmp/ram2
# dd if=/dev/zero of=/tmp/ram1/tt bs=1k count=10000
10000+0 records in
10000+0 records out
# dd if=/dev/zero of=/tmp/ram2/tt bs=1k count=10000
10000+0 records in
10000+0 records out
# cd /tmp/ram1/
# ls
lost+found tt
# Unable to handle kernel paging request at virtual address 00000000, epc ==
000
00000, ra == 00000000
Oops in fault.c:do_page_fault, line 204:
$0 : 00000000 1000fc00 00000000 1000fc01 810ba8f0 00000000 810ba8f0 00000001
$8 : 00000001 00000000 00000000 00000000 00000000 00000000 00000014 00000000
$16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
$24: 00000000 2ab30700 811be000 811bfe38 00000000 00000000
Hi : 00000000
Lo : 00000ce0
epc : 00000000 Not tainted
Status: 1000fc04
Cause : 10000008
Process kupdated (pid: 6, stackpage=811be000)
Stack: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
00000000 ...
Call Trace:
Code:
anyone salted please give me some issues on it. and at the same time I will
try to use kgdb to
debug it.
Any reply will be great appriciated.
Best Regards,
Jason
- Next message: Kasper Dupont: "Re: SIGCHLD, SIG_IGN and zombie processes"
- Previous message: Grzegorz Jablonski: "Re: SIGCHLD, SIG_IGN and zombie processes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
