Re: [PATCH] Remove if_watchdog use

2009-11-17 Thread John Baldwin
On Sunday 15 November 2009 12:17:57 am WATANABE Kazuhiro wrote: > Hi, > > I've tested the following NICs with your patch on CURRENT, and they > works fine. Thanks! > > * Corega FastEther PCI-TX (DEC 21140-AF) > > de0: port 0xe000-0xe07f mem 0xd9001000-0xd900107f irq 12 at device 15.0 on pci0

Re: [PATCH] Remove if_watchdog use

2009-11-14 Thread WATANABE Kazuhiro
Hi, I've tested the following NICs with your patch on CURRENT, and they works fine. Thanks! * Corega FastEther PCI-TX (DEC 21140-AF) de0: port 0xe000-0xe07f mem 0xd9001000-0xd900107f irq 12 at device 15.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: Ethernet address: 00:00:f4:xx:xx:xx de0:

Re: [PATCH] Remove if_watchdog use

2009-11-10 Thread Gavin Atkinson
On Tue, 10 Nov 2009, John Baldwin wrote: On Tuesday 10 November 2009 4:45:03 pm Gavin Atkinson wrote: I managed to get a panic when running wpa_supplicant: System call ioctl returning with the following locks held: exclusive sleep mutex an0 (network driver) r=0 (0xc58fc180) locked @ /usr/src/sy

Re: [PATCH] Remove if_watchdog use

2009-11-10 Thread Gavin Atkinson
On Fri, 6 Nov 2009, John Baldwin wrote: I have a patchset that converts all the remaining users of if_watchdog to using a private callout instead. In some cases the the driver already used a private timer to drive a stats timer and I merely hooked into that timer. In other cases a new callout

Re: [PATCH] Remove if_watchdog use

2009-11-10 Thread John Baldwin
On Tuesday 10 November 2009 4:45:03 pm Gavin Atkinson wrote: > On Fri, 6 Nov 2009, John Baldwin wrote: > > > I have a patchset that converts all the remaining users of if_watchdog to > > using a private callout instead. In some cases the the driver already used > > a > > private timer to drive a