From mexas@bristol.ac.uk  Wed May 14 13:42:56 2014
Return-Path: <mexas@bristol.ac.uk>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hub.freebsd.org (Postfix) with ESMTPS id 789754FF
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 14 May 2014 13:42:56 +0000 (UTC)
Received: from eu1sys200aog101.obsmtp.com (eu1sys200aog101.obsmtp.com [207.126.144.111])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id C655620E0
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 14 May 2014 13:42:55 +0000 (UTC)
Received: from mail-wi0-f174.google.com ([209.85.212.174]) (using TLSv1) by eu1sys200aob101.postini.com ([207.126.147.11]) with SMTP
	ID DSNKU3Ny2EKxB7Amqj5u+kaFN3TuHi58L3bH@postini.com; Wed, 14 May 2014 13:42:55 UTC
Received: by mail-wi0-f174.google.com with SMTP id r20so8051510wiv.1
        for <FreeBSD-gnats-submit@freebsd.org>; Wed, 14 May 2014 06:42:48 -0700 (PDT)
Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241])
        by mx.google.com with ESMTPSA id z14sm361288wiu.6.2014.05.14.06.37.41
        for <FreeBSD-gnats-submit@freebsd.org>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 14 May 2014 06:37:42 -0700 (PDT)
Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1])
	by mech-cluster241.men.bris.ac.uk (8.14.8/8.14.8) with ESMTP id s4EDbe1u021106
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 14 May 2014 14:37:40 +0100 (BST)
	(envelope-from mexas@mech-cluster241.men.bris.ac.uk)
Received: (from mexas@localhost)
	by mech-cluster241.men.bris.ac.uk (8.14.8/8.14.8/Submit) id s4EDbehe021105;
	Wed, 14 May 2014 14:37:40 +0100 (BST)
	(envelope-from mexas)
Message-Id: <201405141337.s4EDbehe021105@mech-cluster241.men.bris.ac.uk>
Date: Wed, 14 May 2014 14:37:40 +0100 (BST)
From: Anton Shterenlikht <mexas@bris.ac.uk>
Sender: Anton Shterenlikht <mexas@bristol.ac.uk>
Reply-To: Anton Shterenlikht <mexas@bris.ac.uk>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: amd64 current 264294 panic: breakpoint instruction fault, possibly iwn bug 
X-Send-Pr-Version: 3.114
X-GNATS-Notify:

>Number:         189802
>Category:       kern
>Synopsis:       amd64 current 264294 panic: breakpoint instruction fault, possibly iwn bug
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 14 13:50:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Anton Shterenlikht
>Release:        FreeBSD 11.0-CURRENT ia64
>Organization:
>Environment:
System: FreeBSD 11.0-CURRENT #11 r264294: Wed Apr  9 13:38:12 BST 2014
    root@mech-aslap33.men.bris.ac.uk:/usr/obj/usr/src/sys/MINKY amd64

	
>Description:

I'm seeing spontaneous reboots on an amd64 laptop with iwn
card. I haven't enabled a dump partition yet (will try to do),
so all I get is:

Fatal trap 3: breakpoint instruction fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0xffffffff805b173e
stack pointer           = 0x28:0xffffffff81018590
frame pointer           = 0x28:0xffffffff810185b0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = IOPL = 0
current process         = 12 (irq259: iwn0)
trap number             = 3
panic: breakpoint instruction fault
cpuid = 0
KDB: enter: panic

iwn behaves really badly, and disconnects every few minutes
with:

wlan0: Ethernet address: 00:21:5c:50:68:c3
wlan0: link state changed to UP
iwn0: iwn_intr: fatal firmware error
firmware error log:
  error type      = "FH_ERROR" (0x0000000C)
  program counter = 0x0000046C
  source line     = 0x000000D0
  error data      = 0x0000000802730000
  branch link     = 0x0000A332000004C2
  interrupt link  = 0x000006DE0000A37E
  time            = 2607530651
driver status:
  tx ring  0: qid=0  cur=22  queued=12
  tx ring  1: qid=1  cur=0   queued=0
  tx ring  2: qid=2  cur=0   queued=0
  tx ring  3: qid=3  cur=16  queued=0
  tx ring  4: qid=4  cur=81  queued=0
  tx ring  5: qid=5  cur=0   queued=0
  tx ring  6: qid=6  cur=0   queued=0
  tx ring  7: qid=7  cur=0   queued=0
  tx ring  8: qid=8  cur=0   queued=0
  tx ring  9: qid=9  cur=0   queued=0
  tx ring 10: qid=10 cur=0   queued=0
  tx ring 11: qid=11 cur=0   queued=0
  tx ring 12: qid=12 cur=0   queued=0
  tx ring 13: qid=13 cur=0   queued=0
  tx ring 14: qid=14 cur=0   queued=0
  tx ring 15: qid=15 cur=0   queued=0
  rx ring: cur=39
ifa_del_loopback_route: deletion failed: 3
wlan0: link state changed to DOWN
wlan0: Ethernet address: 00:21:5c:50:68:c3
wlan0: link state changed to UP

This is a known problem:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/176104

It is interesting to note that iwn
disconnects a lot at work, and very rarely
at home. I suspect that it is too sensitive
to interference, or something like this.

Anyway, I'll try to provide textdump
if I set it up.

	
>How-To-Repeat:
	
>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted:
