On Wed, 24 Nov 2004 18:12:07 -0800 Scott Leighton wrote:

I'm seeing those logged occasionally too, usually in conjunction with kernel: hda: DMA interrupt recovery. Not sure what it all means but there is no noticeable impact on the system.

Have you needed to reboot at any time? Booting up failed for me once because of this. I haven't dared to try it again. - Richard -- Richard Kimber http://www.psr.keele.ac.uk/

On Wed, 24 Nov 2004 18:12:07 -0800 Scott Leighton wrote:

On Wednesday 24 November 2004 1:14 pm, rkimber@ntlworld.com wrote:

...

Yesterday logcheck sent me a message about lost interrupts "kernel: hda: lost interrupt" yet all seemed to be working well

I'm seeing those logged occasionally too, usually in conjunction with kernel: hda: DMA interrupt recovery. Not sure what it all means but there is no noticeable impact on the system.

Another point I meant to emphasise is that these errors are recent. In the preceding six months they had not occurred at all. This suggests some change in either harware or, more likely, software. My guess is that there is a bug in some recently produced update. - Richard -- Richard Kimber http://www.psr.keele.ac.uk/

Andi Kleen wrote:

...

Another point I meant to emphasise is that these errors are recent. In the preceding six months they had not occurred at all. This suggests some change in either harware or, more likely, software. My guess is that there is a bug in some recently produced update.

More likely hardware actually. Lost interrupt means that the hard disk didn't reply to a command in time. I would check the SMART statistics using smartctl and your cables.

-Andi

Hmm, i have testet it with a new SATA Harddisk an new cables. Same problem. Now i'm fighting against the console to get the kernel panic. friendly regards Andreas

On Thu, 25 Nov 2004 14:12:25 +0100 Andi Kleen wrote:

...

Another point I meant to emphasise is that these errors are recent. In the preceding six months they had not occurred at all. This suggests some change in either harware or, more likely, software. My guess is that there is a bug in some recently produced update.

More likely hardware actually. Lost interrupt means that the hard disk didn't reply to a command in time. I would check the SMART statistics using smartctl and your cables.

In fact, both disks passed the 'smartctl -a' test when run from the command line. The documentation on SMART doesn't always help in the interpretation of output, though. For example, for the disk that does NOT lose interrupts smartd has returned:- /dev/hde, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 249 to 250 If I've understood the man page correctly, this refers to to bit 3: SMART status check returned "DISK FAILING" Does such a small performance change really preceed a failure? And how could a failing disk pass the test (above)? Or does it regard anything that happens as 'pre-failure', which in a sense is logical but useless. The evidence so far does not support the idea that it's failing hardware, but we'll see how it develops. - Richard. -- Richard Kimber http://www.psr.keele.ac.uk/

On Fri, 26 Nov 2004 09:54:32 +1300 Volker Kuhlmann wrote:

...

In fact, both disks passed the 'smartctl -a' test

That's not a test, that's querying the disk's status.

Thanks. I was confused by the output, which said:- "SMART overall-health self-assessment test result: PASSED" But presumably this is reported because of some previous test

Run smartctl -s on -o on -S on once per disk. This enables smart and the disk's offline selftests. Any bad sectors found here show up as offline_uncorrectable. There was an excellent discusion on this on the smartmontool-users list over the last days. Thanks. I'll join the list. Run the short and long tests, -t short and -t long, waiting for each to finish. Then run smartctl -a and check for errors.

Both tests completed without error. Perhaps it's not a disk error but a controller or driver error (??) Would that show up in these tests? Thanks for your help. - Richard -- Richard Kimber http://www.psr.keele.ac.uk/

On Fri, 26 Nov 2004 12:04:01 +1300 Volker Kuhlmann wrote:

...

Perhaps it's not a disk error but a controller or driver error

More likely now.

I see I have in the logs:- kernel: hda: dma_timer_expiry: dma status ==0x24 kernel: PDC202XX: Primary channel reset. kernel: hda: DMA interrupt recovery kernel: hda: lost interrupt This is what I got repeats of on the occasion it would not boot up. Is there any mileage in upgrading to 9.2, which has a different kernel? I tried the Live DVD recently and that worked fine, though of course I didn't check for any error messages. - Richard -- Richard Kimber http://www.psr.keele.ac.uk/