op 24-03-14 01:18, Alan Somers schreef:
On Sun, Mar 23, 2014 at 4:23 PM, Mark Felder wrote:
Hi guys,
Any updates?
I've been very busy, but I did finally get those two seqpacket related
bugs fixed in head. The next step is finding time for the merge.
Right now my FreeBSD todo list goes:
1) C
I added some logging to see what is going on and this is what I got (none
of the proposed solution solved the problem)
uhso_detach gets called 7 times (for oid 0-6). It crashes the 2nd time on
the call usbd_transfer_unsetup(sc->sc_xfer, 3);
--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.
On Mon
On 23.06.2014 6:46, Alexander Kabaev wrote:
> Please provide us with the information on the actual audio hardware
> you are using, preferably in form of a dmesg output.
uaudio0: on
usbus3
uaudio0: No playback.
uaudio0: Record: 16000 Hz, 1 ch, 16-bit S-LE PCM format, 2x8ms buffer.
uaudio0: No MI
On 06/23/14 04:46, Alexander Kabaev wrote:
On Mon, 23 Jun 2014 06:04:20 +0400
Andrey Chernov wrote:
Always happens at shutdown after all buffers are synced, see
screenshot: http://i.imgur.com/8WXTMPj.png
--
http://ache.vniz.net/
Hi Andrey,
there's not to much to go on from the screenshoot
On 06/23/14 03:30, Lundberg, Johannes wrote:
Hi
I tried replacing
DRIVER_MODULE(uhso, uhub, uhso_driver, uhso_devclass, uhso_driver_loaded,
0);
with
DRIVER_MODULE_ORDERED(uhso, uhub, uhso_driver, uhso_devclass,
uhso_driver_loaded, 0, SI_ORDER_ANY);
but makes no difference..
Don't know if its re
On Mon, 23 Jun 2014 06:04:20 +0400
Andrey Chernov wrote:
> Always happens at shutdown after all buffers are synced, see
> screenshot: http://i.imgur.com/8WXTMPj.png
>
> --
> http://ache.vniz.net/
Hi Andrey,
there's not to much to go on from the screenshoot alone and one would
expect more deta
Always happens at shutdown after all buffers are synced, see screenshot:
http://i.imgur.com/8WXTMPj.png
--
http://ache.vniz.net/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
Hi
I tried replacing
DRIVER_MODULE(uhso, uhub, uhso_driver, uhso_devclass, uhso_driver_loaded,
0);
with
DRIVER_MODULE_ORDERED(uhso, uhub, uhso_driver, uhso_devclass,
uhso_driver_loaded, 0, SI_ORDER_ANY);
but makes no difference..
Don't know if its relevant but with ucom debug on I get a message j
On 2014-06-22 10:56, O. Hartmann wrote:
>
> Hello.
>
> I face a strange problem on a set of CURRENT driven boxes. The systems in
> question are
> all the same version of CURRENT (more or less, a week or so discrepancy).
>
> The boxes affected have 8 GB of RAM and are old-style Core2Duo systems.
When they segfault, where do they segfault?
-a
On 22 June 2014 07:56, O. Hartmann wrote:
>
> Hello.
>
> I face a strange problem on a set of CURRENT driven boxes. The systems in
> question are
> all the same version of CURRENT (more or less, a week or so discrepancy).
>
> The boxes affected
Hello.
I face a strange problem on a set of CURRENT driven boxes. The systems in
question are
all the same version of CURRENT (more or less, a week or so discrepancy).
The boxes affected have 8 GB of RAM and are old-style Core2Duo systems.
The phenomenon:
Starting up the box shows the operati
11 matches
Mail list logo