Re: Kernel panic with openbsd 6.2
On 2018-01-19, Mik J wrote: > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > n esxi 5.5 > > # grep "" /tmp/if_vmx.dis I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. I suggest switching to e1000 in the vmx file, this works with the em(4) driver and has been stable so far.
Re: Kernel panic with openbsd 6.2
Hello Stuart,Thank you for your answer.I had my VM running for months in version 6.1 and had not problem but I reinstalled it in version 6.2 and the problem is happening.It seems to me that something in version 6.2 is producing the error.One crash today again Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson a écrit : On 2018-01-19, Mik J wrote: > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > n esxi 5.5 > > # grep "" /tmp/if_vmx.dis I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. I suggest switching to e1000 in the vmx file, this works with the em(4) driver and has been stable so far.
Re: Kernel panic with openbsd 6.2
On 2018/01/22 00:22, Mik J wrote: > Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson > a écrit : > On 2018-01-19, Mik J wrote: > > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > > n esxi 5.5 > > > > # grep "" /tmp/if_vmx.dis > > I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. > I suggest switching to e1000 in the vmx file, this works with the em(4) > driver and has been stable so far. > > > Hello Stuart, > Thank you for your answer. > I had my VM running for months in version 6.1 and had not problem but I > reinstalled it in > version 6.2 and the problem is happening. > It seems to me that something in version 6.2 is producing the error. > One crash today again I hit this in last April, which was either 6.1 or -current from soon after. It can take weeks to run into it though so bisecting to find a working kernel is futile.
Re: Kernel panic with openbsd 6.2
Hello Stuart, For me it takes just a few days... I have a crash every 3/4 days maybe (2 crashes so far) and my server does not handle load. Yes I read your reports this morning, although you wrote that there was a combination with snmpd, I have it with nginx on my side. Regards Le lundi 22 janvier 2018 à 10:35:47 UTC+1, Stuart Henderson a écrit : On 2018/01/22 00:22, Mik J wrote: > Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson > a écrit : > On 2018-01-19, Mik J wrote: > > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > > n esxi 5.5 > > > > # grep "" /tmp/if_vmx.dis > > I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. > I suggest switching to e1000 in the vmx file, this works with the em(4) > driver and has been stable so far. > > > Hello Stuart, > Thank you for your answer. > I had my VM running for months in version 6.1 and had not problem but I > reinstalled it in > version 6.2 and the problem is happening. > It seems to me that something in version 6.2 is producing the error. > One crash today again I hit this in last April, which was either 6.1 or -current from soon after. It can take weeks to run into it though so bisecting to find a working kernel is futile.
Re: Kernel panic with openbsd 6.2
Could it be related to: https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/ ? > Sent: Friday, January 19, 2018 at 9:50 PM > From: "Mik J" > To: Misc > Subject: Kernel panic with openbsd 6.2 > > Hello, > > I had many kernel panic these past days. This is a 6.2 openbsd VM running on > esxi 5.5 > > I took screenshots then followed > https://www.openbsd.org/ddb.html > > # objdump -dlr /sys/arch/amd64/compile/GENERIC.MP/obj/if_vmx.o > > /tmp/if_vmx.dis > > # grep "" /tmp/if_vmx.dis > 10f6: e8 d5 00 00 00 callq 11d0 > 1176: e8 55 00 00 00 callq 11d0 > 11d0 : > 1857: e8 74 f9 ff ff callq 11d0 > > # grep -n 10f6 /tmp/if_vmx.dis > 1667: 10f6: e8 d5 00 00 00 callq 11d0 > > # grep ":" /tmp/if_vmx.dis > 11d0 : > > # printf '%x\n' $((0x11d0 + 0x263)) > 1433 > > vi /tmp/if_vmx.dis > 2040 1433: ba 01 00 00 00 mov $0x1,%edx > I find is on line 2040 > > => But the file is only 1251 line long > nl -ba /sys/dev/pci/if_vmx.c | sed -n 2040p > > => So that last command gives me nothing > > Do you have an idea of what mistake I did so that I can make a report ? > > Thank you > >
Re: Kernel panic with openbsd 6.2
On 2018-01-24, who one wrote: > Could it be related to: > https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/ No. > ? > >> Sent: Friday, January 19, 2018 at 9:50 PM >> From: "Mik J" >> To: Misc >> Subject: Kernel panic with openbsd 6.2 >> >> Hello, >> >> I had many kernel panic these past days. This is a 6.2 openbsd VM running on >> esxi 5.5 >> >> I took screenshots then followed >> https://www.openbsd.org/ddb.html >> >> # objdump -dlr /sys/arch/amd64/compile/GENERIC.MP/obj/if_vmx.o > >> /tmp/if_vmx.dis >> >> # grep "" /tmp/if_vmx.dis >> 10f6: e8 d5 00 00 00 callq 11d0 >> 1176: e8 55 00 00 00 callq 11d0 >> 11d0 : >> 1857: e8 74 f9 ff ff callq 11d0 >> >> # grep -n 10f6 /tmp/if_vmx.dis >> 1667: 10f6: e8 d5 00 00 00 callq 11d0 >> >> # grep ":" /tmp/if_vmx.dis >> 11d0 : >> >> # printf '%x\n' $((0x11d0 + 0x263)) >> 1433 >> >> vi /tmp/if_vmx.dis >> 2040 1433: ba 01 00 00 00 mov $0x1,%edx >> I find is on line 2040 >> >> => But the file is only 1251 line long >> nl -ba /sys/dev/pci/if_vmx.c | sed -n 2040p >> >> => So that last command gives me nothing >> >> Do you have an idea of what mistake I did so that I can make a report ? >> >> Thank you >> >> > >
Re: Kernel panic with openbsd 6.2
On Mon, January 22, 2018 10:47 am, Mik J wrote: > Hello Stuart, > For me it takes just a few days... > I have a crash every 3/4 days maybe (2 crashes so far) and my server does > not handle load. > Yes I read your reports this morning, although you wrote that there was a > combination with snmpd, I have it with nginx on my side. > > Regards > > Le lundi 22 janvier 2018 à 10:35:47 UTC+1, Stuart Henderson > a écrit : > > On 2018/01/22 00:22, Mik J wrote: >> Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson >> a écrit : >> On 2018-01-19, Mik J wrote: >> > I had many kernel panic these past days. This is a 6.2 openbsd VM >> running o= >> > n esxi 5.5 >> > >> > # grep "" /tmp/if_vmx.dis >> >> I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. >> I suggest switching to e1000 in the vmx file, this works with the em(4) >> driver and has been stable so far. >> >> >> Hello Stuart, >> Thank you for your answer. >> I had my VM running for months in version 6.1 and had not problem but I >> reinstalled it in >> version 6.2 and the problem is happening. >> It seems to me that something in version 6.2 is producing the error. >> One crash today again > > I hit this in last April, which was either 6.1 or -current from soon > after. > It can take weeks to run into it though so bisecting to find a working > kernel > is futile. > > I am running about a dozen 6.2 -stable VMs on ESXi 6.5. I have exactly one VM that panics with vmxnet3_getbuf but only when it's being snapshotted. And not every time, but usually. I think once it paniced when I was snapshotting a lot of other VMs in the cluster but I don't trust that memory now. I've not seen that again. Tim.
Re: Kernel panic with openbsd 6.2
As Stuart mentioned, em(4) on top of e1000 proven to be more stable. Even under higher load. Vmx starting to misbehave under high load, resulting for ex. with unstable CARP setup. //mxb > 25 jan. 2018 kl. 02:40 skrev trondd : > > On Mon, January 22, 2018 10:47 am, Mik J wrote: >> Hello Stuart, >> For me it takes just a few days... >> I have a crash every 3/4 days maybe (2 crashes so far) and my server does >> not handle load. >> Yes I read your reports this morning, although you wrote that there was a >> combination with snmpd, I have it with nginx on my side. >> >> Regards >> >>Le lundi 22 janvier 2018 à 10:35:47 UTC+1, Stuart Henderson >> a écrit : >> >> On 2018/01/22 00:22, Mik J wrote: >>> Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson >>> a écrit : >>> On 2018-01-19, Mik J wrote: I had many kernel panic these past days. This is a 6.2 openbsd VM >>> running o= n esxi 5.5 # grep "" /tmp/if_vmx.dis >>> >>> I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. >>> I suggest switching to e1000 in the vmx file, this works with the em(4) >>> driver and has been stable so far. >>> >>> >>> Hello Stuart, >>> Thank you for your answer. >>> I had my VM running for months in version 6.1 and had not problem but I >>> reinstalled it in >>> version 6.2 and the problem is happening. >>> It seems to me that something in version 6.2 is producing the error. >>> One crash today again >> >> I hit this in last April, which was either 6.1 or -current from soon >> after. >> It can take weeks to run into it though so bisecting to find a working >> kernel >> is futile. >> >> > > I am running about a dozen 6.2 -stable VMs on ESXi 6.5. I have exactly > one VM that panics with vmxnet3_getbuf but only when it's being > snapshotted. And not every time, but usually. > > I think once it paniced when I was snapshotting a lot of other VMs in the > cluster but I don't trust that memory now. I've not seen that again. > > Tim. >
Re: Kernel panic with openbsd 6.2
On Thu, January 25, 2018 4:29 am, Maxim Bourmistrov wrote: > As Stuart mentioned, em(4) on top of e1000 proven to be more stable. > Even under higher load. > Vmx starting to misbehave under high load, resulting for ex. with unstable > CARP setup. > > //mxb > >> 25 jan. 2018 kl. 02:40 skrev trondd : >> >> I am running about a dozen 6.2 -stable VMs on ESXi 6.5. I have exactly >> one VM that panics with vmxnet3_getbuf but only when it's being >> snapshotted. And not every time, but usually. >> >> I think once it paniced when I was snapshotting a lot of other VMs in >> the >> cluster but I don't trust that memory now. I've not seen that again. >> >> Tim. >> > I should have also said that these VMs all run postgreSQL servers. The busiest nears 200 simultanious connections which may be well below the load other's are handling on their effected systems. Tim.
Re: Kernel panic with openbsd 6.2
esxi 5.5.0 dates back to 2013. obsd runs better on qemu nowadays. To avoid the mess with x86/amd64, perhaps qemu-sparc with obsd-sparc will serve you better. Sent from ProtonMail Mobile On Fri, Jan 19, 2018 at 21:50, Mik J wrote: > Hello, I had many kernel panic these past days. This is a 6.2 openbsd VM > running on esxi 5.5
Re: Kernel panic with openbsd 6.2
Hello lads, I have about 15 OpenBSD 6.x servers 4x 6.2 servers on Vmware and vmxnet net drivers, Im running on Vmware 6.0 Update 2 ( the earlier vmware 6.0 with out updates was very problmeatic) I dont do much on Snapshots, but I use a LSI Logic Paralell Storage Driver (SCSI) and vmxnet3 I havent encountered any kernel panics (when I create the VM I use the Freebsd 64 Bit OS as the installed OS setting in vmware) and amd64 OpenBSD Im using Vm virtual hardware version 11 the Nics on physical servers are a mix between Broadcom Netxtreme and intel pro 1000 I hope this helps Tom Smyth On 25 January 2018 at 21:08, Rupert Gallagher wrote: > esxi 5.5.0 dates back to 2013. > obsd runs better on qemu nowadays. > To avoid the mess with x86/amd64, > perhaps qemu-sparc with obsd-sparc > will serve you better. > > Sent from ProtonMail Mobile > > On Fri, Jan 19, 2018 at 21:50, Mik J wrote: > >> Hello, I had many kernel panic these past days. This is a 6.2 openbsd VM >> running on esxi 5.5
