From owner-freebsd-stable@FreeBSD.ORG Sat Apr 24 02:29:32 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E5941065672 for ; Sat, 24 Apr 2010 02:29:32 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id E76DB8FC13 for ; Sat, 24 Apr 2010 02:29:31 +0000 (UTC) Received: by qyk11 with SMTP id 11so12326829qyk.13 for ; Fri, 23 Apr 2010 19:29:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5NRGH5Iup/K0uqM75QaiAp0FQXwN01hFsqsOQA/XAog=; b=SRg/IKJK0hlz2zGrP5OPnjHAxJJy7/kC5MMnOgD3jPO+askHVyCbYQfHFqEAviwh62 bcGBReIrsJyMkBA5aKWHGuM6KnndUe+jzliCuMwL3y8Cp00yTjokusuHZVCG0pHzLQ1t wrcSjZwkKY/oGQ2EywmCTuUK29aMZdaGGLCnc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ek5xz+GQQRADBU+usRu8FBIqVJOm60+Wj6ILOwsFNyBto1E+frdWRJPgMgiEEtTpRb D6WsBKUFic6gfZFVsHOWwmEeI/voW+v0R6roLDcnfTsg3nmmIBD3lwF2OHwDL/nJTzQ0 OPC3GlLHjN/NTbaXEZtafXAWF99BOTqxwWcTA= MIME-Version: 1.0 Received: by 10.229.212.213 with SMTP id gt21mr1141742qcb.2.1272076171150; Fri, 23 Apr 2010 19:29:31 -0700 (PDT) Received: by 10.229.233.11 with HTTP; Fri, 23 Apr 2010 19:29:31 -0700 (PDT) In-Reply-To: References: <20100418081400.GA40496@mx.techwires.net> Date: Fri, 23 Apr 2010 19:29:31 -0700 Message-ID: From: Garrett Cooper To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Bernhard Schmidt , freebsd-stable@freebsd.org Subject: Re: iwn firmware instability with an up-to-date stable kernel 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: Sat, 24 Apr 2010 02:29:32 -0000 2010/4/18 Olivier Cochard-Labb=E9 : > 2010/4/18 Bernhard Schmidt : >> Are you able to reproduce this on demand? As in type a few commands and >> the firmware error occurs? >> > > No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type =3D "NMI_INTERRUPT_WDG" (0x00000004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter =3D 0x0000046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line =3D 0x000000D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data =3D 0x000000020703000= 0 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link =3D 0x00008370000004C= 2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link =3D 0x000006DA000018B= 8 Apr 23 19:25:24 garrcoop-fbsd kernel: time =3D 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=3D0 cur=3D1 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=3D1 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=3D2 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3D3 cur=3D36 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=3D4 cur=3D123 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=3D5 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=3D6 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=3D7 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=3D8 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=3D9 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=3D10 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=3D11 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=3D12 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=3D13 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=3D14 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=3D15 cur=3D0 queued= =3D0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=3D8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Thanks, -Garrett