I've been having a recurring problem ever since the 2.2 kernel days between
smbfs and autofs.
I'm currently running 2.4.19-pre6-vm33 on this 2x664Mhz P3 machine, but I've
also had the problem in the previous UP machine.
I'm not sure what information will be helpful in debugging this probem.
Would sysrq+t run through ksymoops be helpful?
I also have this in my kernel log:
May 26 06:33:16 fileserver kernel: Uhhuh. NMI received. Dazed and confused, but trying to continue
May 26 06:33:16 fileserver kernel: You probably have a hardware problem with your RAM chips
I did a quick search and it looks like this might be a memory parity error.
Right now this system runs the scripts that triggers the condition, but I
can do tests on a different machine.
Is there anyone interested in this problem?
Oh, I'm running debian and the samba packages are:
ii samba 2.2.3a-6 A LanManager like file and printer server for Unix.
ii smbfs 2.2.3a-6 mount and umount commands for the smbfs (for kernels >= than
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/