All of lore.kernel.org
 help / color / mirror / Atom feed
* xen 4.0.0 pvops-dom0: machine locks up
@ 2010-02-03  8:57 Yasir Assam
  2010-02-03 15:52 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 4+ messages in thread
From: Yasir Assam @ 2010-02-03  8:57 UTC (permalink / raw)
  To: xen-devel

Again, I don't know if this is my hardware playing up, but after leaving 
my Xen machine unattended for a few hours I noticed it was totally 
unresponsive. The screen was in sleep mode, but the power LED was still 
on. Even pressing the reset or power buttons on the case didn't do 
anything. I had to press & hold the power button for 4 seconds to do a 
hard reboot.

When I rebooted I couldn't find anything in either the hypervisor, dom0 
or domU logs do indicate what went wrong.

I'm sorry this isn't a helpful bug report (it may not even be a Xen bug) 
but I thought it might be good to report it anyway, in case it's a bug 
with rc2 or the pvops dom0 (I was running a couple of pv domUs).

Thanks,
Yasir

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xen 4.0.0 pvops-dom0: machine locks up
  2010-02-03  8:57 xen 4.0.0 pvops-dom0: machine locks up Yasir Assam
@ 2010-02-03 15:52 ` Konrad Rzeszutek Wilk
  2010-02-03 20:48   ` Yasir Assam
  0 siblings, 1 reply; 4+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-02-03 15:52 UTC (permalink / raw)
  To: Yasir Assam; +Cc: xen-devel

> When I rebooted I couldn't find anything in either the hypervisor, dom0  
> or domU logs do indicate what went wrong.

What flavour of Dom0 did you have (32/64?)? Did you also have X running? If so,
what video card do you have?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xen 4.0.0 pvops-dom0: machine locks up
  2010-02-03 15:52 ` Konrad Rzeszutek Wilk
@ 2010-02-03 20:48   ` Yasir Assam
  2010-02-05 16:31     ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 4+ messages in thread
From: Yasir Assam @ 2010-02-03 20:48 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 3733 bytes --]

dom0 is 64 bit (as are all the pv-only domUs).

I do have X running. This runs on the Intel Core i 530 which has 
"onboard" graphics (2nd die on the CPU chip) and X correctly picks the 
Intel driver.

I think the kernel driver for this is i915.

Here's a dump from lspci:

$ lspci -k
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller 
(rev 12)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 12)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series 
Chipset HECI Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset 
USB2 Enhanced Host Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8435
         Kernel driver in use: HDA Intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 (rev 06)
         Kernel driver in use: pcieport-driver
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 3 (rev 06)
         Kernel driver in use: pcieport-driver
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 4 (rev 06)
         Kernel driver in use: pcieport-driver
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 5 (rev 06)
         Kernel driver in use: pcieport-driver
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 6 (rev 06)
         Kernel driver in use: pcieport-driver
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset 
USB2 Enhanced Host Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface 
Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 
port SATA IDE Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus 
Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 
port SATA IDE Controller (rev 06)
         Subsystem: ASUSTeK Computer Inc. Device 8383
         Kernel driver in use: ata_piix
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
         Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard
         Kernel driver in use: r8169
05:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller
         Subsystem: ASUSTeK Computer Inc. Device 824f
         Kernel driver in use: pata_jmicron



>> When I rebooted I couldn't find anything in either the hypervisor, dom0
>> or domU logs do indicate what went wrong.
>>      
> What flavour of Dom0 did you have (32/64?)? Did you also have X running? If so,
> what video card do you have?
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2664 - Release Date: 02/03/10 06:35:00
>
>    


[-- Attachment #1.2: Type: text/html, Size: 5357 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xen 4.0.0 pvops-dom0: machine locks up
  2010-02-03 20:48   ` Yasir Assam
@ 2010-02-05 16:31     ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 4+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-02-05 16:31 UTC (permalink / raw)
  To: Yasir Assam; +Cc: xen-devel

On Thu, Feb 04, 2010 at 07:48:34AM +1100, Yasir Assam wrote:
> dom0 is 64 bit (as are all the pv-only domUs).
>
> I do have X running. This runs on the Intel Core i 530 which has  
> "onboard" graphics (2nd die on the CPU chip) and X correctly picks the  
> Intel driver.

Can you send me along your /var/log/Xorg.log output?

You said the machine hanged, were you able to ping it? You wouldn't have
had a serial port attached to that machine to log all of its kernel/Xen
outputs?
>
> I think the kernel driver for this is i915.

That sounds right.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-02-05 16:31 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-03  8:57 xen 4.0.0 pvops-dom0: machine locks up Yasir Assam
2010-02-03 15:52 ` Konrad Rzeszutek Wilk
2010-02-03 20:48   ` Yasir Assam
2010-02-05 16:31     ` Konrad Rzeszutek Wilk

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.