> : dstumbler breaks; on startup it reports
> : "unable to ioctl device socket: Input/output error".
>
> As root or no?
As root, with interface up and configured.
Magnus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
> > to be resolved or documented before MFC. (copied maintainer)
>
> Why, did they not work/build after the commit? I didn't try all the ports
> that depend on the driver but the API (ioctls) should be unchanged except
> f
On Thu, 16 Jan 2003, Sam Leffler wrote:
>...
> to your config files. This probably belongs in UPDATING.
NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
to be resolved or documented before MFC. (copied maintainer)
Magnus
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
On Sun, 24 Feb 2002, Michael Smith wrote:
> 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!
Yow! Works abso
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 ca
I put CURRENT on a new Dell Inspiron 4100 laptop this weekend. Works fine,
but I keep getting these messages:
ACPI-0294: *** Error: Method execution failed, AE_AML_OPERAND_TYPE
The messages are logged once every few seconds, and every time I e g remove
or insert a battery.
I'm not sure wha
