All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Todd Deshane <todd.deshane@xen.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Kernel bug from 3.0 (was phy disks and vifs timing out in DomU)
Date: Thu, 25 Aug 2011 22:11:44 +0100	[thread overview]
Message-ID: <4E56BA90.3050907@overnetdata.com> (raw)
In-Reply-To: <20110819125615.GA26558@dumpdata.com>

[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]

On 19/08/2011 13:56, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 19, 2011 at 11:22:15AM +0100, Anthony Wright wrote:
>> On 03/08/2011 16:28, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Jul 29, 2011 at 08:53:02AM +0100, Anthony Wright wrote:
>>>> I've just upgraded to xen 4.1.1 with a stock 3.0 kernel on dom0 (with
>>>> the vga-support patch backported). I can't get my DomU's to work due to
>>>> the phy disks and vifs timing out in DomU and looking through my logs
>>>> this morning I'm getting a consistent kernel bug report with xen
>>>> mentioned at the top of the stack trace and vifdisconnect mentioned on
>>> Yikes! Ian any ideas what to try?
>>>
>>> Anthony, can you compile the kernel with debug=y and when this happens
>>> see what 'xl dmesg' gives? Also there is also the 'xl debug-keys g' which
>>> should dump the grants in use.. that might help a bit.
>> I've compiled a 3.0.1 kernel with CONFIG_DEBUG=Y (a number of other
>> config values appeared at this point, and I took defaults for them).
>>
>> The output from /var/log/messages & 'xl dmesg' is attached. There was no
>> output from 'xl debug-keys g'.
> Ok, so I am hitting this too - I was hoping that the patch from Stefano
> would have fixed the issue, but sadly it did not.
>
> Let me (I am traveling right now) see if I can come up with an internim
> solution until Ian comes with the right fix.
>
On different hardware with the same software I'm also getting problems
starting DomUs, but this time the error is different. I've attached a
copy of the xl console output, but basically the server hang at
"Mount-cache hash table entries: 512". Again the VM is paravirtualised,
and again I get a qemu-dm process for it.

The references to this message are normally related to memory issues,
but the server has only 1000M of ram, so can't see it causing too much
of a problem.

Is this related to the other problems I'm seeing or completely separate?

thanks,

Anthony



[-- Attachment #2: domU.log --]
[-- Type: text/plain, Size: 7347 bytes --]

[    3.226308] Reserving virtual address space above 0xf5800000                
[    3.226308] Linux version 2.6.30.1 (root@deb-builder) (gcc version 4.3.2 (GCC) ) #2 SMP Mon Jul 18 12:06:12 GMT 2011
[    3.226308] KERNEL supported cpus:                                                                                  
[    3.226308]   Intel GenuineIntel                                                                                    
[    3.226308]   AMD AuthenticAMD                                                                                      
[    3.226308]   NSC Geode by NSC                                                                                      
[    3.226308]   Cyrix CyrixInstead                                                                                    
[    3.226308]   Centaur CentaurHauls                                                                                  
[    3.226308]   Transmeta GenuineTMx86                                                                                
[    3.226308]   Transmeta TransmetaCPU                                                                                
[    3.226308]   UMC UMC UMC UMC                                                                                       
[    3.226308] BIOS-provided physical RAM map:                                                                         
[    3.226308]  Xen: 0000000000000000 - 00000000000a0000 (usable)                                                      
[    3.226308]  Xen: 00000000000a0000 - 0000000000100000 (reserved)                                                    
[    3.226308]  Xen: 0000000000100000 - 000000000065c000 (usable)                                                      
[    3.226308]  Xen: 000000000065c000 - 0000000000853000 (reserved)                                                    
[    3.226308]  Xen: 0000000000853000 - 000000007d000000 (usable)                                                      
[    3.226308] DMI not present or invalid.                                                                             
[    3.226308] last_pfn = 0x7d000 max_arch_pfn = 0x1000000                                                             
[    3.226308] init_memory_mapping: 0000000000000000-00000000229fe000                                                  
[    3.226308] NX (Execute Disable) protection: active                                                                 
[    3.226308] 1446MB HIGHMEM available.                                                                               
[    3.226308] 553MB LOWMEM available.                                                                                 
[    3.226308]   mapped low ram: 0 - 229fe000                                                                          
[    3.226308]   low ram: 0 - 229fe000                                                                                 
[    3.226308]   node 0 low ram: 00000000 - 229fe000                                                                   
[    3.226308]   node 0 bootmap 00007000 - 0000b540                                                                    
[    3.226308] (7 early reservations) ==> bootmem [0000000000 - 00229fe000]                                            
[    3.226308]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]                           
[    3.226308]   #1 [0000853000 - 000085b000]   XEN PAGETABLES ==> [0000853000 - 000085b000]                           
[    3.226308]   #2 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]                           
[    3.226308]   #3 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]                           
[    3.226308]   #4 [0000100000 - 00005366f4]    TEXT DATA BSS ==> [0000100000 - 00005366f4]                           
[    3.226308]   #5 [0000537000 - 0000643000]          PGTABLE ==> [0000537000 - 0000643000]                           
[    3.226308]   #6 [0000007000 - 000000c000]          BOOTMAP ==> [0000007000 - 000000c000]                           
[    3.226308] Zone PFN ranges:                                                                                        
[    3.226308]   DMA      0x00000000 -> 0x00001000                                                                     
[    3.226308]   Normal   0x00001000 -> 0x000229fe                                                                     
[    3.226308]   HighMem  0x000229fe -> 0x0007d000                                                                     
[    3.226308] Movable zone start PFN for each node                                                                    
[    3.226308] early_node_map[3] active PFN ranges                                                                     
[    3.226308]     0: 0x00000000 -> 0x000000a0                                                                         
[    3.226308]     0: 0x00000100 -> 0x0000065c                                                                         
[    3.226308]     0: 0x00000853 -> 0x0007d000
[    3.226308] Using APIC driver default
[    3.226308] SMP: Allowing 8 CPUs, 0 hotplug CPUs
[    3.226308] Local APIC disabled by BIOS -- you can enable it with "lapic"
[    3.226308] Allocating PCI resources starting at 80000000 (gap: 7d000000:83000000)
[    3.226308] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[    3.226308] PERCPU: Allocated 6 4k pages, static data 22940 bytes
[    3.810521] Xen: using vcpu_info placement
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 507400
[    0.000000] Kernel command line: root=/dev/xvda1
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] NR_IRQS:512
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2533.462 MHz processor.
[    0.010000] Console: colour dummy device 80x25
[    0.010000] console [tty0] enabled
[    0.010000] console [hvc0] enabled
[    0.010000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.010000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.010000] Initializing HighMem for node 0 (000229fe:0007d000)
[    0.010000] Memory: 2022248k/2048000k available (2539k kernel code, 22480k reserved, 1067k data, 244k init, 1480712k highmem)
[    0.010000] virtual kernel memory layout:
[    0.010000]     fixmap  : 0xf574f000 - 0xf57ff000   ( 704 kB)
[    0.010000]     pkmap   : 0xf5200000 - 0xf5400000   (2048 kB)
[    0.010000]     vmalloc : 0xe31fe000 - 0xf51fe000   ( 288 MB)
[    0.010000]     lowmem  : 0xc0000000 - 0xe29fe000   ( 553 MB)
[    0.010000]       .init : 0xc0490000 - 0xc04cd000   ( 244 kB)
[    0.010000]       .data : 0xc037ae1d - 0xc0485e18   (1067 kB)
[    0.010000]       .text : 0xc0100000 - 0xc037ae1d   (2539 kB)
[    0.010000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.010000] installing Xen timer for CPU 0
[    0.010000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.92 BogoMIPS (lpj=25334620)
[    0.010000] Mount-cache hash table entries: 512

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

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

  parent reply	other threads:[~2011-08-25 21:11 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com>
2011-07-28  7:24 ` phy disks and vifs timing out in DomU Anthony Wright
2011-07-28 15:01   ` Todd Deshane
2011-07-28 15:36     ` Anthony Wright
2011-07-28 15:46       ` Todd Deshane
2011-07-28 16:00         ` Anthony Wright
2011-07-29 15:55           ` Konrad Rzeszutek Wilk
2011-07-29 18:40             ` Anthony Wright
2011-07-29 20:01               ` Konrad Rzeszutek Wilk
2011-07-30 17:05                 ` Anthony Wright
2011-08-01 11:03                   ` Anthony Wright
2011-07-28 16:28       ` Ian Campbell
2011-07-29  7:53         ` Kernel bug from 3.0 (was phy disks and vifs timing out in DomU) Anthony Wright
2011-08-03 15:28           ` Konrad Rzeszutek Wilk
2011-08-09 16:35             ` Konrad Rzeszutek Wilk
2011-08-19 10:22             ` Anthony Wright
2011-08-19 12:56               ` Konrad Rzeszutek Wilk
2011-08-22 11:02                 ` Anthony Wright
2011-08-25 20:31                 ` Anthony Wright
2011-08-26 14:26                   ` Konrad Rzeszutek Wilk
2011-08-26 14:44                     ` Konrad Rzeszutek Wilk
2011-08-29 12:13                       ` Anthony Wright
2011-08-31 16:58                       ` David Vrabel
2011-08-31 17:07                         ` Konrad Rzeszutek Wilk
2011-09-01  7:42                           ` Ian Campbell
2011-09-01 14:23                             ` Konrad Rzeszutek Wilk
2011-09-01 15:12                               ` David Vrabel
2011-09-01 15:37                                 ` Konrad Rzeszutek Wilk
2011-09-01 15:43                                   ` Ian Campbell
2011-09-01 16:07                                     ` Konrad Rzeszutek Wilk
2011-09-07 12:57                                 ` Anthony Wright
2011-09-07 18:35                                   ` Konrad Rzeszutek Wilk
2011-09-01 15:12                               ` Ian Campbell
2011-09-01 15:38                                 ` Konrad Rzeszutek Wilk
2011-09-01 15:44                                   ` Ian Campbell
2011-09-01 17:34                                     ` Jeremy Fitzhardinge
2011-09-01 19:19                                       ` Ian Campbell
2011-09-01 17:32                             ` Jeremy Fitzhardinge
2011-09-01 19:21                               ` Ian Campbell
2011-09-01 20:34                                 ` Jeremy Fitzhardinge
2011-09-02  7:17                                   ` Ian Campbell
2011-09-02 20:26                                     ` Jeremy Fitzhardinge
2011-09-03 10:27                                       ` Ian Campbell
2011-09-23 12:35                                         ` Anthony Wright
2011-09-23 12:49                                           ` David Vrabel
2011-08-29 17:33                     ` Anthony Wright
2011-08-25 21:11                 ` Anthony Wright [this message]
2011-08-26  7:10                   ` Sander Eikelenboom
2011-08-26 11:23                     ` Pasi Kärkkäinen
2011-08-26 12:16                   ` Stefano Stabellini
2011-08-26 12:15                     ` Anthony Wright
2011-08-26 12:32                       ` Stefano Stabellini
2011-07-29 15:48         ` phy disks and vifs timing out in DomU (only on certain hardware) Anthony Wright
2011-07-29 16:06           ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E56BA90.3050907@overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=todd.deshane@xen.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.