From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [linux test] 2107: regressions - FAIL Date: Fri, 10 Sep 2010 01:53:08 +1000 Message-ID: <4C8902E4.2080203@goop.org> References: <19592.64988.663360.787159@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19592.64988.663360.787159@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 09/10/2010 01:31 AM, Ian Jackson wrote: > Ian Jackson writes ("[linux test] 2107: regressions - FAIL"): >> flight 2107 xen-4.0-testing real >> http://www.chiark.greenend.org.uk/~xensrcts/logs/2107/ >> >> Regressions :-( >> >> tests which did not succeed: >> test-amd64-i386-pair 7 xen-boot/dst_host fail REGR. vs. 2057 >> test-i386-i386-pair 7 xen-boot/dst_host fail REGR. vs. 2057 > This seems to be a real failure. The problem is that the first boot > of the host with Xen and a dom0 pvops kernel hangs. But only one one > of the two machines I'm currently using, "earwig" (a Dell R410); it > works fine on "bedbug" (a desktop PC pressed into service). It also > works fine with a 64-bit dom0. I'm looking at http://www.chiark.greenend.org.uk/~xensrcts/logs/2107/test-amd64-i386-pair/serial-earwig.log.0; is that the right log? It seems to be rebooting (repeatedly) at: Sep 8 11:45:34.232632 [ 3.200319] usb 6-3: New USB device found, idVendor=0424, idProduct=2514 Sep 8 11:45:34.351647 [ 3.204328] usb 6-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Sep 8 11:45:34.351670 [ 3.218041] thermal: Unknown symbol acpi_processor_set_thermal_limit Sep 8 11:45:34.363642 Starting system log daemon: syslogd, klogd. Sep 8 11:45:34.368629 Detecting network hardware ..94%..100% Sep 8 11:45:35.367649 Configuring the network with DHCP ..100% Is it rebooting after printing "thermal: Unknown symbol acpi_processor_set_thermal_limit"? That message on its own suggests that there's something wrong with the kernel config. But I don't see why it should lead to a reboot. J