From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Weekes Subject: Re: credit2 domU freeze at "Writing SMBIOS tables ..." Date: Thu, 28 Apr 2011 12:56:16 -0700 Message-ID: <4DB9C660.2040102@nuclearfallout.net> References: <4DADF781.7070004@nuclearfallout.net> <1303815713.1955.20223.camel@elijah> <4DB6F6AF.7060909@nuclearfallout.net> <1303837366.1955.21010.camel@elijah> <4DB727E6.5000208@nuclearfallout.net> <4DB85157.3050406@nuclearfallout.net> <4DB99513.4040404@nuclearfallout.net> <1304008504.25185.2.camel@elijah> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1304008504.25185.2.camel@elijah> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 4/28/2011 9:35 AM, George Dunlap wrote: > Do you have "loglvl=all guest_loglvl=all" on your xen boot command-line? Yes. My line is: kernel /boot/xen-4.2-unstable.gz dom0_mem=1500M dom0_max_vcpus=4 iommu=dom0-passthrough sched=credit loglvl=all guest_loglvl=all com2=115200,8n1 console=com2 (I've also seen an error very similar to what that you're seeing with the extra logging turned off, but under different circumstances, so that one doesn't seem to require it.) -John > -George > > On Thu, 2011-04-28 at 17:25 +0100, John Weekes wrote: >> On 4/28/2011 6:10 AM, George Dunlap wrote: >>> Is this just using credit2, or does it do the same thing under credit1? >> I just re-tested with credit1, and it seems to do the same thing with >> debug=y (on xen-unstable), you're right. >> >> On 4.1 with debug=n and credit1, which is my normal configuration, it >> doesn't appear to happen, or at least didn't happen over the 10 attempts >> that I just made (it could be a rare problem on that setup). I may have >> to do some additional testing with 4.1 credit2, 4.1 debug=y, and >> unstable debug=n, but it's good that you're seeing something >> reproducible on your end, at least (and with debug=y). >> >>> On my box, stubdoms with a 4-vcpu guest on credit1 fail too, with this >>> output on the console: >>> >>> xs_read_watch() -> /local/domain/3/log-throttling /local/domain/3/log-throttling >>> xs_read(/local/domain/3/log-throttling): ENOENT >>> (XEN) HVM3: HVM Loader >>> xs_read_watch() -> /local/domain/0/backend/console/3 be:0x13fb66:3:0x154240 >>> (XEN) HVM3: Detected Xen v4.2-unstable >>> Page fault at linear address 0x10, eip 0x49d9, regs 0x3cfb3c, sp 0x0, >>> our_sp 0x3cfb18, code 0 >>> (XEN) HVM3: Xenbus rings @0xfeffc000, event channel 5 >>> Thread: main >>> (XEN) HVM3: System requested ROMBIOS >>> EIP: 49d9, EFLAGS 10202. >>> (XEN) HVM3: CPU speed is 1995 MHz >>> EBX: 00000000 ECX: 001589b0 EDX: 00000000 >>> ESI: 0000000c EDI: 0000000c EBP: 003cfbb8 EAX: 00000000 >>> DS: e021 ES: e021 orig_eax: ffffffff, eip: 000049d9 >>> CS: e019 EFLAGS: 00010202 esp: 00000000 ss: 3cfba4 >>> base is 0x3cfbb8 caller is 0x24bd3 >>> base is 0x3cfbf8 caller is 0x9814 >>> base is 0x3cfe88 caller is 0xe8e91 >>> base is 0x3cfff0 caller is 0x31ad >>> >>> 3cfba0: 00 00 00 00 28 15 00 00 00 00 00 00 0a 00 00 00 >>> 3cfbb0: 67 96 13 00 e8 fb 3c 00 f8 fb 3c 00 d3 4b 02 00 >>> 3cfbc0: 00 00 00 00 51 e5 01 00 00 00 00 00 00 00 00 00 >>> 3cfbd0: 00 00 00 00 cb 96 13 00 78 94 00 82 03 00 00 00 >>> >>> 49c0: c8 c1 e8 05 83 e1 1f 8b 44 85 ec d3 f8 a8 01 74 >>> 49d0: 0e 8b 43 14 89 04 24 ff d2 83 7b 10 00 75 23 8b >>> 49e0: 53 0c 85 d2 74 1c 8b 0b 89 c8 c1 e8 05 83 e1 1f >>> 49f0: 8b 44 85 e4 d3 f8 a8 01 74 08 8b 43 14 89 04 24 >>> Pagetable walk from virt 10, base 371000: >>> L3 = 00000000b074f027 (0x372000) [offset = 0] >>> L2 = 00000000b074d067 (0x374000) [offset = 0] >>> L1 = 0000000000000000 [offset = 0] >> I'm not seeing that one yet. >> >> -John >