Re: em0: watchdog timeout with -current
Tried on new Dell Latitude E6320 with em0 at pci0 dev 25 function 0 Intel 82579LM rev 0x04: msi, address and same result when I want to install 'em0: watchdog timeout -- resetting' so I can't install. It's OpenBSD 5.0-beta (RAMDISK_CD) #21: Sat Jul 30 17:13:09 MDT 2011 On Mon, Jul 25, 2011 at 6:50 PM, Sevan / Venture37 ventur...@gmail.com wrote: On 22 July 2011 18:58, Sevan / Venture37 ventur...@gmail.com wrote: On 4 July 2011 21:32, Chris Smith obsd_m...@chrissmith.org wrote: Breakage happens with revision 1.258 (the MSI one), rev 1.257 and earlier work fine. Thanks to all who helped. Chris I'll try double check on mine next week as I experienced the same issues, I sent a follow up to bugs@ http://marc.info/?l=openbsd-bugsm=131135453411288w=2 So I reverted to if_em.c to rev1.257 rolled a new kernel, indeed this stops the watchdog error messages but interface is still useless, I experience high packet loss any replies which make it through have a very high RTT Sevan dmesg: OpenBSD 5.0-beta (GENERIC.MP) #0: Mon Jul 25 17:34:22 BST 2011 B B r...@t105-1.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4292673536 (4093MB) avail mem = 4164284416 (3971MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0ba0 (48 entries) bios0: vendor Dell Inc. version 1.4.4 date 07/30/2009 bios0: Dell Inc. PowerEdge T105 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP TCPA SLIC SPCR EINJ HEST BERT SSDT ERST SRAT SSDT MCFG HPET APIC BOOT acpi0: wakeup devices PCI0(S5) USB0(S0) P2P0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-7 acpihpet0 at acpi0: 2500 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 1212, 2009.49 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Dual-Core AMD Opteron(tm) Processor 1212, 2009.26 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P2P0) acpiprt2 at acpi0: bus 5 (XVR0) acpiprt3 at acpi0: bus 4 (XVR1) acpiprt4 at acpi0: bus 3 (XVR2) acpiprt5 at acpi0: bus 2 (XVR3) acpicpu0 at acpi0: C3, C2, PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: PWRB cpu0: PowerNow! K8 2009 MHz: speeds: 2000 1800 1000 MHz memory map conflict 0xcff6d000/0x11000 pci0 at mainbus0 bus 0 NVIDIA nForce4 DDR rev 0xa4 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce4 ISA rev 0xf1 nviic0 at pci0 dev 1 function 1 NVIDIA nForce4 SMBus rev 0xa2 iic0 at nviic0 spdmem0 at iic0 addr 0x52: 2GB DDR2 SDRAM ECC PC2-5300CL5 spdmem1 at iic0 addr 0x53: 2GB DDR2 SDRAM ECC PC2-5300CL5 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: apic 2 int 20, version 1.0, legacy support ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa4: apic 2 int 20 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 pciide0 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide0: using apic 2 int 20 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: WDC WD2500SD-01KCC0 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6 wd1 at pciide0 channel 1 drive 0: WDC WD800JD-75MSA3 wd1: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 6 pciide1 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide1: using apic 2 int 20 for native-PCI interrupt atapiscsi0 at pciide1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TSSTcorp, CDRWDVD TS-H493B, D200 ATAPI 5/cdrom removable cd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xf2 pci1 at ppb0 bus 1 vga1 at pci1 dev 8 function 0 ATI ES1000 rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 16 drm0 at radeondrm0 ppb1 at pci0 dev
Re: em0: watchdog timeout with -current
On 22 July 2011 18:58, Sevan / Venture37 ventur...@gmail.com wrote: On 4 July 2011 21:32, Chris Smith obsd_m...@chrissmith.org wrote: Breakage happens with revision 1.258 (the MSI one), rev 1.257 and earlier work fine. Thanks to all who helped. Chris I'll try double check on mine next week as I experienced the same issues, I sent a follow up to bugs@ http://marc.info/?l=openbsd-bugsm=131135453411288w=2 So I reverted to if_em.c to rev1.257 rolled a new kernel, indeed this stops the watchdog error messages but interface is still useless, I experience high packet loss any replies which make it through have a very high RTT Sevan dmesg: OpenBSD 5.0-beta (GENERIC.MP) #0: Mon Jul 25 17:34:22 BST 2011 r...@t105-1.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4292673536 (4093MB) avail mem = 4164284416 (3971MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0ba0 (48 entries) bios0: vendor Dell Inc. version 1.4.4 date 07/30/2009 bios0: Dell Inc. PowerEdge T105 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP TCPA SLIC SPCR EINJ HEST BERT SSDT ERST SRAT SSDT MCFG HPET APIC BOOT acpi0: wakeup devices PCI0(S5) USB0(S0) P2P0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-7 acpihpet0 at acpi0: 2500 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 1212, 2009.49 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Dual-Core AMD Opteron(tm) Processor 1212, 2009.26 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P2P0) acpiprt2 at acpi0: bus 5 (XVR0) acpiprt3 at acpi0: bus 4 (XVR1) acpiprt4 at acpi0: bus 3 (XVR2) acpiprt5 at acpi0: bus 2 (XVR3) acpicpu0 at acpi0: C3, C2, PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: PWRB cpu0: PowerNow! K8 2009 MHz: speeds: 2000 1800 1000 MHz memory map conflict 0xcff6d000/0x11000 pci0 at mainbus0 bus 0 NVIDIA nForce4 DDR rev 0xa4 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce4 ISA rev 0xf1 nviic0 at pci0 dev 1 function 1 NVIDIA nForce4 SMBus rev 0xa2 iic0 at nviic0 spdmem0 at iic0 addr 0x52: 2GB DDR2 SDRAM ECC PC2-5300CL5 spdmem1 at iic0 addr 0x53: 2GB DDR2 SDRAM ECC PC2-5300CL5 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: apic 2 int 20, version 1.0, legacy support ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa4: apic 2 int 20 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 pciide0 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide0: using apic 2 int 20 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: WDC WD2500SD-01KCC0 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6 wd1 at pciide0 channel 1 drive 0: WDC WD800JD-75MSA3 wd1: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 6 pciide1 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide1: using apic 2 int 20 for native-PCI interrupt atapiscsi0 at pciide1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TSSTcorp, CDRWDVD TS-H493B, D200 ATAPI 5/cdrom removable cd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xf2 pci1 at ppb0 bus 1 vga1 at pci1 dev 8 function 0 ATI ES1000 rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 16 drm0 at radeondrm0 ppb1 at pci0 dev 11 function 0 NVIDIA nForce4 PCIE rev 0xf3 pci2 at ppb1 bus 2 bge0 at pci2 dev 0 function 0 Broadcom BCM5722 rev 0x00, BCM5755 C0 (0xa200): apic 2 int 16, address 00:1d:09:22:8a:a6 brgphy0 at bge0 phy 1: BCM5722 10/100/1000baseT PHY, rev. 0 ppb2 at pci0 dev 12 function 0 NVIDIA nForce4 PCIE rev 0xf3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA nForce4 PCIE rev 0xf3 pci4 at ppb3 bus 4 ppb4 at pci0 dev 14 function 0 NVIDIA
Re: em0: watchdog timeout with -current
On 4 July 2011 21:32, Chris Smith obsd_m...@chrissmith.org wrote: Breakage happens with revision 1.258 (the MSI one), rev 1.257 and earlier work fine. Thanks to all who helped. Chris I'll try double check on mine next week as I experienced the same issues, I sent a follow up to bugs@ http://marc.info/?l=openbsd-bugsm=131135453411288w=2
Re: em0: watchdog timeout with -current
On 2011-07-04, Chris Smith obsd_m...@chrissmith.org wrote: On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: Then tell us which it is. B You've got the hardware. A bit above my current skill set. But I'll see what docs I can find to assist in the task. You have already worked out how to see cvs logs; getting the diffs is just as easy. Try the MSI one first.
Re: em0: watchdog timeout with -current
Breakage happens with revision 1.258 (the MSI one), rev 1.257 and earlier work fine. Thanks to all who helped. Chris On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: Between a working kernel and a non-working kernel these two commits to the em driver were made: Then tell us which it is. B You've got the hardware. CVSROOT: B B B /cvs Module name: B src Changes by: B kette...@cvs.openbsd.org B B B B 2011/06/03 07:06:06 Modified files: B B B sys/dev/pci B B : if_em.c Log message: Fix em_write_pci_cfg() and em_read_pci_cfg() to avoid unaligned access, and make em_write_pci_cfg() do a proper read/modify/write cycle, to avoid changing the neighbouring 16 bits. B Also remove the comment in em_pci_set_mwi() and em_pci_clear_mwi(); writting 0 to the status bits in the command/status word is the right thing to do. B Fixes a panic on sparc64 and other strict alignment architectures. ok deraadt@ CVSROOT: B B B /cvs Module name: B src Changes by: B kette...@cvs.openbsd.org B B B B 2011/06/16 07:21:00 Modified files: B B B sys/dev/pci B B : if_em.c Log message: Enable MSI on newish PCIe hardware, essentially everything handled by the Linux e1000e driver (which enables MSI as well), leaving everything handled by the old Linux e1000 driver (which doesn't enable MSI) use legacy interrupts. tested by many; ok jsg@ Have no idea if it is a driver issue but if it is this info. might assist. Thanks, Chris On Sun, Jul 3, 2011 at 5:08 PM, Chris Smith obsd_m...@chrissmith.org wrote: System is hanging and I'm getting these errors after upgrading to -current: == em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting == I can still boot and run with the old kernel but the new one is not working. From dmesg: == bios0 at mainbus0: AT/286+ BIOS, date 06/27/03, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfc940 (62 entries) bios0: vendor Intel Corp. version LY84510A.86A.0043.P17.0306270645 date 06/27/2003 bios0: Intel Corporation D845GLAD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC ASF! acpi0: wakeup devices P0P1(S4) UAR1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) AC97(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpicpu0 at acpi0 acpipwrres0 at acpi0: URP1 acpipwrres1 at acpi0: URP2 acpipwrres2 at acpi0: FDDP acpipwrres3 at acpi0: LPTP acpibtn0 at acpi0: SLPB snip em0 at pci1 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: apic 1 int 18, address 00:07:e9:01:67:1b ==
em0: watchdog timeout with -current
System is hanging and I'm getting these errors after upgrading to -current: == em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting == I can still boot and run with the old kernel but the new one is not working. From dmesg: == bios0 at mainbus0: AT/286+ BIOS, date 06/27/03, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfc940 (62 entries) bios0: vendor Intel Corp. version LY84510A.86A.0043.P17.0306270645 date 06/27/2003 bios0: Intel Corporation D845GLAD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC ASF! acpi0: wakeup devices P0P1(S4) UAR1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) AC97(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpicpu0 at acpi0 acpipwrres0 at acpi0: URP1 acpipwrres1 at acpi0: URP2 acpipwrres2 at acpi0: FDDP acpipwrres3 at acpi0: LPTP acpibtn0 at acpi0: SLPB snip em0 at pci1 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: apic 1 int 18, address 00:07:e9:01:67:1b ==
Re: em0: watchdog timeout with -current
Adding that this box has been running OpenBSD for years. Pretty standard hardware, Intel chipset, Intel NIC's (Intel branded board) with nary a problem until now. The partial dmesg is from a 5-7-11 -current kernel build, which works fine as did every other kernel build before it, the two I built recently (7-2-11 and 7-3-11) do not work due to the em0 errors and the box quickly becomes non-responsive (needs a hard reset). May be related to the report on this list on 6-24-11 titled Recent i386 snapshot--em0 and em1 watchdog timeout--resetting, and/or on 7-22-11 titled Watchdog timeout on Marvell Yukon 88E8053 (driver msk, 4.9-release). Chris On Sun, Jul 3, 2011 at 5:08 PM, Chris Smith obsd_m...@chrissmith.org wrote: System is hanging and I'm getting these errors after upgrading to -current: == em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting == I can still boot and run with the old kernel but the new one is not working. From dmesg: == bios0 at mainbus0: AT/286+ BIOS, date 06/27/03, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfc940 (62 entries) bios0: vendor Intel Corp. version LY84510A.86A.0043.P17.0306270645 date 06/27/2003 bios0: Intel Corporation D845GLAD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC ASF! acpi0: wakeup devices P0P1(S4) UAR1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) AC97(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpicpu0 at acpi0 acpipwrres0 at acpi0: URP1 acpipwrres1 at acpi0: URP2 acpipwrres2 at acpi0: FDDP acpipwrres3 at acpi0: LPTP acpibtn0 at acpi0: SLPB snip em0 at pci1 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: apic 1 int 18, address 00:07:e9:01:67:1b ==
Re: em0: watchdog timeout with -current
Between a working kernel and a non-working kernel these two commits to the em driver were made: CVSROOT:/cvs Module name:src Changes by: kette...@cvs.openbsd.org2011/06/03 07:06:06 Modified files: sys/dev/pci: if_em.c Log message: Fix em_write_pci_cfg() and em_read_pci_cfg() to avoid unaligned access, and make em_write_pci_cfg() do a proper read/modify/write cycle, to avoid changing the neighbouring 16 bits. Also remove the comment in em_pci_set_mwi() and em_pci_clear_mwi(); writting 0 to the status bits in the command/status word is the right thing to do. Fixes a panic on sparc64 and other strict alignment architectures. ok deraadt@ CVSROOT:/cvs Module name:src Changes by: kette...@cvs.openbsd.org2011/06/16 07:21:00 Modified files: sys/dev/pci: if_em.c Log message: Enable MSI on newish PCIe hardware, essentially everything handled by the Linux e1000e driver (which enables MSI as well), leaving everything handled by the old Linux e1000 driver (which doesn't enable MSI) use legacy interrupts. tested by many; ok jsg@ Have no idea if it is a driver issue but if it is this info. might assist. Thanks, Chris On Sun, Jul 3, 2011 at 5:08 PM, Chris Smith obsd_m...@chrissmith.org wrote: System is hanging and I'm getting these errors after upgrading to -current: == em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting == I can still boot and run with the old kernel but the new one is not working. From dmesg: == bios0 at mainbus0: AT/286+ BIOS, date 06/27/03, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfc940 (62 entries) bios0: vendor Intel Corp. version LY84510A.86A.0043.P17.0306270645 date 06/27/2003 bios0: Intel Corporation D845GLAD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC ASF! acpi0: wakeup devices P0P1(S4) UAR1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) AC97(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpicpu0 at acpi0 acpipwrres0 at acpi0: URP1 acpipwrres1 at acpi0: URP2 acpipwrres2 at acpi0: FDDP acpipwrres3 at acpi0: LPTP acpibtn0 at acpi0: SLPB snip em0 at pci1 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: apic 1 int 18, address 00:07:e9:01:67:1b ==
Re: em0: watchdog timeout with -current
Between a working kernel and a non-working kernel these two commits to the em driver were made: Then tell us which it is. You've got the hardware. CVSROOT: /cvs Module name: src Changes by: kette...@cvs.openbsd.org2011/06/03 07:06:06 Modified files: sys/dev/pci: if_em.c Log message: Fix em_write_pci_cfg() and em_read_pci_cfg() to avoid unaligned access, and make em_write_pci_cfg() do a proper read/modify/write cycle, to avoid changing the neighbouring 16 bits. Also remove the comment in em_pci_set_mwi() and em_pci_clear_mwi(); writting 0 to the status bits in the command/status word is the right thing to do. Fixes a panic on sparc64 and other strict alignment architectures. ok deraadt@ CVSROOT: /cvs Module name: src Changes by: kette...@cvs.openbsd.org2011/06/16 07:21:00 Modified files: sys/dev/pci: if_em.c Log message: Enable MSI on newish PCIe hardware, essentially everything handled by the Linux e1000e driver (which enables MSI as well), leaving everything handled by the old Linux e1000 driver (which doesn't enable MSI) use legacy interrupts. tested by many; ok jsg@ Have no idea if it is a driver issue but if it is this info. might assist. Thanks, Chris On Sun, Jul 3, 2011 at 5:08 PM, Chris Smith obsd_m...@chrissmith.org wrote: System is hanging and I'm getting these errors after upgrading to -current: == em0: watchdog timeout -- resetting em0: watchdog timeout -- resetting == I can still boot and run with the old kernel but the new one is not working. From dmesg: == bios0 at mainbus0: AT/286+ BIOS, date 06/27/03, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.3 @ 0xfc940 (62 entries) bios0: vendor Intel Corp. version LY84510A.86A.0043.P17.0306270645 date 06/27/2003 bios0: Intel Corporation D845GLAD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC ASF! acpi0: wakeup devices P0P1(S4) UAR1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) AC97(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpicpu0 at acpi0 acpipwrres0 at acpi0: URP1 acpipwrres1 at acpi0: URP2 acpipwrres2 at acpi0: FDDP acpipwrres3 at acpi0: LPTP acpibtn0 at acpi0: SLPB snip em0 at pci1 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: apic 1 int 18, address 00:07:e9:01:67:1b ==
Re: em0: watchdog timeout with -current
On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: Then tell us which it is. B You've got the hardware. A bit above my current skill set. But I'll see what docs I can find to assist in the task.
Re: em0: watchdog timeout with -current
On Sun, Jul 03, 2011, Chris Smith wrote: On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: Then tell us which it is. B You've got the hardware. A bit above my current skill set. But I'll see what docs I can find to assist in the task. You can't backout one change and then the other? The docs you are looking for can be found by running man cvs.
