Today Oliver Fromme wrote:
> The comment in LINT about AUTO_EOI_2 sounds pretty suspicous,
> so I never even tried it: "it works for some clones and some
> integrated versions." That sounds to me like "it works on a
> very limited set of hardware (and if you're lucky)."
I've only got one out o
Oliver Fromme schrieb:
>
> Doug White wrote in list.freebsd-current:
> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > > It seems Dieter Rothacker wrote:
> > > > The solution for me was to recompile the kernel without AUTO_EOI1 and
> > > > AUTO_EOI2.
> > >
> > > Those options newer worked (
Doug White wrote in list.freebsd-current:
> On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > It seems Dieter Rothacker wrote:
> > > The solution for me was to recompile the kernel without AUTO_EOI1 and
> > > AUTO_EOI2.
> >
> > Those options newer worked (for me at least) reliably with anything
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> It seems Dieter Rothacker wrote:
> >
> > Using the new board, I get "waiting for interrupt" errors, and the system
> > freezes while trying to mount the disks (with kernel from 12/03) or the
> > system freeezes before being able to detect the drives (w
It seems Dieter Rothacker wrote:
>
> Using the new board, I get "waiting for interrupt" errors, and the system
> freezes while trying to mount the disks (with kernel from 12/03) or the
> system freeezes before being able to detect the drives (with kernel from
> 12/20).
>
> The solution for me wa
