Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754818AbbLERcw (ORCPT ); Sat, 5 Dec 2015 12:32:52 -0500 Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:3670 "EHLO mx0b-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754296AbbLERcv (ORCPT ); Sat, 5 Dec 2015 12:32:51 -0500 Subject: Re: 4.4-rc3, KVM, br0 and instant hang To: John Stoffel , John Stoffel References: <22114.26609.457727.203801@quad.stoffel.home> <20151205162328.GA32532@quad.stoffel.home> <22115.8036.357755.548697@quad.stoffel.home> CC: , , From: Jens Axboe Message-ID: <56631FBC.4030002@fb.com> Date: Sat, 5 Dec 2015 10:32:44 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <22115.8036.357755.548697@quad.stoffel.home> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.54.13] X-Proofpoint-Spam-Reason: safe X-FB-Internal: Safe X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-12-05_17:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1748 Lines: 39 On 12/05/2015 10:31 AM, John Stoffel wrote: >>>>>> "John" == John Stoffel writes: > > John> On Fri, Dec 04, 2015 at 11:28:33PM -0500, John Stoffel wrote: >>> >>> Hi all, > >>> Anyway, if I try to boot up anything past the 4.2.6 kernel, the system >>> locks up pretty quickly with an oops message that scrolls off the >>> screen too far. I've got some pictures which I'll attach in a bit, >>> maybe they'll help. So at first I thought it was something to do with >>> bad kworker threads, or SCSI or SATA interactions, but as I tried to >>> configure Netconsole to log to my beaglebone black SBC, I found out >>> that if I compiled and installed 4.4-rc3, started the bridge up (br0), >>> even started KVM, but did NOT start my VMs, the system was stable. > > I've now figured out that I can disable all my VMs from autostart, and > the system will come up properly. Then I can setup netconsole to use > the br0 interface, do an "echo t > sysrq" to confirm it's working, > and start up the VMs. > > On my most recent bootup, I thought it was ok, since the VMs worked > for a while (10 minutes) and I was starting to re-compile the kernel > again to make more modules compiled in. No luck, I got the following > crash dump (partial) on my netconsole box. > > [ 1434.266524] ------------[ cut here ]------------ > [ 1434.266643] WARNING: CPU: 2 PID: 179 at block/blk-merge.c:435 blk_rq_map_sg+0x2d9/0x2eb() This is fixed in current -git, as of a few days ago. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/