Aug 21 16:18:09 intranet kernel: _isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF(8, 8192)_isofs_bmap: block>= EOF
(8, 8192)_isofs_bmap: block>= EOF(4, 4096)_isofs_bmap: block>= EOF(4, 4096)_isofs_bmap: block>= EOF(4, 4096)_isofs_bmap: block>= EOF(4, 4096)_isofs_bmap: block>= EOF(4, 4096) kernel code, 384k reserved, 2084k data)
This was on a 2.0.35.pre2 machine.
It seemed to have somehow looped the machine oddly, because I have
several entries like these in the last few days:
Aug 21 16:18:09 intranet kernel: Swansea University Computer Society NET3.035 for Linux 2.0
Aug 21 16:18:09 intranet kernel: NET3: Unix domain sockets 0.13 for Linux NET3.035.
Aug 21 16:18:09 intranet kernel: Swansea University Computer Society TCP/IP for NET3.034
Aug 21 16:18:09 intranet kernel: IP Protocols: ICMP, UDP, TCP
Aug 21 16:18:09 intranet kernel: VFS: Diskquotas version dquot_5.6.0 initialized
Aug 21 16:18:09 intranet kernel:
Aug 21 16:18:09 intranet kernel: Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Aug 21 16:18:09 intranet kernel: Checking 'hlt' instruction... Ok.
Aug 21 16:18:09 intranet kernel: Intel Pentium with F0 0F bug - workaround enabled.
Aug 21 16:18:09 intranet kernel: alias mapping IDT readonly ... ... done
However, machine uptime is 29 days.
Then again the klogd binary looks ancient, which is prob the cause.
Do those iso entries mean there is a very flaky CDrom in the drive?
Paul
-
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