It seems Doug Rabson wrote:
> >
> > That megapatch was only newbus patches and cosmetics around that, one
> > new item was cmd646 support but that is hardly the problem here.
> >
> > > Soren - this is somewhat of a showstopper. Can you reproduce it there?
> >
> > Nope, I've tried several machines here, no problems, even with tons
> > of modules..
> >
> > The only thing I can come up with is that _something_ makes the
> > delayed probe be called _before_ interrupts are up and running.
> > That will make it fail like this. Quuestion is is something
> > else messing with those hooks ?
> > We've seen this before, but back then no solution was found either,
> > it dissaperead all by itself...
>
> Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW.
> Nick spent a couple of hours looking at it without much success. I'll try
> some things today to see if the probe is being called with interrupts
> disabled.
My main dev box is an Athlon too, so that is not the problem.
I still suspect missing interrupts...
-S�ren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
