Date: Thu, 15 Jul 2010 18:00:48 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: =?unknown-8bit?Q?St=E5le?= Kristoffersen <staale@kristoffersen.ws> Cc: freebsd-current@freebsd.org Subject: Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm Message-ID: <20100715160048.GA61891@alchemy.franken.de> In-Reply-To: <20100715123423.GC52222@putsch.kolbu.ws> References: <20100715123423.GC52222@putsch.kolbu.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote: > Upgraded to from stable to current yesterday and very quickly received a > panic. It did however not dump it's core, so I was unable to debug it. > Today it did panic again, and I took a picture: (Sorry about the bad > quality) > > http://folk.uio.no/stalk/mpt/IMG_1403.JPG > > And from the backtrace: > http://folk.uio.no/stalk/mpt/IMG_1404.JPG > > Both times I hade the mpt0: request timed out just before the panic. > > I'm not sure why it's not dumping it's core (It was working under stable, > and I have dumpdev="AUTO" and dumpdir="/var/crash" in rc.conf) What revision were you using? Does using current as of r209598 make a difference? Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100715160048.GA61891>