From owner-freebsd-current@FreeBSD.ORG Thu Dec 10 22:20:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28A151065676 for ; Thu, 10 Dec 2009 22:20:13 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 85FEA8FC1B for ; Thu, 10 Dec 2009 22:20:12 +0000 (UTC) Received: by bwz5 with SMTP id 5so237767bwz.3 for ; Thu, 10 Dec 2009 14:20:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6St8hpzYKzvRrH8mti0z9suktkQEvaU3/hPb6QwtG4I=; b=Du4v76ZfN+Uu4LUMAVm5Uh9B0lkohYWhcddUV6Rjy+ECpuBZYH4bjYVLDZ62u6mC57 6BCweVYdKhNMm6UFcBs00AqZF2HhRejwJQj1K9ozg7XH8pDpNcCV+iYCXEGf8Xjh25hj azvgnuB8s/uSjr92ywco406emBawQRxmZG9Zc= 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=MvMKOLN+wl7ZQ14uHkb+0Wrd0n3w0CRKLZy+R3du5EFDzAVxfJ8IXWcolhrH19Hmk1 QoJTJPEO87x37SWIme3rIGdU/lGI1aU7e9mpwCK97gfzwBnwTq3BgGnbpIXsIkrT7ick 5slVK441ZVmgpF8yicg5ThSMy5C4MhmJMoMmw= MIME-Version: 1.0 Received: by 10.204.24.130 with SMTP id v2mr308378bkb.33.1260483608162; Thu, 10 Dec 2009 14:20:08 -0800 (PST) In-Reply-To: <20091210210901.GA23550@lor.one-eyed-alien.net> References: <20091210210901.GA23550@lor.one-eyed-alien.net> Date: Fri, 11 Dec 2009 01:20:08 +0300 Message-ID: From: pluknet To: Brooks Davis Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: jfv@freebsd.org, freebsd-current@freebsd.org Subject: Re: panic with em(4) in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 22:20:13 -0000 2009/12/11 Brooks Davis : > Something with the latest e1000 update in current causes a panic during > attach on my laptop. =A0Rolling sys/dev/e1000 back to the previous versio= n > fixes the problem. =A0Here's the hand transcribed panic: > > panic: mtx_lock() of spin mutex &dev_spec->swflag_mutex @ ../../../dev/e1= 000/e1000_ich8lan.c:651 > > The back trace places me at: e1000_acquire_swflag_ich8lan()+0x30 Hi, I see bug there: +#define E1000_MUTEX_INIT(mutex) mtx_init((mutex), #mutex, \ + MTX_NETWORK_LOCK, \ + MTX_DEF | MTX_SPIN) mtx_init() first looks for MTX_SPIN flag and assign lock_class_mtx_spin class to mutex. Then mtx_lock() on spin mutex called. > > The device in question is in my lenovo x61s laptop and the pciconf > output is: > > em0@pci0:0:25:0: =A0 =A0 =A0 =A0class=3D0x020000 card=3D0x20de17aa chip= =3D0x10498086 rev=3D0x03 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Intel Corporation' > =A0 =A0device =A0 =A0 =3D 'Gigabit Network Connection Interface Controlle= r (82566MM NIC)' > =A0 =A0class =A0 =A0 =A0=3D network > =A0 =A0subclass =A0 =3D ethernet > > Thanks, > Brooks > --=20 wbr, pluknet