[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: a bug in ext3 code for 2.4.7



Hi,

On Wed, Oct 24, 2001 at 11:17:55PM +0000, Nikolai Vladychevski wrote:

> ok, i didnt put it complete because I had to transcript from the monitr, but 
> here it goes: 
 
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c0127304>]
> EFLAGS: 00010082
> eax: 0000001b  ebx: cf68e000  ecx: 00000001  edx: c025fe08
> esi: 00000000  edi: c141fd40  ebp: cf6c7240  esp: ce355ed0
> ds: 018  es: 0018  ss: 0018
> Process mount (pid: 41, stackpage=ce355000)
> Stack:
> c021fb8f c021fc2b 0000048d cf68e005 cf6c7240 00008043 cf68e005 c012793f
> c141fd40 cf6c7240 cf68e005 cf5af1c0 00000001 00000246 cc26b440 ffffffd8
> 00008043 ce355f7c c013a5d1 c141fd40 cf68e005 ce355f84 cc26b440 00000001
> Call Trace: [<c012793f>] [<c013a5d1>] [<c012793f>] [<c012eaa4>] [<c012ed93>] 
> [<c0106f77>]
> Code: 0f 0b 83 c4 0c 8b 5d 14 83 fb ff 74 35 eb 0d 90 90 90 90 90 

Code: 0f 0b is a BUG() assertion.  Can you run this trace through
ksymoops to make it useful for debugging?  Is it reproducible for you?

Thanks,
 Stephen





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]