>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).
I had the same problem with 2.1.110 anyway. Something in the dcache
(lookup_dentry) oops's on the request_module call so I can get ENOSYS on
basically anything modularized. klogd trying to load Unix sockets causes a
flood of messages until I hit ALT+SysRQ+E.
Something broken in the 2.1.x SMP (2.0.x SMP works fine) single processor
area?
-George
-
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