linux-kernel - Re: frequent lockups in 3.18rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Dec 2014 17:00:59 -0500
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Chris Mason <clm@...com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Jones <davej@...hat.com>,
	Mike Galbraith <umgwanakikbuti@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Dâniel Fraga <fragabr@...il.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: frequent lockups in 3.18rc4

On 12/11/2014 04:57 PM, Chris Mason wrote:
> On Thu, Dec 11, 2014 at 4:52 PM, Sasha Levin <sasha.levin@...cle.com> wrote:
>> On 12/11/2014 04:49 PM, Linus Torvalds wrote:
>>>  On Thu, Dec 11, 2014 at 6:54 AM, Dave Jones <davej@...hat.com> wrote:
>>>>  >
>>>>  > So either one of those 'good's actually wasn't, or I'm just cursed.
>>>  Even if there was a good that wasn't, that last "bad"  (6f929b4e5a02)
>>>  is already sufficient just on its own to say that likely v3.16 already
>>>  had the problem.
>>>
>>>  Just do
>>>
>>>     gitk v3.16..6f929b4e5a02
>>>
>>>  and cry.
>>>
>>>  (or "git diff --stat -M v3.16...6f929b4e5a02" to see what that commit
>>>  brought in from the common ancestor).
>>>
>>>  So I'd call that bisect a failure, and your "v3.16 is fine" is
>>>  actually suspect after all. Which *might* mean that it's some hardware
>>>  issue after all. Or there are multiple different problems, and while
>>>  v3.16 was fine, the problem was introduced earlier (in the common
>>>  ancestor of that staging tree), then fixed for 3.16, and then
>>>  re-introduced later again.
>>
>> Is it possible that Dave and myself were seeing the same problem after
>> all?
>>
>> I'll go bisect it even further back...
> 
> For both of you, I'm curious how long 3.18 lasts if you turn off the serial console (and netconsole) completely.

I didn't try turning it off, but I tried switching debug level to critical
which meant that nothing was going out. I still saw the same hang...


Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/