Date: Fri, 22 May 2009 14:19:42 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Stefan Bethke <stb@lassitu.de> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ifconfig triggers kernel trap on boot Message-ID: <20090522141756.A72053@maildrop.int.zabbadoz.net> In-Reply-To: <8FE57686-E9EE-4118-A0F5-0DBF0B154D27@lassitu.de> References: <746CE32B-BCF8-460A-982D-25341554E8FD@lassitu.de> <4A167B39.2090405@ongs.co.jp> <15095A18-F361-4F8E-8253-0B675C771FC4@lassitu.de> <8FE57686-E9EE-4118-A0F5-0DBF0B154D27@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 May 2009, Stefan Bethke wrote: Hi, >> A kernel compiled from the same sources with practically identical >> configuration (GENERIC minus most devices) running inside VMware (but also >> SMP) does not exhibit this issue. > > Using the failing kernel in VMware triggers the same panic, so it does appear > to be configuration dependant. I'll see what's different between the two > configs. The problem itself has been known for a week and while we had some people seeing it we could not reproduce it ourselves. Thanks for those extra pointers. As you seem to be in my TZ and debugging this, I sent you a private follow-up so we can possibly figure things out to get this fixed. We'll report back to the list once we know more. /bz -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090522141756.A72053>