All of lore.kernel.org
 help / color / mirror / Atom feed
* xm save still fails
@ 2009-11-17  2:35 Yasir Assam
  2009-11-17  3:41 ` Dan Magenheimer
  2009-11-20  4:06 ` Jeremy Fitzhardinge
  0 siblings, 2 replies; 6+ messages in thread
From: Yasir Assam @ 2009-11-17  2:35 UTC (permalink / raw)
  To: xen-devel

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

I sent a message to this list a few weeks ago about this but I'm not 
sure that it was ever resolved.

xm save still fails on xen 3.4.2 when I try to save a domU running 
pv-ops 2.6.31.6 (domU & dom0 are 64-bit).

The original thread is here (contains log & config files):
http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01477.html

If anyone can tell me whether this is a bug, or whether I'm doing 
something wrong, I'd really appreciate it.

Thanks,
Yasir

[-- Attachment #2.1: "AVG certification" --]
[-- Type: text/plain, Size: 159 bytes --]


No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.68/2507 - Release Date: 11/16/09 19:53:00

[-- Attachment #3: 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] 6+ messages in thread

* RE: xm save still fails
  2009-11-17  2:35 xm save still fails Yasir Assam
@ 2009-11-17  3:41 ` Dan Magenheimer
  2009-11-17 23:52   ` Yasir Assam
  2009-11-20  4:06 ` Jeremy Fitzhardinge
  1 sibling, 1 reply; 6+ messages in thread
From: Dan Magenheimer @ 2009-11-17  3:41 UTC (permalink / raw)
  To: Yasir Assam, xen-devel

Jeremy suggested trying out this bug fix a few days ago, but
I haven't had a chance to try it yet as my test machines
have been in use for other things.

http://lists.xensource.com/archives/html/xen-devel/2009-11/msg00672.html

Pasi also noticed that save/restore did not fail for a single
vcpu domain but has a (non-fatal) error message, but does fail
for vcpus>1 (see other email in the same thread).

It would be great if you could try this fix and let us
know if it solves one or both problems.  Since the fix
is on the Linux side, there's a good chance it will fix
the problem for both 3.4.2 and xen-unstable.

> -----Original Message-----
> From: Yasir Assam [mailto:mail@endlessvoid.com]
> Sent: Monday, November 16, 2009 7:36 PM
> To: xen-devel@lists.xensource.com
> Subject: [Xen-devel] xm save still fails
> 
> 
> I sent a message to this list a few weeks ago about this but I'm not 
> sure that it was ever resolved.
> 
> xm save still fails on xen 3.4.2 when I try to save a domU running 
> pv-ops 2.6.31.6 (domU & dom0 are 64-bit).
> 
> The original thread is here (contains log & config files):
> http://lists.xensource.com/archives/html/xen-devel/2009-10/msg
01477.html

If anyone can tell me whether this is a bug, or whether I'm doing 
something wrong, I'd really appreciate it.

Thanks,
Yasir

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

* Re: xm save still fails
  2009-11-17  3:41 ` Dan Magenheimer
@ 2009-11-17 23:52   ` Yasir Assam
  2009-11-19 13:25     ` Valtteri Kiviniemi
  0 siblings, 1 reply; 6+ messages in thread
From: Yasir Assam @ 2009-11-17 23:52 UTC (permalink / raw)
  To: Dan Magenheimer; +Cc: xen-devel

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

Thanks for responding Dan.

I applied that patch to my domU kernel (2.6.31.6) and I still get the 
same problem.

This is what I got on the domU console:

PM: Device rtc_cmos failed to suspend: error -22
xen suspend: dpm_suspend_start -22

and I've attached /var/log/kern.log from the domU.

The same thing happens whether I use 1 or 2 VCPUs.

Thanks,
Yasir


> Jeremy suggested trying out this bug fix a few days ago, but
> I haven't had a chance to try it yet as my test machines
> have been in use for other things.
>
> http://lists.xensource.com/archives/html/xen-devel/2009-11/msg00672.html
>
> Pasi also noticed that save/restore did not fail for a single
> vcpu domain but has a (non-fatal) error message, but does fail
> for vcpus>1 (see other email in the same thread).
>
> It would be great if you could try this fix and let us
> know if it solves one or both problems.  Since the fix
> is on the Linux side, there's a good chance it will fix
> the problem for both 3.4.2 and xen-unstable.
>
>   
>> -----Original Message-----
>> From: Yasir Assam [mailto:mail@endlessvoid.com]
>> Sent: Monday, November 16, 2009 7:36 PM
>> To: xen-devel@lists.xensource.com
>> Subject: [Xen-devel] xm save still fails
>>
>>
>> I sent a message to this list a few weeks ago about this but I'm not 
>> sure that it was ever resolved.
>>
>> xm save still fails on xen 3.4.2 when I try to save a domU running 
>> pv-ops 2.6.31.6 (domU & dom0 are 64-bit).
>>
>> The original thread is here (contains log & config files):
>> http://lists.xensource.com/archives/html/xen-devel/2009-10/msg
>>     
> 01477.html
>
> If anyone can tell me whether this is a bug, or whether I'm doing 
> something wrong, I'd really appreciate it.
>
> Thanks,
> Yasir
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.425 / Virus Database: 270.14.68/2507 - Release Date: 11/16/09 19:53:00
>
>   


-- 
Yasir Assam
Endless Void - Software and Web Development

http://www.endlessvoid.com
Tel: +61 (0)2 6679 7084

525 Midginbil Road
Midginbil
NSW 2484
Australia

ABN 57 175 061 347


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

Nov 18 10:35:54 lit kernel: imklog 3.18.6, log source = /proc/kmsg started.
Nov 18 10:35:54 lit kernel: Linux version 2.6.31.6-xen-domU-64 (yhassan@eir) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #2 SMP Wed Nov 18 10:35:03 EST 2009
Nov 18 10:35:54 lit kernel: Command line: root=/dev/xvda2 ro console=hvc0
Nov 18 10:35:54 lit kernel: KERNEL supported cpus:
Nov 18 10:35:54 lit kernel:  AMD AuthenticAMD
Nov 18 10:35:54 lit kernel: BIOS-provided physical RAM map:
Nov 18 10:35:54 lit kernel: Xen: 0000000000000000 - 00000000000a0000 (usable)
Nov 18 10:35:54 lit kernel: Xen: 00000000000a0000 - 0000000000100000 (reserved)
Nov 18 10:35:54 lit kernel: Xen: 0000000000100000 - 0000000008000000 (usable)
Nov 18 10:35:54 lit kernel: DMI not present or invalid.
Nov 18 10:35:54 lit kernel: last_pfn = 0x8000 max_arch_pfn = 0x400000000
Nov 18 10:35:54 lit kernel: e820 update range: 0000000000001000 - 0000000000006000 (usable) ==> (reserved)
Nov 18 10:35:54 lit kernel: Scanning 1 areas for low memory corruption
Nov 18 10:35:54 lit kernel: modified physical RAM map:
Nov 18 10:35:54 lit kernel: modified: 0000000000000000 - 0000000000001000 (usable)
Nov 18 10:35:54 lit kernel: modified: 0000000000001000 - 0000000000006000 (reserved)
Nov 18 10:35:54 lit kernel: modified: 0000000000006000 - 00000000000a0000 (usable)
Nov 18 10:35:54 lit kernel: modified: 00000000000a0000 - 0000000000100000 (reserved)
Nov 18 10:35:54 lit kernel: modified: 0000000000100000 - 0000000008000000 (usable)
Nov 18 10:35:54 lit kernel: initial memory mapped : 0 - 20000000
Nov 18 10:35:54 lit kernel: init_memory_mapping: 0000000000000000-0000000008000000
Nov 18 10:35:54 lit kernel: 0000000000 - 0008000000 page 4k
Nov 18 10:35:54 lit kernel: kernel direct mapping tables up to 8000000 @ 8000-4a000
Nov 18 10:35:54 lit kernel: (6 early reservations) ==> bootmem [0000000000 - 0008000000]
Nov 18 10:35:54 lit kernel:  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Nov 18 10:35:54 lit kernel:  #1 [000150f000 - 000151e000]   XEN PAGETABLES ==> [000150f000 - 000151e000]
Nov 18 10:35:54 lit kernel:  #2 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
Nov 18 10:35:54 lit kernel:  #3 [0001000000 - 00014ab424]    TEXT DATA BSS ==> [0001000000 - 00014ab424]
Nov 18 10:35:54 lit kernel:  #4 [00014cc000 - 000150f000]   XEN START INFO ==> [00014cc000 - 000150f000]
Nov 18 10:35:54 lit kernel:  #5 [0000008000 - 0000038000]          PGTABLE ==> [0000008000 - 0000038000]
Nov 18 10:35:54 lit kernel: Zone PFN ranges:
Nov 18 10:35:54 lit kernel:  DMA      0x00000000 -> 0x00001000
Nov 18 10:35:54 lit kernel:  DMA32    0x00001000 -> 0x00100000
Nov 18 10:35:54 lit kernel:  Normal   0x00100000 -> 0x00100000
Nov 18 10:35:54 lit kernel: Movable zone start PFN for each node
Nov 18 10:35:54 lit kernel: early_node_map[3] active PFN ranges
Nov 18 10:35:54 lit kernel:    0: 0x00000000 -> 0x00000001
Nov 18 10:35:54 lit kernel:    0: 0x00000006 -> 0x000000a0
Nov 18 10:35:54 lit kernel:    0: 0x00000100 -> 0x00008000
Nov 18 10:35:54 lit kernel: On node 0 totalpages: 32667
Nov 18 10:35:54 lit kernel:  DMA zone: 56 pages used for memmap
Nov 18 10:35:54 lit kernel:  DMA zone: 51 pages reserved
Nov 18 10:35:54 lit kernel:  DMA zone: 3888 pages, LIFO batch:0
Nov 18 10:35:54 lit kernel:  DMA32 zone: 392 pages used for memmap
Nov 18 10:35:54 lit kernel:  DMA32 zone: 28280 pages, LIFO batch:7
Nov 18 10:35:54 lit kernel: SMP: Allowing 1 CPUs, 0 hotplug CPUs
Nov 18 10:35:54 lit kernel: No local APIC present
Nov 18 10:35:54 lit kernel: APIC: disable apic facility
Nov 18 10:35:54 lit kernel: nr_irqs_gsi: 16
Nov 18 10:35:54 lit kernel: PM: Registered nosave memory: 0000000000001000 - 0000000000006000
Nov 18 10:35:54 lit kernel: PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
Nov 18 10:35:54 lit kernel: Allocating PCI resources starting at 8000000 (gap: 8000000:f8000000)
Nov 18 10:35:54 lit kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:1 nr_node_ids:1
Nov 18 10:35:54 lit kernel: PERCPU: Allocated 20 4k pages, static data 77920 bytes
Nov 18 10:35:54 lit kernel: trying to map vcpu_info 0 at ffffc9000000b020, mfn 62e80, offset 32
Nov 18 10:35:54 lit kernel: cpu 0 using vcpu_info at ffffc9000000b020
Nov 18 10:35:54 lit kernel: Xen: using vcpu_info placement
Nov 18 10:35:54 lit kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32168
Nov 18 10:35:54 lit kernel: Kernel command line: root=/dev/xvda2 ro console=hvc0
Nov 18 10:35:54 lit kernel: PID hash table entries: 512 (order: 9, 4096 bytes)
Nov 18 10:35:54 lit kernel: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Nov 18 10:35:54 lit kernel: Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Nov 18 10:35:54 lit kernel: Initializing CPU#0
Nov 18 10:35:54 lit kernel: Memory: 123060k/131072k available (2799k kernel code, 404k absent, 7444k reserved, 1230k data, 388k init)
Nov 18 10:35:54 lit kernel: NR_IRQS:320
Nov 18 10:35:54 lit kernel: Detected 2411.110 MHz processor.
Nov 18 10:35:54 lit kernel: Console: colour dummy device 80x25
Nov 18 10:35:54 lit kernel: console [tty0] enabled
Nov 18 10:35:54 lit kernel: console [hvc0] enabled
Nov 18 10:35:54 lit kernel: Xen: using vcpuop timer interface
Nov 18 10:35:54 lit kernel: installing Xen timer for CPU 0
Nov 18 10:35:54 lit kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4822.22 BogoMIPS (lpj=24111100)
Nov 18 10:35:54 lit kernel: Mount-cache hash table entries: 256
Nov 18 10:35:54 lit kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Nov 18 10:35:54 lit kernel: CPU: L2 Cache: 512K (64 bytes/line)
Nov 18 10:35:54 lit kernel: tseg: 0000000000
Nov 18 10:35:54 lit kernel: CPU: Physical Processor ID: 0
Nov 18 10:35:54 lit kernel: CPU: Processor Core ID: 1
Nov 18 10:35:54 lit kernel: SMP alternatives: switching to UP code
Nov 18 10:35:54 lit kernel: Freeing SMP alternatives: 32k freed
Nov 18 10:35:54 lit kernel: cpu 0 spinlock event irq 1
Nov 18 10:35:54 lit kernel: Brought up 1 CPUs
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:platform
Nov 18 10:35:54 lit kernel: Booting paravirtualized kernel on Xen
Nov 18 10:35:54 lit kernel: Xen version: 3.4.2 (preserve-AD)
Nov 18 10:35:54 lit kernel: Grant table initialized
Nov 18 10:35:54 lit kernel: Time: 165:165:165  Date: 165/165/65
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 16
Nov 18 10:35:54 lit kernel: PM: Adding info for xen:vbd-51714
Nov 18 10:35:54 lit kernel: PM: Adding info for xen:vbd-51713
Nov 18 10:35:54 lit kernel: PM: Adding info for xen:vif-0
Nov 18 10:35:54 lit kernel: PM: Adding info for xen:console-0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:vtcon0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:default
Nov 18 10:35:54 lit kernel: bio: create slab <bio-0> at 0
Nov 18 10:35:54 lit kernel: xen_balloon: Initialising balloon driver.
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:lo
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:mem
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:kmem
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:null
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:zero
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:full
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:random
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:urandom
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:kmsg
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 2
Nov 18 10:35:54 lit kernel: IP route cache hash table entries: 1024 (order: 1, 8192 bytes)
Nov 18 10:35:54 lit kernel: TCP established hash table entries: 4096 (order: 4, 65536 bytes)
Nov 18 10:35:54 lit kernel: Switched to high resolution mode on CPU 0
Nov 18 10:35:54 lit kernel: TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
Nov 18 10:35:54 lit kernel: TCP: Hash tables configured (established 4096 bind 4096)
Nov 18 10:35:54 lit kernel: TCP reno registered
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 1
Nov 18 10:35:54 lit kernel: PM: Adding info for platform:rtc_cmos
Nov 18 10:35:54 lit kernel: platform rtc_cmos: registered platform RTC device (no PNP device found)
Nov 18 10:35:54 lit kernel: cpu0(1) debug files 149
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:msr0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:cpu0
Nov 18 10:35:54 lit kernel: Scanning for low memory corruption every 60 seconds
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:snapshot
Nov 18 10:35:54 lit kernel: audit: initializing netlink socket (disabled)
Nov 18 10:35:54 lit kernel: type=2000 audit(1258500948.968:1): initialized
Nov 18 10:35:54 lit kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Nov 18 10:35:54 lit kernel: msgmni has been set to 256
Nov 18 10:35:54 lit kernel: alg: No test for stdrng (krng)
Nov 18 10:35:54 lit kernel: io scheduler noop registered
Nov 18 10:35:54 lit kernel: io scheduler anticipatory registered
Nov 18 10:35:54 lit kernel: io scheduler deadline registered
Nov 18 10:35:54 lit kernel: io scheduler cfq registered (default)
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:fbcon
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:evtchn
Nov 18 10:35:54 lit kernel: Event-channel device installed.
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:console
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:vcs
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:vcsa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:vcs1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:vcsa1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty10
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty11
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty12
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty13
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty14
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty15
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty16
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty17
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty18
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty19
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty20
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty21
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty22
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty23
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty24
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty25
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty26
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty27
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty28
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty29
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty30
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty31
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty32
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty33
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty34
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty35
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty36
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty37
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty38
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty39
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty40
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty41
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty42
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty43
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty44
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty45
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty46
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty47
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty48
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty49
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty50
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty51
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty52
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty53
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty54
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty55
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty56
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty57
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty58
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty59
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty60
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty61
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty62
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:tty63
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyp9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptypa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptypb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptypc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptypd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptype
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptypf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyq9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqe
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyqf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyr9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyra
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyrb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyrc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyrd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyre
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyrf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptys9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptysa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptysb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptysc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptysd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptyse
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptysf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyp9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttypa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttypb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttypc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttypd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttype
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttypf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyq9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqe
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyqf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyr9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyra
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyrb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyrc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyrd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyre
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyrf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys8
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttys9
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttysa
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttysb
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttysc
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttysd
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttyse
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ttysf
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ptmx
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:hvc7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:0
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:3
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:4
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:5
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:6
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:loop7
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:7:7
Nov 18 10:35:54 lit kernel: loop: module loaded
Nov 18 10:35:54 lit kernel: Initialising Xen virtual ethernet driver.
Nov 18 10:35:54 lit kernel: blkfront: xvda2: barriers enabled
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:xvda2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:202:2
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:eth0
Nov 18 10:35:54 lit kernel: blkfront: xvda1: barriers enabled
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:xvda1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:202:1
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:dummy0
Nov 18 10:35:54 lit kernel: i8042.c: No controller found.
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:mice
Nov 18 10:35:54 lit kernel: mice: PS/2 mouse device common for all mice
Nov 18 10:35:54 lit kernel: cpuidle: using governor ladder
Nov 18 10:35:54 lit kernel: Netfilter messages via NETLINK v0.30.
Nov 18 10:35:54 lit kernel: nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Nov 18 10:35:54 lit kernel: CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
Nov 18 10:35:54 lit kernel: nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
Nov 18 10:35:54 lit kernel: sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Nov 18 10:35:54 lit kernel: ctnetlink v0.93: registering with nfnetlink.
Nov 18 10:35:54 lit kernel: xt_time: kernel timezone is -0000
Nov 18 10:35:54 lit kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 18 10:35:54 lit kernel: ClusterIP Version 0.8 loaded successfully
Nov 18 10:35:54 lit kernel: arp_tables: (C) 2002 David S. Miller
Nov 18 10:35:54 lit kernel: TCP cubic registered
Nov 18 10:35:54 lit kernel: Initializing XFRM netlink socket
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 10
Nov 18 10:35:54 lit kernel: lo: Disabled Privacy Extensions
Nov 18 10:35:54 lit kernel: IPv6 over IPv4 tunneling driver
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:sit0
Nov 18 10:35:54 lit kernel: sit0: Disabled Privacy Extensions
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:ip6tnl0
Nov 18 10:35:54 lit kernel: ip6tnl0: Disabled Privacy Extensions
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 17
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 15
Nov 18 10:35:54 lit kernel: RPC: Registered udp transport module.
Nov 18 10:35:54 lit kernel: RPC: Registered tcp transport module.
Nov 18 10:35:54 lit kernel: NET: Registered protocol family 33
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:cpu_dma_latency
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:network_latency
Nov 18 10:35:54 lit kernel: PM: Adding info for No Bus:network_throughput
Nov 18 10:35:54 lit kernel: PM: Resume from disk failed.
Nov 18 10:35:54 lit kernel: registered taskstats version 1
Nov 18 10:35:54 lit kernel: XENBUS: Device with no driver: device/console/0
Nov 18 10:35:54 lit kernel:  Magic number: 1:252:3141
Nov 18 10:35:54 lit kernel: kjournald starting.  Commit interval 5 seconds
Nov 18 10:35:54 lit kernel: EXT3-fs: mounted filesystem with writeback data mode.
Nov 18 10:35:54 lit kernel: VFS: Mounted root (ext3 filesystem) readonly on device 202:2.
Nov 18 10:35:54 lit kernel: Freeing unused kernel memory: 388k freed
Nov 18 10:35:54 lit kernel: Adding 262136k swap on /dev/xvda1.  Priority:-1 extents:1 across:262136k SS
Nov 18 10:35:54 lit kernel: EXT3 FS on xvda2, internal journal
Nov 18 10:36:03 lit kernel: eth0: no IPv6 routers present
Nov 18 10:36:19 lit kernel: platform rtc_cmos: preparing suspend
Nov 18 10:36:19 lit kernel: platform rtc_cmos: suspend
Nov 18 10:36:19 lit kernel: PM: Device rtc_cmos failed to suspend: error -22
Nov 18 10:36:19 lit kernel: xen suspend: dpm_suspend_start -22

[-- Attachment #3.1: "AVG certification" --]
[-- Type: text/plain, Size: 159 bytes --]


No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.71/2510 - Release Date: 11/17/09 19:26:00

[-- Attachment #4: 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] 6+ messages in thread

* Re: xm save still fails
  2009-11-17 23:52   ` Yasir Assam
@ 2009-11-19 13:25     ` Valtteri Kiviniemi
  2009-11-23 16:31       ` Ian Campbell
  0 siblings, 1 reply; 6+ messages in thread
From: Valtteri Kiviniemi @ 2009-11-19 13:25 UTC (permalink / raw)
  To: xen-devel@lists.xensource.com >>
	"xen-devel@lists.xensource.com"

Hi,

I have this same problem with xen-unstable. When I try to save a domU it 
wont do anything. The following error messages appear:

in the domU's console that I'm trying to save:

Ignoring shutdown request: suspend

in xend.log:

[2009-11-19 15:18:51 2740] DEBUG (XendCheckpoint:124) [xc_save]: 
/usr/lib/xen/bin/xc_save 57 1 0 0 0
[2009-11-19 15:18:51 2740] INFO (XendCheckpoint:424) xc_save: failed to 
get the suspend evtchn port

- Valtteri Kiviniemi

Yasir Assam kirjoitti:
> Thanks for responding Dan.
> 
> I applied that patch to my domU kernel (2.6.31.6) and I still get the 
> same problem.
> 
> This is what I got on the domU console:
> 
> PM: Device rtc_cmos failed to suspend: error -22
> xen suspend: dpm_suspend_start -22
> 
> and I've attached /var/log/kern.log from the domU.
> 
> The same thing happens whether I use 1 or 2 VCPUs.
> 
> Thanks,
> Yasir
> 
> 
>> Jeremy suggested trying out this bug fix a few days ago, but
>> I haven't had a chance to try it yet as my test machines
>> have been in use for other things.
>>
>> http://lists.xensource.com/archives/html/xen-devel/2009-11/msg00672.html
>>
>> Pasi also noticed that save/restore did not fail for a single
>> vcpu domain but has a (non-fatal) error message, but does fail
>> for vcpus>1 (see other email in the same thread).
>>
>> It would be great if you could try this fix and let us
>> know if it solves one or both problems.  Since the fix
>> is on the Linux side, there's a good chance it will fix
>> the problem for both 3.4.2 and xen-unstable.
>>
>>  
>>> -----Original Message-----
>>> From: Yasir Assam [mailto:mail@endlessvoid.com]
>>> Sent: Monday, November 16, 2009 7:36 PM
>>> To: xen-devel@lists.xensource.com
>>> Subject: [Xen-devel] xm save still fails
>>>
>>>
>>> I sent a message to this list a few weeks ago about this but I'm not 
>>> sure that it was ever resolved.
>>>
>>> xm save still fails on xen 3.4.2 when I try to save a domU running 
>>> pv-ops 2.6.31.6 (domU & dom0 are 64-bit).
>>>
>>> The original thread is here (contains log & config files):
>>> http://lists.xensource.com/archives/html/xen-devel/2009-10/msg
>>>     
>> 01477.html
>>
>> If anyone can tell me whether this is a bug, or whether I'm doing 
>> something wrong, I'd really appreciate it.
>>
>> Thanks,
>> Yasir
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 8.5.425 / Virus Database: 
>> 270.14.68/2507 - Release Date: 11/16/09 19:53:00
>>
>>   
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> No virus found in this outgoing message.
> Checked by AVG - www.avg.com 
> Version: 8.5.425 / Virus Database: 270.14.71/2510 - Release Date: 11/17/09 19:26:00
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

* Re: xm save still fails
  2009-11-17  2:35 xm save still fails Yasir Assam
  2009-11-17  3:41 ` Dan Magenheimer
@ 2009-11-20  4:06 ` Jeremy Fitzhardinge
  1 sibling, 0 replies; 6+ messages in thread
From: Jeremy Fitzhardinge @ 2009-11-20  4:06 UTC (permalink / raw)
  To: Yasir Assam; +Cc: xen-devel

On 11/17/09 10:35, Yasir Assam wrote:
> I sent a message to this list a few weeks ago about this but I'm not
> sure that it was ever resolved.

I've been at Xen summit this week, so I haven't had a chance to look at it.

    J

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

* Re: xm save still fails
  2009-11-19 13:25     ` Valtteri Kiviniemi
@ 2009-11-23 16:31       ` Ian Campbell
  0 siblings, 0 replies; 6+ messages in thread
From: Ian Campbell @ 2009-11-23 16:31 UTC (permalink / raw)
  To: Valtteri Kiviniemi
  Cc: xen-devel@lists.xensource.com >>
	"xen-devel@lists.xensource.com"

On Thu, 2009-11-19 at 13:25 +0000, Valtteri Kiviniemi wrote:
> Hi,
> 
> I have this same problem with xen-unstable. When I try to save a domU it 
> wont do anything. The following error messages appear:
> 
> in the domU's console that I'm trying to save:
> 
> Ignoring shutdown request: suspend

That suggests you don't have CONFIG_PM_SLEEP enabled. Without this
suspend/resume cannot work.

Ian.

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

end of thread, other threads:[~2009-11-23 16:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-17  2:35 xm save still fails Yasir Assam
2009-11-17  3:41 ` Dan Magenheimer
2009-11-17 23:52   ` Yasir Assam
2009-11-19 13:25     ` Valtteri Kiviniemi
2009-11-23 16:31       ` Ian Campbell
2009-11-20  4:06 ` Jeremy Fitzhardinge

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.