Re: re(4)/atom freezes (was Re: [SOLVED] Re: OpenBSD 4.8 freezes on certain activities)

2010-11-13 Thread Alexey Suslikov
Anton Maksimenkov wrote: 2010/11/12 Stuart Henderson s...@spacehopper.org: In my case: system just appears to freeze, no response to numlock etc, cannot enter DDB (typing blind as I'm generally in X and the machine has no serial port, but no response to ctrl-alt-esc followed by boot r).

Re: re(4)/atom freezes (was Re: [SOLVED] Re: OpenBSD 4.8 freezes on certain activities)

2010-11-13 Thread Andre Keller
Hoi Aarno Ich kann das auf meinem 5015H reproduzieren. Das erkldrt auch wieso unser rt01-peer nicht crashed, da benutzen wir re nur f|r Management, die anderen Interfaces sind em. Ich werde Escapenet einen Vorschlag zum Update machen, es ist sowieso noch eine R|ckmeldung vom Donnerstag offen

Re: re(4)/atom freezes (was Re: [SOLVED] Re: OpenBSD 4.8 freezes on certain activities)

2010-11-13 Thread Andre Keller
Sorry that should not have gone to the mailinglist. My apologies.

Re: re(4)/atom freezes (was Re: [SOLVED] Re: OpenBSD 4.8 freezes on certain activities)

2010-11-13 Thread Stuart Henderson
On 2010/11/12 21:32, Stuart Henderson wrote: (at first I forgot to disable IPsec - the IPsec gateway for my netbook is an alix, so I was also able to discover that netblast is rather good at triggering the vr(4) hangs there which require ifconfig down+up to recover from - I guess I will be

making fsck respect fs_passno 2

2010-11-13 Thread Chris Kuethe
Hi all, here's a diff to fsck to accept pass numbers greater than 2 so that one can avoid slaughtering IO-limited deviced. This is useful for people who have stacked softraids, all backed by the same disk, as might be found on a laptop with encrypted home: /dev/wd0a / ... 1

Re: Is there MCE/MCA support on amd64?

2010-11-13 Thread Philip Guenther
On Sat, Nov 13, 2010 at 2:23 PM, V.T. Mueller v...@vorsprung-durch-denken.de wrote: After a while of searching I found a note in http://www.openbsd.org/plus39.html that code for MCE/MCA was added on i386. There, it also reads: amd64 should get this next. Was there work on this already? If so,