Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Jun 2013 10:43:49 +0200
From:      Florian Smeets <flo@smeets.im>
To:        attilio@FreeBSD.org
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:  <51CBFB45.6090107@smeets.im>
In-Reply-To: <CAJ-FndByQ7B4uK=bxoNKtQppyj1cgSjv%2BRujQ8nCkZue8DAa-w@mail.gmail.com>
References:  <CAGHfRMBRJHsQv=Ma1%2BVHyDHrAMpV=dXa7EU-4VRaYVsEhgeHKg@mail.gmail.com> <51CA0B57.8000204@smeets.im> <CAJ-FndByQ7B4uK=bxoNKtQppyj1cgSjv%2BRujQ8nCkZue8DAa-w@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On 26.06.13 03:19, Attilio Rao wrote:
> 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?
> 

I cannot reproduce on kernels from yesterday/today. So for me the case
is closed.

Florian


[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJRy/tGAAoJECrpj4KP8Zz/SrAH/231lcW9Ds4sWrL/vumWIvy7
OUhrkFjaq7NtlSgJcOvmg2sPWOMIU+i7Ap+kp07GiteVWR68f2GF1X2E0LGQ/kCf
O/TqBNDnDTenmfGSqcFmbo+U+aOZwHPORJxKnu+1P4urfXrxn7GnkBLLeE+xlUOc
LCUsOI5tabrXbAKbEN8raa341g50DJOLzfLvP+n74f0nNjIf6dEhm5SfddFGRly3
nqOIH61KSQTBtq8UZqZ/MIwUHC7t0pe8PgJgxuR4gFb40dJbpEqHnKzB24OWTi8n
mj/hYtyFPzK3eg4BCqP3b8jd25zOW6HwR2zc3KzFe29SW87qHjcTvTZnl9kflk8=
=QaYh
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51CBFB45.6090107>