support new

0 C Australia P Victoria T Melbourne Z 3000 O Applied OpenBSD I Duncan Hart M dun...@appliedopenbsd.com U https://www.AppliedOpenBSD.com/ N Applied OpenBSD research and development

Re: Problems installing 6.5 on Supermicro X11SDV-8C-TP8 motherboard - can't see/find network interfaces

On 2019-05-19 04:33, Hrvoje Popovski wrote: > On 19.5.2019. 3:08, Don Jackson wrote: >> I recently acquired a Supermicro 1019D-FRN8TP server with a X11SDV-8C-TP8 >> motherboard. > > try to install latest snapshot. After installation execute > sendbug -P > 1019D-FRN8TP.txt and send that output

Re: USB sound card not playing

Hi, Alexandre Ratchov this PC is old(about 10 yeas old) hitachi server (HA-8000) . the full dmesg is # dmesg OpenBSD 6.5-current (GENERIC.MP) #17: Sun May 12 00:53:38 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem =

Re: athn: device timeout

On Sun, May 19, 2019 at 07:09:00PM +, Lévai, Dániel wrote: > On Sunday, 19 May 2019 20:42, Stefan Sperling wrote: > > On Sun, May 19, 2019 at 05:38:03PM +, Lévai, Dániel wrote: > > > > > > And for some reason -- and this is really strange, I know --, sometimes > > > it gets into a

Re: Haskell compilation issues

On 5/19/19 1:24 PM, Matthias Kilian wrote: On Sun, May 19, 2019 at 12:18:44AM -0500, Joe Nelson wrote: Matthias Kilian wrote: ps: please note that I'm not subscribed to misc@ with my 'real' mail account, only with a crappy gmail account I'm only reading on my tablet (from which I forwarded

Re: Haskell compilation issues

On Sun, May 19, 2019 at 12:18:44AM -0500, Joe Nelson wrote: > Matthias Kilian wrote: > > ps: please note that I'm not subscribed to misc@ with my 'real' > > mail account, only with a crappy gmail account I'm only reading on > > my tablet (from which I forwarded your mail to my real address). So >

Re: malloc_conf J j

On May 19 16:46:44, schwa...@usta.de wrote: > >> The current "increase/decrease" wording in malloc(3) > >> can suggest it has a memory. For example, setting > >> > >>vm.malloc_conf=J > >> > >> "increases" junk level to two; > >> does setting > >> > >>vm.malloc_conf=C > >> > >> later

Re: Haskell compilation issues

Matthias Kilian wrote: > I've a really smart solution for the problem: I'll never ever even try > to give some helpful answer to any of the mails on misc@ Sorry, my message must have sounded snarky. I didn't intend it that way. Honestly just wanted to help you with your email setup. It can be

Re: athn: device timeout

On Sunday, 19 May 2019 20:42, Stefan Sperling wrote: > On Sun, May 19, 2019 at 05:38:03PM +, Lévai, Dániel wrote: > > > And for some reason -- and this is really strange, I know --, sometimes it > > gets into a state where no client can connect/auth to the AP, and nothing > > seems to be

Re: athn: device timeout

On Sun, May 19, 2019 at 05:38:03PM +, Lévai, Dániel wrote: > And for some reason -- and this is really strange, I know --, sometimes it > gets into a state where no client can connect/auth to the AP, and nothing > seems to be able to fix it other than a hard reset of the AP. On a Linux >

Re: athn: device timeout

On Sunday, 19 May 2019 18:48, Stefan Sperling wrote: > On Sun, May 19, 2019 at 02:30:25PM +, Lévai, Dániel wrote: > > > Hi everyone! > > I wonder if this 0 particular issue is what I'm experiencing. Judging from > > the fact that the only thing needed for this to happen is a full-bandwidth

Re: athn0: bad ROM checksum 0x2c64

On Sun, May 19, 2019 at 06:49:25PM +0300, 3 wrote: > > On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote: > >> shit. i have upgraded to 6.5 and now the interface is losing settings > >> after about 30 seconds: > >> athn0: flags=8843 mtu 1500 > >> lladdr b0:48:7a:8c:41:79 > >> index

Re: athn: device timeout

On Sun, May 19, 2019 at 02:30:25PM +, Lévai, Dániel wrote: > Hi everyone! > > I wonder if this [0] particular issue is what I'm experiencing. Judging from > the fact that the only thing needed for this to happen is a full-bandwidth > (~1MB/s) throughput via athn0 for about 20 seconds, I'm

Re: athn0: bad ROM checksum 0x2c64

> On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote: >> shit. i have upgraded to 6.5 and now the interface is losing settings >> after about 30 seconds: >> athn0: flags=8843 mtu 1500 >> lladdr b0:48:7a:8c:41:79 >> index 17 priority 4 llprio 3 >> groups: wlan >>

Re: route-to rule problem after upgrading to 6.5

On 19/05/2019 14:16, Ville Valkonen wrote: > On Sun, 19 May 2019 at 12.14, Carlos Lopez > wrote: > > Hi all, > >   Yesterday, I have upgraded my home OpenBSD's fws from 6.4 to 6.5. > All > seems to work ok execpt with route-to rules. The following

Re: malloc_conf J j

On Sun, May 19, 2019 at 04:46:44PM +0200, Ingo Schwarze wrote: > Hi, > > Otto Moerbeek wrote on Sun, May 19, 2019 at 02:55:09PM +0200: > > On Sun, May 19, 2019 at 08:50:20AM +0200, Jan Stary wrote: > > >> Does 'J' simply make the junk level two and > >> does 'j' simply make the junk level zero?

Re: malloc_conf J j

Hi, Otto Moerbeek wrote on Sun, May 19, 2019 at 02:55:09PM +0200: > On Sun, May 19, 2019 at 08:50:20AM +0200, Jan Stary wrote: >> Does 'J' simply make the junk level two and >> does 'j' simply make the junk level zero? No, it does not. For example, if sysctl vm.malloc_conf contains j and

athn: device timeout

Hi everyone! I wonder if this [0] particular issue is what I'm experiencing. Judging from the fact that the only thing needed for this to happen is a full-bandwidth (~1MB/s) throughput via athn0 for about 20 seconds, I'm inclined to say yes. I wanted to ask if this [1] commit should've fixed

Re: malloc_conf J j

On Sun, May 19, 2019 at 08:50:20AM +0200, Jan Stary wrote: > Does 'J' simply make the junk level two and > does 'j' simply make the junk level zero? > > The current "increase/decrease" wording in malloc(3) > can suggest it has a memory. For example, setting > > vm.malloc_conf=J > >

malloc_conf J j

Does 'J' simply make the junk level two and does 'j' simply make the junk level zero? The current "increase/decrease" wording in malloc(3) can suggest it has a memory. For example, setting vm.malloc_conf=J "increases" junk level to two; does setting vm.malloc_conf=C later

Re: route-to rule problem after upgrading to 6.5

On Sun, 19 May 2019 at 12.14, Carlos Lopez wrote: > Hi all, > > Yesterday, I have upgraded my home OpenBSD's fws from 6.4 to 6.5. All > seems to work ok execpt with route-to rules. The following rules have > been working smoothly in previous versions: > > pass in quick inet proto tcp from to

Re: athn0: bad ROM checksum 0x2c64

On Sun, May 19, 2019 at 12:33:33PM +0300, 3 wrote: > shit. i have upgraded to 6.5 and now the interface is losing settings > after about 30 seconds: > athn0: flags=8843 mtu 1500 > lladdr b0:48:7a:8c:41:79 > index 17 priority 4 llprio 3 > groups: wlan > media:

Re: Problems installing 6.5 on Supermicro X11SDV-8C-TP8 motherboard - can't see/find network interfaces

On 19.5.2019. 3:08, Don Jackson wrote: > I recently acquired a Supermicro 1019D-FRN8TP server with a X11SDV-8C-TP8 > motherboard. Hi, try to install latest snapshot. After installation execute sendbug -P > 1019D-FRN8TP.txt and send that output to b...@openbsd.org with hardware description and

Re: athn0: bad ROM checksum 0x2c64

> This should fix attach but there's some other remaining problem. > The device detaches itself again when I try to use it. > diff 709e530bc956c51de2da4aff727d8da450babdc4 /usr/src > blob - 74025dba1aff37e328c92779398e428caef72c04 > file + sys/dev/ic/ar9287.c > --- sys/dev/ic/ar9287.c > +++

route-to rule problem after upgrading to 6.5

Hi all, Yesterday, I have upgraded my home OpenBSD's fws from 6.4 to 6.5. All seems to work ok execpt with route-to rules. The following rules have been working smoothly in previous versions: pass in quick inet proto tcp from to port = 80 flags S/SA keep state (if-bound) label "Force