Some questions about da0 on USB2 (recent bad behaviour)
bf1783 at googlemail.com
Mon Oct 26 21:28:07 UTC 2009
On 10/26/09, Andrew Reilly <areilly at bigpond.net.au> wrote:
> On Sat, Oct 24, 2009 at 07:07:00PM +0000, b. f. wrote:
> I haven't run -current for, probably, ten years, and the
> occasional messages about lock-order-reversals worry me a bit,
> but don't seem to be doing any harm. Should I report them? In
> a PR?
Some of them are known, and are either harmless or a false positive.
If you get an LOR, you can check to see if a similar LOR has already
been noted on Bjoern Zeeb's page:
If it hasn't, send him an email with the LOR, and the circumstances
under which it arose, as described on that page. Don't forget that
there is a lot of debugging code enabled by default under -CURRENT
(which at this point is still pretty close to 8-STABLE, and will be
until after the release of 8.0, so it ought to be fairly stable). If
you feel confident about the safety of using -CURRENT, and want to get
the best performance, disable the debugging code as described in
> Please count this message as a vote for MFC'ing those cam and
> usb changes to 8-STABLE.
I'm guessing that these changes will make it into 8.0, or at least
8-STABLE, fairly soon; but mav@, thompsa@, and re@ will know more.
More information about the freebsd-stable