From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 11:24:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2E8216A412 for ; Wed, 27 Sep 2006 11:24:21 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (tandgrisner.ismobile.com [213.88.244.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C12243D46 for ; Wed, 27 Sep 2006 11:24:20 +0000 (GMT) (envelope-from goran.lowkrantz@ismobile.com) Received: from [172.16.2.106] (viglaf.hq.ismobile.com [172.16.2.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTP id 1EAD422940 for ; Wed, 27 Sep 2006 13:24:16 +0200 (CEST) Message-ID: <451A5F5F.6050900@ismobile.com> Date: Wed, 27 Sep 2006 13:24:15 +0200 From: glz Organization: isMobile AB User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927094509.GB75104@hugo10.ka.punkt.de> <20060927110820.GD75104@hugo10.ka.punkt.de> In-Reply-To: <20060927110820.GD75104@hugo10.ka.punkt.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 11:24:21 -0000 I have seen the watchdog and reset problem on a -STABLE laptop, both em and iwi. It only occur when I try to connect using Mulberry e-mail client so I thought it could be a problem with the linuxilator. The load on the box is normally low but both driver have shared interrupts, either with cbb or usb. Here is what I can see: uname -a: FreeBSD viglaf 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #55: Thu Sep 21 22:15:38 CEST 2006 root@viglaf:/usr/obj/usr/src/sys/VIGLAF i386 dmesg: em0: port 0x8000-0x803f mem 0xc0220000-0xc023ffff,0xc0200000-0xc020ffff irq 11 at device 1.0 on pci2 em0: Ethernet address: 00:0d:60:89:36:e8 em0: [FAST] iwi0: mem 0xc0214000-0xc0214fff irq 9 at device 2.0 on pci2 iwi0: Ethernet address: 00:16:6f:8b:0a:21 vmstat -i interrupt total rate irq0: clk 11148090 999 irq1: atkbd0 32271 2 irq5: pcm0 atapci+ 157115 14 irq6: fdc0 1 0 irq7: 1 0 stray irq7 1 0 irq8: rtc 1426745 127 irq9: cbb1 cbb2++* 26582 2 irq11: cbb0 em0++* 762544 68 irq12: psm0 516858 46 irq14: ata0 43494 3 irq15: ata1 82 0 Total 14113784 1265 This is a development machine so I can debug and test patches as needed. Best regards, Goran L Patrick M. Hausen wrote: > Hello! > >> On -stable occasionally other people complained about very similar >> looking problems with bge and other drivers. My guess is, though >> I'm not a kernel developer, just an experienced admin, that >> em stands out as problematic just by coincidence. Certain onboard >> network components tend to come with certaiin chipsets and certain >> architectures. > > I forgot to mention: we do have systems with em interfaces that > never showed this problem! > > Regards, > Patrick -- ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ...............................................