On Thu, 7 Mar 2002, Stephen C. Tweedie wrote:
> Hi,
>
> On Wed, Mar 06, 2002 at 06:01:14PM -0500, Tom Diehl wrote:
>
> > I suddenly found myself unable to access one of my file systems on a 7.2
> > machine with all of the updates except wa running the 2.4.9-21 kernel.
> > Looking in the logs the only thing I could see was the following:
> >
> > Mar 6 05:12:31 kanga syslogd 1.4.1: restart.
> > Mar 6 05:12:30 kanga kernel: [ext3:__insmod_ext3_S.bss_L1024+163840/116200300] __insmod_wd_S.bss_L1376
>
> Time going backwards??
Hummm, Interesting since this machine runs ntpd. I hadn't noticed. Any idea what would cause
this? Could it simply be that syslog had not gotten things written to disk
before syslog was restarted by logrotate? I do not know if this is possible or not.
FWIW this was the last entry before the log was rotated:
Mar 6 05:12:24 kanga automount[787]: attempting to mount entry /kanga/ftp
>
> > Mar 6 05:12:32 kanga kernel: Code: 0f 0b 59 58 eb 04 89 f6 89 c3 89 d8 5b c3 8d 76 00 8d bc 27
>
> "Code: 0f 0b" is a kernel BUG() trap, and it is always accompanied by
> a register dump; in ext3, it is also accompanied by a debug text line.
> Without that, I can't really tell you what was happening here, nor
> guess as to whether the root cause was a software or hardware problem.
Going back in the last log that got rotated I also found this:
Mar 6 04:36:10 kanga kernel: hdc: timeout waiting for DMA
Mar 6 04:36:10 kanga kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
Mar 6 04:36:10 kanga kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 6 04:36:10 kanga kernel: hdd: DMA disabled
Mar 6 04:36:10 kanga kernel: hdc: drive not ready for command
Mar 6 04:36:11 kanga kernel: ide1: reset: success
I realize that this is not what you asked for above. I am just wondering
if it provides any clues as to what is going on?
Is it likely the info you need is in the logs?? If so please tell me what
I am looking for and I will provide it. I looked and could not see any thing
like you described above. If it is not in the logs can you tell me where
to look and what to capture should it happen again. Things like this
really bother me. This machine has been extremely reliable. If some sort
of failure is near I would like to take appropriate action.
Thanks for your help,
--
......Tom CLUELESSNESS: There Are No Stupid Questions, But
tdiehl@rogueind.com There Are LOTS of Inquisitive Idiots. :-)
