Re: SS20: malloc: out of space in kmem_map

2015-09-27 Thread Tobias Ulmer
How about shaving some useless looking mallocs off? Here is a start, saving 4K: Index: isofs//cd9660/cd9660_node.c === RCS file: /home/vcs/cvs/openbsd/src/sys/isofs/cd9660/cd9660_node.c,v retrieving revision 1.29 diff -u -p -r1.29

Re: fix iwm bsd.rd / lladdr random (was: Re: iwm0 not working during upgrade with bsd.rd)

2015-09-27 Thread Mark Kettenis
> Date: Sat, 26 Sep 2015 19:21:28 +0200 > From: Stefan Sperling > > On Sat, Sep 26, 2015 at 11:32:06AM -0400, Ted Unangst wrote: > > can we please use memcpy in new code? > > Sure. New diff below. > > Also uses less pointless casts in net/if.c as requested by guenther@ ok

drm hang after resume

2015-09-27 Thread Ted Unangst
with latest kernel (with the hang warnings fixed) after resume on x1 the system partially redrew the screen, then seemed hung for a while. switch to virt console and back to x either fixed it, or just coincidence. i notice this in dmesg: error: [drm:pid20144:i915_context_is_banned] *ERROR*

Re: Waking wscons powered down display hardlocks system.(Broadwell)

2015-09-27 Thread Gerald Hanuer
Hello bugs@, >>Waking from wscons display.vblank hardlocks system. I was able to get a trace out of ( kern.splassert=2 ) Not able to get to ddb. Full sendbug(1) output is with my first mail The kernel dmesg(8) that made this trace follows. The source was checkout at Sun Sep

[no subject]

2015-09-27 Thread giovanni
>Synopsis: device timeout after some minutes of use with athn(4) >Category: wireless >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8-current (GENERIC.MP) #1377: Wed Sep 23 20:48:11 MDT 2015

Re: your mail

2015-09-27 Thread Giovanni Bechis
On 09/27/15 11:26, Stefan Sperling wrote: > On Sun, Sep 27, 2015 at 10:38:36AM +0200, giova...@paclan.it wrote: >>> Synopsis: device timeout after some minutes of use with athn(4) >>> Category: wireless >>> Environment: >> System : OpenBSD 5.8 >> Details : OpenBSD

Re: your mail

2015-09-27 Thread Stefan Sperling
On Sun, Sep 27, 2015 at 12:13:08PM +0200, Giovanni Bechis wrote: > Before this athn(4) I had, on this same laptop, an urtwn(4) wireless device > that worked fine. This might be related to power consumption. Perhaps the athn draws more power than urtwn does and triggers hub driver problems more