Date: Fri, 11 Dec 2009 01:20:08 +0300 From: pluknet <pluknet@gmail.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: jfv@freebsd.org, freebsd-current@freebsd.org Subject: Re: panic with em(4) in current Message-ID: <a31046fc0912101420v2ef8ec17gf9b9105c8128b79@mail.gmail.com> In-Reply-To: <20091210210901.GA23550@lor.one-eyed-alien.net> References: <20091210210901.GA23550@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/12/11 Brooks Davis <brooks@one-eyed-alien.net>: > Something with the latest e1000 update in current causes a panic during > attach on my laptop. Rolling sys/dev/e1000 back to the previous version > fixes the problem. Here's the hand transcribed panic: > > panic: mtx_lock() of spin mutex &dev_spec->swflag_mutex @ ../../../dev/e1000/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: class=0x020000 card=0x20de17aa chip=0x10498086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Gigabit Network Connection Interface Controller (82566MM NIC)' > class = network > subclass = ethernet > > Thanks, > Brooks > -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0912101420v2ef8ec17gf9b9105c8128b79>