Re: OpenBSD-current on MacBookPro9,2 Xorg acpilk-ed

2013-12-31 Thread Mark Kettenis
> I have the same symptoms on a MacbookAir5,1 running -current: boot up, run > startx (gnome), wait a couple hours while X is running, eventually observe > the screen is frozen (whatever was on the screen stays and no longer > changes), ssh into the box, run top, notice Xorg in the 'acpilk' WAI

Re: OpenBSD-current on MacBookPro9,2 Xorg acpilk-ed

2013-12-31 Thread Scott Bonds
I have the same symptoms on a MacbookAir5,1 running -current: boot up, run startx (gnome), wait a couple hours while X is running, eventually observe the screen is frozen (whatever was on the screen stays and no longer changes), ssh into the box, run top, notice Xorg in the 'acpilk' WAIT column.

Re: em(4): Don't count RX overruns and missed packets as input errros

2013-12-31 Thread Brad Smith
On 31/12/13 5:50 AM, Mike Belopuhov wrote: On 31 December 2013 09:46, Brad Smith wrote: On 31/12/13 3:14 AM, Mark Kettenis wrote: Date: Tue, 31 Dec 2013 01:28:04 -0500 From: Brad Smith Don't count RX overruns and missed packets as inputs errors. They're expected to increment when using MCLG

Re: re(4): tedu some unused code

2013-12-31 Thread Brad Smith
On Tue, Dec 31, 2013 at 09:55:54AM -0800, Chris Cappuccio wrote: > Brad Smith [b...@comstyle.com] wrote: > > tedu some unused code. it has never been enabled and will not be; to > > deal with a hardware defect for rare boards. unmaintained, untested, etc. > > want to get rid of it. > > > > Comment

Re: re(4): tedu some unused code

2013-12-31 Thread Chris Cappuccio
Brad Smith [b...@comstyle.com] wrote: > tedu some unused code. it has never been enabled and will not be; to > deal with a hardware defect for rare boards. unmaintained, untested, etc. > want to get rid of it. > > Comments? OK? > If RE_DIAG wasn't being compiled in, then it should be removed. Th

Re: tedu old PKG_PREFIX

2013-12-31 Thread Landry Breuil
On Tue, Dec 31, 2013 at 01:19:32PM +0100, Marc Espie wrote: > I think I put this in for compatibility with the old tools years ago. > I don't think anyone still uses this, so this can probably die. > > (I have run a grep thru the ports tree and the man pages, no reference at all) > > okay ? I th

tedu old PKG_PREFIX

2013-12-31 Thread Marc Espie
I think I put this in for compatibility with the old tools years ago. I don't think anyone still uses this, so this can probably die. (I have run a grep thru the ports tree and the man pages, no reference at all) okay ? Index: OpenBSD/Delete.pm ===

Re: em(4): Don't count RX overruns and missed packets as input errros

2013-12-31 Thread Mike Belopuhov
On 31 December 2013 09:46, Brad Smith wrote: > On 31/12/13 3:14 AM, Mark Kettenis wrote: >>> >>> Date: Tue, 31 Dec 2013 01:28:04 -0500 >>> From: Brad Smith >>> >>> Don't count RX overruns and missed packets as inputs errors. They're >>> expected to increment when using MCLGETI. >>> >>> OK? >> >>

Re: TOD clock for octeons

2013-12-31 Thread Paul Irofti
On Tue, Dec 31, 2013 at 02:22:10AM +0200, Paul Irofti wrote: > On Mon, Dec 30, 2013 at 06:49:38PM +0200, Paul Irofti wrote: > > On Mon, Dec 30, 2013 at 02:47:58PM +0200, Paul Irofti wrote: > > > The following enables the DS1337 RTC clock found on octeon boards. > > > > > > I've tested it on my DSR

Re: em(4): Don't count RX overruns and missed packets as input errros

2013-12-31 Thread Brad Smith
On 31/12/13 3:14 AM, Mark Kettenis wrote: Date: Tue, 31 Dec 2013 01:28:04 -0500 From: Brad Smith Don't count RX overruns and missed packets as inputs errors. They're expected to increment when using MCLGETI. OK? These may be "expected", but they're still packets that were not received. And

Re: em(4): Don't count RX overruns and missed packets as input errros

2013-12-31 Thread Mark Kettenis
> Date: Tue, 31 Dec 2013 01:28:04 -0500 > From: Brad Smith > > Don't count RX overruns and missed packets as inputs errors. They're > expected to increment when using MCLGETI. > > OK? These may be "expected", but they're still packets that were not received. And it is useful to know about thes