Messages in this thread | | | Date | Sun, 9 Mar 2003 20:16:35 -0800 (PST) | Subject | Re: [Linux-NTFS-Dev] ntfs OOPS (2.5.63) | From | "Randy.Dunlap" <> |
| |
> > On Sat, 8 Mar 2003, Szakacsits Szabolcs wrote: >> >> EFLAGS: 00010282 >> eax: f6c0f080 ebx: 0000416d ecx: 00010282 edx: f6c0f0f8 >> esi: c040b078 edi: f6c0f0f8 ebp: f6dd1dbc esp: f6dd1db4 >> ds: 007b es: 007b ss: 0068 >> >> 3c0: b9 06 00 00 00 mov $0x6,%ecx >> ... not important ... >> 3cc: 89 d7 mov %edx,%edi >> 3ce: 89 55 f4 mov %edx,0xfffffff4(%ebp) 3d1: >> f3 a5 repz movsl %ds:(%esi),%es:(%edi) 3d3: 8d >> 50 78 lea 0x78(%eax),%edx >> 3d6: 8b 4d f4 mov 0xfffffff4(%ebp),%ecx 3d9: >> 89 51 18 mov %edx,0x18(%ecx) ## OOPS ## >> >> So %ecx should be %edi-24 = f6c0f0e0, instead it's EFLAGS. Oops [indeed]. >> %ebp value is correct, I checked. So it seems a hardware, strong radiation >> or an interrupt that didn't restore ecx. > > Actually the "interrupt" did a pushfl and overwrote 0xfffffff4(%ebp). esp = > 0xfffffff4(%ebp). For kernel code the compiler shouldn't have generated the > above code. > > Szaka
Hi Szaka,
Should I just close this bugzilla entry as invalid or not an NTFS problem? I don't mind doing that.
Thanks, ~Randy
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |