> Wow! This did away with the once-a-minute error messages from Notify()s
> on processor objects on my laptop.
> However, I am now getting frequent panics from from a GIANT_REQUIRED
> assertion in kmem_malloc(). kmem_malloc() gets called via malloc() from
> AcpiOsAllocate(), without Giant locked.
> The call to AcpiOsAllocate() happens deep in a AML object evaluation
> in from acpi_tz_thread().
> I tried naively to modify AcpiOsAllocate to grab Giant before malloc()
> and release it afterward, but this appears to be a very bad idea: There
> is a mtx_assert(&Giant, MA_NOTOWNED) in ithread_loop() in kern/kern_intr.c
> which blows up during boot.
Try grabbing Giant in acpi_tz_thread when it wakes up, then dropping it
again before it goes to sleep. This is probably a hack, but I'd guess a
required one for now.
If that works, send me a diff and I'll commit it with thanks!
To announce that there must be no criticism of the president,
or that we are to stand by the president, right or wrong, is not
only unpatriotic and servile, but is morally treasonable to
the American public. - Theodore Roosevelt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message