Re: "em0: watchdog timeout" with -current

2011-08-01 Thread Tomas Bodzar
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

Re: "em0: watchdog timeout" with -current

2011-07-25 Thread Sevan / Venture37
On 22 July 2011 18:58, Sevan / Venture37 wrote: > On 4 July 2011 21:32, Chris Smith 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 > iss

Re: "em0: watchdog timeout" with -current

2011-07-22 Thread Sevan / Venture37
On 4 July 2011 21:32, Chris Smith 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

Re: "em0: watchdog timeout" with -current

2011-07-04 Thread Chris Smith
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 wrote: >> Between a working kernel and a non-working kernel these two commits to >> the em driver were made: > > Then tell us which i

Re: "em0: watchdog timeout" with -current

2011-07-04 Thread Stuart Henderson
On 2011-07-04, Chris Smith wrote: > On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt > 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; get

Re: "em0: watchdog timeout" with -current

2011-07-03 Thread Ted Unangst
On Sun, Jul 03, 2011, Chris Smith wrote: > On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt > 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 oth

Re: "em0: watchdog timeout" with -current

2011-07-03 Thread Chris Smith
On Sun, Jul 3, 2011 at 8:41 PM, Theo de Raadt 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

2011-07-03 Thread Theo de Raadt
> 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 >

Re: "em0: watchdog timeout" with -current

2011-07-03 Thread Chris Smith
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 messag

Re: "em0: watchdog timeout" with -current

2011-07-03 Thread Chris Smith
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 re

"em0: watchdog timeout" with -current

2011-07-03 Thread Chris Smith
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: ===