Date: Wed, 26 Jun 2013 03:19:38 +0200 From: Attilio Rao <attilio@freebsd.org> To: Florian Smeets <flo@smeets.im> Cc: Matthew Fleming <mdf@freebsd.org>, Alexander Motin <mav@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Garrett Cooper <yaneurabeya@gmail.com> Subject: Re: Kernel hangs on reboot on system with 05/2013~06/2013 CURRENT sources Message-ID: <CAJ-FndByQ7B4uK=bxoNKtQppyj1cgSjv%2BRujQ8nCkZue8DAa-w@mail.gmail.com> In-Reply-To: <51CA0B57.8000204@smeets.im> References: <CAGHfRMBRJHsQv=Ma1%2BVHyDHrAMpV=dXa7EU-4VRaYVsEhgeHKg@mail.gmail.com> <51CA0B57.8000204@smeets.im>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 25, 2013 at 11:27 PM, Florian Smeets <flo@smeets.im> wrote: > On 06/25/2013 22:45, Garrett Cooper wrote: >> Long story short is that I've run into an issue on several VM >> images and real machines where UFS on mpt fails to reboot because it >> hangs in the kernel. I don't have any specific details, other than it >> occurs regularly with cam/mpt on VMware boxes running builds; however >> I've also seen this occur with a Dell box that has an mpt SAS >> controller with 2 zpools and gobs of RAM. Does anyone know of any >> issues in this area [recently]? >> This set of issues appears to have started cropping up after >> 03/2013, because I was running reliable builds off those sources. >> Thanks! >> -Garrett >> > > Yes, I saw the same thing today when rebooting a box running r251905: > Tue Jun 18 10:12:42 CEST 2013 with ahci on a zfs only system. > > I update this box about once a week, that previous kernel was from Jun > 11. and that still rebooted successfully. As the kernel from June 18. is > now kernel.old I don't know the SVN rev for the June 11 kernel, but it > looks like it was broken between June 11. and 18. Can you break into KDB once the loop happens? Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-FndByQ7B4uK=bxoNKtQppyj1cgSjv%2BRujQ8nCkZue8DAa-w>