schedule_timeout: wrong timeout value ffffffb4 from c012bb59
I've seen other people mention similar errors, but when it happens to me,
1) it doesn't seem to affect system performance at all. If I simply set
the log level (w/ sysreq) to 0 on the console, and have syslog not log
kernel messages to the console, I would never notice the problem.
2) It has nothing to do with NFS. I have NFS compiled as a module, but
I've not actually loaded the module since booting the machine with 2.1.128
this morning. The only modules that have been loaded are sound.
Specifically, opl3sa2.
[113] isaac:~ % uname -a
Linux isaac 2.1.128 #5 Fri Nov 13 09:16:22 EST 1998 i586 unknown
Pentium MMX 233. One thing I've noticed (that may or may not be related)
is that the BogoMIPS reported for this machine are in the 400's, which is,
much higher than a P233 should be getting, right?
Pretty boring kernel config. Lots of filesystems (NFS, NTFS, Mac, VFAT,
Minix, ISOFS) compiled as modules. Modular opl3sa2 sound. Standard stuff,
mostly. .config available if anyone wants it.
One other thing. The schedule_timeout messages seem to come and go.
Specificially, it started at Nov 13 21:20:28 (after about 13 hours of
uptime). It hasn't stopped yet, but it very well might have by tomorrow
morning. Under 2.1.127, it would stop after a few hours (once from
~10am-~1pm, once from 1am til I rebooted, and a few other things like
that). If anyone *really* wants, I have a ~5M log of all the kernel
messages since this started happening.
Any ideas? This problem definetly started with 2.1.127
Mike Sackton
-- "I always try to make sure that I never spell the word typo wrong, because I think that would look really silly." -- Laura Sackton
- 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.tux.org/lkml/