From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Seabios incompatible with Linux 2.6.26 host? Date: Mon, 08 Feb 2010 14:21:24 +0200 Message-ID: <4B7001C4.4080303@redhat.com> References: <4B6C2F2B.4050303@siemens.com> <3D47E453-3C6B-467C-B38C-28FD9EA6C3B4@irisa.fr> <4B6C3448.8010204@siemens.com> <28F324FB-8015-4807-B2A2-FCBC2786A151@irisa.fr> <4B6FF1DB.5060101@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pierre Riteau , KVM list To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8084 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750830Ab0BHMVb (ORCPT ); Mon, 8 Feb 2010 07:21:31 -0500 In-Reply-To: <4B6FF1DB.5060101@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/08/2010 01:13 PM, Jan Kiszka wrote: >> >> I confirm that this exception does not happen with kvm-kmod-2.6.33-rc6. >> >> However, after I run and stop a guest VM just executing the bios sequence (no disk/CD image attached), I get this kind of errors on the host when untar a small archive (less than 1MB, about 300 files): >> >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073865] Bad page state in process 'gzip' >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.073867] page:ffffe200040c4638 flags:0x020000000000001c mapping:0000000000000000 mapcount:0 count:0 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102991] Trying to fix it up, but a reboot is needed >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.102992] Backtrace: >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.129821] Pid: 3559, comm: gzip Tainted: P 2.6.26-2-amd64 #1 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143267] >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.143268] Call Trace: >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.156024] [] hrtick_set+0x88/0xf7 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.167250] [] bad_page+0x6b/0x95 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.179879] [] get_page_from_freelist+0x3e1/0x606 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.195345] [] __alloc_pages_internal+0xd6/0x3bf >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.210580] [] handle_mm_fault+0x244/0x867 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.223694] [] filemap_fault+0x1c2/0x33c >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.237948] [] do_page_fault+0x5d8/0x9c8 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.251793] [] error_exit+0x0/0x60 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.265754] [] file_read_actor+0x52/0x125 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.278595] [] get_page_from_freelist+0x45a/0x606 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.294022] [] generic_file_aio_read+0x29e/0x4ae >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.309319] [] do_sync_read+0xc9/0x10c >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.322816] [] autoremove_wake_function+0x0/0x2e >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.338051] [] do_page_fault+0x5d8/0x9c8 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.351919] [] vfs_read+0xaa/0x152 >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.366108] [] sys_read+0x45/0x6e >> Feb 8 12:00:32 paraquad-7 kernel: [ 200.378750] [] system_call_after_swapgs+0x8a/0x8f >> >> > Haven't seen this before. Can you reproduce it with > > a) kvm-kmod-2.6.32.7? > b) a host kernel>= 2.6.27? > Good guess - perhaps we are busted without mmu notifiers. For b), please ensure CONFIG_MMU_NOTIFIER is enabled in the host kernel configuration. -- error compiling committee.c: too many arguments to function