Date: Fri, 10 Jun 2011 10:56:06 +0200 From: Bartosz Stec <bartosz.stec@it4pro.pl> To: Andriy Gapon <avg@FreeBSD.org> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org> Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE Message-ID: <4DF1DC26.5010600@it4pro.pl> In-Reply-To: <4DCD1672.4020405@FreeBSD.org> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2011-05-13 13:30, Andriy Gapon pisze: > on 12/05/2011 22:43 Bartosz Stec said the following: >> Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=156974 >> > I suspect that your best course here is to add some diagnostic printfs in > igb_refresh_mbufs and in m_getzone to see what value is actually passed to > m_getjcl and why. > You're probably right, although I would need some guidance how to do it. Sorry :( Yesterday I rebuilt this machine with fresh sources to upgrade filesystem to ZFSv28 which was MFC'ed lately. After that server started to panic regardless of igb loaded as module or integrated into kernel. Finally I found that problem was caused by MSIX somehow. No more panic after hw.pci.enable_msix=0 was included in loader.conf. There's also no panic with GENERIC kernel. Should I really care abou MSIX? -- Bartosz Stec
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DF1DC26.5010600>