Re: mips64 problems with linux-xfs

[Roman Vasylyev <romis@xxxxxxxxxxxxx>]

Christoph Hellwig wrote:
> On Fri, Jun 04, 2004 at 04:19:24PM +0400, Roman Vasylyev wrote:
>
> > Hello,
> >
> > I'm need to test xfs filesystem on 
> > mips64(broadcom-bcm91250_m64-mips64_fp_be) platform using ltp-tests and 
> > find problems.
> > dd if=/dev/zero of=xfs.img bs=1k count=50k
>
>
> don't you need a mkfs.xfs here?
>
>
> > mount -o loop xfs.img /mnt
> > cp -r ltp-fs /mnt
> > cd /mnt/ltp-fs
> > ./runalltests.sh
> >
> > after that in different random places of tests i receve this message and 
> > system halts:
> >
> > do_cpu invoked from kernel context! in traps.c::do_cpu, line 764:
> > Cpu 0
> > $0      : 0000000000000000 ffffffff803af850 a800000000376980 
> > ffffffff803af850
> > $4      : a80000000e5b8000 a80000000fccc000 0000000000000007 
> > ffffffff8037b000
> > $8      : 0000000000000000 0000000000000000 000000000000008b 
> > 0000000000000000
> > $12     : 0000000004001ff3 ffffffffdfffffff ffffffff8003fe60 
> > 0000000000000000
> > $16     : 0000000000000000 a800000000376980 000000001000b250 
> > a80000000fccc000
>
>
> without feeding the oops through ksymoops it's compeletely useless.

Thanks,
I'm just forget to point mkfs.xfs:
mkfs.xfs -f xfs.img




ksymoops 2.4.6 on i686 2.4.20-8.  Options used
    -v /home/savl/workdir/mips64_humb/linux/vmlinux (specified)
    -K (default)
    -L (default)
    -O (default)
    -m /home/savl/workdir/mips64_humb/linux/System.map (specified)

Error (pclose_local): read_nm_symbols pclose failed 0x100
Warning (read_vmlinux): no kernel symbols in vmlinux, is 
/home/savl/workdir/mips64_humb/linux/vmlinux a valid vmlinux file?
Cpu 0
$0      : 0000000000000000 ffffffff803f2010 a80000000c12ac60 
ffffffff803f2010
$4      : a80000000b1f8000 ffffffff802f4000 0000000000000001 
0000000000000001
$8      : 0000000000000000 0000000000000002 0000000000000001 
0000000000001320
$12     : 0000000004001ff3 ffffffffdfffffff ffffffff8003fe60 
35b6458b00000dd8
$16     : a80000000c12ac60 ffffffff802f4000 a80000000b1f8000 
ffffffff80310020
$20     : a8000000005bf208 000000000000039c a80000000b1fbb58 
a80000000b1fbb50
$24     : 0000000000000000 000000002acaa26c
$28     : a80000000b1f8000 a80000000b1fba60 a80000000b1fba60 
ffffffff801258e0
epc     : ffffffff801064a8    Not tainted
Using defaults from ksymoops -t elf32-little -a unknown
Process growfiles (pid: 484, stackpage=a80000000b1f8000)
Stack: 00000000000001e4 ffffffff802f4000 0000000000000002 c00000000007c0c0
      a8000000005bf200 0000000000000000 a80000000b1f8000 0000000000000002
      a80000000b1fbb5c ffffffff8010727c 00000000005bf200 a80000000b1f8000
      a8000000005bf210 a8000000005bf210 a8000000005bf200 a80000000c4123c0
      0000000000000004 000000000000039c a80000000c6d3e38 c000000000055af0
      0000000000000e20 0000000000000e2c a80000000c858000 000000000000039c
      a80000000c6d3e38 000000000000000a 0000000000000001 a8000000005bf200
      a80000000b1fbc10 c000000000054af0 a80000000c4124c0 0000000100007e00
      a8000000005a1800 0000000d0002897c a80000000bbb9608 0000000000000000
      0000000000000000 0000000100000e20 0000000000000000 0000000000000005
      000000000000000d ...
Call Trace: [<c00000000007c0c0>] [<ffffffff8010727c>] [<c000000000055af0>]
           [<c000000000054af0>] [<c0000000000530e0>] [<c000000000065a2c>]
           [<c00000000004c1c4>] [<c00000000004edf8>] [<c000000000065048>]
           [<c0000000000724f4>] [<c000000000086700>] [<c000000000086c94>]
           [<ffffffff8018009c>] [<ffffffff8017ff70>] [<ffffffff80180274>]
           [<ffffffff801802bc>] [<ffffffff8011a384>] [<ffffffff80180188>]
Code: 018d6024  fc8c3fd0  000c7140 <05c10011> f4800878  f4810880 
f4830890  f48508a0  f48708b0
Error (Oops_bfd_perror): scan_arch for specified architecture File in 
wrong format
Sorry, looks like your binutils cannot handle the specified architecture


>>$1; ffffffff803f2010 <trace_callback_table+8/170>
>>$3; ffffffff803f2010 <trace_callback_table+8/170>
>>$5; ffffffff802f4000 <init_task_union+0/4000>
>>$17; ffffffff802f4000 <init_task_union+0/4000>
>>$19; ffffffff80310020 <runqueues+0/4c800>
>>$31; ffffffff801258e0 <schedule+308/5a0>

>>???; ffffffff801064a8 <resume+68/164>   <=====

Trace; c00000000007c0c0 Before first symbol
Trace; ffffffff8010727c <__down+7c/b8>
Trace; c000000000055af0 Before first symbol
Trace; c000000000054af0 Before first symbol
Trace; c0000000000530e0 Before first symbol
Trace; c000000000065a2c Before first symbol
Trace; c00000000004c1c4 Before first symbol
Trace; c00000000004edf8 Before first symbol
Trace; c000000000065048 Before first symbol
Trace; c0000000000724f4 Before first symbol
Trace; c000000000086700 Before first symbol
Trace; c000000000086c94 Before first symbol
Trace; ffffffff8018009c <vfs_unlink+21c/308>
Trace; ffffffff8017ff70 <vfs_unlink+f0/308>
Trace; ffffffff80180274 <sys_unlink+ec/1a8>
Trace; ffffffff801802bc <sys_unlink+134/1a8>
Trace; ffffffff8011a384 <handle_sysn32+84/a4>
Trace; ffffffff80180188 <sys_unlink+0/1a8>


1 warning and 2 errors issued.  Results may not be reliable.