This is not a crash, but a hang. Are you running current? You still haven't improved your bug reporting. Please refer to the official guide to OpenBSD bug reporting:
http://www.openbsd.org/report.html On 1 August 2016 at 11:45, Antonis Psaras <[email protected]> wrote: > Hello Mike > > > > One more crash with hi CPU usage > > > > > > -----Original Message----- > From: Mike Belopuhov [mailto:[email protected]] > Sent: Saturday, July 30, 2016 1:35 AM > To: Antonis Psaras <[email protected]> > Cc: [email protected]; Evgeniy Sudyr <[email protected]> > Subject: Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive > > > > I've decided to bite the bullet and solved the issue with task threads and > timeouts for now. There's a considerable increase in performance, but more > importantly, I can't DoS the system anymore. I welcome independent tests, > perfomance evaluations and code review. > > > > Cheers, > > Mike > > > > On Fri, Jul 29, 2016 at 20:41 +0200, Mike Belopuhov wrote: > > > A number of TX-related issues have been fixed in -current. > > > Please make sure that you're running -current with up-to-date source > > > tree (sys/dev/pv/if_xnf is at revision 1.27 as of writing) and > > > retest. > > > > > > I don't have a sensible fix for RX stalls at the moment short of of > > > polling (be it a periodic timer or a thread wakeup). > > > > > > On 28 July 2016 at 13:49, Antonis Psaras <[email protected]> > wrote: > > > > > > > I ‘ve done many updates in the past without any issue. I am not sure > > > > why I have that problem on updating to snapshot. > > > > > > > > > > > > > > > > I will give it a try again. > > > > > > > > > > > > > > > > *From:* Mike Belopuhov [mailto:[email protected] <[email protected]> > ] > > > > *Sent:* Thursday, July 28, 2016 1:28 PM > > > > > > > > *To:* Antonis Psaras <[email protected]> > > > > *Cc:* [email protected] > > > > *Subject:* Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive > > > > > > > > > > > > > > > > On 28 July 2016 at 11:18, Antonis Psaras <[email protected]> > wrote: > > > > > > > > I tried that but I get the same message. > > > > > > > > > > > > > > > > > > > > > > > > Well, you need to understand how to upgrade OpenBSD if you're going > > > > to use it. > > > > > > > > > > > > > > > > > > > > > > > > I also experience very slow i/o resulting to very low performance in > > > > general > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Paravirtualized disk driver is not implemented yet. > > > > > > > > > > > > > > > > Would it be help full for you to give you access on the box? > > > > > > > > > > > > > > > > > > > > > > > > Definitely not. > > > > > > > > > > > > > > > > Regards > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *From:* Mike Belopuhov [mailto:[email protected] <[email protected]> > ] > > > > *Sent:* Thursday, July 28, 2016 1:37 AM > > > > > > > > > > > > *To:* Antonis Psaras <[email protected]> > > > > *Cc:* [email protected] > > > > *Subject:* Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive > > > > > > > > > > > > > > > > The path it's showing you in the installer says > 'pub/OpenBSD/6.0/amd64'. > > > > > > > > You have to change that to 'pub/OpenBSD/snapshots/amd64'. Official > > > > > > > > release of 6.0 is expected September 1. > > > > > > > > > > > > > > > > On 27 July 2016 at 18:25, Antonis Psaras <[email protected]> > wrote: > > > > > > > > I tried 2nd method using bsd.rd to update the system but I get an > > > > error message stating that cannot find OpenBSD/amd64 6.0 sets. > > > > > > > > > > > > > > > > Path is correct, I crossed check that. > > > > > > > > > > > > > > > > When 6.0 is expected? > > > > > > > > > > > > > > > > Regards > > > > > > > > > > > > > > > > > > > > > > > > *From:* Mike Belopuhov [mailto:[email protected] <[email protected]> > ] > > > > *Sent:* Wednesday, July 27, 2016 5:25 PM > > > > > > > > > > > > *To:* Antonis Psaras <[email protected]> > > > > *Cc:* [email protected] > > > > *Subject:* Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive > > > > > > > > > > > > > > > > Antonis, > > > > > > > > > > > > > > > > You need to grab the files from 'snapshots/amd64' instead > > > > > > > > of the release directory, e.g. from here: > > > > > > > > http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/ > > > > > > > > > > > > > > > > And then either: > > > > > > > > > > > > > > > > 1) reinstall the system (i'd say it's easier to do that) > > > > > > > > > > > > > > > > 2) if you have access to the console, put new bsd.rd into / > > > > > > > > and then run "boot /bsd.rd" at the "boot>" prompt > > > > > > > > > > > > > > > > 3) live update your system like specified here: > > > > > > > > http://www.openbsd.org/faq/upgrade59.html#NoInstKern > > > > > > > > (copy bsd.mp kernel you've downloaded to / and then > > > > > > > > follow the "Install new userland" section). This is not > > > > > > > > advised however. > > > > > > > > > > > > > > > > After that you'll have to either build new kernel from > > > > > > > > the source code or I can send you a binary. > > > > > > > > > > > > > > > > On 27 July 2016 at 15:37, Antonis Psaras <[email protected]> > wrote: > > > > > > > > Hello Mike > > > > > > > > > > > > > > > > Thank you for your quick response. > > > > > > > > > > > > > > > > The problem is totally random and probably has to do with traffic on > > > > the interface. Never the less, the problem always produce the > > > > problem on xnf0 which is one of the Wan interfaces I have and never > > > > on xnf1 which is the LAN interface or xnf2,3,4 which are also Wan > > > > interfaces. The installation I have is a Wifi gateway. Wifi devices > > > > are connected on a wireless network and get access to the internet > > > > via OpenBSD Box. Services that OpenBSD has are ISC DHCP, NGINX, > UNBOUND, SQUID etc. > > > > > > > > > > > > > > > > Bellow you can find the traffic graph for that period > > > > > > > > > > > > > > > > > > > > > > > > I can try any patch but please send me some more information on how > > > > to do that. > > > > > > > > > > > > > > > > Regards > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Mike Belopuhov [mailto:[email protected] <[email protected]>] > > > > Sent: Wednesday, July 27, 2016 1:01 PM > > > > To: Antonis Psaras <[email protected]> > > > > Cc: [email protected] > > > > Subject: Re: OpenBSD 5.9 on XenServer 6.5, Network unresponsive > > > > > > > > > > > > > > > > Hi Antonis, > > > > > > > > > > > > > > > > While your report could have been a bit more detailed (for instance > > > > describing how did you get into this situation), I'm aware of the > > > > generic problem with failed interrupt delivery that can be triggered > > > > under heavy network load, e.g. packet flood. I'm trying to fix this > > > > right now. I'll be committing some diffs to -current, so I'd highly > > > > recommend updating to the latest snapshot (right now we're in the > > > > end of locking down 6.0) if you would like to test patches. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Mike > > > > > > > > > > > > > > > > On 26 July 2016 at 23:17, Antonis Psaras <[email protected]> > wrote: > > > > > > > > > Hello > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have installed OpenBSD 5.9 amd64 on XenServer 6.5 with all > > > > > patches > > > > > > > > > up to > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The problem I have is that the xnf interfaces are getting > unresponsive. > > > > > > > > > Console through XenCenter interface is working fine but some (not > > > > > all) > > > > > > > > > xnf interface are not. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Console output > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Strange thing is that xnf 1 2 and 3 are working fine but xnf0 is not. > > > > > > > > > The only way to have that working again is by rebooting. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > How can I debug the above issue? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Just a note, I tried a patch on Xen for e1000 emulation but I have > > > > > the > > > > > > > > > same response. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank you in advance > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Antonis. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
