From owner-freebsd-wireless@freebsd.org Sun Aug 23 18:26:46 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64D7D9C1A24 for ; Sun, 23 Aug 2015 18:26:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BD0816C2 for ; Sun, 23 Aug 2015 18:26:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igcse8 with SMTP id se8so32218603igc.1 for ; Sun, 23 Aug 2015 11:26:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RCvnbWj6NkfR5kc8YsDVWYy4/bYYr3p8VvkQ1Wv8FmA=; b=LzGC5SEBd0CmvTDru6qD+B4+OAbtX1KzsuTMZNk2/1gELgYJI0GJaK3QEDYnvp0KJD skMizVJs8iLCykvX3lIFlASH473KQWPqq2dvjFEGkPbgWXf3Yt8UjisPwgrvHx3iNmC5 znfRaFoAsbTnvNry3VpbUiTdn0gKqZeK8H5caSkYvhsLsgCeTcRPvfHeZlYFfJ8tgxrx KXc63dCyKinwCp81UdSWhTA6MDBcFk3GwAeNIr0dXLAs/lrvjS/jHGlVqoroB+F06CfC 46UOS4UAeHPqWk7OZRkOeb5/prD8ESyd2NfcsyIoatgaRHzqgC8QesIb6IT2mSK/+qEi bGIw== MIME-Version: 1.0 X-Received: by 10.50.128.169 with SMTP id np9mr12364165igb.37.1440354405578; Sun, 23 Aug 2015 11:26:45 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Sun, 23 Aug 2015 11:26:45 -0700 (PDT) In-Reply-To: References: <20150819124357.GR4954@e-new.0x20.net> <20150819132523.GV4954@e-new.0x20.net> <1440002356.1200.17.camel@michaeleichorn.com> Date: Sun, 23 Aug 2015 11:26:45 -0700 Message-ID: Subject: Re: X230 Intel Centrino Wireless-N 2200 not working From: Adrian Chadd To: Toby Slight Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2015 18:26:46 -0000 hi! nope - it looks like you had the whole transmit side get out of sync, it threw a seqno != seqno error, then firmware panic. I wish i knew what else was lurking here to cause this :( Does it happen often? -a On 23 August 2015 at 05:56, Toby Slight wrote: > > On 23 August 2015 at 06:26, Adrian Chadd wrote: >> >> email -wireless with some info, and if it's something we can poke, >> file a bug at bugs.freebsd.org/submit >> > > Cool. Well since this is already going to -wireless, here's the exert from > my /var/log/messages. Do you think enabling acpi_ibm or coretemp might have > had anything to do with it? > > Aug 23 00:45:17 xbsd kernel: acpi_ibm0: on acpi0 > Aug 23 00:51:07 xbsd kernel: coretemp0: on cpu0 > Aug 23 00:51:07 xbsd kernel: coretemp1: > Aug 23 00:51:07 xbsd kernel: on cpu1 > Aug 23 00:51:07 xbsd kernel: coretemp2: on cpu2 > Aug 23 00:51:07 xbsd kernel: coretemp3: on cpu3 > Aug 23 00:54:58 xbsd kernel: iwn0: device timeout > Aug 23 00:54:58 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_tx_data: m=0xfffff800105a7b00: seqno > (11604) (84) != ring index (0) ! > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_intr: fatal firmware error > Aug 23 00:55:03 xbsd kernel: firmware error log: > Aug 23 00:55:03 xbsd kernel: error type = "UNKNOWN" (0x0000102C) > Aug 23 00:55:03 xbsd kernel: program counter = 0x0000CEA8 > Aug 23 00:55:03 xbsd kernel: source line = 0x000006A4 > Aug 23 00:55:03 xbsd kernel: error data = 0x000000FE80000000 > Aug 23 00:55:03 xbsd kernel: branch link = 0x0000CDBA0000CDBA > Aug 23 00:55:03 xbsd kernel: interrupt link = 0x0000E1AE00000000 > Aug 23 00:55:03 xbsd kernel: time = 4610402 > Aug 23 00:55:03 xbsd kernel: driver status: > Aug 23 00:55:03 xbsd kernel: tx ring 0: qid=0 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 1: qid=1 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 2: qid=2 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 3: qid=3 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 4: qid=4 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 5: qid=5 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 6: qid=6 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 7: qid=7 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 8: qid=8 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 9: qid=9 cur=14 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 10: qid=10 cur=1 queued=1 > Aug 23 00:55:03 xbsd kernel: tx ring 11: qid=11 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 12: qid=12 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 13: qid=13 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 14: qid=14 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 15: qid=15 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 16: qid=16 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 17: qid=17 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 18: qid=18 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 19: qid=19 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: rx ring: cur=24 > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_panicked: controller panicked, > iv_state = 5; resetting... > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > > I was hoping to have a crash dump to poke at (or at least try and learn how > to poke at), but it seems that despite having dumpdev set to AUTO in > rc.conf, because I don't have sufficient swap space and/or because I'm using > a full ZFS system nothing was saved in /var/crash. > > Is there any other information that might be useful? And is this worth > filing an official bug report about?