Re: [pkg-go] Bug#852959: Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

2017-01-29 Thread Martín Ferrari
Jeffrey, On 29/01/17 21:09, Jeffrey Walton wrote: > As a stopgap, you might consider adding a small swapfile and setting > swapiness to a low value. I am talking about buildds, and a package prevented from migrating to testing because of this :) > Nearly every ARM gadget I had was suffering OOM

Re: [pkg-go] Bug#852959: Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

2017-01-29 Thread Jeffrey Walton
> Sadly, it turns out armhf fails to build due to one test taking a bit > too much memory[1], and there is an RC bug open for that: #852959[2]. > > So now I don't know what to do, except asking for removal of prometheus > from armhf. As a stopgap, you might consider adding a small swapfile and set

Re: [pkg-go] Bug#852959: Bug#852959: prometheus FTBFS on armhf: github.com/prometheus/prometheus/storage/local fails

2017-01-29 Thread Martín Ferrari
Hello ARM porters, I am the maintainer for the prometheus suite, which is in testing. Last week, just before the deadline I prepared and uploaded a new upstream release (which I even tested in an armel porterbox to be sure). Sadly, it turns out armhf fails to build due to one test taking a bit to

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
On Sunday 29 January 2017 13:56:53 Tzafrir Cohen wrote: > On Sun, Jan 29, 2017 at 12:47:34PM -0500, Gene Heskett wrote: > > On Sunday 29 January 2017 11:58:57 Paul Wise wrote: > > > USB protocol: use wireshark to see if the keyboard event packets > > > are reaching the device. > > > > I'll have to

Re:[SOLVED]missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
On Sunday 29 January 2017 13:56:53 Tzafrir Cohen wrote: > On Sun, Jan 29, 2017 at 12:47:34PM -0500, Gene Heskett wrote: > > On Sunday 29 January 2017 11:58:57 Paul Wise wrote: > > > USB protocol: use wireshark to see if the keyboard event packets > > > are reaching the device. > > > > I'll have to

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Alan Corey
Hmm, sort of like sitting a couple hundred feet in the air with tons of rocket fuel and LOX under you hoping it doesn't all blow up. Yeah, I used to run (not own) a South Bend lathe about that size. I've got a Microlux 7x14. Nice little digital scope, more than I can afford on my SS. I've got a

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Tzafrir Cohen
On Sun, Jan 29, 2017 at 12:47:34PM -0500, Gene Heskett wrote: > On Sunday 29 January 2017 11:58:57 Paul Wise wrote: > > USB protocol: use wireshark to see if the keyboard event packets are > > reaching the device. > > I'll have to install these tools. And I'll report what I find. I was > not a

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
On Sunday 29 January 2017 12:40:21 Alan Corey wrote: > I wonder why there's so much noise. Are you using something like a > light dimmer for speed control? And what kind of noise, continuous or > spikes when events happen? If you turn on an AM radio in the vicinity > you'll probably hear your l

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
On Sunday 29 January 2017 12:16:52 Jonathan Wilson wrote: > On Sun, 2017-01-29 at 08:47 -0500, Gene Heskett wrote: > > Greetings everybody; > > > > I am in the process of bringing a nearly 70 yo Sheldon lathe back to > > life, useing an raspberry-pi 3b for the machine controller. > > > > However,

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
On Sunday 29 January 2017 11:58:57 Paul Wise wrote: > On Sun, Jan 29, 2017 at 9:47 PM, Gene Heskett wrote: > > However, I have now had 5 different keyboards plugged into it, some > > wired, some wireless, and none of them can give me a dependable > > response to a key, and the error seems much wor

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Alan Corey
I wonder why there's so much noise. Are you using something like a light dimmer for speed control? And what kind of noise, continuous or spikes when events happen? If you turn on an AM radio in the vicinity you'll probably hear your lathe noises, which might be helpful. I was thinking lathe = i

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Jonathan Wilson
On Sun, 2017-01-29 at 08:47 -0500, Gene Heskett wrote: > Greetings everybody; > > I am in the process of bringing a nearly 70 yo Sheldon lathe back to > life, useing an raspberry-pi 3b for the machine controller. > > However, I have now had 5 different keyboards plugged into it, some > wired, s

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Paul Wise
On Sun, Jan 29, 2017 at 9:47 PM, Gene Heskett wrote: > However, I have now had 5 different keyboards plugged into it, some > wired, some wireless, and none of them can give me a dependable response > to a key, and the error seems much worse for the key-up event. Check the different layers of the

Re: missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Mark Morgan Lloyd
On 29/01/17 14:00, Gene Heskett wrote: Greetings everybody; I am in the process of bringing a nearly 70 yo Sheldon lathe back to life, useing an raspberry-pi 3b for the machine controller. However, I have now had 5 different keyboards plugged into it, some wired, some wireless, and none of them

missed keystrokes problem, back with a vengeance.

2017-01-29 Thread Gene Heskett
Greetings everybody; I am in the process of bringing a nearly 70 yo Sheldon lathe back to life, useing an raspberry-pi 3b for the machine controller. However, I have now had 5 different keyboards plugged into it, some wired, some wireless, and none of them can give me a dependable response to