On 30 June 2013 07:22, Ian Smith wrote:
> After removing [numbers] (for WITNESS?), diff started making sense.
> The below is between the first and second suspend/resume cycles in
> dmesg-3.txt, encompassing the others.
Cool!
> Nothing of note that I can see, if that usb hub-to-bus remapping is
On Sun, Jun 30, 2013 at 02:20:21PM -0400, Jason Hellenthal wrote:
> When using svn 1.8 I have come across a situation where when it is used
> pointing to a symlink that refers to a working directory that a update will
> either segfault or exit prematurely and leave a lock held on the working
> d
When using svn 1.8 I have come across a situation where when it is used
pointing to a symlink that refers to a working directory that a update will
either segfault or exit prematurely and leave a lock held on the working
directory that the symlink points to.
This leaves you with one choice but
On Sat, 29 Jun 2013, Adrian Chadd wrote:
> On 27 June 2013 04:58, Ian Smith wrote:
> > We don't yet know if this is a bus, ACPI &/or USB issue. Home yet? :)
>
> Yup:
>
> http://people.freebsd.org/~adrian/usb/
>
> dmesg.boot = dmesg at startup
>
> 1 - after powerup, usb device in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-EN-13:02.vtnet Errata Notice
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-EN-13:01.fxpErrata Notice
The FreeBSD Project
Topic:
