> G> My previously reported flood of oops' after I removed a single Pentium from
> G> my Tyan Tomcat IV go away if I use 'nosmp' on the command line. Something
> G> isn't quite happy in the SMP code if it only gets one processor now...
>
> G> mount("/dev/hdc", "/mnt/cdrom", "iso9660", 0xc0ed0000, 0x80541f0) = -1
> G> ENOSYS (Function not implemented)
> G> mount("/dev/hdc", "/mnt/cdrom", "iso9660", 0xc0ed0000, 0x80541f0) = -1
> G> ENOSYS (Function not implemented)
> G> mount("/dev/hdc", "/mnt/cdrom", "iso9660", 0xc0ed0000, 0x80541f0) = -1
> G> ENOTBLK (Block device required)
>
> This looks _very similar_ to the amd mounting problems that happen since 114.
> I got ENOSYS errors on mount syscall too. UP kernel.
> The scheduler was changed and some mount stuff broke.
> As a temporary workaround you might try to back out the sched.c changes in
> 2.1.114 (2 first hunks of sched.c changes).
>
It even gets stanger. I get ENOSYS from open() two times, if opening
/dev/vtx (saa module), the third time ENODEV - very strange.
Richard.
-- Richard Guenther <richard.guenther@student.uni-tuebingen.de> PGP: 2E829319 - 2F 83 FC 93 E9 E4 19 E2 93 7A 32 42 45 37 23 57 WWW: http://www.anatom.uni-tuebingen.de/~richi/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html