I used to get these on my gateway laptop.  I got them whenever the laptp
would spin down the disk, but not go into shutdown.  On my system, when I
started getting these, the driver would never recover.  I hacked the wd
driver to recover by re-initing the controller, but it was not a pretty
hack.  I can send you the code if you like.  But I finally solved the
problem by upgrading the BIOS.  It's flash downloadable and I got the new
release off their ftp site.  See if your vendor has a BIOS upgrade.

Dave

> Hello,
> 
> Had these in my syslog last night:
> 
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> err
>       or 0
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 2@wd0:2112838
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> err
>       or 0
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 2@wd0:2112838
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> err
>       or 0
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 1@wd0:2112838
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> err
>       or 0
> Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 1@wd0:2112838
> 
> Are these dangerous?  What should I do about them?  Is my disk dying?  Has
> some data been lost?  Am I just being a paranoid? :-)
> 
> Thanks,
> 
>   -jm
> 
> -- 
> 
>                      ---> http://www.jmp.fi/~jmarin/ <---