[lkml]   [2003]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Linux-NTFS-Dev] ntfs OOPS (2.5.63)
> On Thu, 6 Mar 2003, Szakacsits Szabolcs wrote:
>> On Wed, 5 Mar 2003, Randy.Dunlap wrote:
>> > > Could you try to turn on debugging in the NTFS driver (compile option
>> in the menus), then once ntfs module is loaded (or otherwise anytime)
>> as root do:
>> > >
>> > > echo -1 > /proc/sys/fs/ntfs-debug

Did that, got lots of output, but the oops isn't reproducible
AFAIK, so I haven't collected all of that debug output.

>> > > Then mount and to the directory changes. Assuming that you get the bug
>> again could you send me the captured kernel log output? (Note there
>> will be massive amounts of output.)
>> > >
>> > > The code looks ok and I can't reproduce here so it would be helpful to
>> see if there are any oddities on your partition. Just to make sure it
>> is not the compiler, could you do a "make fs/ntfs/inode.S" and send me
>> that as well?

The .config file, gcc -v output, and /proc/cpuinfo are added as
attachments at

objdump disassembly and make fs/ntfs/inode.s files are also
attached there.

I tried to decode the disassembly, got lots of it done,
but I bogged down on something that may be outside of the
NTFS realm. I have ALL kernel hacking options enabled
(=y), and it's a bit hairy (for me) to decode all of the
extra/added code, and this may be where the oops is
happening. Dunno really, just wanted to warn you.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.097 / U:3.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site