Re: Watchdog timeout reset in 5.1 on intel nic:s
Problem seems to be found A change of int intr_shared_edge; to int intr_shared_edge = 1; in i386/machdep.c plus kernel recompile solves the problem. Can you post the dmesg of this fixed kernel?
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 23 maj 2012, at 10:14, Mark Kettenis wrote: Problem seems to be found A change of int intr_shared_edge; to int intr_shared_edge = 1; in i386/machdep.c plus kernel recompile solves the problem. Can you post the dmesg of this fixed kernel? Hi Of course The hardware is all cases are exactly the same. This is from the working 4.9 stable: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-4.9i386-stable+patches-to-20110819_running_in_KVM.txt This is from the new 5.1 stable that is NOT working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-5.1i386-stable-patches-to-20120510-not-working_running_in_KVM.txt http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/KVM_ Screenshot_5.1_stable+patches-to-may-8-2012.png This is from the fixed 5.1 that is working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-bsd-5.1-stable_plus_if_em.c-1.252_plus_machdep.c-mod (Note that this works with the 5.1 stable if_em.c as wel (i.e 1.261).) Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
From: =?iso-8859-1?Q?Per-Olov_Sj=F6holm?= p...@incedo.org Date: Wed, 23 May 2012 11:27:34 +0200 On 23 maj 2012, at 10:14, Mark Kettenis wrote: Problem seems to be found A change of int intr_shared_edge; to int intr_shared_edge = 1; in i386/machdep.c plus kernel recompile solves the problem. Can you post the dmesg of this fixed kernel? Hi Of course The hardware is all cases are exactly the same. This is from the working 4.9 stable: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmesg-4.9i386-stable+patches-to-20110819_running_in_KVM.txt This is from the new 5.1 stable that is NOT working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmesg-5.1i386-stable-patches-to-20120510-not-working_running_in_KVM.txt http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/KVM_Screenshot_5.1_stable+patches-to-may-8-2012.png This is from the fixed 5.1 that is working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmesg-bsd-5.1-stable_plus_if_em.c-1.252_plus_machdep.c-mod (Note that this works with the 5.1 stable if_em.c as wel (i.e 1.261).) What happens if you disable uhci in a unmodified 5.1 kernel?
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 23 maj 2012, at 16:29, Mark Kettenis wrote: From: =?iso-8859-1?Q?Per-Olov_Sj=F6holm?= p...@incedo.org Date: Wed, 23 May 2012 11:27:34 +0200 On 23 maj 2012, at 10:14, Mark Kettenis wrote: Problem seems to be found A change of int intr_shared_edge; to int intr_shared_edge = 1; in i386/machdep.c plus kernel recompile solves the problem. Can you post the dmesg of this fixed kernel? Hi Of course The hardware is all cases are exactly the same. This is from the working 4.9 stable: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-4.9i386-stable+patches-to-20110819_running_in_KVM.txt This is from the new 5.1 stable that is NOT working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-5.1i386-stable-patches-to-20120510-not-working_running_in_KVM.txt http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/KVM_ Screenshot_5.1_stable+patches-to-may-8-2012.png This is from the fixed 5.1 that is working: http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-bsd-5.1-stable_plus_if_em.c-1.252_plus_machdep.c-mod (Note that this works with the 5.1 stable if_em.c as wel (i.e 1.261).) What happens if you disable uhci in a unmodified 5.1 kernel? Both interfaces stopped working! But that was tried before I made this change in machdep.c Per-Olov -- GPG keyID: 5231C0C4 GPG fingerprint: B232 3E1A F5AB 5E10 7561 6739 766E D29D 5231 C0C4
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 19 maj 2012, at 20:09, Per-Olov Sjvholm wrote: On 19 maj 2012, at 17:58, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 04:40:08PM +0200, Per-Olov SjC6holm wrote: On 19 maj 2012, at 08:11, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a fresh 5.1 rel plus stable patches. No upgrade... What happened before you applied the stable patches? On the fresh 5.1 release without any changes, that is... -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st That i have not tried.. Per-Olov Problem seems to be found A change of int intr_shared_edge; to int intr_shared_edge = 1; in i386/machdep.c plus kernel recompile solves the problem. This seems to have changed between the working and non working kernels... http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/i386/machdep.c.diff?f =hr1=texttr1=1.487r2=texttr2=1.506 Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Fri, May 18, 2012 at 11:11:07PM -0700, Garry Dolley wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I find it very hard to credit that the network card would behave differently in the upgrade and install cases. Both install the exact same new kernel, wherein the drivers reside. Ken
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 19 maj 2012, at 16:31, Kenneth R Westerback kwesterb...@rogers.com wrote: On Fri, May 18, 2012 at 11:11:07PM -0700, Garry Dolley wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I find it very hard to credit that the network card would behave differently in the upgrade and install cases. Both install the exact same new kernel, wherein the drivers reside. Ken +1 Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 19 maj 2012, at 08:11, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a fresh 5.1 rel plus stable patches. No upgrade... Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Sat, May 19, 2012 at 04:40:08PM +0200, Per-Olov Sjvholm wrote: On 19 maj 2012, at 08:11, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a fresh 5.1 rel plus stable patches. No upgrade... What happened before you applied the stable patches? On the fresh 5.1 release without any changes, that is... -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 19 maj 2012, at 17:58, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 04:40:08PM +0200, Per-Olov SjC6holm wrote: On 19 maj 2012, at 08:11, Garry Dolley gdol...@arpnetworks.com wrote: On Sat, May 19, 2012 at 01:54:54AM +0200, Per-Olov Sjvholm wrote: On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? I don't have any clues. I wasn't able to reproduce the problem, even though one customer I have who also upgraded experienced this behavior. They did not do a fresh install (that I'm aware), but upgraded (similar to you). I'm not sure what the previous version was. They have one NIC and I believe run amd64. The only difference that I can see is that on a fresh 5.1 install, there is no issue. But if you upgrade from a previous release, then the issue *might* appear. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a fresh 5.1 rel plus stable patches. No upgrade... What happened before you applied the stable patches? On the fresh 5.1 release without any changes, that is... -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st That i have not tried.. Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 17 maj 2012, at 12:53, Garry Dolley wrote: On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st I have a running 4.9 release + patches ( i.e 4.9 stable) working perfect. When Updated to 5.1 release + patches I have real problems with watchdog timeout resets on my intel nic:s. Same hardware, but just different OpenBSD version. I have tried a bunch of kernels from Stuart Henderson (Broken after 4.9.). I have also recompiled the 5.1 stable kernel with most versions of the if_em.c driver. I have compiled and tried the following... (note that the userland was 5.1 stable with all kernel tests) bsd-5.1-stable bsd-5.1-stable_plus_if_em.c-1.249 bsd-5.1-stable_plus_if_em.c-1.250 bsd-5.1-stable_plus_if_em.c-1.251 bsd-5.1-stable_plus_if_em.c-1.252 bsd-5.1-stable_plus_if_em.c-1.253 bsd-5.1-stable_plus_if_em.c-1.254 bsd-5.1-stable_plus_if_em.c-1.263 Watchdog timeout resets on all versions. NOTE that the Watchdog timeout reset appears in version 1.249 of if_em.c as well. And that version is default in 4.9 stable which works fantastic. So if I haven't done anything totally wrong it must be related to something else in the kernel. So my nic hardware and the kvm bios is the same. And an if_em.c version that works in 4.9 is tried. I can see above that you got rid of the problem by testing the same version as me.. But you use AMD and I use i386. Also... I have a firewall with 2 nic:s. Often ONE nic works but the other gives watchdog timeout resets and wont work. Any clues? Tnx Per-Olov
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. One post by maxim reported the problem on 5.0, so I was being thorough. Starting with 5.0, and going up... I am going to try a 5.1 stock install tonight and work up to -current. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Thu, May 17, 2012 at 03:19:07AM -0700, Garry Dolley wrote: On Fri, May 11, 2012 at 09:13:30AM -0400, Simon Perreault wrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. I now have a stock 5.1 test VM set up. OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC I don't see any timeouts. I grabbed the ports tree via curl several times and have been slaving away at it over SSH. I don't notice anything wrong. So, perhaps this issue does not appear in stock 5.1, but in a newer kernel. I'll try something newer soon... I have tried the following newer kernels: bsd.20120330 bsd.20120419 bsd.20120427 bsd.20120516 I still can't reproduce the problem. I have disabled mpbios on all these kernels, forgot to mention that. I will leave this be for now; will pick it up again if any new information should arise. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
I've had the same problem with a KVM, maybe worth a note in the install docs? -- p On May 11, 2012, at 19:05, Per-Olov Sjvholm p...@incedo.org wrote: On 11 maj 2012, at 11:16, Stuart Henderson wrote: On 2012/05/11 01:15, Garry Dolley wrote: On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them. Guys, I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Hmm - Mar 28 is already after 5.1 was released. Could somebody seeing the problem (sperreault?) please send a dmesg from a kernel showing the problem? Hi Stuart Here is a dmesg on 4.9 where it's working and on 5.1 when it's not working. http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/ Note that both are virtual OpenBSDs running on the exact same KVM host version and use the same bios etc. Regards P-O -- GPG keyID: 5231C0C4 GPG fingerprint: B232 3E1A F5AB 5E10 7561 6739 766E D29D 5231 C0C4 I had this once back in the day, not sure which release but it was mid-4-point-something. It turned out to be the presence of my external real-hardware (IO-GEAR) KVM switch's - internal - USB HUB monkeying detection of the upstream real USB keyboard. Once a keyboard was direct connected, then everything was fine. Perhaps your real- and/or pseudo- hardware (and firmware/bios) chain is impairing similarly. Good luck,
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them. Guys, I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 2012/05/11 01:15, Garry Dolley wrote: On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them. Guys, I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Hmm - Mar 28 is already after 5.1 was released. Could somebody seeing the problem (sperreault?) please send a dmesg from a kernel showing the problem?
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. Simon
Re: Watchdog timeout reset in 5.1 on intel nic:s
I see the same issue on the most recent snapshot. Upgrading to current, disabling mpbios, and applying mikeb's patch[1] on tech@ and things are looking a lot better. bsd.rd has never exhibited this issue for me FWIW [1] http://marc.info/?l=openbsd-techm=133665750315650w=2 On Fri, May 11, 2012 at 2:13 PM, Simon Perreault sperrea...@openbsd.orgwrote: On 2012-05-11 04:15, Garry Dolley wrote: I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. That's expected. 5.0 has been running without issue for me for a long time. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Why not just test 5.1? Problems have been reported against 5.1, not -current. Simon
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 11 maj 2012, at 11:16, Stuart Henderson wrote: On 2012/05/11 01:15, Garry Dolley wrote: On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them. Guys, I now have an amd64 test VM set up, where I installed stock 5.0. I ran a lot of traffic over em0 without any timeouts. I also have been trying several -current kernels. As of: OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 I don't see any em0 timeouts. I will continue to try newer ones and report back here... Hmm - Mar 28 is already after 5.1 was released. Could somebody seeing the problem (sperreault?) please send a dmesg from a kernel showing the problem? Hi Stuart Here is a dmesg on 4.9 where it's working and on 5.1 when it's not working. http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/ Note that both are virtual OpenBSDs running on the exact same KVM host version and use the same bios etc. Regards P-O -- GPG keyID: 5231C0C4 GPG fingerprint: B232 3E1A F5AB 5E10 7561 6739 766E D29D 5231 C0C4
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 05/10/2012 09:14 AM, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. I see this on 5.0-stable as well (one so far). //maxim
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Thu, May 10, 2012 at 1:18 PM, mxb m...@alumni.chalmers.se wrote: On 05/10/2012 09:14 AM, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. I see this on 5.0-stable as well (one so far). //maxim FWIW, I have a VPS from ARP running amd64 5.0-stable that is working just fine. I was looking forward to possibly not having to disable mpbios with 5.1... Included dmesg and pcidump below, apologies in advance for the crappy formatting. --david # OpenBSD 5.0-stable (GENERIC) #2: Wed Nov 30 11:46:44 EST 2011 root@vm.localdomain:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 267321344 (254MB) avail mem = 246370304 (234MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbd3f (10 entries) bios0: vendor QEMU version QEMU date 01/01/2007 acpi0 at bios0: rev 0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 mpbios at bios0 not configured vmt0 at mainbus0 vmware: open failed, eax=564d5868, ecx=001e, edx=5658 vmt0: failed to open backdoor RPC channel (TCLO protocol) cpu0 at mainbus0: (uniprocessor) cpu0: QEMU Virtual CPU version 0.9.1, 2667.18 MHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MM X,FXSR,SSE,SSE2,SSE3,NXE,LONG cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 82441FX rev 0x02 pcib0 at pci0 dev 1 function 0 Intel 82371SB ISA rev 0x00 pciide0 at pci0 dev 1 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: QEMU HARDDISK wd0: 16-sector PIO, LBA48, 5632MB, 11534336 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: QEMU, QEMU DVD-ROM, 0.9. ATAPI 5/cdrom removable wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 cd0(pciide0:0:1): using PIO mode 0 atapiscsi1 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi1: 2 targets cd1 at scsibus1 targ 0 lun 0: QEMU, QEMU DVD-ROM, 0.9. ATAPI 5/cdrom removable cd1(pciide0:1:0): using PIO mode 0 uhci0 at pci0 dev 1 function 2 Intel 82371SB USB rev 0x01: irq 11 piixpm0 at pci0 dev 1 function 3 Intel 82371AB Power rev 0x03: irq 10 iic0 at piixpm0 iic0: addr 0x4c 48=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x4e 48=00 words 00= 01= 02= 03= 04= 05= 06= 07= vga1 at pci0 dev 2 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 3 function 0 Intel PRO/1000MT (82540EM) rev 0x03: irq 11, address 52:54:00:27:27:15 Qumranet Virtio Memory rev 0x00 at pci0 dev 4 function 0 not configured Qumranet Virtio Console rev 0x00 at pci0 dev 5 function 0 not configured isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 nvram: invalid checksum mtrr: Pentium Pro MTRR support vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on wd0a (76f03dc8be45c6fe.a) swap on wd0b dump on wd0b clock: unknown CMOS layout Domain /dev/pci0: 0:0:0: Intel 82441FX 0x: Vendor ID: 8086 Product ID: 1237 0x0004: Command: Status ID: 0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 02 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00 0x0010: BAR empty () 0x0014: BAR empty () 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1af4
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 10 maj 2012, at 19:18, mxb wrote: On 05/10/2012 09:14 AM, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. I see this on 5.0-stable as well (one so far). //maxim Ok something must have happen since 4.9. My virtual OpenBSD 4.9 run perfect. When trying 5.1 I use the same physical nics and the same KVM host and version (i.e same bios etc). Could it be the em driver or kernel itself ? I will go through the em cvs Hm. Could version 1.262 from http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_em.c be related to this issue? Tnx Peo -- GPG keyID: 5231C0C4 GPG fingerprint: B232 3E1A F5AB 5E10 7561 6739 766E D29D 5231 C0C4 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Watchdog timeout reset in 5.1 on intel nic:s
In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them.
Re: Watchdog timeout reset in 5.1 on intel nic:s
On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: In gmane.os.openbsd.misc, Garry Dolley wrote: On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon I had another customer on amd64 report this problem today. Not sure what the solution is. I'm recommending either downgrade to 5.0 or use i386 arch for now. If possible, tracking down the commit which broke it, or at least narrow it to a reasonably small date range, would help. I have an archive of snapshot kernels if you want to work through them rather than cvs checkouts, contact me if you'd like access to them. I will take you up on this and post the results back here. -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st
Watchdog timeout reset in 5.1 on intel nic:s
Hi I have an OpenBSD 4.9 i386 stable (patched to aug 19 2011) running as virtual in KVM with VTd (PCI passthrough by using pci-stub) for two intel NICs. It's running flawless. The KVM host (fully patched Redhat 6.2) have two extra Intel PRO/1000 MT (82574L) that is given out to the OpenBSD virtual host. The OpenBSD virtual host sees and uses the physical nic:s directly. As said, it run flawless The working solution dmesg can be seen here http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/dmes g-4.9i386-stable+patches-to-20110819_running_in_KVM.txt Now... I wanted to upgrade to OpenBSD 5.1. I installed a new virtual OpenBSD 5.1 i386 stable. I patched it to may 8 2012. When I run it, I cannot get any traffic through it and the console says what can be seen here in this png screenshot... http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/KVM_ Screenshot_5.1_stable+patches-to-may-8-2012.png It says em1: watchdog timeout -- resetting more info... - mpbios is disabled on both OpenBSD installations as the KVM shutdown wont work on the virtual host otherwise... - Uses uniprocessor kernel as I have measured it gives better throughput than MP Any suggestions of where to look for a possible solution would be very much appreciated. Tnx in advance P-O
Re: Watchdog timeout reset in 5.1 on intel nic:s
On 2012-05-08 19:08, Per-Olov Sjvholm wrote: It says em1: watchdog timeout -- resetting aol I saw the same on an amd64 VPS from arpnetworks.com. Network was not functional. Backed out. Did not investigate further. /aol Simon
