Subject: Re: Feb 12 wd.c: lost interrupt - ouch!
To: None <>
From: Holger Veit <>
List: current-users
Date: 02/22/1994 12:36:19
>     Simon> I did try rebuilding a kernel with the Nov20 wd.c in it,
>     Simon> but it would not compile.  I figured an occasional hang
>     Simon> requiring a reset was less hassle than trashed filesystems.
>     Simon> Has any work been done on wd.c in the last week or so?
> Welcome to the club. You are the fourth one I know of (including me)
> who suffers from that really bad bug in wd.c that everyone keeps
> telling me is my defective hardware. It's not.

Add me as number 5 in the meantime. When I upgraded to -current from
0.9, I tried to boot a foreign -current kernel. The time it crashed on
bootup, the second time after a real reset (switch-off-switch-on) it
came up, and crashed during the work and managed to scatter various
blocks all over the disk (including parts of an OS/2 partition it didn't
own). I returned to the 0.9 driver, changed some insignificant parts
(prototype warnings), and now there is one an 'extra interrupt' during
bootup, and everything works fine.

> Dirk

         Dr. Holger Veit                   | INTERNET:
|  |   / GMD-SET German National Research  | Phone: (+49) 2241 14 2448
|__|  /  Center for Computer Science       | Fax:   (+49) 2241 14 2342
|  | /   Schloss Birlinghoven              | Had a nightmare yesterday:
|  |/    53754 St. Augustin, Germany       | My system started up with
                                           | ... Booting vmunix.el ...