<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ks_c_5601-1987">
<META content="MSHTML 6.00.2722.900" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>Dear Eric.<BR><BR>Thanks for your reply.<BR>Follows are
"ksymoops" decoding message.<BR><BR>Regards,<BR>malas<BR><BR>-----------------
ksymoops decoding message -----------------<BR><BR>c022ade5<BR>*pde =
00017063<BR>Oops: 0002<BR>CPU: 0<BR>EIP:
0010:[<c022ade5>] Not tainted<BR>EFLAGS:
00010246<BR>eax: 00000000 ebx: c58bc000 ecx:
00001000 edx: 00000000<BR>esi: 0806acb8 edi:
c58bc000 ebp: c109f2c8 esp: c1089f34<BR>ds:
0018 es: 0018 ss: 0018<BR>Process mkreiserfs (pid: 127,
stackpage=c1089000)<BR>Stack: 00000000 00001000 00001000 c124f054 00000000
00001000 00000000 00000000 <BR> 011de000
00000000 c109f220 00000000 00000001 0806acb8 c109f28c c109f220
<BR> c13bbaa0 c01290df c13bbaa0 0806acb8
00001000 c13bbac0 0806acb8 c13bbaa0 <BR>Call Trace:
[<c01290df>] [<c0133c65>] [<c0108d43>]<BR>Code: f3 aa 58 59 e9
9f df ef ff b8 f2 ff ff ff 30 d2 e9 b7 14 f0 <BR><BR><BR>>>EIP; c022ade5
<rwsem_down_failed_common+1175/2d00> <=====<BR><BR>Trace;
c01290df <generic_file_write+6f/b0><BR>Trace; c0133c65
<sys_write+85/100><BR>Trace; c0108d43
<system_call+33/40><BR><BR>Code; c022ade5
<rwsem_down_failed_common+1175/2d00><BR>00000000
<_EIP>:<BR>Code; c022ade5
<rwsem_down_failed_common+1175/2d00> <=====<BR>
0: f3
aa
repz stos %al,%es:(%edi) <=====<BR>Code; c022ade7
<rwsem_down_failed_common+1177/2d00><BR> 2:
58
pop %eax<BR>Code; c022ade8
<rwsem_down_failed_common+1178/2d00><BR> 3:
59
pop %ecx<BR>Code; c022ade9
<rwsem_down_failed_common+1179/2d00><BR> 4: e9 9f
df ef ff
jmp ffefdfa8 <_EIP+0xffefdfa8> c0128d8d
<do_generic_file_write+3fd<BR>/6e0><BR>Code; c022adee
<rwsem_down_failed_common+117e/2d00><BR> 9: b8 f2
ff ff ff
mov $0xfffffff2,%eax<BR>Code; c022adf3
<rwsem_down_failed_common+1183/2d00><BR> e: 30
d2
xor %dl,%dl<BR>Code; c022adf5
<rwsem_down_failed_common+1185/2d00><BR> 10: e9 b7 14 f0
00
jmp f014cc <_EIP+0xf014cc> c112c2b1
<END_OF_CODE+e4ce6d/????<BR><BR><BR>1 warning issued. Results may not
be reliable.<BR><BR>----- Original Message ----- <BR>From: "Eric W. Biederman"
<<A href="mailto:ebiederman@lnxi.com">ebiederman@lnxi.com</A>><BR>To:
"Munjun Kang" <<A
href="mailto:malas@pinetron.com">malas@pinetron.com</A>><BR>Cc: <<A
href="mailto:linuxbios@clustermatic.org">linuxbios@clustermatic.org</A>><BR>Sent:
Saturday, November 23, 2002 4:02 PM<BR>Subject: Re: occurs segmentation fault,
when I make a file system(ext3 or reiserfs)<BR><BR><BR>> "Munjun Kang" <<A
href="mailto:malas@pinetron.com">malas@pinetron.com</A>> writes:<BR>>
<BR>> > Dear linuxbios.<BR>> > <BR>> > Hello.<BR>> >
<BR>> > I've worked for development of Embedded linux project in my
corp.<BR>> > Following is decription of my projcet.<BR>> > CPU : VIA
C3 800Mhz (EBGA)<BR>> > Reference Board : VT6015<BR>> > Northbridge
: VT8606 (include S3 twister video core)<BR>> > Southbridge : VT8231
(include VIA rhine II LAN core)<BR>> > Bootbios : Linuxbios<BR>> >
OS : linux 2.4.19 ( ramdisk include glibc 2.3.1, busybox 0.60.5 and
tinylogin<BR>> > 1.2 )<BR>> > <BR>> > <BR>> > Now, It
works well except hard disk.<BR>> > I try to boot the kernel in two
way.<BR>> > First, it loads compressed kernel and ramdisk image via
network using tftp<BR>> > protocol.<BR>> > <BR>> > Second, it
loads elfImage, generated by 'mkelfImage' via network.<BR>> > All of them
work great. (It means that I can see the prompt '\ '.)<BR>> > <BR>>
> But, when I try to make a file system the harddisk, 'segmentation fault'
occurs.<BR>> > <BR>> > mke2fs and mkreiserfs have same
problem.<BR>> > <BR>> > For find out the cause, I try to make a file
system in various method.<BR>> > <BR>> > 1. Buildin Bios + Redhat
8.0 installed harddisk + test harddisk<BR>> > 2. Linuxbios + Redhat 8.0
installed harddisk + test harddisk<BR>> > 3. Linuxbios + Kernel(newly
compiled), own ramdisk + test harddisk<BR>> > <BR>> > After boot, I
try to make a file system on test harddisk.<BR>> > <BR>> > In case
1, It works well. Of course, it must be.<BR>> > In case 2 and 3, I meet
the segmentation fault.<BR>> > So, I think that this problem caused in
Linuxbios.<BR>> > <BR>> > Maybe, this problem caused by harddisk
initialization in linuxbios.<BR>> > But, there are no harddisk
initialization code in linuxbios.<BR>> > <BR>> > Cound you help
me?<BR>> > <BR>> > Thanks for reading.<BR>> > Regards,<BR>>
> malas<BR>> > <BR>> > PS. In addition, memtest86 v3.0 works well
without error.<BR>> <BR>> <BR>> My hunch is that it is a DMA problem,
or a similar hardware timing<BR>> problem. But you missed the most
important part of the kernel crash.<BR>> The symbolic output of ksymoops.
<BR>> <BR>> Without knowing where the code crashed it is hard to guess
where the<BR>> code crashed in the kernel, and thus have a good idea what the
real<BR>> problem is.<BR>> <BR>> Eric<BR>> <BR>>
_______________________________________________<BR>> Linuxbios mailing
list<BR>> <A
href="mailto:Linuxbios@clustermatic.org">Linuxbios@clustermatic.org</A><BR>>
<A
href="http://www.clustermatic.org/mailman/listinfo/linuxbios">http://www.clustermatic.org/mailman/listinfo/linuxbios</A><BR>>
<BR></BODY></HTML>