Hi Michael,
Are you already using usb-1.3.0.0? If not, could you upgrade and test
again? That release fixed the deadlock that Ben and Carter where
talking about.
Good luck,
Bas
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
Bas,
I have not upgraded, mainly because my problems manifest without enabling USB.
However, I think I can upgrade in a few days and move forward.
Are you using ghc 7.8.10 these days or something older?
Mike
On Jan 21, 2015, at 12:52 PM, Bas van Dijk v.dijk@gmail.com wrote:
Hi Michael,
Bas,
I checked my cabal file and I was already using 1.3.0.0.
Mike
On Jan 21, 2015, at 12:52 PM, Bas van Dijk v.dijk@gmail.com wrote:
Hi Michael,
Are you already using usb-1.3.0.0? If not, could you upgrade and test
again? That release fixed the deadlock that Ben and Carter where
had with ghc-7.8 (7.6 too, but it's worse on
ghc-7.8 for some reason), involving possible misbehavior of the
thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
-7.8 for some reason), involving possible misbehavior of the
thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs
7.6.X
I moved from 7.6 to 7.8 and my
, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very
differently. I have three threads, an application thread that
plots
reason), involving possible misbehavior of the
thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves
Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very
differently. I have three threads, an application thread that
plots data with wxhaskell or sends
, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very
differently. I have three threads, an application thread
-7.8 for some reason), involving possible misbehavior of the
thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs
7.6.X
I moved from 7.6 to 7.8 and my
at 2:18 PM, Michael Jones m...@proclivis.com
mailto:m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very
differently. I have three threads, an application thread that
plots data
Donn,
True, but in that case I was using a driver for the Aardvark, and my current
two test cases use:
A) DC1613A from LTC
B) /dev/i2c driver with FFI wrapper I wrote
Case A uses the haskell usb package and libusb. I suppose SIGVALRM could be in
used in the libusb driver. I know for sure it
a problem very similar to one
that we had with ghc-7.8 (7.6 too, but it's worse on ghc-7.8 for some
reason), involving possible misbehavior of the thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3
Quoth Michael Jones m...@proclivis.com,
...
5) What does -V0 do that makes a problem program run?
Well, there's that SIGVTALRM barrage, you may remember we went
over that mid-August. I expect there are other effects.
Donn
___
Michael Jones m...@proclivis.com writes:
Sorry I am reviving an old problem, but it has resurfaced, such that
one system behaves different than another.
[snip]
1) Does ghc 7.8.4 have any improvements that might pertain to these kinds of
scheduling/thread problems?
2) Is there anything
Ben,
Interesting.
In this case, I can duplicate the problem when not using USB (USB to i2c
dongle) by using /dev/i2c_n, and when I do use USB, in some cases the USB is
working (can see i2c on scope), but the GUI is hung. So I believe this is not
causing the problem.
Thanks,
Mike
On Jan 13,
at 2:18 PM, Michael Jones m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I have
three threads, an application thread that plots data with wxhaskell or sends
it over a network
...@haskell.org] On Behalf Of Edward Z. Yang
| Sent: 30 October 2014 00:41
| To: John Lato
| Cc: GHC Users List
| Subject: Re: Thread behavior in 7.8.3
|
| Yes, that's right.
|
| I brought it up because you mentioned that there might still be
| occasional delays, and those might be caused
29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data with
wxhaskell or
sends it over
Jones m...@proclivis.com
wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very
differently. I
have three threads, an application thread that plots data with
wxhaskell or
sends it over a network (depends
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I have
three threads, an application thread that plots data with wxhaskell or sends it
over a network (depends on settings), a thread doing usb bulk writes
Michael Jones m...@proclivis.com writes:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data with
wxhaskell or sends it over a network (depends
bgamari.f...@gmail.com wrote:
Michael Jones m...@proclivis.com writes:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data with
wxhaskell or sends it over
Michael Jones m...@proclivis.com writes:
Ben,
I am using Bas van Dijk’s usb, and I am past the -threading issue by
using the latest commit.
Excellent; I hadn't noticed the proclivis in your email address
I don’t have any easy way of making comparisons between 7.6 and 7.8
productivity, but
, 2014 at 2:18 PM, Michael Jones m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data with wxhaskell or
sends it over
...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I have
three threads, an application thread that plots data with wxhaskell or sends
it over a network (depends on settings), a thread
-7.8 for some
reason), involving possible misbehavior of the thread scheduler.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have
, Michael Jones m...@proclivis.com wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data with wxhaskell or
sends it over a network (depends
.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones m...@proclivis.com
wrote:
I have a general question about thread behavior in 7.8.3 vs 7.6.X
I moved from 7.6 to 7.8 and my application behaves very differently. I
have three threads, an application thread that plots data
29 matches
Mail list logo
