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 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
> talking about.
>
>
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 wrote:
> Hi Michael,
>
> Are you already
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
ht
ies to create a wxHaskell frame. In another non-UI version of the
>>>>>>> program it also fails to run. Logging to a file gives a similar
>>>>>>> indication. It is clear that the program starts up, then fails during
>>>>>>> the
e time. When it did
>>>>>>> run, it continued to run properly. This perhaps indicates some kind
>>>>>>> of
>>>>>>> internal race condition.
>>>>>>>
>>>>>>> In the fail to run case, it does some printing
run your program with
`+RTS -C0.005` ? If so, I suspect you're having 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 mailt
the above was done with profiling enabled, so I removed that and
> >>>>> instead enabled eventlog to look for clues.
> >>>>>
> >>>>> In this case it lies between good and bad, in that IO to my USB is
> >>>>> working, but the
s, but
>>>>> USB continues.
>>>>>
>>>>> Questions:
>>>>>
>>>>> 1) Does ghc 7.8.4 have any improvements that might pertain to these
>>>>> kinds of scheduling/thread problems?
>>>>> 2) Is there anything about t
s 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 it over a network
What does -V0 do that makes a problem program run?
>>>
>>> Mike
>>>
>>>
>>>
>>>
>>> On Oct 29, 2014, at 6:02 PM, Michael Jones >> <mailto:m...@proclivis.com>> wrote:
>>>
>>>> John,
>>>>
.
On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones 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 wi
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 is
Quoth Michael Jones ,
...
>> 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
___
Glasgow-haskell-users mailing lis
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 wrote:
>>> I have a general questio
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,
Michael Jones 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 about the nature
sbehavior of the thread scheduler.
>>
>> On Wed, Oct 29, 2014 at 2:18 PM, Michael Jones 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
>>>> help at N1.
> >>>>
> >>>> We did see this behavior in 7.6, but it's definitely worse in 7.8.
> >>>>
> >>>> Incidentally, has there been any interest in a work-stealing
> scheduler?
> >>>> There was a discuss
like this.
>>>>
>>>> John L.
>>>>
>>>> On Thu, Oct 30, 2014 at 8:02 AM, Michael Jones
>>> wrote:
>>>>
>>>>> John,
>>>>>
>>>>> Adding -C0.005 makes it much better. Using -C0.001 makes
...@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
is saves my project, as I need to deploy on a single core
> > Atom
> > > > and was stuck.
> > > >
> > > > Mike
> > > >
> > > > On Oct 29, 2014, at 5:12 PM, John Lato wrote:
> > > >
> > > > By any chance do t
ct, as I need to deploy on a single core
> Atom
> > > and was stuck.
> > >
> > > Mike
> > >
> > > On Oct 29, 2014, at 5:12 PM, John Lato wrote:
> > >
> > > By any chance do the delays get shorter if you run your program with
> `+RTS
&
r program with `+RTS
> > -C0.005` ? If so, I suspect you're having 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
gt; 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 wrote:
>
>> I have a general question about thread behavior in 7.8.3 vs 7.6.X
>&g
chael Jones 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 set
ed, Oct 29, 2014 at 2:18 PM, Michael Jones 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 o
Michael Jones 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 from osci
:
> Michael Jones 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
Michael Jones 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
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, and
30 matches
Mail list logo
