On Thu, 24 Feb 2000, Mike Smith wrote:
> > It seems Mike Smith wrote:
> > > That's possible; it may be that the kernel linker is calling something
> > > before you expect it to be called.
> >
> > Well, its rather that the delayed probe rutine I register with
> > config_intrhook_establish() is called before interrupts are actually
> > working, that would explain why it times out on the probe...
> > This didn't happen before, so thats probably why it breaks...
> > It should break SCSI systems too, ass they do the same...
>
> Hmm. You're assuming that interrupts are working when the hooks are run,
> rather than assuming that it's safe to do things which will subsequently
> cause interrupts which ought to be correctly handled.
>
> I'd hazard a guess that the presence of modules is causing the kernel
> linker to run and pull all the sysctl hooks for modules it's finding.
> I'm probably wrong, just a guess.
It certainly seems like the intrhooks are called really early. I did a
little bit of experimenting with this problem last night, and that's
the most I found: intrhooks really seem to be called to early. I guess
I'll go look up cold usage, and see if it necessarily has to be done that
early. I'll also investigate that sysctl possibility.
> --
> \\ Give a man a fish, and you feed him for a day. \\ Mike Smith
> \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED] `------------------------------'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
